VOGONS


First post, by egranzow

User metadata
Rank Newbie
Rank
Newbie

I'm using DosBox to overcome W7's restrictions on 16B executables. I've built a command input line (thanks to forum posts that runs an old DOS program in the DosBox shell. I'm trying to access mutliple trees from the root directory, so I need 8.3 nomenclature to reference subdirs. The problem is that the results of both the DOS "%s" command (returns equivalent 8.3 pathname and a dir /x query both return different values for directories than the cd in DosBox. This may be a special case but it definitely looks like there's a bug in how DosBox is pointing to the directories. The command line I'm using is below. There are two directories, 2015_a~1 and 2035_a~2. The cd operation ends up pointing the opposite one as "MSDOS". This is a W7 64 environment. G: is local to that machine.

C:\Utilities\dosbox\dosbox.exe -exit -noconsole -c "mount c g:/" -c "c:" -c "cd \GSA_DHS\2035_A~2" -c "c:\mwcog.dhs\software\COGMC mc%_purpose_%.ctl"

Any help appreciated. Thanks.

ed granzow

Reply 2 of 3, by collector

User metadata
Rank l33t
Rank
l33t

And this is why DOSBox is not intended for non-gaming applications. Almost no DOS games need long file name support. Many features not needed by games have purposely have not been included. DOSBox has a high compatibility with games, but not so much applications.

The Sierra Help Pages -- New Sierra Game Installers -- Sierra Game Patches -- New Non-Sierra Game Installers

Reply 3 of 3, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

The matter was handled by email, as I was contacted there as well.

Water flows down the stream
How to ask questions the smart way!