- Blaster patch
- Posted by Scott Harding - MS MVP on August 18th, 2003
where does it stop? What is the error?
--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server
scrockel@***No_SPAM***hotmail.com
"Carl Gross" <cfgross@scapca.org> wrote in message
news:012a01c365a3$99b5a9c0$a301280a@phx.gbl...
- Posted by Scott Harding - MS MVP on August 18th, 2003
Not sure why this happened but it could be related to reapplying the Service
Pack after the hotfix. This may have replaced the very file you just
installed. Typically you ONLY need to reapply the Service Pack if you add
something from your original NT cd. There really shouldn't be any other
reason to reapply the service pack as many of the updates are going to be
for files that are currently in the service packs and reapplying the SP
could replace the file and cause mismatched files.
--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server
scrockel@***No_SPAM***hotmail.com
"Carl Gross" <cfgross@scapca.org> wrote in message
news:01c301c365c1$5a3a2780$a601280a@phx.gbl...
- Posted by Ricardo M. Urbano - W2K/NT4 MVP on August 18th, 2003
Exactly, the Blaster hotfix (any future hotfixes for that matter) is
specifically a post-SP6a hotfix, which means it replaces a file or files
in SP6a and *should* be installed after installing SP6a. In fact, if
you do reinstall SP6a, I would reinstall all my post-SP6a hotfixes.
Anyway, that having been said, I actually don't think the problem was
related to reinstalling the sp after the hotfix. I have a hunch it was
just reinstalling the sp period. Your boot volume wouldn't happen to
run outside the 7.8GB boot volume limit, would it?
Scott Harding - MS MVP wrote:
--
Ricardo M. Urbano
Microsoft Windows 2000/NT MVP
- Posted by Carl Gross on August 19th, 2003
The boot disk is separated into two partitions: a 4GB and
a 4.5GB partition. the 4GB partition is the boot
partition.
- Posted by Ricardo M. Urbano - W2K/NT4 MVP on August 19th, 2003
In Disk Administrator, is the 4GB partition the 1st partition on the
drive? If NOT, that could explain what happened. If it is, it probably
was a result of reapplying Sp6a after the hotfix. Regardless, you are
definitely not supposed to reapply sp6a after a post sp6a hotfix. If
you've gotten away w/ it up until now, you've been lucky.
Carl Gross wrote:
--
Ricardo M. Urbano
Microsoft Windows 2000/NT MVP
