The following is a summary of the improvements in version 2.55, compared with
version 2.04. This list is designed as a guide for current users of version
2.04.
 | General
 | the background colour of dialogs has been changed to light grey for
readability |
| CD devices are now detected and omitted from display and selection
(e.g. in the 'All info' table) |
| devices on buses other than the standard Atari ACSI/SCSI/IDE are now
accessible (through the use of the SCSIDRV interface) |
| the AP_TERM message is now handled |
| the 'Edge' icon, used in 'About', 'Preferences' and 'Mirror', now has
a 4-colour version for correct display in medium-resolution |
| in the 'multiple' dialog, when doing a 'clear all', only objects that
are currently selected are redrawn, reducing screen flicker |
| the help files have been updated, and you can now scroll through them
backwards as well as forwards
|
|
| Medic
| for consistency, lost clusters are now displayed as errors in the
medic map, and a list of the lost cluster numbers is written to the
medic log file |
| for invalid folders or FAT errors, the medic log now contains more
precise information |
| the run time of the 'map bad' function has been reduced by speeding up
the internal compare memory routine |
| in the 'map bad' function, if write errors occurred when testing
FAT/root sectors, the previous code still attempted to write the
FAT/root when creating a new file system. the errors are now displayed,
and no attempt is made to create the FAT/root |
| in 'map bad', if write errors occur due to the disk being
write-protected, the user is now informed via an alert
|
|
| Partition
| partition sizes are now validated before the new partition table is
written to the disk |
| the function of the 'TOS x.xx' button has been changed: it now rotates
through 1.00/1.04/4.00, and its setting controls the checking of
partition sizes |
| the function of the 'Maximum' button has been changed: it now
generates either GEM or BGM maximum-size partitions, depending on the
currently-displayed TOS version in the same dialog
|
|
| Utility
| when Zeroing a drive, if the save of the Unzero information fails, the
user is notified |
| when Zeroing a drive, if the Unzero information is being saved to the
drive that's about to be Zeroed, the user is notified
|
|
| Print file
| the system remained busy for an excessive time if printing was
requested while the printer was offline; this situation is now detected
and reported via an alert
|
|
| View file
| the file viewer has been completely rewritten and now supports
scrolling backwards as well as forwards |
|
| Medic
| the 'fix collisions' function always failed |
| in 'validate files', errors were reported incorrectly if the 'check
program header' option differed between the creation and checking of a
validation file |
| in 'validate files', errors were reported incorrectly if two files in
different folders had the same name/date/time/size, but the contents
differed |
| when attempting to fix duplicate filenames, each failed attempt at
choosing a new one caused the 'bad filename' count to increment |
| invalid clusters in subdirectories were not handled properly under
certain circumstances |
| under some circumstances, a bad sector in a directory cluster could
cause the 'Map bad' function to crash |
| a memory overlay could occur in rare circumstances when using the
'Write-Read' option in 'Map bad' |
| a spurious error was reported if any file occupied either of the last
two clusters of a drive (this will not happen under TOS, but can happen
under MagiC)
|
|
| Optimize
| compress free space with write priority mangled the partition when bad
sectors were present |
| if a read error occurred during full optimisation, the retry was
incorrect; this could cause the partition to be mangled |
| for compress free space with read priority, the progress bar did not
run to 100% properly |
| if a frag map was done for a drive, followed by a diskinfo, and then a
compress free space, a subsequent frag map did not reflect the changes
made by the compress free space function
|
|
| Partition
| when rebuilding a partition, a memory overlay could occur |
| choosing 'Max' when rebuilding a partition table would cause a memory
overlay if the disk capacity exceeded 1 GB |
| when setting up partitioning, if two or more consecutive partitions
were eliminated by blanking out their sizes, each redraw of the
partition display only removed one blank line |
| some bugs existed in partition size handling when switching between
ICD and Atari modes |
| after reading in a partition file, the file was not closed; if this
was done a number of times, a subsequent open would fail due to a
shortage of file handles
|
|
| Preferences
| three of the four options that appear under both the Medic and the
Optimize menu items (ignore illegal names, save lost clusters, visual
update) were implemented wrongly: each pair of options shared a common
variable, but the check marks in the menu were not synchronised, and the
options were saved separately in the preferences file, leading to
obscure bugs |
| when loading a saved preferences file during initialisation, if the
saved file had the 'Remove deleted' option not set, then the
'Prioritize read' menu item would be set
|
|
| Undelete
| if there were no previously-deleted entries in a directory, the
function failed with a misleading memory allocation failure message
|
|
| View file
| 'mouse droppings' could occur due to the mouse pointer not being
hidden during a screen blit |
|
