jwierer

---------- Capture Output ---------- > "C:\Atari2600\bB\2600bas.bat" D:\bBProjects\Undecided2\default.bas batari Basic v1.01 ©2005-2007 (134): Error: Unknown keyword: B Compilation failed. > Terminated with exit code 0. In testing with other codes that use include div_mul.asm, the latest 2600basic.exe seems to occasionally fail on my machine? When I revert to the compiler dated 12.6.2009 it works just fine. I tested this outside of VisualbB to make sure it was't an issue of something I was doing there. I would PM Batari your source so he can debug it during compilation. EDIT: In testing more sometimes 2600basic.exe simply crashes, other times is displays the following: batari Basic v1.01 (C)2005-2007 (586): extraneous end statement found (595): Error: Unknown keyword: 2☺ -Jeff

I updated those last week. -Jeff

You have to make sure you're using the other latest 32 bit binaries. If you're using the original 16-bit versions it won't work. You can grab copy of my working Win7 64-bit bB folder here. -Jeff

Galactic Chase, a Galaga clone, was converted for the 5200. For some reason I can't find the link online, but this is what it looks like. EDIT: Sorry I am thinking of Galaxian. (slow start to the brain this morning) -Jeff

Nice. How about fixing the horrible colors in Ms. Pacman? -Jeff

You can download Crystal Castles & Donkey Kong here, and Stargate here for the 5200. All hosted here at AtariAge. EDIT: There is a thread of most conversions here -Jeff

Have you looked at this section yet: http://www.randomter...l#kerneloptions Another trick in vbB that you can use is from the Project Explorer, switch to commands. Expand Compile Directives->Kernel Options. From there you can double click or drag any of the valid kernel options to the top of your code. Only valid options are provided in the list. -Jeff

It's only dark red if using PAL. My guess is your emulator is set to NTSC which would be purple. -Jeff

How do I set the kernel options? Putting that string of code you said gives an error. Did you remember the space before "set"? Posting the .bas would be easier to fix. -Jeff

playerXXXcolor: and playerXXX: should be player0color/player0 or player1color/player1. Also you need to make sure your kernel options are set. " set kernel_options playercolors player1colors pfcolors" What I recommend you do is open the file folder using Windows explorer, then right click preview on the sprite. What that does in the background is vbB creates and compiles a temporary .bas file <spritename>_preview.bas. You can look at the source of that file for a proper way to display and move a sprite. Be careful because after you close the emulator it cleans up those files. -Jeff

I was going to suggest turning off Windows 7 Aero (aka glass) effect. If you don't have the correct video drivers, or your machine simply can't handle it, you'll get display garbage like you're seeing. -Jeff If I can play crysis with DX10, I can display a .net app . That only proves it can run the APIs in use. Windows forms don't leverage DirectX, or at least I can confirm I don't use DX. -Jeff

Can you right click on any of your sprites/playfields and preview in emulator? If that doesn't work then most likely you doing have the bB compiler installed correctly. Most folks forget to either enable the environment variables. The bB readme describes this. Also, if I recall bB doesn't handle spaces in directory names very well. for that reason I always create a directory structure without spaces. A screenshot of your settings tab, and copy of your program file (.bas) might also help troubleshoot. -Jeff

If you have a "good" image you can take it into the image converter and work some magic. This looks like a compressed jpeg and that's not going to work very well because the best way is to convert to black and white and a compressed image won't have consistent colors throughout. Honestly with a sprite, it's so small it would be faster to recerate by hand. -Jeff

I was going to suggest turning off Windows 7 Aero (aka glass) effect. If you don't have the correct video drivers, or your machine simply can't handle it, you'll get display garbage like you're seeing. -Jeff

Great! Did you have to update your bB files as well? Up until last week I didn't realize I was still using 16-bit copies of preprocess, postprocess, and optimize that wouldn't load in 64-bit Windows. Batari gave me the updated ones last week so I figured I'd share the wealth. -Jeff

Check and see if you have the same problem with the previous release. At least that narrows it down to the current build. It looks more like a general problem with Windows explorer. -Jeff

I've compiled a number of updates and fixes over the last couple of months. For all the new technology adopters, I think I finally have everything you need to get this working well under Windows 7 64-bit. You can download from the first post. Because AA limits 2MB uploads you'll need to download both files and unzip it to the same folder. New Features Build tool strip menu button remembers if you used the standard or alternate batch file for compiling Allows reordering of results and projects tab Better cleanup of previous compilation errors after a successful compile Active project tab is colored Startup and Settings tabs are colored bB reference guide defaults to online copy if internet is available vbB now warns you if you have unsaved changes before compiling Support for DATA and SDATA in music editor End data for music editor simplified to "255" Channel 1 is displayed when using 2 voices in music editor Music editor allows you to select if you want to cleanup (delete) test music binaries ImgToCode.exe now allows you to right-click Convert to Assembly so if you create a playfield, edit it and convert to assembly. Right click Save Snapshot for playfields/Sprites Added Setting for associating .bas, .pla, and .spr files with VisualbB. Double clicking any file will launch in vbB Added a pause button to the music and sound editor Image Converter (ImgToCode) now supports the Title Kernel Added new context menu item for code editor allowing you to highlight a term and seach for next instance or jump to code where a label is defined Bug Fixes Now Works under Windows 64-bit editions (see upgrade info) When using a shortcut to run visualbB.exe some menu items didn't appear Using File-Open would crash vbb if a project was not selected "Test" bins were not being deleted in the music editor When in the settings tab, hitting backspace while typing in the compiler field crashes VbB When you try to set playercolor or playfield color the dialog always said background Removed dependency on gif.components.dll Save as GIF in sprite animater fails if run from shortcut When REGION is changed the color palette is applied to all open sprites/playfields when dragging sprites from from project explorer it will always use the latest even if not saved. Identified registry issue for those not able to use the playfield/sprite editors. This was due to a bad registry setting (see this thread) Upgrading for 64-bit Windows If you are running on a Windows 64-bit operating system and you have settings that you like, you should migrate them before upgrading. Note this is a one time step. Run your CURRENT version of visualbB and go to file->export settings Edit the resulting .reg file and replace instances of HKEY_LOCAL_MACHINE\SOFTWARE\VisualbB with HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VisualbB Double click the .reg file to import it into the registry, just say yes when it asks you if you want to do this. Replace your vbb files with updated version I've also included a copy of my bB folder that includes all 32-bit binaries for the compiler. -Jeff

That will be fixed in the next update.

No plans for Linux support. Probably won't work under wine unless it now supports the .net framework. -Jeff

I think some early adopters of bB avoided using space as 2600IDE was limited to reading files less than 32K. That's no longer an issue with vbB, but old habits die hard. -Jeff

Over the last couple years I've been making small tweaks and fixes. Featurewise you can now go back in a search as well as the ability to search compare results. Also there was a bit of an annoying bug where the emulator paths couldn't have spaces. I haven't heard any reports of other issues so here is the latest I have on my machine. HOM3.0.3.2.zip -Jeff

I use the Pocket Programmer http://secure.transtronics.com/osc/product_info.php/cPath/55/products_id/621 I have the older parallel port version hooked up to an older PC, but it has worked fine with older 2732s for years. They are more expensive ($249), but easy to use. I got mine off eBay for about half the price. There might be older parallel port versions for cheaper if you still have a PC that support it. -Jeff

If you have a hotmail account you have access to 25GB of free storage on skydrive.live.com. I drag all my source code there after making any changes. -Jeff

Sure. Added it to my original post. -Jeff

I attempted to do just that, but the maze hieght isn't the same to get it exactly. This is pretty close. To try it, just play regular pacman. paccol_pokey_v8_protoMaze.bin paccol_pokey_v8_protomaze.a78 -Jeff