How to Hack Protected Windows XP Files - Using Wininit.ini on legacy systems.
(Page 5 of 5 )
Older Windows and DOS systems use a text file named Wininit.ini in the Windows directory for performing these operations. This file uses a standard INI file setup. Each operation appears on a single line in the [rename] section. Our above example would look like this in a Wininit.ini file:
[rename]
C:\Windows\renamed.txt=C:\Windows\original.txt
NUL=C:\deleteme.txt
C:\newdir~1\original.file= C:\original.file
In a Winint.ini file, each operation is on a single line. File name pairs are listed in reverse and separated by an equals sign. In other words, the new file name or path is listed first.
Note the use of the NUL indicator when performing a file delete. Older DOS systems will require 8.3 formatted paths and names while newer systems supporting LFNs will have no issues with spaces. The Wininit.ini file is also case insensitive.
Newer Windows versions supporting long file names will accept them in the Wininit.ini file; however, the rename operations will be written using the short file name equivalent.
While newer versions of Windows will support the Wininit.ini method for compatibility, it is highly recommended that you avoid this method whenever possible. You should always use the PendingFileRenameOperations registry key whenever available.
One last scenario to consider is when you wish to edit a file that is absolutely necessary for Windows to boot such as NTDETECT.COM or ntldr. There is no way to edit or replace these files from within the Windows operating system. You will need to boot into an alternative environment that can provide you with hard disk access.
Well, that pretty much wraps it up. You should now have all of the tools you need to edit or replace files that are either in use or protected by Windows. Please use this information with caution as I am in no way responsible if destroy your system.
Also understand that editing such files may very well violate user agreements and void warranties. Please be prepared to accept these responsibilities should you decide to attempt these changes.
I hope you’ve all had a chance to learn something. In my opinion it’s always good to take a deeper look at how things work. Until next time…
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
/ 10 
