Originally from: Don deCourcelle

Hi Paul,

I ran some experiments tonight.

First, I removed Glidos from G:/Program Files and then reinstalled it. There was no uninstaller I could find so I just removed the entire Glidos directory (hope that's right). I also went hunting for Glidos in the Registry, found some things and removed them too.

Then I reinstalled Glidos on my G: drive (my games boot drive), using the location G:/Program Files/Glidos. I ran Glidos and verified it was looking for the same ID as before: GlidosID: 0AA638A25742B565F3707211609D1BEE

I reinstalled the code I already had for that ID from last time, the one you also verified was working. Ran TR and no change – GLIDOS still spinning around.

Getting desperate, I went back into my
Control Panel -> System Properties -> Hardware Tab -> Device Manager and re-enabled drive C (as I mentioned, I normally keep this disabled when playing games to protect my business interests). Running Glidos now with C: enabled showed it wanted a different ID, and when I reinstalled my old Glidos code TR worked fine – no spinning GLIDOS!

There's something about drive C: ? Does Glidos require it to be there? If you are the author of all the Glidos code, maybe you could check for that?

Here's some more data for you...

When I originally bought Glidos months ago, I had booted from Drive G: at installation time, but drive C: was still enabled. When I ran the Glidos installer I missed the fact that it defaulted to drive C: and I installed and got it authorized all before realizing I had installed Glidos on the wrong drive. (This is sort of a bug in Glidos btw, it should default to installing on the boot drive, not drive C:)

Actually, everything would have been fine with that installation that way were it not for the LSASS.EXE errors I started getting when I rebooted from C: The LSASS.EXE errors were causes problems with my video driver. This did not go away, actually they got worse until I completely reloaded Windows XP from the CD on drive C:. :/ This was the point where I realized I had to take precautions to save my business data on that drive.

So that's how I came to my present situation. For business work I boot drive C: but for games I boot drive G: (a single processor configuration with drive C: disabled).

Getting back to the registry – is there perhaps something in the registry or a hidden file I can't uninstall, or something that has a link to my old drive C: installation?

That's everything I know. If you still have no clues what's wrong, may I again suggest using some sort of log or print trace I can forward back to you. A few print statements where Glidos verifies its code ought to clarify how this is going wrong. Probably easily fixed and in your best interests.

Thanks so much

Don deCourcelle