I've just installed Glidos 1.43 with VDos32 0.8b on Windows XP 32-bit SP3. Unfortunately, I've discovered that my Glidos ID changes after every reboot.

Seeing that this problem was encountered in previous versions of Glidos and posted about on this forum, I've run the "MIBTest.exe" executable one, rebooted, and ran it again. The results of this are posted below. I do have a randomly changing MAC number it seems.

===TEST 1===
[0,24] (MS TCP Loopback interface)
[1,6] 00-FF-68-DD-2C-8A (Juniper Network Connect Virtual Adapter)
[2,6] 00-13-D3-C3-C8-B5 (NVIDIA nForce Networking Controller - Virtual Machine Network Services Driver)

===TEST 2===
[0,24] (MS TCP Loopback interface)
[1,6] 00-FF-48-19-44-8A (Juniper Network Connect Virtual Adapter)
[2,6] 00-13-D3-C3-C8-B5 (NVIDIA nForce Networking Controller - Virtual Machine Network Services Driver)

Any help to avoid the constantly changing Glidos IDs would be appreciated. I don't want to burn up my Glidos allocations. And although I realize that I can enable/disable the driver for Juniper (doing so seems to return my Glidos ID to an "old" one), I was hoping that you might have a more elegant solution than that.

Also, I note that VDos32 needs to be unlocked after each reboot as well, but so far nothing has complained.