SUSE93 - wine - default drive and/or working directory
It is my understanding that wine might also be used to run some MSDOS apps on Linux? Under DOS/WIN environment, I have software that was initially installed on network drive "J" and will only run from that drive. I have successfully (and legally) run this software on a non-networked DOS/WIN machine by creating a local directory that is a copy of "drive J", then using "subst" command to make drive "J" point to a local directory; then make drive "J" the current directory, then invoke program. If I attempt to run software from any other "working directory", the software fails. Under SUS93, I figured out how to create a "drive J" in wine (using ln -s), but I don't know how to make "J" the current/working drive/directory before invoking the DOS app. Any ideas how to properly invoke this app under Linux?
On Tue, Aug 09, 2005 at 01:55:59PM -0400, Frank Bax wrote:
It is my understanding that wine might also be used to run some MSDOS apps on Linux? Under DOS/WIN environment, I have software that was initially installed on network drive "J" and will only run from that drive. I have successfully (and legally) run this software on a non-networked DOS/WIN machine by creating a local directory that is a copy of "drive J", then using "subst" command to make drive "J" point to a local directory; then make drive "J" the current directory, then invoke program. If I attempt to run software from any other "working directory", the software fails. Under SUS93, I figured out how to create a "drive J" in wine (using ln -s), but I don't know how to make "J" the current/working drive/directory before invoking the DOS app. Any ideas how to properly invoke this app under Linux?
cd ~/.wine/dosdevices ln -s /what/ever/directory j: and now drive j: points to the installation. Ciao, Marcus
At 02:51 PM 8/9/05, Marcus Meissner wrote:
On Tue, Aug 09, 2005 at 01:55:59PM -0400, Frank Bax wrote:
Under SUSE93, I figured out how to create a "drive J" in wine (using ln -s), but I don't know how to make "J" the current/working drive/directory before invoking the DOS app. Any ideas how to properly invoke this app under Linux?
cd ~/.wine/dosdevices ln -s /what/ever/directory j:
and now drive j: points to the installation.
I *did* that! My question was "what's next?". wine j:program.exe will invoke the program, but the working/current drive is not "J:" - at least that's what the application says when I try to run it. I think the current drive is still "C:", but I'm not even sure how to confirm that.
On Tue, Aug 09, 2005 at 03:12:26PM -0400, Frank Bax wrote:
At 02:51 PM 8/9/05, Marcus Meissner wrote:
On Tue, Aug 09, 2005 at 01:55:59PM -0400, Frank Bax wrote:
Under SUSE93, I figured out how to create a "drive J" in wine (using ln -s), but I don't know how to make "J" the current/working drive/directory before invoking the DOS app. Any ideas how to properly invoke this app under Linux?
cd ~/.wine/dosdevices ln -s /what/ever/directory j:
and now drive j: points to the installation.
I *did* that! My question was "what's next?". wine j:program.exe will invoke the program, but the working/current drive is not "J:" - at least that's what the application says when I try to run it. I think the current drive is still "C:", but I'm not even sure how to confirm that.
Just cd /what/ever/directory ; wine foo.exe It should pick up that it is in J: Ciao, Marcus
At 03:15 PM 8/9/05, Marcus Meissner wrote:
On Tue, Aug 09, 2005 at 03:12:26PM -0400, Frank Bax wrote:
At 02:51 PM 8/9/05, Marcus Meissner wrote:
On Tue, Aug 09, 2005 at 01:55:59PM -0400, Frank Bax wrote:
Under SUSE93, I figured out how to create a "drive J" in wine (using ln -s), but I don't know how to make "J" the current/working drive/directory before invoking the DOS app. Any ideas how to properly invoke this app under Linux?
cd ~/.wine/dosdevices ln -s /what/ever/directory j:
and now drive j: points to the installation.
I *did* that! My question was "what's next?". wine j:program.exe will invoke the program, but the working/current drive is not "J:" - at least that's what the application says when I try to run it. I think the current drive is still "C:", but I'm not even sure how to confirm that.
Just cd /what/ever/directory ; wine foo.exe
It should pick up that it is in J:
That was so easy, thanks! I got past the "current drive" errors from app, but it doesn't work under wine. I get the following messages, then it hangs. Warning: unprotecting the first 64KB of memory to allow real-mode calls. NULL pointer accesses will no longer be caught. fixme:int:DOSVM_Int10Handler Select Active Display Page (0) - Not Supported fixme:int:DOSVM_Int10Handler Read individual DAC register - Not Supported fixme:int:DOSVM_Int10Handler Read individual DAC register - Not Supported fixme:int:DOSVM_Int10Handler Read individual DAC register - Not Supported fixme:int:DOSVM_Int10Handler Read individual DAC register - Not Supported fixme:int:DOSVM_Int10Handler Read individual DAC register - Not Supported fixme:int:DOSVM_Int10Handler Read individual DAC register - Not Supported fixme:int:DOSVM_Int10Handler Read individual DAC register - Not Supported fixme:int:DOSVM_Int10Handler Read individual DAC register - Not Supported fixme:int:DOSVM_Int10Handler Read individual DAC register - Not Supported fixme:int:DOSVM_Int10Handler Read individual DAC register - Not Supported fixme:int:DOSVM_Int10Handler Read individual DAC register - Not Supported fixme:int:DOSVM_Int10Handler Read individual DAC register - Not Supported fixme:int:DOSVM_Int10Handler Read individual DAC register - Not Supported fixme:int:DOSVM_Int10Handler Read individual DAC register - Not Supported fixme:int:DOSVM_Int10Handler Read individual DAC register - Not Supported fixme:int:DOSVM_Int10Handler Read individual DAC register - Not Supported
On Wed, Aug 10, 2005 at 10:38:00AM -0400, Frank Bax wrote:
At 03:15 PM 8/9/05, Marcus Meissner wrote:
On Tue, Aug 09, 2005 at 03:12:26PM -0400, Frank Bax wrote:
At 02:51 PM 8/9/05, Marcus Meissner wrote:
On Tue, Aug 09, 2005 at 01:55:59PM -0400, Frank Bax wrote:
Under SUSE93, I figured out how to create a "drive J" in wine (using ln -s), but I don't know how to make "J" the current/working drive/directory before invoking the DOS app. Any ideas how to properly invoke this app under Linux?
cd ~/.wine/dosdevices ln -s /what/ever/directory j:
and now drive j: points to the installation.
I *did* that! My question was "what's next?". wine j:program.exe will invoke the program, but the working/current drive is not "J:" - at least that's what the application says when I try to run it. I think the current drive is still "C:", but I'm not even sure how to confirm that.
Just cd /what/ever/directory ; wine foo.exe
It should pick up that it is in J:
That was so easy, thanks! I got past the "current drive" errors from app, but it doesn't work under wine. I get the following messages, then it hangs.
Warning: unprotecting the first 64KB of memory to allow real-mode calls. NULL pointer accesses will no longer be caught. fixme:int:DOSVM_Int10Handler Select Active Display Page (0) - Not Supported fixme:int:DOSVM_Int10Handler Read individual DAC register - Not Supported
It is a DOS program... DOS program support is limited in WINE. Please use "dosemu" or "dosbox". Ciao, Marcus
It is my understanding that wine might also be used to run some MSDOS apps on Linux? Under DOS/WIN environment, I have software that was initially installed on network drive "J" and will only run from that drive. I have successfully (and legally) run this software on a non-networked DOS/WIN machine by creating a local directory that is a copy of "drive J", then using "subst" command to make drive "J" point to a local directory; then make drive "J" the current directory, then invoke program. If I attempt to run software from any other "working directory", the software fails. Under SUS93, I figured out how to create a "drive J" in wine (using ln -s), but I don't know how to make "J" the current/working drive/directory before invoking the DOS app. Any ideas how to properly invoke this app under Linux? You might be better off to use either DOSEMU or DOSBOX for regular DOS
On Tuesday 09 August 2005 1:55 pm, Frank Bax wrote:
programs. The setup is very simple. Nearly every DOS program will run under
these. Both Dosbox and DOSEmu are included with SuSE 9.3. I checked the
documentation and it is simple to set up different drives.
This is DOSEMU:
C:\>lredir j: LINUX\Fs\tmp
J: = LINUX\FS\TMP attrib = READ/WRITE
C:\>j:
J:\>dir
Volume in drive J is /tmp
...
--
Jerry Feldman
At 03:28 PM 8/9/05, Jerry Feldman wrote:
On Tuesday 09 August 2005 1:55 pm, Frank Bax wrote:
It is my understanding that wine might also be used to run some MSDOS apps on Linux? Under DOS/WIN environment, I have software that was initially installed on network drive "J" and will only run from that drive. I have successfully (and legally) run this software on a non-networked DOS/WIN machine by creating a local directory that is a copy of "drive J", then using "subst" command to make drive "J" point to a local directory; then make drive "J" the current directory, then invoke program. If I attempt to run software from any other "working directory", the software fails. Under SUS93, I figured out how to create a "drive J" in wine (using ln -s), but I don't know how to make "J" the current/working drive/directory before invoking the DOS app. Any ideas how to properly invoke this app under Linux?
You might be better off to use either DOSEMU or DOSBOX for regular DOS programs. The setup is very simple. Nearly every DOS program will run under these. Both Dosbox and DOSEmu are included with SuSE 9.3. I checked the documentation and it is simple to set up different drives. This is DOSEMU: C:\>lredir j: LINUX\Fs\tmp J: = LINUX\FS\TMP attrib = READ/WRITE
C:\>j:
J:\>dir Volume in drive J is /tmp ...
Sounds interesting - but neither package can be found on any of the 5 cd's I burned.
On Wed, 2005-08-10 at 10:41 -0400, Frank Bax wrote:
At 03:28 PM 8/9/05, Jerry Feldman wrote:
On Tuesday 09 August 2005 1:55 pm, Frank Bax wrote:
You might be better off to use either DOSEMU or DOSBOX for regular DOS programs. The setup is very simple. Nearly every DOS program will run under these. Both Dosbox and DOSEmu are included with SuSE 9.3. I checked the documentation and it is simple to set up different drives. This is DOSEMU: C:\>lredir j: LINUX\Fs\tmp J: = LINUX\FS\TMP attrib = READ/WRITE
C:\>j:
J:\>dir Volume in drive J is /tmp ...
Sounds interesting - but neither package can be found on any of the 5 cd's I burned.
Have you checked the ftp download area on your favorite mirror? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Wednesday 10 August 2005 10:41 am, Frank Bax wrote:
Sounds interesting - but neither package can be found on any of the 5 cd's I burned.
Here are the main pages for the 2 packages.
http://dosemu.sourceforge.net/
http://dosbox.sourceforge.net/download.php?main=1
--
Jerry Feldman
participants (4)
-
Frank Bax -
Jerry Feldman -
Ken Schneider -
Marcus Meissner