Vim syntax highlighting for Atasm

[Vim syntax highlighting for Atasm]

See subject. Put m65.vim in $HOME/.vim/syntax (create the directory if necessary) and add the following to your .vimrc file

 

augroup filetype
au! BufRead,BufNewFile *.m65	 set filetype=m65
augroup END

m65.vim.zip

[Turn off Overscan in Altirra 2.10]

I guess it all depends a lot on the kind of TV you used to use in the past. Our B/W TV cut off a lot more than our colour TV later in life. Both were unable to display the left side of the screen though. My current colour TV has the same problem. If I set the left margin to zero, the cursor in text mode is not visible. That's the reason why I have been experimenting with an ATTiny chip to delay the SYNC signal by a little less than one scanline to have the display more centered.

 

But most of the time I have my 800XL hooked up to a 'bttv' capture card, which has no problems displaying everything that's in the video signal, including annoying blinking pixels way out left or right of the usual display (Bruce Lee has that for example). So, I added a (software) crop filter to get rid of that

[Here <== DOS 2.5 source]

Oh well, here is DUP.SYS converted to assemble with atasm 1.07

dup.zip

[Feelings and join to everyone:]

I am tempted to jump into this discussion, but I won't. IMHO it's best to leave religion and politics out of this forum. General Chat might be an option, but I suppose there are better places on the internet to have such discussions.

[SIC! Cart conversions]

Option 'B' return to cart/basic will return to Turbo basic if previously loaded and not corrupt.

 

I don't think we need a new cart for that. I looked into it and it's just a small patch to make 'B' do the same as 'M' 2080. You can just put his DUP.SYS on your working disk and write MEM.SAV. After that, if you go to DOS from the cart's Turbo Basic, that particular DUP will be read. You can also use an unmodified DUP and do M 2080 to return to Turbo Basic.

[SIC! Cart conversions]

I'll have a look at it if I have some time this coming weekend. Could you tell me what this enhancement is exactly?

 

Regards,

[SIC! Cart conversions]

Yes, a larger cart is no problem. It just flashes the first 16 banks and then quits. I only have 512kB here, too.

 

For saving files, you need an empty DOS 2.5 floppy. If you do not want to reset your computer to start the DUP, you can put DUP.SYS on it and if you want to be able to link multiple programs without resetting the computer (which means power-cycling if you do not have a reset button on your cart) you can put RUNTIME2.EXE on it as well.

 

Personally, I prefer resetting and running DUP from cart. It's also faster.

[SIC! Cart conversions]

Here's a complete Turbo Basic development cart. It includes the following:

 

DOS 2.5

Turbo Basic XL 1.5

Turbo Basic XL Compiler 1.1

Turbo Basic XL Runtime

Turbo Basic XL Linker

 

The linker includes RUNTIME2.EXE, but only for a in single link "session". Also, do not forget to press ESC after linking, otherwise the file doesn't get closed.

 

If you just want to flash your SIC! cart with this, you need ...-atr.zip

If you want to use the binaries for, say, a MaxFlash cart, you need ...-binaries.zip

If you want to see how it's done or change/fix things, you need ...-sources.zip

 

Regards,

Ivo

turbo_basic_sic_cart-atr.zip

turbo_basic_sic_cart-binaries.zip

turbo_basic_sic_cart-source.zip

[SIC! Cart conversions]

Turbo Basic Compiler

 

BTW I noticed that data/sicmenu.obx that is distributed with sicmenu 0.61a does not work correctly. It crashes loading the compiler. If I assemble my own (mads sicmenu.asm) and use that one to build the cart image, everything works fine. (sicmenu 0.60a source code)

 

Right now I have a cart with DOS 2.5, TB and its compiler. Isn't that what you want/mean Marius?

 

Edit: I also notice that the 0.60a sicmenu loader is waaay faster than the 0.61a that I used to use before.

turboc.xex

turboc-source.zip

[SIC! Cart conversions]

No. Turbo Basic is an application that runs partly from main RAM and large parts of the RAM under the OS ROM. There's no way it'll fit in 8kB, not even with compression. Code generally does not compress very well.

 

BTW The above does not turn a SIC cart into an instant Turbo Basic. It's just an exe file that can be loaded from a sicmenu, or any other $700-based loader for that matter. It's pretty fast though and IMHO it's cleaner than Nir Dary's (sp?) conversion.

 

On-topic again:

 

Any interest in a conversion of the Turbo Basic compiler, too?

[SIC! Cart conversions]

DOS 2.5

sicdos25.xex

sicdos25.zip

[SIC! Cart conversions]

Here's a conversion of Turbo Basic XL.

turbosic.xex

turbosic-source.zip

[64 columns screen driver?]

Thanks Claus! Was an interesting read.

[64 columns screen driver?]

I have source code with a couple of my 80 column handlers here: http://atari.kenscla...8utilities.html

Was going to double check for sure source code is included as I have listed but don't have an unarc utility handy at the moment.

 

Thanks! Now I am confused. The flash80 documentation in CharlieChaplin's zip-file says it's Bill Kendricks. It seems to be the same code as yours, and yours include source code. I assume it was you who wrote it then?

[64 columns screen driver?]

Thanks! Looks like Bill Kendrick's flash80.com is the fastest w/ 1200-1400 characters per second.

[Expanded memory]

@Claus, thanks! I remember reading that article a while ago but totally forgot about it.

 

@Rybags, I agree that more memory mapping schemes might be inconvenient, but I suppose having two expansions side by side would not be such a problem, i.e. traditional portb $4000-7fff and another expansion for the lower 16kB

[64 columns screen driver?]

Thanks! I'll have a look at it. Any source available? And what about its speed, i.e. characters per second and memory usage?

[Some Early Atari A8 Development Docs...]

Thanks!

[Expanded memory]

Hi,

 

Did anyone ever consider expanding the memory in such a way that one can switch 32kB banks, starting from $0000. Having a different stack and zero page would be very nice for a multitasking OS. Another possibility might be a small circuit that remaps $00xx and/or $01xx to any other page, selected by two 8-bit latches somewhere in the hardware area.

 

Regards,

[64 columns screen driver?]

Hi,

 

I was wondering if there's any code floating around that implements a 64 column text mode in graphics 8? If not I'm considering to implement a 64x30 vt100 console.

 

Regards,

[Suggestions for 8-Mb Utility Flash Cartridge?]

You might want to take a look at how I combined Atmas II and DOS.SYS in a single executable:

 

http://www.atariage.com/forums/topic/204330-sic-cart-conversions/

 

It would be a waste of space though if you had to duplicate this for a lot of utilities.

[SIC! 31 in 1 cartridge]

Hi,

 

Here's a way to store 31 cartridges in one SIC! cart.

 

sic31in1.zip contains an example cartridge image.

 

sic31in1-source.zip contains all source material so anybody can build their one custom cart.

 

Cartridge images need to be 16kB or 8kB. The 8kB ones need to be padded with zeroes up to 16kB.

Next you can edit sic.m65 to match the right names and bank selection bytes. These range from $01 to $1f, add $20 for 16kB roms.

Next, assemble with atasm -r sic.m65

To build the final SIC! rom, concatenate empty8k.rom, sic.bin and all rom images.

On Linux you can simply use cat and I believe window's cmd.exe has copy /b file + file + file dest

 

Regards,

Ivo

 

 

Edit: all code can be used freely in case somebody wants to make a GUI based ROM builder. Also, use OPTION/SELECT to select the game you want, press START to run.

sic31in1.zip

sic31in1-source.zip

[AspeQt: Yet another SIO2PC/APE clone]

You should seriously consider why you are having trouble finding a paying day job...... Nough said!...

 

That's low and uncalled for. Have you seen post #428? It seems you are constantly one or two posts behind what fjc said.

[Here <== DOS 2.5 source]

I adjusted pathnames in FMS.m65, replaced labels starting with ':' and fixed @ORG and @ERROR macros to work with atasm.

 

In addition to that, I also changed an occurrence of DFDFL1+FILDIR to FILDIR+DFDFL1 because of a bug in atasm. atasm thinks you are addressing page zero (DFDFL1 = 0) and then segfaults during the second pass.

 

Just added this information in case somebody decides to convert DUP.SYS and stumbles upon a similar problem.

[AspeQt: Yet another SIO2PC/APE clone]

None at all. The QT build I installed was enormous, and I'm a complete noob at using it.

 

You probably installed a version with debug symbols, et cetera, and/or are compiling with debug information.