Post by Ant Post by pjp
I suspect if you use Disk Management to delete the Mac partition you can
then create a NTFS partition and things should be fine after that.
Apparently Ext32 can write/read by both OS's if you want/need to use it
I tried to use 64-bit W7's Disk Management to remove all partitions, but couldn't do all. :(
FAT32 is read/write on Windows/Mac/Linux
NTFS is read/write on Windows/Linux, with Linux not having reparse points
supported in livecd-based mounts, and (maybe) FUSE mounts having some
support. This makes deleting some Win10 content on NTFS, a problem.
MacOSX support was read-only for the longest while, and I cannot tell
you what epoch full support might have been switched on. This could
be a patent/licensing issue of some sort, rather than a technical issue.
Linux has no problem messing up NTFS for users :-) (Journal state
invalidated, dirty bit set, cannot access hibernated OS partitions...)
EXFat support, not sure. WinXP is via separate package. Linux by FUSE
file system (not enabled by default necessarily on a LiveCD),
MacOSX only recently.
I generally "have no fear" with FAT32 or NTFS.
There are a couple IFS packages so you can mount Linux EXT partitions.
The Mac HFS/HFS+ usually has some tools for interworking, so it's
not a dead loss. Linux can copy files off Mac partitions.
UFS is the tough one (Unix File System). That might be
as used in FreeBSD.
To fix USB flash sticks, you can try Diskpart (the command line equivalent
of Disk Management).
select disk 0
clean <--- zeros the MBR
clean all <--- zeros every sector
A USB flash stick should not support Secure Erase. Secure Erase was
added to the ATA standard a number of years ago. It might not
exist in SCSI (and maybe SAS). But it should exist on SATA and IDE.
Secure Erase erases every sector, MBR and all. Enhanced Secure Erase
not only erases every sector, it (attempts) to erase all "spare" sectors
on the drive. Spare sectors that are not normally accessible via the IDE
interface. The Enhanced flavor is a kind of forensic erasure.
Diskpart cannot work, if the device refuses to show up as a
"row" in Disk Management. For a storage device which is
annoying you, run Disk Management first. The disk numbering
in Disk Management, is "similar" to DiskPart, but not necessarily
the same. Some of the interfaces in Windows are zero-origin, and
some are one-origin. Lots of things are "in the same order",
but watch the numbering carefully.
So if the objective here was to not use Linux, your
two options are
1) diskpart, clean or clean all, of a selected disk
2) dd.exe as a means to zero any sector your heart
could desire. With "seek" and "skip" you can rip
and tear anything you want, with byte precision.
For example, with dd.exe, you can replace the 446 bytes
of boot code in the MBR, without affecting the partition
table. As long as you have a second disk drive, with a sample
of those 446 bytes to use. Many other operations will be
done with sector-level accuracy (whatever the native
sector happens to be).
dd --list # administrator command prompt, use this command
# to get the "disk names"
dd if=/dev/zero of=\\?\Device\Harddisk3\Partition0 # Erase the fourth disk completely
# Needs more params, for speed reasons
I don't like to erase whole Flash devices, because it
wastes one wear cycle. But if you absolutely must get
on with your life, that's how you can do it.
Zeroing the MBR works for MSDOS partitioning.
Zeroing the MBR as well as the 128MB GPT partition table,
works for GPT. Zeroing the MBR *might* have worked, except
too many utilities "sniff" the remaining GPT and this defeat
your attempts to move on in life. The utilities "assume"
you want GPT forever after, if they "sniff" that table.
It can be trying at times, to work with USB flash sticks,
but with enough hammers, you'll eventually succeed.