Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

35 Excellent

About mikro

  • Rank
    Chopper Commander

Contact / Social Media

Profile Information

  • Gender
  • Location
    Košice / Slovakia

Recent Profile Visitors

4,820 profile views
  1. Although I know what you want to say here, your mocking of the user there is completely off because this is what he meant: https://github.com/retro16/acsi2stm/blob/stable/doc/a2setup.md and YES, this is an integrated FAT16 driver, only not for usage directly with the Atari but for storing disk images which are to be exposed to the Atari.
  2. En/decryption is the least of your problems. As you said, it's short messages, there's not that much needed from the CPU side. What is much worse is the fact that most of the emails floating around these days are just wrapped html sites and downloading, converting and opening even a single jpg picture can take 10x longer than decrypting the whole message
  3. It depends. If you want 100% generic, cycle-accurate emulation in the most obscure areas of the hardware, it's really not possible. However if you settle with some simplifications, resort to usage of host hardware (Falcon has the ability to display rasters and interrupts as well, for instance), code a nice 6502 JIT CPU emulator... it's definitely possible. I have made some experiments in that area so for instance demos like The Asskicker (not very hardware demanding, just showing one framebuffer) could run even on plain Falcon.
  4. Not sure whether it applies in this case but sometimes it was part of copy protection, i.e. some levels would be corrupted / not possible to finish if not properly deprotected.
  5. EMUTOS.PRG would strongly disagree with this statement. You can execute an OS from another OS without any issue.
  6. I'm not a hardware expert but as mentioned on Facebook, feel free to ask on https://www.exxoshost.co.uk/forum/, there's quite a few skilled hardware people. But I'm sure you don't need to configure anything when it comes to RAM size. The RAM card takes care of that. Btw you can use Hatari for tracing what TOS does and what values it expects. For example, 14 MB Falcon: IO read.w $ffff8006 = $a661 pc=e00034 IO read.w $ffff8006 = $a661 pc=e0003a IO write.w $ffff8940 = $0007 pc=e0003e IO write.w $ffff828c = $0020 pc=e00082 IO write.w $ffff8282 = $0010 pc=e00088 IO read.b $ffff8007 = $61 pc=e0008e IO write.b $ffff8007 = $65 pc=e0008e IO read.b $ffff8007 = $65 pc=e00094 IO write.b $ffff8001 = $0f pc=e000a6 IO write.b $ffff8800 = $07 pc=e000cc IO write.b $ffff8802 = $c0 pc=e000d0 IO write.b $ffff8800 = $0e pc=e000d6 IO write.b $ffff8802 = $07 pc=e000da IO write.w $ffff8240 = $0fff pc=e000ea IO write.w $ffff8242 = $0f00 pc=e000ea IO write.w $ffff8244 = $00f0 pc=e000ea IO write.w $ffff8246 = $0ff0 pc=e000ea IO write.w $ffff8248 = $000f pc=e000ea IO write.w $ffff824a = $0f0f pc=e000ea IO write.w $ffff824c = $00ff pc=e000ea IO write.w $ffff824e = $0555 pc=e000ea IO write.w $ffff8250 = $0333 pc=e000ea IO write.w $ffff8252 = $0f33 pc=e000ea IO write.w $ffff8254 = $03f3 pc=e000ea IO write.w $ffff8256 = $0ff3 pc=e000ea IO write.w $ffff8258 = $033f pc=e000ea IO write.w $ffff825a = $0f3f pc=e000ea IO write.w $ffff825c = $03ff pc=e000ea IO write.w $ffff825e = $0000 pc=e000ea IO write.b $ffff8266 = $00 pc=e000f0 IO write.l $ffff9800 = $ffff00ff pc=e000fc IO write.l $ffff9804 = $ff000000 pc=e000fc IO write.l $ffff9808 = $00ff0000 pc=e000fc IO write.l $ffff980c = $ffff0000 pc=e000fc IO write.l $ffff9810 = $000000ff pc=e000fc IO write.l $ffff9814 = $ff0000ff pc=e000fc IO write.l $ffff9818 = $00ff00ff pc=e000fc IO write.l $ffff981c = $aaaa00aa pc=e000fc IO write.l $ffff9820 = $55550055 pc=e000fc IO write.l $ffff9824 = $ff550055 pc=e000fc IO write.l $ffff9828 = $55ff0055 pc=e000fc IO write.l $ffff982c = $ffff0055 pc=e000fc IO write.l $ffff9830 = $555500ff pc=e000fc IO write.l $ffff9834 = $ff5500ff pc=e000fc IO write.l $ffff9838 = $55ff00ff pc=e000fc IO write.l $ffff983c = $00000000 pc=e000fc IO write.b $ffff8260 = $00 pc=e00102 IO write.b $ffff8201 = $01 pc=e00108 IO write.b $ffff8203 = $00 pc=e0010e IO read.b $ffff8007 = $65 pc=e00112 IO write.b $ffff8007 = $65 pc=e00112 IO read.b $ffff8006 = $a6 pc=e00288
  7. What exactly are you looking for? That "Falcon" isn't a Falcon at all, it's a prototype based on the TT. It has nearly nothing to do with the Sparrow/Falcon030. In the beginning it wasn't supposed to have even a DSP. Falcon030, as you perhaps know, doesn't use SIMMs. So any of that register values do not have any use here. Combel reads the jumper settings from the RAM card and setup internally according to that. No need to configure anything further. 0xff8001 is not used on Falcon030. 0xff8006 is (its word has various configuration properties accessible but the size of RAM is taken from hardware, same as monitory type).
  8. Also, be prepared for rather disappointing VGA output (without further help -- a graphics card, RGBtoHDMI, OSSC, ...)
  9. You know that the TOS has a built-in CRC mechanism, right? So in case some bit would flip for some hardware reason, it would be shown during the boot. Most likely it was you who didn't apply enough pressure when inserting new ROMs or there is a fragile spot somewhere in the socket. So most likely you've just made an idiot of yourself, publicly.
  10. I have an interesting issue. A year later, after I (re-)fixed my XEGS, I've decided to look after U1MB updates. So I find the 4.05 version, decided to play it safe, so I dumped my QMEG into a ROM file and overwrote the whole thing with ULTIMATE.ROM. Everything went well, I saw my profile has been reset, no problem. Tried new GOS, fine. Go back to the menu, I basically leave everything as is, just save the profile and reboot back to SDX. New SDX version, sweet. Start UFLASH.XEX and boom -- Unidentified hardware! Tried manual selection, nope. As it worked virtually seconds before flashing, I assume it must be somehow software related? EDIT: Phew, mystery solved. It was caused by the Ultimate Atari Cartridge presence. Interesting. Is it a known incompatibility? (I tried to boot also the older update ATR and it refused to acknowledge U1MB presence as well... perhaps UFLASH/BIOS stores some vital data into cartridge memory region? If so, it's still interesting that it didn't complain during flashing)
  11. Finally found some answers: http://www.atari.org.pl/forum/viewtopic.php?id=11691 ... so it seems that yes, one needs one U-Switch for every switching operation.
  12. I wanted to take a closer look at the U-Switch, following the note which @flashjazzcat left in the other thread. However I have realised that not only U-Switch is no longer available but it's gone with all its documentation (if there even was any). My main question would be: is it possible to use U-Switch for more than one switching task? Right now I have a stereo switch there (U-Switch's BIN <-> U1MB's M0, IIRC) and there are only the --1-- and --2-- pins there which seem to serve more as configuration pins than inputs. And while we are at it, Lotharek's stereo seems to be gone as well (so no docs available, too...) -- I'm wondering about the three pins (Sr, Bell, A4). Bell and A4 are connected in my XEGS but Sr isn't? Is there more information about it somewhere?
  13. Nearly exactly five years to the dot, I can update my original post. A year ago I had an issue with ROM and instead of diagnosing it by myself I let someone else do it. The trouble was that the fix was just temporary and he tampered with my original wiring so I couldn't close the XEGS anymore: So when a few days ago the problem reappeared I decided to fix all the problems (in the end it was a badly soldered ROM socket, my soldering skills weren't great back then). I noticed that the U1MB pins can be actually grouped with an IDC header: That allowed me to create much cleaner wiring (as you can see, I also replaced the horrible thick red wires with classic audio ones): I intentionally kept the unused wires from the ribbon cable there so future expansions could be added to it (doubtful but perhaps COVOX would one of them). Assembled together all works nicely, even the cartridge port works after the cleanup now:
  14. You can go for https://www.atari-forum.com/viewtopic.php?p=381588#p381588 but it's quite pricey.
  • Create New...