View Full Version : Project 1999 under Linux Mint 11 via WINE?
Veluux
11-07-2011, 01:17 AM
I'm a relatively new Linux user, so I don't quite know all the ins and outs of the OS yet... so I need a little extra help getting this running. After a couple hours of tinkering around I was able to get EQ running under WINE, but only after patching (which I know i'm not supposed to do for P99). I couldn't find a way to change the target for the desktop link or "shortcut" to add the "patchme" to the eqgame.exe path. I successfully installed project 1999 on my windows 7 system, but can't get it working on Linux yet. I'm hoping to get it figured out before P1999Red releases on the 18th. Any help would be AMAZING! I tried following some of the Linux guides already posted, the UBUNTU guide (which would probably be closest to mine) is pretty outdated, was just wondering if anyone knew how to get this running under the newest release of WINE?
My specs are:
OS: Linux Mint 11
CPU: Phenom II x6 1090T
Memory: 16gigs
MB: Sabertooth 990FX
GPU: Nvidia GTX 560
So I know my computer should have no trouble running this at all, I just can't figure out the technical details. I'll be happily annoyed to find out that what I was doing wrong was something small and incredibly simple. Keeping my fingers crossed, lol.
Naez 4.20
11-07-2011, 04:14 PM
Make a file on desktop called EQEmu.sh, then put the following script in it
#!/bin/bash
cd "/path/to/Sony/EQEmu"
taskset -c 0x1 wine eqgame.exe patchme
Right click->properties->Permissions: Read&Write, Allow execution as program.
Give it a pretty icon
You might not need the 'taskset -c 0x1' since your processor is 6 cores, its a "dual core bug" fix and not sure if it affects you or not.
Veluux
11-08-2011, 01:22 AM
Make a file on desktop called EQEmu.sh, then put the following script in it
#!/bin/bash
cd "/path/to/Sony/EQEmu"
taskset -c 0x1 wine eqgame.exe patchme
Right click->properties->Permissions: Read&Write, Allow execution as program.
Give it a pretty icon
You might not need the 'taskset -c 0x1' since your processor is 6 cores, its a "dual core bug" fix and not sure if it affects you or not.
Hey, thanks for the response!
Did a fresh install of the game, double-checking all the normal things. Created the .sh file and copied in the script. When I click the .sh file I get a dialogue box that says:
"Do you want to run "EQEmu.sh", or display its contents?"
("EQEmu.sh" is an executable text file)
With the options to 1) Run in Terminal 2) Display 3) Cancel 4) Run.
Both Run and Run in Terminal don't do anything at all. Even watching my system monitor there is not even a slight rise in processor activity after choosing either of the options.
Veluux
11-08-2011, 01:25 AM
Oh. I also tried both the full script you listed, and then again without the 'taskset -c 0x1'
Naez 4.20
11-08-2011, 01:47 AM
post the output of the Run in Terminal option imo
Veluux
11-08-2011, 02:05 AM
It flashes something really fast, but I couldn't read it. I managed to take a screen shot, but the window is always half gone in the screen shot. It looks like it's saying:
/home/alex/desktop/EQEmu.sh: line 2: cd: /path/to/Sony/EQEmu: No such file or directory exists
I installed EQ via EQTitanium CD .iso's in WINE btw
Naez 4.20
11-08-2011, 02:08 AM
haha yea I had a feeling it might be something simple like that.
you gotta edit the "/path/to/EQEmu" to wherever eqgame.exe actually is on the drive!
Sounds like it might be in:
"/home/USERNAME/.wine/drive_c/Program Files/Sony/EverQuest"
But you'll have to find it yourself to make sure. BTW you'll have to "view->hidden files/folders" to see the .wine directory or find it with cmd line
Veluux
11-08-2011, 02:09 AM
That's what I was thinking as soon as I saw the partial screen shot. I'm gonna change it now and see what pops out
Veluux
11-08-2011, 02:15 AM
Its giving me the same error when my script is:
#!/bin/bash
cd "/home/alex/.wine/drive_c/Program Files/Sony/Everquest"
wine eqgame.exe patchme
Do I need to be linking it directly to the eqgame,exe file like this?:
#!/bin/bash
cd "/home/alex/.wine/drive_c/Program Files/Sony/Everquest eqgame.exe"
wine eqgame.exe patchme
Naez 4.20
11-08-2011, 02:16 AM
the 1st way would be right
try /yadda/EverQuest, because of linux case sensitivity maybe?
Veluux
11-08-2011, 02:25 AM
YAY Progress!!! So I was tinkering around and when I added eqgame.exe it said "Not a Directory" so I put took away eqgame.exe and left the / at the end and it worked! WINE attempted to boot the game and I got this WINE dialogue box:
""The program eqgame.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience.
This can be caused by a problem in the program or deficiency in Wine. You may want to check http://appdb.winehq.org for tips about running this application.
If this problem is not present under Windows and has not been reported yet, you can report it at http://bugs.winehq.org,""
Is this the message people were getting that led to the previous Linux guides where the directx files needed to be edited?
Naez 4.20
11-08-2011, 02:29 AM
the directx.c edit has more to do with character models than avoiding a fatal crash, but you could give it a shot (takes literally 2 hours to compile tho). I've ran it both with and without compiling wine from source, but have had my own unresolved issues (http://www.project1999.org/forums/showthread.php?t=53689) as well.
If you, instead of clicking the script, just open a terminal and copy/paste the 2 commands into it, you should be able to paste the logs of wine's output (it won't like auto-close the terminal when it crashes... or at least shouldnt !) and then it'll be easier to diagnose where its going haywire.
Veluux
11-08-2011, 02:36 AM
Oh geez. Yeah that's a hell of alot easier than timing a perfect screenshot, LOL. So here is what I got:
alex@ORION-LPC ~ $ #!/bin/bash
alex@ORION-LPC ~ $ cd "/home/alex/.wine/drive_c/Program Files/Sony/EverQuest/"
alex@ORION-LPC ~/.wine/drive_c/Program Files/Sony/EverQuest $ wine eqgame.exe patchme
fixme:advapi:SetSecurityInfo stub
fixme:win:EnumDisplayDevicesW ((null),0,0x32e9cc,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32ecd8,0x00000000), stub!
err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found 1280x720x32 @0! (XRandR)
err:d3d9:device_parent_CreateSwapChain (0x12d164) CreateAdditionalSwapChain failed, returning 0x8876086a
err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found 1280x720x32 @0! (XRandR)
err:d3d9:device_parent_CreateSwapChain (0x12d164) CreateAdditionalSwapChain failed, returning 0x8876086a
err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found 1280x720x32 @0! (XRandR)
err:d3d9:device_parent_CreateSwapChain (0x12d164) CreateAdditionalSwapChain failed, returning 0x8876086a
wine: Unhandled page fault on read access to 0xfffffffc at address 0x1000f0ce (thread 0009), starting debugger...
Veluux
11-08-2011, 02:39 AM
After I clicked "close program" a lot more popped up in the terminal from the debugging:
Unhandled exception: page fault on read access to 0xfffffffc in 32-bit code (0x1000f0ce).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:1000f0ce ESP:0032fa44 EBP:014a0074 EFLAGS:00010202( R- -- I - - - )
EAX:ffffffff EBX:0000001f ECX:00000000 EDX:ffffffff
ESI:0032fa90 EDI:01499930
Stack dump:
0x0032fa44: 01499930 014a3398 00000000 10013011
0x0032fa54: 00000818 00000000 0000000b 00001012
0x0032fa64: 00000000 0032fab0 1001301d 0032fa90
0x0032fa74: 00000000 014999d4 00000074 01499930
0x0032fa84: 00000074 00000004 0000000d 00000000
0x0032fa94: 00000000 00000000 00000000 00000004
Backtrace:
=>0 0x1000f0ce in eqgraphicsdx9 (+0xf0ce) (0x014a0074)
1 0x00000000 (0x014a00a8)
2 0x00000000 (0x101c58fc)
3 0x10003480 in eqgraphicsdx9 (+0x347f) (0x100034b0)
0x1000f0ce: movl 0x0(%ecx,%edx,4),%edx
Modules:
Module Address Debug info Name (86 modules)
PE 330000- 344000 Deferred dsetup
PE 400000- 9cf000 Deferred eqgame
PE d00000- d58000 Deferred dpvs
PE 1830000- 1b25000 Deferred eqmain
PE 10000000-10c8a000 Export eqgraphicsdx9
PE 21100000-2115f000 Deferred mss32
ELF 7b800000-7b97c000 Deferred kernel32<elf>
\-PE 7b810000-7b97c000 \ kernel32
ELF 7bc00000-7bcba000 Deferred ntdll<elf>
\-PE 7bc10000-7bcba000 \ ntdll
ELF 7bf00000-7bf04000 Deferred <wine-loader>
ELF 7c7e3000-7df05000 Deferred libnvidia-glcore.so.270.41.06
ELF 7df05000-7dfd3000 Deferred libgl.so.1
ELF 7dff3000-7e129000 Deferred wined3d<elf>
\-PE 7e000000-7e129000 \ wined3d
ELF 7e129000-7e15d000 Deferred d3d9<elf>
\-PE 7e130000-7e15d000 \ d3d9
ELF 7e1a0000-7e1d4000 Deferred uxtheme<elf>
\-PE 7e1b0000-7e1d4000 \ uxtheme
ELF 7e1d4000-7e1da000 Deferred libxfixes.so.3
ELF 7e1da000-7e1e4000 Deferred libxcursor.so.1
ELF 7e1e4000-7e1e8000 Deferred libxcomposite.so.1
ELF 7e1e8000-7e1f0000 Deferred libxrandr.so.2
ELF 7e1f0000-7e1fa000 Deferred libxrender.so.1
ELF 7e1fa000-7e200000 Deferred libxxf86vm.so.1
ELF 7e200000-7e204000 Deferred libxinerama.so.1
ELF 7e204000-7e20a000 Deferred libxdmcp.so.6
ELF 7e20a000-7e223000 Deferred libxcb.so.1
ELF 7e223000-7e33e000 Deferred libx11.so.6
ELF 7e33e000-7e34d000 Deferred libxext.so.6
ELF 7e34d000-7e365000 Deferred libice.so.6
ELF 7e365000-7e36d000 Deferred libsm.so.6
ELF 7e38d000-7e42e000 Deferred winex11<elf>
\-PE 7e3a0000-7e42e000 \ winex11
ELF 7e434000-7e45e000 Deferred libexpat.so.1
ELF 7e45e000-7e48d000 Deferred libfontconfig.so.1
ELF 7e48d000-7e4a2000 Deferred libz.so.1
ELF 7e4a2000-7e528000 Deferred libfreetype.so.6
ELF 7e529000-7e52b000 Deferred libnvidia-tls.so.270.41.06
ELF 7e548000-7e635000 Deferred comctl32<elf>
\-PE 7e550000-7e635000 \ comctl32
ELF 7e635000-7e696000 Deferred shlwapi<elf>
\-PE 7e640000-7e696000 \ shlwapi
ELF 7e696000-7e86f000 Deferred shell32<elf>
\-PE 7e6a0000-7e86f000 \ shell32
ELF 7e86f000-7e883000 Deferred lz32<elf>
\-PE 7e870000-7e883000 \ lz32
ELF 7e883000-7e89c000 Deferred version<elf>
\-PE 7e890000-7e89c000 \ version
ELF 7e89c000-7e8bd000 Deferred imm32<elf>
\-PE 7e8a0000-7e8bd000 \ imm32
ELF 7e8bd000-7e930000 Deferred rpcrt4<elf>
\-PE 7e8d0000-7e930000 \ rpcrt4
ELF 7e930000-7ea2f000 Deferred ole32<elf>
\-PE 7e950000-7ea2f000 \ ole32
ELF 7ea2f000-7ea68000 Deferred dinput<elf>
\-PE 7ea40000-7ea68000 \ dinput
ELF 7ea68000-7ea7d000 Deferred libresolv.so.2
ELF 7ea7e000-7ea82000 Deferred libxau.so.6
ELF 7ea82000-7ea9d000 Deferred dinput8<elf>
\-PE 7ea90000-7ea9d000 \ dinput8
ELF 7ea9d000-7eabd000 Deferred iphlpapi<elf>
\-PE 7eaa0000-7eabd000 \ iphlpapi
ELF 7eabd000-7eaeb000 Deferred ws2_32<elf>
\-PE 7eac0000-7eaeb000 \ ws2_32
ELF 7eaeb000-7eb80000 Deferred winmm<elf>
\-PE 7eaf0000-7eb80000 \ winmm
ELF 7eb80000-7ebda000 Deferred advapi32<elf>
\-PE 7eb90000-7ebda000 \ advapi32
ELF 7ebda000-7ec65000 Deferred gdi32<elf>
\-PE 7ebf0000-7ec65000 \ gdi32
ELF 7ec65000-7ed97000 Deferred user32<elf>
\-PE 7ec80000-7ed97000 \ user32
ELF 7ef97000-7efa3000 Deferred libnss_files.so.2
ELF 7efa3000-7efba000 Deferred libnsl.so.1
ELF 7efba000-7efe0000 Deferred libm.so.6
ELF 7efe0000-7efe5000 Deferred libuuid.so.1
ELF 7efe5000-7f000000 Deferred wsock32<elf>
\-PE 7eff0000-7f000000 \ wsock32
ELF f74e3000-f74ee000 Deferred libnss_nis.so.2
ELF f74f0000-f74f4000 Deferred libdl.so.2
ELF f74f4000-f7651000 Deferred libc.so.6
ELF f7651000-f766a000 Deferred libpthread.so.0
ELF f7682000-f768a000 Deferred libnss_compat.so.2
ELF f768a000-f77ca000 Deferred libwine.so.1
ELF f77cc000-f77ea000 Deferred ld-linux.so.2
Threads:
process tid prio (all id:s are in hex)
00000008 (D) C:\Program Files\Sony\EverQuest\eqgame.exe
00000009 0 <==
0000000e services.exe
00000014 0
00000010 0
0000000f 0
00000011 winedevice.exe
00000018 0
00000017 0
00000013 0
00000012 0
00000019 explorer.exe
0000001a 0
Backtrace:
=>0 0x1000f0ce in eqgraphicsdx9 (+0xf0ce) (0x014a0074)
1 0x00000000 (0x014a00a8)
2 0x00000000 (0x101c58fc)
3 0x10003480 in eqgraphicsdx9 (+0x347f) (0x100034b0)
Veluux
11-08-2011, 02:44 AM
I also tried changing the code to:
#!/bin/bash
cd "/home/alex/.wine/drive_c/Program Files/Sony/EverQuest/"
taskset -c 0x1 wine eqgame.exe patchme
But got the exact same error read-out from the terminal. So i'm thinking it has to do with the WINE build since the error is showing the retrace and return keywords that I remember from reading the linux guide for compiling WINE. You said it takes like 2 hours?
Naez 4.20
11-08-2011, 02:45 AM
Found some people with the same issues, but no clue if/how they resolved them...
http://www.winehq.org/pipermail/wine-users/2007-April/027033.html
http://appdb.winehq.org/objectManager.php?sClass=version&iId=2939&iTestingId=1215
My best guess at this point is bad gfx driver or bad install (of either wine or EQ) =X
I'm not really qualified to decipher the output or know anyone who is though! Maybe the Wine IRC channel or something man idk
Veluux
11-08-2011, 02:54 AM
Alright. Well thanks man. Still a big help, learning how to create a shell script shortcut on the desktop! That was kicking my but just trying to get the game to launch and not patch! Lol. It looks like its a problem with the graphics in WINE. I'm going to try editing the DLL they talk about in the main Linux guide.
Again, thanks for helping me get at least a little bit further. :D
Do you think maybe I just need to install a windows graphics driver with WINE?
cadiz
11-08-2011, 04:49 AM
Alright. Well thanks man. Still a big help, learning how to create a shell script shortcut on the desktop! That was kicking my but just trying to get the game to launch and not patch! Lol. It looks like its a problem with the graphics in WINE. I'm going to try editing the DLL they talk about in the main Linux guide.
Again, thanks for helping me get at least a little bit further. :D
Do you think maybe I just need to install a windows graphics driver with WINE?
Do you have a 64bit os? Make sure you have 32bit x11 and mesa packages.
Veluux
11-08-2011, 05:02 AM
Do you have a 64bit os? Make sure you have 32bit x11 and mesa packages.
Meh. I'm trying an alternative route. I'm going to see if I can get it running in a Win7 Virtual Box. My computer is quite powerful enough to run both OS's simultaneously, and it's an older game that uses less GPU resources anyhow. So I think it's a simpler route. Besides, now one of my additional 4 HDD's actually has a purpose. Lol.
Appreciate all the help guys. If all else fails I will just run P1999 on my old computer (win 7 OS). Cause there's no way i'm moving away from Linux on my new computer. :D
Mcbard
11-14-2011, 05:36 PM
I've heard that Virtual Box virtual drivers are pretty lame and make gaming under Virtual Box difficult.
How did that work out for you? Does it run fine?
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.