-
-
Notifications
You must be signed in to change notification settings - Fork 477
Fixes #6220 floppy disk issues with OS/2 and NT 3.1 systems #6232
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…to motor-on loop.
Updated README to reflect the new project name and added details about the Immersive86Box features and future plans.
…he files and intallation instructions
Added instructions for audio emulation installation.
…e operation and when it's finished at call fdc to set the appropriate fdc flags. Also added time logic to fdd to calculate seek duration and a callback function for it.
DISABLE_FDD_AUDIO definition added, to disable the feature via cmake/build.
This reverts commit 98a0478.
This reverts commit 7d32cb6.
…ill take the "correct" amount of time for each system and the seek time is based on the track count. E.g. 40 track FDD system causes 40 track seek time to be 80/40 * 6ms * 40 tracks + 50ms = 480ms + 50ms -> 530ms. 80 track system full seek is 80/80 * 6ms * 80 + 50ms = 530ms, 40 track seek would take 240 + 50 = 290ms.
Fixed PS/1, PS/2 and PS/55 FDD issues.
…ow found there, looks in the executable directory
Feature/fdd 5.25 drive sound
FDD audio timing/volume tunings
…even_when_it_gets_no_more_accesses Fixed second drive motor keeps running when first drive is only accessed
…ly accessed." This reverts commit 307b173.
Teac 5.25" drive sounds added and FDD settings audio selection is now drive specific
…disk issues. Changed the fdc->stat bit to 0x10 which states fdc busy. Previous implementation with seek time 0, set the ready flag 0x80 immediadely - which was correct for that time, but now as the drive is busy during seek, the value should 0x10. Implemented a backup for fdd commands during fdd seek to be processes after the seek is completed.
Contributor
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.


Summary
OS/2 Warp 3.0 had an issue with loading the setup from disk01, the FDD/FDC got into a seek loop / reset loop. Issue was the OS/2 was sending read sector command during FDD seek. I changed stat flag to 0x10 to state that the FDD/FDC is busy during seek and created a backup in the FDD to enqueue any request it received during seek and process them after the seek has finished.
Tested with:
Checklist