Warning: getdate() [function.getdate]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 155

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 156

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: Cannot modify header information - headers already sent by (output started at /home/notgoo73/public_html/rss.php:155) in /home/notgoo73/public_html/rss.php on line 220
http://www.notgoodenough.org:/index.php Opticon RSS Feeds Consumer website www.NotGoodEnough.org en-au Mon, 04 Apr 2016 02:50:29 GMT http://www.notgoodenough.org:/viewtopic.php?f=96&t=42590 commsRus_NOT! Wed, 09 Sep 2015 11:52:38 GMT http://www.notgoodenough.org:/viewtopic.php?f=96&t=42391 grumpydog Sun, 22 Feb 2015 03:25:26 GMT http://www.notgoodenough.org:/viewtopic.php?f=96&t=35364 gettingthewordout Wed, 11 Feb 2015 01:18:04 GMT http://www.notgoodenough.org:/viewtopic.php?f=96&t=42294 1961Classic Thu, 08 Jan 2015 23:40:16 GMT http://www.notgoodenough.org:/viewtopic.php?f=96&t=35364 noshameo Wed, 16 Jul 2014 06:51:32 GMT http://www.notgoodenough.org:/viewtopic.php?f=96&t=41860 GaryBNE2 Wed, 22 Jan 2014 21:37:03 GMT http://www.notgoodenough.org:/viewtopic.php?f=96&t=41845 commodore98 Fri, 10 Jan 2014 06:55:56 GMT http://www.notgoodenough.org:/viewtopic.php?f=96&t=41845 Cas98 Tue, 07 Jan 2014 03:20:41 GMT http://www.notgoodenough.org:/viewtopic.php?f=96&t=41845 Cas98 Tue, 07 Jan 2014 03:19:55 GMT http://www.notgoodenough.org:/viewtopic.php?f=96&t=41845 Cas98 Tue, 07 Jan 2014 03:19:18 GMT http://www.notgoodenough.org:/viewtopic.php?f=96&t=41845 computerflyer Mon, 06 Jan 2014 01:14:32 GMT http://www.notgoodenough.org:/viewtopic.php?f=96&t=41845 Cas98 Sun, 05 Jan 2014 23:33:10 GMT http://www.notgoodenough.org:/viewtopic.php?f=96&t=41845 commodore98 Sun, 05 Jan 2014 04:14:55 GMT http://www.notgoodenough.org:/viewtopic.php?f=96&t=41845 Reggie2010 Sun, 05 Jan 2014 01:43:45 GMT http://www.notgoodenough.org:/viewtopic.php?f=96&t=41704 LucyGussy Wed, 14 Aug 2013 12:56:53 GMT So your real problem is that you are having trouble with an insurance company? The OP was clearly about the (lack of) satisfaction with the washing machine with a side reference to the extended warranty. It is implied the OP sees the residual time of an extended warranty as being more valuable than protecting the clothes by buying something new and writing off the extended warranty. The machine is 4+ years old, and well under an expected lifetime for a major appliance. But If a washing machine is $1-2,000, what is the cost of the shredded clothes and where does one simply write off the F&P product and extended warranty? One could expect a motor or pump or belt or bearing to fail - but not have the machine mature into a shredder with the lame response F&P provided. Maybe a bearing has gone creating a misalignment that can shred? Warranties cover things clearly broken, not just working badly. The former is the usual experience in Australia, the latter is taken on board to resolve only by the better companies. > Fisher and Paykel have advised us to wash our clothes in Washer Bags. F&P as a manufacturer should at least be able to offer engineering insights on potential causes. > Whilst I don't know who has been working on your appliance, it just may be that you have been sent to the wrong/inexperienced person for the repair. .... I'd be taking up the issue with the repairer. Some repairers might look for the problem, but as you should know that is not what manufacturers pay their warranty contractors to do - they pay you as little as possible to fix things that are clearly broken within strict T&C stated in the warranty/extended warranty. Please let us know how you would research the problem as a warranty contractor, and how you would be compensated. Assume there was no obvious sharp edge and the bearings were not clearly gone. What then?]]> http://www.notgoodenough.org:/viewtopic.php?f=96&t=41580 computerflyer Thu, 16 May 2013 21:54:25 GMT http://www.notgoodenough.org:/viewtopic.php?f=96&t=41580 DinerDog Thu, 16 May 2013 12:11:24 GMT disgraceful unit .... the product quality is pathetic .... called Sony numerous times .... repair centre as well 4 days since you reported the problem on the 29th is longer than I would expect to get a repair arrangement in place. Inhale, drop the rhetoric, and give them a chance. Whatever paperwork and process they go through, and however long that takes, is going to happen regardless. > the service quality is the worst you can ever experience in Australia. Sony is cited on-line for their less than crisp service network but I can assure you there are *FAR* worse than Sony. You were unlucky to get a unit that failed. It happens. TVs will usually fail in the first days to a few months, and my understanding is the failure rate then reduces to a very low number before rising toward the 4 to 5 years mark. That is one reason extended warranties are so profitable - the original failure is the manufacturer warranty, and then the products usually become stable until an extended warranty has expired. A more serious warranty problem some experience is that service agents repair the obvious fault - sometimes the same one again and again and again; they are neither paid to nor will look for why the part repetitively failed. For example, a dodgy power supply can cause other parts to have short lives, but the dodgy power supply has not failed so will neither be found nor replaced. Once the warranty ends the problem persists but the manufacturer advises it is now your problem. This is the nature of the industry, not just any particular manufacturer. In that circumstance, resolution is taking your case higher up in a company, and if receiving no help then to your state consumer law agency, or more often consumers will just suck up and buy a new one from a different brand. You called the helpline to lodge a complaint but cite a repair reference number. Is it a warranty repair reference or a complaint reference? You could be in difference processes for each. If you went the complaint route you may have added self inflicted days to a response as your case is reviewed and then acted on, not just queued for repair. Good luck getting a resolution.]]> http://www.notgoodenough.org:/viewtopic.php?f=96&t=41590 computerflyer Thu, 02 May 2013 21:18:12 GMT http://www.notgoodenough.org:/viewtopic.php?f=96&t=41590 rajsarin Thu, 02 May 2013 14:31:43 GMT http://www.notgoodenough.org:/viewtopic.php?f=96&t=41580 whingermonger1 Sat, 20 Apr 2013 04:08:56 GMT