or Connect
AVS › AVS Forum › Video Components › Home Theater Computers › MyHD120 timed recording problems
New Posts  All Forums:Forum Nav:

MyHD120 timed recording problems  

post #1 of 19
Thread Starter 
I have 2 problems regarding the MyHD120 card and a timer recording.

When I set the MyHD to record something and put the computer into hibernation one of two things happen;
1. Either I get a siren like 2 tone beeping and the system stops with a post code of 25 (the board has a display that shows the posts codes). It is Award V6 w/ the latest bios.
2. Or it just doesn't wake up at all.

If I leave the computer on it will record the program, but if I put it in hibernation the above happens.
This wasn't like this at the start. It seems to of gotten worse (problem happening more often). I does work once in a while, but that is rare.
The only hardware change was a newer printer (both HP) but it was doing this before I changed the printer.
I have removed the audio card and NIC, but with the same results. I have removed one of the memory sticks and moved it to another slot with the same results.

My questions are:

1. Just how does this program send a command to the MB to wake the system up and where is it stored since the HDD isn't in the picture yet?
2. Just what is the difference between manually starting the system from hibernation (by pushing a button) and the program doing it?

I do have a idea that there might be a issue with 2 HDD's both w/ the same O/S sending commands to the MB (not at the same time mind you).
The idea with the 2 HDD's is if one goes down I have a backup to start the system via a front panel toggle switch. I have been doing this for years with little problems. I believe the 2nd problem not even starting up was after I loaded the program on the 2nd drive (it hasn't seen the card up to this point) and tried troubleshooting from that drive instead of messing up the main drive.
BTW, I have contacted Epox and they think the 25 might be the video card. Post code 25 is shown as "reserved" at Awards site. I will look into hibernation at M$'s site though I dread trying to search for anything over there.

Before someone says to 'reload the O/S, if that is done what does that have to do with the code 25 that is long before the O/S is in the picture? Remember I can start the system out of hibernation manually with rarely a problem, it is only when it is done through the MyHD software that there is a problem.

Specs:

Win 2k w/sp4
Epox 8-RDA MB w/nForce2 chipset MB (bios 2/04)
Athlon 2100b
2 256MB PC2700 Corsair memory sticks
V 1.63 software for the MyHD 120 card w/daughterboard
Powercolor ATI 9600Pro video (3/04 drivers)
Antec True Power 330W PS
SB Live Value audio (w/ KX Project driver package)
3M NIC

NO overclocking!

Thanks in advanced
post #2 of 19
Thread Starter 
I spent a hour searching and looking at a couple of KB articles, but nothing applies.

What I have done in addition to what I have already posted:

removed the NIC and SB Live cards,
reloaded a 2k w/sp4 image to the backup bootable HDD,
loaded DX9,
loaded the driver for the video card,
loaded the s/w for the tuner card,
flashed the bios with the 11/03 version (had the 2/04) (Epox 8-RDA MB, Award V6),
reset the bios (jumper)
swapped video cards to a nVidia GeForce2 (removed orginal ATI drivers first),
disconnected the other HDD,
checked time and date,
checked temp's,

SAME THING................the MB is NOT being woke up when it goes into hibernation, let alone the code 25 deal.
The program DOES record if I let the computer stay on.

Now I think it might have something to do with the clock even though the time and date is correct.
I replaced the battery a month ago. The orginal battery showed 2.95v (which should of been more than enough) because the syatem was way off time wise and was getting worse. It seems ok now (keeps proper time).

What do you think of this since I am out of other ideas other than guessing heat or low voltage which I really don't think is the problem since I have look many times at these and never saw something of suspect.
The clock was picking up time over that last year or so. Maybe a few minutes a week. I would correct it, but it would still gain time. The MB was installed 2/03. A couple of weeks ago it started to loose time, something around 30 minutes A DAY! I reste it, but it was still way off. I checked that battery and it showed 2.95v which in no way should of caused a problem. I changed it to a new one reading 3.2v
Now it seems to be fine. It keeps correct time within seconds over a number of days. Might I have a problem in the clock circuit even though it is working correctly that could be affecting this?

Is there some utility to test hibernation that would issue a command to wake the system up (other than through a NIC) at a certain time to duplicate the funtion of the tuner card?
post #3 of 19
"Is there some utility to test hibernation that would issue a command to wake the system up (other than through a NIC) at a certain time to duplicate the funtion of the tuner card?"

Yes, MyHD uses the same API as Windows Task Scheduler to start the computer from sleep modes. Set up an event in WTS to wake the computer and you'll likely see the same problem you do with MyHD, because the problem doesn't sound at all like a software one.
post #4 of 19
Thread Starter 
Ok, sounds like a plan. I don't think it is a S/W problem either since it is doing the same thing, orI should say NOT doing the same thing on both drives.

Stupid question; since I have NEVER usewd Task Scheduler, it would wake the system up when it is in hibernation to do something or does it have to be on or in standby?
post #5 of 19
Thread Starter 
Ok, I tried Task Scheduler and it seems to work (most of the time). No code 25 and it does start the box ok. A coup[le of times it started the system, but not the program. I don't know if it was user error or something with the program. I tried another program and it sems to run ok.

I don't see a way to shut down the system (not just the program). Is there?

Anyway, now what? That seems to take the blame away from the MB, but since I have no idea how this differs from starting the system and MyHD starting it I don't know where to look next.
post #6 of 19
Quote:
Originally posted by videobruce
...Task Scheduler...seems to work (most of the time). No code 25 and it does start the box ok. A coup[le of times it started the system, but not the program. I don't know if it was user error or something with the program. I tried another program and it sems to run ok.
I actually meant that you'd set up WTS to start, say, calculator.exe--not MyHD--so as to eliminate MyHD from the equation. What does "most of the time" mean? WTS should either work or not. If it fails sporatically that alone would indicate some system problem, IMO.
Quote:
I don't see a way to shut down the system (not just the program). Is there?
Google "suspend.exe" and you'll find at least one way.
Quote:
Anyway, now what? That seems to take the blame away from the MB, but since I have no idea how this differs from starting the system and MyHD starting it I don't know where to look next.
If WTS reliably starts calculator.exe on your system and MyHD hangs only upon scheduled capture startups, my next guess would be that there is a startup power-draw surge causing voltage sag or some such problem. What else is waking at the same time? Are all components drawing from the same household branch circuit??
post #7 of 19
Here is a suspend test utility that uses the same API as MyHD and also allows you to run any application from the command line.

 

suspendtest.zip 5.9697265625k . file
post #8 of 19
Thread Starter 
Quote:
I actually meant that you'd set up WTS to start, say, calculator.exe--not MyHD--so as to eliminate MyHD from the equation. What does "most of the time" mean? WTS should either work or not. If it fails sporatically that alone would indicate some system problem, IMO.
I was using DU Meter, then USDM (Unified System Diagnostic Manager) from Epox. It was DU Meter that didn't seem to start. It might just be that program. I will try a couple of more times with that and USDM (both are small programs which is why I picked them). USDM did start everytime.

Quote:
If WTS reliably starts calculator.exe on your system and MyHD hangs only upon scheduled capture startups, my next guess would be that there is a startup power-draw surge causing voltage sag or some such problem. What else is waking at the same time? Are all components drawing from the same household branch circuit??
When you ay what else is waking at the same time, do you mean something other than the computer or what is inside? I'm confused about a "power draw surge" since everything inside the box powers up at the same time no matter how it starts, right?

Cliff, thanks for the utility.
post #9 of 19
Quote:
Originally posted by videobruce
When you ay what else is waking at the same time, do you mean something other than the computer or what is inside? I'm confused about a "power draw surge" since everything inside the box powers up at the same time no matter how it starts, right?
Yes, I meant outside of the computer. I was allowing for the possibility that you were somehow powering up a monitor/projector/whatever when the computer waked.

Does the machine wake (with or without MyHD) as expected using Cliff's utility or does it give the BIOS error?
post #10 of 19
Thread Starter 
Only the computer powers up. No load problem.

NOW for the fun (if I haven't already had my share):

Great little utility, works as intended. put it in hibernation, woke it up with the program running. Wow, all is fine,

EXCEPT, MyHD STILL doesn't work!

What I did was; first just ran that utility with that check box unchecked, set the timer, put it in hibernation, the box powered up and MyHD was running when the desktop showed which I was surprised since that check box wasn't checked!
Next I changed the command line to DU Meter, and that worked fine, then to USDM and that worked fine!
I went back to MyHD and tried that by itself after I ran the utility once with MyHD as the command line and MyHD did work and recorded.
I tried it again, but back to square one, nothing! No idea why it worked only once.
I tried it a few more times checking the settings, but nothing.
I uninstalled MyHD, looked for left over registry entries, and reinstalled V 1.63 again, but still nothing. I did run the utiltiy once, then MyHD to see if thast would do it as it appeared to do once before, but still nothing.

The suspend utility works fine and the system doesn't bark either. Only once it didn't but that time I forgot to click 'set timer' before I checked 'hibernate'.

OK, now what?????
post #11 of 19
Does any of this happen when you install version 1.61 MyHD software?
post #12 of 19
Thread Starter 
Don't know, it DID work with 1.63 orginally.
The older versions had problems with nForce2 chipsets as they never tested the s/w with them.
post #13 of 19
Quote:
Originally posted by videobruce
Don't know, it DID work with 1.63 orginally.
Oh. Well then, the solution is simple: put it back the way it was when it worked. :D

Seriously, you need to systematically eliminate all sw and hw changes from that working state to find which change you made broke it. And since you're seeing things work "once" or "some of the time", I'd suspect a hw "change"--such as a flakey connector somewhere.
post #14 of 19
Thread Starter 
1.63 is what is there now!
post #15 of 19
But that's the constant. You need to identify the variables. ;)
post #16 of 19
Thread Starter 
The varibles are; the test program works, the actual program doesn't! According to Cliff it uses the same command(s) as MyHD.

The way I understand this; MyHD sends (or is suppose to send) a command to the bios to wake the system up, buit apparently isn't. When it did something was wrong and it causes a code 25 at boot.
post #17 of 19
The MyHD v1.63 application is doing the same thing that it did when you say it was working before. Something outside of the MyHD application changed on your computer. That's the "variable" that you need to be looking for.

If the MyHD application were the variable, you would have fixed the problem by reinstalling it.
post #18 of 19
Thread Starter 
If something in the app was corupted it would. Happens all the time.

You lost me when you said: "The MyHD v1.63 application is doing the same thing that it did when you say it was working before."
post #19 of 19
Thread Starter 
I tried that utility on my other box with the card installed and the box doesn't wake up at all! It will only if I press the power button!
Now I can't even test the card since hibernation doesn't work here. It is a Epox 8-KTA w/ a 6/02 bios (last one).
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Home Theater Computers
This thread is locked  
AVS › AVS Forum › Video Components › Home Theater Computers › MyHD120 timed recording problems