Jump to content
Have You Played Atari Today?
2600|5200|7800|Lynx|Jaguar|Forums|Store  

atarimac

Members
 View Profile  See their activity

  • Content Count

    219

  • Joined

  • Last visited

Posts posted by atarimac

  1. Posted

    @KlasO, the step you need to allow you run FDISK is for the SIO Patch to be disabled as shown in the screenshot below.  It is intercepting the SIO calls the PBI Bios is making to detect the disk.   In a future release there may be a way to make them play together, but my easy attempts have failed, so I will probably need to replace the SIO Patch that is in the atari800 emulator with something more like what Altirra uses.  

     

    For the next release (which will be 6.0, with ARM Mac Native support), what does everyone think?  Leave it as is?  Disable it if Ultimate1mb and SIDE2 are both present, or warn the user if it is enabled and Ultimate1mb and SIDE2 are present?

     

    1993530653_ScreenShot2021-01-10at10_46_47AM.thumb.png.175a0f245a46fd46ce1185fdb77c5bd1.png

    • Thanks 2

  2. Posted

    I've found the issue.   It's the SIO Patch.  It's not compatible with the PBI Bios, and that's why it doesn't work from SDX in Ultimate1mb.  So please turn it off in the Preferences/Atari Tab.

     

    This may have been mentioned in an earlier post, and I have been running with it off, but must have turned it on in testing.

     

    The atari800 core SIO Patch won't work, and at some point I may try and use something like Altirra does, but in the next release, I will be turning it off if Ultimate1mb and SIDE2 are enabled.

    • Like 1

  3. Posted

    Your right, the format commands do need to be used carefully.  What I omitted in a rush to respond, was the first command:

     

    sudo hdik test.img

     

    will return on the console the name of the disk that was mounted, in other words, /dev/disk3, in the example I used.  You are correct, in that with other disks that number would be different.  Once you have that name, then you can use it in the second command.  So if it returned instead say /dev/disk4, then in the second command, assuming that the FAT partition you want to format is the first one, you would use /dev/disk4s1 instead.   The same goes for ejecting the image with the last command.  

     

    This is covered in the "Handle Hard Disk Images" help page in the application, and includes the caveat about disk number.

     

    If Apple is depending on resource forks in this case, it is a bad decision.  Windows knows nothing about resource forks, they don't exist there, nor extended attributes, and this is a file format that originated there.  VHD files have a header, that they have to read to be able to process it, and it has magic numbers so it can't be misidentified.  The strange part is they will happily do that if it has the WRONG extension for the format, .img, but will not do it for the correct one, .vhd.

  5. Posted

    I just released an updated version 5.5.1 which has a very small fix for the correct SIDE2 hard disk mounting (RAW or VHD) based on the image name.  (.vhd and .img are mounted as VHD, anything else is mounted as RAW, along with images named .vhd or .img which fails to mount as a VHD image).

    • Like 1
    • Thanks 1

  7. Posted

    I will see if @flashjazzcat will chime in for the reason, as my expertise on the Ultimate/SIDE2 is pretty basic.

     

    But, I believe you need to run FDISK from the SIDE2 SDX image, not the Ultimate1mb SDX image.  So in the Ultimate1mb configuration, you will need to enable the SDX Cart ROM, then issue a CAR command from the Ultimate1mb to run the SIDE2 SDX image.  The alternative is to just insert the SIDE2 in a 1088XL machine in the emulator to do the formatting.

     

    You should then see the device when you run FDISK.  But.......I just found out there is a bug in the Hard Disk Image creation/mounting on the Mac that escaped due to a last minute change that didn't get tested.

     

    To explain, I need to diverge.   Apple sometimes makes silly decisions in my opinion, and this is one of them.  A Mac will mount a VHD image if you double click on it,  however, the Mac won't mount the image if it has a .vhd extension.  It has to have a .img extension.   So, I changed the image creation code to name newly created files with a .img extension to handle this.   The problem is, I forgot to change the Image mounting code in the SIDE2 emulation, so it ends up mounting it as a RAW image instead of a VHD.   To fix this for now, you can rename the image file extension to .vhd to mount it with the emulator. 

     

    I'll issue a 5.5.1 bug fix release soon to fix the mounting issue.

     

    By the way, the Mac will mount the VHD image if it has a .img, but it also has to have a valid file system the OS recognizes.  Well that's a catch 22, since how to you get the FAT16 formatted then?

    So, as another hint if you want to format that FAT16 partition in the image (test.img for this example) that you have created on the Mac, you can do these commands (of course after making it test.img instead of test.vhd if you changed it):

     

    sudo hdik test.img

    sudo newfs_msdos -F 16 /dev/disk3s1

    sudo hide -e /dev/disk3

     

    You will need to press the ignore button in the dialog that pops up after the first command.

     

    Then, you can double click to mount the image and copy files to the FAT16 partition to be used by the SIDE2 loader.

     

     

     

     

     

     

    • Thanks 1

  8. Posted

    New Features (in version 5.5.0):

    • Added support for the PCLINK host disk system, providing a working alternative to H: for SpartaDOSX.
    • Added enhanced copy and paste, so that ATASCII graphics characters may be copied and pasted as well, along with support for automation with delays.
    • Added ability to specify a string that is pasted automatically at the startup of the emulator.
    • Added Break key to Touch Bar, and removed Power key. The funtionality of the Power key is now achieved by pressing Shift along with the Reset Touch Bar key.

    Bug Fixes (in version 5.5.0):

    • Fixed copy of text in Full Screen
    • Fixed copy of text in 80 column modes

     

    You can get the release here: https://github.com/atarimacosx/Atari800MacX/releases or http://atarimac.com/downloads.php .

     

    Note, for PCLink to work, you need to have the PCLINK.SYS driver available on the SpartDosX Toolkit disk.  PCLINK use is documented under the Preferences->Hard Drives Tab section in the built in help.

     

    The Copy and Paste is documented under the Copy and Paste topic in the built in online help.

    • Like 12

  9. Posted

    @curtludwig, there is a sub-menu under the control menu.  This allows you to choose what happens when you press the Mac Arrow keys.  If you choose "Arrow Keys Only", it will give you the *, +, etc that correspond to the Atari keys only without control, which I think is what it sounds like you want with Ultima II.

    • Like 2

  12. Posted

    I think I found a quick fix for the SIO Patch issue with Ultimate1mb/SIDE2.  What it does is in the patch, if the SIO address of the drive is outside of the range of D1-D8 or C:, it calls the original OS routine to handle it (not accelerating it).

     

    I've given @jc13 a test version of it, if anyone else is having this issue and would like to help test the fix, let me know and I will send you a link.

    • Like 1

  15. Posted

    I've released a quick bugfix release of Atari800MacX.  I'm working on implementing PCLINK and an enhanced Copy/Paste for the 5.5 release, but it is taking a bit longer that I thought, so I thought I would get these fixes out.  I didn't even realize the mouse emulation had the inverted axis issue, but ran into it from a comment by someone in an Atariage forum recently.

     

    Bug Fixes (in version 5.4.4):

    • Fix issue with Trackball and Mouse emulation. The Y Axis was inverted, making Trackball emulation of little use. By default, the Y Axis is now inverted, but an option has been added to the Controllers tab of Preferences which allows the original behavior.
    • Fix issue with not being able to sector edit an ATR image that does not contain a supported DOS.

     

    http://atarimac/downloads.php

    https://github.com/atarimacosx/Atari800MacX/releases/tag/Release_5.4.4

    • Like 4
    • Thanks 2

  16. Posted

     Bob,

    Yes, I agree on the Universal binary, and I've been trying to keep the code base in good shape to do that.  As soon as someone in the community gets one, I can start to see if I can build one.  (I suspect I will need to have at least one machine on Big Sur at that point).  The plan on my side is to start a 6.x version at that point, that may coexist for awhile with 5.x versions, we will see.

     

    The next release will have PCLINK so that modern Sparta Dos's can get to an H: like device.  After that, probably SIDE3, parts of FujiNet, and who knows. 

  17. Posted

    I will probably modify Atari800MacX to use file length as well (at least for the emulator portion, I will probably leave the ATR Image editors as they are).  And I understand the early design decisions.

     

    @darwinmac I will let you know when I make the change.  I will probably not do an official release for just this change, I'll give you an Alpha build of the next version for it.

  18. Posted

    @darwinmac and @hlabrand, I have found why the emulator is returning SIO errors, which I'm sure is what is causing the emulator to fail. The ATR Header in the image indicates that the disk image is 720 sectors long, but looking at the file length, subtracting the 16 byte ATR header, it is 1076 128byte sectors long.

    Atari800MacX uses the ATR header to determine the sector count, and so when the program tries to read a sector greater than 720, it gets returned an SIO error.  As to why Altirra and SDrive Max do not return errors, it may be they use the file size for sector count instead of expecting the header to be valid.  I can ask phaeron, I didn't find it at a quick look at the Altirra code.

    I've fix the issue darwinmac was seeing, by using a hex editor on the file.  The 3rd and 4th bytes were 0x80 and 0x16  (0x1680, since th header wants the number of 16byte section, this is 720 sectors), and I changed them to 0xA0 0x21 (1076 sectors).  I can send the modified file to @hlabrand if desired.

  20. Posted

    @kogden, as Mathy said, there is an Alpha version of SIO2OSX that I compiled to be a 64 bit app, but unfortunately it does recognize SIO2PC hardware.  I'm not able to test it, as I don't currently have a working SIO2PC adapter, and one of my two Atari computers also did not survive my move.   I won't say never, but with the additional time needed for teaching in a COVID environment, and some health issues, I don't have time to get HW working and debug SIO2OSX.  The source is open source, if anybody has the time or means to look at it (https://github.com/atarimacosx/Sio2OSX ).

  22. Posted

    All,

    I've released a quick bug fix version for Atari800MacX with the following fixes:

     

    Bug Fixes (in version 5.4.3):

    • Fixed issue with initial setting of Ultimate1mb and SIDE2 Preferences if they have not be set before.
    • Fixed issue with Atari 800 Bounty Bob Strikes Back cartridge.  It still conflicts with the 😧 and H: patches so those will have to be turned off for the cartridge to work.

     

    Since Ultimate1mb/SIDE2 is the main focus of the 5.4.x series, I wanted to get this out here as it's harder for people to try out that feature with the bugs that were in the initial ROM setup.

     

    Mark

    • Like 6

  23. Posted

    I found the issue with Bounty Bob Strikes Back 800 Cartridge version.  It has to do with my need to move the D:, H:, and R: patches such that they don't conflict with Ultimate1mb.  I moved them to the GTIA area, and apparently, just like they do with POKEY and ANTIC, the authors used mirrored addresses in that area as well.  I restored the mirrored addresses if the patches are not enabled, but they will need to be turned off to run that cartridge.  Update will be in the 5.4.3 release, most likely tomorrow.

  24. Posted

    Mathy,

      Thanks for letting me know, I've had weird problems with the security updates before as well.....or the image got corrupted twice which is weird.

     

    Everyone,

       I did find several issues with entering the Ultimate1mb and SIDE2 file preferences for the first time.  I will release a 5.4.3 sometime later this weekend, but I wanted to see if I or anyone else found any other issues.

AtariAge
Forums
Store
General
Follow AtariAge

Copyright ©1998-2021 AtariAge

×
×
  • Create New...