FX CORE (1.20) no longer working with SDX 446 the new SVBXE101 drivers..
Yeah, the new drivers explicitly check for FX core 1.21 or higher. The only new feature I can see in the 1.21-1.24 cores is the shared/nonshared memory bit, the rest of the changes being bug fixes. Here's a version that emulates FX core 1.24 and will work with the new driver.http://www.virtualdu...-2.30-test1.ziphttp://www.virtualdu...0-test1-src.zip
I am loving the faux Amiga Workbench disk prompt!
After seeing JAC's 1.3 prompt, I couldn't resist doing the 2.0 version. I was waiting to see who would recognize it.
It's real, btw... if you stick in a disk, it'll boot. Haven't got around to testing it on real hardware, but it just uses regular SIO calls.
To asking a question about the bios that comes with the emu. Which OS revision is it largely or loosely based on, pre XL, XL or XE And how close (from an emulation PoV) is the bios to the OS revision it is based on (percentage wise)
The built-in OSes are written from scratch but are based primarily on the spec in the Atari OS Manual, with additions from the XL Addendum and a few specifics from Mapping the Atari (to aid with naughty programs that don't follow the official specs). The LLE and LLE-XL ROMs target OS-B and XL/XE/XEGS level functionality, respectively. The HLE OS targets both at the same time, since it can cheat with C/C++ code. There is also an U1MB placeholder OS that is based on the LLE-XL ROM. The OSes work well enough to boot DOS, SpartaDOS X, the various cartridge/device flashers, and a decent selection of games.
In terms of functionality and compatibility, they're at about 75%. Breakdown per section (LLE):
- Boot/init: 70%. There's some pollution between OS-B and XL/XE boot behavior I need to work out.
- SIO: 80%. Base functionality is implemented, but retry logic and cassette support is incomplete. Type 3 polling is missing.
- CIO: 90%. Supports all major functionality as well as some undocumented calls, but lacks some permission checks.
- S:/E: device: 70%. Fine scrolling is not implemented, some vars are in the OS-B place instead of XL/XE place, graphics reads are incomplete, and it still takes too much ROM space.
- P: device: 0%. Not a high priority since Altirra's printer support is intercept based and it doesn't implement an SIO-based printer.
- K: device: 90%. All the main pieces are there, just waiting for something else to break.
- C: device: 20%. Reading is implemented but still has problems... no writing support at all.
- Math pack: 70%. Basic functionality works enough for Atari BASIC to run, but it cuts some corners on rounding to save on code size and has some differences in error behavior.
- Parallel Bus: 40%. SIO block devices work, but interrupts are untested (no such devices are emulated). PBI-based CIO devices and relocatable handlers are not yet supported.
- Interrupts: 90%. Almost everything is in. VBI doesn't handle 400/800 ports 3 and 4 correctly (uses XL/XE behavior) and I'm not sure anyone cares about the GINTLK check.
- Undocumented bogus entry points: 5%. Most software that uses non-official entry points will fail.
100% compatibility won't be possible -- there is too much naughty software out there -- but the goal is to at least hit full compatibility with well-behaved software, including BASIC and DOS.
The 5200 LLE BIOS has a much higher compatibility rate simply because the 5200's OS barely does anything. I'm not sure there are any official games left that don't run on it.
Lastly is there a section within the manual that refers to making MaxFlash images with Altirra, as well as images that can be used with these other i/o devices that are emulated (i.e Myide etc) and what kind of data can be put on these images (i.e atr/xfd/xex/atx etc etc)
All the help there is is in the help file.
For MaxFlash images, you can run the flasher disks within Altirra and "flash" a virtual ROM image out of it, but you can't actually build the flasher disks or ROM images from sources. For that you need external software like the official Atarimax software.
XFD images only allow for single and medium density floppy disks and no protected disks. ATR images support all densities (SD/MD/DD/512b), no protected disks. DCM supports SD/MD/DD, again no protected disks. ATX supports single density only but does support storing many types of disk protection, including missing sectors, duplicated sectors, bad CRCs, and weak sectors. PRO only supports single density and doesn't really store disk protection information properly -- it stores information about the load pattern of the program rather than what's actually on the disk -- so it shouldn't be used for any new images.
32-bit version seems to keep crashing (i.e. a Windows app crash) when I have Ultimate 1MB enabled. If I start the emulator, open the debugger, then press F8, the whole thing crashes. I can't get the machine to boot with U1MB enabled either, even if the debugger is closed (although in that case, Altirra simply locks up).
That's serious, even if it is due to a broken ROM image. 6502 code should never be able to hard crash the emulator. If you have the .mdmp file available, I'd appreciate it if you PM'ed it to me so I can fix the problem.
file name can not start with a numeral.... only alphanumeric ..
Yup, this is a MyDOS problem. The H: device allows such filenames isn't even getting called in this case. Could be that someone used a tool to create the disk with names that are invalid for MyDOS.