Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Groups keyboard shortcuts have been updated
Dismiss
See shortcuts
Crossrunner
79 views
Skip to first unread message
Ian Brumby
Dec 27, 2023, 5:30:11 AM12/27/23
to
Crossrunner, a brand new Apple IIGS emulator, is available now.
Currently available for Windows.
Mac and Linux beta testing starting soon.
https://www.crossrunner.gs
Currently available for Windows.
Mac and Linux beta testing starting soon.
https://www.crossrunner.gs
Jeff Blakeney
Dec 27, 2023, 7:07:14 AM12/27/23
to
out at some point but when the download finished, Chrome told me that it
detected a virus.
fadden
Dec 27, 2023, 1:56:29 PM12/27/23
to
On 12/27/2023 4:07 AM, Jeff Blakeney wrote:
> Just downloaded it with Google Chrome on my Windows 10 machine to try it
> out at some point but when the download finished, Chrome told me that it
> detected a virus.
I got the usual "unsigned executable" warning, but no viruses detected.
> Just downloaded it with Google Chrome on my Windows 10 machine to try it
> out at some point but when the download finished, Chrome told me that it
> detected a virus.
Also using Chrome on Win10.
Jedi Mindtrick
Jan 2, 2024, 10:22:00 AM1/2/24
to
Wonderful to see a new emulator for the IIgs! I am especially excited about the debugging capabilities! I have been using ORCA with Golden Gate as my development platform, and it has been great, but debugging natively with GSBug, is clunky at best. I downloaded 1.01 and ran my code in the full emulation more, with no issues, other than some problems with getting keypresses from the number-pad, on my PC keyboard. I then tried out setting up the debugger, using the Debug and CompatibilityLayer switches and I saw my code, with the source! Oh happy day!
Well, now to some questions, as I am having a few issues when running in the debug mode. The first question would be, that I am assuming that when the CompatibiliyLayer is in effect, not all Toolbox calls are working? Maybe similar to Golden Gate, where just the basics are functional? i.e. Things like`_QDStartup`, just result in a BRK getting hit. I was able to skip doing that, as I was only using QD to turn on the graphics, however I seem to have run into some other issues with the CompatibilityLayer. I hate to file bugs for these, without some additional information about the state of the layer, in case I'm just doing some things incorrectly, or they are not supported.
Two things I noticed so far is that calling `_NewHandle`, to get a block of memory at a specific location, required me to set the `attrBank` flag, as well as the `attrAddr` flag, I don't believe the former should be necessary, when requesting a specific location. With just the attrAddr flag set, the `_NewHandle` call succeeded, but did not return a block at the address I requested ($012000). That was a quick workaround, however, I am stuck trying to read from a file. I used the `_OpenGS` call to open a file at prefix 9, then called `_GetEOFGS` to get its length. Both of those worked fine, but then calling `_ReadGS`, fails, returning a $27, which is a generic I/O error.
Let me know if you think I should just post these at issues on your Github repository.
I am really looking forward to using the debug capabilities of the emulator, and am happy to help out if needed.
-Ken
Well, now to some questions, as I am having a few issues when running in the debug mode. The first question would be, that I am assuming that when the CompatibiliyLayer is in effect, not all Toolbox calls are working? Maybe similar to Golden Gate, where just the basics are functional? i.e. Things like`_QDStartup`, just result in a BRK getting hit. I was able to skip doing that, as I was only using QD to turn on the graphics, however I seem to have run into some other issues with the CompatibilityLayer. I hate to file bugs for these, without some additional information about the state of the layer, in case I'm just doing some things incorrectly, or they are not supported.
Two things I noticed so far is that calling `_NewHandle`, to get a block of memory at a specific location, required me to set the `attrBank` flag, as well as the `attrAddr` flag, I don't believe the former should be necessary, when requesting a specific location. With just the attrAddr flag set, the `_NewHandle` call succeeded, but did not return a block at the address I requested ($012000). That was a quick workaround, however, I am stuck trying to read from a file. I used the `_OpenGS` call to open a file at prefix 9, then called `_GetEOFGS` to get its length. Both of those worked fine, but then calling `_ReadGS`, fails, returning a $27, which is a generic I/O error.
Let me know if you think I should just post these at issues on your Github repository.
I am really looking forward to using the debug capabilities of the emulator, and am happy to help out if needed.
-Ken
0 new messages