First post, by marvins
Hi,
I have activate Glidos in order to play Tombraider 1.
It work fine (under Vista 32bits), but in the Lost City Level the Glidos Logo is turning on the screen.
What can I do to make it go away ?
Hi,
I have activate Glidos in order to play Tombraider 1.
It work fine (under Vista 32bits), but in the Lost City Level the Glidos Logo is turning on the screen.
What can I do to make it go away ?
By activate you mean the unlocking procedure, copying the GlidosID to the web page, and installing the key, yes?
Are you using v1.37?
Has your GlidosID changed since you unlocked?
Yes I mean unlocking Glidos using the GlidosID.
It works with the beginning of the game where the logo disappears, but in the Lost City level, the logo is here.
I didn't play more to say if the logo stays here in the next levels.
I use the last version of Glidos and the last version of VDos32.
I dont know if my GlidosID changed since I unlock, but if I start a new game, the logo isn't here.
Glidos inhibits the logo for the first two TR1 levels, so the problem is that Glidos is just not unlocked.
The all imporant thing is your GlidosID. You can log back into the unlock website and compare your current ID with the one you used to unlock. I think you'll find them different.
If you are not using v1.37 of Glidos, then that's it: versions before that wouldn't unlock correctly under Vista. If you using v1.37 then this could be more serious. Try repeatedly closing Glidos and restarting it to see if the GlidosID stays the same. It is supposed to. Also try rebooting your computer and see if that causes a change in ID. It shouldn't do.
I should be able to sort this out for you, when we've established the cause.
Ok, you were right, Glidos was not unlocked and the GlidosId was not the same as in the website. Strange...
So I unlock Glidos and now it works great !
Thanks a lot for all your job 😀
I have another little problem with Glidos :
I have a dual screen PC, and I play Glidos windowed (not fullscreen).
Every time the window refresh, she moves automaticaly between the two screens and I must use the mouse to put the window back in the middle of one of my screens.
This happens when the game begins, when a FMV begins, when I load a savegame.
Marvins, if you select Direct3D mode, the screen will always appear with its top right close to the top right of the main Glidos dialog.
Marvins, if you select Direct3D mode, the screen will always appear with its top right close to the top right of the main Glidos dialog.
Ok ! Thanks 😀 !
Hang on... so does this mean you are running Glidos and VDos32 under Vista and the audio is ok?
The sound is neatly ok.
In the setup I change the "Sound Blaster 16" settings to "Soundblaster" and the audio in the FMV is nearly perfect.
In the game theres no background music, but the FX are playing great.
Yesterday, I unlocked again Glidos, and today I wanted to play again and the Glidos Logo was here. So when I restart my PC, the GlidosID change and I must re-activate it again. It's take only 10/20 sec do to it, so it's not very important.
Is there anything I can do to help you to fix this problem ?
Can you describe the flaws in the audio when using SB16? Is it just generally scratchy, or does it pop, drop out, or echo.
For the unlock problem, I'll post a program later that should help find out what is happening.
Here's a program that should help sort out the activation problem. It would be handy if you could run it, press the Test button, and post the result. Even better if you can reboot your computer and repeat the experiment.
First : since yesterday my GlidosId change one time again.
So here are my results :
Before reboot :
[0,24] (Software Loopback Interface 1)
[1,131] (WAN-Miniport (L2TP))
[2,131] 50-50-54-50-30-30 (WAN-Miniport (PPTP))
[3,23] 33-50-6F-45-30-30 (WAN-Miniport (PPPOE))
[4,6] 7C-1B-20-52-41-53 (WAN-Miniport (IPv6))
[5,6] 7C-1B-20-52-41-53 (WAN-Miniport (IP))
[6,23] 20-41-53-59-4E-FF (Asynchroner RAS-Adapter)
[7,6] 00-18-F3-B6-21-EA (Marvell Yukon 88E8053 PCI-E-Gigabit-Ethernet-Controller)
[8,6] 00-18-F3-B6-2B-4A (Marvell Yukon 88E8053 PCI-E-Gigabit-Ethernet-Controller #2)
[9,131] 00-00-00-00-00-00-00-E0 (isatap.{B4967E83-7641-4201-AF0D-59DF73E67C97})
[10,131] 02-00-54-55-4E-01 (Teredo Tunneling Pseudo-Interface)
[11,131] 00-00-00-00-00-00-00-E0 (isatap.{E61B2DD9-5155-4251-BEDC-947C79438634})
[12,6] 7C-1B-20-52-41-53 (WAN-Miniport (IPv6)-QoS Packet Scheduler-0000)
[13,6] 7C-1B-20-52-41-53 (WAN-Miniport (IP)-QoS Packet Scheduler-0000)
[14,6] 00-18-F3-B6-21-EA (Marvell Yukon 88E8053 PCI-E-Gigabit-Ethernet-Controller-QoS Packet Scheduler-0000)
[15,6] 00-18-F3-B6-2B-4A (Marvell Yukon 88E8053 PCI-E-Gigabit-Ethernet-Controller #2-QoS Packet Scheduler-0000)
After reboot :
[0,24] (Software Loopback Interface 1)
[1,131] (WAN-Miniport (L2TP))
[2,131] 50-50-54-50-30-30 (WAN-Miniport (PPTP))
[3,23] 33-50-6F-45-30-30 (WAN-Miniport (PPPOE))
[4,6] D2-A9-20-52-41-53 (WAN-Miniport (IPv6))
[5,6] D2-A9-20-52-41-53 (WAN-Miniport (IP))
[6,23] 20-41-53-59-4E-FF (Asynchroner RAS-Adapter)
[7,6] 00-18-F3-B6-21-EA (Marvell Yukon 88E8053 PCI-E-Gigabit-Ethernet-Controller)
[8,6] 00-18-F3-B6-2B-4A (Marvell Yukon 88E8053 PCI-E-Gigabit-Ethernet-Controller #2)
[9,131] 00-00-00-00-00-00-00-E0 (isatap.{B4967E83-7641-4201-AF0D-59DF73E67C97})
[10,131] 02-00-54-55-4E-01 (Teredo Tunneling Pseudo-Interface)
[11,131] 00-00-00-00-00-00-00-E0 (isatap.{E61B2DD9-5155-4251-BEDC-947C79438634})
[12,6] D2-A9-20-52-41-53 (WAN-Miniport (IPv6)-QoS Packet Scheduler-0000)
[13,6] D2-A9-20-52-41-53 (WAN-Miniport (IP)-QoS Packet Scheduler-0000)
[14,6] 00-18-F3-B6-21-EA (Marvell Yukon 88E8053 PCI-E-Gigabit-Ethernet-Controller-QoS Packet Scheduler-0000)
[15,6] 00-18-F3-B6-2B-4A (Marvell Yukon 88E8053 PCI-E-Gigabit-Ethernet-Controller #2-QoS Packet Scheduler-0000)
Brilliant. Much appreciated. I think I can see the cause of the changing ID. I should be able to give you a version of VDos32 and Glidos that don't need repeated unlocking.
Actually, on closer inspection, I can't see what is causing the problem after all. Are you still having to unlock after every reboot?
only thing I see is that the wan miniport and it's qos are swapped
Water flows down the stream
How to ask questions the smart way!
Got it.
You are right about the WAN Miniport being the problem. I was thinking it wasn't because I already special case that. I check for that string and discard those records.
But, on my machine its "WAN Miniport" not "WAN-Miniport".
Looks like it's language specific ("Asynchroner RAS-Adapter" is german)
1+1=10
Ah right. That would figure
I just wanna try to new 1.38 Glidos version, but when I try to unlock it, the website says :
You have used your allocation of unlock codes.
What can I do ?
Try again now.