Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1,056 Excellent

About Wrathchild

  • Rank
    River Patroller

Contact / Social Media

Profile Information

  • Gender
  • Location
    Reading, UK.
  • Interests
    Porting games the A8 never had

Recent Profile Visitors

22,769 profile views
  1. Greetings to the SillyVenture attendees Have fun!
  2. I thought @ndary had done this a long time ago?
  3. Reminds me of "Waiter, there's a fly in my soup"... "Ssshh, or everyone will want one"
  4. I wonder if some tunes/effects could be lifted from arcade games? https://forums.arcade-museum.com/archive/index.php/t-390819.html
  5. Perhaps Altirra "isn't the droid you are looking" ? Xformer 10 seemed to be more the sort of thing for people just wanting to fire up and play games.
  6. You're welcome to try this cart version as the AvgCart provides the mapper. I did have a report of it locking up after a few rounds but didn't get any followup on that if I recall, so worth giving it a try first. Mule_MaxFlash.car
  7. Some games can but it takes a heck of an amount of work to get to point where you'll know. Two that I'd looked into for 5200 ports that would need more than the 16K RAM were Zybex and Lode Runner. Then again, some can surprise you, Rampage was an example of that.
  8. Indeed, that isn't a problem though, hopefully the Beeb assembler you are using can compile to an address but run at another? When I do A8->5200 ports or C64->A8 then I come across this and both the CC65 suite (by which I mean the CA65 assembler and LD65 linker) or MADS let you specify different LOAD and RUN addresses. At load time you then relocate from ROM to RAM and anything using it knows correctly where to look
  9. Yeah but that wouldn't be stock Atari then (plus the original was 128KB) A bit harsh, there were of course 128KB XEGS ROM titles (examples) and latterly the XEGS switchable, AtariMax & MegaCart type carts that gave better capacity. The advantage of a such a cart version is that you could actually target 64K, even 48K, as the 'stock' model. If Philsan is more referring to the more recent AVG & UNO, Ultimate and The!Cart cartridges which themselves can emulate the above bank switching models, then that kinda defeats the point as these (maybe with the exception of the Ultimate Cart) can run ATR images and sector load times, yes, aren't as fast as switched bank but still fast enough. But again, being able to use a cart image instead means the 48K/64K RAM target instead of 128K. As you are already employing a form of bank switching for the 130XE's extra memory in the $4000->$7FFF window then a build for a MegaCart image with its window at $8000->$BFFF should pose too many problems.
  10. Anything larger than from, say, a physical floppy in an 810 or 1050 would require use of an SIO2PC or SIO2SD type device where the ATR image is mounted. Others could comment better I think, but you could actually use Altirra setup with an CF image file (maybe even direct) and manage things through that, then take the card to the 800.
  11. Yes, using FDISK, maybe check this video
  12. Side loader would certainly be the easiest for any beginner as you are just coping files from your PC/MAC direct to the FAT partition on the CF card and so support the long name format directly and FJC's cool code handles the displaying/wrapping and the searching of them. To use images, you would partition your CF card and the max size of a partition is the 65535 sectors (not sure why that isn't 65536?). So once setup and allocated to a drive number you can use a disk copy tool to transfer the ATR image. There are some PC tools too I think that let you work on a raw CF image and then write the whole image to a CF card. I am guessing that many of the files in the ATR collection came from the 8.3 Atari DOS days and kept as-is and so there was a better chance they ran from DOS, even if it overwrites it later. To the most part I would expect the same file in a collection which has a nice long name to actually be binary equivalent. The MyPicoDos menu loader utilises a file (PICONAME.TXT) to handle the long name translations but required you to manage a file per folder. If anyone is a good script writer then the folder structure and files could be extracted from the 4 ATRs and then the text files used to rename files with their long names Then you'd have one big folder to copy to a FAT partition and load using the SIDE loader... but then you are probably better off compiling your own from the bulk-downloads already mentioned.
  13. I appreciate the OP wanted to do this via Side Loader but elsewhere on AA was posted a set of 4 x 16MB ATR images stuffed with titles with some PAL specific titles on Disk 4. I set these up as partitions on the CompactFlash card I used in my Incognito but wanted to launch the MyPicoDos menu from a boot drive and then from there change disk number as required. As booting Incognito in SDX, these images had an issue as certain titles' filenames began with an illegal character, e.g. 3DTICTA.COM for 3D Tic-Tac-Toe. So I manually tidied these up in a hex-editor and re-blew the partitions and the menu behaved fine afterwards. Patched disks (only 1 & 4, 2 & 3 were OK) included here. [Edit] my memory is coming back in regard to this... I think the name issue was possibly something that occurred if I used a recursive copy tool to take the files from the disk image (mounted via an SIO2SD unit) to the partition that I had formatted as SpartaDos and not MyDos. Mark Disks1-4.zip
  14. sometimes on some old ISA graphic cards [Edit] Ha, hadn't seen Rybag's post
  • Create New...