Fix "map to device sector 0" option in CALL MAPDRV #151
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
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.
The
CALL MAPDRVBASIC command has an option to map a drive directly to sector zero of a device (for cases where the device doesn't have partitions and the FAT filesystem starts directly at sector zero), by specifying zero as the partition number. However this option wasn't actually working, it would always throw an "Invalid partition" error. This pull request fixes that.Note that this bug was in the
CALL MAPDRVBASIC command only, the command line toolMAPDRV.COMalready works as expected.