View Single Post
  #8  
Old June 4th 05, 05:06 PM
Kerry Brown
external usenet poster
 
Posts: n/a
Default

"Al Waschka" wrote in message
...
Oh,yeah....
Wouldn't the fact that loading from one partition "repairs" a load from a
different partition indicate that some driver or dll or whatever isn't
getting loaded into memory by the defective partition and survives a
restart
but not a cold boot? And this is not a random occurrence. I had exactly
the
same problem (symptoms-wise) a few months ago. It came back, exactly like
before, when I "upgraded" to SP2.


To find out what is causing the problem you have to eliminate the simple,
obvious things first. Booting into a working install of Windows may
initialise some hardware that is not happening on the other install with
SP2. If the installs were exactly the same except for SP2 then I would
suspect SP2. The installs are not exactly the same. You mentioned that some
time elapsed, printers were installed etc. Troubleshooting is a time
consuming process with few if any shortcuts. Test for the problem after each
change. Start with the simplest steps first. 1) Reset the CMOS. Test for the
problem. 2) disconnect the printer that had problems and remove it's drivers
Test for the problem. 3) download and install the latest drivers for all
your other hardware. Test for the problem, and so on and so on until it's
solved. It may very well end up that something, hardware or software, is not
compatible with SP2. Until you eliminate all the other possibilities you'll
never know.

Kerry



"Kerry Brown" wrote:

"Al Waschka" wrote in message
...
My defective SP2 installation is on Drive0
My working pre-SP2 installation is on Drive1
When 0 will not start, if I switch boot device in CMOS to 1, windows
comes
up, as expected.
If I then switch back to 0, IT WORKS!
But then, if I cycle power, i.e. shutdown followed by startup, it hangs
again.


That's nice, but it doesn't answer my question. :-) Did you reset the
CMOS
via the jumper on the motherboard after flashing the BIOS? Failure to do
this can sometimes cause erratic results like you are describing. This
may
not solve the problem but it eliminates one possible cause.

Kerry





Ads