-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
v2.1.0: post-RC1 fixes #61
Merged
Merged
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
The problem was that these routines ececute from bank 4, but when the disk error hooks take control they expect bank 0 to be active.
The LUN_INFO function can now return a new flag that when set will cause Nextor to ignore the device+LUN combination when searching for suitable devices to perform automapping.
- Fix: after booting pressing 3, CALL SYSTEM doesn't work. - Fix (hopefully): slot disable keys not working on real machines.
Also, NEXBOOT tool now accepts "*" parameter, to disable all Nextor kernels in the next boot.
…edia change if the driver provides drive mapping via DRV_CONFIG.
…ut has the "ignore for automapping" flag.
When using 7BB0h there's only room for 16 bytes, but the DPB is 19 bytes, thus an incorrect one was being used.
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.
Fix: broken RAM disk (introduced in RC1).
Fix: disk errors for old MSX-DOS 1 file functions in BASIC crash the computer (Call to BDOS from the DOS2 driver ends nowehere #59).
Add: new flag returned by LUN_INFO allows to instruct Nextor to ignore devices when searching devices for automatic device to drive mapping (Impossible to implement phantom drive properly #54).
Fix: files can't have 3 or 4 in their names in DOS 1 mode (In DOS1 mode files with certain extensions can't be found/loaded #55).
Fix: after booting directly yo BASIC by pressing 3, CALL SYSTEM doesn't work.
Fix: slot disable keys don't work on real MSX computers (Slot keys do not work? #49).
Add: new boot key, pressing
N
at boot time disables all the Nextor kernels present.Add: default DPB gets a fixed address of 7BAAh in banks 0 and 3, so it can be customized reliably.
Add:
PROMPT
routine made available to drivers at address 41E8h (Implementing phantom floppy drive in device-based subsystem #42).Fix: the DOS 1 variables "data buffer changed" and "redirect console output to printer" were not zeroed when switching to DOS 1 mode at boot time.
Fix: can't change volume name when there are long filename entries in the root directory (Cannot change volume name by command VOL - System file exists #57).
Fix: absolute sector read/write functions not working properly when a file is mounted to a drive (Nextor shouldn't block sector I/O to MAPDRV drives when FAT12 disk images are used #43).
Fix: bad sector buffer management when writing to a mounted file causing data corruption on the mounted file (_MAPDRV mount disk image - buffers from RAM on write not save to disk. #58).
Fix: drive parameters not updated on first access to a drive after a media change if the driver provides drive mapping via DRV_CONFIG, causing bad data read (Device-based removable media replacement problem #45).