registry files are not working on some systems

[FunkyFr3sh]

On a german system the registry path is not IPX Connection For DirectPlay , it is IPX-Verbindung für DirectPlay instead

Windows 7 SP1 x86

[solemnwarning]

Hey, lets localise bits of paths in the registry, wouldn't that be funny?

• Someone at Microsoft, probably

Thanks for reporting this, I guess I'll replace the reg files with a utility that checks for an existing provider by its Guid before updating it or registering a new one.

[FunkyFr3sh]

Yep, it's really weird.

Done some more testing:

On a new german windows 7 install I do not have the german reg keys, only the english ones.

What's weird, if I rename the key to "IPX-Verbindung für DirectPlay1" (appended 1 at the end) then it's still broken. BUT, if I prefix it with a 1 like "1IPX-Verbindung für DirectPlay" then it would actually switch to the english key name and it works. This is a really a mess.

So it seems to read both, but the order matters. Heres how it looks like with the 1 prefix (working)

Here original (broken - reads english first and then german)

Edit: Yep, it does not care about the name at all. Probably looks for the GUID?

named it z instead IPX Connection For DirectPlay to ensure it's the last in the list and it does override both the english and german key

[solemnwarning]

Yep, the GUID is used as the key for this. Games which hard-code a specific service provider use that.

[solemnwarning]

IPXWrapper 0.7.2 released.