Changes between Version 31 and Version 32 of TestingGuide


Ignore:
Timestamp:
Feb 12, 2012, 6:38:10 PM (13 years ago)
Author:
David Azarewicz
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TestingGuide

    v31 v32  
    3030     a) If it stops when the desktop starts (Snap logo or blue screen), your problem is probably not with the PSD. Make sure you have the updated keyboard driver (10.163 or later), doscall1.dll (10-Nov-2011 or later), etc. If you have a multi-core system you can also try the /MAXCPU=1 switch.
    3131
    32      b) If it stops after the chkdsks run but before the desktop starts, probably one of the drivers is having trouble initializing. Use ALT-F4 to load the drivers one at a time and see which one is failing.
     32     b) If it stops after the chkdsks run but before the desktop starts, probably one of the drivers is having trouble initializing. Use ALT-F2 or ALT-F4 to load the drivers one at a time and see which one is failing.
    3333
    3434     c) Otherwise, go to step 2
    … …  
    4343     a) If it stops when the desktop starts (Snap logo or blue screen), your problem is probably not with the PSD. Make sure you have the updated keyboard driver (10.163 or later), doscall1.dll (10-Nov-2011 or later), etc. If you have a multi-core system you can also try the /MAXCPU=1 switch.
    4444
    45      b) If it stops after the chkdsks run but before the desktop starts, probably one of the drivers is having trouble initializing. Use ALT-F4 to load the drivers one at a time and see which one is failing.
     45     b) If it stops after the chkdsks run but before the desktop starts, probably one of the drivers is having trouble initializing. Use ALT-F2 or ALT-F4 to load the drivers one at a time and see which one is failing.
    4646
    4747     c) Otherwise, go to step 3