V2.0.1 issues

[kl1246]

Okay I'm going to start off by saying I'm a total amateur and I don't know what I'm doing. I really need help figuring out this problem. I keep getting this error when I'm using the newer version, and when I revert to an older version of xiloader it allows me to put in my login info, but obviously there's a version mismatch

[WinterSolstice8]

Try running xiloader from cmd.exe

it looks like FTX ui has problems with running from terminal or powershell, though I can't find any issues on it on their repo

[dawggydawgg]

Did you ever resolve this issue? I'm having same problem on a Windows 10 client with version 2.0.1 and 2.1.1. I've tried with cmd and Windows terminal and neither presents the FTUXI. I've updated Visual C++ redist and update .NET framework. I tested Xiloader on a 2022 server VM and it appears fine there (was able to least create an account). I need to figure out how to get my workstation with FFXI to work but not sure how to resolve this.

[dawggydawgg]

For those that might be having a similar issue, I was able to resolve this by adding a registry key to the machine. This seem to resolve the issues when running xiloader from cmd prompt.

Under HKLU:\Console , add a new Dword(32-bit) with the name 'VirtualTerminalLevel' and set the value to 1. Restart your cmd prompt and attempt to launch xiloader again.

[Binarynova]

I'm having an issue in Linux, using Wine, that I think is related to this. Wine uses it's own console host cohost.exe rather than the real windows command line, and I think it's unable to interpret ANSI escape codes.

When I launch a profile in Windower 4, I get the following:

Those garbage characters and messed up menu are drawn and scrolled down about four times before it stops and any keyboard key pressed makes the whole sequence go again.

I understand this is a very "YMMV" Linux issue, but using a pre-2.0 version of xiloader.exe shows the menu and interacts with the user just fine. But of course, that fails due to the mismatch with LandSandBoat.

---

EDIT: I found a workaround for this. Despite all the garbage characters flying by, the menu is still taking the input. So I simply pressed 2, then slowly entered each character of my username followed by ENTER, then the same for the password followed by ENTER, and then confirmed it followed by ENTER.

With those credentials in my Windower4 profile it now logs in.