Results 1 to 3 of 3

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Registered User
    Join Date: Apr:2004
    Posts: 29

    Hauppauge WinTV PVR150

    2-3 . WinTV2000 : WinTV inicialization Error. hTV=0. . . CD- , . Hauppauge, - 1-2 . . Hauppauge, ( ).

  2. #2
    Registered User
    Join Date: Jul:2001
    Location: Sofia
    Posts: 1,956
    Ne Sutor Supra Crepidam

  3. #3
    Registered User
    Join Date: Apr:2004
    Posts: 29

    !!!!

    !! !!! - )))
    , .
    : ASUS A7N8X- Deluxe M/B.
    , .
    10 core13 ))))
    -----------------------------
    My system :
    ASUS A7N8X Deluxe M/B
    AMD 2400 Processor
    Windows XP O/S
    Silicon Image SiI 3112 SATARaid Controller *
    Maxtor 80 Gb Hard drives x2 (striped) Array *
    WinTV PVR 250

    Then I came upon this article by a chap called Brian

    <snip>

    I discovered a way to make the problem you people are describing go away on my XP/TV rig.

    I had a system that was working perfectly, and I used Norton Ghost to make an exact copy of the OS from a system drive on the nForce ATA controller to a new system drive on the *Silicon Image SATA array controller. That's when I started seeing the problem. So long as I booted from that RAID set, I had to do the "stop/restart" on the WinTV card that has been described here. I tried putting the older hard drive back in, and the problem went away.

    The fix:

    I found that by changing the Hauppauge driver to start at "Boot" instead of "Automatically", the problem went away. However, this option (which in NT4 was available on all devices) is now only available on non plug-and-play devices in the GUI. You have to hack the registry.

    So let me say up front: This is risky. Have a backup of your system before you try this. I only tried it on mine, and it worked, but I can't promise it will work for you. I am not aware of any problems this will cause, but that doesn't mean there aren't any.

    In regedit, go to this key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl Set\Servic es\hcwPVRP2

    Change the value "Start" from "3" to "0".

    Cross your fingers and reboot.

    If your system is totally screwed up by this, you can always hit F8 and select "Last Known Good Configuration", which will return this area of the registry to the older, working values.

    Hope this helps.

    -Brian

    <snip>

    It certainly worked for me Brian . So many thanks.
    So I hope it works for others out there !!!

    So Hauppauge Tech support anything to add to this resolution.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Copyright © 1999-2011 . .
iskamPC.com | mobility.BG | Bloody's Techblog | | 3D Vision Blog |