Spring RTS Engine

I've just d/l'ed version 0.63b1 of Spring, which includes the new TASClient (0.15). The bad news is that this client doesn't work at all for me.

* At startup it gives me an "Failed to get data for '~Mhz'" error. But I can click it away.
* After that I get a nice "Access violation at adress ... bla bla bla". This one I can also click away.
* But at connection I get an infinite number of "Erro: FlagBitmaps not initialized! Please report this error!"

Uhm ... what's up?

Hmm it does work fine when I'm logged in as Administrator under Win2000. Normally I log in as a user. So I'm guessing the new client wants to access some parts of the registry where only admins can see.

Bit strange that the client doesn't use the same registry entry points as Spring ...

To answer to all of you having similar problems:

<sopel39> for example on start is says for me that it cant find data associated with ~MHZ
<sopel39> first bug
<sopel39> secong
<sopel39> it says TASClient has access voliation
<sopel39> third
<sopel39> countryflags can't be initialized
<sopel39> spring doesn't save my settings in game

Client saves all it's data to registry, for preferences it uses:
HKEY_CURRENT_USER\Software\TASClient

and to get CPU speed:
HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0

So if you don't have permission to access these registry locations, it obviously won't work. Also, if you use Windows 98 (or any windows before 2000 I think), you won't have the CPU path in the registry.

That explains it. But would you try to fix it so that regular window users don't get an error message? Because as it is at the moment, I can't use the client at all (perhaps you should try for yourself to launch it as a regular user ...).

If I disable the "show flags" option I no longer get a bunch of ""Erro: FlagBitmaps not initialized! Please report this error!" errors when connecting. Seems to me that the cpu tag is not the only thing causing problems ....

Lobby client has just been updated. These issues should now be fixed (you can use non-admin account, it will just ignore the CPU field in registry if it can't read it).