gs80065xe

The crew at the Antic podcast says these work very well. https://www.retrotink.com/product-page/2x-mini https://ataripodcast.libsyn.com/antic-episode-74-name-wars

I refactored the program to take advantage of FastBasic's built in PMGraphics functions. I didn't have to do the special test on row 21 for the collision test. And using MSET and MOVE are very fast at making vertical changes. Negating the need for the machine language routine. Thanks again for the help.

Thanks. It's mostly working now. Collision detection is a little weird. Watching the value displayed once P0 collides with the playfield's text, changes to 1 instead of 4. So changed the repeat to check 53252 = 1. But it stops when y=21 because it changes to 1 there. So changed the repeat to 53252=1 and y>21. And it works fine. Don't understand why it is set to 1 after the first loop. But is 0 for all the rest. I know FastBasic offers PM support. But, I'm trying to learn two languages at the same time. Assembly from an old assembly book which has examples in Atari Basic. And FastBasic by converting Atari Basic programs to FastBasic. I chose to not use the PM features in FastBasic because they won't be available in Assembly.

SKR, I was reading the hex values in memory using Altira's debugger. TGB1718, thanks for the help. I added the PLA back to the beginning. Your Data statements are the same as what's in the book. But it still hangs. I've attached my FastBasic program. I ported it from Atari basic. Tried the program in Atari Basic as it is in the book, and it works. Not sure what I've done wrong. collision.atr

I'm trying an example program testing PM Collisions. The program has a machine language routine it calls to speed up moving the player vertically. But it isn't working for me. And I still don't have a good grasp of assembly to under stand why. One thing I noticed is the book had two PLA statements at the start of the routine. That caused the program to hang. Removing one of them stops it from hanging. But the player doesn't appear to move. In fact I don't see the player at all. The line it is called on is st=usr(adr(dli),pb+512+y) DLI HEX: 68,68,85,cc,68,85,85,cb,a0,14,b1,cb,c8,91,cb,88,88,c0,ff,d0,f5,60

Well, it worked fine this time for both FB and FBI. Thought maybe TD Line being on caused the problem the yesterday. But it works as well. At this point, I don't know what I did wrong yesterday. But it works now. Thanks.

Hmmmm. I did try it before posting. It went crazy for me when I loaded FastBasic. And the editor was all wrong. But I was running it in Altirra. And it was running the integer only version. I'll try again.

Does anyone know if there is an option in FastBasic to make it work with the SDX con64 display driver?

Thanks for the help everyone.

Sorry. Didn't take time to research what you meant by relocatable. Just wanted to test the program.

Thanks. That got it to work. By the way, the new handler appears to cause a conflict which stops FastBasic from loading.

I just tried both programs in Atari Basic. The second gives error 136. The first just a black screen. I booted from the n-handler disk from irattaonline. FujiNet is running the latest firmware. The disk’s DumbTerm basic program worked. Are you two using something that hasn’t been released yet?

Thanks. I found out why it was flickering. It only occurs if I have SpartaDOS X with TD ON. I turn it off and it works fine.

Some more information. This is running on latest Altirra using xl/Xe os and Basic roms. And Rambo 256k to simulate my real hardware. I rewrote the program with Atari basic. Same results. Except reset resulted in losing the program. I noticed the exercise mentions it is more for the 400/800 and basic rev a which lacked an antic mode 14 graphics object. Changed Altirra to mimic an 800 with the Atari rev cart. Loaded the basic program and get a black screen without flickering. But Altirra crashed when I reset to exit the program.

Atari Assembly Language Programmer's Guide by Allan Moose and Marian Lorenz Publisher is Weber.

Still early in the book. But the author is trying to do some things starting in Basic. He assumes the readers will be familiar with it. And I assume later he will show it in Assembly. But I haven't gotten that far because I'm trying to get my display list working for the last day or two. I know there are Display list methods in FastBasic. But the author wants the reader to manually create the Display List because you'll need to do the same thing in Assembly.

I'm studying Assembly language and am currently on Display Lists. The author has an exercise to create an Antic mode 14 display list from scratch. Using what I've learned I created a program in FastBasic. The program is on the attached atr file. But it appears when the program is run, the screen goes blank and there are pixelated artifacts flashing on the screen. Almost like the display list and or screen ram are in a location being used by another program. The flashing continues after I stop the program execution. But now there are characters flashing. I have to do a warm reset to get the display back to normal. I tried to keep it simple. So I'm currently being wasteful with RAM. But the exercise is to focus on creating the display list. Any ideas? Thanks. dlist.atr

Thanks. That’s the behavior I observed. Since it only affects printing then I guess it’s OK. I’ve been spoiled by modern tech. No used to these tight constraints.

I’m converting an Atari Basic display list dump program to FastBasic. But the display list starts at the edge of the 16bit integer maximum limit. So many of the addresses are overflowing When using variables. I’ve tried using float variables. But peek and dpeek doesn’t accept them. I get a parser error. Is there a way to only use positive integer variables with values 0 to 65535?

What is the aux2 option #3 in the open command? The wiki only lists 0 and 1. Your Dumbterm program uses it.

Where can I find doc on the N device's aux1 and aux2 options for the Open and XIO commands as wells as the command options for XIO? Thanks.

I was trying to convert Thomas Cherry Holmes DumbTerm.bas for the Fujinet project to FastBasic. And he gets the Status from Fujinet's N device. But upon further review, I don't see it used elsewhere.

Does anyone know what the FastBasic equivalent to the OSS Atari BASIC's Status command would be? My best guess is to get the result from Err().

Is there an N-Handler for SpartaDosX

Trying use Thomas' DumbTerm BASIC program shown on YouTube. But it fails on my 65XE with error 130 on line #100. Tried several URL's. Fujinet is the 11/15/2020 release. Booted from AVG cart to SpartaDosX v4.49.