3 ms·

Mind, the trickest part of dealing with pre-4.0 is mounting the file system, assuming the OS was placed onto NTFS rather than FAT. A couple of times I've tried

by einr 9y ago

Mind, the trickest part of dealing with pre-4.0 is mounting the file system, assuming the OS was placed onto NTFS rather than FAT. A couple of times I've tried mounting an NT 3.51 disk in a modern Windows 7 system and while it works (you can read from and write to it fine,) once you even mount it, NT 3.51 will never boot from that disk again. It hangs during the blue NTLDR stage. I'm not sure what would ever possess anyone to think it a good idea to write to a filesystem immediately upon mounting it, but Windows 7 does something to old NTFS volumes which renders them incompatible with NT 3.x.

jaclaz 9y ago
Most probably the filesystem is updated (silently), like it happened historically. In the good ol' times there were free demo CD's of Windows 2000 (90 or 120 days trial), everyone (that was running NT 4.0) tried them. Those with NT 4.0 already up to SP 4 had no issues (but chkdsk stopped working) all the ones with earlier service packs had unbootable machine (if the NT 4.00 was on NTFS). At the time there were a couple "workarounds" for the CHKDSK issue, one by Sysinternals/Mark Russinovich NTFSCHK and one, Mark4NTFS by M. Tartsch. Just in case: https://msfn.org/board/topic/169500-chkdsk-refuses-to-check-ntfs-volume-under-windows-nt-40/ https://msfn.org/board/topic/169500-chkdsk-refuses-to-check-... But no idea if the mark4NTFS can help for NT 3.x.