Need help with bB -- problems compiling after installation / Tutorial

[jwierer]

I really appreciate the time you spent verifying these steps for me RT. I followed your aforementioned instructions from start to finish, but the same thing still happens when I compile zombie_chase.bas or any .bas for that matter. It comes up with the same message every single time.

 

I guess I’ll take it for what it is and give it a rest for now. Thank you to everyone for their help!

If you just go to your bB folder and type 2600bas <path of .bas file> what happens?

 

-Jeff

[STGuy1040]

I really appreciate the time you spent verifying these steps for me RT. I followed your aforementioned instructions from start to finish, but the same thing still happens when I compile zombie_chase.bas or any .bas for that matter. It comes up with the same message every single time.

 

I guess I’ll take it for what it is and give it a rest for now. Thank you to everyone for their help!

If you just go to your bB folder and type 2600bas <path of .bas file> what happens?

 

-Jeff

 

I get the following message:

 

Cannot open default.inc for reading

Compilation failed

[SeaGtGruff]

I really appreciate the time you spent verifying these steps for me RT. I followed your aforementioned instructions from start to finish, but the same thing still happens when I compile zombie_chase.bas or any .bas for that matter. It comes up with the same message every single time.

 

I guess I’ll take it for what it is and give it a rest for now. Thank you to everyone for their help!

If you just go to your bB folder and type 2600bas <path of .bas file> what happens?

 

-Jeff

 

I get the following message:

 

Cannot open default.inc for reading

Compilation failed

That means it can't find the include files. How (where) do you have everything installed-- what are all the directory names and subdirectory names?

 

Michael

[STGuy1040]

I really appreciate the time you spent verifying these steps for me RT. I followed your aforementioned instructions from start to finish, but the same thing still happens when I compile zombie_chase.bas or any .bas for that matter. It comes up with the same message every single time.

 

I guess I’ll take it for what it is and give it a rest for now. Thank you to everyone for their help!

If you just go to your bB folder and type 2600bas <path of .bas file> what happens?

 

-Jeff

 

I get the following message:

 

Cannot open default.inc for reading

Compilation failed

That means it can't find the include files. How (where) do you have everything installed-- what are all the directory names and subdirectory names?

 

Michael

 

 

I bet that is where I went wrong.

 

Here's a picture of everything:

 

[+Random Terrain]

Now there's a difference. I need to edit my post about what I did. I made a VbB folder in the atari2600 folder and unzipped the VbB zip file in there. I did not put it in the same folder with bB. I wonder if that makes a difference?

[SeaGtGruff]

Now there's a difference. I need to edit my post about what I did. I made a VbB folder in the atari2600 folder and unzipped the VbB zip file in there. I did not put it in the same folder with bB. I wonder if that makes a difference?

It shouldn't.

 

Michael

[SeaGtGruff]

I bet that is where I went wrong.

No, I don't think so. I noticed your .bat file is different than mine-- you're using the one from 02/09/2008that was posted in this thread, right?-- so I checked that file, and I think it has some stuff in it that might not be 100% kosher in Windows. I'm attaching a copy of the .bat file that I use, which has been edited a little bit from the original. Some of the changes are just spacing differences for what I think is improved readability, which should make no difference in how it runs. The changes that *can* make a difference to Windows are where I changed some forward slashes to backslashes, such as here:

 

if exist %bB%/sed.exe goto havesed

That's correct in Unix, but in Windows the slash should be a backslash:

 

if exist %bB%\sed.exe goto havesed

Likewise

 

dasm %1.asm -I%bB%/includes -f3 -o%1.bin

should be

 

dasm %1.asm -I%bB%\includes -f3 -o%1.bin

I've also added spaces around certain character sequences that gave me trouble under Windows 95, although I think they worked okay under Windows XP:

 

preprocess <%1 | 2600basic.exe -i %bB%>bB.asm

As I recall, Windows 95 tended to flake out a bit if the < and > redirectors didn't have any spaces around them, as if it had trouble recognizing and interpreting them properly, so I just made sure to put spaces around them:

 

preprocess < %1 | 2600basic.exe -i %bB% > bB.asm

Aside from the changes described above, I also added the "set bB" and "set path" statements inside the .bat file, because some people were having trouble setting them outside the .bat file. Anyone who uses my .bat file should modify the "set bB" statement to fit their particular directory setup.

 

And finally, I added the "-l" switch (lowercase L) to the dasm.exe command line, to generate an assembly listing.

 

Try unzipping my .bat file into your C:\Atari2600\bB directory and see if it helps.

 

Michael

2600bas_mikes.zip

[STGuy1040]

I bet that is where I went wrong.

No, I don't think so. I noticed your .bat file is different than mine-- you're using the one from 02/09/2008that was posted in this thread, right?-- so I checked that file, and I think it has some stuff in it that might not be 100% kosher in Windows. I'm attaching a copy of the .bat file that I use, which has been edited a little bit from the original. Some of the changes are just spacing differences for what I think is improved readability, which should make no difference in how it runs. The changes that *can* make a difference to Windows are where I changed some forward slashes to backslashes, such as here:

 

if exist %bB%/sed.exe goto havesed

That's correct in Unix, but in Windows the slash should be a backslash:

 

if exist %bB%\sed.exe goto havesed

Likewise

 

dasm %1.asm -I%bB%/includes -f3 -o%1.bin

should be

 

dasm %1.asm -I%bB%\includes -f3 -o%1.bin

I've also added spaces around certain character sequences that gave me trouble under Windows 95, although I think they worked okay under Windows XP:

 

preprocess <%1 | 2600basic.exe -i %bB%>bB.asm

As I recall, Windows 95 tended to flake out a bit if the < and > redirectors didn't have any spaces around them, as if it had trouble recognizing and interpreting them properly, so I just made sure to put spaces around them:

 

preprocess < %1 | 2600basic.exe -i %bB% > bB.asm

Aside from the changes described above, I also added the "set bB" and "set path" statements inside the .bat file, because some people were having trouble setting them outside the .bat file. Anyone who uses my .bat file should modify the "set bB" statement to fit their particular directory setup.

 

And finally, I added the "-l" switch (lowercase L) to the dasm.exe command line, to generate an assembly listing.

 

Try unzipping my .bat file into your C:\Atari2600\bB directory and see if it helps.

 

Michael

 

 

Hell yeah! You solved my problems! I'd hug you but I think buying you a cold one would be better received!

[+Random Terrain]

Good to see that it wasn't Gremlins.

 

So is it OK to add that .bat file to the Updated bB Files to Download?

[SeaGtGruff]

Hell yeah! You solved my problems!

I'm glad it's working now!

 

Michael

[SeaGtGruff]

So is it OK to add that .bat file to the Updated bB Files to Download?

I'd say you should probably remove the "set bB" and "set path" statements, and probably take out the "-l" parameters as well, so it will be more generic. And it's okay for Windows users, but the original version with the forward slashes is what Unix or Linux users should be using.

 

Michael

[+Random Terrain]

So is it OK to add that .bat file to the Updated bB Files to Download?

I'd say you should probably remove the "set bB" and "set path" statements, and probably take out the "-l" parameters as well, so it will be more generic. And it's okay for Windows users, but the original version with the forward slashes is what Unix or Linux users should be using.

Thanks. I'll do that later tonight. On a different subject, have you seen this post yet:

 

http://www.atariage.com/forums/index.php?s...t&p=1612952

[SeaGtGruff]

On a different subject, have you seen this post yet:

 

http://www.atariage.com/forums/index.php?s...t&p=1612952

Yes, I have. (What's the smiley for "embarrased, sheepish grin"?) Adding the inventory strip to v1.0 ought to be easy, and I should have done it already. But the title screen thing would be more involved. Someone already did something like that a year or two ago, but I was thinking more along the lines of an include file that could be used in a program if desired. I'm sort of letting it roll around in my head to see what ideas I come up with for it-- preferably something that fits in with bB's canned kernels with a minimum of muss and fuss.

 

Michael

[+Random Terrain]

On a different subject, have you seen this post yet:

 

http://www.atariage.com/forums/index.php?s...t&p=1612952

Yes, I have. (What's the smiley for "embarrased, sheepish grin"?) Adding the inventory strip to v1.0 ought to be easy, and I should have done it already. But the title screen thing would be more involved. Someone already did something like that a year or two ago, but I was thinking more along the lines of an include file that could be used in a program if desired. I'm sort of letting it roll around in my head to see what ideas I come up with for it-- preferably something that fits in with bB's canned kernels with a minimum of muss and fuss.

The only title screen related thing I have seen was just a Superchip RAM hi-res screen that wasn't as useful as your ideas for game title screens with a much bigger title in the center of the screen, additional lines for things like the copyright message, or "press fire to begin," or the game difficulty level picker which would hopefully work with all modes instead of just Superchip RAM. I know you'll think of the best way to make it happen. Once you figure it out, I bet a lot of bB users will be doing a happy dance.