Jump to content


New Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

4 Neutral

About CaptainMidnight

  • Rank
    Space Invader

Profile Information

  • Location

Recent Profile Visitors

136 profile views
  1. Wow thanks, it's not exactly the version I'm looking for but it's essentially the same game - the timeframe is also roughly right - I think this is probably an American version of the game. Thanks again 👍
  2. Hi All In the very early 80's, many home computer magazines included type-in game and program listings - these normally spanned 4/5/6/... pages of the magazine, seemed like they took ages to type in and longer to debug where you'd made mistakes typing them in 🤣 'Timebomb' was such a game - from memory the aim of the game was to collect flags / mark bombs before they exploded(?) while trying to out run a skull and crossbones type enemy(?) Here's a picture of the game which was released for the ZX Spectrum years after it was publised as a basic type-in listing for the Atari 400/800 at that time. It's one of those iconic games I can remember from my childhood and would love to find the listing of it and ultimately recreate it. If anyone comes across this Atari BASIC game listing (preferably as a .bas file 😉) please give me a shout - god loves a trier 🙏 Phil Timebomb - Exactly the same as a magazine published Atari 400/800 type-in listing
  3. OK OK here we go whoop whoop, finally some success, still testing, but at least we get to see the Atari screen running on the Pi. Just in case others or the author would like to know how to get this to work on the latest RPi4 running Pi OS 64-bit, where we go: - sudo apt-get install libsdl1.2-dev libgtk2.0-dev --no-install-recommends tar xzf atari++.tgz ./configure make sudo make install then to actually run it: - atari++ -FrontEnd SDL -Sound SDL From the looks of it, the issues I've been experiencing could be related to building on the 64-bit version of Pi OS, so when I get a bit of time later I'll trial a build on the Pi OS 32-bit.
  4. ........... a little progress! After a bit of prolonged googling, I've now successfully (by all accounts) installed the SDL requirement via: - sudo apt-get libsdl1.2-dev My next probably even more basic question is what are the minimal paramaters you'd expect that need to be passed to atari++ for it to start ? [email protected]:~/atari++ $ ./atari++ Failure: Invalid argument: unable to define the hardware parameters
  5. Now just the RPi build to sort ............... Your latest build, after './configure' and 'make', creates the executable atari++, on running produces: - [email protected]:~/atari++ $ ./atari++ Failure: object doesn't exist: unable to build a suitable frontend. Either LibX11, SDL or Curses must be available Has anyone got any actual command steps on how to create a working build version on a Raspberry Pi ?
  6. ..... here's a blank Alpha-Load menu disk (SSDD 180KB) used with the utilities on side A. Blank Alpha-Load menu disk.zip
  7. These Alpha-Load menu disks work on the various emulators and work perfectly well under 800XL/130XE emulation etc but you may need to change the disk emulation settings in some of the emulators. They also work on real hardware as long as the 1050 drive has been hardware upgraded with a US Doubler / Happy 1050 / Speedy etc modification. There are a fair few versions of the Alpha-Load utility disks where the menu makers are broken - working versions can be found on this forum and the main ftp sites - generally the most original working ones from back then are normally called - AlphaMenuUtilitiesSideA.ATR and AlphaMenuUtilitiesSideB.ATR - I've attached them here for your convinience. Alpha-Load_utilities.zip
  8. Unfortunately, there appears to be some issues with Atari++ which causes concern and currently are show stoppers wrt investigating it's suitability for my projects. 1. As documented previously, I still can't create a working build on one of the target operating systems, i.e the RPi Pi OS - work ongoing on this, although no breakthroughs as of yet.... 2. From what I've seen from Atari++ on my Windows 10 systems anything other than full screen is or appears compromised running in a window on a FHD display for dev work - maximum windows size/scaling appears limited? (native window scaling seems absent and preset window sizes seem too small) I'd have to double check but I think the Windows dev build is already using SDL output, not too sure on that at the moment, but offers a very limited selection of window geometry. [Update: sorted the graphics scaling and screen size issue on the Windows dev build] Any further assistance or advice you could offer on the above points would be greatly appreciated.
  9. Thanks for the suggestion, I'll test that theory out when I rebuild the RPi using the standard 32-bit OS image, just in case the current 64-bit beta image is at fault.
  10. Yes, sorry all for the diversion, will move this to github. Still interested in any pi users out there currently using Atari++ 😉
  11. Yes saw your updates thanks, much appreciated. As confirmed through my GitHub comments, Atari++ drive emulation of the double/US double density format and menu writing process just works, but unfortunately atari800 fails with i/o errors, although atari800 (wrt display scaling etc) appears the more polished emulator. I'll look at trying out your suggestion. Thanks again for your help
  12. Yeah that's what I would have thought, but I've got a nagging feeling it's a pi specific issue - I'll have to build another pi image with the standard raspbian 32-bit image to try and eliminate some possibilities from the not running equation...... I'd be interested to hear from any other pi atari++ users, just to try and discount the various options. The other pi alternative, atari800 just works but has SIO implmentation issues with some disk formats - HowfenDos being one of them. I've got both an Intel NUC and RPi4B8 at my disposal for atari emulation - the NUC is running altirra 3.90 - rock solid (so disappointed that this is windows only, they have now brought out an arm64 vervision for windows tablets but not buildable on a pi), just would like to get the little pi sorted as with it being quad core @2Ghz should easily be up to the task.
  13. .... it'll be the standard lxde I would of assumed, so maybe also have to change to X11 then I'm assuming or am I missing something subtle specific to the pi?
  14. ... whoops, obviously, the AtariAge forum system doesn't produce scroll code windows - OK point noted, will just post attachments.
  • Create New...