Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

*Suggestion* 250vb waiting time after access to disc #23

Open
Nju79 opened this issue Dec 9, 2021 · 1 comment
Open

*Suggestion* 250vb waiting time after access to disc #23

Nju79 opened this issue Dec 9, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@Nju79
Copy link

Nju79 commented Dec 9, 2021

Hi there,
In the documentation for every AmiBlitz version, it is strongly recommended to wait around 250 vertical blanks after accessing a drive before switching to Blitz mode. The reason for this should be that drive accesses can still occur within this time.

I find this waiting time very annoying, especially when I just want to quickly reload something from floppy disk or hard drive. I've seen numerous other games not have this waiting time and are able to stop the drive when they finish loading data. This not only applies to assembler or C games, but also to AMOS games (e.g. the newly released Shadows of Sergoth).

I assume that AmiBlitz has no such function, e.g. to stop the motor/access of a floppy/hard disk drive "immediately"? Would it be possible to implement such a function in AmiBlitz?

Best regards

@honitos honitos added enhancement New feature or request and removed investigation labels Apr 1, 2022
@daedalus2097
Copy link

It would be interesting to see what those examples do in this situation. Waiting 5 seconds is probably related to booting from floppy, and to using a hard drive with old (1.x) versions of the OS which had a delayed cache flush. It's pretty simple to turn the floppy drive motor off, there's a motor control function in trackdisk.device so maybe a command library to handle low-level trackdisk.device (or generic #?.device) commands would help? It's a difficult thing to do safely though - with a multitasking OS, drive access can happen at any time due to another program, including within that 5 second wait period.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants