-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wouldn't it be nice to have a client a2pi*.s on the GS? #6
Comments
Yep. That is the network name of my IIgs.
The machine detection is already in the startup program. It only differentiates between the ][+ and later models. I just never wrote a IIgs client because it wasn't high on my priority list and I don't have the correct serial cable (and I secretly hate the IIgs )
|
Yep, I finally found all the bits on the project. I'll add a little more discriminating detector and a pigs file. After one year - it seems you have your first IIgs customer. (and I secretly hate the IIgs ) |
First pass implemented in pull request #7. It will be interesting to consider the case where an Apple II Pi card (with 6551 chip) is inserted into a GS. I'm not sure how we would autodetect the card vs. an SSC card vs. the native serial SCC serial port(s) - and correctly decide which to use. We might have to let autodetection fail in that case and ask the user to choose which driver to use (6551 vs. SCC-based). |
So, there's a2pi.s and a2piplus.s. I guess a GS version would be a2pigs.s. Some basic questions... how do the .s files get assembled (I assume by Merlin), how do they get invoked at the client end (I assume there is some init code in startup), and the coolest thing would probably be to autodetect which machine it was on and pick the appropriate client.
The text was updated successfully, but these errors were encountered: