APPLE FORUMS REMOVED THIS POST!
what are your thoughts?
Exact post:
Dear Apple, if I followed your advice I'd have ****** my computer and had to pay £100 - a forum member here fixed it in 5 seconds.
In a nutshell I had a trash warning glitch that I couldn't get rid of on a 9 day old gi7 imac that I had previously set up with all my info via Time Machine from my macbook pro. Calling Apple - they said that the only way to get rid of this was to perform a clean install making sure to back-up everything. I said that that was crazy and would involve me in having to invest in a new HD as I've already filled the imac with 500gb of stuff that has now been wiped over and I don't have a spare 500 gigs kicking around. I told them that I'm pretty sure a simple Terminal command would do the trick but they told me that they don't train their "help" to use it and that it was there for developers. I said that as it was their software which they installed then they should at least have people on the end of the phone that could help. After causing a fuss and wanting to make complaints I was passed to a senior guy who tracked down this exact problem on this forum and emailed me the link. We went through the terminal commands with no luck but I contacted the guy directly - Dave Sneddon, known as "dbsneddon" here. Two simple Terminal commands fixed the issue first time and took about 5 seconds!
Now my point here is, firstly: if I had followed the original advice from Apple I would have had to buy a new 1TB HD and then tracked down all the software installs of all my software - some of it custom and obscure (it took my years to get the mac exactly how I like it) and I doubt I would have gotten back 100%.
Secondly - why is there no-one at Apple that can help with Terminal commands? I was told this was for developers - I explained I was not a developer and that as it was a standard part of the Mac app software they should have someone at their "help" end who could deal with it.... two short lines of code, that's all it took!!
It was only after asking to complain that I got to someone who went the extra mile (yes, I love Apple and appreciate this but this only came by with me making a nuisance of myself).
So, at the end of the day, it was a forum member here who sorted out the issue in one hit.
My suggestion (which the Apple guy said he would bring up in his next meeting) is to have a separate subdivision of Apple help that is allowed to talk about Terminal - at the very least the could have guys like Dave Sneddon here on retainer and forward any Terminal issues to him directly - a win-win situation surely?
Secondly - the first guy I spoke to at Apple really didn't have a clue about this issue and gave me me 'bad' advice that would have cost me money and made my mac less perfect (to the way I had set it up).... he really insisted that this was the only way to sort it out.... he was wrong! - If I didn't force the issue this is what I would have been left with as the solution.
Either way the problem is sorted and I hope no-one else has to go through advice that would have taken hours and hours that was fixed in a few seconds through Terminal.
Dave - thanks again
1st Apple guy - fail!
2nd Apple guy - admirable effort and well appreciated
what are your thoughts?
Exact post:
Dear Apple, if I followed your advice I'd have ****** my computer and had to pay £100 - a forum member here fixed it in 5 seconds.
In a nutshell I had a trash warning glitch that I couldn't get rid of on a 9 day old gi7 imac that I had previously set up with all my info via Time Machine from my macbook pro. Calling Apple - they said that the only way to get rid of this was to perform a clean install making sure to back-up everything. I said that that was crazy and would involve me in having to invest in a new HD as I've already filled the imac with 500gb of stuff that has now been wiped over and I don't have a spare 500 gigs kicking around. I told them that I'm pretty sure a simple Terminal command would do the trick but they told me that they don't train their "help" to use it and that it was there for developers. I said that as it was their software which they installed then they should at least have people on the end of the phone that could help. After causing a fuss and wanting to make complaints I was passed to a senior guy who tracked down this exact problem on this forum and emailed me the link. We went through the terminal commands with no luck but I contacted the guy directly - Dave Sneddon, known as "dbsneddon" here. Two simple Terminal commands fixed the issue first time and took about 5 seconds!
Now my point here is, firstly: if I had followed the original advice from Apple I would have had to buy a new 1TB HD and then tracked down all the software installs of all my software - some of it custom and obscure (it took my years to get the mac exactly how I like it) and I doubt I would have gotten back 100%.
Secondly - why is there no-one at Apple that can help with Terminal commands? I was told this was for developers - I explained I was not a developer and that as it was a standard part of the Mac app software they should have someone at their "help" end who could deal with it.... two short lines of code, that's all it took!!
It was only after asking to complain that I got to someone who went the extra mile (yes, I love Apple and appreciate this but this only came by with me making a nuisance of myself).
So, at the end of the day, it was a forum member here who sorted out the issue in one hit.
My suggestion (which the Apple guy said he would bring up in his next meeting) is to have a separate subdivision of Apple help that is allowed to talk about Terminal - at the very least the could have guys like Dave Sneddon here on retainer and forward any Terminal issues to him directly - a win-win situation surely?
Secondly - the first guy I spoke to at Apple really didn't have a clue about this issue and gave me me 'bad' advice that would have cost me money and made my mac less perfect (to the way I had set it up).... he really insisted that this was the only way to sort it out.... he was wrong! - If I didn't force the issue this is what I would have been left with as the solution.
Either way the problem is sorted and I hope no-one else has to go through advice that would have taken hours and hours that was fixed in a few seconds through Terminal.
Dave - thanks again
1st Apple guy - fail!
2nd Apple guy - admirable effort and well appreciated