• Reformatting a Drive from ex FAT to NTFS Without Loosing Already Saved Data?

    From Boris@nospam@invalid.com to alt.windows7.general on Sat Jul 26 06:17:09 2025
    From Newsgroup: alt.windows7.general

    My Western Digital My Book external hard drive is formatted exFAT. I've been using it for years. It has prior Acronis Backups on it, and other data. The drive is formatted exPAT. I'd now like to use the drive to image another
    hard drive, but I'd have to format the drive as NTFS to do so.

    Is it possible to (re)format the drive from exFAT to NTFS without loosing the data that's already (i.e. the Acronis Backups, etc.) on it?

    TIA
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Boris@nospam@invalid.com to alt.windows7.general on Sat Jul 26 06:32:06 2025
    From Newsgroup: alt.windows7.general

    Boris <nospam@invalid.com> wrote in news:XnsB327ECE09BE6Anospaminvalidcom@157.180.91.226:

    My Western Digital My Book external hard drive is formatted exFAT. I've
    been using it for years. It has prior Acronis Backups on it, and other
    data. The drive is formatted exPAT. I'd now like to use the drive to
    image another hard drive, but I'd have to format the drive as NTFS to do
    so.

    Is it possible to (re)format the drive from exFAT to NTFS without
    loosing the data that's already (i.e. the Acronis Backups, etc.) on it?

    TIA


    Or, do I simply move data out, to be safe, reformat to NTFS, and then move
    data back in?
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.windows7.general on Sat Jul 26 04:27:53 2025
    From Newsgroup: alt.windows7.general

    On Sat, 7/26/2025 2:32 AM, Boris wrote:
    Boris <nospam@invalid.com> wrote in news:XnsB327ECE09BE6Anospaminvalidcom@157.180.91.226:

    My Western Digital My Book external hard drive is formatted exFAT. I've
    been using it for years. It has prior Acronis Backups on it, and other
    data. The drive is formatted exPAT. I'd now like to use the drive to
    image another hard drive, but I'd have to format the drive as NTFS to do
    so.

    Is it possible to (re)format the drive from exFAT to NTFS without
    loosing the data that's already (i.e. the Acronis Backups, etc.) on it?

    TIA


    Or, do I simply move data out, to be safe, reformat to NTFS, and then move data back in?


    You move the data off the partition, onto a second storage device.

    +-----+------------+
    Disk1 | MBR | D: ExFAT |
    +-----+------------+
    \_______________ (the backup files etcetera)
    \
    v
    +-----+---------------------------------------------------------------+ Disk2 | MBR | E: (Storage drive for temporary storage while fixing stuff) |
    +-----+---------------------------------------------------------------+

    You then format the original drive letter. A new/empty NTFS file system is created

    +-----+------------+
    Disk1 | MBR | D: NTFS |
    +-----+------------+

    Then move the data back.

    +-----+---------------------------------------------------------------+ Disk2 | MBR | E: (Storage drive for temporary storage while fixing stuff) |
    +-----+---------------------------------------------------------------+
    __________________________/
    /
    v
    +-----+------------+
    Disk1 | MBR | D: NTFS |
    +-----+------------+

    Paul
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From NY@me@privacy.net to alt.windows7.general on Sat Jul 26 14:29:47 2025
    From Newsgroup: alt.windows7.general

    On 26/07/2025 07:17, Boris wrote:
    My Western Digital My Book external hard drive is formatted exFAT. I've been using it for years. It has prior Acronis Backups on it, and other data. The drive is formatted exPAT. I'd now like to use the drive to image another hard drive, but I'd have to format the drive as NTFS to do so.

    Is it possible to (re)format the drive from exFAT to NTFS without loosing the data that's already (i.e. the Acronis Backups, etc.) on it?

    In a DOS / Command Prompt window,

    convert d: /fs:ntfs

    It is a one-way process: you can't convert NTFS back to FAT, FAT32 or exFAT.

    I'd copy the data off to a second drive, because I'm cautious or even paranoid, and then try to convert the original drive and see what happens.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From J. P. Gilliver@G6JPG@255soft.uk to alt.windows7.general on Sat Jul 26 15:40:42 2025
    From Newsgroup: alt.windows7.general

    On 2025/7/26 7:32:6, Boris wrote:
    Boris <nospam@invalid.com> wrote in news:XnsB327ECE09BE6Anospaminvalidcom@157.180.91.226:

    My Western Digital My Book external hard drive is formatted exFAT. I've
    been using it for years. It has prior Acronis Backups on it, and other
    data. The drive is formatted exPAT. I'd now like to use the drive to
    image another hard drive, but I'd have to format the drive as NTFS to do
    so.

    Assuming you mean by "image" what I mean by image, then do you need to
    change anything at all? By "image", I mean make in effect a giant zip
    file, representing the contents of a drive, partition, or combination
    thereof, which can be restored in the event of disaster (drive failure, ransomware, or just real screwup).

    The only reason I could think of that you might need to reformat -
    assuming you _do_ mean the same as me by the word "image" - is that NTFS allows larger files than exFAT (or exPAT!). I don't know if that is the
    case. (I have vague memories that one of the systems around, has a file
    size limit of 2 or 4 G.) Macrium, which I use for imaging, isn't
    troubled by that - if it needs to make an image bigger than the file
    systen on the target drive can handle, it just makes a multi-file image; YMMV.>>
    Is it possible to (re)format the drive from exFAT to NTFS without
    loosing the data that's already (i.e. the Acronis Backups, etc.) on it?

    NY has given a command line method ...>>
    TIA


    Or, do I simply move data out, to be safe, reformat to NTFS, and then move data back in?
    ... but says he'd do that anyway. As, I think, would I.
    --
    J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

    By the very definition of "news," we hear very little about the dominant threats to our lives, and the most about the rarest, including terror. "LibertyMcG" alias Brian P. McGlinchey, 2013-7-23
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.windows7.general on Sat Jul 26 11:29:50 2025
    From Newsgroup: alt.windows7.general

    On Sat, 7/26/2025 9:29 AM, NY wrote:
    On 26/07/2025 07:17, Boris wrote:
    My Western Digital My Book external hard drive is formatted exFAT.-a I've been
    using it for years.-a It has prior Acronis Backups on it, and other data.-a The
    drive is formatted exPAT.-a I'd now like to use the drive to image another >> hard drive, but I'd have to format the drive as NTFS to do so.

    Is it possible to (re)format the drive from exFAT to NTFS without loosing the
    data that's already (i.e. the Acronis Backups, etc.) on it?

    In a DOS / Command Prompt window,

    convert d: /fs:ntfs

    It is a one-way process: you can't convert NTFS back to FAT, FAT32 or exFAT.

    I'd copy the data off to a second drive, because I'm cautious or even paranoid, and then try to convert the original drive and see what happens.

    convert /?
    Converts a FAT volume to NTFS. <=== "FAT", the legacy version from WinXP era or so

    CONVERT volume /FS:NTFS [/V] [/CvtArea:filename] [/NoSecurity] [/X]


    volume Specifies the drive letter (followed by a colon),
    mount point, or volume name.
    /FS:NTFS Specifies that the volume will be converted to NTFS.
    /V Specifies that Convert will be run in verbose mode.
    /CvtArea:filename
    Specifies a contiguous file in the root directory
    that will be the place holder for NTFS system files.
    /NoSecurity Specifies that the security settings on the converted
    files and directories allow access by all users.
    /X Forces the volume to dismount first if necessary. <=== [It cannot dismount C: of course...]
    All open handles to the volume will not be valid.

    That also does a poor job, because the output NTFS filesystem has
    a tiny cluster size that isn't a very good choice. And one
    cluster-changer I tried (I paid money for it), corrupted the NTFS
    I tested it on.

    The previous paragraph tells you something. It tells you a commercial
    company released a file system utility which seemed to lack testing.
    I only caught the file conversion issue by accident, noticing that
    some of the System32 OS files on my machine, had 0 byte sizes after
    the conversion of the cluster size :-) (I did this while holding a backup
    in my hand, but if I'd thrown away the backup file, I would have been
    screwed.) This means, for any person with a head on their shoulders,
    you SHOULD NOT trust partition management software, further than
    you can throw it, and you should THOROUGHLY TEST such scum-ware,
    before doing such conversions without a backup.

    The Microsoft "documentation" simply refuses to enumerate what it refers
    to as FAT, but at this point in time, the ExFAT might not even
    be known about (as the convert.exe was invented in Win2K era or earlier).
    I do not get the impression that utility was under active development
    over the years. Maybe it covers FAT12, FAT16, FAT32, but if so, they
    should say that.

    https://web.archive.org/web/20150111022619/http://support.microsoft.com/kb/214579

    https://en.wikipedia.org/wiki/Convert_%28command%29

    Paul
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From John@Man@the.keyboard to alt.windows7.general on Sat Jul 26 21:31:50 2025
    From Newsgroup: alt.windows7.general

    On Sat, 26 Jul 2025 06:17:09 -0000 (UTC), Boris <nospam@invalid.com>
    wrote:

    My Western Digital My Book external hard drive is formatted exFAT. I've been >using it for years. It has prior Acronis Backups on it, and other data. The >drive is formatted exPAT. I'd now like to use the drive to image another >hard drive, but I'd have to format the drive as NTFS to do so.

    Is it possible to (re)format the drive from exFAT to NTFS without loosing the >data that's already (i.e. the Acronis Backups, etc.) on it?

    Yes, it is possible.

    No, *I* would not trust any valuable data to such a process.

    The easiest way would be to highlight the drive and to pick "Format"
    from the pop-up menu. The Windows Format command is pretty good. It is
    also fast, if you do a "quick format".

    But - before you do this - copy all of the data onto some other drive
    just so it is safe. Quick formatting may preserve your data but if you
    are careful or paranoid enough you won't want to chance that.

    Also, the Format command inside Windows says that it *can* convert
    NTFS back into exFAT but I've never tried that one.
    J.




    TIA
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From NY@me@privacy.net to alt.windows7.general on Sat Jul 26 22:18:31 2025
    From Newsgroup: alt.windows7.general

    On 26/07/2025 21:31, John wrote:
    The easiest way would be to highlight the drive and to pick "Format"
    from the pop-up menu. The Windows Format command is pretty good. It is
    also fast, if you do a "quick format".

    But - before you do this - copy all of the data onto some other drive
    just so it is safe. Quick formatting may preserve your data but if you
    are careful or paranoid enough you won't want to chance that.
    Unless I'm very wrong, even quick format will *wipe all your data* as it
    is formatting the drive. So you *must* copy all the data off to a second
    drive first. And maybe check that it is a good copy.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.windows7.general on Sat Jul 26 18:12:59 2025
    From Newsgroup: alt.windows7.general

    On Sat, 7/26/2025 4:31 PM, John wrote:
    On Sat, 26 Jul 2025 06:17:09 -0000 (UTC), Boris <nospam@invalid.com>
    wrote:

    My Western Digital My Book external hard drive is formatted exFAT. I've been
    using it for years. It has prior Acronis Backups on it, and other data. The
    drive is formatted exPAT. I'd now like to use the drive to image another >> hard drive, but I'd have to format the drive as NTFS to do so.

    Is it possible to (re)format the drive from exFAT to NTFS without loosing the
    data that's already (i.e. the Acronis Backups, etc.) on it?

    Yes, it is possible.

    No, *I* would not trust any valuable data to such a process.

    The easiest way would be to highlight the drive and to pick "Format"
    from the pop-up menu. The Windows Format command is pretty good. It is
    also fast, if you do a "quick format".

    But - before you do this - copy all of the data onto some other drive
    just so it is safe. Quick formatting may preserve your data but if you
    are careful or paranoid enough you won't want to chance that.

    Also, the Format command inside Windows says that it *can* convert
    NTFS back into exFAT but I've never tried that one.

    Which part of the following, suggests a "conversion routine" rather
    than a "format operation" ( clears previous metadata and the ability
    to access the data clusters ) ?

    *********************************************************************

    format /?
    Formats a disk for use with Windows.

    FORMAT volume [/FS:file-system] [/V:label] [/Q] [/L[:state]] [/A:size] [/C] [/I:state] [/X] [/P:passes] [/S:state]
    FORMAT volume [/V:label] [/Q] [/F:size] [/P:passes]
    FORMAT volume [/V:label] [/Q] [/T:tracks /N:sectors] [/P:passes]
    FORMAT volume [/V:label] [/Q] [/P:passes]
    FORMAT volume [/Q]

    volume Specifies the drive letter (followed by a colon),
    mount point, or volume name.
    /FS:filesystem Specifies the type of the file system (FAT, FAT32, exFAT,
    NTFS, UDF, ReFS).
    /V:label Specifies the volume label.
    /Q Performs a quick format. Note that this switch overrides /P.
    /C NTFS only: Files created on the new volume will be compressed
    by default.
    /X Forces the volume to dismount first if necessary. All opened
    handles to the volume would no longer be valid.
    /R:revision UDF only: Forces the format to a specific UDF version
    (1.02, 1.50, 2.00, 2.01, 2.50). The default
    revision is 2.01.
    /D UDF 2.50 only: Metadata will be duplicated.
    /L[:state] NTFS Only: Overrides the default size of file record.
    By default, a non-tiered volume will be formatted with small
    size file records and a tiered volume will be formatted with
    large size file records. /L and /L:enable forces format to
    use large size file records and /L:disable forces format to
    use small size file records.
    /A:size Overrides the default allocation unit size. Default settings
    are strongly recommended for general use.
    ReFS supports 4096, 64K.
    NTFS supports 512, 1024, 2048, 4096, 8192, 16K, 32K, 64K,
    128K, 256K, 512K, 1M, 2M.
    FAT supports 512, 1024, 2048, 4096, 8192, 16K, 32K, 64K,
    (128K, 256K for sector size > 512 bytes).
    FAT32 supports 512, 1024, 2048, 4096, 8192, 16K, 32K, 64K,
    (128K, 256K for sector size > 512 bytes).
    exFAT supports 512, 1024, 2048, 4096, 8192, 16K, 32K, 64K,
    128K, 256K, 512K, 1M, 2M, 4M, 8M, 16M, 32M.

    Note that the FAT and FAT32 files systems impose the
    following restrictions on the number of clusters on a volume:

    FAT: Number of clusters <= 65526
    FAT32: 65526 < Number of clusters < 4177918

    Format will immediately stop processing if it decides that
    the above requirements cannot be met using the specified
    cluster size.

    NTFS compression is not supported for allocation unit sizes
    above 4096.

    /F:size Specifies the size of the floppy disk to format (1.44)
    /T:tracks Specifies the number of tracks per disk side.
    /N:sectors Specifies the number of sectors per track.
    /P:count Overwrite the volume "count" times using a different random
    number each time followed by writing zeros to every sector.
    If "count" is zero, we'll just zero every sector on the
    volume. This switch is ignored when /Q is specified.
    /S:state Specifies support for short filenames (enable, disable)
    Short names are disabled by default
    /TXF:state Specifies if txf should be enabled/disabled (enable, disable)
    TxF is enabled by default
    /I:state ReFS only: Specifies whether integrity should be enabled on
    the new volume. "state" is either "enable" or "disable"
    Integrity is enabled on storage that supports data redundancy
    by default.
    /DAX[:state] NTFS Only: Enable direct access storage (DAX) mode for this
    volume. In DAX mode, the volume is accessed via the memory
    bus, boosting IO performance. A volume can be formatted
    with DAX mode only if the hardware is DAX capable.
    State can specify "enable" or "disable". /DAX is considered
    as /DAX:enable.
    /LogSize[:size] NTFS Only: Specifies the size for NTFS log file in kilobytes.
    The minimum supported size is 2MB, so specifying size smaller
    than 2MB will result in a 2MB log file. Zero indicates the
    default value which generally depend on the volume size.
    /NoRepairLogs NTFS Only: Disables NTFS repair logs. If the flag is set
    spotfix (i.e. chkdsk /spotfix) will not work.
    /NoTrim Skip sending trim (delete notification) during format.
    /DevDrv ReFS Only: Format the volume as a dev drive. A dev drive or
    a developer volume, is a volume optimized for performance of
    developer scenarios. Gives administrators control over what
    mini-filters are attached to this volume.
    /Y No prompt, force the volume to dismount if necessary
    and assumes empty label when no label is specified.



    *********************************************************************

    https://techcommunity.microsoft.com/discussions/windows11/how-to-convert-exfat-to-ntfs-on-windows-11-without-losing-data/4425411

    "I know Windows doesn't have a direct convert command for exFAT
    like it does for FAT32 to NTFS, so I'm looking for the safest method.

    Here's what IrCOve considered:

    Backup & Reformat
    ...
    "

    DiskGenius is claimed to have an ExFAT shrink capability, but in a test
    it damaged a users ExFAT. Other utility brands including Disk Management
    will not touch shrinking ExFAT. This is standard practice for commercial utilities, that the user does the testing. And by the time you've made your backup copy of the files, all need for additional shenanigans are gone.
    You can carry on with the destructive format operation on the source
    partition, then restore the files.

    Paul


    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.windows7.general on Sat Jul 26 18:45:39 2025
    From Newsgroup: alt.windows7.general

    On Sat, 7/26/2025 5:18 PM, NY wrote:
    On 26/07/2025 21:31, John wrote:
    -a The easiest way would be to highlight the drive and to pick "Format"
    from the pop-up menu. The Windows Format command is pretty good. It is
    also fast, if you do a "quick format".

    -a But - before you do this - copy all of the data onto some other drive
    just so it is safe. Quick formatting may preserve your data but if you
    are careful or paranoid enough you won't want to chance that.

    Unless I'm very wrong, even quick format will *wipe all your data* as
    it is formatting the drive. So you *must* copy all the data off to a
    second drive first. And maybe check that it is a good copy.

    The leverage point on the file systems, is how the structure information
    is recorded.

    On a FAT32 partition, the File Allocation Table is an example of a
    relatively small structure that records information about your files.
    Such a scheme eventually points to where the clusters for the file start.
    If you don't have a "map" of some sort as to where things are, then
    it is considered your data is "lost". The data is not really lost, but
    you have to be a mind reader to join fragmented parts of your data together
    (as Photorec.exe attempts to do).

    On an NTFS partition, the Master File Table is a similar example of
    a table of data about your files. If you format an NTFS partition,
    it deletes the previous Master File Table, creates a new/empty Master File Table
    and the new Master File Table is very small and fits in a thimble. Your reference to the 600,000 files that used to be on the partition, are
    now gone. The following list, would be very close to what a $MFT would
    have info for, right after the volume has been formatted again. Files 0..15
    are standard parts of NTFS. "Everything is a file" :-) It's because
    everything is a file, that the $MFT can be fragmented and nobody cares!

    *******

    Since I have the utility for it (nfi.exe from Microsoft), let us look at examples of tables the NTFS file system keeps.

    NTFS File Sector Information Utility.
    Copyright (C) Microsoft Corporation 1999. All rights reserved.

    File 0
    Master File Table ($Mft) <=== The $MFT can be fragmented and broken into chunks and it still works...
    $STANDARD_INFORMATION (resident)
    $ATTRIBUTE_LIST (nonresident)
    logical sectors 81504488-81504999 (0x4dba8e8-0x4dbaae7)
    $FILE_NAME (resident)
    $DATA (nonresident)
    logical sectors 6291456-6506495 (0x600000-0x6347ff) \
    logical sectors 107974536-109123071 (0x66f8f88-0x68115ff) \___ This one is stored in three fragments
    logical sectors 159989416-160004143 (0x9893ea8-0x989782f) /
    $BITMAP (nonresident)
    logical sectors 173472-173647 (0x2a5a0-0x2a64f)

    File 1
    Master File Table Mirror ($MftMirr) <=== this one is a short stub, it is NOT a full $MFT
    $STANDARD_INFORMATION (resident)
    $FILE_NAME (resident)
    $DATA (nonresident)
    logical sectors 16-23 (0x10-0x17) <=== it is using a single 4096 byte cluster

    File 2
    Log File ($LogFile)
    $STANDARD_INFORMATION (resident)
    $FILE_NAME (resident)
    $DATA (nonresident)
    logical sectors 6156936-6288007 (0x5df288-0x5ff287)

    File 3
    DASD ($Volume)
    $STANDARD_INFORMATION (resident)
    $FILE_NAME (resident)
    $OBJECT_ID (resident)
    $VOLUME_NAME (resident)
    $VOLUME_INFORMATION (resident)
    $DATA (resident)

    File 4
    Attribute Definition Table ($AttrDef)
    $STANDARD_INFORMATION (resident)
    $FILE_NAME (resident)
    $DATA (nonresident)
    logical sectors 14229696-14229703 (0xd920c0-0xd920c7)

    File 5
    Root Directory
    $STANDARD_INFORMATION (resident)
    $FILE_NAME (resident) <=== We could have stored "C:\" in here, but this is not how it works.
    $OBJECT_ID (resident) It remains empty, while MountVol or similar in the Registry records
    $INDEX_ROOT $I30 (resident) drive letters (drive letters are defined by each boot OS for their own usage).
    $INDEX_ALLOCATION $I30 (nonresident) When File 5 tries to access File 5 as its "Parent Dir", we know then that
    logical sectors 80-95 (0x50-0x5f) File 5 is the top of the file tree, and we should stop trying to climb the
    $BITMAP $I30 (resident) tree while building our absolute path. nfi.exe lists things by its absolute
    Attribute Type 0x100 $TXF_DATA (resident) path, which is why it takes two minutes for this utility to run. See
    File 17 below, for an example of a userland file absolute-path example.
    File 6
    Volume Bitmap ($BitMap)
    $STANDARD_INFORMATION (resident)
    $FILE_NAME (resident)
    $DATA (nonresident)
    logical sectors 6288008-6291455 (0x5ff288-0x5fffff)
    logical sectors 2408176-2412327 (0x24bef0-0x24cf27)
    $DATA $SRAT (resident)

    File 7
    Boot Sectors ($Boot)
    $STANDARD_INFORMATION (resident)
    $FILE_NAME (resident)
    $SECURITY_DESCRIPTOR (resident)
    $DATA (nonresident)
    logical sectors 0-15 (0x0-0xf)

    File 8
    Bad Cluster List ($BadClus) <=== A sparse file used to map out clusters known to be bad.
    $STANDARD_INFORMATION (resident) Since a backup/restore keeps this info, and the info ends up
    $FILE_NAME (resident) restored onto our brand new hard drive, usage of this feature is "not recommended"
    $DATA (resident) This means there is one option in CHKDSK you should avoid using,
    $DATA $Bad (nonresident) and it is the option that takes hours to run, too.

    File 9
    Security ($Secure)
    $STANDARD_INFORMATION (resident)
    $ATTRIBUTE_LIST (nonresident)
    logical sectors 7018880-7018887 (0x6b1980-0x6b1987)
    $FILE_NAME (resident)
    $INDEX_ROOT $SDH (resident)
    $INDEX_ROOT $SII (resident)

    File 10
    Upcase Table ($UpCase)
    $STANDARD_INFORMATION (resident)
    $FILE_NAME (resident)
    $DATA (nonresident)
    logical sectors 7273504-7273759 (0x6efc20-0x6efd1f)
    $DATA $Info (resident)

    File 11
    Extend Table ($Extend)
    $STANDARD_INFORMATION (resident)
    $FILE_NAME (resident)
    $INDEX_ROOT $I30 (resident)

    File 12
    (unknown/unnamed)
    $STANDARD_INFORMATION (resident)
    $SECURITY_DESCRIPTOR (resident)
    $DATA (resident)

    File 13
    (unknown/unnamed)
    $STANDARD_INFORMATION (resident)
    $SECURITY_DESCRIPTOR (resident)
    $DATA (resident)

    File 14
    (unknown/unnamed)
    $STANDARD_INFORMATION (resident)
    $SECURITY_DESCRIPTOR (resident)
    $DATA (resident)

    File 15 <=== These last four files, we don't know what they do.
    (unknown/unnamed) Being "Resident" type, their technical content is 700 bytes or less
    $STANDARD_INFORMATION (resident) They could also be "fillers", accounting for the first 0..15 files
    $SECURITY_DESCRIPTOR (resident) of the file system. By filling them with something, no one else
    $DATA (resident) can use Filenum 12..15

    File 17
    \System Volume Information\Chkdsk\Chkdsk20221020071312.log <=== This happens to be the first userland file at the moment
    $STANDARD_INFORMATION (resident) This is not a metadata file, but something the OS uses.
    $FILE_NAME (resident)
    $SECURITY_DESCRIPTOR (resident)
    $DATA (nonresident)
    logical sectors 11496952-11496967 (0xaf6df8-0xaf6e07) <=== The $MFT tells us where the data clusters are stored.
    Format the $MFT ? All pointers are lost.
    File 18
    \System Volume Information\Chkdsk\Chkdsk20240206030858.log
    $STANDARD_INFORMATION (resident)
    $FILE_NAME (resident)
    $SECURITY_DESCRIPTOR (resident)
    $DATA (nonresident)
    logical sectors 2280-2295 (0x8e8-0x8f7)

    Paul



    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Boris@nospam@invalid.com to alt.windows7.general on Mon Jul 28 02:11:22 2025
    From Newsgroup: alt.windows7.general

    "J. P. Gilliver" <G6JPG@255soft.uk> wrote in news:1062pda$2ehh0$5@dont- email.me:

    On 2025/7/26 7:32:6, Boris wrote:
    Boris <nospam@invalid.com> wrote in
    news:XnsB327ECE09BE6Anospaminvalidcom@157.180.91.226:

    My Western Digital My Book external hard drive is formatted exFAT. I've >>> been using it for years. It has prior Acronis Backups on it, and other
    data. The drive is formatted exPAT. I'd now like to use the drive to
    image another hard drive, but I'd have to format the drive as NTFS to do >>> so.

    Assuming you mean by "image" what I mean by image, then do you need to change anything at all? By "image", I mean make in effect a giant zip
    file, representing the contents of a drive, partition, or combination thereof, which can be restored in the event of disaster (drive failure, ransomware, or just real screwup).

    I was meaning to create an image of the entire disk by using the Windows built-in imaging program found at Control Panel>Backup and Restore>Create a system image.

    The problem is that when I selected "Create a system image", and selected the Western Digital exFAT formatted My Book as the destination disk, the message was "This drive cannot be used to store a system image because it is not formatted NTFS."

    I did consider copying the data out to a spare disk, reformatting the My Book disk to NTFS, and then moving the data back to the My Book disk. But, I realized that I didn't have a spare disk with enough room to which I could copy out all the data.

    I decided to use Macrium Reflect Free to create an image on the My Book. Image of created fine.

    I have a Windows 7, non-SP1, original CD from Dell that came with the machine back in October 2010. The OS has long since been updated to SP1. It's the image I just created. But, if I ever have to use the original non-SP1 CD, rather than the image just created, to reinstall Windows 7, and if I care about SP1, I'll have to find it. I looked on the Microsoft Update Catalog, but couldn't find it. Perhaps my search terms were bad. My understanding is that it's not a mandatory or critical update, though.


    The only reason I could think of that you might need to reformat -
    assuming you _do_ mean the same as me by the word "image" - is that NTFS allows larger files than exFAT (or exPAT!).

    Yeah, I did proof read before sending, but my tired eyes saw that P as an F.


    I don't know if that is the
    case. (I have vague memories that one of the systems around, has a file
    size limit of 2 or 4 G.) Macrium, which I use for imaging, isn't
    troubled by that - if it needs to make an image bigger than the file
    systen on the target drive can handle, it just makes a multi-file image; YMMV.>>
    Is it possible to (re)format the drive from exFAT to NTFS without
    loosing the data that's already (i.e. the Acronis Backups, etc.) on it?

    NY has given a command line method ...>>
    TIA


    Or, do I simply move data out, to be safe, reformat to NTFS, and then move >> data back in?
    ... but says he'd do that anyway. As, I think, would I.


    Thanks for the reply.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.windows7.general on Sun Jul 27 23:03:47 2025
    From Newsgroup: alt.windows7.general

    On Sun, 7/27/2025 10:11 PM, Boris wrote:
    "J. P. Gilliver" <G6JPG@255soft.uk> wrote in news:1062pda$2ehh0$5@dont- email.me:
    Or, do I simply move data out, to be safe, reformat to NTFS, and then move >>> data back in?
    ... but says he'd do that anyway. As, I think, would I.

    The individual files sitting on the MyBook, are they compressed at all ?
    (like, compressed by Acronis True Image).

    On modern file sets, you don't always get that much improvement in size,
    but it would be a way of requiring less space for your archive files.

    On Macrium, I back up in an uncompressed state, then use 7ZIP to make
    .mrimg.7z from the files and 7ZIP can compress files pretty well.

    One problem with compressing files this time of year, it running 100% on
    all cores makes the room warm. Compressing files in winter, well, throw
    another log on the fire.

    There was an article a few weeks ago, mentioning the latest version
    of 7ZIP now allows more CPU cores to be used (core groups, like on
    Win11 Workstation). That means, for only $11,000 or so, your compression operation could go faster. I think I'd rather have a small used car instead :-)

    *******

    Macrium is better at backups than the "Windows 7 Backup" is, I think
    it's a good thing you did a backup with the Macrium instead. The Macrium
    has a "Verify" function, whereas I don't think the Microsoft "Windows 7 Backup" has a Verify function. I've not seen any mention of the features you would expect from a commercial backup, in the Microsoft one.

    Similarly, if you did a 7Z compression, there is a Verify function for
    that too (it just verifies the checksum).

    Macrium, they made a claim they have a repair capability, for their big backup file, but I have not seen mention of anyone using that.

    Maybe Santa Claus will buy you a bigger backup drive :-)
    Then you can put NTFS on it.

    Paul


    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From J. P. Gilliver@G6JPG@255soft.uk to alt.windows7.general on Mon Jul 28 06:13:30 2025
    From Newsgroup: alt.windows7.general

    On 2025/7/28 4:3:47, Paul wrote:
    []

    Macrium is better at backups than the "Windows 7 Backup" is, I think
    it's a good thing you did a backup with the Macrium instead. The Macrium

    Also, I don't _think_ it's bothered about what the target drive is
    formatted as (if it's one with a smaller filesize limit than needed, it
    just makes a multi-file image); from what Boris was saying, sounds like
    the W7 backup thing will only image to NTFS. (Or maybe needed the file
    size, if that's bigger on NTFS.)

    has a "Verify" function, whereas I don't think the Microsoft "Windows 7 Backup"
    has a Verify function. I've not seen any mention of the features you would expect from a commercial backup, in the Microsoft one.

    Similarly, if you did a 7Z compression, there is a Verify function for
    that too (it just verifies the checksum).

    Macrium, they made a claim they have a repair capability, for their big backup
    file, but I have not seen mention of anyone using that.

    I'm not sure if what the W7 backup system produces is bootable; to do a
    "cold metal" restore from a Macrium image, you do need a Macrium boot
    device (M5 and M6 will fit on a mini-CD, and are fine for W7 systems;
    later versions of W10 need later Macrium, though I'm not sure which. M8
    needs a DVD, though I think would still fit on a mini one.)>
    Maybe Santa Claus will buy you a bigger backup drive :-)
    Then you can put NTFS on it.

    Paul


    John
    --
    J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

    Everyone learns from science. It all depends how you use the knowledge.
    - "Gil Grissom" (CSI).
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.windows7.general on Mon Jul 28 05:43:34 2025
    From Newsgroup: alt.windows7.general

    On Mon, 7/28/2025 1:13 AM, J. P. Gilliver wrote:
    On 2025/7/28 4:3:47, Paul wrote:
    []

    Macrium is better at backups than the "Windows 7 Backup" is, I think
    it's a good thing you did a backup with the Macrium instead. The Macrium

    Also, I don't _think_ it's bothered about what the target drive is
    formatted as (if it's one with a smaller filesize limit than needed, it
    just makes a multi-file image); from what Boris was saying, sounds like
    the W7 backup thing will only image to NTFS. (Or maybe needed the file
    size, if that's bigger on NTFS.)

    has a "Verify" function, whereas I don't think the Microsoft "Windows 7 Backup"
    has a Verify function. I've not seen any mention of the features you would >> expect from a commercial backup, in the Microsoft one.

    Similarly, if you did a 7Z compression, there is a Verify function for
    that too (it just verifies the checksum).

    Macrium, they made a claim they have a repair capability, for their big backup
    file, but I have not seen mention of anyone using that.

    I'm not sure if what the W7 backup system produces is bootable; to do a
    "cold metal" restore from a Macrium image, you do need a Macrium boot
    device (M5 and M6 will fit on a mini-CD, and are fine for W7 systems;
    later versions of W10 need later Macrium, though I'm not sure which. M8
    needs a DVD, though I think would still fit on a mini one.)>
    Maybe Santa Claus will buy you a bigger backup drive :-)
    Then you can put NTFS on it.

    The ExFAT as a file system, should be perfectly functional as far as
    storage goes. It doesn't have a 4GB limitation on files like FAT32.
    That is presumably one of the design objectives of making a new
    file system, was removing that limitation.

    But it is not a journaled file system as far as I know (could be corrupted
    by your random unplugging of it). And it's not an attempt to match all the capabilities of NTFS either. It's a unique filesystem, likely intended for external flash storage (like a USB stick or a camera system or something).
    If your external drive is a HDD, with no discernible "wear issue", there
    is hardly a reason to be using ExFAT on that. One of the intents of ExFAT,
    is less write-wear on the flash (because it is not journaled).

    I've formatted things a couple times with ExFAT, and it just seems soon
    after, I'm putting NTFS on the same storage device later. And not being
    able to shrink/expand it, even with third party tools (if one works doing that), that puts a damper on the fun. If you could shrink the ExFAT partition, you could create an NTFS partition in the space that is freed up.

    Some of the OS functions, if you believe the Microsoft documentation,
    they have "an NTFS requirement", yet you can find examples of third-party coding attempts that seem to get by without meeting that. There have
    been things, where NTFS as a mount point was claimed to be a requirement,
    and a third party managed to get it running on FAT32.

    The "Windows 7 backup on Windows 7" is VHD based, with a 2.2TB limitation. That's the difference between VHD and VHDX files, is VHDX allows a much larger container to be constructed than the 2.2TB limit. It could be, that the "thing" being backed up has to be NTFS (maybe having something to do with applying
    a VSS shadow to C: when backing it up). But the output file system, there really should not be a big deal writing out a VHD. It's just a file. It can
    be configured as a dynamically expanding container, so you don't have to pre-allocate storage for it. That's one of the reasons I like it.

    I can emulate a 500TB container with some of the dynamically expanding containers, and the thing might take less than 1GB of storage when it is
    empty. That allows me to take pictures of absurdly large storage, without actually owning that much storage. In theory, you should be able to make
    a container larger than that, but that's roughly the practical limit
    (for taking pictures of it in disk management at least).

    One of the disadvantages of large HDD, is needing yet another large HDD
    to offload it. But you can't run computers in a vacuum, so once you have storage at home, you also need the tools for doing the maintenance of it.
    And unloading a device, while doing maintenance on it, is a degree of
    freedom you need for practical usage.

    Like the person who keeps asking questions about "the practical running
    of a hard drive which is full of CRC errors". Well, don't do that.
    Or, get another hobby. We're not on Mars here, and we're not trying to
    grow a potato in the wrong kind of soil. Or making fuel out of the
    Martian ice caps. Just find another drive, even a used one, that doesn't
    have CRC errors, and use that. Running a drive with CRC errors would be
    fine... if the CRC errors did not move, or if the situation was "stable".
    But having additional CRC errors show up randomly with time, you would
    be spending more time on disk maintenance, than getting anything done.
    That's why I retire drives that have shown their true colors (like the
    five or six Seagate 500GB drives that exhibited some really weird
    performance issues, and some day, when I open those up, I know I'm
    going to find there is no plastic landing ramp for the heads inside those).

    Paul

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From J. P. Gilliver@G6JPG@255soft.uk to alt.windows7.general on Mon Jul 28 12:32:05 2025
    From Newsgroup: alt.windows7.general

    (You have forgotten far more on this subject than I ever knew.)

    On 2025/7/28 10:43:34, Paul wrote:
    On Mon, 7/28/2025 1:13 AM, J. P. Gilliver wrote:
    On 2025/7/28 4:3:47, Paul wrote:
    []

    Macrium is better at backups than the "Windows 7 Backup" is, I think
    it's a good thing you did a backup with the Macrium instead. The Macrium

    []

    I'm not sure if what the W7 backup system produces is bootable; to do a


    The ExFAT as a file system, should be perfectly functional as far as
    storage goes. It doesn't have a 4GB limitation on files like FAT32.
    That is presumably one of the design objectives of making a new
    file system, was removing that limitation.

    (Oh: the two partitions on my SSD here are NTFS. Does that mean it's
    wearing at twice the rate, because of the journalling? [Currently
    showing as 97%, "good", in Crystal.])>
    But it is not a journaled file system as far as I know (could be corrupted
    by your random unplugging of it). And it's not an attempt to match all the capabilities of NTFS either. It's a unique filesystem, likely intended for external flash storage (like a USB stick or a camera system or something).
    If your external drive is a HDD, with no discernible "wear issue", there
    is hardly a reason to be using ExFAT on that. One of the intents of ExFAT,
    is less write-wear on the flash (because it is not journaled).

    I've formatted things a couple times with ExFAT, and it just seems soon after, I'm putting NTFS on the same storage device later. And not being
    able to shrink/expand it, even with third party tools (if one works doing that), that puts a damper on the fun. If you could shrink the ExFAT partition,
    you could create an NTFS partition in the space that is freed up.

    "Everything" (the voidtools utility) alone justifies, for me, using
    NTFS; I use Everything a lot, and although it does work on FAT (I forget
    which one), it's _far_ slower. I presume it works as fast as it does
    _because_ it uses the journalling in some way.>
    Some of the OS functions, if you believe the Microsoft documentation,
    they have "an NTFS requirement", yet you can find examples of third-party coding attempts that seem to get by without meeting that. There have
    been things, where NTFS as a mount point was claimed to be a requirement,
    and a third party managed to get it running on FAT32.

    In much the same way that the built-in (from W7 I think) partition
    manager is unable to shrink partitions beyond a point (usually when it
    gets to certain system files, I think), whereas external ones like the
    EaseUS one can (I presume by moving said files).>
    The "Windows 7 backup on Windows 7" is VHD based, with a 2.2TB limitation. That's the difference between VHD and VHDX files, is VHDX allows a much larger
    container to be constructed than the 2.2TB limit. It could be, that the "thing"
    being backed up has to be NTFS (maybe having something to do with applying
    a VSS shadow to C: when backing it up). But the output file system, there really should not be a big deal writing out a VHD. It's just a file. It can be configured as a dynamically expanding container, so you don't have to pre-allocate storage for it. That's one of the reasons I like it.

    I can emulate a 500TB container with some of the dynamically expanding containers, and the thing might take less than 1GB of storage when it is empty. That allows me to take pictures of absurdly large storage, without actually owning that much storage. In theory, you should be able to make
    a container larger than that, but that's roughly the practical limit
    (for taking pictures of it in disk management at least).

    One of the disadvantages of large HDD, is needing yet another large HDD
    to offload it. But you can't run computers in a vacuum, so once you have storage at home, you also need the tools for doing the maintenance of it.
    And unloading a device, while doing maintenance on it, is a degree of
    freedom you need for practical usage.

    Yes, when I bought this laptop with its 500G (actually 480.1) SSD, I
    bought a 1TB external for backup.>
    Like the person who keeps asking questions about "the practical running
    of a hard drive which is full of CRC errors". Well, don't do that.

    Agreed.

    Or, get another hobby. We're not on Mars here, and we're not trying to
    grow a potato in the wrong kind of soil. Or making fuel out of the
    Martian ice caps. Just find another drive, even a used one, that doesn't
    have CRC errors, and use that. Running a drive with CRC errors would be fine... if the CRC errors did not move, or if the situation was "stable".

    Yes. _Sometimes_ they do not move, as shown by for example HDTune, but
    on the whole, if a hard drive has errors, they tend to increase. If it's
    the main drive in your main system, you may have no option but to keep
    using it, but you should only do so while waiting for the replacement to
    arrive (and be making more frequent backups while waiting).

    But having additional CRC errors show up randomly with time, you would
    be spending more time on disk maintenance, than getting anything done.
    That's why I retire drives that have shown their true colors (like the
    five or six Seagate 500GB drives that exhibited some really weird
    performance issues, and some day, when I open those up, I know I'm
    going to find there is no plastic landing ramp for the heads inside those).

    Paul

    The only time I've ever opened one up was - in a laptop prone to
    overheating - it had spot-welded a head or something: it just stopped
    spinning that day. Though I was able to free it (and retrieve lots -
    95-97%, I think - of what was on it), I definitely considered it as
    scrap, and this seemed justified: even though I'd opened it in a positive-pressure clean cabinet I had access to at work, every time I
    checked it after that, it had more errors.

    John
    --
    J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

    "Everyone is entitled to an *informed* opinion." - Harlan Ellison
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.windows7.general on Mon Jul 28 15:00:02 2025
    From Newsgroup: alt.windows7.general

    On Mon, 7/28/2025 7:32 AM, J. P. Gilliver wrote:
    (You have forgotten far more on this subject than I ever knew.)

    The ExFAT as a file system, should be perfectly functional as far as
    storage goes. It doesn't have a 4GB limitation on files like FAT32.
    That is presumably one of the design objectives of making a new
    file system, was removing that limitation.

    (Oh: the two partitions on my SSD here are NTFS. Does that mean it's
    wearing at twice the rate, because of the journalling? [Currently
    showing as 97%, "good", in Crystal.])>

    The journal makes entries every time a file is created, written to (at
    a certain chunk size an entry is made), or deleted. It does not wear quite
    as much as the activity it records, but it also does not represent zero wear either. Call it a "five percent tax" if you like. The journal also broadcasts to applications like Everything, which register to "listen in" on the activity (important for keeping search files updated).


    "Everything" (the voidtools utility) alone justifies, for me, using
    NTFS; I use Everything a lot, and although it does work on FAT (I forget which one), it's _far_ slower. I presume it works as fast as it does _because_ it uses the journalling in some way.

    Journaling, is much more efficient than having to rescan the entire
    ExFAT volume to build a file list. However, journaling is not perfect,
    because the user might cheat and use the drive in a situation where
    journaling is not supported. You should still do an end-to-end file list
    scan at regular intervals, which is what Everything does do.


    In much the same way that the built-in (from W7 I think) partition
    manager is unable to shrink partitions beyond a point (usually when it
    gets to certain system files, I think), whereas external ones like the
    EaseUS one can (I presume by moving said files).

    Yes, most commercial efforts have been able to move the un-moveable file :-) Amazing when you think about it. And somebody knows how to defragment the $MFT, but they went out of business.

    The only time I've ever opened one up was - in a laptop prone to
    overheating - it had spot-welded a head or something: it just stopped spinning that day. Though I was able to free it (and retrieve lots -
    95-97%, I think - of what was on it), I definitely considered it as
    scrap, and this seemed justified: even though I'd opened it in a positive-pressure clean cabinet I had access to at work, every time I
    checked it after that, it had more errors.

    Stiction was an issue with some drive like Quantum Fireball?, or some drive around that era. I might have had a 250MB drive with the stiction problem,
    and a sharp rap with a screwdriver handle onto the side of the drive casing would free it. That drive is still in the room, and has not been run
    for over 30 years.

    They kinda cured the stiction problem, in the sense that the method of making
    a landing zone was adjusted a bit. Originally (like a Quantum Fireball), the landing zone was just a flat smooth area (thus, stiction of heads to platter was the harvested result). The early patterning efforts left a lot to be desired
    (head juddering over cobble stones). And back in those days, heads were not all that robust. A head today, can rub against a platter (zero clearance) for 30 days,
    before the head is ground off :-) Hitachi tried this in the lab. That's how good
    the polymer finish on the platter is now. In any case, the patterning that works,
    is "laser patterning", which means some fairly tiny features are embossed in the
    landing zone. There are no details such as micrographs of the pattern available though. You'd have to get out your own microscope and see what they have done.

    So that's what my 250GB drive was supposed to have in it, no plastic landing ramp, and a cheap, laser patterned landing zone near the hub. And that could run for 10,000 hours before becoming feeble (mostly proportional to power cycles, rather than to hours of operation). The drive might have lasted
    longer if the power had stayed on at all times.

    Paul
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From NY@me@privacy.net to alt.windows7.general on Mon Jul 28 20:45:29 2025
    From Newsgroup: alt.windows7.general

    On 28/07/2025 10:43, Paul wrote:

    The ExFAT as a file system, should be perfectly functional as far as
    storage goes. It doesn't have a 4GB limitation on files like FAT32.
    That is presumably one of the design objectives of making a new
    file system, was removing that limitation.

    But it is not a journaled file system as far as I know (could be corrupted
    by your random unplugging of it). And it's not an attempt to match all the capabilities of NTFS either. It's a unique filesystem, likely intended for external flash storage (like a USB stick or a camera system or something).
    If your external drive is a HDD, with no discernible "wear issue", there
    is hardly a reason to be using ExFAT on that. One of the intents of ExFAT,
    is less write-wear on the flash (because it is not journaled).

    I think an advantage of exFAT over NTFS is that it is often readable by devices (eg DVD/HDD TV recorders with ability to plug in a memory stick) because it is FAT-like, even if they can't read NTFS. It has the
    advantage over FAT/FAT32 that is doesn't have the cursed 4GB file size
    limit.


    Once interesting aside... I understand that a lot of devices such as HDD recorders and digital cameras can't read/write NTFS because they would
    need to pay a licence fee to Microsoft. And yet Debian/Raspbian distros
    of Linux include NTFS capability, for writing as well as reading,
    without needing to pass on a Microsoft fee to punters. And it works: my Raspberry Pi which records TV programmes to an external (spinning) HDD
    uses an NTFS rather than Unix-specific filesystem so I can unplug the
    disk and read it on Windows if required.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Boris@nospam@invalid.com to alt.windows7.general on Mon Jul 28 21:07:41 2025
    From Newsgroup: alt.windows7.general

    Paul <nospam@needed.invalid> wrote in news:1066pal$3c6ji$1@dont-email.me:

    On Sun, 7/27/2025 10:11 PM, Boris wrote:
    "J. P. Gilliver" <G6JPG@255soft.uk> wrote in news:1062pda$2ehh0$5@dont-
    email.me:
    Or, do I simply move data out, to be safe, reformat to NTFS, and then
    move data back in?
    ... but says he'd do that anyway. As, I think, would I.

    The individual files sitting on the MyBook, are they compressed at all ? (like, compressed by Acronis True Image).

    Nope.


    On modern file sets, you don't always get that much improvement in size,
    but it would be a way of requiring less space for your archive files.

    On Macrium, I back up in an uncompressed state, then use 7ZIP to make .mrimg.7z from the files and 7ZIP can compress files pretty well.

    One problem with compressing files this time of year, it running 100% on
    all cores makes the room warm. Compressing files in winter, well, throw another log on the fire.

    There was an article a few weeks ago, mentioning the latest version
    of 7ZIP now allows more CPU cores to be used (core groups, like on
    Win11 Workstation). That means, for only $11,000 or so, your compression operation could go faster. I think I'd rather have a small used car
    instead :-)

    *******

    Macrium is better at backups than the "Windows 7 Backup" is, I think
    it's a good thing you did a backup with the Macrium instead. The Macrium
    has a "Verify" function, whereas I don't think the Microsoft "Windows 7 Backup" has a Verify function. I've not seen any mention of the features
    you would expect from a commercial backup, in the Microsoft one.

    I don't recall if Windows System Imaging had a 'verify' function towards
    the end of the process. I didn't watch it all the way to the end. It
    just said 'completed successfully'. I ran it only because I was curious
    to see what it would image. I prefer Macrium and Acronis True Image
    because I can browse the images.



    Similarly, if you did a 7Z compression, there is a Verify function for
    that too (it just verifies the checksum).

    Macrium, they made a claim they have a repair capability, for their big backup file, but I have not seen mention of anyone using that.

    Maybe Santa Claus will buy you a bigger backup drive :-)
    Then you can put NTFS on it.

    Paul





    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.windows7.general on Mon Jul 28 19:20:02 2025
    From Newsgroup: alt.windows7.general

    On Mon, 7/28/2025 3:45 PM, NY wrote:
    On 28/07/2025 10:43, Paul wrote:

    The ExFAT as a file system, should be perfectly functional as far as
    storage goes. It doesn't have a 4GB limitation on files like FAT32.
    That is presumably one of the design objectives of making a new
    file system, was removing that limitation.

    But it is not a journaled file system as far as I know (could be corrupted >> by your random unplugging of it). And it's not an attempt to match all the >> capabilities of NTFS either. It's a unique filesystem, likely intended for >> external flash storage (like a USB stick or a camera system or something). >> If your external drive is a HDD, with no discernible "wear issue", there
    is hardly a reason to be using ExFAT on that. One of the intents of ExFAT, >> is less write-wear on the flash (because it is not journaled).

    I think an advantage of exFAT over NTFS is that it is often readable by devices (eg DVD/HDD TV recorders with ability to plug in a memory stick) because it is FAT-like, even if they can't read NTFS. It has the advantage over FAT/FAT32 that is doesn't have the cursed 4GB file size limit.


    Once interesting aside... I understand that a lot of devices such as HDD recorders and digital cameras can't read/write NTFS because they would need to pay a licence fee to Microsoft. And yet Debian/Raspbian distros of Linux include NTFS capability, for writing as well as reading, without needing to pass on a Microsoft fee to punters. And it works: my Raspberry Pi which records TV programmes to an external (spinning) HDD uses an NTFS rather than Unix-specific filesystem so I can unplug the disk and read it on Windows if required.

    The lawyers are likely to pursue the for-profit companies.
    A RedHat Linux for example, might have to pay a license fee.

    As far as I know, *all* of the Microsoft filesystems have license
    fees attached. Do a Google on TomTom, to see what one of the victims
    went through. They had to "pick an example for the lawyers to chew on"
    and that was TomTom.

    One of the differences can be, you can attach a commercial patent to
    a standards body standard, as long as the license fee is FRAND
    (Fair and Reasonable licensing fee). As a result, some of the
    licensing fees are smaller than others, or the fee does not have
    a unit multiplier attached to it.

    If you check the article on ExFAT, you might find which physical
    devices where it is mandatory.

    https://en.wikipedia.org/wiki/ExFAT

    "exFAT is the official file system of SDXC cards. Because of this,
    any device not supporting exFAT, such as the Nintendo 3DS, may not
    legally advertise itself as SDXC compatible, despite supporting
    SDXC cards as mass storage devices by formatting the card with
    FAT32 or a proprietary file system tied to the device in question."

    And Microsoft can wangle such an arrangement, by offering the filesystem
    to the standards body (who ever handles Secure Digital), on the understanding the licensing shall be FRAND. In the previous paragraph, the issue for
    Nintendo 3DS, would be the license terms for *it* to read using ExFAT protocol. Some companies are very resistant to license fees, agreeing that $0
    is FRAND for the license. So you can see in the example, how Nintendo
    plays at odds with others. The users read the above paragraph and
    put on their forensic hat, to understand what to do next.

    This kind of dicking around, is why you will find a lot of graphics
    items with just one HDMI connector, and multiple DP connectors.
    The HDMI costs money, the DP license terms are quite different.

    My company had to chase another scrote of a company through court,
    to collect $2 million from them for a license. A hardware project
    I was working on, was canceled, when some executive discovered we
    were using silicon chips from the company we were dragging through
    court. Which likely cost them a lot more than $2 million if they'd
    just paid up and my project had gone ahead. So not only were we
    looking for our $2 million, we also stopped buying parts from them.
    And we ordered (small-value) parts in lots of one million at a time,
    so the orders aren't exactly value-less. But for some companies,
    it is "personal, with the executives". The executive would sooner
    set the earth on fire, than pay a licensing fee. If you get away
    without paying a license fee, you have the most huge shit-eating
    grin on your face. And even if your company loses money via
    the decision, the exec gets to do his little dance.

    Paul
    --- Synchronet 3.21a-Linux NewsLink 1.2