I have a question regarding moving Wine's C:/ drive to another file system. My hard drive is currently partitioned into 3 primaries. I have a NTFS partition that Windows is on, a Ext4 with Ubuntu, and a third, larger, FAT32 partition that I use to hold cross-OS data (music, pictures, documents ect).
I have had infinite difficulty getting wine to run apps that I installed (through wine) to my FAT32 partition. Every time I try to run an app, it throws an error "The program <appname> has encountered a serious error and needs to close...". After doing some Googling it seems Wine can only run apps that are installed to it's C:/ drive. This has created some problems for me as my Linux partition is substantialy smaller than my storage partition that I use for my windows apps. My question is, is it possible to either run apps off a different fat32 partition, or move the default C:/ folder to the fat32 partition. When I tried moving it manually it was impossible to create a link to it from the default install location.
Any ideas on how to remedy this?
Moving wine's C: drive to another file system
-
James Mckenzie
Moving wine's C: drive to another file system
1. Wine does not support running programs from a FAT32 partition at this time, very well.I have a question regarding moving Wine's C:/ drive to another file system. My hard drive is currently partitioned into 3 primaries. I have a NTFS partition that Windows is on, a Ext4 with Ubuntu, and a third, larger, FAT32 partition that I use to hold cross-OS data (music, pictures, documents ect).
I have had infinite difficulty getting wine to run apps that I installed (through wine) to my
FAT32 partition. Every time I try to run an app, it throws an error "The program <appname> has
encountered a serious error and needs to close...". After doing some Googling it seems Wine
can only run apps that are installed to it's C:/ drive. This has created some problems for me
as my Linux partition is substantialy smaller than my storage partition that I use for my
windows apps. My question is, is it possible to either run apps off a different fat32
partition, or move the default C:/ folder to the fat32 partition. When I tried moving it
manually it was impossible to create a link to it from the default install location.
2. FAT32 partitions do not support SYMLINKS in Linux. NTFS might, but that is an iffy proposition, from what I understand (please correct me if I'm wrong or incorrect about this.)
3. Is there any reason you cannot create another EXT4 type partition out of the FAT32 partition to support installing applications to?
Yes, your Wine applications, for now must be installed to a Linux type partition. This IS being worked on and will be available in the future (just cannot say when.)Any ideas on how to remedy this?
James McKenzie
I tried step 3, but it doesn't seem to work. My third primary is now split into 3 logicals; swap, fat32 and ext4 (for wine). When I tried to cut, via file explorer, the directory /home/.wine/drive_c to my ext4 partition "Wine" there was no paste option. I'm sure part of the problem could be by using the file explorer instead of terminal, but I want to check why this is happening before I start seriously screwing things up.
I've been wondering about how true this really is, since I run a TON of apps from a FAT32 disk just fine. It seems rather a problem with apps that require some sort of direct disk access, which means 99% of all other software should probably be fine, ext or FAT32.1. Wine does not support running programs from a FAT32 partition at this time, very well.
Well I went ahead and moved my drive_c folder to the new ext4 filesystem, linked the /home/username/.wine/drive_c to /media/Wine/drive_c and have gotten slightly farther. Now whenever I try to run a program, the cursor changes to the "hourglass" for ~15 seconds then nothing happens. If I run a Setup.exe type program off a cd, the splash screen will show up, but when I run the program I get two of the same errors: "The program IKernel.exe has encountered a serious problem and needs to close." I'm not sure why this is happening, drive_c stayed exactialy the same, and I cant imagine the link being an issue. My account is the owner of the new partition, that is the only issue I can see. Should I report this as a bug?
Here is the terminal output of a Setup.exe program:
Here is the terminal output of a Setup.exe program:
Code: Select all
fixme:winmm:MMDRV_Exit Closing while ll-driver open
fixme:winmm:MMDRV_Exit Closing while ll-driver open
<username>@<computername>:~$ wine: Unhandled page fault on read access to 0x0045b7a8 at address 0x45b7a8 (thread 0020), starting debugger...
Unhandled exception: page fault on read access to 0x0045b7a8 in 32-bit code (0x0045b7a8).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:0045b7a8 ESP:0033fe94 EBP:0033fea8 EFLAGS:00010216( R- -- I -A-P- )
EAX:00000000 EBX:7b883ff4 ECX:6606b201 EDX:0033ff10
ESI:7ffdf000 EDI:0045b7a8
Stack dump:
0x0033fe94: 7b85595c 7ffdf000 00000000 7b883ff4
0x0033fea4: 7ffdf000 0033fee8 7b857beb 7ffdf000
0x0033feb4: 0045b7a8 00000000 00000000 00000000
0x0033fec4: 00000000 00000000 00000000 00000000
0x0033fed4: 00000000 00000000 7bc9bff4 ffe0f1a4
0x0033fee4: 7ffdf000 0033fef8 7bc70db0 7ffdf000
Backtrace:
=>0 0x0045b7a8 EntryPoint() in ikernel (0x0033fea8)
1 0x7b857beb in kernel32 (+0x47bea) (0x0033fee8)
2 0x7bc70db0 call_thread_func+0xb() in ntdll (0x0033fef8)
3 0x7bc70f80 call_thread_entry_point+0x6f() in ntdll (0x0033ffc8)
4 0x7bc4c09a in ntdll (+0x3c099) (0x0033ffe8)
0x0045b7a8 EntryPoint in ikernel: pushl %ebp
Modules:
Module Address Debug info Name (63 modules)
PE 400000- 4aa000 Export ikernel
ELF 7b800000-7b93c000 Export kernel32<elf>
\-PE 7b810000-7b93c000 \ kernel32
ELF 7bc00000-7bcb8000 Export ntdll<elf>
\-PE 7bc10000-7bcb8000 \ ntdll
ELF 7bf00000-7bf04000 Deferred <wine-loader>
ELF 7e294000-7e2c8000 Deferred uxtheme<elf>
\-PE 7e2a0000-7e2c8000 \ uxtheme
ELF 7e2c8000-7e2d2000 Deferred libxcursor.so.1
ELF 7e2d2000-7e2d8000 Deferred libxfixes.so.3
ELF 7e2d8000-7e2dc000 Deferred libxcomposite.so.1
ELF 7e2dc000-7e2e4000 Deferred libxrandr.so.2
ELF 7e2e4000-7e2ee000 Deferred libxrender.so.1
ELF 7e2ee000-7e2f4000 Deferred libxxf86vm.so.1
ELF 7e2f4000-7e2f8000 Deferred libxinerama.so.1
ELF 7e2f8000-7e31a000 Deferred imm32<elf>
\-PE 7e300000-7e31a000 \ imm32
ELF 7e31a000-7e320000 Deferred libxdmcp.so.6
ELF 7e320000-7e324000 Deferred libxau.so.6
ELF 7e324000-7e33e000 Deferred libxcb.so.1
ELF 7e33e000-7e343000 Deferred libuuid.so.1
ELF 7e343000-7e460000 Deferred libx11.so.6
ELF 7e460000-7e470000 Deferred libxext.so.6
ELF 7e470000-7e489000 Deferred libice.so.6
ELF 7e489000-7e492000 Deferred libsm.so.6
ELF 7e4b1000-7e553000 Deferred winex11<elf>
\-PE 7e4c0000-7e553000 \ winex11
ELF 7e57f000-7e5a6000 Deferred libexpat.so.1
ELF 7e5a6000-7e5d6000 Deferred libfontconfig.so.1
ELF 7e5d6000-7e5eb000 Deferred libz.so.1
ELF 7e5eb000-7e661000 Deferred libfreetype.so.6
ELF 7e680000-7e694000 Deferred lz32<elf>
\-PE 7e690000-7e694000 \ lz32
ELF 7e694000-7e77c000 Deferred oleaut32<elf>
\-PE 7e6b0000-7e77c000 \ oleaut32
ELF 7e77c000-7e87c000 Deferred ole32<elf>
\-PE 7e7a0000-7e87c000 \ ole32
ELF 7e87c000-7e8de000 Deferred shlwapi<elf>
\-PE 7e890000-7e8de000 \ shlwapi
ELF 7e8de000-7eaae000 Deferred shell32<elf>
\-PE 7e8f0000-7eaae000 \ shell32
ELF 7eaae000-7eb22000 Deferred rpcrt4<elf>
\-PE 7eac0000-7eb22000 \ rpcrt4
ELF 7eb22000-7eb7c000 Deferred advapi32<elf>
\-PE 7eb30000-7eb7c000 \ advapi32
ELF 7eb7c000-7ec07000 Deferred gdi32<elf>
\-PE 7eb90000-7ec07000 \ gdi32
ELF 7ec07000-7ed38000 Deferred user32<elf>
\-PE 7ec20000-7ed38000 \ user32
ELF 7ed38000-7ee21000 Deferred comctl32<elf>
\-PE 7ed40000-7ee21000 \ comctl32
ELF 7ee21000-7ee2d000 Deferred libnss_files.so.2
ELF 7ee2d000-7ee37000 Deferred libnss_nis.so.2
ELF 7ee37000-7ee3f000 Deferred libnss_compat.so.2
ELF 7ee45000-7ee5e000 Deferred version<elf>
\-PE 7ee50000-7ee5e000 \ version
ELF 7efbb000-7efe1000 Deferred libm.so.6
ELF 7efe9000-7f000000 Deferred libnsl.so.1
ELF f74b7000-f74bb000 Deferred libdl.so.2
ELF f74bb000-f7615000 Deferred libc.so.6
ELF f7616000-f762f000 Deferred libpthread.so.0
ELF f764e000-f778e000 Export libwine.so.1
ELF f7790000-f77ae000 Deferred ld-linux.so.2
Threads:
process tid prio (all id:s are in hex)
0000000e services.exe
00000015 0
00000014 0
00000010 0
0000000f 0
00000011 winedevice.exe
00000017 0
00000016 0
00000013 0
00000012 0
00000018 explorer.exe
00000019 0
0000001d Setup.exe
0000001e 0
0000001f (D) C:\Program Files\Common Files\InstallShield\Engine\6\Intel 32\IKernel.exe
00000020 0 <==
Backtrace:
=>0 0x0045b7a8 EntryPoint() in ikernel (0x0033fea8)
1 0x7b857beb in kernel32 (+0x47bea) (0x0033fee8)
2 0x7bc70db0 call_thread_func+0xb() in ntdll (0x0033fef8)
3 0x7bc70f80 call_thread_entry_point+0x6f() in ntdll (0x0033ffc8)
4 0x7bc4c09a in ntdll (+0x3c099) (0x0033ffe8)
wine: Unhandled page fault on read access to 0x0045b7a8 at address 0x45b7a8 (thread 0024), starting debugger...
Unhandled exception: page fault on read access to 0x0045b7a8 in 32-bit code (0x0045b7a8).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:0045b7a8 ESP:0033fe94 EBP:0033fea8 EFLAGS:00010216( R- -- I -A-P- )
EAX:00000000 EBX:7b883ff4 ECX:59d7488f EDX:0033ff10
ESI:7ffdf000 EDI:0045b7a8
Stack dump:
0x0033fe94: 7b85595c 7ffdf000 00000000 7b883ff4
0x0033fea4: 7ffdf000 0033fee8 7b857beb 7ffdf000
0x0033feb4: 0045b7a8 00000000 00000000 00000000
0x0033fec4: 00000000 00000000 00000000 00000000
0x0033fed4: 00000000 00000000 7bc9bff4 ffaf0074
0x0033fee4: 7ffdf000 0033fef8 7bc70db0 7ffdf000
Backtrace:
=>0 0x0045b7a8 EntryPoint() in ikernel (0x0033fea8)
1 0x7b857beb in kernel32 (+0x47bea) (0x0033fee8)
2 0x7bc70db0 call_thread_func+0xb() in ntdll (0x0033fef8)
3 0x7bc70f80 call_thread_entry_point+0x6f() in ntdll (0x0033ffc8)
4 0x7bc4c09a in ntdll (+0x3c099) (0x0033ffe8)
0x0045b7a8 EntryPoint in ikernel: pushl %ebp
Modules:
Module Address Debug info Name (63 modules)
PE 400000- 4aa000 Export ikernel
ELF 7b800000-7b93c000 Export kernel32<elf>
\-PE 7b810000-7b93c000 \ kernel32
ELF 7bc00000-7bcb8000 Export ntdll<elf>
\-PE 7bc10000-7bcb8000 \ ntdll
ELF 7bf00000-7bf04000 Deferred <wine-loader>
ELF 7e294000-7e2c8000 Deferred uxtheme<elf>
\-PE 7e2a0000-7e2c8000 \ uxtheme
ELF 7e2c8000-7e2d2000 Deferred libxcursor.so.1
ELF 7e2d2000-7e2d8000 Deferred libxfixes.so.3
ELF 7e2d8000-7e2dc000 Deferred libxcomposite.so.1
ELF 7e2dc000-7e2e4000 Deferred libxrandr.so.2
ELF 7e2e4000-7e2ee000 Deferred libxrender.so.1
ELF 7e2ee000-7e2f4000 Deferred libxxf86vm.so.1
ELF 7e2f4000-7e2f8000 Deferred libxinerama.so.1
ELF 7e2f8000-7e31a000 Deferred imm32<elf>
\-PE 7e300000-7e31a000 \ imm32
ELF 7e31a000-7e320000 Deferred libxdmcp.so.6
ELF 7e320000-7e324000 Deferred libxau.so.6
ELF 7e324000-7e33e000 Deferred libxcb.so.1
ELF 7e33e000-7e45b000 Deferred libx11.so.6
ELF 7e45b000-7e46b000 Deferred libxext.so.6
ELF 7e46b000-7e484000 Deferred libice.so.6
ELF 7e484000-7e48d000 Deferred libsm.so.6
ELF 7e48d000-7e52f000 Deferred winex11<elf>
\-PE 7e4a0000-7e52f000 \ winex11
ELF 7e57f000-7e5a6000 Deferred libexpat.so.1
ELF 7e5a6000-7e5d6000 Deferred libfontconfig.so.1
ELF 7e5d6000-7e5eb000 Deferred libz.so.1
ELF 7e5eb000-7e661000 Deferred libfreetype.so.6
ELF 7e680000-7e694000 Deferred lz32<elf>
\-PE 7e690000-7e694000 \ lz32
ELF 7e694000-7e77c000 Deferred oleaut32<elf>
\-PE 7e6b0000-7e77c000 \ oleaut32
ELF 7e77c000-7e87c000 Deferred ole32<elf>
\-PE 7e7a0000-7e87c000 \ ole32
ELF 7e87c000-7e8de000 Deferred shlwapi<elf>
\-PE 7e890000-7e8de000 \ shlwapi
ELF 7e8de000-7eaae000 Deferred shell32<elf>
\-PE 7e8f0000-7eaae000 \ shell32
ELF 7eaae000-7eb22000 Deferred rpcrt4<elf>
\-PE 7eac0000-7eb22000 \ rpcrt4
ELF 7eb22000-7eb7c000 Deferred advapi32<elf>
\-PE 7eb30000-7eb7c000 \ advapi32
ELF 7eb7c000-7ec07000 Deferred gdi32<elf>
\-PE 7eb90000-7ec07000 \ gdi32
ELF 7ec07000-7ed38000 Deferred user32<elf>
\-PE 7ec20000-7ed38000 \ user32
ELF 7ed38000-7ee21000 Deferred comctl32<elf>
\-PE 7ed40000-7ee21000 \ comctl32
ELF 7ee21000-7ee2d000 Deferred libnss_files.so.2
ELF 7ee2d000-7ee37000 Deferred libnss_nis.so.2
ELF 7ee37000-7ee3f000 Deferred libnss_compat.so.2
ELF 7ee40000-7ee45000 Deferred libuuid.so.1
ELF 7ee45000-7ee5e000 Deferred version<elf>
\-PE 7ee50000-7ee5e000 \ version
ELF 7efbb000-7efe1000 Deferred libm.so.6
ELF 7efe9000-7f000000 Deferred libnsl.so.1
ELF f7408000-f740c000 Deferred libdl.so.2
ELF f740c000-f7566000 Deferred libc.so.6
ELF f7567000-f7580000 Deferred libpthread.so.0
ELF f759f000-f76df000 Export libwine.so.1
ELF f76e1000-f76ff000 Deferred ld-linux.so.2
Threads:
process tid prio (all id:s are in hex)
0000000e services.exe
00000015 0
00000014 0
00000010 0
0000000f 0
00000011 winedevice.exe
00000017 0
00000016 0
00000013 0
00000012 0
00000018 explorer.exe
00000019 0
0000001d Setup.exe
0000001e 0
00000023 (D) C:\Program Files\Common Files\InstallShield\Engine\6\Intel 32\IKernel.exe
00000024 0 <==
Backtrace:
=>0 0x0045b7a8 EntryPoint() in ikernel (0x0033fea8)
1 0x7b857beb in kernel32 (+0x47bea) (0x0033fee8)
2 0x7bc70db0 call_thread_func+0xb() in ntdll (0x0033fef8)
3 0x7bc70f80 call_thread_entry_point+0x6f() in ntdll (0x0033ffc8)
4 0x7bc4c09a in ntdll (+0x3c099) (0x0033ffe8)
err:ole:CoGetClassObject no class object {91814ec0-b5f0-11d2-80b9-00104b1f6cea} could be created for context 0x4
Why are you bothering with trying to link things to ~/.wine? Just create a new wineprefix on the ext4 partition, and use it.
http://wiki.winehq.org/FAQ#head-faf9617 ... 522d490faf
http://wiki.winehq.org/FAQ#head-faf9617 ... 522d490faf
That doesn't seem to work, or I am not doing something right. I ran the commands
Code: Select all
export WINEPREFIX=/media/Wine
wine winecfg[code] and it added files and directories to the new folder. However the "Browse C: Drive" in the start menu takes me right back to the original drive_c. I guess I'm a little fuzzy on what the export WINEPREFIX really did, it created some folders, but doesn't recognize them as the C:/ drive.-
John Drescher
Moving wine's C: drive to another file system
On Mon, May 31, 2010 at 5:22 PM, X-Windows <[email protected]> wrote:
Try to run the application from the new prefix in the terminal,
It did the correct thing. The browse C: drive shortcut did the wrong thing.That doesn't seem to work, or I am not doing something right. I ran the commandsCode: Select all
export WINEPREFIX=/media/Wine wine winecfg[code] and it added files and directories to the new folder. However the "Browse C: Drive" in the start menu takes me right back to the original drive_c. I guess I'm a little fuzzy on what the export WINEPREFIX really did, it created some folders, but doesn't recognize them as the C:/ drive.
Try to run the application from the new prefix in the terminal,
-
Gert van den Berg
Moving wine's C: drive to another file system
On Mon, May 31, 2010 at 23:28, John Drescher wrote:
WINEPREFIX should be correct. The ones installed with Wine usually
assume the default WINEPREFIX (As far as I know, they are create by
the packages for Wine, not Wine itself...)
(An understanding of how environment variables moves around under an
Unix-like system might also be useful, if the user really want to
understand why the shortcuts are unaware of the change...)
Gert
Another note: Menu shortcuts created for things installed in the newIt did the correct thing. The browse C: drive shortcut did the wrong thing.
Try to run the application from the new prefix in the terminal,
WINEPREFIX should be correct. The ones installed with Wine usually
assume the default WINEPREFIX (As far as I know, they are create by
the packages for Wine, not Wine itself...)
(An understanding of how environment variables moves around under an
Unix-like system might also be useful, if the user really want to
understand why the shortcuts are unaware of the change...)
Gert
I ran an installer and installed a program to "C:/Program Files" and it put it right back in the origional drive_c folder. So i went ahead and linked the origional drive_c to the new partition's drive_c and things seemed to be working, programs installed ok, but when I run them they come back with the same "This program has encountered a serious problem and needs to close" error. This is way too complicated...
-
John Drescher
Moving wine's C: drive to another file system
Install and run your program from the terminal. When things are notI ran an installer and installed a program to "C:/Program Files" and it put it right back in the origional drive_c folder. So i went ahead and linked the origional drive_c to the new partition's drive_c and things seemed to be working, programs installed ok, but when I run them they come back with the same "This program has encountered a serious problem and needs to close" error. This is way too complicated...
working this is what you need to do to be able to get help.
Start reading the FAQ here:
http://wiki.winehq.org/FAQ#head-13df66c ... 1479c880f5
John
-
John Drescher
Moving wine's C: drive to another file system
On Mon, May 31, 2010 at 6:03 PM, John Drescher <[email protected]> wrote:
export WINEPREFIX=/media/Wine
before you start your installation from the terminal.
John
I forgot to mention. Make sure you use your prefix.Install and run your program from the terminal. When things are notI ran an installer and installed a program to "C:/Program Files" and it put it right back in the origional drive_c folder. So i went ahead and linked the origional drive_c to the new partition's drive_c and things seemed to be working, programs installed ok, but when I run them they come back with the same "This program has encountered a serious problem and needs to close" error. This is way too complicated...
working this is what you need to do to be able to get help.
Start reading the FAQ here:
http://wiki.winehq.org/FAQ#head-13df66c ... 1479c880f5
export WINEPREFIX=/media/Wine
before you start your installation from the terminal.
John
-
Gert van den Berg
Moving wine's C: drive to another file system
On Mon, May 31, 2010 at 23:57, X-Windows <[email protected]> wrote:
created in the menu will set the variable for applications launched
from them to ehat it was for the installer...) (And if you do not run
the export on its own, you need to prefix it before every command...)
If you change the WINEPREFIX, you must also run the installer from the
terminal where you changed it.
Unix parts of http://en.wikipedia.org/wiki/Environmen ... e#Synopsis
and http://en.wikipedia.org/wiki/Environment_variable#Unix is relevant
if you want to understand why...
These have a similar effect. Assuming bash.... # ignore next part if
you are confused... (The environment within bash itself differs
though)
# Option 1
export WINEPREFIX=/some/where
winecfg
cd /media/cdrom
wine setup.exe
# Option 2
WINEPREFIX=/some/where winecfg
cd /media/cdrom
WINEPREFIX=/some/where wine setup.exe
Gert
You need to run the export every time you open a terminal. (shortcutsI ran an installer and installed a program to "C:/Program Files" and it put it right back in the origional drive_c folder. So i went ahead and linked the origional drive_c to the new partition's drive_c and things seemed to be working, programs installed ok, but when I run them they come back with the same "This program has encountered a serious problem and needs to close" error. This is way too complicated...
created in the menu will set the variable for applications launched
from them to ehat it was for the installer...) (And if you do not run
the export on its own, you need to prefix it before every command...)
If you change the WINEPREFIX, you must also run the installer from the
terminal where you changed it.
Unix parts of http://en.wikipedia.org/wiki/Environmen ... e#Synopsis
and http://en.wikipedia.org/wiki/Environment_variable#Unix is relevant
if you want to understand why...
These have a similar effect. Assuming bash.... # ignore next part if
you are confused... (The environment within bash itself differs
though)
# Option 1
export WINEPREFIX=/some/where
winecfg
cd /media/cdrom
wine setup.exe
# Option 2
WINEPREFIX=/some/where winecfg
cd /media/cdrom
WINEPREFIX=/some/where wine setup.exe
Gert
Alright, completely removed and reinstalled wine. Starting fresh, here is what I am doing.
When I click the launcher button to start an installer (Install Shield) I get the same error as in my first post. When I click the "Browse C: Drive" it correctly takes me to the clean install drive_c.
With an app that uses a different installer, the program installs without issue, but when I try to run the program, it throws the same error: "<programname> has encountered a serious problem and needs to close".
What is going on here? It is far too difficult to change an install directory in wine.
Code: Select all
export WINEPREFIX=/media/Wine
cd /media/CD_name
wine Setup.exe
With an app that uses a different installer, the program installs without issue, but when I try to run the program, it throws the same error: "<programname> has encountered a serious problem and needs to close".
What is going on here? It is far too difficult to change an install directory in wine.
For the InstallShield problem: what version of Wine are you using? If it's not the latest development release, upgrade. There were some problems with InstallShield a few versions ago that have been fixed.X-Windows wrote:Alright, completely removed and reinstalled wine. Starting fresh, here is what I am doing.
When I click the launcher button to start an installer (Install Shield) I get the same error as in my first post. When I click the "Browse C: Drive" it correctly takes me to the clean install drive_c.Code: Select all
export WINEPREFIX=/media/Wine cd /media/CD_name wine Setup.exe
With an app that uses a different installer, the program installs without issue, but when I try to run the program, it throws the same error: "<programname> has encountered a serious problem and needs to close".
For the second problem: what app is this? Post terminal output. Make sure you cd to the program directory before trying to run it.
Apps can fail to run for lots of reasons; don't assume this problem has anything to do with the location of the wineprefix.
According to winecfg About, I am using Wine 1.2-rc2.
I am currently installing DeusEx, a program i had working on the default C: drive (installed fine). Here is the output when I run the program through terminal:
I am currently installing DeusEx, a program i had working on the default C: drive (installed fine). Here is the output when I run the program through terminal:
Code: Select all
/media/Wine/drive_c/Program Files/DeusEx/System$ wine DeusEx.exe
err:module:attach_process_dlls "Core.dll" failed to initialize, aborting
err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program Files\\DeusEx\\System\\DeusEx.exe" failed, status c0000005
Did you remember to export WINEPREFIX=/media/Wine before all this?X-Windows wrote:According to winecfg About, I am using Wine 1.2-rc2.
I am currently installing DeusEx, a program i had working on the default C: drive (installed fine). Here is the output when I run the program through terminal:
Code: Select all
/media/Wine/drive_c/Program Files/DeusEx/System$ wine DeusEx.exe err:module:attach_process_dlls "Core.dll" failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program Files\\DeusEx\\System\\DeusEx.exe" failed, status c0000005
-
James McKenzie
Moving wine's C: drive to another file system
dimesio wrote:
automatically whenever the user logs in. This is beyond the scope of
this project.
James McKenzie
You can edit the users .profile file to add this so it will happenX-Windows wrote:
Did you remember to export WINEPREFIX=/media/Wine before all this?According to winecfg About, I am using Wine 1.2-rc2.
I am currently installing DeusEx, a program i had working on the default C: drive (installed fine). Here is the output when I run the program through terminal:
Code:
/media/Wine/drive_c/Program Files/DeusEx/System$ wine DeusEx.exe
err:module:attach_process_dlls "Core.dll" failed to initialize, aborting
err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program Files\\DeusEx\\System\\DeusEx.exe" failed, status c0000005
automatically whenever the user logs in. This is beyond the scope of
this project.
James McKenzie
