New version crash

[HtV]

You should disable it to get rid of the error

[sub]

This weekend I built my 2nd GB-PVR system, everything on it was a clean install - XP SP2, all updates, and GB-PVR. I'm getting the crash on exist as well, but as the others noted, it seems harmless.

Yes, I have the 'direct access to hauppauge remote' setting enabled.

This 'direct access to hauppauge remote' should only be used by PVR250 or PVR350 owners. It doesnt do anything for any other model of Hauppauge device, and is even optional for PVR250 or PVR350 owners.

You've got a Hauppauge PVR USB2, so this setting shouldnt be enabled.

[mpking]

I've begun to get this error now.

But I'm getting it when I try to play a recorded show.

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 5/29/2006
Time: 8:09:46 PM
User: N/A
Computer: MICHAEL
Description:
EventType clr20r3, P1 gbpvr.exe, P2 1.0.2325.30009, P3 1b, P4 mscorlib, P5 2.0.0.0, P6 4333ab80, P7 122f, P8 14, P9 system.missingmethodexception, P10 NIL.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 63 00 6c 00 72 00 32 00 c.l.r.2.
0008: 30 00 72 00 33 00 2c 00 0.r.3.,.
0010: 20 00 67 00 62 00 70 00 .g.b.p.
0018: 76 00 72 00 2e 00 65 00 v.r...e.
0020: 78 00 65 00 2c 00 20 00 x.e.,. .
0028: 31 00 2e 00 30 00 2e 00 1...0...
0030: 32 00 33 00 32 00 35 00 2.3.2.5.
0038: 2e 00 33 00 30 00 30 00 ..3.0.0.
0040: 30 00 39 00 2c 00 20 00 0.9.,. .
0048: 31 00 62 00 2c 00 20 00 1.b.,. .
0050: 6d 00 73 00 63 00 6f 00 m.s.c.o.
0058: 72 00 6c 00 69 00 62 00 r.l.i.b.
0060: 2c 00 20 00 32 00 2e 00 ,. .2...
0068: 30 00 2e 00 30 00 2e 00 0...0...
0070: 30 00 2c 00 20 00 34 00 0.,. .4.
0078: 33 00 33 00 33 00 61 00 3.3.3.a.
0080: 62 00 38 00 30 00 2c 00 b.8.0.,.
0088: 20 00 31 00 32 00 32 00 .1.2.2.
0090: 66 00 2c 00 20 00 31 00 f.,. .1.
0098: 34 00 2c 00 20 00 73 00 4.,. .s.
00a0: 79 00 73 00 74 00 65 00 y.s.t.e.
00a8: 6d 00 2e 00 6d 00 69 00 m...m.i.
00b0: 73 00 73 00 69 00 6e 00 s.s.i.n.
00b8: 67 00 6d 00 65 00 74 00 g.m.e.t.
00c0: 68 00 6f 00 64 00 65 00 h.o.d.e.
00c8: 78 00 63 00 65 00 70 00 x.c.e.p.
00d0: 74 00 69 00 6f 00 6e 00 t.i.o.n.
00d8: 20 00 4e 00 49 00 4c 00 .N.I.L.
00e0: 0d 00 0a 00 ....

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I just double checked. I do not have 'direct access to hauppauge remote' enabled.

I have not applied any patches to 97.07 yet.

I've run fine for quite a few days on 97.07, so I'm not sure what has happend to make this start happening.

One other thing, twice, while I was typing this, I've seen a dos box flash on the screen, like the service was restarting (Very quick, can't read it) but nothing is in the eventlog to indicate this is actually what is happening.

I looked at the logs produced, and saw something about the software recorder plugin. (Which is very old, and I never ended up using) so I removed it's two files.
This did not appear to have any effect. Here's a weird part however.
when the program crashed, it threw the standard microsoft error. However, if I didn't close it, it would play the video in the background.

I'm attaching logs.

[sub]

What files do you have in the c:\program files\devnz\gbpvr\plugins directory?

[mpking]

These

(This should show version)
Video Archive is the new version that is 97.7

I'm still on MS-Access.

[sub]

Its one of those causing your problem. Sorry I couldnt be more specific.

Try moving them out of the directory and putting them back one at a time.

[mpking]

Yep. I'll report back when I find it.

[mpking]

MyVideosPlugin.dll is the culprit.

It's ok, I don't think I even use it really.

[mpking]

Ok.

I've definatly confirmed it being the MyVideosPlugin (Version 4.1)

You might want to add it to the survival guide. (if you get a chance, I can't believe the sheer number of posts you've done the last few days)

Any guessitmates on when all the patches are going to be rolled up into 97.7.1 (or something)

[sub]

Any guessitmates on when all the patches are going to be rolled up into 97.7.1 (or something)

Probably in a few days time. It wont help problems like this one though. The author this plugin (reven) will need to update the plugin for compatibility. He is already aware of this problem.