LSEGSave V1.2
=============
There are very few programs which are able to write the executables in the
LSEG-Segments of an harddisc, Microbotics RDPrep got an undocumented option
SAVE_LSEG but this will only work if the whole RDB & Partition-data are 100%
ok - and sadly many partioning tools make a lot of mistakes.
RDPrep will flash the faulty fields and allows to modify them in complex
mode, but any filesystem will be removed.
But it's a good tool anyway -> http://aminet.net/package/disk/misc/rdp391
Other programs only allow to save the whole RDB, for example RDBArc is
quite good -> http://aminet.net/package/disk/misc/2b_RDBArc18
So i wrote the missing piece myself.
Usage: LSEGSave device <unit> (default 0)
Will save the found LSEG-Entries on the device to RAM-files which then can be
reused for other drives.
At first it will try the name stored in the Filesystem-header
(FSHD.fhb_Reserved3), if there is none or the fullname failed "LSEG_#"
will be written to RAM:
If there is a problem in the RDSK, FSHD or LSEG it will be written to console.
Update 1.1:
Small Offset-Error corrected when RDSK is not in Block 0
Checksum testing for RDSK & FSHD, but will continue even when invalid.
Update 1.2:
More System-friendly code, only reads 16 blocks in search for RDSK,
and rdb_HighRDSKBlock (Number of used RDSK blocks), reducing ram-usage a lot.
Checksum testing for all LSEG-blocks combined for each FSHD-entry.
More output, how many sectors got read, where RDSK/FSHD&LSEG where found ..
Name for files is now RAM:LSEG_DosType_XXXX_# if no name is in FSHD.
And RAM:LSEG_DosType_XXXX_FSHDName if it is there.
XXXX = FFS3, PFS3 and so on ..
*****************************************************************************
*** Warning !!! ***
I tested if my Tool works with other Blocksizes than the default 512 Bytes,
and was suprised that the saved file was corrupt, then i noticed the LSEG-
Segments on the drive only use 123*4 longs and the rest are "0".
The culprit was HDToolbox V45.6, which wrote only the data for a
512-bytesector and left the rest empty ! Then i checked with HDToolbox V46.24
from 3.1.4 and it works fine.
Then i checked the older Versions and they all got this bug:
HDToolbox 44.23 (OS3.9)
HDToolbox 45.1 (OS3.9 BoingBag1)
HDToolbox 45.6 (OS3.9 BoingBag2)
So when you want bigger blocksize use an older/newer HDToolbox.
I will keep the V45.6, because:
1) It allows for example ASKDEVICE as Tooltype, then you can select which
device to use.
2) It got no "Drives has been added or removed .. blabla" Requester at start.
3) It's immediatly in "Advanced Mode"
4) When exiting it's not nagging about "Some disks have changes ..."
5) The "512 Bytes" limit isn't that awful, with TD64 or Direct-SCSI (which
FFS & PFS) supports, the maximum drive-size is 2TB, and PFS uses 1024 Bytes
as default blocksize for its filesystem, so 4TB. With bigger blocksizes for
the filesystem upto 128TB - just dont use bigger blocksizes for the disc
creation/RDB and everything will be fine.
6) Only the OS3.9 versions save the Filesystemname in FSHD.fhb_Reserved3
But i noticed it didn't check if there is enough sectors in RDB when adding
FileSystems, you could overwrite your partion when adding to many !!!
46.24 Handles RDB space fine and checks/notifies you when not enough space.
But this only happend because i only took a 16MB Testpartition and added
9 filesystems. :P
Bigger drivers also reserve more blocks for the RDB, so it's unlikely to
happen in normal situations.
*****************************************************************************
DISCLAIMER
This software is subject to the "Standard Amiga FD-Software Copyright
Note". It is Giftware as defined in paragraph 4g. If you like it and
use it regulary, please send me a small gift.
For more information please read "AFD-COPYRIGHT".
Diese Software unterliegt der "Standard Amiga FD-Software Copyright
Note". Sie ist Giftware wie definiert in Absatz 4g. Falls du sie magst
und regelmaessig benutzt, sende bitte ein kleines Geschenk.
Fuer mehr Informationen lies bitte "AFD-COPYRIGHT".
(/pub/aminet/docs/misc/AFD-FilesV-XX.lha V=Version,XX=Languages)
AUTHOR
Please send comments, bug-reports or small gifts like a Vampire V4
or a now "worthless :P" NVidia RTX 2080 Ti, or Paypal me to:
Holger.Hippenstiel AT gmx.de
Hauptstr. 38
71229 Leonberg
Germany
|
aminet net>