Can't autostart in emulate mode

[mvallevand]

I was trying to make an "autostart GBPVR in emulate mode" checklist for myself, so thought I'd share it in the forum. IF Martin says correct...Wiki-folks feel free to use :-)

That's a good effort and I'll add what my problem was. The key to this wiki entry is that it is the tweaker's that cause the problem, using the Windows defaults work just fine.

Under Control Panel -> System -> Device Manager

Setting

View -> By Connection
View -> Show Hidden Devices

There is a device called "Netbios over Tcpip" which has to be enabled. This is independent of the NetBIOS settings in networking.

http://msdn2.microsoft.com/en-us/library/ms143696.aspx shows the instructions I must have used to set this.

Martin

[mvallevand]

Wrt the dongle name: My guess is that gbpvr renames the file to dongle.bin before serving it to the mvp.(If at all necessary)

Using the GBPVR approach mvpmc requests dongle.bin and GBPVR responds by transferring the file that you have identified in the CONFIG program as the dongle. There is small issue here because the files that show up in the drop down must have a bin extension which goes against the mvpmc naming convention, so when alpha testing is over there won't be a dongle.bin anymore and a manual rename will be necessary. I just rename it to mvpmc.bin.

Regardless of the name you choose the file in the mvpmc share must be named dongle.bin.config

Martin

[jksmurf]

I have my server-ip there, not my mvp's ip:eek: this is from a post from Martin:

Sorry GBPVR Server is correct, but my server's (static) IP IS 192.168.1.10. Martin's post was correct.

Now the one million dollar question: Is it autostarting for you with these settings?

Nope :o . So much for the checklist. Even with firewall on or off, loads fine but goes to the mvpmc menu.... not sure what to do next ...

Thanks for the responses Martin. I'm keeping the revised dongle.bin name for now...

k.

[mvallevand]

So much for the checklist. Even with firewall on or off, loads fine but goes to the mvpmc menu.... not sure what to do next ...

There's still step one from the wiki

http://forums.gbpvr.com/showpost.php?p=1...stcount=64

Did you confirm that it shows

tftp=192.168.1.10

Martin

[jksmurf]

There's still step one from the wiki

http://forums.gbpvr.com/showpost.php?p=1...stcount=64

Did you confirm that it shows

tftp=192.168.1.10

Martin

Yes. As you can see I am a COMPLETE newbie at all this etc stuff, so ... what's next :-) (What's the password..?)

192.168.1.10 = GBPVR Server
192.168.1.200 = MVP.

btw I used to be able to type mediamvp.lounge in a browser window and WinXP Pro resolved the Static IP hostname to 192.168.1.200. Doesn't do that anymore???

k.

[pz1]

Yes. As you can see I am a COMPLETE newbie at all this etc stuff, so ... what's next :-) (What's the password..?)

192.168.1.10 = GBPVR Server
192.168.1.200 = MVP.

btw I used to be able to type mediamvp.lounge in a browser window and WinXP Pro resolved the Static IP hostname to 192.168.1.200. Doesn't do that anymore???

k.

I ran into the same problem you mention here. Did you check this http://forums.gbpvr.com/showpost.php?p=1...stcount=33 link? Please do note this is not a registry setting, but via -Menu-Programs-Administrative Tools-Local Security Policy. That did the trick for me.

[jksmurf]

I ran into the same problem you mention here. Did you check this http://forums.gbpvr.com/showpost.php?p=1...stcount=33 link? Please do note this is not a registry setting, but via -Menu-Programs-Administrative Tools-Local Security Policy. That did the trick for me.

Yup .. it hates me ....

k.

[mvallevand]

Yes. As you can see I am a COMPLETE newbie at all this etc stuff, so ... what's next :-) (What's the password..?)

192.168.1.10 = GBPVR Server
192.168.1.200 = MVP.

1. Your mount to GBPVR is working so you don't have a share problem
2. Mounting the MVP will never work and is not needed
3. The host name would come from either your hosts file or DHCP, it is not related to the MVP itself.

So, now that we now your share is connecting try this

ls /etc/mvpmc

You should see dongle.bin.config

If not then you have some rights issue on the file itself, if it is there, upload a copy, you might have a syntax error in it.

Martin

[jksmurf]

Hi,

Started from scratch. Checked & reset server IP address on server and in MVPs. Removed & re-created share. Checked users in User Manager and realised Guest account was disabled so enabled it.

Re-started GBPVR server processes & rebooted MVP. Whooopeeee! It works.

Well "I did a Bobins" and blow me, it worked! There must be something about deleting and re-creating shares after you have fiddled around with other stuff like guest logons etc.... I disabled guest a/c too.

Here's the ls output anyway...

k.

[pz1]

Well "I did a Bobins" and blow me, it worked! There must be something about deleting and re-creating shares after you have fiddled around with other stuff like guest logons etc....

Good!!
Did you first happen to move the dongle.bin.config to the mvpmc directory? If you move a file they don't get the access rights of the parent directory as far as I know. That might have caused the problem
This mvpmc dongle with autostart definitely increased the WAF at this end.
pieter