Yapi2Xml Errors - Possible Solution

[sjwaste]

Hey everyone, it's been a LONG time. I'm just getting back to trying GB-PVR again, since I've decided to rebuild my htpc.

Anyway, I ran into the common errors using Yapi2Xml, and I think I might've found a "fix". I got the runtime error, subscript out of range, as well as the non-fatal could not download lineups.

My fix was to rename MSINET.OCX in the plugin directory to MSINET.OC_ or anything else, basically backing up the file without deleting it (just in case I'm wrong here). The program works just fine after that, so maybe it's a bad hook in the specific version of the file included with the plugin. I hope this helps someone.

Mods, of course, delete if this post is in the wrong spot or it's so obvious it hurts, but I couldn't find it from searching.

[zehd]

Hey everyone, it's been a LONG time. I'm just getting back to trying GB-PVR again, since I've decided to rebuild my htpc.

Anyway, I ran into the common errors using Yapi2Xml, and I think I might've found a "fix". I got the runtime error, subscript out of range, as well as the non-fatal could not download lineups.

My fix was to rename MSINET.OCX in the plugin directory to MSINET.OC_ or anything else, basically backing up the file without deleting it (just in case I'm wrong here). The program works just fine after that, so maybe it's a bad hook in the specific version of the file included with the plugin. I hope this helps someone.

Mods, of course, delete if this post is in the wrong spot or it's so obvious it hurts, but I couldn't find it from searching.

You know, you may have found something. By renaming the ocx, you are correcting a possible 'DLL hell' problem. There's no doubt that the program is still using a version of msinet.ocx somewhere on your computer. It would be worth a look to search your whole drive for existences of the file and compare version numbers. It would be good to know what OS you are using and what versions are on your system...

[sjwaste]

You know, you may have found something. By renaming the ocx, you are correcting a possible 'DLL hell' problem. There's no doubt that the program is still using a version of msinet.ocx somewhere on your computer. It would be worth a look to search your whole drive for existences of the file and compare version numbers. It would be good to know what OS you are using and what versions are on your system...

That's exactly what I was going for. I knew it was a fairly common runtime file, and that it was probably already elsewhere, so I gave it a shot. Here are the versions I have on my machine, Win XP Pro SP3, IE7, .NET 2.0 runtime (latest), no 1.1 or 3.0 installed:

YApi2Xml Bundled: 6.0.88.62 (May 11, 2000) !!!!!! May 2000??

Here's where it gets interesting. The system has no other instance of that file present on the drive. I haven't looked at the source code, but this might be a case where there's a statically linked copy of the library in the executable conflicting with the bundled version.

I need to do a bit more digging, but one thing I do know, is that the program now works.

[khaver]

My installation has the May 11, 2000 version but it's been working fine for months. The only problem I've had was finding a time in the day that their server was working.