Jump to content


+AtariAge Subscriber
  • Content Count

  • Joined

  • Last visited

Posts posted by SS

  1. 3 hours ago, ChaoticBiker said:

    So looking for RAM extension, and was pretty much set at buying everything in order to solder the chips on the mainboard and expand to 320kb. 

    I am a big fan of @tf_hh's internal 576K RAM upgrade board.  It will likely do everything for you that you're looking for and is relatively inexpensive.  However on an XE machine you will have to do a bit of desoldering and re-soldering work to install it, although this probably won't be a big deal if you were already planning on replacing some RAM chips anyway. 

    • Like 1

  2. I don't honestly know if I've ever used the 2/4MB setting on my ANTONIA.  I generally just leave it at 576K or 1MB; both settings meet pretty much all of my needs.  What I really do appreciate about the ANTONIA is that it has the 8 open configurable and easily selectable OS slots.  

    • Like 1

  3. 6 hours ago, andymanone said:

    The reason for it are two filter capacitors (C89/C90) connected to SIO Data_IN / Data_OUT (see attached pictures)
    After removing both caps, the 600XL boots up perfectly with the PokeyMax

    Is this an issue only with the 600XL or might it affect 800XLs too?

  4. 1 hour ago, koolmoecraig said:

    How exactly would I get the audio out with the Sophia DVI?  I'm picturing DVI to HDMI input on my TV but then how will I get my TV to put out the audio if it's just looking to the HDMI for the signals?

    You have to run a separate audio line out of your Atari.  My television has a 3.5mm audio input jack that overrides everything else, whatever is plugged into it is what the TV speakers output.  Apparently not all televisions are made this way though.  A friend of mine also has a SOPHIA DVI installed in his XE and has to output the audio to a pair of external speakers. 


    Here is a picture of my DVI and audio lines out of the back of my 600XL:


    • Like 1

  5. 2 hours ago, _The Doctor__ said:

    assign your sio 2 sd as another device... you can choose 0-3 or is it 4


    43 minutes ago, retrobits said:

    Wow, thanks Doc, I just tried this and it worked!  Running both SIO2SD and SDrive-MAX at the same time.

    Yep.  That seems to have cleared up my problem too, as long as "D0" isn't selected on the SDrive-MAX (which I never use anyway).  Thanks!  :)

  6. 22 hours ago, retrobits said:

    the SIO2SD seems to work more reliably when connected to the SIO Splitter.
    Also I have the SDrive Max .

    Do you find that you have trouble using the SIO2SD's onscreen menu while the SDrive-MAX is connected in serial via the splitter?  Because I do.  Both devices will communicate with each other just fine if I do not try to load the menu, so I am stuck with the device displays if I want to have both connected at the same time.  

  7. 1 hour ago, flashjazzcat said:

    Just attach 'ULTIMATE.ROM' from the latest firmware ZIP; that's all you need. Add that as Ultimate 1MB firmware, 'Set as default', and don't forget to enable U1MB in the 'Memory' section of the 'Configure System' dialogue. There is no need to scan anything at all. You just need ULTIMATE.ROM.


    Granted I have not done any of this yet but, if I wanted to change the U1MB settings in Altirra, would I still need to run a SpartaDOS X image and then run UFLASH with it in order to virtually flash the virtual U1MB?  Would the procedure be exactly the same as if I were flashing real hardware? 

  8. @drac030 - Everything seems to work on my end with ANTTEST3.  I tested with the same eight Operating Systems that I used previously and had no issues that caused any interruptions or glitches in operation at all.  OSa no longer causes the program to hang; the system now reboots after loading OSa as expected. 


    The screen does still flash momentarily with garbage graphics while loading under OSa, OSb, and Oldrunner the same as it did in the video that I posted yesterday; screenshot posted below.  However, this does not effect the loading process or program operation at all.  It is only a very few momentary effects on screen and not problematic in any way.  I do not see this effect under any other Operating System. 


    • Thanks 1

  9. 16 hours ago, Philsan said:

    I don't know if SIO splitter is too tight or SIO plug too big.

    I find that the splitter connections *are* just a bit on the tight side, even some of my vintage cables take a bit of extra pressure to fit in.  Your 3D printed plugs are probably a little big though; some light sanding should fix this problem. 

    • Like 1

  10. @drac030 - ANTTEST2 fully loaded and worked with all of the Operating Systems that I tried it with OSa, OSb, Oldrunner, Omniview, XL/XE rev.3, MyBios, Altirra, and Reverse BASIC XL.


    The garbled graphics on the flasher screen that I had seen in the previous revision are no longer present. 


    When I change my configuration to OSa and hit -Accept-, the system does not automatically reboot.  The screen goes black and the computer apparently hangs.  The configuration *does* change to OSa, though, because that is what the system is set to when I reload the ANTTEST2 Configurator.  This is not a problem, just an oddity.  None of the other Operating Systems that I tried caused this behavior.   


    The video below shows the screen while ANTTEST2 is loading under OSa, OSb, and Oldrunner.  I do not see this effect when loading the Configurator under other Operating Systems.  Again, this is not a problem at all, just another oddity. 


    All in all, I would say that ANTTEST2 has solved all of the problems that I was previously experiencing.  Thanks.

    • Like 1
    • Thanks 1

  11. I am a real fan of the FIFJr homebrew on the Sega Genesis.  I just have this version a try on the VICE emulator.  Very nice job indeed.  Too bad that I don't own a real C64 anymore because I'd like to see it running on actual hardware.  I can tell that it was designed for PAL, though, as it ran a little fast when I had VICE set for NTSC.  

  12. @drac030 - This new version fully loaded under every OS that I tried it with : OSa, OSb, Oldrunner, Omniview, XL/XE rev.3, MyBios, Altirra, and Reverse BASIC XL.  


    However, I got a garbled screen after I hit the "F" button on the ROM Flasher screen.  I was able to load the new OS ROM into the desired slot; it was only the Flasher screen that caused the effect.  I have attached a screenshot below.


    • Thanks 1
  • Create New...