New forum theme up and running!
Originally posted by Trevlacn the forensics, we had to do get in to the admin account on a machine with only a linux live boot. After the whole competition, I won 1st place. I need to take a pic of my medal...
Originally posted by ~*Sweet Ichifo*~Good thing the only game I play on my computer is Pac-Man..O_o.
Originally posted by OsmoseAccording to this and this , you are not, as Trevlac says, screwed. It's okay, Trevlac. We still think you're cool. We'd just appreciate it if you didn't try to brag without checking the facts. Just because you've used Linux doesn't mean you're a god.
Originally posted by RazorWell, too late.I've gone and reinstalled XP over the old one I'm going to have all my old stuff, however I will have to reinstall everything if I want to use it, and may have to reinstall my drivers too.Setup will complete in approximately: 34 minutes.Woo!
Originally posted by DragonBlazequote:Originally posted by ~*Sweet Ichifo*~Good thing the only game I play on my computer is Pac-Man..O_o.Pac-Man Thats the worst of all, if you lose, those damn ghosts get into your system and start eating all your files.
The first time you see the option to "Repair" XP, it's through the "Recovery Console", which is an advanced "command line" function. Skip that, continue to install XP as you normally would with a fresh install, you will get the "Repair" option again, this is the time to choose "Repair".It will install XP over top of itself, re-writing all the XP/Windoze files, but leave your games/files/programs intact.It takes as long as a regular install of XP, but you don't lose all your programs/files/etal.
this problem occurs when you try to update drivers in the computer..sometimes windows XP cannot update the driver and that corrupts system.ini file as it has a lot of bad entries..Due to this you will get this error mesage..No its not due to virus.its due to an attempt to change system.ini fileWindows could not start because the following file is missing or corrupt: WINDOWSSYSTEM32CONFIGSYSTEMThat means the System Registry Hive has become corrupted.There are two ways to get back up and running. The easy way which doesn't always work, and then there is the hard way.Easy Way --- Note that this doesn't always work.When you are booting your system, press the F8 key during the start of the bootup sequence, meaning after it does the Power On Self Test.Once you press the F8 key, you will be taken to a Menu. Select "Boot Using Last Known Good Configuration".It will now attempt to load Windows XP using a past set of configuration files.If that doesn't work, there is the next step....the hard way.Hard WayBoot your system with the Windows XP Install CD, let the system boot into the Setup. Once in the Setup, choose to run the Recovery Console.You will now be presented with a screen similar to good old DOS.First, we will recover the System Hive.Now, type in the following commands with pressing Enter after each line.md tmpcopy C:windowssystem32configsystem C:windowstmpsystem.bakdelete C:windowssystem32configsystemcopy C:windowsrepairsystem C:windowssystem32configsystemBe very careful when you are typing in these commands, one wrong move, and you have, broken Windows XP.Also, change the C in the commands to whatever your Windows XP drive letter is.Attempt to boot the system, if it doesn't boot, get back into the Recovery Console and do the following commands.md tmpcopy C:windowssystem32configsoftware C:windowstmpsoftware.bakdelete C:windowssystem32configsoftwarecopy C:windowsrepairsoftware C:windowssystem32configsoftware