Re: Apple advocates PAYING BIG BUCKS to run Windows on their Macs

In article <kto2u1d01apps0c1tgsgfs9kcbcddlbejo@xxxxxxx>, foo@xxxxxxx 
wrote:

> >> Sure it is.  It suggests that you should take it to your hardware
> >> vendor for support.  If you don't have one, you should find someone
> >> who does know how to troubleshoot (as apparently you couldn't or
> >> wouldn't) so they could help you.
> >
> >...since it can't be done by simply looking at the dumps, which you've 
> >suggested numerous times is the only course of action one needs to 
> >take in order to pinpoint the problem. This pretty much boils down to:
> 
> Correct to a point.  For hardware, bets are off.

Which pretty much makes your point with dumps pretty stupid.

> >foo: problems with any PC or Xp can be found with the dumps, send me 
> >the dumps
> >
> >sandman: sure, I'm having problems, here are the dumps.
> >
> >foo: uhm... ok... I guess you have a problem with your hardware, or 
> >possibly with your drivers
> >
> >sandman: no *shit* einstein? that was some mighty troubleshooting 
> >skillz you've got there!
> 
> Just the facts.

What *facts*, David? You said that it *probably* was the hardware and 
could be driver related. That pretty much encompasses any problem you 
CAN have with a PC. It's - as I said - like saying "You're having 
problems with your computer". Well, duh.

> Have someone else look at them if you like - I bet
> they'll say the same thing.  

Well, I'd probably talk to people with better troubleshooting skills 
than you :)

> >> If you wanted to troubleshoot more you should've said so; the thread
> >> died shortly after I posted that information and others chimed in
> >> about your lack of knowledge of dumps.
> >
> >What does my lack of knowledge of XP dumps have to do with anything?
> 
> You claimed no one used them;

Quote me.

> >> That's what I suggested.
> >
> >And a failure to pinpoint the problem. You've could just as easily 
> >have said "You've got a problem with your computer" :)
> 
> *I* am trying to be serious here.  

I've never been anything but.

> >> >> You can google for my suggestions; overall the suggestion was
> >> >> hardware, with a suggestion to return it to your vendor for hardware
> >> >> troubleshooting.  It wasn't blank; there was no smoking gun though.
> >> >
> >> >Plus, there was no vendor to return it to, since it is a homebuilt 
> >> >system.
> >> 
> >> Who's fault is that?
> >
> >Aha, so buying parts is now wrong?
> 
> If you can't troubleshoot them....  

So, the story is - "buying part PCs means you can buy dirt cheap PCs, 
but if you ever get a problem with them, you have yourself to blame 
for buying part PCs"

Great advocacy!

> >> If you can't troubleshoot yourself, buy from a vendor and get a
> >> warranty.
> >
> >...since troubleshooting is so hard that you have to actually send it 
> >in to the shop, as you have displayed with your lack of ability to 
> >pinpoint the problem? Sure.
> 
> You're the one with a) physical access to the hardware and b) the
> problem.  Since it's a hardware problem, what in the world would you
> expect me to do about it?

What you claimed you could - troubleshoot it by looking at the dumps.

> >> Glad you got it fixed.  It's a shame you had to stoop to being
> >> insulting; I stated it was probably hardware.
> >
> >You boosted about your troubleshooting skills and you failed. I called 
> >you on your hot air and you didn't live up to your hype.
> 
> Not at all.

here, have another cup of denial.

> >"It's probably hardware" is the exact opposite of troubleshooting. 
> >It's guessing on the biggest possible factor in a computer. It's like 
> >a car shop would say that "You probably got a problem with your 
> >engine". Well Duh!
> 
> You know nothing about how debuggers work, and you prove it with every
> post.  

Whenever you've got an actual argument that support you, feel free to 
share it.



-- 
Sandman[.net]

"As far as my decision to use the PC goes, that
 went according to my pocketbook"
   - Edwin, too poor to afford a Mac.
.

Relevant Pages

  • Re: Anthonys drive issues.Re: ssh password delay
    ... >> They're trying to help troubleshoot over the list. ... Not if the hardware is going bad or has a problem. ... Pull out that shit controller and set of drives, ...
    (freebsd-questions)
  • Re: boot sector f*ed
    ... allways best to try to break down the problem in tiny bits and solve them ... They can be caused by faulty hardware. ... The path variable was correct but the shell just ... I don't normally troubleshoot hardware that way (instead, ...
    (freebsd-questions)
  • Re: D Drive
    ... In BIOS, check that the DVD is installed as a UDMA device. ... Do not install similar programs that use the DVD drive - Roxio and Nero. ... > Windows cannot start this hardware device because its configuration ... > Click Troubleshoot to start the troubleshooter for this device. ...
    (microsoft.public.windowsxp.general)
  • Re: Apple advocates PAYING BIG BUCKS to run Windows on their Macs
    ... It suggests that you should take it to your hardware>> vendor for support. ... you should find someone>> who does know how to troubleshoot (as apparently you couldn't or ... >>...since it can't be done by simply looking at the dumps, which you've>suggested numerous times is the only course of action one needs to>take in order to pinpoint the problem. ... with a suggestion to return it to your vendor for hardware ...
    (comp.sys.mac.advocacy)
  • Re: OWA Issues- Follow up to 6/29 post- Need some help here!
    ... I think it is the hardware ... I have checked your metabase file and event ... I think the best way to troubleshoot this issue is to get netmon ... >> Microsoft Partner Support Professional ...
    (microsoft.public.windows.server.sbs)