Jump to content

Rybags's Photo


Member Since 29 Sep 2005
ONLINE Last Active Today, 9:34 AM

#3442702 Daisy-chaining the SIO2SD

Posted by Rybags on Wed Feb 17, 2016 12:03 AM

Another option which some take is putting it inside the actual computer though that then limits it's use to one machine.


Or you could put it inside a peripheral, even powering it locally as well.

#3442610 Daisy-chaining the SIO2SD

Posted by Rybags on Tue Feb 16, 2016 9:41 PM

It can but I see no reason not to just have it at the end unless you have problems with high speed that way.


Fairly sure the homebuilt plans for SIO2PC include a "decoupling capacitor", no idea if SIO2SD has or needs one.

#3442320 800XL red screen

Posted by Rybags on Tue Feb 16, 2016 3:50 PM

For the purpose of testing it's fine to use the Antic from NTSC 5200.

  • jum likes this

#3442300 800XL red screen

Posted by Rybags on Tue Feb 16, 2016 3:26 PM

If the CPU is good but the (now removed) Ram was causing crashes, then you should get a black screen every time.

  • jum likes this

#3441493 Atari ANTIC Technical Reference PDF?

Posted by Rybags on Mon Feb 15, 2016 3:48 PM

Antic Attached File  antic.pdf   2.56MB   63 downloads


CGIA - never released but doc contains some useful Antic related info Attached File  cgia.pdf   4.15MB   51 downloads

#3441491 800XL red screen

Posted by Rybags on Mon Feb 15, 2016 3:47 PM

OS is unable to start early initialization.  GTIA will often/usually display a reddish brown as background colour on startup, this is normally cleared by OS startup within about 1/2 second.


Bad Ram won't necessarily be the cause though if the Ram is outputting data in an unsolicited way it could crash the CPU.

Easy way to test, remove all the Ram, easy so long as it's socketed that is.


My order of suspicsion would be CPU, Antic, MMU, OS Rom.  This is a lot easier to debug if you have a similar known good machine to test swap components.

  • jum likes this

#3440923 Images generated by RastaConverter

Posted by Rybags on Sun Feb 14, 2016 11:53 PM

I think once again, the background is hurting it.


'shopping required, I'd take the original and turn everything above that dirt ripple just below underpant level into a sky background.

Just plain monochrome would be boring though, it'd need to be something that's graduated.

#3439113 Game titles I like to see appearing on A8 hardware...

Posted by Rybags on Fri Feb 12, 2016 9:12 PM

Space Zap is sort of like the great grandfather to Plants vs Zombies.


As it would happen, I did Space Attack back in 1983.  It was the first or second full game I ever did on Atari, and the first incorporating assembly routines within a Basic program.

I did the game based on the how to play guide alone from the book "How to master the video games".  I don't think I've ever seen a real machine, maybe played it once or twice in Mame.

The version I did only has enemies coming at you, they don't shoot then disappear like the arcade.




The explosion of your ship sequence... heavily infuenced by a popular game of the time, no prize for guessing which one.


Download from Atarimania - http://www.atarimani...tack_27933.html

#3436984 STM32 Cartridge

Posted by Rybags on Wed Feb 10, 2016 6:09 AM

Dunno... there is Veronika, there is F7, Bob's XL accelerator and probably others.

What would be nice is for an existing one to get a high adoption rate at an affordable price.

Throwing more in muddies the waters and makes it harder for those already out there.


And as nice as it'd be to have a cartridge with 200 MHz RISC which can run it's own program and present the Atari with near unlimited objects mapped to memory that Antic just displays and the 6502 can run a kernal for colour and PM changes - it just becomes a case of the Atari itself becoming a peripheral of something bigger.

#3434604 Weird ERROR 130 error in DOS 2.5

Posted by Rybags on Sun Feb 7, 2016 3:28 AM

If source code is available (or even without) a fix could be put in place. Simply have Dup.sys reside a bit higher up in memory to allow for more buffers.

#3434447 Weird ERROR 130 error in DOS 2.5

Posted by Rybags on Sat Feb 6, 2016 8:42 PM

Has Phaeron (amplified by Rybags) not already fully described the reason behind this issue?


Precisely.  The problem and cause has been described.  And it was a known issue which the Setup.com program actually warned you about (though it doesn't tell you exactly why).


Device handlers, hardware etc. have little/nothing to do with it.  It's all down to the buffers running into workspace which happens to corrupt the filespec that's used during copy and probably some other operations as Phaeron described earlier.


Case closed.  There's absolutely no point arguing or complaining about it.  It is what it is.

In any case, if you're a "power user" who needs to use 3 or more drives at a time, Atari's DOS 2.x is about the last thing you should be using.

Throw away the training wheels and use SpartaDos instead.

#3433655 Henry's House on Altirra

Posted by Rybags on Fri Feb 5, 2016 6:48 PM

.dumpsnap command issued from the debugger console.




.dumpsnap    Create bootable snapshot image

  Create a bootable snapshot image from the current simulator state.
    .dumpsnap [-u] <path.atr>
    -u    Disable compression and use uncompressed blocks
  Records hardware and memory state to a disk image with a loader that
  restores the state on boot. The snapshot image contains the base 64K
  of memory and requires a 128K system to boot (the extra memory is
  used by the loader). The loader attempts to reconfigure the hardware
  to match the snapshot state and then resume the running program.
  Not all state is restored precisely and load success depends on the
  exact state and program code. For best results, the same OS ROM
  should be used, no cartridge should be present, and the snapshot
  should be taken at the beginning of the NMI handler for the vertical
  blank interrupt.



#3433235 Did my mobile Phone wipe tracks/sectors of my floppy disk?!?

Posted by Rybags on Fri Feb 5, 2016 9:30 AM

Vibrate function would probably create the moving type of magnetic field which is the enemy of magnetic media.

#3431549 Weird ERROR 130 error in DOS 2.5

Posted by Rybags on Tue Feb 2, 2016 9:49 PM

OK - it's a case of RTFS, the bug is known and the Setup.com program warns you that a configuration where Ramdisk as well as 4 drives will make the Dos menu not work properly.

Actually, the warning isn't exactly verbose, it only bothers to tell you if you have a setup that won't work or the one you have won't work if you enable Ramdisk.





#3427560 atari 800 monitor jack to modern TV: problem

Posted by Rybags on Fri Jan 29, 2016 10:28 AM

By default the 800XL doesn't have the chroma signal connected at all to the monitor port.  So your cable is probably fine but you need to do an addition inside the computer.





There used to be a page with better instructions but I don't think it exists any more.

Note that it's suggested a  100 Ohm resistor be used inline.