Worth a shot...
http://support.microsoft.com/default.aspx?scid=kb;en-us;812415
SYMPTOMS
If your Windows 2000-based or Windows XP-based computer with multiple ATA
drives enters the S1 power state, you may experience one of the following
symptoms:
Windows does not recognize the ATA drives when you resume your computer from
sleep or standby.
You may receive the following error message:
* Unsafe Removal of Device:
* You have unplugged or ejected a device without stopping it. Unplugging or
ejecting devices without first stopping them can frequently cause your
computer to crash and loose valuable data.
* Windows may stop responding (hang).
----------------------------------------------------------------
CAUSE
This problem occurs partly because the IDE storage driver stack incorrectly
accesses registers that are required for a software reset. This leaves the
host controller or device in a hung state. This problem does not affect
computers that are using ATA Host controllers that are configured for Legacy
mode operation. Although this issue has been identified on the Intel
ICH5-based chip set, it is not limited to this hardware.
-------------------------------------------------------------
RESOLUTION
Windows XP
Hotfix Information
The following files are available for download from the Microsoft Download
Center:
-Windows XPDownload the 812415 package now.
http://microsoft.com/downloads/deta...8D0-4110-A7DF-8955A47BA8F5&displaylang=en
===========================================
HTH
Don
===========================================
| Well at least the Soundmax problem seems to be resolved. Here's my take on
| what was happening...This screen asking what was plugged into the line out
| (green) jack keeps popping up every time the system boots even after
telling
| it, so I check the "don't ask again" check box. Doing so apparently
| "unchecks" one of the boxes under preferences called "Enable AudioESP" and
| this was the problem. With this box unchecked my system refuses to go into
| standby by itself (timed standby). I thought checking this box again would
| cause the "what's plugged...." screen to start popping up again but it
| doesn't and once checked the system goes into standby by itself without
any
| problems.
|
| The keyboard wakeup issue seems to stem from the fact that in previous
Asus
| BIOSs the APM keyboard power on settings not only determined the behavior
| when powering on the system but also when waking from standby. Now it
seems
| that it only determines behavior when powering on. I checked an Asus CUSL2
| system and under keyboard properties in device manager (XP Home) there is
no
| power management tab. With the P4C800-E system (XP Prof) there is a power
| management tab with the usual "Allow this device to bring the computer out
| of standby" check box and the setting here determines the keyboard standby
| behavior. Perhaps I'm missing something but both XP Home and XP Prof are
| using the same keyboard driver/inf files so I doubt whether this is a
| difference between the two.
|
| | > Just installed one of these boards and encountered the following;
| >
| > 1. Soundmax application software prevents system from going into suspend
| > mode (S3) by itself (timed standby)
| > 2. Any keyboard key wakes the system even if keyboard wakeup is disabled
| in
| > the BIOS. Wanted just spacebar to wake system as it should when set that
| way
| > in the BIOS..
| >
| > Using latest BIOS (1014) and drivers. The culprit in 1 above was the
file
| > SMax4PNP.exe that is loaded at XP startup. My solution was to install
just
| > the drivers and forget about the software which includes that file. I'll
| > probably just disable the onboard audio and get a Soundblaster card
since
| > Creative's software is way better with equalizer, reverb, lots more and
no
| > standby problems with my other Asus boards.
| >
| > Anybody else had similar experiences? Haven't tried Firewire yet but
other
| > than the above, so far so good.
| >
| >
|
|
