Dosdev #3347
Merged
Dosdev #3347
Conversation
This file contains 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
2 tasks
leecher1337
added a commit
to leecher1337/dosbox-x
that referenced
this pull request
Oct 9, 2022
…g breaking changes to get joncampbell123#3347 working again (MEM_BlockWrite MUSTN'T be called on ext device, otherwise it overwrites buffer which causes malfunction)
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.
This pull request fixes the handling of DOS file I/O device drivers
What issue(s) does this PR address?
There are some device drivers that expect a pre-filled input-buffer on READ function (3Fh) and also don't like to be called for every single byte in that buffer. Therefore the current implementation doesn't work correctly for them.
Therefore to do proper buffer transfers, the device driver should be called directly with the correct buffer pointer in place which also eliminates unnecessary copying.
The current code also has a bug that it lets the buffer point to the beginning of the DCP, which is not desirable, because:
dosbox-x/src/dos/dos_devices.cpp
Line 138 in 6533d69
but:
dosbox-x/src/dos/dos_devices.cpp
Line 101 in 6533d69
0x20 & 0xF = 0!