Alfred Posted December 29, 2018 Share Posted December 29, 2018 I say ignore everything but SpartaDOS versions. The more SpartaDOS specific things get, the more people will migrate to SpartaDOS and maybe start to make it the Atari standard deveolpers use, and therefore, everyone uses. It's got a menu tree for those that don't like command-line Atari DOS. I'm sick and tired of half the stuff coming out being for Sparta and half for DOS 2.5 compatibles which are so much inferior anyway. I left them behind as much as I could back in '86 when I first got the SpataDOS construction set with my 1050 US doubler. Now I have to duck down to avoid the fodder surely headed my way by MyDOS and other users... Why ? Unless it's a disk backup program or something like that, most programs should be generally unaware of what DOS is resident. I don't see any reason why Platoterm should give a sh!t what DOS is being used as long as it's configured to have a MEMLO under $2000, which I think DOS 2.0 and it's clones can do. Quote Link to comment Share on other sites More sharing options...
tschak909 Posted December 29, 2018 Author Share Posted December 29, 2018 The problem with the mouse and trakball drivers literally stem from the fact that they conflict with the serial driver, which both use POKEY IRQs. The affected mouse/trakball drivers need to be rewritten NOT to use POKEY IRQs. The developers of the driver code used in CC65 didn't take into account that many years after they were written, some crazy jagoff would try to use mouse and serial I/O at the same time. -Thom 4 Quote Link to comment Share on other sites More sharing options...
mr-atari Posted April 12, 2019 Share Posted April 12, 2019 For any one, who wan't to try, I created a patched PLATO version doing 2400 BAUD. You can find it on my SIO2WiFi-page. It supports the stock ESP8266-WiFi modules. That need a long TTY before you are connected to the server.... http://www.mr-atari.com/Mr.Atari/SIO2WiFi/ Enjoy, Sijmen. 2 Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted April 12, 2019 Share Posted April 12, 2019 The problem with the mouse and trakball drivers literally stem from the fact that they conflict with the serial driver, which both use POKEY IRQs. The affected mouse/trakball drivers need to be rewritten NOT to use POKEY IRQs. The developers of the driver code used in CC65 didn't take into account that many years after they were written, some crazy jagoff would try to use mouse and serial I/O at the same time. -Thom make a request to have that changed... Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted April 12, 2019 Share Posted April 12, 2019 Or turn off mouse movement when using the SIO. Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.