MVP with Rebuild GBPVR v 1.0.16

[sub]

lol

[HarryH3]

I don't run any firewalls and my MVP is slow to connect. Not 5 min, but not 5 sec either. Probably a min or two. I tried the mvpmc dongle and couldn't get it to work at all.

Oh, and it will still reset itself when setting up the first recurring recording also.

Double check the Windows Firewall setting. What you describe is EXACTLY the same symptom that I was seeing when the firewall had turned itself back on. I don't know why the mvpmc dongle wouldn't work, but it never loaded. The standard dongle.bin would load, but it took several minutes to do so. But once it loaded, trying to actually watch anything resulted in the MVP rebooting.

[mvallevand]

Double check the Windows Firewall setting. What you describe is EXACTLY the same symptom that I was seeing when the firewall had turned itself back on. I don't know why the mvpmc dongle wouldn't work, but it never loaded. The standard dongle.bin would load, but it took several minutes to do so. But once it loaded, trying to actually watch anything resulted in the MVP rebooting.

Thanks that would offer an explanation. Since the firmware tftp will timeout if the entire file is not received in a certain period of time, I'm betting that the elapse time window isn't large enough to transfer mvpmc's extra 1Mb You likely saw the blocks on the screen get to a certain point and then restart somewhere along the process, that would be because of this timeout.

Martin

[mkenyon2]

If somebody were to force open the Windows Firewall, what port would they use?

[HtV]

Sub, I think the only person who ever beat you was HtV last week.

Martin

I'm not sure if that's a compliment or a symptom of true addiction.:eek:

cya Hans

[HarryH3]

Thanks that would offer an explanation. Since the firmware tftp will timeout if the entire file is not received in a certain period of time, I'm betting that the elapse time window isn't large enough to transfer mvpmc's extra 1Mb You likely saw the blocks on the screen get to a certain point and then restart somewhere along the process, that would be because of this timeout.

Martin

Hi Martin, that's precisely what I was seeing. Shutting down Windows Firewall solved that issue.

[mvallevand]

If somebody were to force open the Windows Firewall, what port would they use?

I've answered this several times the easy one is here

http://forums.gbpvr.com/showpost.php?p=2...ostcount=3

and a more accurate one here

http://forums.gbpvr.com/showpost.php?p=2...ostcount=3

Martin

[steeb]

Thanks to HarryH3 for your comment , (and a note for any other XP users),

I thought it was weird as one of the 1st things I do on a new XP build is turn off the Firewall (BUT it is there for a reason, Firewalls are important!) Without a doubt after updating the MS O/S something turned the Firewall back on and I forgot to look at this as it wasn't an issue with previous GBPVR builds for me.

I would like to add that the response from the MVP with 1.0.16 is awesome, I used my first MVP with GBPVR build pre 99.05 and there were some issues, so good stuff, and booting into an MVP with this build (I've just timed it @ 3.5 seconds) makes it a VERY friendly Wife Acceptable Appliance!

Cheers

STEEB

[HarryH3]

Glad to hear that you got it working! Wouldn't you just love to slap the brainiac at Microsoft that released a patch to turn the firewall back on? I wonder how many millions of man hours were wasted around the world trying to figure that little "gotcha" out? :mad:

Like you, I didn't think to look at it, because I KNEW that I had turned it off. :confused:

[SFX Group]

1 thing to check........... DHCP is "Dynamic Host Configuration Protocol" now, this means you can pass shed loads of settings over to the MVP, one thing you really NEED to send is "option 1" which is the subnet mask of your network, this means the server knows what the subnet is to look for the server.

I found if this wasnt sent you get odd time delays, i always get a connection up in about 3 seconds and never had problems (even with v1.0.16), i use DHCP Turbo, my subnet is 255.255.255.0 but this will change depending on your network topology.