Jump to content

a8isa1

Members
  • Content Count

    1,844
  • Joined

  • Last visited

Posts posted by a8isa1


  1. On 9/11/2021 at 3:20 PM, Faicuai said:

     

    Alright, just wanted to circle-back here and close the loop.

     

    After a much longer testing, I finally got my 040-0077 800 to reliably work with BOTH AVG *and* SIDE-2 carts, with absolutely NO modifications of any kind the MoBo, and still with stock RAS-signal (instead of Phi2) on the left-port. The intermittent nature of this problem has been a long-standing, unresolved mystery on my end, which now seems finally addressed.

     

    What (absolutely) made the difference was replacing the older 6502 A/B type CPU board (as well as any of my same-kind spare boards) for a fresher (1983) 6502-Sally type board. ALL timing errors disappeared in a single-stroke, being everything reduced to an occasional (but ineffectual) ATA-command misfire during IDEDIAG tests in SDX, which does not show up anywhere else in any of external-app tests and latest versions of AVG and Side2 Loaders + SDX. I also confirmed this significant improvement to be effective irrespective of my OS boards (stock-form or RAMROD with 52K enabled).

     

    FYI (and just in case), I noticed that, when testing several older-style 6502 A/B CPU boards, one could fare partially better than other, in that specific group. However, I eventually tracked the difference down to the CPU itself (which I swapped between such like-boards, improving, but not solving the problem entirely on such boards).

     

    Furthermore, I cannot discard the chance of finding an 6502 A/B outlier that will drive perfectly both AVG and Side2 carts' HDs, but as far as I could test, the possibility seems remote. So you may save plenty of time by testing Sally-boards, right from the get-go. 

     

    In line with above findings, there is a possibility that when swapping such older boards for a fresher Sally-type, you may not instantly mitigate the offending timing issues, BUT testing 2 or 3 different 6502/Sally chips on that newer board, may very well get rid of such problems, if you are experiencing them. (also important for any XL users out there randomly experiencing these timing errors).

     

    Just trying to close the case for any 800 owners out there, that would like to bring the best out of the system's architecture and potential with essentially no other internal HW mods, but a few plug-and-play enhancements (e.g. AXLON RAM, RAMROD 52K & multi-OS card, Hard-Drive add-on via AVG or Side-2, latest SDX DOS, etc.)

     

    Enjoy!

     

     

     

     

    Time to add to the confusion. Sorry. My 1981 800 has a 6502B and is perfectly happy with AVGCart and AXLON compatible 512K SRAM board.  No modifications or other additions.

     

    a8isa1_6502B.thumb.png.ddf01aed2d81d3cd2d37c47b7c0f4b13.png

     

    -SteveS


  2. On 8/30/2021 at 3:37 PM, darwinmac said:

    I purchased the digital download yesterday. It’s unfortunate that mono has to be used, but the video explains why the trade offs were made. 
     

    I don’t need any more software boxes, but $10 was easy to justify to support people writing for the Atari. 
     

    Bob C

    I did the same.

    • Thanks 1

  3. 22 hours ago, tmp said:

    so no "ERROR 144" during those tests on 800?

     

    also dma/no dma speeds being swapped on 800 is weird and doesn't make much sense (unless it's a bug in SI2 but i don't know what would be the reason to handle 800 and 800XL differently there)

    no "Error 144" .

     

    • Thanks 1

  4. 3 hours ago, tmp said:

    so no "ERROR 144" during those tests on 800?

     

    also dma/no dma speeds being swapped on 800 is weird and doesn't make much sense (unless it's a bug in SI2 but i don't know what would be the reason to handle 800 and 800XL differently there)

    oops my *dyslexia* kicked in.   reversed "enabled" and "disabled".

    • Like 1

  5. On 8/23/2021 at 2:33 PM, Faicuai said:

    Ok, not only tested on XL-mode (with PBI disabled on BIOS), but also on COLLEEN mode (where there is no PBI to speak of, and being as close you can get to stock 800).

     

    The results are the same, SI-v226 HD (DOS) test works with or without DMA. All of this always booting SDX from AVG directly (nowhere else).

     

    As a side note, I re-tested with Incognito's PBI-enabled (on XL-mode), so I could access all APT HD partitions, from both AVG and Incognito's own HD. It is worth mentioning that when running tests with System Information 2.26 set to DOS (not OS), Incognito's HD speed reports around 68 KB/sec, whereas AVG reports 60 KB/sec, at most (this is with DMA=on). The latter is also the same readout when running this test on a 800XL platform. This is over 10% of speed-increase when reading Incognito's internal HD, though.

     

    Let me know what else would you like to test.

    My 800 with retrocanada's designed 512K axlon board, assembled by Jeffrey Worley, SI2 reports for AVGCart (DD21 FloB edition) with old stock Sandisk 32GB SD card (class 4) a rate of 62 KB/sec (best rate, *sequential read*, I think) with DMA disabled.  With DMA enabled it reports 98 KB/sec. There are no modifications aside from the Axlon.   I don't own an Incognito equipped 800.

     

    The very same AVGCart, now in my 800XL, yields similar numbers, also 62 KB/sec with DMA but now in the *random sector* test.  60 KB/sec for *read sequence*.  The number were reversed on the 800.  97 KB/sec best rate with screen .DMA disabled.

     

    In the same 800XL I have an internal MyIDE with an IDE to CF adapter.  Numbers are also similar here as well, 62/60 KB/sec (*read sequence*/*random sectors*) and 96 KB/sec (across all tests).

     

    -SteveS

     

    P.S.

    These are all the "HDD" options I own.


  6. 4 hours ago, Mclaneinc said:

    Hi folks, yes tried the various shortcut methods, all work very well, my initial silly mistake was forgetting that BASIC does not exist internally on a 400 / 800, so I was expecting the U1MB and the AVG to do miracles, oops, my bad as they say.

     

    The only mild anomaly I've found and tested a few times is that a shortcut of a BASIC cart and an ATX set with a tab just causes boot errors, yet the same ATX without the car shortcut works fine. Now this is ok if its an XL compatible game, but if its under an OSB rom its a no go here.. I don't have a working 800 to hardware test it on, the way I was doing it was under the U1mb and selecting an OSB os (which is handy for Non basic programs as it saves hunting out the Translator)

     

    Its up to tmp if he wants to research why the cart shortcut bombs on ATX but is fine on ATR..

     

    Tried a few ATXs, all did the same.. It feels like the way it deals with ATX files make the car shortcut act like an unknown disk, hence the boot errors

    I have the same issue will a real 800.  ATX will not boot, quick *raspberries* or very slow sounds, I/O retries I assume..

     

    ATRs do load but with some retries along the way.

     

    I did a quick comparison with an Atari BASIC (rev A) cartridge and SIO2PC (fujinet-pc software).  Similar results.  ATX has never loaded (on the 800)

     

    @Mclaneinc

     

    Try Omniview 256 XE OS.  I was able load both "Abuse* ATXes (Don't Ask Software version being the second one) on my 800XL with this OS.  Either ATX load most of the time but with I/O retries along the way.   I do not recall them ever loading cleaning the way the cracked ATRs do.

     

    I can't try it myself (because I don't have a flash ROM for my OSes) but I'm curious about Oldrunner OS

     

     

    Good luck!

     

    Regards,

     

    -SteveS

     


  7. I was able to load the ATX version of "Abuse" to load using Translator B.

     

    Use this procedure:

     

    - place game and Translator in the same folder on AVGCart's SD card

    - Atari BASIC can be put in any folder but you must set a shortcut for it. Shortcuts are permanently retained, that is until you clear them or change them.  Navigate to Atari BASIC.  Press CONTROL + # (where # is numeral 1 through 9)

    - Navigate to the Translator ATR.  Press TAB.  You will see the numeral '1' appear meaning the first disk has been added in your disk set.

    - Navigate to your game (which must be in the same folder).  Press TAB to add this disk to your set.  The numberal '2' will appear.

    - Press the numeral which you earlier assigned as your shortcut key for Atari BASIC.   The first disk in your set, the Translator, will load.

    - Translator will instruct you to press SELECT when you are ready to boot your disk.    At this point I believe the Atari would normally load the game but we instead are brought back to the AVGCart menu.  If you had added the game lastly to your set then that ATX/ATR will be selected again.   Just press RETURN and the game will now load.   If the game is not selected then navigate to it again and then press RETURN.

     

    That's it.

     

    Regards,

     

    SteveS

    • Like 1

  8. 7 hours ago, Mclaneinc said:

    Hi tmp, having issues with ABUSE both ATR and ATX, tried various with U1MB set to OSB, I only have Altirra Basic or Basic C but surely one would be ok... It feels like its not getting BASIC??

     

    Same image works on Altirra..

     

    Sample file used

     

    Abuse v2.9 (1981)(Don't Ask Software)(US)[!][BASIC][OS-B]

     

    Edit: Also tested Color Print which I picked because it needed Basic and sure enough, it was going to dos saying only type one letter which is what happens if Basic isn't enabled..its an ATX, I thought just pressing fire or return would be right, no need to hold Option to disable basic..

    I got the above ATR to work on my NTSC 800XL.   My OS options are limited to four.  Omniview 256 XE is the closest thing I have to OS-B on this machine and it was close enough.

     

    Abuse program runs with Atari BASICs Rev A or C and also Altirra BASIC on AVGCart.   Also with built-in Atari BASIC (is this Rev B or Rev C?).  Omniview has reversed OPTION key function.   The ATR is on AVGCart's SD card.  Access was done via the SIO cable to AVGCart.

     

    I didn't try a Translator disk.

     

    I didn't try the ATX either.

     

    -SteveS

    • Like 1

  9. I tried the ROMs from SDX distribution that were similar sized 262k (ish).   SDXImageUser accepted those ROMs but they don't work if use the aforementioned header.   I haven't any tools to add a .CAR header to a raw SIDE 2 ROM image.  I also don't know if such an image needs modification to work in AVGCart.

     

    -SteveS


  10. @tmp and @flashjazzcat

     

    It has been mentioned that SIDE 2 emulation requires a .CAR with a special cartridge type.   Does the ROM image, s2sdx3.car, conform to a cartridge type or ROM image with a banking scheme that SDXImageUser can recognize. If so, which type of cartridge is it?

     

    I wish to add/change files on the image and I would also like to edit CONFIG.SYS.  

     

    Regards,

     

    -SteveS

     

    I wish to add/change files contained on the cartridge and I would also like to edit CONFIG.SYS.


  11. On 8/1/2021 at 4:18 AM, unebonnevie said:

    hi,

     

    I managed to build the circuit of the SDrive at http://raster.infos.cz/atari/hw/sdrive/sdriveen.htm.

     

    When the board is plugged into the Atari 800XL's SIO port, only the GREEN led is ON and it stays on EVEN I have made sure to insert the SD card in.

     

    What does the SENSE connection to the SD card connector in the schematic mean?  Does it mean that the firmware would try to detect if the SD is plugged in?  If so, is the sense supposed to HIGH or LOW once the SD card is plugged in?  My SD card does not have the sense pin.  So, I simulate that with a jumper to 5V or GND.  I should jump to GND to say that the SD is plugged in, that is, to help the firmware to determine that the SD has been plugged in?

     

    Thanks for any tips!

    my purchased sdrive works after some sketchy repairs.

     

    After 10 years my own "ghetto sdrive", no LEDs, no buttons or switches, stopped working. 

     

    I don't recall ever attempting to connect the read/write pin or a sense pin.

     

    What I made was a kludge. Minimum of parts and skipped some key engineering.

     

    Freeduino board as a breakout board for the Atmega8. Used a crystal because I couldn't source the resonator. Skipped the load capacitors. Used zener diodes in reverse breakdown instead of voltage divider circuit. Skipped the current limiting resistors. SD breakout board may or may not have helped me there. My voltage switchers were defective so I used 2 signal diodes in series. A 3.7volts I was powering the SD card above specification.

     

    Somehow it worked and continued for 10 years.

     

    i've since switched SIo2pc, fujinet, Sdrive-MAX, and AVGCart.

     

    Some day I will rebuild the ghetto SDrive just because I liked its simplicity with no moving parts


  12. On 8/1/2021 at 4:18 AM, unebonnevie said:

    hi,

     

    I managed to build the circuit of the SDrive at http://raster.infos.cz/atari/hw/sdrive/sdriveen.htm.

     

    When the board is plugged into the Atari 800XL's SIO port, only the GREEN led is ON and it stays on EVEN I have made sure to insert the SD card in.

     

    What does the SENSE connection to the SD card connector in the schematic mean?  Does it mean that the firmware would try to detect if the SD is plugged in?  If so, is the sense supposed to HIGH or LOW once the SD card is plugged in?  My SD card does not have the sense pin.  So, I simulate that with a jumper to 5V or GND.  I should jump to GND to say that the SD is plugged in, that is, to help the firmware to determine that the SD has been plugged in?

     

    Thanks for any tips!

    I did some quick testing (after doing some not quick repairs to my classic SDrive).

     

    Green LED isn't a power indicator per se.  It is normally turned off until there is Read activity.

     

    The normal start sequence is the Green LED blinks momentarily then turns off.   The four yellow LEDs light.  Activity on the Green LED and it goes out again.  Finally yellow LED L1 is the only one lit and the SDrive menu is displayed on the screen.

     

    IF the green LED lights but nothing else does I believe this means the Atmega is correctly programmed but there is something wrong with the SD card.

     

    - It's not installed.

    - It's not formatted FAT16.

     

    IF green LED blinks and only yellow LED L1 lights then

     

    - SDRIVE.ATR is not in the root of the SD card

     

    If SDRIVE.ATR is corrupt then

     

    - all four yellow LEDs stay lit and "BOOT ERROR"

     

    I hope this helps.

     

    Regards,

     

    SteveS


  13. Auto Start (CONTROL + SHIFT + A) does not seem to be working for me with DD21, FloB edition.

     

    Thinking that I might be typing the wrong sequence I temporarily rolled back to 0020.   The feature works fine.

     

    Unfortunately, my test created more problems for myself.   After reinstalling DD21 I discovered that I had forgotten to clear Auto Start. AVGCart was now automatically booting to Action. Since  CONTROL + A also does not work in DD21 I had to repeat my steps. Reinstall 0020, clear Auto Start setting, reinstall the DD21

     

    Regards,

     

    -SteveS

    • Like 1

  14. I find Jatari fun to play.  I had issues

     

    - More than once I mispelled my answer. 

     

    - once there was a list of items separated by commas. I neglected to insert the commas but otherwise my answer was correct.  Suggestion: treat commas (and perhaps periods) like whitespace.

     

    - failing to type the article "the" in a title resulted in an incorrect answer.   I don't recall if exact titles were required in the TV game Jeopardy or not.  Perhaps the host would prompt, "I need more".  I see a way to do this in Jatari.

     

    These issues are probably difficult to remedy via programming.   Perhaps an option to manually override and flag the answer as CORRECT.

     

    Regards,

    -SteveS

     

    • Like 2

  15. This may seem trivial but I was stumped as to how to advance after completing the first level.

     

    Despite the title of the screen being "Select World:" I saw only "Escape from the Lab" as the only choice.  I reached for OPTION, SELECT, and START but those aren't helpful at this point.

      

     

    I actually needed the suggestion (from mazzspeed  [EDIT] actually, it was SadMan) to move RIGHT.

     

    Perhaps something like --> to point to the next choice.

     

    I've been playing by keyboard.   Perhaps it would have been obvious had I been using a joystick.   

     

    FloB is great fun and I can play it without a joystick!   (I have arthritis in my thumbs and I'm still looking for an alternative to an Atari style joystick).

     

    -SteveS

     

    [EDIT]

    LOL

     

    Oh!  The arrow could not have been any bigger.    I must have thought it was part of the artwork.

     

    Just ignore me!

     

    • Like 1
    • Haha 3

  16. 5 hours ago, DjayBee said:

    See this post and grab the last file from the very first post of this thread. 

    Test it on hardware and give feedback. 

    NTSC 800XL with Rambo XL 256        Mouse                  Copyright Notice               Demo

    Fujinet  1.0                                            0:36                      0:56                                   1:59

    SWP ATR8000                                      0:52                      1:36                                   2:47

     

                          

    • Like 1

  17. Sorry, as typical for me, it was a user error.

     

    I extracted newer fujinet-pc not realizing the files were extracting into folder ../fujinet-pc-fujinet-pc.    I had moved the prior version into ../fujinet-pc.  This folder name was easier for me to remember.    The newer version never got compiled.

     

    It's working now.

     


  18. I get this instead.

    Spoiler

     

    sioNetwork::parseURL(N:HTTP://api.open-notify.org/iss-now.json)
    sioNetwork::parseURL transformed to (N:HTTP://api.open-notify.org/iss-now.json, HTTP://api.open-notify.org/iss-now.json)
    Parse and instantiate protocol: N:HTTP://api.open-notify.org/iss-now.json
    Invalid protocol: HTTP
    Could not open protocol.
    write: 1
    ERROR!
    write: 1
    ERROR!
    SIO CMD processed in 149 ms
    read: 0
    read: 5

    CF: 71 53 00 00 c4
    sioNetwork::sio_process 0x53 'S': 0x00, 0x00
    write: 1
    ACK!
    sioNetwork::sio_status_local(0)
    ->SIO write 4 bytes
    write: 1
    COMPLETE!
    write: 4
    write: 1
    SIO CMD processed in 14 ms
    read: 0
    read: 5

    CF: 71 52 00 00 c3
    sioNetwork::sio_process 0x52 'R': 0x00, 0x00
    sioNetwork::sio_read( 0 bytes)
    write: 1
    ACK!
    write: 1
    ERROR!
    SIO CMD processed in 4 ms
    read: 0
    read: 5

    CF: 71 52 00 00 c3
    sioNetwork::sio_process 0x52 'R': 0x00, 0x00
    sioNetwork::sio_read( 0 bytes)
    write: 1
    ACK!
    write: 1
    ERROR!
    SIO CMD processed in 5 ms
    read: 0
    read: 5

    CF: 71 43 00 00 b4
    sioNetwork::sio_process 0x43 'C': 0x00, 0x00
    sioNetwork::sio_close()
    write: 1
    ACK!
    write: 1
    COMPLETE!
    SIO CMD processed in 5 ms

     

     


  19. Is fujinet-pc at the point of development where it can support Bill Kendrick's ISS.XEX? I ask because I'm not sure about the cable I cobbled together. I think I have PROCEED connected to RTS but ISS.XEX is not retrieving data.

     

    -SteveS

×
×
  • Create New...