Version 0.92 is now available from the download page: https://partitionlogic.org.uk/download/
... and a bunch of other improvements to the Visopsys OSOverview: This maintenance release introduces usability and stability improvements, fixes RAM disk boot support, adds sparse file and 64-bit support to the EXT filesystem driver, and includes a number of bug fixes.
- Added support for 64-bit EXT filesystems (read-only, as before).
- Added support for sparse files to the EXT filesystem driver.
- Fixed some problems with the RAM disk boot feature, first introduced in version 0.85.
- Updated the ‘edit’ Text Editor program to add ‘New’ and ‘Save As’ menu items, bringing it more in line with conventions used by other editors. When invoked without a filename or creating a ‘New’ document, the ‘Save’ menu item is disabled. Use of a temporary file for unsaved documents has been discontinued.
- Updated the administration.conf files for German, Spanish, Russian, and Turkish.
- Factored some code in the BIOS OS loader and fixed some rounding errors.
- Added a lock to the freeEntries list in kernelFile.c.
- Added locking to directory fileEntry structures when adding to or removing from their lists of entries.
- Renamed the floppy image file to include the word ‘floppy’.
- Fixed: A SATA driver problem with VmWare’s virtual SATA disks. There was an error in the setting of SATA AHCI DMA modes during initial disk enumeration.
- Fixed: Problems with Jpeg loading and/or image resizing when creating thumbnails or clicking on multiple images. In a number of cases, thumbnails were created, but the View program would report an error trying to load them.
- Fixed: When booted from a read-only filesystem (CD), pressing PrtScn could cause a page fault, and error messages on the console saying “Filesystem is read-only” and “Unable to open [file] for writing”.
- Fixed: When mounting a new filesystem, it would appear before the other, alphabetically-sorted, items in a directory listing. The most recently mounted filesystem was always being inserted as the first entry in its mount point’s parent directory, because the file name had not yet been set.