Jump to content
drac030

SpartaDOS X 4.49 (release version)

Recommended Posts

Allowing to assign to D1-D4 is ok.

 

Those loading multiple times would extend memlo every time with full HS code? - Just asking to be sure.

  • Like 1

Share this post


Link to post
Share on other sites
On 8/20/2020 at 5:33 PM, drac030 said:

@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.

You're welcome, I'm happy to assist and test.

Finally I've found time to do so and can report following:

 

1) highspeed reading works

2) highspeed writing works (tested only creating directory)

3) FORMAT with SDX internal tool works (DD 180KB, SDX format) - at first had an error with apparently damaged diskette.

  • Like 1

Share this post


Link to post
Share on other sites

Meanwhile I've done two RWTEST runs on same Turbo 1050 disk drive and same disk:

 

1) TOPDRV.SYS - ATARI OS

 

20200823_175421.thumb.jpg.1a063440b24e2bb08df23241de0fb81e.jpg

 

2) QMEG built-in UltraSpeed (F) used under SDX via SIO.SYS /A

 

20200823_175647.thumb.jpg.4f927988518a677d2190d394ce1fd269.jpg

 

It's great with TOPDRV.SYS to have standalone driver now, I'm just wondering, why QMEG's UltraSpeed is even slightly quicker, while 1050 Turbo / Top Drive theoretically can run at 68,2 kbps and UltraSpeed at 57,6 kbps (3xSIO)? ;)

 

Edited by Jacques

Share this post


Link to post
Share on other sites

@lemiel Yes, of course.

 

@Jacques It is probably the sector interleave which is decisive here, that is why there is virtually no difference. The tiny difference you are observing is probably due to a 1 extra VBL tick which occurs due to extra time consumed on transfer setup in Atari OS routines which QMEG possibly saves or something like that.

Edited by drac030
  • Thanks 1

Share this post


Link to post
Share on other sites

@Jacques how it could be UltraSpeed in Turbo only drive? It is also Turbo. Bad name. Only 3 bytes per second faster QMEG in reading... Not possible with bigger difference between 09 and 06 POKEY divisor. 

Edited by lemiel
Typo

Share this post


Link to post
Share on other sites
46 minutes ago, lemiel said:

@Jacques how it could be UltraSpeed in Turbo only drive? It is also Turbo. Bad name. Only 3 bytes per second faster QMEG in reading... Not possible with bigger difference between 09 and 06 POKEY divisor. 

 

Errrmmm,

 

as far as I know QMEG has built-in drivers for Speedy 1050 (ultraspeed), Happy 1050 (warp+ultraspeed), US-Doubler (ultraspeed), Turbo 1050 (turbospeed) and XF551 (XF highspeed). So whenever QMEG sees a Turbo 1050 it uses turbospeed and NOT ultraspeed...

 

Share this post


Link to post
Share on other sites

But QMEG is NOT SIO2SD, in QMEG the letter N = normal speed, F = fast speed; where fast speed can be ultraspeed, warpspeed, turbospeed or XF-highspeed. Stefan did not want to use several letters, so he chose only two, one for normal speed and one for fast speed...

 

  • Thanks 1

Share this post


Link to post
Share on other sites

If you have an Incognito, U1M, XEL or 1088XLD, I'd use Jon's BIOS HighSpeed option. It is basically Hias code. I patched it to support the new SDX 4.49 INDUSX.SYS. This is SuperSynch w/ track buffering and a lower (faster) divisor.

Share this post


Link to post
Share on other sites
10 hours ago, lemiel said:

@Jacques how it could be UltraSpeed in Turbo only drive? It is also Turbo. Bad name. Only 3 bytes per second faster QMEG in reading... Not possible with bigger difference between 09 and 06 POKEY divisor. 

Maybe there could be an option to change POKEY divisor by TOPDRV.SYS driver in similiar way, original 1050 Turbo  / Top Drive does?
I just wonder if it's possible to extract those 68,2 kbps under SDX...

Share this post


Link to post
Share on other sites

So QMEG is autodetecting speed and speeder type like Hias did in his code. 

Everything clear now. 

 

@Kyle22 where is that patch?

And new Indusx.sys still needs patch? I thought that @trub incorporated buffering in it.

 

@Jacques it is 68,2k in Turbo mode. 

Share this post


Link to post
Share on other sites
19 minutes ago, lemiel said:

where is that patch?

It's in the U1MB or Incognito firmware menu. 'SIO and CIO drivers'. Enable the HSIO option and apply it to whatever range of devices and drives you want.

Share this post


Link to post
Share on other sites
8 hours ago, Jacques said:

Maybe there could be an option to change POKEY divisor by TOPDRV.SYS driver in similiar way, original 1050 Turbo  / Top Drive does?
I just wonder if it's possible to extract those 68,2 kbps under SDX...

What you are seeing *IS* 68.2kbps - the sectors are indeed transferring at this speed, but without track buffering there is a lot of latency between requesting each sector, the drive reading it from the disk, and the drive transmitting it. This loses more than half the "theoretical" max in rwtest.

 

Interestingly, the interleave formatted by Turbo 1050 can also be read fullspeed by a usdoubler at 54Kbps, slightly faster than the "ultraspeed" interleave commonly laid down by spartados formatters.

 

The very small difference seen here between the two drivers could just be within the random variance you may see with multiple runs, or as simple as RPM variance with the drive warming up and spinning a little faster...

Share this post


Link to post
Share on other sites

Thank you. The disk I was doing RWTEST on was formatted under TOPDRV.SYS using SDX's format program. How to format it to get most out of it without buffering, then?

Normally on Turbo 1050 / TOP DRIVE re-reading other drives' disks and writing given disk-side again dramatically increases reading-speed.

Share this post


Link to post
Share on other sites

@Jacques Every floppy drive during formatting a disk puts the physical sectors on every track in a characteristic order (known as "interleave" or "sector skew") which should be (and most often is) optimal for the bitrate and rotational speed the drive is using. This is the factor which is decisive when comes to reading/writing efficiency. Inserting a disk with wrong interleave usually causes dramatical speed decrease (or no improvement when comparing to 19200 bps).

 

Also, in most drives the interleave is fixed by the firmware and cannot be changed. Some drives support the US Doubler format command which allows to tune the interleave, others (as Indus/LDW/CA, TOMS) are programmable, so in theory one could also format a disk on them with custom interleave. Most drives, though, simply use the optimal interleave for the selected formatting mode.

 

http://atariki.krap.pl/index.php/Przeplot

 

I hope that this is what you wanted to know :)

Edited by drac030
typos

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...