Skip to content
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.1 beta 2 #102

Merged
merged 5 commits into from Mar 22, 2022
Merged

v2.1.1 beta 2 #102

merged 5 commits into from Mar 22, 2022

Conversation

This new BASIC command works the same way as the old CALL SYSTEM, but it will always load MSXDOS2.SYS even if NEXTOR.SYS is available. This helps getting back some TPA memory, since MSXDOS2.SYS is smaller than NEXTOR.SYS, but at the expense of not being able to use the Nextor-exclusive function calls (so tools like e.g. MAPDRV.COM won't work).
Change the mechanism to access mounted files from file based to sector based.

- A new restriction is introduced: a file needs to be stored across consecutive sectors in disk in order to be mountable.
- Message for error .ICLUS has been changed from "Invalid cluster number" to "Invalid cluster number or sequence".
- New BASIC error code introduced: code 82, message "Invalid cluster sequence".
- The _GDLI function call will now return two extra values for a drive that has a mounted file: "start cluster" and "start sector"
Add a new KILLDSKIO environment variable to disable DSKI$ and DSKO$

When set to "on", the 512 byte buffer for DSKI$ and DSKO$ won't be allocated, and the commands will be disabled.
@Konamiman Konamiman added the release Release branch label Mar 22, 2022
@Konamiman Konamiman added this to the v2.1.1 beta 2 milestone Mar 22, 2022
@Konamiman Konamiman self-assigned this Mar 22, 2022
@Konamiman Konamiman merged commit 413810c into v2.1 Mar 22, 2022
@Konamiman Konamiman deleted the v2.1.1-beta2 branch March 22, 2022 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Release branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant