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.

Sign up for GitHub

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

Jump to bottom

_MAPDRV mount disk image - buffers from RAM on write not save to disk. #58

Closed
mr-GreyWolf opened this issue Jun 3, 2020 · 2 comments
Closed

_MAPDRV mount disk image - buffers from RAM on write not save to disk. #58

mr-GreyWolf opened this issue Jun 3, 2020 · 2 comments
Labels
bug Something isn't working fixplemented This bug has already been fixed/this feature has already been implemented in a released version

Comments

@mr-GreyWolf
Copy link

Nextor kernel version 2.1.0 beta 2
NEXTOR.SYS version 2.10
COMMAND2.COM version 2.44

Buffers from RAM on write not save to disk.
Example:

  1. I mapped floppy disk image(size: 737280 bytes) by commands:
_MAPDRV("B:","A:BASIC_PG\BASIC.DSK")
_CHDRV("B:")
  1. I saved file from BASIC, file successful saved and viewed by by command FILES.
  2. I reboot machine but file on disk image is not found...
    I viewed this image on PC and found this file content, but file name in FAT table is missing.
@Konamiman
Copy link
Owner

Konamiman commented Jun 14, 2020 •
edited
Loading

Hello, I'be been able to reproduce not this exact bug but a similar one: after creating a file with copy con on a mounted file, the file gets apparently created, but then trying to display the file contents with type gives garbage. Clearly there's something wrong when writing to mounted files. Thanks for reporting!

@Konamiman Konamiman added the bug Something isn't working label Jun 14, 2020
@Konamiman Konamiman mentioned this issue Jul 10, 2020
Merged
@Konamiman Konamiman added the due in next version This will be fixed/implemented in the next version label Jul 11, 2020
Konamiman added a commit that referenced this issue Jul 26, 2020
@Konamiman
v2.1.0: post-RC1 fixes (#61)
ab66c7d 
- 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 Konamiman added fixplemented This bug has already been fixed/this feature has already been implemented in a released version and removed due in next version This will be fixed/implemented in the next version labels Aug 1, 2020
@Konamiman
Copy link
Owner

Fixed in v2.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working fixplemented This bug has already been fixed/this feature has already been implemented in a released version
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Konamiman @mr-GreyWolf