donnerkuh Posted December 22, 2010 Share Posted December 22, 2010 hi. i used batari basic and crimson editor for 2 years without problems. but now, i have to install new. my problem is now: if i try to compile, following error appears: ---------- Capture Output ---------- > "C:\BB\2600bas.bat" C:\BB\1944.bas "bB=c:\BB" kann syntaktisch an dieser Stelle nicht verarbeitet werden. > Terminated with exit code 255. can somebody help? Quote Link to comment Share on other sites More sharing options...
jwierer Posted December 22, 2010 Share Posted December 22, 2010 hi. i used batari basic and crimson editor for 2 years without problems. but now, i have to install new. my problem is now: if i try to compile, following error appears: ---------- Capture Output ---------- > "C:\BB\2600bas.bat" C:\BB\1944.bas "bB=c:\BB" kann syntaktisch an dieser Stelle nicht verarbeitet werden. > Terminated with exit code 255. can somebody help? Looks like you have the environment variable set, but is the path also correct? From commandline type path and make sure c:\BB is included. -Jeff Quote Link to comment Share on other sites More sharing options...
donnerkuh Posted December 24, 2010 Author Share Posted December 24, 2010 thx for your help, problem fixed. now i have this feedback: ---------- Capture Output ---------- > "C:\BB\2600bas.bat" C:\BB\samples\zombie_chase.bas DASM V2.20.07, Macro Assembler ©1988-2003 redistributable for non-profit only DASM sourcefile [options] -f# output format -oname output file -lname list file -Lname list file, containing all passes -sname symbol dump -v# verboseness -t# Symbol Table sorting preference (#1 = by address. default #0 = alphabetic) -Dname=exp define label -Mname=exp define label as in EQM -Idir search directory for include and incbin -p# max number of passes -P# max number of passes, with less checks Fatal assembly error: Check command-line format. > Terminated with exit code 0. ------------------------------------------------- will i have to edit the 2600bas.bat? i have no idea Quote Link to comment Share on other sites More sharing options...
SeaGtGruff Posted December 24, 2010 Share Posted December 24, 2010 (edited) will i have to edit the 2600bas.bat? It looks like there's a problem with the DASM command line. I know of two possible reasons: (1) Maybe you have a space inside the name of a directory or file? (2) Maybe there's a problem with the way the DASM command line is typed in the batch file? If it's case 1, you can fix it by adding quotation marks in the Crimson Editor tool that calls the compile batch. I checked my setup, and the only quotation marks I have in the compile tool are in the Argument field, as follows: Argument: "$(FilePath)" If it's case #2, you can fix it by editing the batch file. This problem is discussed in another thread, so you might want to search for that thread for a complete description, but following are two problems I can see within the default batch file: (1) Wherever you see a greater than (>), less than (<), or pipe (|) in the batch file, make sure there's a space on both sides of it. (2) Wherever you see a slash, make sure to change it to a backslash *if* the slash is supposed to be part of a directory path-- e.g., -I%bB%/includes should be -I%bB%\includes. Of course, it could be something else causing the problem. The only way to be sure what the problem is would be to edit the batch file (2600bas.bat) and temporarily remove the first line (@echo off), or else temporarily change it to say @echo on. Then you should be able to see what the DASM command line looks like when you're compiling, to help you figure out what's wrong with it. Michael Edit: With regard to the slash and backslash, it should be noted that this refers to using the 2600bas.bat file in a *Windows* environment, because Windows uses backslashes in directory paths, whereas Unix uses slashes in directory paths. Edited December 24, 2010 by SeaGtGruff Quote Link to comment Share on other sites More sharing options...
donnerkuh Posted December 25, 2010 Author Share Posted December 25, 2010 thank you for your tips. now, this is the result. i think it is not a big thing, just a little bug somewhere (?). i don´t see it ---------- Capture Output ---------- > "C:\BB\2600bas.bat" C:\BB\1944.bas C:\BB>if Xc:\BB == X goto nobb C:\BB>if exist sed.exe goto havesed C:\BB>preprocess 0<C:\BB\1944.bas | 2600basic.exe -i c:\BB 1>bB.asm batari Basic v1.01 ©2005-2007 (219) Warning: long line 2600 Basic compilation complete. C:\BB>if errorlevel 1 goto bBerror C:\BB>if X == X-O goto optimize C:\BB>postprocess -i c:\BB 1>C:\BB\1944.bas.asm C:\BB>goto nooptimize C:\BB>dasm C:\BB\1944.bas.asm -I c:\BB\includes -f3 -o C:\BB\1944.bas.bin | sed "/Label mismatch/d" | sed "/shakescreen /d; /rand16 /d;/debugscore/d;/pfscore/d;/noscore/d;/vblank_bB_code/d;/PFcolorandheight/d;/pfrowheight/d;/pfres/d;/PFmaskvalue/d;/overscan_time/d;/vblank_time/d;/no_blank_lines/d;/superchip/d;/ROM2k/d;/NO_ILLEGAL_OPCODES/d;/minikernel/d;/debugcycles/d;/mincycles/d;/legacy/d;/PFcolors/d;/playercolors/d;/player1colors/d;/backgroundchange/d;/readpaddle/d;/multisprite/d;/PFheights/d;/bankswitch/d;/Unresolved Symbols/d" | sed "2,/-->/!{ /-->/,/-->/d; }" | sed "s/--> 0./Possible duplicate label: /" DASM V2.20.07, Macro Assembler ©1988-2003 redistributable for non-profit only DASM sourcefile [options] -f# output format -oname output file -lname list file -Lname list file, containing all passes -sname symbol dump -v# verboseness -t# Symbol Table sorting preference (#1 = by address. default #0 = alphabetic) -Dname=exp define label -Mname=exp define label as in EQM -Idir search directory for include and incbin -p# max number of passes -P# max number of passes, with less checks Fatal assembly error: Check command-line format. C:\BB>rem yes, I know This is the first attempt to make DASM's output more useful! C:\BB>goto end > Terminated with exit code Quote Link to comment Share on other sites More sharing options...
SeaGtGruff Posted December 26, 2010 Share Posted December 26, 2010 C:\BB>dasm C:\BB\1944.bas.asm -I c:\BB\includes -f3 -o C:\BB\1944.bas.bin | sed "/Label mismatch/d" | sed "/shakescreen /d; /rand16 /d;/debugscore/d;/pfscore/d;/noscore/d;/vblank_bB_code/d;/PFcolorandheight/d;/pfrowheight/d;/pfres/d;/PFmaskvalue/d;/overscan_time/d;/vblank_time/d;/no_blank_lines/d;/superchip/d;/ROM2k/d;/NO_ILLEGAL_OPCODES/d;/minikernel/d;/debugcycles/d;/mincycles/d;/legacy/d;/PFcolors/d;/playercolors/d;/player1colors/d;/backgroundchange/d;/readpaddle/d;/multisprite/d;/PFheights/d;/bankswitch/d;/Unresolved Symbols/d" | sed "2,/-->/!{ /-->/,/-->/d; }" | sed "s/--> 0./Possible duplicate label: /" It looks like there are some spaces there that should *not* be there: -I c:\BB\includes Take out the space that's right after the -I. -o C:\BB\1944.bas.bin Take out the space that's right after the -o. I think that should fix the problem. Michael 2 Quote Link to comment Share on other sites More sharing options...
donnerkuh Posted December 26, 2010 Author Share Posted December 26, 2010 you are the godfather of 8-bit technology. now it works. if my new game idea is playable, you will get it first. thank you thank you thank you 1 Quote Link to comment Share on other sites More sharing options...
SeaGtGruff Posted December 26, 2010 Share Posted December 26, 2010 I'm glad it's working now! Michael Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.