Joined
·
16,966 Posts
I really don't know where to begin.
I still can not resolve this issue of waking the system back out of hibernation without using another application other than MyIRC to do a timed recording.
I can not get MyHD to 'wake' the system back up.
If I use a 'helper' application (Suspend Test), that will wake the system up without issue. Once woke, it will record ok. Digital Connection tells me the command(s) are thru the MyIRC using some kind of TCP/IP protocol. The MB manufacture blames the problem on the software/hardware. DG blames me for incorrect settings in the bios.
If I could get a exact understanding just what/where the command is sent before the system goes into hibernation I might be able to narrow it down somewhat. I have gone through the bios more than I can remember and surely more than I have in the last 6 years with all the other systems I have worked on.
What I have done:
Loaded fail safe AND optimized defaults
Checked PS voltages
Reloaded the O/S more than once
Updated the bios
Tried XP Pro (I'm using 2k w/sp4)
Changed MB's (both with the nForce 2 chipset)
Changed s/w versions from 1.63 to 1.65
Virus checks
Started as many Windows services I could find even though most I have never used.
Enabled as much in the bios as I could see that might have something to do with this.
The only thing I haven't done is change the memory and processor, but that would have to be the longest of longshots I could imagine. I have asked this in other forums and the stock answer is; hibernation has problems with many devices.
BTW, this did work for the first 2 months..........
First board: Epox 8-RDA
current board: Abit NF7-S v2
I still can not resolve this issue of waking the system back out of hibernation without using another application other than MyIRC to do a timed recording.
I can not get MyHD to 'wake' the system back up.
If I use a 'helper' application (Suspend Test), that will wake the system up without issue. Once woke, it will record ok. Digital Connection tells me the command(s) are thru the MyIRC using some kind of TCP/IP protocol. The MB manufacture blames the problem on the software/hardware. DG blames me for incorrect settings in the bios.
If I could get a exact understanding just what/where the command is sent before the system goes into hibernation I might be able to narrow it down somewhat. I have gone through the bios more than I can remember and surely more than I have in the last 6 years with all the other systems I have worked on.
What I have done:
Loaded fail safe AND optimized defaults
Checked PS voltages
Reloaded the O/S more than once
Updated the bios
Tried XP Pro (I'm using 2k w/sp4)
Changed MB's (both with the nForce 2 chipset)
Changed s/w versions from 1.63 to 1.65
Virus checks
Started as many Windows services I could find even though most I have never used.
Enabled as much in the bios as I could see that might have something to do with this.
The only thing I haven't done is change the memory and processor, but that would have to be the longest of longshots I could imagine. I have asked this in other forums and the stock answer is; hibernation has problems with many devices.
BTW, this did work for the first 2 months..........
First board: Epox 8-RDA
current board: Abit NF7-S v2