Jump to content

JAC!

+AtariAge Subscriber
  • Content Count

    2,042
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by JAC!

  1. "I found the described source code for this game" - that is the most surprising part for me - I never thing these things when I search for them :-). Looking forward to see the code how you use the VBXE.
  2. This tools will create the required signature and header to turn a valid ROM file (e.g. 1 MB Atarimax) into a corresponding CAR file. This way the emulator knows the banking scheme and that the file is integer. Means: If you have solved your problem of creating the ROM, the tool will help ou run it. What do you mean by "multiple.xex to several banks"? And which type of cartdige are you aiming at? Creating a sequential XEX loader which loads from the ROM is fairly easy to do. Start with the first byte on the first bank and "stream" the next byte into the loader until your're done. Provided the XEXs themselves don't use the $A000-$BFFF area (at least not during loading).
  3. The Atari 800 emulator and Altirra 4.10 have added support for 5 new cartridge types: 71 for Atari 5200: Super Cart 64 KB 5200 cartridge (32K banks) 72 for Atari 5200: Super Cart 128 KB 5200 cartridge (32K banks) 73 for Atari 5200: Super Cart 256 KB 5200 cartridge (32K banks) 74 for Atari 520: Super Cart 512 KB 5200 cartridge (32K banks) 75 for Atari 800/XL/XE: Atarimax 1 MB Flash cartridge (new) Therefore I've also added support for these cartridge types to Atari ROM Maker and Atari ROM Checker.
  4. The Atari 800 emulator and Altirra 4.10 have added support for 5 new cartridge types: 71 for Atari 5200: Super Cart 64 KB 5200 cartridge (32K banks) 72 for Atari 5200: Super Cart 128 KB 5200 cartridge (32K banks) 73 for Atari 5200: Super Cart 256 KB 5200 cartridge (32K banks) 74 for Atari 520: Super Cart 512 KB 5200 cartridge (32K banks) 75 for Atari 800/XL/XE: Atarimax 1 MB Flash cartridge (new) Therefore I've also added support for these cartridge types to Atari ROM Maker and Atari ROM Checker.
  5. Hi Avery, after a long time I've had the chance to do something Atari related and add support for the new cartridge types 71-75 to my code. These two make the 4.10 build dump. Probably something's also wrong with them, but the result should not be a dump. UPDATE: I've debugged the startup sequence of the 5200 and fixed three things in my code. - YEAR+1 is set to $ff (diagnostic cart) now, to skip the slash screen as it has no use and no valid year anyway. - Code is now on the right (initial bank). - Initialization of ZP pointers is correct. Still these two updates one trigger the minidump. - Peter. Super Cart 128 KB 5200 cartridge (72).car Super Cart 256 KB 5200 cartridge (73).car
  6. Sorry, but I'm still in the process of making the logic parts work and creating real unit tests for them. This weekend I've completed the parts dealing with keeping the disassembly listing in memory (finally no linked lists anymore) and the logic to save it to .asm files in the different forms (one file, one file plus one include, main file with all includes, main file with chained includes). This gives me the confidence that for all of this, I'm really done and don't have to touch it again. In other words: I am not yet on the UI layer and the link between the different controls doesn't work yet. In the original code, there basically every control calling every other control. I want to change that to a regular MVC approach, so I can ultimately also test the UI logic without clicks.
  7. Yes, I've also received support from Thomas Scott Giese who has provided fixes and some good ideas. And besides that I keep on adding tests primarily. I haven't pushed a new binary though.
  8. The platform setting in DIS6502 defines which system equates files are loaded. The 2.2 version supports selecting Atari 5200 as platform via the command line: DIS6502.EXE /5200 In the 3.x version this was changed to /ATARI800, /ATARI5200, /ORIC,.... There you can also choose the platform when creating a new workspace.
  9. Update: Selecting, loading individual disk sectors from 90k (SD) / 130k (ED) and 180k (DD) now works again. The first 3 sectors of DD images are assumed to be 128 bytes.
  10. File handling of the input stream and the pasers for reading XEX and other file types has been revised. Now, instead of simply returning "false" and a generic error message like "is corrupted or contains more then 4096 segments", you now get a specific error message for every error situation. The texts are not yet great, but there is a different text not for every error which should already be helpful. With this instrumentation you can see that in the sample file given above there is a file with broken DOS file links (corrupted file) and one which is valid file, but not a valid XEX file with and $FFFF header. The last file loaded was OK, so no error message. Daily is updated. UPDATE: Name of the inner EXE and number sectors are now also output in the status message and the message texts have been revised already. Note that adding freely selected sectors does not yet work. That's next.
  11. Haha, thanks for pointing me to the "box of pandora"... the code for handling ATR files and DOS 2.5 file systems. I had never really used that (only tested .XEX/.BIN) and ended up reworking it completely now. It is now complemented with a set of unit tests that will test 8.3 filename conversion, read 3 reference ATRs, compare the directories, compile the file sizes and contents with the reference content. So in case there anything still does not work, it can now be found quickly. Also all file related dialogs require much less code now. https://sourceforge.net/p/dis6502/git/ci/master/tree/src/systems/atari800/AtariDiskImageTest.cpp Daily is updated.
  12. Hello Marco. Today I've managed to fix the bug when reading old workspaces, I was able to load a large example and click around. The new daily is uploaded to https:/www.wudsn.com/productions/windows/dis6502/dis6502.zip . If you find something, please send a PM.
  13. Finally a sign of life from project. Over 60 commits took place meanwhile. Still most of the work is under the hood, yet I feel this is worth sharing. The following may seen simple, but it was a long hard way from DOS plain C with pointers and fixed array sizes everywhere and logic interwoven with WIN32 API calls and UI parts .. to the code without fixed limits (number of segments, size of labels, ..) , without char pointers and instead with standard libararies and the lasted C++ 20 features (type inference, bounds checking). But what does that mean?? This means I can now finally write tests for all the essential parts and run them automatically, instead of clicking though the UI. This will bring back the confidence in that all the changes have the correct results, simplify tracing and fixing bugs and it will help make the project more and more stable over time.
  14. Great video! I see really many things you can really be proud of. The space rescue is especially nice for me, with the different screens using different graphics and skills. And for those games where you think speed is the issue, you could run them though a BASIC compilers to get decent results without changing anything/much.
  15. Anwser: On new Mac OS you have to use the 64 bit version. See mads.macos-x86-64 on https://github.com/peterdell/wudsn-ide-tools/tree/main/ASM/MADS
  16. Only possible thanks to skr who lend me his MacBook since the Fujiama party.
  17. i386 is the 32 bit version. Monterey will not run 32 bit applications anymore from what I know. I recented started to create new builds. Check mads.macos-x86-64 on https://github.com/peterdell/wudsn-ide-tools/tree/main/ASM/MADS
  18. Wow, feels like Christmas - all of these are absolutely incredible. Thanks you guys for these masterpieces!
  19. Hello Marco. Sorry nothing new here. Visiting Fujiama and SillyVenture parties was the only Atari related thing my job allowed me to do this year. Hard to believe one year has already passed...
  20. Yes, that is really the problem. The .exe simply wraps the .bat file, it it was version information, icons etc. In case of problems, you can run just the .bat file.
  21. Atasm does not generate the required information in the files. You need to use MADS. Converting from ATASM to MADS is easy. See the FAQ in the WUDSN IDE. Edit: Just saw you are referring to a new version. I have not seen that yet. Probably it is most effektive if you contact Mark directly.
  22. ad 1/2) Menu Window/preferences. What & where the assembler outputs depends on these settings. ad 3) That is exactly the .lst file in case of ATASM and MADS
  23. Implemented with https://github.com/peterdell/wudsn-ide/commit/3db927c9f196bcd105dcceb98d3197bf506426d2. Will be included in the next build. Would you mind creating a feature request on github for this? I'd like to learn how that works and how an I tag a feature request with the commit.
  24. There is no seting. I think here font loading forthe Atari TTF font from the plugin does not actually work for some reason. Can you provide a screen shot and the context of the ".metadata/.log" file. I had already figured out that with newer X-Code versions, you have to install the Command Line Tools separately and add the path the lib. See function compileWithFPC() in https://github.com/peterdell/wudsn-ide-tools/blob/main/make.sh
×
×
  • Create New...