Search the Community

Version 4.00 of my emulator Altirra is out at the usual place: https://www.virtualdub.org/altirra.html As usual, thanks to everyone who tried the releases or just chimed in on just about anything during the 4.00-test series. Never thought I'd been working on it this long, but here's the highlights (it's been about a year since 3.90): Tape: New turbo support, tape editor, and support for loading raw tapes directly from .flac files. Disk: Atari 815 emulation, 8" disk geometry support, Disk Explorer can now access files in Indus CP/M images, many full disk drive emulation fixes. Display: Palette solver, monochrome mode, HDR display support, ANTIC fixes. Sound: Improved audio filtering, automatic output switching when using WASAPI output, POKEY fixes. Input: Preset template generator for making input maps, low-latency paddle option, retuned trackball speeds, 5200 fixes. Devices: Percom AT88-SPD, SIDE 3, 1090 80-column board, Bit 3, virtual FAT16/FAT32/SDFS hard disk; modem, XEP80 and Rapidus fixes. UI: Improved dark mode theme support. Debugger: Memory window upgraded with variable width, type, and graphics decoding support; improved speed, more banked cartridge debugging support, improved 65C816 native mode support, more timestamped logging options, and more verifier options. As usual, 4.00 final is essentially the same as 4.00-test43, except for version number changes and using the release check-update channel. (Previous thread for 3.90/4.00-test) Note that starting with 4.00, Altirra requires at least Windows 7. For Windows XP and Vista users, there is also a 3.91 maintenance release at the above link, which contains backported changes from 4.00 of critical bug fixes and the latest version of AltirraOS. And, per tradition, starting off the 4.10-test series: https://www.virtualdub.org/beta/Altirra-4.10-test1.zip https://www.virtualdub.org/beta/Altirra-4.10-test1-src.7z The device tree now better preserves selection when adding or removing devices. AltirraOS updated to 3.32 with fixes for a couple of compatibility issues with the math pack, so B-Graph and House of Usher now work. Fixes to the docking UI to reduce glitching when switching layouts or toggling full screen mode, due to panes becoming visible too soon and drawing in weird places before being moved to their final location. Fixed a few timing bugs in the standard disk emulator. 810s now produce the head bump sound, the timeout was too short for Record Not Found (RNF) errors, and with long retries the idle timeout was sometimes kicking in too soon. Happy 810 and 1050 now have retuned receive rates. The standard disk emulator now attempts to emulate track buffering for the Happy 810, 1050, and Speedy 1050 profiles, where the drive will burst transmit sectors from memory after reading in new tracks. This makes timing closer to the default modes for those drives. The Happy 1050 commands for toggling track buffering are now also support.

Is there a device driver/plugin for Altirra that emulates the MPP-1000 joystick modem? Thx in advance. Wade

Since most of us Mac users like single clicky launch thingies, I thought it might be a good idea to have a single thread for macOS Altirra to make it easier to find all relevant information and files for each release. Altirra 2.8 Lets start with Peters original thread for a Wine bottled Altirra 2.8 (32 bit): http://atariage.com/forums/topic/256928-altirra-28-wine-port-for-macos-sierra/?hl=%2Baltirra+%2B2.9&do=findComment&comment=4081583 Altirra 3.0 Then move to the his Wine bottled Altirra 3.0 thread: http://atariage.com/forums/topic/278822-altirra-30-mac-wine-port/ I polluted that thread (my bad) with an update for 3.1, including all the instructions for what it took to get it both 3.0 and 3.1 running under macOS 10.14 Mojave. Instructions that were cobbled together from the threads: 1) Take Peters original 2.8 download (bottle) and extract it. 2) Move the "altirra.app" (from extraction) to Applications folder. I also renamed it to "Altirra" from "altirra". 3) Take the download from post #15 (in the 2.8 thread above) for MacOS >= 10.13, and extract it. 4) Open Applications folder, and choose "Show Package Contents" from the context menu (right click) of "Altirra". 5) Open folder where post #15 (2.8 thread) was extracted, and choose "Show Package Contents" from the context menu of "Altirra.app". 6) In both windows navigate to the Resources folder. 7) Copy the following files from the post #15 Altirra.app Resources folder into the Altirra.app Resources folder from Petes bottle: - File: Wine.bundle - Folder: wineprefix Close Finder windows. Launch Altirra, run through setup. You'll need to navigate to your ROMS and CARTs folders using the / folder and then the tree where its stored. Seems the Wine stuff doesn't respect any aliases. I zipped the 3.0 release Wine/Altirra Application (package) in a zip that can be extracted and run as is, without having to go through all those steps. Here: https://www.dropbox.com/s/n8q30oexq5ymrju/Altirra30_Mojave.zip?dl=0 Altirra 3.1 I then updated the package for the 3.1 release by performing these steps: To get this, I took the 3.10 binaries from the Altirra site, and copied them to the folder "Altirra.app/Contents/Resources/wineprefix/drive_c/winebottler". Files: - Additions.atr - Altirra.chm - Copying - Altirra.exe - Altirra64.exe Just replacing the files still launched the 3.0 version. I did some additional thread digging and found that I also had to remove the following (one or more of these had cached data). Your install may vary in name: ~/Library/Application Support/Wine ~/Library/Application Support/Avery Lee_152528885525251 ~/Library/Application Support/com.altirra_15264834116685 (current bundle identifier) I then zipped the 3.1 release Wine/Altirra Application (package) in a zip file that can be extracted and run as is, without having to perform the additional steps. Here: https://www.dropbox.com/s/xhsvfxs38y3z1vi/Altirra31_Mojave.zip?dl=0 Alternate location in 7z format with smaller size (thanks Roland). Remove the .txt after downloading. See post #12 for details on extraction: Altirra31_Mojave.7z.txt Status 2018.12.14: This was working fine before the 10.14.2 update. With 10.14.2, it still works but will generate a warning about application compatibility in a future macOS release. 2018.12.14: Updated the 3.1 zip after editing the package metadata. Altirra in macOS application title now shows as proper case. Package version info also shows as 3.1 instead of 3.0, and Avery is credited. 2018.12.20: Added 7z version of Altirra 3.1, served directly from AtariAge.

Hi All, I just set up Altirra 4.10 and FujiNet-PC PC 2307.1 on my Windows 11 laptop. I followed the setup instructions and I am able to get Altirra to boot to the FujiNet. Problem is any disk or cart image I mount never loads, it boots into the Altirra BASIC screen. I am not sure what I might be doing wrong or miss-configuring. Has anyone run into this issue or might know of a fix? Thanks in advance.

As there is no full direct Linux support in Altirra nor WUDSN, i did wrote a simple wrapper script that simplifies full ALTIRRA-WUDSN integration under linux. Requirements: wine Howto: Copy the attache script to your Altirra64.exe location. Open WUDSN ide, go to: Window->Preferences->Languages->Assembler->Atari 8-bit Assembler->Altirra TAB Enter path to the wrapper script instead of altirra64.exe. (see attached picture) Enjoy Your new Linux Dev Setup. AltirraLinuxWrapper.sh

Experiment of the day: Altirra's co6502 and POKEY emulation cores adapted for RASTER Music Tracker 1.28. altirra-rmt.zip People had been asking about this, so I decided to try it out. There are two modes of usage: You can use one of the DLLs without the other. There's probably no point in using sa_c6502.dll by itself, as the default one is perfectly fine at emulating the RMT player. Using sa_pokey.dll will give you only the Altirra POKEY emulation core, with register writes aligned to RMT ticks. You need to rename or remove apokeysnd.dll for this as RMT will prefer it to sa_pokey.dll. If you use both of them together, they will notice each other and the 6502 core will talk directly to the POKEY core, bypassing RMT's POKEY register handling. This gives cycle-precise write timing as well as access to other POKEY registers not normally mirrored by RMT (particularly SKCTL). There are still no interrupts or any other hardware. Note that this is based on the Altirra 4.00-test core, so these DLLs will not work on Windows XP. There are some gotchas due to quirks in the RMT DLL interfaces. RMT's sa_pokey.dll interface only allows 44.1KHz/8-bit sound output, so this sa_pokey.dll bypasses RMT's output and runs its own 48KHz/16-bit output. Somewhat more janky is that RMT is always running both the 6502 player and POKEY in stereo mode, but for a mono file it mirrors the $D200-D208 to $D210-D218 in between sa_c6502.dll and sa_pokey.dll. Thus, in linked mode, sa_pokey.dll has to detect whether RMT is running in mono or stereo mode and dynamically switch the second POKEY on and off. You may hear it take a moment to switch when changing songs with different modes. Finally, RMT seems to always init sa_pokey.dll with NTSC parameters, so pitches will be relative to NTSC clock. Song tempo will still be correct, however, as this is determined by how often RMT runs the player and requests samples. To be honest, I don't know if I'll continue maintaining these DLLs, as this was an experiment and I had to do some really hacky things to work with RMT (like doing a cross-call to msvcrt.dll's atexit() to cleanup). I can't tell the difference from the ASAP core (apokeysnd.dll), though I'm no musician. But, I did get some code cleanup done and figured there might be some community interest.

No, it's not a question, it is a tutorial Promised myself to do something Atari-useful this weekend, my experimental PCBs are still in the mail, so here it goes. My quest was to figure out the possible ways of creating and using VHD files on Linux to be used with Altirra, more specifically the SIDE3 device emulation. Now, you will say that one can create VHD files from within Altirra and Bob is your uncle. This, however, creates a totally empty drive, and unless it is not to be used entirely for APT partitions and formatted from the Atari/SDX level, you are still in trouble in the Linux land, as it is possible to mount VHD files (even for R/W operations, see below), but for editing partitions or formatting them there is still no easy way of doing it on Linux (and frankly I actually did not find any way for this particular thing). All this information is not new or anything, it is all out there, but sometimes you need to do 2+2, and also, some tutorials on this are totally wrong. In any case, below my notes on how to go about doing all this and having relatively full control over the VHD files and their contents from Linux. One step in this, unfortunately, requires having VirtualBox tools installed (no need to have any Windows virtual machines though). I do this on Ubuntu 20.04, your mileage may vary, and even on Ubuntu you can go alternative routes at some points. You may also need to have some packages installed on Linux that I already have (I had tons of crap accumulated over time). There are four steps to get there: Create and initialize an empty drive image with suitable partitions Pre-populate the image with files Convert that to an VHD file Mount the VHD file on Linux to extract from or add new files to the virtual drive Preemptive warning - make sure you do not have the same VHD file mounted / used by multiple ends, like Linux / VirtualBox / Altirra, this may end up in a total disaster. I am also very modest with any deeper explanations, I hope that if you are in the Linux land you do have some clue of what you are doing and what these things are. 1. Create an empty drive image and setup a FAT partition dd if=/dev/zero of=sd.img bs=1M count=32 (adjust the count parameter to the desired size, this one is for 32MB) fdisk sd.img Inside fdisk, do "o" to write a DOS label, "n" to create a new partition, choose (p)rimary, hit Enter through other questions to get the defaults. Then say "t" to change type, choose "c" for FAT, and finally say "w" to write the partition. sudo losetup -Pf --show sd.img This will print you the loop device identifier that was linked to your image file, let's say it is /dev/loop5 (almost certainly it will be different for everyone, and it cab be different each time you do it). You can also use "lsblk" to see your loop device with the partition you created listed. Now you can format the partition with: sudo mkfs -t vfat /dev/loop5p1 At this point you can go two different routes to put some initial files on it, one is the "old-school" using mount, one is using Ubuntu / modern facilities. 2a. Pre-populate the image with files, old-school way Keep the loop device linked, and then: sudo mount -t vfat -o loop /dev/loop5p1 /mnt With super user privileges (sudo bash for example) you can now copy your files to /mnt. When done, unmount all this and unlink the loop device: sudo umount /mnt sudo losetup -d /dev/loop5 Go to point 3. below 2b. Pre-populate the image with files, udisksctl / Ubuntu way First, unlink the loop device you created in step 1. if it is still linked. sudo losetup -d /dev/loop5 Then: udisksctl loop-setup --file sd.img This will also print the loop device identifier assigned to your sd.img file, but here this is probably irrelevant. Instead, the Ubuntu file mounter should kick in, mount this for you and offer to open a file browser, use the file manager tools you are familiar with to copy the files over. (This should be the same behavior and procedures you get when inserting a USB Flash drive). When you are done you can simply unmount / eject the drive through the OS GUI. Alternatively, if for whatever reason the automatic mounting did not work, you can do things by hand: udisksctl mount -b /dev/loop5p1 Similar to the automatic way, this will mount it at /media/<your user>/<disk label>. When done copying your files over, do: udisksctl umount -b /dev/loop5p1 udisksctl loop-delete -b /dev/loop5 3. Create the actual VHD file that you can use with Altirra For this step you need to have the Oracle VirtualBox tools, installing VirtualBox is outside of scope of this instruction. VBoxManage convertfromraw sd.img image.vhd --format VHD This will create a expandable VHD, if you want to have the fixed size one (it will be as large as the sd.img file you created), you can add "--variant Fixed" at the end of the last call. At this point you can use image.vhd with Altirra, and it is now safe to delete sd.img (unless you want to keep it for whatever reason). 4. Mount the VHD file to later add more files from Linux, or copy files you created on Atari back to Linux Do not do this when Altirra is running and has the VHD file in use! For this you need guestfs things, install them with (for me it pulled in quite some dependencies): sudo apt-get install libguestfs-tools Then you need to figure out the device identifier for the partition inside the VHD, though I am convinced it is /dev/sda1 in 99.9% of cases, the proper way to do this is: sudo guestfish --ro -a image.vhd Inside guestfish say: run list-filesystems exit The second command will give you the device name for the FAT partition inside, you then use it with this command: sudo guestmount -a image.vhd -m /dev/sda1 --rw /mnt (/dev/sda1 is what you get from list-filesystems above). Now you can copy things to and from /mnt, but you do need to be in the superuser mode for this. When done, unmount (again, do not forget this before starting Altirra again!): sudo guestunmount /mnt And that is pretty much it. For the last point you can also use a Windows virtual machine if you have one running under VirtualBox, and mount image.vhd there to copy files with your virtual Windows, but I leave that exercise for the curious.

Hello there o/ STORY Today I want to tell you about a small my project — Altirra Middle Runner (amr). It all started with the fact that looking through a huge number of programs for atari, I had to constantly switch configurations of the Altirra emulator. Some programs required BASIC, others asked to remove the cartridge. The third required a different version of rom - OS-B, the fourth needed more memory than was selected in the default profile. All this tired me out, because the only thing I would like is to click on the icon with the image of a disk or cassette in windows and immediately get a running emulator with the necessary parameters, and not waste precious time figuring out once again why the program freezes or crashes the emulator with error. If anyone does not know, there is such a standard for describing file parameters - TOSEC. You may have seen how the names of the files, along with the name of the program, file has additional information in square brackets, describe the required hardware necessary to run it. For example: Anti-Sub Patrol (1983)(Roklan)(US)[BASIC][OS-B][cr CSS].atr You can read more about the TOSEC specification on the Internet, and we are interested in two parameters here: [BASIC] and [OS-B]. First, the [OS-B] parameter tells us that we need an earlier Atari 800 with "OS-B" firmware. And secondly, the [BASIC] parameter says it is necessary to insert a cartridge with "Atari Basic rev B.rom", since it was inserted separately. Now it is enough for us to specify the arguments when starting the emulator, so that the program we have chosen will be successfully loaded. And here comes my program. What it does? The file name is passed to the amr program as an argument, then it is analyzed and the parameters of the necessary hardware are determined. After that, the launch line with the emulator arguments is already formed and all this is transferred to altirra.exe. To prevent these parameters from overwriting the main settings of the emulator, the "/tempprofile" argument is used. This is a test version of the program and it will be improved in the future, but at the moment it successfully detects and allows you to correctly launch the emulator with the following settings: [BASIC] [OS-A] [OS-B] [XL-OS] [req 8K] [req 16K] [req 24K] [req 48K] [req 52K] [req 64K] [req 128K] [req 256K] [req 320K] [req 320KCOMPY] [req 576K] [req 576KCOMPY] [req 1088K] (PAL) (NTSC) At this stage, this is quite enough to run most programs, but in the future the list will certainly grow. Another thing that haunted me was the automatic loading of "Turbo 2000" cassettes. Altirra does a great job with this task, but I would like to run such files with a single click. Luckily for me, Altirra is able to work with VFS (Virtual File System) and in particular with files inside zip archives. As a result, the idea arose to pack a wav file with an audio recording in the "turbo 2000" format with name "data.wav" into a zip archive, change the file extension to t2k and set associations for the correct launch. The only caveat is that in order to load such cassettes, you must first run the T2000 loader. INSTALL To correctly install amr, just unpack the archive inside the Altirra folder. So that amr64.exe is located next to Altirra64.exe Next, you need to run "make_reg.bat". It will generate an association file for the windows registry - "amr.reg". This file will use icons from the "icons" folder and current path to associate amr64.exe to the following file types: atr atx bas car cas dcm pro rom xex xfd t2k. If necessary, this list can be expanded by adding new file types. Now we doubleclick on the amr.reg file and confirm the changes to the windows registry. At this stage installation is completed. The only thing that needs to be done is to place the file with the firmware "Atari Basic rev B.rom" in the "roms" folder. This file is critical and necessary to run programs requiring "OS-B". RUN If you did everything right, now just click on the atari-file in windows explorer. Since everything is in test mode, a console window will open, which will describe the parameters that could (or not) be determined, as well as the startup arguments line for Altirra. In the future, of course, this window will not be needed and don't show. To run the "Turbo 2000" cassettes, it is also necessary that the loader file "T2000 loader.xex" be located next to amr64.exe. After starting the emulator, the inscription "T2000" will appear on the screen. After play sound signal you must press the "return" (enter) key. After the flickering of black and gray stripes, the name of the program will appear and you must press "return" (enter) again. Your further participation is not required and in a minute you will see the result of the loading. amr64.7z

Hello there o/ I'm tired of the standard icons for Altirra. I made my own collection: floppy disks images, cassette, cartridge, rom (binary), well, for basic and XEX. Inside the archive you will find PNG files sized 512x512px, as well as ICO files for windows, sized 256x256 and smaller. Also there are blanks of reg-files for windows. You only need to change the path where the icons are located @="E:\\Workspace\\Icons\\atr.ico" and the path where the emulator is located @="\"e:\\Emu\\Atari\\Altirra \\Altirra64.exe\" \"%1\"" WinIcons.zip

On the Altirra emulator for Atari 8-Bit, I can boot into it with roms, disks and other media types and they all boot in fullscreen, but when I try to boot a tape load, it opens in a window instead, even if I set the /f parameter for fullscreen. Is there a way of booting tapes in fullscreen? Some setting I can't see?

Are questions about Phaeron's excellent Altirra emulator OK in here? I'm having trouble pasting text into the Atari LOGO programming language, either through the pointy clicky or the Alt+Shift+V shortcut. It works fine with Atari BASIC. Also from printing from within LOGO, or more specifically, SAVE "P: as the LOGO reference manuals suggest to dump the workspace to the printer, so I can copy it into a plain Windows text file. I'm sure it's pilot error on my part, but after chasing my tail for too long I decided to punt and SAVE "C: to the cassette device and then whip up a script to extract text from .CAS files. LOGO's such a memory hog that I'm trying to avoid sacrificing even 1KB to load a disk or host device driver, so, cassettes. Interestingly enough, when I attempt to paste text into LOGO, then give up and boot ATARIBAS.ROM without first shutting down Altirra, the text immediately pastes into BASIC, as if the pastes were waiting in a queue that LOGO doesn't read. If I try to paste into LOGO, then do a Warm Reset, Cold Reset, or Cold Reset (Computer Only) LOGO does read and display one character from the paste queue each time I reset. Any clues as to what's going on? Maybe LOGO interacts with the keyboard as a game might and polls a register instead of doing a blocking read? Thanks!

Version 3.90 of my emulator Altirra is out: http://www.virtualdub.org/altirra.html Thanks for everyone's continuing support, whether it be bug reports, feature requests, discussion, trying out the helper programs on real hardware, etc. 3.90 final is essentially the same as 3.90-test34, except for release changes. Although previous versions tended to be about six months apart, it's almost been a year since 3.20, so I figured I'd better hurry up. Highlights of the 3.90 release: Accuracy: 800 System Reset timing fixed, undocumented RMW and WSYNC timing fixes, several fixes to 65C816 direct page wrapping and Veronica, many fixes to FDC/RIOT/6809 for full disk drive emulation, improved POKEY two-tone mode emulation, more accurate power-up hardware state. Debugger: Improved disassembly window with automatic block separation and inline call target preview, more disassembly options, better loop detection in the history window, Alt+Shift+click to jump to history for a pixel. Disk drives: 810 Turbo, Amdek, and Percom AT-88 full emulation; easier file import/export in the Disk Explorer. Display: Improved PAL artifacting and color defaults, gamma-corrected frame blending, color setting import/export, PERITEL and monochrome monitor emulation, fixes to color correction logic (esp. with VBXE). Firmware: Updated AltirraOS 3.26 for improved compatibility with hardware addons and software, improved autodetection for custom OS ROMs. Tape: Faster emulation especially in warp mode, audio filter compensation for better turbo decoding, and enhanced debugging for tape issues. Video recording: Aspect ratio correction, scaling, and direct H.264/WMV compression support through Media Foundation. UI: Dark theme, improved audio monitor/scope, improved timing for slightly reduced latency. With 3.90 done, it's now time to start the 4.00 test series: http://www.virtualdub.org/beta/Altirra-4.00-test1.zip http://www.virtualdub.org/beta/Altirra-4.00-test1-src.zip First, there are a couple of breaking changes in 4.00: End of support for Windows XP SP3 and Vista. The new minimum operating system requirement is Windows 7 SP1. End of support for DirectDraw, which has not been native since Vista, and OpenGL, of which only old versions were used anyway (and was not enabled by default). New features and fixes: Palette solver: Matching color palettes in Altirra has been a long-standing issue, since it is unable to take .pal/.act files due to needing the generation parameters for the palette rather than the final colors for various features, and matching colors from real hardware is a difficult task. Pretty much everyone has their opinion on what "true colors" should be. Well, in 4.00-test1 there is now a solver to guess the parameters for you: You can either give it a PAL/ACT file, or you can give it a picture -- and although the picture needs to be a good one, it doesn't have to be perfectly straight as you can align it to compensate for projection by dragging the corner dots. It's compatible with any show-palette tool for the Atari that does 16 lumas across and 16 hues down. Click Match, and it'll start grinding on the parameters to try to get as close as possible, and tell you how good the match is. Or, you can have it overlay the current palette as dots over the picture to check the palette while manually tuning it. Debugger: On-screen watches now update continuously while stepping and the 'wx' command has options for hex formatting, bank-sensitive debugging is now supported for SpartaDOS X cartridges, improved handling of subdirectories when looking for source files, and the console output window is faster when flooded with output. Oh, and the Memory window has been improved with scrolling and more display options: Display: Added pure white monochrome mode, and fixed a bug in the high artifacting engine where chroma artifacts moved in the wrong direction for ascending hues. XEP-80: Fixed an emulation bug in the way that scrolling occurs, and added a couple of new toys to the Additions disk: an XEPVHOLD.COM tool to reprogram the XEP80's timing chain for a shorter display that's less likely to roll on modern displays, and a new ultra-speed ALTXEP8U.SYS driver that runs at symmetric 31.5Kbaud instead of 15.7K or 31.5K send / 15.7K receive. Tape: Added support for KSO Turbo 2000. Disks: Added emulation for the Percom AT88-SPD, and added 1791/1795 FDC selection for the AT-88. Fixed support for virtual SpartaDOS disks with directories and files whose names start with periods. Added a polling workaround option for virtual disks for environments where file change notifications don't work (some Wine environments). Audio: More accurate emulation of uneven volume bits, and rewrote cycle-level filtering emulation for improved high frequency aliasing rejection during downsampling. UI: Dark mode now has reskinned buttons. Added support for auto-hiding the menu bar. Fixed mouse wheel scrolling when the OS page-at-a-time option is on. H: device: Lifted 16MB limit for binary (untranslated) access, and fixed errors not being returned properly during burst I/O accesses. AltirraOS 3.27: Fixes to the printer handler for EOL handling, particularly for the Atari 1025, and improved compatibility of variable usage to work with Monkey Wrench II. Custom Devices: More scripting language constructs like break, while/do-while loops, and forward declaration of functions, better threading support, and more scripting methods for manipulating memory. Custom devices can now raise Parallel Bus Interface IRQs. Custom video outputs can now be created with either text or graphical output, and even support text select/copy like the emulator's built in ANTIC and XEP-80 video outputs. New sample custom devices: Bit-3 80 column, 1090 80-column, and a PBI-based metronome.

It was suggested to open a new thread, so here I go. Simply put, I'm trying to run Diamond GOS 3.0 with the utilities disk in Altirra 4.01. After some struggle I've gotten Altirra seemingly working, GOS boots, but when I install the utilities disk I only get this error. Current Altirra setup: Base system NTSC 130XE Additional Devices None OS Firmware Atari XL/XE OS ver.3 [29F133F7] Mounted Images Disk: Diamond GOS3 Utilities.ATR [93FCA643] Cartridge: DIAMGOS3.ROM [3671BDC5] I am brand new to this, so I don't know enough to know whether I'm making an Altirra mistake, a Diamond GOS mistake, or a general Atari computing mistake. The extent of my Atari computing experience is being fascinated by Basic Programming for the 2600 as a kid, and trying for the last few weeks to get this emulator working. I have never experienced the real hardware. I don't know whether the GOS manual left out a step that was too obvious to need explaining at the time, or if I've broken something that normally just works. Has anyone gotten this working in Altirra? Or if you've gotten it working on real hardware, is there something to the procedure that might not be obvious to a newbie who has only tried emulation? Thanks to anyone who can help. And thanks to this forum for saving GOS 3.0 from becoming lost.

Hello - I'm sure I cannot be the first to encouter this, but I cannot find anybody writting it up, not can I find a solution. I have a setup that works perfectly fine on actual hardware where I have a 130XE, U1MB, and a Side3 cart. On the SD card I have hard drive partitions, including a SpartaDOS 3 partition. With this configuration I can boot to SD3 on that partition and everything works swimingly. However, I have tried to replicate the configuration using Altirra and the SpartaDOS 3 partition will not boot. It does not tell me "NO DOS" or "BOOT ERROR", it goes directly into the internal self test menu. I can access all of the partitions on the SD card using SpartaDOS X on the U1MB. I have the latest firmwares on all devices, both in actual hardware, and in Altirra. I have also made an image of the physical SD card to use in Altirra, so I am certain that the card itself is not the issue. Has anybody else been able to boot a SpartaDOS 3 partition from a Side3 cart within Altirra? If so, how did you get that to work?

Is it possible to change the host keyboard mapping in altirra for the special Atari Keys? I use a program, where i have to press Ctrl-Esc on the Atari-Keyboard for a menu-line. The host key in Altirra for the ATARI "Ctrl+Esc" is "Ctrt+\" So with an english "QWERTY" Keyboard there is no problem. But i use a german keyboard "QWERTZ" in Windows. There is no single key fpr the backslash an i have to press "AltGr+ß" (ß is a special german letter). However, it is not possible to press Ctrl in addition to AltGr, on a german Windows keyboard layout. Consequently, it is also not possible to execute the ATARI key function "Ctrl+Esc" on a german windows keyboard layout. My wish would be to change the Atari keys mapping to the host keys mapping so i can use another key combination instead of "Ctrt+\". Is this possible?

I started back into 6502 assembler after a good 30+ years and wanted to use the tools I'm familiar with. That is VS Code as the editor. ATasm was the assembler of choice and Altirra the emulator. Now getting back into learning some 6502 had me dumping hex codes on the screen until I found out that Altirra has a nice debugger. Still I had no easy way of finding my code in the disassembly view, so I was padding the points of interest with nops etc. There had to be a better way. I found some topics here talking about debugging options in Altirra but there was no guide or documentation (none that I could find). At least the source code for Altirra is available and after getting it to compile and running, I managed to figure out the file format to get source level debugging to work. I modified ATasm to generate the required symbol and list files so that Altirra could load them. Then I wrote a VSCode extension to bring it all together. Now I can write my asm code, set a breakpoint in VSCode and launch the debugger and have it stop where I want it. The extension is called Atasm Altirra Bridge https://marketplace.visualstudio.com/items?itemName=cerebus.atasm-altirra-bridge

I have Altirra installed on my Windows PC. I've used the Atari800 emulator under Linux and it has the ability to change the speed of the Emulated 6502. Is there any such feature in Altirra? I was looking for something to speed up BASIC here and there. Plus some other applications would be nice to run a little faster. I did search for anything related to emulation speed, but I haven't found anything. Just looking for something pointing me in the right direction.

Convert Altirra Cheat Codes to Retroarch Cheat Codes for Atari 800 Games 1. Altirra Cheat Codes are saved as atcheats files. These text files include cheat name, hex address, hex value. 2. This cheat code information can be manually entered into the Retroarch Cheat Menu for Retroarch Handled data entry. See this weblink: https://docs.libretro.com/guides/cheat-codes/ 3. This method can be used to create and save Retroarch format cheat files that work for the libretro version of Atari800 (3.1) provided with the Nintendo Wii version of Retroarch. The Retroarch frontend software allows this older version of Atari800 to accept hex address cheat codes. 4. I am attaching a zip file with two cheat files for Jumpman (Epyx). Both use the hex address of $30F0 and the hex value of $06. Jumpman Cheats.zip

I've been playing with some code and using atasm to assemble it. Loading the code and using the Altirra debugger is ready easy, especially with the -l options to dump the labels to a file. As long as the labels file has the same base filename as the executable all is ok. The only thing missing from the joy was source level debugging; Altirra's documentation mentioned you had to use mads or xasm. But atasm is my tool of choice, so I pulled the source code and made the changes. If you assemble a file with the -l and -g options you will now get a .lst file that allows source level debugging under Altirra. Also added support for the ;##TRACE and ;##ASSERT diagnostics. If you assemble the above file with atasm 1.11 (https://github.com/CycoPH/atasm) and launch Altirra like this: Altirra.exe altirra.xex /debugcmd:.loadsym /debug you will see Altirra break into the debugger and showing you where the display list is located. Clicking Debug and selecting "Source file list ..." will give you altirra.asm as an option. Load it and you will have full source level debugging

Now that @phaeron released his latest 4.00-test43 source code, including the RMT libraries, more than ever, I would like to compile Altirra from source. Instead of asking Phaeron directly, I thought it would be nice to have a compilation guide here on AtariAge Has anybody, besides Phaeron, ever compiled it from source? Which compiler do I need? Is it free? Does it run on WINE? How hard do you think it would be to cross-compile with i686-w64-mingw32-gcc? Edit: answering two of my own questions: There's a free version of Visual Studio at https://visualstudio.microsoft.com/free-developer-offers/ Does it work on WINE? https://appdb.winehq.org/objectManager.php?sClass=application&iId=892 NO! Edit2: found two vcproj2cmake projects (1, 2) but both are very old. Now that VS integrates CMake more and more (https://docs.microsoft.com/en-us/cpp/build/cmake-projects-in-visual-studio?view=msvc-160, would it be possible to generate them from within VS?

Hi, i'm currently using atari800winplus4.1 which is quite outdated. I would like to switch to altirra, but I cannot use its debugger - i dont know how to. I also cannot get used to monitor commands and i hate when command window losts focus. is there any guide how to effectively use debugger in altirra with its unique features? i just found CHM file with brief description, but I would need something better, screen based... ideally video based. do we have something like that already?

SupeReversion This is a Reversi game I got from some magazine a while back. It's probably one of the best looking Reversi games on any 8-bit computer with it's 3-D style board. I made some modifications such as changed how the pointer works, displays in several random colors, boots from Altirra disk and improved the game play a bit. To play press Option or Select to change player then Start key to start. There is a flashing square you move in 4 directions to the spot where you want to place your piece using the joystick. Press the joystick button to set then piece down. You can play human v. computer, human v. human and even computer v. computer. Enjoy SuperReverse-ALT.atr

Version 3.20 of my emulator Altirra is out: http://www.virtualdub.org/altirra.html As usual, thanks for everyone who helped with testing, suggestions, criticism, analysis, and witty banter during 3.10's development. 3.20 is almost the same as the last 3.20-test release, except for a small bug fix (broken BASIC profiling option). Highlights since 3.10 (https://atariage.com/forums/topic/281825-altirra-310-released ) : Accuracy: Fixes to several cartridge types, VBXE, Black Box, raw Shift key handling. Disk: Fixes to address and data CRC error handling, non-standard sector size encoding support, ATX physical sector size chunk support, rotate disk now works with full disk drives. Debugger: Additional disk debugging features, bank-sensitive breakpoints and symbol lookup for AtariMax carts, deferred auto-loading of symbols, more Turbo-Basic XL debugging support, minor fixes to various commands. Devices: APE Warp+ OS 32-in-1 is now emulated, Ultimate1MB can soft-control stereo and Covox, fixes to some broken modem and CIO acceleration options. Display: Hardware accelerated effects support including distortion and bloom, new color preset for the NTSC 800 model, new overscan preset to match modern widescreen displays. Firmware: Updated to Altirra BASIC 1.56 with minor startup fix, AltirraOS 3.17 with fixes to the math pack, SIO, boot screen, and keyboard handler. Software: The ColorMap tool on the Additions disk now supports CTIA systems. UI: Easier enabling/disabling of portable mode, enhanced drag-and-drop support, system overview/recommendations, escaped text paste, Alt+click to decode BASIC PEEK/POKE addresses, mounted tapes and non-internal BASIC carts now persist, fixes to input state and console controllers in 5200 mode, bogus DOS/Windows executable detection, automatic BASIC/binary switching for tape boot. And per tradition, now that there's been a release, new test release: http://www.virtualdub.org/beta/Altirra-3.90-test1.zip http://www.virtualdub.org/beta/Altirra-3.90-test1-src.zip Experimental support for dark theme. This is hidden behind a /dark command line switch because it is incomplete due to a ton of really annoying restrictions in the OS (basically a total lack of actual dark support in the Win32 API), so I'm not sure if it's feasible to get it to a polished state, but it works well enough that I've left it on for my own development. Some UI elements like buttons and menus are not reskinned due to insufficient OS support (short of going ham on owner draw). Improvements to the debugger's Disassembly window. As seen above, it now has an option to infer and visually separate procedures, as well as hyperlinking and previewing JSR/JMP targets. This makes it possible to peek at the called procedure without losing your place. There are also go back/forward buttons. The history loop detector has been updated to more tightly identify loops, reducing the number of loose instructions in the trace. Disassembly options in the disassembly and history windows are now saved. Several debugger commands that take paths now accept "?" as the path, which causes the debugger to open a file dialog to browse to the desired file: .loadsym ? Accuracy improvements based on research into power-up state on actual hardware. Several registers have been tweaked to have more representative values, and the reset NMI on 400/800 models is now properly synchronized to vertical blank. WIP on new save state system. The format has been changed to a zip file with mixed JSON and named memory block files, which makes it much easier to pull out data with tools. The internals have been rewritten as well to better support in-memory saves and extensibility, the CPU save code can now save in the middle of an instruction, and standard disk drives can now save and restore a pending disk read operation. The plan is to gradually increase the amount of state saved, including device state that previously hasn't been saved. Note that saving to the v1 *.altstate format is no longer supported, although loading it still is, and this is still very new so I really don't recommend keeping your valuables in save states. Tape decoding and emulation code has been partially rewritten. The emulation-side of the tape decoder has been rewritten to be edge-based with much less host CPU load during tape operations, especially with acceleration on. There is also a prefilter option now to reduce phase shifts from high-frequency attenuation, which improves the reliability of turbo decoding of tapes archived using non-Atari tape recorders. The Add Firmware UI now has heuristics to detect 10K and 16K OS ROMs other than the specific Atari ROMs in the signature list, including custom OS ROMs. This helps detect when a ROM image appears to be another 16K ROM type is actually an OS ROM. AltirraOS updated to 3.20: XL/XE mode boot screen now continues boot instead of restarting when a disk is inserted for faster boot and preserving Option suppress-BASIC state, POKEY configuration changed to give more familiar sound during tape loads, QUICKED.SYS and SIDE Loader compatibility fixes, fixed background color in GR.11, fixed combined disk+rightcart and disk+tape boots. This ROM export package is attached for people testing this outside of the emulator. Also, deprecation notice: 3.20 will be the last major version of the emulator to support Windows XP/Vista. The plan is to release the next version as 4.00 with Windows 7 as the minimum OS. 3.90-test1 still currently builds with XP targeting but I will be changing over to the newer non-XP toolchain in the future. AltirraOS-3.20.zip

I have encountered some strange behavior while writing some Atari BASIC code. This little code snippet reads 34 bytes from Sector 1 of a disk and then prints them out. The code works under Altirra 3.90 as seen in the first picture but fails under A800WinPlus 4.x in the second picture. They are both trying to read the same disk but only one emulator is running at a time. I know someone out there will look at this and know exactly what the problem is but I cannot see it. Any ideas? det_sd.bas

This is a continuation of a thread started in the Emulation section about RetroArch that morphed into using ReShade with Altirra. I am trying to get ReShade Home (reshade.me) to work with Altirra in one of the DirectX modes. I can get it to work using OpenGL when installing ReShade and selecting OpenGL as the only api in Altirra. The problem is that OpenGL is too slow on the Atari VCS. I cannot get it to work if I install it as DirectX 9 or DirectX 10, 11 or 12 and selecting the corresponding DirectX in Altirra. Youxia was able to get it to work with DirectX 11 by somehow installing ReShade as OpenGL and then swapping to DirectX 11...but this method doesn't work for me. ReShade is working with Stella and DirectX so I'm hoping there is still a way to get it to work in Altirra.