![]() ![]() ![]() In that case you really either need to mount it in an operating system that does support read-only mounts, or, best of all, use a hardware-based write-blocker. This is a suitable technique for troubleshooting but is not a suitable technique for forensic purposes. In particular, toggling this bit and forgetting to toggle it back off prevents Windows from booting when you return the disk back to the source system. You're modifying the disk to prevent it from being modified. The change you're making using diskpart to toggle a readonly attribute on the volume is making changes to the "read-only" disk. It's definitely not like a read-only mount on a *nix operating system. There is a built-in mehanism to mount a filesystem read-only in Windows, sort of.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |