Latest iPod update fucked up my iPod, of course.
Jamie Kahn Genet
option was to unlug it which lead to a forced restore.
God I want to fucking hurt someone at Apple nowadays.
--
If you're not part of the solution, you're part of the precipitate.
Jamie Kahn Genet
> The latest iPod update naturally failed for my iPod classic. The only
> option was to unlug it which lead to a forced restore.
>
> God I want to fucking hurt someone at Apple nowadays.
Oh, and my iPod was not showing in the Finder or iTunes which is why I
had to unplug it.
Gregory Weston
jam...@wizardling.geek.nz (Jamie Kahn Genet) wrote:
> The latest iPod update naturally failed for my iPod classic. The only
> option was to unlug it which lead to a forced restore.
>
> God I want to fucking hurt someone at Apple nowadays.
You should find out why they're targeting you.
--
"Harry?" Ron's voice was a mere whisper. "Do you smell something ... burning?"
- Harry Potter and the Odor of the Phoenix
Jamie Kahn Genet
> In article <1ikl4uc.u5bptrcdh936N%jam...@wizardling.geek.nz>,
> jam...@wizardling.geek.nz (Jamie Kahn Genet) wrote:
>
> > The latest iPod update naturally failed for my iPod classic. The only
> > option was to unlug it which lead to a forced restore.
> >
> > God I want to fucking hurt someone at Apple nowadays.
>
> You should find out why they're targeting you.
I should find out why they do no fucking testing.
George Kerby
On 7/24/08 7:51 AM, in article
uce-D400D8.0...@newsclstr02.news.prodigy.com, "Gregory Weston"
<u...@splook.com> wrote:
> In article <1ikl4uc.u5bptrcdh936N%jam...@wizardling.geek.nz>,
> jam...@wizardling.geek.nz (Jamie Kahn Genet) wrote:
>
>> The latest iPod update naturally failed for my iPod classic. The only
>> option was to unlug it which lead to a forced restore.
>>
>> God I want to fucking hurt someone at Apple nowadays.
>
> You should find out why they're targeting you.
He's part of the precipitate, that's why! <G!>
Gregory Weston
jam...@wizardling.geek.nz (Jamie Kahn Genet) wrote:
> Gregory Weston <u...@splook.com> wrote:
>
> > In article <1ikl4uc.u5bptrcdh936N%jam...@wizardling.geek.nz>,
> > jam...@wizardling.geek.nz (Jamie Kahn Genet) wrote:
> >
> > > The latest iPod update naturally failed for my iPod classic. The only
> > > option was to unlug it which lead to a forced restore.
> > >
> > > God I want to fucking hurt someone at Apple nowadays.
> >
> > You should find out why they're targeting you.
>
> I should find out why they do no fucking testing.
They do tons of testing. Everyone experiences obscure problems from time
to time - because no matter how much testing a vendor does they can't
test on literally every deployed machine in the world, which means they
can't test every scenario - but you seem to experience every conceivable
problem with your machines, as well as a few that *aren't* conceivable.
Either you're cursed, there's some habit or practice you follow that
routinely destabilizes your machines, or you're being specifically
victimized.
Jamie Kahn Genet
> In article <1ikm161.1ds3bw7jdv5x7N%jam...@wizardling.geek.nz>,
> jam...@wizardling.geek.nz (Jamie Kahn Genet) wrote:
>
> > Gregory Weston <u...@splook.com> wrote:
> >
> > > In article <1ikl4uc.u5bptrcdh936N%jam...@wizardling.geek.nz>,
> > > jam...@wizardling.geek.nz (Jamie Kahn Genet) wrote:
> > >
> > > > The latest iPod update naturally failed for my iPod classic. The only
> > > > option was to unlug it which lead to a forced restore.
> > > >
> > > > God I want to fucking hurt someone at Apple nowadays.
> > >
> > > You should find out why they're targeting you.
> >
> > I should find out why they do no fucking testing.
>
> They do tons of testing. Everyone experiences obscure problems from time
> to time - because no matter how much testing a vendor does they can't
> test on literally every deployed machine in the world, which means they
> can't test every scenario - but you seem to experience every conceivable
> problem with your machines, as well as a few that *aren't* conceivable.
>
> Either you're cursed, there's some habit or practice you follow that
> routinely destabilizes your machines, or you're being specifically
> victimized.
How do you explain that the majority of the annoying issues I experience
showed up within 48 hours of getting my second (the first was declared
DOA due to more serious issues) replacement late 2007 iMac and then
showed up within hours of multiple clean installs and then showed up
AGAIN on my third iMac (with yet another clean install)?
No, that's not bad luck. That's Apple doing SFA testing.
FYI - nine months later I still have to overwrite certain files twice
due to permissions errors the first time, I still get the Dock
reappearing during fullscreen playback of video in QT, I still have
Expose's and the Dashboard views disappearing immediately after
activation, requiring me to tap the Expose/Dashboard key a second time,
I still suffer graphical corruption of the Dock even running popular
games like WoW, etc, effing etc.
Many of these issues also show up on other Macs I use, even those
without any third party software.
Gregory Weston
Best guess? Some action that you're taking which you consider to be a
basic element of turning "a" machine into "your" machine.
> No, that's not bad luck. That's Apple doing SFA testing.
The question remains: why you? I look at your recent posting history and
I see, as I described above, that you seem to be having far worse luck
than anyone I've heard of in the quarter century I've been in this
industry. You. No other Apple customer has had this overwhelming
combination of experiences.
> FYI - nine months later I still have to overwrite certain files twice
> due to permissions errors the first time, I still get the Dock
> reappearing during fullscreen playback of video in QT, I still have
> Expose's and the Dashboard views disappearing immediately after
> activation, requiring me to tap the Expose/Dashboard key a second time,
> I still suffer graphical corruption of the Dock even running popular
> games like WoW, etc, effing etc.
>
> Many of these issues also show up on other Macs I use, even those
> without any third party software.
FWIW, as I understand it, WoW is known to corrupt the dock UI.
Everything else that you've described is an aberration. The question is
why this one person seems to experience every possible aberration.
You experience more problems than anyone else and you experience them on
multiple machines. How do you arrive at the conclusion that *you* are
not - in some way - an element of those problems?
Tom Stiller
Why don't you do us all a favor and sign up to do quality control
testing for Apple?
--
Tom Stiller
PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3 7BDA 71ED 6496 99C0 C7CF
Jamie Kahn Genet
You mock me, but you don't think I wish I could? AppleCare has utterly
failed me in getting my issues solved.
Jamie Kahn Genet
> In article <1ikmbcc.199ku111hzqrlvN%jam...@wizardling.geek.nz>,
> jam...@wizardling.geek.nz (Jamie Kahn Genet) wrote:
>
> > Gregory Weston <u...@splook.com> wrote:
> >
> > > In article <1ikm161.1ds3bw7jdv5x7N%jam...@wizardling.geek.nz>,
> > > jam...@wizardling.geek.nz (Jamie Kahn Genet) wrote:
> > >
> > > > Gregory Weston <u...@splook.com> wrote:
> > > >
> > > > > In article <1ikl4uc.u5bptrcdh936N%jam...@wizardling.geek.nz>,
> > > > > jam...@wizardling.geek.nz (Jamie Kahn Genet) wrote:
> > > > >
> > > > > > The latest iPod update naturally failed for my iPod classic. The
> > > > > > only option was to unplug it which lead to a forced restore.
> > > > > >
> > > > > > God I want to fucking hurt someone at Apple nowadays.
> > > > >
> > > > > You should find out why they're targeting you.
> > > >
> > > > I should find out why they do no fucking testing.
> > >
> > > They do tons of testing. Everyone experiences obscure problems from time
> > > to time - because no matter how much testing a vendor does they can't
> > > test on literally every deployed machine in the world, which means they
> > > can't test every scenario - but you seem to experience every conceivable
> > > problem with your machines, as well as a few that *aren't* conceivable.
> > >
> > > Either you're cursed, there's some habit or practice you follow that
> > > routinely destabilizes your machines, or you're being specifically
> > > victimized.
> >
> > How do you explain that the majority of the annoying issues I experience
> > showed up within 48 hours of getting my second (the first was declared
> > DOA due to more serious issues) replacement late 2007 iMac and then
> > showed up within hours of multiple clean installs and then showed up
> > AGAIN on my third iMac (with yet another clean install)?
>
> Best guess? Some action that you're taking which you consider to be a
> basic element of turning "a" machine into "your" machine.
Bullshit, pure and simple.
> > No, that's not bad luck. That's Apple doing SFA testing.
>
> The question remains: why you? I look at your recent posting history and
> I see, as I described above, that you seem to be having far worse luck
> than anyone I've heard of in the quarter century I've been in this
> industry. You. No other Apple customer has had this overwhelming
> combination of experiences.
No offence, but that shows a remarkable ignorance if you think I've had
the worst experiences ever with Apple.
> > FYI - nine months later I still have to overwrite certain files twice
> > due to permissions errors the first time, I still get the Dock
> > reappearing during fullscreen playback of video in QT, I still have
> > Expose's and the Dashboard views disappearing immediately after
> > activation, requiring me to tap the Expose/Dashboard key a second time,
> > I still suffer graphical corruption of the Dock even running popular
> > games like WoW, etc, effing etc.
> >
> > Many of these issues also show up on other Macs I use, even those
> > without any third party software.
>
> FWIW, as I understand it, WoW is known to corrupt the dock UI.
> Everything else that you've described is an aberration. The question is
> why this one person seems to experience every possible aberration.
It's not just WoW. Even Apple's DVD Player app did it once. But mostly
it's games. NOT just WoW by any means.
> You experience more problems than anyone else and you experience them on
> multiple machines. How do you arrive at the conclusion that *you* are
> not - in some way - an element of those problems?
Care to explain how suddenly after years of relatively trouble-free use
of System 6, 7 (well... maybe not System 7, at least till 7.6 anyway -
but that was far from just my experience), 8.6 (best classic MacOS ever
IMHO), 10.3 and 10.4 I suddenly develop a special 'fuck Apple Technology
field'? Care to explain how my first late 2007 iMac crashed right after
having it's HD zeroed and a clean install of Leopard (right after the
intro movie played)? Care to explain how it exhibited extremely unstable
behaviour right out of the box without any configuration or third party
software installed (which lead after many hours troubleshooting to the
last ditch zeroing and clean install)? Care to explain how my second
iMac showed less serious issues right after Leopard was installed over
Tiger? Care to explain how my third replacement iMac showed some of the
issues still present today right after Leopard was installed over the
copy already there (so much time had gone by that the Macs were finally
being shipped with Leopard pre-installed, but I was taking no chances
and re-installed it anyway)? I also used different Leopard install discs
each time just in case you're suspecting that. I also have an expensive
Belkin surge protector (the one with the unlimited warranty) isolating
my iMac from the mains and LAN. Every physical connection be it power or
ethernet goes through that surge protector. I also swapped out surge
protectors in case it was at fault. Likewise with all peripherals.
So I call bullshit on your assertion that it's my fault.
Regards,
Jamie Kahn Genet
P.S.As I type this the WindowServer is maxing one CPU core. Joy. I'd
love to know how the fuck I caused that.
Gregory Weston
jam...@wizardling.geek.nz (Jamie Kahn Genet) wrote:
> > > How do you explain that the majority of the annoying issues I experience
> > > showed up within 48 hours of getting my second (the first was declared
> > > DOA due to more serious issues) replacement late 2007 iMac and then
> > > showed up within hours of multiple clean installs and then showed up
> > > AGAIN on my third iMac (with yet another clean install)?
> >
> > Best guess? Some action that you're taking which you consider to be a
> > basic element of turning "a" machine into "your" machine.
>
> Bullshit, pure and simple.
And that's based on? Anything more than your conviction that it couldn't
possibly be you?
> > > No, that's not bad luck. That's Apple doing SFA testing.
> >
> > The question remains: why you? I look at your recent posting history and
> > I see, as I described above, that you seem to be having far worse luck
> > than anyone I've heard of in the quarter century I've been in this
> > industry. You. No other Apple customer has had this overwhelming
> > combination of experiences.
>
> No offence, but that shows a remarkable ignorance if you think I've had
> the worst experiences ever with Apple.
Fine. Identify someone who did, then.
> Care to explain how suddenly after years of relatively trouble-free use
> of System 6, 7 (well... maybe not System 7, at least till 7.6 anyway -
> but that was far from just my experience), 8.6 (best classic MacOS ever
> IMHO), 10.3 and 10.4 I suddenly develop a special 'fuck Apple Technology
> field'? [rantrantrant]
After you explain the inkjet printer that I mentioned to you during one
of your earlier problems. I'll refresh your memory: About 15 years ago,
I had a brand new inkjet printer that would reliably fail if my wife was
in the room when a print job started. Every time.
Today we realized that one of the Wii Remotes is unreliable when she
uses it. One. Fails for her. Not for me. Not for our daughter. And the
other one doesn't have a problem with any of us.
The same time I mentioned that printer to you, I also noted that
machines that have been consistently failing for hours have on multiple
occasions suddenly started working when I got near them. Not touched;
got near.
You explain to me how *those* consistently person-specific behaviors
occur and I'll have your answer about how your machines don't like you.
> So I call bullshit on your assertion that it's my fault.
Technically that was an implication.
G
Jolly Roger
Oh come on, now Jamie. Surely it's a possibility.
--
Send responses to the relevant news group rather than to me, as
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.
JR
Jamie Kahn Genet
Sure, but other than when anger at my situation clouds my judgement, I
do not see how it is logically possible. Besides - how does Gregory
account for the Macs running earlier OS's and PCs running Windows,
Linux, etc that I frequently use, with which I do not suffer the same
seemingly endless series of troubles?
My trouble began with this model Intel iMac and Leopard. I suspect it
will end there as well... one way or the other. Either Snow Leopard will
work out for me or I'll be moving to Linux, most likely. Or possibly one
of the BSD Unixes. That's assuming I hold out long enough with Leopard.
Jolly Roger
jam...@wizardling.geek.nz (Jamie Kahn Genet) wrote:
> Jolly Roger <jolly...@pobox.com> wrote:
>
> > In article <1ikn9f4.1cyjzf6ayx1ltN%jam...@wizardling.geek.nz>,
> > jam...@wizardling.geek.nz (Jamie Kahn Genet) wrote:
> >
> > > Gregory Weston <u...@splook.com> wrote:
> > >
> > > > In article <1ikmbcc.199ku111hzqrlvN%jam...@wizardling.geek.nz>,
> > > > jam...@wizardling.geek.nz (Jamie Kahn Genet) wrote:
> > > >
> > > > > Gregory Weston <u...@splook.com> wrote:
> > > > >
> > > > Best guess? Some action that you're taking which you consider to be a
> > > > basic element of turning "a" machine into "your" machine.
> > >
> > > Bullshit, pure and simple.
> >
> > Oh come on, now Jamie. Surely it's a possibility.
>
> Sure, but other than when anger at my situation clouds my judgement, I
> do not see how it is logically possible. Besides - how does Gregory
> account for the Macs running earlier OS's and PCs running Windows,
> Linux, etc that I frequently use, with which I do not suffer the same
> seemingly endless series of troubles?
Like Gregory said, it could be the result of some action that you're
taking which you consider to be a basic element of turning "a" Mac into
"your" Mac.
For instance, in another post, you mentioned log entries that show you
are running Input Managers. Input Managers, by their very nature, can
cause problems that affect multiple applications in similar ways, giving
the appearance of systemic causes. Certainly if one happened to run just
the right combination of things with just the right combination of
faulty interactions, one might be able to reproduce the problem
faithfully on *any* Mac. This is a definite possibility - even a
definite probability, IMO.
> My trouble began with this model Intel iMac and Leopard. I suspect it
> will end there as well... one way or the other. Either Snow Leopard will
> work out for me or I'll be moving to Linux, most likely. Or possibly one
> of the BSD Unixes. That's assuming I hold out long enough with Leopard.
I'm not sure what to say to you in response to that other than I'm sorry
to see anyone having as much trouble with a computer - especially a Mac.
And I'll be slightly saddened to see you go. With that said, I think
everyone should always do what makes them happy and less stressed!
bi...@mix.com
> For instance, in another post, you mentioned log entries that show you
> are running Input Managers.
Here's a good discussion of them -
http://daringfireball.net/2006/01/smart_crash_reports
It's a bit technical, but not so much that it can't be understood,
I believe, by anyone participating in this thread.
It was written in January, 2006, and mentions three applications
that silently install input managers. There are likely more now.
Not to mention those installed with the likely uninformed consent
of the user, which is pretty damn close to 'silent.'
| *Crux of this entire essay:* This behavior - the silent installation
| of a system extension that modifies all applications - is both wrong
| and dangerous.
> Input Managers, by their very nature, can cause problems that
> affect multiple applications in similar ways, giving the appearance
> of systemic causes.
| [...] every installed input manager loads into (nearly) every
| application.
Billy Y..
Jolly Roger
> Jolly Roger <jolly...@pobox.com> writes:
>
> > For instance, in another post, you mentioned log entries that show you
> > are running Input Managers.
>
> Here's a good discussion of them -
>
> http://daringfireball.net/2006/01/smart_crash_reports
And another:
<http://db.tidbits.com/article/08430>
Jamie Kahn Genet
> In article <g6d9c6$pen$1...@reader1.panix.com>, bi...@MIX.COM wrote:
>
> > Jolly Roger <jolly...@pobox.com> writes:
> >
> > > For instance, in another post, you mentioned log entries that show you
> > > are running Input Managers.
> >
> > Here's a good discussion of them -
> >
> > http://daringfireball.net/2006/01/smart_crash_reports
>
> And another:
>
> <http://db.tidbits.com/article/08430>
Heh, I've actually read both articles before. Sure, I don't Input
Managers being used for unintended purposes, but I DO like the results
and only use those that are widely used and considered stable. Besides,
I'm doubtful it is Input Managers causing my slowdown issues (disabling
them had no effect) - qutting BOINCManager seems to have restored speed.
I suspect CrashPlan and BOINC were fighting a turf war over resources,
but more testing is needed.
Regards,
Jamie Kahn Genet
Jeffrey Goldberg
> Either you're cursed, there's some habit or practice you follow that
> routinely destabilizes your machines, or you're being specifically
> victimized.
My theory is that JKG is the scape-user. All of the bad luck, bad
hardware, bad configurations and so on fall on him so that the rest of us
can enjoy reliable systems. It all balances out very nicely, except of
course for the scape-user.
-j
--
Jeffrey Goldberg http://www.goldmark.org/jeff/
I rarely read top-posted, over-quoting or HTML postings.
http://improve-usenet.org/
Jeffrey Goldberg
> You explain to me how *those* consistently person-specific behaviors
> occur and I'll have your answer about how your machines don't like you.
Someone once said that Unix is a friendly OS, but that it is picky about
who its friends are.
The number of threads that we've had over the years in which JKG described
a serious bug that nobody else could reproduce does make me wonder whether
he is doing something odd or whether there are strange things about his
operating environment.
I'm sure it is extremely frustrating to be in his shoes. But I've come to
expect that when he reports a problem there will be little that anyone
will be able to say that is remotely helpful or comforting. Not even a
"me, too".
Jamie Kahn Genet
> In <uce-EC7BCE.0...@newsclstr02.news.prodigy.com>, Gregory
> Weston...:
>
> > You explain to me how *those* consistently person-specific behaviors
> > occur and I'll have your answer about how your machines don't like you.
>
> Someone once said that Unix is a friendly OS, but that it is picky about
> who its friends are.
>
> The number of threads that we've had over the years in which JKG described
> a serious bug that nobody else could reproduce does make me wonder whether
> he is doing something odd or whether there are strange things about his
> operating environment.
>
> I'm sure it is extremely frustrating to be in his shoes. But I've come to
> expect that when he reports a problem there will be little that anyone
> will be able to say that is remotely helpful or comforting. Not even a
> "me, too".
>
> -j
Well actually I've had independant confirmation from others that the
Dock's graphics get corrupted by apps that change resolution or colour
depth (and sometimes less than that), and that the Dock reappears during
fullscreen video playback in QT Player. I've even had another rather
desperate sounding user email me asking me to advise if a solution is
ever found to the later problem. Plus there are many angry folk on
Apple's useless support forums (what a waste of time that is).
Jolly Roger
jam...@wizardling.geek.nz (Jamie Kahn Genet) wrote:
> there are many angry folk on
> Apple's useless support forums (what a waste of time that is).
I've found Apple's "support forums" are really just user forums whose
best value is confirmation that you're not alone. ; )