drac030 Posted May 10, 2020 Author Share Posted May 10, 2020 10 minutes ago, ebiguy said: maybe you have some kind of include file that you use for compiling SDX code or toolkit that you would be willing to share Sure, here is the file you need: page7.icl But these are just the labels for the reverse-engineered source, the truly "official" ICD labels were different. This is not yet, er, integrated. 1 1 Quote Link to comment Share on other sites More sharing options...
ebiguy Posted May 10, 2020 Share Posted May 10, 2020 Thank you very much, Nothing has changed since the last version I had. Quote Link to comment Share on other sites More sharing options...
Mr Robot Posted July 13, 2020 Share Posted July 13, 2020 Has anyone got a copy of the add-ons written by mono? The page linked on the SDX website http://sdx.atari8.info/index.php?show=en_addons is a 404 now Quote Link to comment Share on other sites More sharing options...
JR> Posted July 13, 2020 Share Posted July 13, 2020 might be archived.... https://web.archive.org/web/20200110104736/http://mono.atari.pl/ Quote Link to comment Share on other sites More sharing options...
Mr Robot Posted July 13, 2020 Share Posted July 13, 2020 a couple of them were but mostly just 502 Bad Gateway Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted July 14, 2020 Share Posted July 14, 2020 (edited) you're correct, perhaps there is backup? Someone surely has them all... Edited July 14, 2020 by _The Doctor__ Quote Link to comment Share on other sites More sharing options...
mono Posted July 14, 2020 Share Posted July 14, 2020 (edited) My projects are available at http://mono.i-demo.pl now. Edit: I'll ask trub about fixing links. Edited July 14, 2020 by mono wrong url 2 2 Quote Link to comment Share on other sites More sharing options...
Mr Robot Posted July 14, 2020 Share Posted July 14, 2020 Thank you @mono, I'm so glad your hard work hasn't disappeared forever! @mono I notice a program called edx is still being created, any idea when there will be a release? I'm looking for just such a tool Quote Link to comment Share on other sites More sharing options...
Jacques Posted July 22, 2020 Share Posted July 22, 2020 Did someone manage to somehow enable quick transmition for Atari 1050 with "1050 turbo" (by B. Engl) or its Polish clone (Top Drive 1050)? SIO.SYS or INDUS.SYS don't recognize it, and it would be nice to have turbo speed, not only normal Quote Link to comment Share on other sites More sharing options...
drac030 Posted August 16, 2020 Author Share Posted August 16, 2020 @Jacques I remember that there was some TTD.SYS in the past which was intended to enable the Top Drive turbo protocol in SDX. Maybe it is time to dig it out or recreate. But the problem is that my Top Drive 1050 does not work any more, so I can hardly see how such a driver could be tested. And, for a different topic: some time ago someone reported that the alias feature in DOSKEY in SDX 4.49 does not work. I cannot find that post now. Anyway, here is a version attached that is hopefully fixed. To use it: 1) unpack (ARC X DOSKEY), then copy to the desired destination drive/directory, e.g. C:>BIN> 2) in your CONFIG.SYS file, add or edit the line which loads the DOSKEY program bundled with the 4.49. If it says, f.e. DEVICE DOSKEY C:>ALIASES.INI replace it with DEVICE C:>BIN>DOSKEY C:>ALIASES.INI (or whatever are the paths to these two). 3) reboot DOSKEY.ARC 5 Quote Link to comment Share on other sites More sharing options...
+Nezgar Posted August 17, 2020 Share Posted August 17, 2020 (edited) @drac030 If I am not mistaken, the 1050 Turbo used the same tops highspeed protocol - and tf_hh sells replicas of it. I have one myself - working on NTSC too. Not in highspeed with SDX though, as the highspeed handler has to load from the drive when booting with no disk in the drive. This was the novel upgrade that did true double density in a 1050 with no additional RAM - just the stock 128 bytes in the 6532 + 128 in the 6810, and a whopping 8KB ROM to allow for creative ways to work with basically no stack in RAM. Edited August 20, 2020 by Nezgar 8KB ROM, not 32KB ROM... Quote Link to comment Share on other sites More sharing options...
Jacques Posted August 17, 2020 Share Posted August 17, 2020 5 hours ago, Nezgar said: @drac030 If I am not mistaken, the 1050 Turbo used the same tops highspeed protocol - and tf_hh sells replicas of it. I have one myself - working on NTSC too. Not in highspeed with SDX though, as the highspeed handler has to load from the drive when booting with no disk in the drive. This was the novel upgrade that did true double density in a 1050 with no additional RAM - just the stock 128 bytes in the 6532 + 128 in the 6810, and a whopping 32KB ROM to allow for creative ways to work with basically no stack in RAM. The whole idea is to enable highspeed via driver under SDX, not via Turbo 1050 / Top Drive firmware (which also does not work with SDX, from my experience). @drac030 I'll search for TTD.SYS, maybe will be able to find it on the Internet Quote Link to comment Share on other sites More sharing options...
drac030 Posted August 17, 2020 Author Share Posted August 17, 2020 10 hours ago, Nezgar said: the 1050 Turbo used the same tops highspeed protocol Yes, I know. 10 hours ago, Nezgar said: Not in highspeed with SDX though, as the highspeed handler has to load from the drive when booting with no disk in the drive. As you certainly realize, the point is to provide a (relocatable) *.SYS driver which would functionally replace that handler. 5 hours ago, Jacques said: I'll search for TTD.SYS I have found it. It does not work (at least under the emulation). Quote Link to comment Share on other sites More sharing options...
Jacques Posted August 17, 2020 Share Posted August 17, 2020 (edited) 6 hours ago, drac030 said: I have found it. It does not work (at least under the emulation). So it might be similiar or even the same as TOMS.SYS (TOMS Turbo) driver I found elsewhere, that didn't work too. TTD can stand for Toms Turbo Drive, I guess(?) Edited August 17, 2020 by Jacques Quote Link to comment Share on other sites More sharing options...
lemiel Posted August 18, 2020 Share Posted August 18, 2020 (edited) On 8/17/2020 at 3:58 PM, drac030 said: Yes, I know. As you certainly realize, the point is to provide a (relocatable) *.SYS driver which would functionally replace that handler. I have found it. It does not work (at least under the emulation). Please do that driver in way that it is on way that supports other connected drive types and turns on turbo only for selected drives numbers. Something that Hias wrote about original 1050 Turbo driver. Will try to find that topic and paste link to it here. And so on... Edited August 18, 2020 by lemiel Typo autotype on phone. Quote Link to comment Share on other sites More sharing options...
drac030 Posted August 19, 2020 Author Share Posted August 19, 2020 We already have something that trub says work on real hardware. But on Altirra's generic emulation (File -> Disk drives -> 1050 Turbo) it does not, and I do not have the required firmware image to setup the exact emulation. So nothing to download this time, until we are sure where the problem (visible under the said emulation) is. 1 Quote Link to comment Share on other sites More sharing options...
+Nezgar Posted August 20, 2020 Share Posted August 20, 2020 On 8/19/2020 at 9:07 AM, drac030 said: I do not have the required firmware image to setup the exact emulation. I just dumped the 2764 EPROM from my Turbo 1050 replica. Attached. A quick test in Altirra 3.90-test10 worked with "1050 Turbo II disk drive (full emulation)" It did not work when selecting "1050 Turbo" - had to be "1050 Turbo II" - I wonder the difference? Turbo_1050_1988_B_Engl.BIN 1 Quote Link to comment Share on other sites More sharing options...
Jacques Posted August 20, 2020 Share Posted August 20, 2020 All original "1050 Turbo" EPROMs' dumps from the era can be found here: https://www.strotmann.de/~cas/Infothek/1050Turbo/ ( software_1050_turbo.zip ). 2 Quote Link to comment Share on other sites More sharing options...
drac030 Posted August 20, 2020 Author Share Posted August 20, 2020 @Nezgar and @Jacques thank you very much. I will give it a shot today's evening. The driver in its current state is here: http://sdx.atari8.info/sdx_files/test/topdrv.sys It for now allows to define just one drive as Top Drive 1050, but it is no problem to make it accept more, if there is need. 1 Quote Link to comment Share on other sites More sharing options...
lemiel Posted August 21, 2020 Share Posted August 21, 2020 Please do. E.g. for copying from Turbo drive to SIO2SD, etc. I know, rare use cases but possible. Quote Link to comment Share on other sites More sharing options...
drac030 Posted August 21, 2020 Author Share Posted August 21, 2020 Does not SIO2SD support UltraSpeed? Quote Link to comment Share on other sites More sharing options...
lemiel Posted August 21, 2020 Share Posted August 21, 2020 Yes it does. Quote Link to comment Share on other sites More sharing options...
drac030 Posted August 22, 2020 Author Share Posted August 22, 2020 So what's the use again? Stuff can be copied from a drive in TopDrive mode and to SIO2SD in US mode, I guess. Quote Link to comment Share on other sites More sharing options...
lemiel Posted August 22, 2020 Share Posted August 22, 2020 TopDrive on D1: and TOMS Turbo Drive on D2:. But yes, very rare conditions. Quote Link to comment Share on other sites More sharing options...
drac030 Posted August 22, 2020 Author Share Posted August 22, 2020 In that case for now you can load TOPDRV.SYS twice, once for D1:, the second time for D2:. And for the future, I guess then, that it will be sifficient, if the driver allows to assign D1-D4 as 1050 Turbo drives? 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.