There's a few ways you could do it.
1. Put RUN "program.bas" onscreen then either set forced input on (AUX1=$0D) or put a Return into the keypress buffer. To keep the user in the dark as to what's going on you could set the text colour = background colour and disable key/Break processing.
2. "Inject" the program into memory, set Basic's zero-page pointers appropriately and call the routine in Basic ROM to run the program.
3. Do a direct call to the Basic ROM with the RUN "program.bas" parameter set up.
The Basic Source book might have more info. As for programs to do this sort of thing, there'd be dozens of them around.
- AtariAge Forums
- → Viewing Profile: Rybags
Rybags
Member Since 29 Sep 2005ONLINE Last Active Today, 6:29 AM
Community Stats
- Group Members
- Active Posts 9,751 (4.19 per day)
- Profile Views 20,245
- Member Title Quadrunner
- Age 44 years old
- Birthday October 1, 1967
-
Gender
Male
-
Location
Australia
Contact Information
Posts I've Made
In Topic: Source (or explanation) of Autorun.Sys for Basic?
Today, 6:28 AM
In Topic: Peripheral Emulator for ST
Today, 4:37 AM
He's wanting to emulate a real drive via connection to the ST.
AFAIK there are no such systems to do it by PC connection. ST and Amiga drives have offboard controllers, so the computer talks to the drive at a low level.
There's standalone solutions like SatanDisk and Hcx floppy emulator (multi-system) and I believe there's also modern day hard disk replacement options.
For transferring files to ST you can essentially do it using 720K MS-Dos disks although 1.44 Meg drives aren't the ideal solution for creating them. There's also null-modem cable setups but they're fairly slow.
AFAIK there are no such systems to do it by PC connection. ST and Amiga drives have offboard controllers, so the computer talks to the drive at a low level.
There's standalone solutions like SatanDisk and Hcx floppy emulator (multi-system) and I believe there's also modern day hard disk replacement options.
For transferring files to ST you can essentially do it using 720K MS-Dos disks although 1.44 Meg drives aren't the ideal solution for creating them. There's also null-modem cable setups but they're fairly slow.
In Topic: Dead 800XL?
Today, 12:10 AM
A single bad RAM is enough to cripple the machine because each chip supplies 1 bit per byte accessed.
Diag cart at least might verify the CPU is OK and maybe indicate that some RAM is bad.
Swapping a bad RAM chip into a good machine shouldn't hurt the good RAM. It's a quick way to verify if the chip isn't good.
Booting to Self-Test generally requires the machine to be at least partially working. Bad RAM generally means the system might have trouble getting that far.
Diag cart at least might verify the CPU is OK and maybe indicate that some RAM is bad.
Swapping a bad RAM chip into a good machine shouldn't hurt the good RAM. It's a quick way to verify if the chip isn't good.
Booting to Self-Test generally requires the machine to be at least partially working. Bad RAM generally means the system might have trouble getting that far.
In Topic: Atari Assembler Editor Cartridge and inline comments
Yesterday, 11:09 PM
I prefer to leave labels with nothing else on the line anyway.
It makes it easier to read and easier to insert new code.
It makes it easier to read and easier to insert new code.
In Topic: Dead 800XL?
Yesterday, 10:03 PM
Diag carts are fairly universal. There's images around that can be flashed to Atarimax carts.
Some games run in "diag" mode - if you've got a Star Raiders cartridge, try that.
But by your description you've probably got some bad RAM. You could try swapping those 2 suspect chips into a known good machine, although only 800XL and early 65/130 XE use the 64k x 1 RAMs.
Some games run in "diag" mode - if you've got a Star Raiders cartridge, try that.
But by your description you've probably got some bad RAM. You could try swapping those 2 suspect chips into a known good machine, although only 800XL and early 65/130 XE use the 64k x 1 RAMs.
- AtariAge Forums
- → Viewing Profile: Rybags
- Guidelines




Send me a message
Find content
Display name history

