HELP!!!

[capone]

I had it happen once where I installed, rebooted, and then canceled what looked like a 2nd instal (you mentioned this is a "feautre" of the installer you were stuck w/). May not be your problem.

[TKLX.com]

I dont believe there is anything wrong with GB-PVR. I suspect there is something broken with the .net v1.1 runtime installed on your machine.

I have already tried to uninstall and reinstall .net a few times. then i would install gbpvr and it would work fine until the 2nd reboot. why would it work fine if the .net is broken? would another program be corrupting it?

thanks for your quick reply. I will keep trying. I'll uninstall .net and gbpvr and reinstall both again.

[betlit]

hmm.. this is just a shot in the dark.... could it be that you have a file in your root directory called 'program'?

in this case if you try to start an app in c:\program files\xy\stuff.exe, windows decides you want to start c:\program with 'files\xy\stuff.exe' as parameters. since 'program' is no win32-exe you'll get this message.

happened to me once when i ran xmltv the first time with out=c:\program files\xmltv\tv.xml without quotes

betlit

[rvtazdevil]

It almost sounds as though the file or database is getting corrupted. Do you have all the latest motherboard drivers installed? I have heard of this happening with Windows with bleeding edge non-Intel chipsets.

Rick

[Cippo]

Actually betlit is most probably right. Somewhere in the path to your installation of GB-PVR there is a space. To fix this (which should have been done by the installer) you must do some changes to your registry after the installation. Start regedit. On the left locate HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\GB-PVR Recording Service. Now on the right double click on ImagePath. Now put a quote (") as first character on the line and one as last. Depending on where you installed GB-PVR it should look something like this: "c:\program files\devnz\gbpvr\gbpvrrecordingservice.exe". Be careful while poking around in the registry so you don't change anything else! If the magic works you can now start the service without problems! Actually Microsoft recommend these paths to be quoted always by installers to avoid this problem.

Hope this helps,

Cippo

[smalldave]

Discovered the reason for my problems.

Installing a new virus checker found a huge number of files infected with Win32:Jeefo. The issue occured on a number of machines as I'd been using the same (infected) file to install GBPVR on various machines and consequently infecting those. Oops!

Jeefo alters the executable causing the 'not a valid win32 application' message.