Done. 😕 Still don't understand it... as the autoexec is the same with or without "-c .."; and on the other hand adding the same PATH stuff from autoexec into a "-c .." command works again. wd, maybe you could be a bit more eloquent to a newbie? 😉

Yes, thanks, I got it working now with such a work-around (or one like I described in my previous message). Just I still don't understand that if it's a character limit of autoexec, why does it work fine if only I don't put any "-c ... " in the command line...

Thanks Qbix, but why does the same dosbox.conf (*with* the PATH command) then work without any "-c" in the command line?? And why does it also seem to work, as I found out, if I delete the PATH command from dosbox.conf, and write dosbox -conf dosbox.conf -c "set PATH=z:\;e:\bat\e:\graf\mg321\;e:\ …

(the above doesn't solve the problem, though, since the PATH settings are needed for the programs to work... so is this a bug?)

Yes, I can reproduce that: If I comment out the line with SET PATH=... , it works correctly. However, changing %PATH% in that line to Z:\ does not help... (yes, it should be "already", not "allready" - I just wrote the error message as it appears on the screen)

Qbix: Pity. MiniMax: If I had MS-DOS 7 (but I don't), that might be a way, just somewhat more complicated than if that would directly be supported by DosBox (should be easy, in lfnlib source code everything needed should be there... although only for running on Windows as a host OS).

Strange... Could you try exactly my dosbox.conf (or at least its autoexec section), for most exact reproduction? It seems that that error message ("Exit to error: autoexec: allready created...") continues with the 14th character of the first executable line in the autoexec section.

P.S.3: The mentioned behavious seems to come up if there are any executable commands in the autoexec section of dosbox.conf... (only, e.g., "SET" is ok, but with, e.g., "mount" the error appears)

Attachments don't seem to work for some reason, so here is dosbox.conf: [sdl] # fullscreen -- Start dosbox directly in fullscreen. # fulldouble -- Use double buffering in fullscreen. # fullresolution -- What resolution to use for fullscreen: original or fixed size (e.g. 1024x768). # windowresolution …

P.S.: This behaviour as described in 3) above seems to be independent of what is the command, also if I change it to "dir" it's the same P.S.2: Finally comes the DosBox.conf (I hope)

Ok, I will specify the problem further with an example (attached is my dosbox.conf for reference): - 1) If I start DosBox just with "DosBox -conf dosbox.conf", and then manually type "drawperf" (to start a batch file in the path that launches the DOS graphics program Draw Perfect), it works fine. - …

I use VBDOS with data files that are also used by other Windows programs. These data files may have long file names. For VBDOS, there is a library called lfnlib which translates long to short filenames, and vice versa. It works in any "DOS in Windows", but not in DosBox.

I know this is not exactly an issue for most games, but would it be possible to add support for long files names, in the same or compatible way as done in Win 95/98 (and further until XP) to DosBox? I'm using DosBox with Visual Basic for DOS, and inside that a library called lfnlib that translates …

Sorry if I have overseen something obvious, but is it possible to add a command from the DosBox command line to be executed *after* the config file is processed, but *without* mounting anything? ( seems to try to mount to C, "-C " seems to add a command *before* the config file is read)

wd: Ok, although I had really no problems of mounting c:\ to C, I took your advise and moved all DOS applications away from drive c: - took a while to fix all those static links in numerous batch and other files again, but now it seems to work without using drive C at all for any program except …

I agree with Kruwi that practically all of the DOS programs that I'm using are running well with DosBox. So making it more useable for people who want to run general DOS applications, or for people who program under DOS (I'm still using VBDOS a lot), it not actually necessary to add lots of more …

P.S.: Is there any special reason why not to use c:\ as C otherwise? Does DOSBOX write any files to C which could overwrite system files?

When I mount c:\ as C in DOSBox, it gives me a message "you shouldn't do this, use a subdirectory next time". This post gives an example why this may be a very useful thing to do anyway: I have two PCs, on both of which is running and old, but very good DOS graphics program which uses DOS full …