You have commas in the "/o op+,os+,ow+,oz+,oaq+,osq+,omq+" portion. Could those be interfering with the parsing, since snasm68k.exe uses commas to separate the paths that follow? If so, perhaps doing...

1set var1=/o op+,os+,ow+,oz+,oaq+,osq+,omq+
2..\..\asm\dosbox\snasm68k.exe /j ..\..\src\ /p /k %var1% ..\..\src\source.asm,..\..\bin\emu\rom.bin,..\..\bin\emu\rom,..\..\bin\emu\rom > ..\..\logs\emu.log

...would work. I think that you'll have to use DOSBox SVN Daum, though, since this doesn't work in official DOSBox and even recent vanilla SVN builds ("echo %var1%" echoes "%var1%", not the contents of the variable). It seems ironic that, for as much as the devs say that SVN Daum is "broken," it gets right a basic DOS feature that their own builds don't. If you don't want to use SVN Daum, using 4DOS inside DOSBox might work, instead.

If commas in that portion isn't the problem, maybe simply using DOSBox SVN Daum or 4DOS in DOSBox would make your existing batch file work, since your problem could be related to the same incomplete DOS support in official/vanilla DOSBox that I just gave an example of.

Osprey wrote:

You have commas in the "/o op+,os+,ow+,oz+,oaq+,osq+,omq+" portion. Could those be interfering with the parsing, since snasm68k. […]
Show full quote

You have commas in the "/o op+,os+,ow+,oz+,oaq+,osq+,omq+" portion. Could those be interfering with the parsing, since snasm68k.exe uses commas to separate the paths that follow? If so, perhaps doing...

Copy code to clipboard

1set var1=/o op+,os+,ow+,oz+,oaq+,osq+,omq+
2..\..\asm\dosbox\snasm68k.exe /j ..\..\src\ /p /k %var1% ..\..\src\source.asm,..\..\bin\emu\rom.bin,..\..\bin\emu\rom,..\..\bin\emu\rom > ..\..\logs\emu.log

...would work. I think that you'll have to use DOSBox SVN Daum, though, since this doesn't work in official DOSBox and even recent vanilla SVN builds ("echo %var1%" echoes "%var1%", not the contents of the variable). It seems ironic that, for as much as the devs say that SVN Daum is "broken," it gets right a basic DOS feature that their own builds don't. If you don't want to use SVN Daum, using 4DOS inside DOSBox might work, instead.

If commas in that portion isn't the problem, maybe simply using DOSBox SVN Daum or 4DOS in DOSBox would make your existing batch file work, since your problem could be related to the same incomplete DOS support in official/vanilla DOSBox that I just gave an example of.

Ok,

1) Where do i go to get DOSBox SVN Daum?
2) Where do i get 4DOS, it's website and how do i install it?

Sincerely,

Scorpion Illuminati

Scorpion Illuminati wrote:

1) Where do i go to get DOSBox SVN Daum?
2) Where do i get 4DOS, it's website and how do i install it?

Well, you could just google them 😉, but I'm feeling nice, so...

SVN Daum is available at http://ykhwong.x-y.net/

For 4DOS, my post here has a link and some instructions that may be useful: HOW-TO Use the FOR command (+ other missing DOS commands) & automate ISO mounting

Rather than running 4DOS.com /c, followed by each command that you want, though, you may prefer to simply run it once and do all of your work in its environment.

I would try SVN Daum first, if it wasn't clear, as I've tested that the variable use that I gave above works in it. I mentioned 4DOS only if you really prefer the DOSBox build that you're on or if you end up having any further problems that 4DOS might solve.

1@echo off
2rem save the old path
3@echo on
4SET oldpath=%path%
5
6@echo off
7rem set the path to the working folder, otherwise compilation will fail
8@echo on
9path c:\;%path%
10
11@echo off
12rem delete old assembled binary if it exists
13@echo on
14if exist ..\..\bin\emu\rom.bin del ..\..\bin\emu\rom.bin
15
16@echo off
17rem /j set include search directory
18rem /p pure binary
19rem /k enable if assembler directives
20rem /o enable optimisations
21rem ow+ optimise absolute long addressing
22@echo on
23set flags=/o op+,os+,ow+,oz+,oaq+,osq+,omq+
24rem ..\..\util\4dos.com /c ..\..\asm\dosbox\snasm68k.exe /j ..\..\src\ /p /k %flags% ..\..\src\source.asm,..\..\bin\emu\rom.bin,..\..\bin\emu\rom,..\..\bin\emu\rom
25rem ..\..\util\4dos.com /c ..\..\asm\dosbox\snasm68k.exe /j ..\..\src\ /p /k %flags% ..\..\src\source.asm,..\..\bin\emu\rom.bin,..\..\bin\emu\rom,..\..\bin\emu\rom > ..\..\logs\emu.log
26..\..\asm\dosbox\snasm68k.exe /j ..\..\src\ /p /k %flags% ..\..\src\source.asm,..\..\bin\emu\rom.bin,..\..\bin\emu\rom,..\..\bin\emu\rom > ..\..\logs\emu.log
27
28@echo off
29rem restore the old path
30@echo on
31path %oldpath%
32pause

SNASM68K, version 2.02Ex, Mar 24 1995, 15:22:35 (c) 1993-95 Cross Products Ltd. All Rights Reserved Warning : Could not open lis […]
Show full quote

SNASM68K, version 2.02Ex, Mar 24 1995, 15:22:35
(c) 1993-95 Cross Products Ltd. All Rights Reserved
Warning : Could not open list file '..\..\bin\'
*********************
* Binary Statistics *
*********************

*********************
* Rom Usage *
*********************
43554 bytes used
4150238 bytes left

*********************
* Ram Usage *
*********************
772 bytes of ram used
64763 bytes of ram left

No Dice unfortunately, even though it looks like it's being concatenated correctly. Trying your suggestion to use 4DOS:

1@echo off
2rem save the old path
3@echo on
4SET oldpath=%path%
5
6@echo off
7rem set the path to the working folder, otherwise compilation will fail
8@echo on
9path c:\;%path%
10
11@echo off
12rem delete old assembled binary if it exists
13@echo on
14if exist ..\..\bin\emu\rom.bin del ..\..\bin\emu\rom.bin
15
16@echo off
17rem /j set include search directory
18rem /p pure binary
19rem /k enable if assembler directives
20rem /o enable optimisations
21rem ow+ optimise absolute long addressing
22@echo on
23rem ..\..\util\4dos.com /c ..\asm\dosbox\snasm68k.exe /j ..\..\src\ /p /k %flags% ..\..\src\source.asm,..\..\bin\emu\rom.bin,..\..\bin\emu\rom,..\..\bin\emu\rom
24..\..\util\4dos.com /c ..\asm\dosbox\snasm68k.exe /j ..\..\src\ /p /k %flags% ..\..\src\source.asm,..\..\bin\emu\rom.bin,..\..\bin\emu\rom,..\..\bin\emu\rom > ..\..\logs\emu.log
25
26@echo off
27rem restore the old path
28@echo on
29path %oldpath%
30pause

Unknown Command ..\asm\dosbox\snasm68k.exe

Removing the 4DOS part reverts it back to the truncated path. Any ideas?

Sincerely,

Scorpion Illuminati

Note that Daum is broken and getting old. Also, if this starts dealing more with DOSBox you should be posting in the DOSBox part of the forum.

Osprey wrote:

I think that you'll have to use DOSBox SVN Daum, though, since this doesn't work in official DOSBox and even recent vanilla SVN builds ("echo %var1%" echoes "%var1%", not the contents of the variable). It seems ironic that, for as much as the devs say that SVN Daum is "broken," it gets right a basic DOS feature that their own builds don't.

Contrary to your criticism, inserting environment variables in commands does not work from the prompt in real DOS; it only works in batch files. So in terms of compatibility with DOS, official DOSBox gets it right and Daum does not.

Can't you just CD up the tree a bit before that line, reduce total length?

ripsaw8080 wrote:

Contrary to your criticism, inserting environment variables in commands does not work from the prompt in real DOS; it only works in batch files. So in terms of compatibility with DOS, official DOSBox gets it right and Daum does not.

Huh? Swear I did it all the time in 6.0 through 6.22

ripsaw8080 wrote:

Contrary to your criticism, inserting environment variables in commands does not work from the prompt in real DOS; it only works in batch files. So in terms of compatibility with DOS, official DOSBox gets it right and Daum does not.

That's a bit surprising and I don't have real DOS to confirm, but I was wrong about official DOSBox not supporting it in batch files. I was testing only at the prompt and not in a batch file. I just tested with a batch file and official DOSBox does handle the variables correctly there, which is a big relief.

Scorpion, sorry to lead you off in a wrong direction. You can probably put the Daum version and 4DOS aside, at least for now.

BitWrangler wrote:

Can't you just CD up the tree a bit before that line, reduce total length?

I was about to suggest the same thing. All of those "..\.." are taking up length and could be removed if he just changes his working directory.

Well, if you actually have a use for the feature when typing commands at the prompt, it apparently didn't occur to Microsoft.

BTW, since the OP seems to be compiling something, perhaps adding to the PATH environment variable would remove the need to specify some files on the command line.

Osprey wrote:

That's a bit surprising and I don't have real DOS to confirm, but I was wrong about official DOSBox not supporting it in batch f […]
Show full quote

ripsaw8080 wrote:

Contrary to your criticism, inserting environment variables in commands does not work from the prompt in real DOS; it only works in batch files. So in terms of compatibility with DOS, official DOSBox gets it right and Daum does not.

That's a bit surprising and I don't have real DOS to confirm, but I was wrong about official DOSBox not supporting it in batch files. I was testing only at the prompt and not in a batch file. I just tested with a batch file and official DOSBox does handle the variables correctly there, which is a big relief.

Scorpion, sorry to lead you off in a wrong direction. You can probably put the Daum version and 4DOS aside, at least for now.

BitWrangler wrote:

Can't you just CD up the tree a bit before that line, reduce total length?

I was about to suggest the same thing. All of those "..\.." are taking up length and could be removed if he just changes his working directory.

No worries, was worth a try.

Directory Tree

1c:\foo(root)
2 |
3asm
4|_dosbox
5|_win32
6|
7build
8|_dosbox
9|_win32
10|
11src
12|_assets
13|_framework
14...

Trying to keep everything separate and orderly.

I add the mounted drive to the path at compile-time, so it should technically be available but without the ../../ the assembler complains about not finding the files.

1rem ******************************************************************************************************************************************************************************************
2rem  add to path here
3rem ******************************************************************************************************************************************************************************************
4@echo off
5rem save the old path
6@echo on
7SET oldpath=%path%
8
9@echo off
10rem set the path to the working folder, otherwise compilation will fail
11@echo on
12path c:\;%path%
13
14@echo off
15rem delete old assembled binary if it exists
16@echo on
17if exist ..\..\bin\emu\rom.bin del ..\..\bin\emu\rom.bin
18
19@echo off
20rem /j set include search directory
21rem /p pure binary
22rem /k enable if assembler directives
23rem /o enable optimisations
24rem ow+ optimise absolute long addressing
25@echo on
26set flags=/o op+,os+,ow+,oz+,oaq+,osq+,omq+
27rem ..\..\util\4dos.com /c ..\..\asm\dosbox\snasm68k.exe /j ..\..\src\ /p /k %flags% ..\..\src\source.asm,..\..\bin\emu\rom.bin,..\..\bin\emu\rom,..\..\bin\emu\rom
28rem ..\..\util\4dos.com /c ..\..\asm\dosbox\snasm68k.exe /j ..\..\src\ /p /k %flags% ..\..\src\source.asm,..\..\bin\emu\rom.bin,..\..\bin\emu\rom,..\..\bin\emu\rom > ..\..\logs\emu.log
29..\..\asm\dosbox\snasm68k.exe /j ..\..\src\ /p /k %flags% ..\..\src\source.asm,..\..\bin\emu\rom.bin,..\..\bin\emu\rom,..\..\bin\emu\rom > ..\..\logs\emu.log
30rem ******************************************************************************************************************************************************************************************
31rem remove from path here
32rem ******************************************************************************************************************************************************************************************
33@echo off
34rem restore the old path
35@echo on
36path %oldpath%
37pause

Sincerely,

Scorpion Illuminati

What about simply changing to the root folder?

1c:
2asm\dosbox\snasm68k.exe /j src\ /p /k %flags% src\source.asm,bin\emu\rom.bin,bin\emu\rom,bin\emu\rom > logs\emu.log

...assuming that the folders are also accessible as c:\asm, c:\bin, etc. (not c:\foo\asm, c:\bin\foo, etc.)

Osprey wrote:

What about simply changing to the root folder? […]
Show full quote

What about simply changing to the root folder?

Copy code to clipboard

1c:
2asm\dosbox\snasm68k.exe /j src\ /p /k %flags% src\source.asm,bin\emu\rom.bin,bin\emu\rom,bin\emu\rom > logs\emu.log

...assuming that the folders are also accessible as c:\asm, c:\bin, etc. (not c:\foo\asm, c:\bin\foo, etc.)

Nope

1@echo off
2rem save the old path
3@echo on
4SET oldpath=%path%
5
6@echo off
7rem set the path to the working folder, otherwise compilation will fail
8@echo on
9path c:\;%path%
10
11@echo off
12rem delete old assembled binary if it exists
13@echo on
14if exist ..\..\bin\emu\rom.bin del ..\..\bin\emu\rom.bin
15
16rem go to root folder
17c:
18
19@echo off
20rem /j set include search directory
21rem /p pure binary
22rem /k enable if assembler directives
23rem /o enable optimisations
24rem ow+ optimise absolute long addressing
25@echo on
26set flags=/o op+,os+,ow+,oz+,oaq+,osq+,omq+
27asm\dos\snasm68k.exe /j src\ /p /k %flags% src\source.asm,bin\emu\rom.bin,bin\emu\rom,bin\emu\rom > logs\emu.log
28
29@echo off
30rem restore the old path
31@echo on
32path %oldpath%
33pause

Sincerely,

Scorpion Illuminati

I meant for you to run the snasm68k.exe line from the root of C:\. Since you're doing it in a batch file, do:

1cd c:\
2asm\dosbox\snasm68k.exe /j src\ /p /k %flags% src\source.asm,bin\emu\rom.bin,bin\emu\rom,bin\emu\rom > logs\emu.log

in your errormessages, there appears to be mostly file not found messages (either the compiler itself, or the files used by it), are you certain that your mount commands are correct (and your includes for your compiler) ?

There is a known bug in dosbox which affects long locations, (in that we check the length before resolving the ..\ ) but then we are talking about a length of 1 element being over 120 characters or so. I doubt that that is happening here. The files not found are

1Warning : Could not open list file '..\..\bin\'

Are nowhere near that length, so my guess is that you might have setup the mounts/includes directories/paths incorrectly. Can you double check those ?
Alternatively, you can download the debug version of DOSBox and look which files are actually being opened (because the errormessage might be wrong)

Let me move the thread to the dosbox section
*moved*

isn't it ms-dos limiation on Program Segment Prefix, that it can only accept max 127 characters as parmeters?
So most decent compilers would usually work around it by using a text file as replacement for its lenghty parameters option?

Yes, 127 characters is the DOS limit. Compilers can avoid lengthy command lines by setting up a PATH= environment variable that lists all directories containing files that compilation might need.

It seems that DJGPP environment has some hacks that allow passing long command lines from one DJGPP program to another.
http://www.delorie.com/djgpp/v2faq/faq16_4.html