PVR150 Timestamp issue - new drivers.

[gazoo]

Ok, I went to do the regedit but I don't have HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
instead I have HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet001\ and
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet002\

which one do I modify?

[sub]

I've never seen a machine that doesnt have this registry key. Sorry, I dont know.

[jksmurf]

Ok, I went to do the regedit but I don't have HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
instead I have HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet001\ and
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet002\

which one do I modify?

Perhaps you can download the reg from here

http://gbpvr.com/pmwiki/pmwiki.php/Tips/...Issue#toc4

or just add it manually and see what happens....

k.

[zehd]

Ok, I went to do the regedit but I don't have HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
instead I have HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet001\ and
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet002\

which one do I modify?

A lot of times when someone reinstalls windows in place ther will be alternate special folders created, like user.admin and user etc in the documents and settings folder

Anyway, maybe the main currentcontrolset gets renamed or new numbering when there's a reinstall. I've never seen it either, so I'm just guessing

[gazoo]

Reporting back-

I had two registry settings (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet001\ and
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet002\) instead of just the one like everyone else. I added the new dword to each and it seems to have done the trick. I've recorded about 20-30 programs since then and have not had the timestamp issue.

[wrocky]

I recently upgraded (downgraded/crossgraded), from a machine running Server 2003 to a faster box running Vista home, as my primary recording machine, and am now having the timestamp issue. (Signature block not updated yet)

I am a little confused after reading some of the postings, as there are only a few people who specify their O/S, and I'm wondering if the "fix" is the same for Vista as it is for XP. I'm using the out of box drivers that came with Vista for my 2 PVR-150 cards.

Is it now just a matter of applying the registry change, or does Vista require all the Hauppauge software, and/or the registry change to fix the timestamp?

[zehd]

I recently upgraded (downgraded/crossgraded), from a machine running Server 2003 to a faster box running Vista home, as my primary recording machine, and am now having the timestamp issue. (Signature block not updated yet)

I am a little confused after reading some of the postings, as there are only a few people who specify their O/S, and I'm wondering if the "fix" is the same for Vista as it is for XP. I'm using the out of box drivers that came with Vista for my 2 PVR-150 cards.

Is it now just a matter of applying the registry change, or does Vista require all the Hauppauge software, and/or the registry change to fix the timestamp?

Try the reg fix. If it works great, if it doesn't you haven't hurt anything

[GoodGuys]

I've never seen a machine that doesnt have this registry key. Sorry, I dont know.

Well, just to let you know - I've recently installed from scratch, and also got the same condition - I had the ..001 and ..002 keys.

Still, I've imported the .reg file without a problem, and it seems like there is no problem on my machine. Of course I could be wrong and just haven't noticed a problem yet.

GGF

[Reddwarf]

I'v installed the new drivers four days ago and have not seen any timestamp problem since then, was a huge problem earlier and I could not figure out what cauced it before I found this thread. Seems good so far.

[DarthBarb]

hello,
I am new to regedit and retime, etc, so I am a little befuddled on how to work with them. I understand that I need to make a new key for driverdata, but in vista I am given columns and have to enter a d word, etc. I am confused. Also, what is the best driver for a pvr 150 that can fix the timestamp issue? Which one works the best?
thanks for your help
darthbarb