You will not be able to post if you are still using Microsoft email addresses such as Hotmail etc
See here for more information viewtopic.php?f=20&t=7296
See here for more information viewtopic.php?f=20&t=7296
BOOKMARK THIS PAGE !
https://www.exxosforum.co.uk:8085/IP_CHECK/
You can unban yourself if needed. It also sends me reports to investigate the ban.
https://www.exxosforum.co.uk:8085/IP_CHECK/
You can unban yourself if needed. It also sends me reports to investigate the ban.
DO NOT USE MOBILE / CGNAT DEVICES WHERE THE IP CHANGES CONSTANTLY!
At this time, it is unfortunately not possible to whitelist users when your IP changes constantly.
You may inadvertently get banned because a previous attack may have used the IP you are now on.
So I suggest people only use fixed IP address devices until I can think of a solution for this problem!
At this time, it is unfortunately not possible to whitelist users when your IP changes constantly.
You may inadvertently get banned because a previous attack may have used the IP you are now on.
So I suggest people only use fixed IP address devices until I can think of a solution for this problem!
EMUTOS fast floppy loading ?
-
exxos
- Site Admin

- Posts: 28213
- Joined: 16 Aug 2017 23:19
- Location: UK
EMUTOS fast floppy loading ?
Does anyone know why EMUTOS is like a million times faster at loading stuff floppy than TOS is ?
-
ijor
- Posts: 825
- Joined: 30 Nov 2018 20:45
Re: EMUTOS fast floppy loading ?
I don't have much personal experience with Emutos but it should be faster, at least in many cases, because it uses a more efficient seek implementation. Original TOS uses FDC command Seek with Verify, and the Verify part doesn't help too much besides wasting one revolution per track.
http://github.com/ijor/fx68k 68000 cycle exact FPGA core
FX CAST Cycle Accurate Atari ST core
http://pasti.fxatari.com
FX CAST Cycle Accurate Atari ST core
http://pasti.fxatari.com
-
czietz
- Posts: 583
- Joined: 14 Jan 2018 13:02
Re: EMUTOS fast floppy loading ?
I was pointed to this thread and was asked to comment. (Sidenote: The mailing list might be a faster way to get EmuTOS developers to notice.) However, ijor already provided the answer; therefore, I can only add some further explanation here.
Atari TOS, for reasons unknown, uses a "seek with verify." With that command, after seeking to a track, the FDC waits for the first address mark (sector header) to verify the track number. On a normal floppy format, the track layout always has sector 1 after the index mark, followed by sectors 2 - 9. If you read consecutive sectors spanning more than one track, "seek with verify" means that one always misses sector 1 for reading (because it is consumed by the seek command). Therefore, one wastes one revolution of the disk per track.
EmuTOS does not set the verify bit for the seek command. You might ask: But isn't this dangerous if the drive ever seeks to the wrong track? Well, it isn't! Before reading or writing, the FDC verifies the track number again, anyway.
In fact, people used to patch the verify bit from Atari TOS, as discussed in the (German) Scheibenkleister book. This can also be seen for example in the (German) TOSPATCH program. Otherwise, you can also speed up loading by clever floppy formats (track layouts), as done by Martin Backschat's FastCopy.
Atari TOS, for reasons unknown, uses a "seek with verify." With that command, after seeking to a track, the FDC waits for the first address mark (sector header) to verify the track number. On a normal floppy format, the track layout always has sector 1 after the index mark, followed by sectors 2 - 9. If you read consecutive sectors spanning more than one track, "seek with verify" means that one always misses sector 1 for reading (because it is consumed by the seek command). Therefore, one wastes one revolution of the disk per track.
EmuTOS does not set the verify bit for the seek command. You might ask: But isn't this dangerous if the drive ever seeks to the wrong track? Well, it isn't! Before reading or writing, the FDC verifies the track number again, anyway.
In fact, people used to patch the verify bit from Atari TOS, as discussed in the (German) Scheibenkleister book. This can also be seen for example in the (German) TOSPATCH program. Otherwise, you can also speed up loading by clever floppy formats (track layouts), as done by Martin Backschat's FastCopy.
-
exxos
- Site Admin

- Posts: 28213
- Joined: 16 Aug 2017 23:19
- Location: UK
Re: EMUTOS fast floppy loading ?
Thanks for the replies. I didn't see it as a relevant topic for the mailing list, so didn't ask there.
I did see the same in the 206 sources..
But when I tried it, it didn't seem to make any odds. It's why I thought EMUTOS was doing something different. I will try it again to make sure.
EDIT:
OK so it is faster, just didn't notice then :roll:
Loading sysinfo from A:
206 normal - 32 seconds
206 FAST LOAD - 24 seconds
EMUTOS -25 seconds
ETOS likely was slower as for some reason running MAPROM caused the floppy to malfunction. So I tested without anything loaded which is likely where the slowdown came from. In otherwords, ignore the ETOS test :)
I did see the same in the 206 sources..
Code: Select all
#if TP_23 /* FASTLOAD */
moveq.l #$10,d6 /* execute 1770 "seek" */
#else
moveq.l #$14,d6 /* execute 1770 "seek_with_verify" */
#endifBut when I tried it, it didn't seem to make any odds. It's why I thought EMUTOS was doing something different. I will try it again to make sure.
EDIT:
OK so it is faster, just didn't notice then :roll:
Loading sysinfo from A:
206 normal - 32 seconds
206 FAST LOAD - 24 seconds
EMUTOS -25 seconds
ETOS likely was slower as for some reason running MAPROM caused the floppy to malfunction. So I tested without anything loaded which is likely where the slowdown came from. In otherwords, ignore the ETOS test :)
Who is online
Users browsing this forum: CCBot and 3 guests