Scott Harding - MS MVP said:
Well this could have been totally unrelated to the updates. I have 17
servers completely patched and even more client machines up to date without
any issues. This issue could have been just waiting for a reboot and did not
rear it's ugly head until you rebooted. Stop 7b typically has to do with
drivers for your controller or something to do with the MBR of the drive or
a non standard atapi.sys file, like from a ZIP drive or other external drive
on the system that has taken over the MS atapi.
No Zipdrive or external devices.
Is this machine running on
standard IDE drives? SCSI? something else?
Yes, only IDE devices.
Is this machine covered in
applications? This is really the nature of the beast as MS can never cover
all the problems and conflicts that could arise from other products on the
thier OS's.
I was installing from scratch, but I did have Norton firewall and antivirus
running (is it adviseable at all to update through the internet without
firewall/antivirus???). It seems these progs. had made tasks which live
their own lives. After eliminating these, I could finish the MS security
updates succesfully, but only one by one.
Yes I agree that it sucks and I feel for you but how can this
ever go away? If you were completely running MS only products and apps then
this may be more consistent but this is a tough one. Did you install
everything correctly?
Indeed I did
) But nowadays, on top of that, one has a full-time job
updating, correcting and figuring out work-arounds for all sorts of software
errors.
You should be stopping any unnecessary services,
disabling Anti Virus software, and any other apps that may have been
running. That in itself can save you the head aches that you went through.
Just my $0.02 on the whole update scenario from experience....
Thanks your reply,
--
regards,
|\ /|
| \/ |@rk
\../
\/os
