2007-01-03, 09:18 PM
If you had the config app open when you edited, then it would have been overwritten when you clicked ok in the config app.
2007-01-03, 09:18 PM
If you had the config app open when you edited, then it would have been overwritten when you clicked ok in the config app.
2007-01-03, 09:26 PM
Indeed, that could have been the case. I didn't notice a checkbox for that particular option in the config utility tho - does it exist? Thought perhaps the config utility appended only the settings it was aware of to the file, not rewrite the whole thing..
![]() S.
2007-01-03, 09:27 PM
Quote:I didn't notice a checkbox for that particular option in the config utility tho - does it exist?No there isnt. I only put commonly used options in the config app. This is not common - in fact, I've never recommend another user that they should change this, but I suspect something funny about this devices drivers requires it.
2007-01-03, 09:38 PM
It's a long shot, but might help.
I have looked for a solution that will allow me to "restart" the NIC cards from within the GBPVR. so, I found about a command "devcon". Not sure if I needed to install something, but it's part of the OS (so maybe I downloaded something from M$ or some kind of resource bundle, who knows). Anywho, this command can control the devices. It's like going to Device Manager and doing Disable, or Enable. Now, I am assuming (if not, then ignore this post ![]() It takes a lot of digging, cause this devcon has it's own way of refering to the devices. But you can list them. I managed to write the following batch file that will restart my NIC. works every time: Code: RunWait("devcon disable *DEV_4220*") Hope it helps...
* Rogers Analog Cable [Canada]
* Hauppauge WintTV PVR USB2 * IBM Thinkpad T42 / 1GB Mem / Centrino 1.6Ghz / 60GB HD / ATI Mobility Radeon 7500 + VGA/DVI out * MCE Remote + Keyboard * Win XP SP2 / GBPVR [Latest version. always] * Pioneer HDTV via VGA (1360x768) * MS Remote Keyboard * Logitech Harmony 880 [via MS Remote Control Reciever]
2007-01-03, 10:11 PM
(This post was last modified: 2007-01-03, 10:16 PM by BlueMagician.)
I don't want to jinx it, but it looks like a combination of v99.5 with that <BDAAutoDetectTuner> switch set, the latest (July 4.6.606) Hauppauge drivers, and a later CyberLink MUX (5.0.2022) has solved all.
I've both cold started, and resumed from standby a couple of times, and both tuners have responded and an MPEG2 file created successfuly. No 'Check Signal' or 0kb recordings so far... ![]() MY SINCERE thanks to all who made suggestions (I may still need them! lol), but for now a HUGE thanks to Sub to finding the solution to what I think was the critical thing. Cheers all, S.
2007-01-04, 02:32 AM
Cool - glad you got it working.
|
|