Urgent Help needed please.

[saintalan]

I have been running the MVP (UK) for a couple of months now with no major problems. From the start I have been using GBPVR/MyMusic etc in preference to the Hauppauge s/w.

Yesterday I made a few changes to accomodate pulling data of more than one server, basically by setting up an a/c on other machines. To start with no problems, managed to get music & video across 2 servers.

After playing with videos from the new server the MVP started to lose control as if it could not keep up and then would reboot back (bypassing the main screen) to the Video list. I then thought I would reset the MVP by unplugging power. (A mistake!) since then I have not been able to get the MVP working again. Forget GBPVR for the moment I can't get basic Hauppauge working I just get the intro screen with the 5 bars. No luck after a few hours last night. I left everything off overnight LAN router wireless bridge etc and it came on briefly this morning and then BAM same again. I have now been at it all day with no success.

I have tried reloading software/reconnecting LAN in variuous ways/turning off Firewalls etc and all the usual suspects but can not make it work.

I have had a similar problem occasionally to a much lesser extent where it refuses to boot but a couple of unplug/replugs has sorted it. NOT this time!

All and any ideas appreciated.

Cheers

Alan

[sub]

I'm not sure if this is your problem, but...

In the newest version v0.91.9 there is a bug on skins with the Clock or Next Recording panels which can cause the MVP not to start. Switching to the blue skin resolves the issue (as it doesnt have these enabled).

[saintalan]

THanks Sub but I am not even trying to run GBPVR at the moment. Just can't get it past the Hauppauge set up screen it does not get as far as contacting servers.

But thanks

Alan

[pauly666]

You've probably already done this, but have you done a full MediaMVP uninstall/delete remaining Hauppauge MediaMVP folders followed by a new install (of course with the MVP unpowered through all that)?

Do you have something that automatically kills the MVPStart service on a reboot so that the basic Hauppauge sw cannot come up (since it sounds like you are just trying to get back to basics at the mo)? This is likely if you always reboot and come up running GB-PVR (personally I always do mine manually just in case something like this happens and I forget! )

I hate it when things stop working!

[saintalan]

You've probably already done this, but have you done a full MediaMVP uninstall/delete remaining Hauppauge MediaMVP folders ...!

Done all that Paul except deleting any folders . I'll see if any remain.

Cheers

Alan

[saintalan]

Paul, thought you may have been on to something there as I had a lot of dupilcate folders remaining after the uninstall. But alas no luck.

I seem to remember something about networking connections from a switch have to be connected initially in the right order and thereafter they will be OK, but I cant seem to remember where I saw it. I'll do some searching!

Thanks

Alan

[Guy]

Hi Alan,

I'm sure that you've already thought about this, but I suffered a similar problem with my first MVP, which worked fine in my office when I was experimenting with it for a week or so, but as soon as I had installed it in its final location (under my TV, on top of a set top box) it started dropping the connection/booting back to previous menus, corrupting video etc, as soon as it was doing any hard work. Eventually, after I turned it off completely, I had real problems getting it to reload the hauppauge software at all.

Turns out that I had an MVP from a bad batch with a manufacturing glitch that meant the box overheated badly - in its new location (on top of a fairly warm set top box) it was overheating as soon as it was doing any hard work ....apparently any MVP that is marked as 'Model D3' (on the underside of MVP) is affected by this. Anything marked 'Model D3A' is a re-badged D3 that has been fixed.

This is unlikely to be the problem if you haven't moved your MVP to a 'hotter' place though and its been working fine for ages - but just in case you might check model number....took me ages & lots of hair pulling to figure this out at the time.


guy.

[saintalan]

Many thanks Guy. I have an E1 and its not in a hot place or indeed getting hot, but nevertheless I am beginning to think it may be the unit!

It's driving me mad!

Thanks,Alan

[Guy]

Hi Again Alan,

Here's something else you could try. This was from another problem that I had - it's probably easier if I describe my original problem and then you can figure out if it applies to your set up:

I have one MVP (call it MVP A) hooked up directly to my broadband router (with a standard ip address of 192.168.1.1). The main server ('videoserver') and a second MVP box (call it MVP B) are attached to a switch which is itself then linked by ethernet to the broadband router. The router provides a DHCP server that both of MVP boxes get their IP addresses from. The system and network kind of grew organically over last two months and was working no problems at all. Then I had to go an mess with it....

All I actually did was to actually power down the broadband router. After I brought it back up again, everything else on my network worked fine, except for MVP A, which refused to connect to the server, except leaving it running for ages & it would very occasionally connect and then lose the connection pretty quickly.

Like you I tried going back to the original hauppauge software, but same problem. Looking in the GBPVR logs (the gbpvr.exe.log.txt) on the videoserver it was apparent that the mvp was correctly announcing its presence and the videoserver was responding to it, but MVP A wasn't handshaking. Then looking in the hauppauge logs when trying to connect to the original software, I noticed that the the hauppauge software was also seeing the request from the MVP, but the IP address MVP A was declaring was 192.168.1.1 (e.g. my router's address), not 192.168.1.100 (which was the IP address the router thought that the MVP had). Throughout all of this MVP B continued to work fine.

Now I don't know, as I'm very new to networking, but I figured that what may have happened was that when I powered down the router, MVP A must have assigned itself an IP address in lack of an available external DHCP server & rather annoyingly it assigned itself the same address as my router.... Whatever actually happened the result was that MVP A was reporting itself as being at 192.168.1.1 to the videoserver, but the router believed it was at 192.168.1.100 (I was getting no response, for example, when trying to ping 192.168.1.100).

So what I ended up doing was:
1. Power everything down completely
2. bring up the router / dhcp server first
3. bring up the videoserver / other computers to renew their ip addresses etc.
4. power on MVP A and MVP B last

This seemed to do the trick. MVP A got its IP address from the router and correctly reported it to the videoserver and responded fine to pings.....

Incidentally - I had to completely power down MVP A before it would renew its IP address...

Anyway, I don't know if this story is of any use, but have a look in gbpvr and hauppauge logs when the mvp is trying to connect, to at least see if it is announcing itself to the world....

have fun!

g.

[colin]

download and run etheral to get an idea of what is happening in your network.

If you have your mvp connected through a router, check to see if the router is assigning an IP address (assuming the router is the DHCP server), otherwise whatever is serving out the IP addresses check it out.

Etheral will at least give you an idea as to what is happening with the MVP,

cheers,
Colin.