7 replies
by jhazard112 Accepted solution
by older mycroft Accepted solution
The file you are referring to is at the very heart of the operating system you are currently using.
In [u]finding[/u] this file [u]using[/u] whichever [u]file manager[/u] is your preference, then [u]highlighting[/u] this file and attempting to [u]access[/u] it by [u]executing[/u] [u]Notepad[/u] EACH UNDERLINED ACTION was being controlled (to a greater or lesser extent) by the very file you are trying to 'look' at.
In much the same way as you cannot Delete a file if it is still being used by another process, you also cannot Examine a file while it is in use.
The file you are talking about, is CONSTANTLY in RAM therefore not available to the User.
Try this:
You can attempt to repair this file by starting windows setup using the original setup CD-Rom. Select "r" at the first screen to start repair. Do NOT use an OEM "Recovery Disc". Only a valid Windows XP media will work or a disc from the OEM that says "Operating System" may sometimes work depending on how the manufacturer labeled the CD.
by jhazard112 Accepted solution
by cmatthews Accepted solution
Boot with a live Linux such as Knoppix, rename the current file to SYSTEM.old and copy an earlier version of SYSTEM (from the RP folders) in \System Volume Information.
As for getting this from another system, don't.
The hash codes within the other SYSTEM file are likely different.
by jhazard112 Accepted solution
by cmatthews Accepted solution
..by imaging (if that's how you roll-out configurations in your shop). SID's are XOR'ed somehow to codify the registry (especially the SAM). They change a little more when joined to a domain. Check the SID's of several domain machines on your network and compare. Use PsGetSid here:
http://technet.microsoft.com/en-us/sysinternals/bb897417.aspx
This video's kind of cool..
http://www.youtube.com/watch?v=PmwlkyTomVs
Cheers
by slayer_ Accepted solution
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending