xiloader failing to open game

[ssj4puar]

Hello all,

I'm having an issue getting a server/client setup on the same PC working. When i open xiloader it can connect to the login server and i can create accounts. I can also select the account and log in. Once xiloader finishes it closes and XI never opens.

I thought it might be the server installation so i gave it a whirl with oldschool.dspt.info but the same thing happened. has anyone had this happen before?

I probably should mention that i have a 2nd installation of FFXI that i play on Nasomi's server. Cant really use that for Dev as its a really modified client and server arent whats currently on git. I know that XI uses windows registries to define an install path. im not sure how much xiloader would rely on that?

[whasf]

Sounds like your client is in a weird state (to play on Nasomi's server). Only thing I can suggest is to uninstall and reinstall it, but that'll prevent you from playing on Nasomi.

Your choice,,, lol

[ssj4puar]

yeah im having a friend who used to play on retail test via VPN to see if he can connect any better...


doesnt really help my scenario but at least it will yeild some answers

[ssj4puar]

I ended up changing some registry data in the windows registry and was able to get XI to launch. Its complaining about some version data issue so im going to attempt to update XI and see how it goes from here.

For those who are curious, i changed the following registry entries to switch to the DSP version:

Code: Select all

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{4CFFC456-9368-4CA4-9435-B65E7A5674ED}\1.0\0\win32
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{4CFFC456-9368-4CA4-9435-B65E7A5674ED}\1.0\HELPDIR
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{75AA93EE-48B1-4A54-B570-6E717178C49F}\1.0\0\win32
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{75AA93EE-48B1-4A54-B570-6E717178C49F}\1.0\HELPDIR
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{989D7900-6236-11D4-80E9-00105A81E890}\1.0\0\win32
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{989D7900-6236-11D4-80E9-00105A81E890}\1.0\HELPDIR
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{0DF0E951-D03C-4A94-90EF-40AE60668F5F}\InprocServer32
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{1027DC46-750D-4B1F-8834-1D25B8BEBAB8}\InprocServer32
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{989D790D-6236-11D4-80E9-00105A81E890}\InprocServer32
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{E636B693-A5A7-4161-9F02-D769178DE989}\InprocServer32
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{E697F40A-B701-4F75-A201-635FA69A41B3}\InprocServer32
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Classes\TypeLib\{3B0B8E16-C984-4792-ADD7-C23C75127DFD}\1.0\0\win32

I simply changed all (Default) key instances of "NasomiXI" to "PlayOnline" in the above mentioned registry locations. I'm assuming reverting the changes will allow me to reconnect to Nasomi. I have yet to test this.

[ssj4puar]

If this update for XI doesnt help the connect server is giving me the following error before it disconnects the client...

lobbyview_parse: Incorrect client version: got 301811xx_x, expected 301806xx_x
lobbyview_parse: The server must be updated to support this client version

when downloading the server i chose the "stable" repo. Should i get a different repo?

edit:
I was able to get on my server by changing the version.info file's version number from 30180604_0 to 30181103_0, pretty sure i just need to update the server but i'm not really sure how to go about that?

on an interesting side note. the registries i editted allow me to launch XI but prevent my from launching through the Nasomi Launcher that he provided. So it does appear to directly conflict with a 2nd installation of XI.

[whasf]

Sounds like there was a retail update, nothing really to do on your end until someone figures out what changed and updates the darkstar GitHub.

[jono659]

I did a lot of testing on this, you can run dsp with a Nasomi install but it's messy and hit and miss. Problem with the Nasomi install is that it isn't actually an install, it copies existing install folders to the Nasomi folder, then adds some registry settings and registers some DLLs. He also supplies a custom Bootloader.

In the end I used Nasomi uninstaller and installed from scratch.