Final Fantasy XI issues

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Post Reply
BenR
Newbie
Newbie
Posts: 2
Joined: Sun Jan 09, 2011 8:27 pm

Final Fantasy XI issues

Post by BenR » Mon Mar 30, 2020 4:50 am

Made this thread to stop making comments on the main page.

Attempting install from a brand new prefix on wine 5.0 - http://dpaste.com/1RQJVG7
Attempting install from a brand new prefix on wine 5.5 - http://dpaste.com/1P65866

Attempting to run FFXI from old prefix on wine 5.0 with virtual desktop - http://dpaste.com/1V5QQJG

FFXI now runs on wine 5.5 with or without virtual desktop, 5.4 did not when I had tested it the other day. So I guess I don't need to install fresh, but I'm not sure why the installer isn't going. I checked for hanging processes and found none.

pandoraxero
Level 1
Level 1
Posts: 6
Joined: Wed May 15, 2013 6:12 pm
Location: Michigan

Re: Final Fantasy XI issues

Post by pandoraxero » Mon Mar 30, 2020 7:40 am

most "fixme"s can be safely ignored
And just to check - the install stops after the lines displayed? That seems fairly short for a wine output.

The installer is known to have issues mostly pertaining to getting itself set up, where it looks like it's just spinning its wheels, but eventually returns to functioning normally. If you haven't been dropped back to the command line, it's still running. You can make a pot of coffee and come back and it should be on to the next step.

I would say try setting WINEDEBUG="+warn", but if you're not prepared for the deluge of output that can produce, it might not be a good idea - it produces a particularly large amount of output when it's stuck in the installer. it looks something like this:

Code: Select all

0009:warn:msidb:TABLE_CreateView table not found
0009:warn:msidb:WHERE_CreateView can't create table: L"MsiAssembly"
0009:warn:msidb:get_tablecolumns Couldn't find id for L"MsiAssembly"
- and prints that same 3 lines a couple hundred thousand times before continuing as normal. Without WINEDEBUG="+warn" it won't show these messages.
you might want to use &> to push all the console output to a file if there is a lot of output.

Post Reply