Technical Support

Hey all,
After years of no particular errors happening between me and Ryzom, I have a new one, and it's really peculiar:

I activate the client and the first thing I see, even before the login screeen is:



If I click on either "Continue" or "Cancel" the window disappears and the client starts normally. (Try Again refreshes the error message, naturally enough.) So this isn't really a *problem* so much as a puzzle/really minor irritation.

This started when I had to (major crash) go from my Win7 to a new Win10 computer. The directory for the Ryzom installation was copied directly from the old disk.

The directories for the other three installations I have on my machine are still on the original disk, which I added to the new computer. All are the current patched 64bit client, all of them give the same error.

In both machines C: is the system disk, D: is/was a CDRW drive and E: is the data disk.

1. Has anyone else seen this???
2. Anyone have any ideas?

3. Yes, I have sent in a ticket. I got a note back saying it was very peculiar and shouldn't be happening. I agree.

Have you checked in the usual system config files for a reference to said D: drive? Yes, there's no reason for such reference to appear, but..

Another suggestion, try running regedit and look at the Ryzom-related keys without modifying them..

Error is from Windows and not from Ryzom. Not sure whats causing it.
See if opening/closing drive fixes it. Next workaround would be to rename drive d: to some other letter that comes after e:. Disk (or drive) manager (windows admin tools) can do that.

@Mjollren --
That was the first thing I tried (though I didn't expect to find anything since I wasn't getting the message when running in Win7) and there was nothing.
Checking the registry, I don't find anything with D: in it.

@Karu - Yes, I know the error is from Windows, but Ryzom has to be triggering it somehow.

continuing on...

Odd thought...

Does your new system have ALL of the same *.DLLs, and are they all in the same places? I mean, I know you copied the Ryzom directories, but if there is anything outside of those directories (maybe OpenGL/DirectX stuff) that the client calls on, the filepaths may not match up. What happens when it can't find what it's looking for? Usually an error.

Over the decades I've been computing, I've found that when dealing with Windows, blaming DLLs is often a good default position with filepaths a strong second guess.

If the client were misbehaving after the error window pops up, I'd agree with you, Gidget, but it runs fine. The PATH variable has no D: in it. In addition I can't see any .dll calling on drive D: when it is a DVD. It is mysterious.