Page 1 of 1

Re: checksum error every time I start the game

Posted: Thu Oct 07, 2004 6:00 pm
by bizango
Unregistered wrote:Hi, I have a big problem after the today's patch : everytime I start the game there's a message "checksum error - please relaunch". I can click on "relaunch" but the game does not relaunch. When I manualy restart the game there's again the messag "checksum error" ...
Have you been in the game before the last patch?

I am having the same problem, just got my game yesterday and am trying to install. On Klient, they suggested it was a corruption in my install and I needed to reinstall. I'm installing my third time now and being very careful about noting any oddities.

edit later, I suspect it has something to do with our OS since other peeps are not reporting the same... I am running Win98SE and no other concurrent tasks.

Re: checksum error every time I start the game

Posted: Fri Oct 08, 2004 1:25 am
by bizango
I solved the bug. The update batch file did not completely copy all the files after being unpacked. This is probably peculiar only to Win98SE users.

I suggest you do not try this unless you fully understand what you are doing. If you make a mistake, you may need to reinstall...

Reboot your computer and go to your Ryzom directory. In it, you should find a file named UPDT_NL.BAT . Edit that file and delete all lines down to but not including the section that wants to copy Client_Ryzom_RD.EXE. In my case it was the section labeled "loop15:".

Then execute UPDT_NL.BAT. After that, you should be good to go.

Re: checksum error every time I start the game

Posted: Wed Oct 13, 2004 4:37 pm
by bizango
Bump for patch 11. I experience the same problem installing patch 11.

The problem should be peculiar only to Win98 users.

The workaround I describe in the previous message still works.

Re: checksum error every time I start the game

Posted: Thu Oct 21, 2004 5:30 pm
by bizango
Bump for patch 13. I experience the same problem installing patch 13.

The problem should be peculiar only to Win98 users.

The workaround I describe in response #3 still works.