Implementing phantom floppy drive in device-based subsystem #42
Assignees
Labels
enhancement
New feature or request
fixplemented
This bug has already been fixed/this feature has already been implemented in a released version
Comments
Merged
|
Final version of Nextor 2.1.0 will provide a proper PROMPT routine for this purpose. |
Konamiman
added
enhancement
Konamiman
added a commit
that referenced
this issue
Jul 26, 2020
- Fix: broken RAM disk (introduced in RC1). - Fix: disk errors for old MSX-DOS 1 file functions in BASIC crash the computer (#59). - Add: new flag returned by LUN_INFO allows to instruct Nextor to ignore devices when searching devices for automatic device to drive mapping (#54). - Fix: files can't have 3 or 4 in their names in DOS 1 mode (#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 (#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 (#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 (#57). - Fix: absolute sector read/write functions not working properly when a file is mounted to a drive (#43). - Fix: bad sector buffer management when writing to a mounted file causing data corruption on the mounted file (#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 (#45).
Konamiman
added
fixplemented
|
Fixed in v2.1.0 (PROMPT routine made visible, and "ignore when auto-assigning" flag in LUN_INFO) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As I understood from conversation with Nestor that phantom drive and "Insert the diskette form drive X:" must be implemented in driver for device-based configuration. If DEV_STATUS will be called as polling then it will cause driver to display unexpected "Insert the diskette" messages if DEV_STATUS is called for phantom driver and back.
Thus I need confirmation that DEV_STATUS is called only when kernel wants to perform I/O access of specific logical drive.
In general the message "Insert diskette" and related routines are present in both DOS1 and DOS2 kernels of Nextor, and it would be logical to reuse them in device-based configuration.
The text was updated successfully, but these errors were encountered: