pedgarcia #1 Posted January 29, 2020 I have an SDrive2 which I never could boot a SpartaDOS 3.2 with it. Is there a limitation that such device is not compatible with SpartaDOS? I tried the same version with emulators and they work fine. What am I missing? Thanks Quote Share this post Link to post Share on other sites
+Nezgar #2 Posted January 29, 2020 SpartaDOS 3.2 negotiates the ultraspeed protocol with drives, originally the 1050 US Doubler, at a non-configurable 54000bps when engaged. The S-Drive max also supports the ultraspeed protocol, but at a configurable rate, which may be too fast for your system if you haven't done modifications to remove speed limiting capacitors from your computer. I have limited experience with the S-drives, but I have toyed with a configurable highspeed index setting in the bootable menu, try changing the value which might default to something like $06 to something slower like $0A or $10. Quote Share this post Link to post Share on other sites
tschak909 #3 Posted January 29, 2020 SpartaDOS's high speed code really falls apart at speeds higher than US Doubler's 0x0a divisor. For a contrast, use the high speed code in the U1MB PBI BIOS. -Thom Quote Share this post Link to post Share on other sites
TGB1718 #4 Posted January 29, 2020 8 hours ago, tschak909 said: For a contrast, use the high speed code in the U1MB PBI BIOS Have to differ on that, when I write to SDX floppys on SDrive Max I get constant errors, reading disks is fine. I just found out (yesterday) if I turn HSIO OFF, the disks are still accessed at high speed, but I don't get any errors. Was thinking about raising a bug report on this Quote Share this post Link to post Share on other sites
flashjazzcat #5 Posted January 29, 2020 26 minutes ago, TGB1718 said: I just found out (yesterday) if I turn HSIO OFF, the disks are still accessed at high speed, but I don't get any errors. I've noticed that the HSIO code doesn't much care for intermediate divisors with SIO2PC, at least when using SDX (divisor 3 or so, IIRC), despite the fact there are no issues at divisor 0. I checked Hias' original patched OS and behaviour was identical, so it doesn't appear to be a PBI implementation issue. 1 Quote Share this post Link to post Share on other sites
pedgarcia #6 Posted January 30, 2020 Thanks all. Changing the value to 0x0a worked, apparently with no errors. As a complete noob, took me a while to understand what HSIO OFF meant, but I think I've got it. Doing that, the SPX disk actually booted two, but since the other value also did, I will stick with that. Cheers! 2 Quote Share this post Link to post Share on other sites