MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically.
Search the Community
Showing results for tags 'NTFS'.
Found 4 results
-
Hello, everyone. I recently did a fresh install of Microsoft Windows NT 4.0 Workstation inside Virtual PC 2004, allocated 64 MB memory to the VM, created a fixed 4 GB hard disk (4,095 MB) image, partitioned and formatted the hard disk as NTFS v1.2 file system. Windows NT 4.0 installed without a hitch. However, when I used a disk mounting utility called IMDisk to view the contents of the partition formatted as NTFS, Windows 2000, the host OS upgraded the NTFS partition to version 3.0. After I unmounted the hard disk image, I powered up the Windows NT 4.0 Workstation VM again and when I attempted to run the CHKDSK command, I get this error message: I looked at this page regarding Windows NT 4.0 CHKDSK refusing to check NTFS v3.0/v3.1 volumes (KB196707) and it wasn't very much of a help at all. What baffles me is that I looked at this forum thread, NT4 NTFS Versions by nt4-ever on 2007-07-19 and it mentioned hacks and workarounds including NTFSCHK, a utility to run the Windows 2000 version of CHKDSK from Windows NT 4.0 and another utility called Mark4NTFS, a Windows NT 4.0 utility to revert the partition from NTFS v3.0 down to NTFS v1.2. I tried to download a utility called Mark4NTFS.zip and found that the site that was hosted on it was gone! There was also mention of the KB872952 hotfix, but I can't seem to find the hotfix available for download at all either. Are there any good utilities or disk hex editing hacks that will help fix this problem? I know that the consequences are that every time I attempt to mount a NTFS v1.2 formatted volume with IMDisk under Windows 2000 or Windows XP, it will upgrade the version of the file system on the mounted hard disk image. Let me know what you can come up with. -
After much of tests i was able to write a Powershell Script, that replace, all inherits of all folders and subfolders (even the one with long names), without taking the Ownership ! Reasons: - Taking the Ownership of a Windows Folder can make much Problems ! (I dont like solutions, that can make more problems than they solve, and i even dont like it, if people say, dont change Permissions of systemfolders blabla - Me, the Owner of my Harddrive, like to have R/W Permissions to all Folders, but some folders get there permission inherit from a Top Folder, and so, i wasnt able to set their permissions... so many commands iacls, dir -ad, some powershell commands and ways, just didn´t do it, but i was able to to it (R4 never gives up...) 1) You need to allow Powershellscripts - in a Powershell console (with Adminrights) run: Set-ExecutionPolicy RemoteSigned (maybe "unrestricted could do the job too, you can set it back to restricted later) 2) Then run the script (with Adminrights too) 3) THis could take a while !!! Some really rare folders (probably Symbolic NTFS Links, Junctions or Similar) give Errormessages, - you can ignore it ! cd "C:\" foreach ($i in Get-ChildItem -Recurse -Force| ?{ $_.PSIsContainer}) { echo $i.FullName $acl=Get-ACL $i.FullName $acl.SetAccessRuleProtection($True, $True) Set-Acl $i.FullName -AclObject $acl } (this little success brings me some steps forward, in getting a clean os, - next step is setting r/w permissions for buildIN Admin, and then check the 1355 dll´s i identified, that can be called by regsvr32) - (maybe i could replace reginherits too...) mfg R4D3 Edit: Uhm, sorry my Script seems to switch all folderinherits like 180 degree (good for folders with inherits, but not for folders without - SetAccessRuleProtection($True, $False) seems to be better, and with giving Adminrights this hopefully does it: Edit: Just moved $acl.SetAccessRuleProtection($True, $True) before the new rule (cause, first the existing inherits must be replaced with local one, before the new-Object Rule, took them off and give Built-In Admin permissions.... cd "C:\" foreach ($i in Get-ChildItem -Recurse -Force| ?{$_.PSIsContainer}){ echo $i.FullName $acl=Get-ACL $i.FullName $person=[System.Security.Principal.NTAccount]"BUILTIN\Administrators" $access=[System.Security.AccessControl.FileSystemRights]"FullControl" $inheritance=[System.Security.AccessControl.InheritanceFlags]"ObjectInherit" $propagation=[System.Security.AccessControl.PropagationFlags]"None" $type=[System.Security.AccessControl.AccessControlType]"Allow" $acl.SetAccessRuleProtection($True, $True) $rule=New-Object System.Security.AccessControl.FileSystemAccessRule($person,$access,$inheritance,$propagation,$type) $acl.AddAccessRule($rule) $acl.SetAccessRule($rule) Set-Acl $i.FullName -AclObject $acl }
-
Windows NTFS Compression and Native Boot VHD/ VHDX? Issues or Conflicts? I am currently cleaning out my Windows 7 x64 Ultimate SP1 for a 2 step upgrade > Win 8 > Win 8.1 and then will convert it to VHD. I have this \Windows\Installer folder that is taking a lot of space and seems to be unused mostly. Eventually, I wish to clean it out/ delete it or major stuff inside it. But, till then I was considering "compressing" option it as suggested here instead of delete/ remap right now. http://superuser.com/questions/23479/is-it-safe-to-delete-from-c-windows-installer http://superuser.com/questions/707767/how-can-i-to-free-up-drive-space-from-the-windows-installer-folder-without-killi If I do this right now (during Win 7 > 8 > 8.1) I am wondering this will cause any issues creatingin or running the VHD? I googled around for VHD and NTFS compression and did not find anything good or bad either way (with exception that Windows XP and VHD had some issues) http://blogs.msdn.com/b/virtual_pc_guy/archive/2007/05/24/be-careful-with-vhds-and-windows-xp-compressed-folders.aspx -
Hallo I have searched Google a Little, and found this site, and I can see you are pretty hardcore about drives which are strange.. I have my laptop, and after a update (Windows 8 to 8.1) my computer won´t boot anymore. The strange part is that during the update (i was not at my computer when it was updating, it turned off) When I use Disk Part to reveal my drive, I can see my drive with Windows 8 is now a Raw Drive, and not a NTFS. Can you help me fix that, without formatting the drive? Here is a Logfile from testdisk quick scan. http://www29.zippyshare.com/v/24558047/file.html (somehow I´m not permitted to use THIS site uploader?)
