If my partition table was bad the computer wouldn't be able to detect the file system on my hard disk at all, however that is not the case. In addition, I know that the first stage of the boot loader is working fine, as my laptop is successfully loading the "ntldr" file, which is the second stage of the Windows XP boot process.
If my MBR was bad, the ntldr file most likely wouldn't be able to be loaded. If a bad MBR was to blame I really shouldn't be able to get to phase 5 in the boot process-- I would instead probably be halting at phase 2 or 3. I don't really know if any of the three suspects that I mentioned above are to blame for my booting problem, but that is the direction that I am currently going to investigate in right now.
In any case, thanks for your suggestions thus far-- they may have not solved my problem, but I don't mind having ideas bounced off of me. In the mean time I am going to continue to keep on trying to troubleshoot this problem. Everyone please feel free to keep posting their troubleshooting solutions or suggestions, and if I somehow manage to solve this problem on my own I will definitely post the solution here so that others with the same problem can benefit from it.
The 1st was made for Win XP. XP Pro was installed 1st. The 2nd partition was for Win 7 and was installed after Win XP was setup. Exact same file size and date. No help. Thank you for your time. Threats include any threat of suicide, violence, or harm to another. Any content of an adult theme or inappropriate to a community web site. Any image, link, or discussion of nudity. Any behavior that is insulting, rude, vulgar, desecrating, or showing disrespect. Any behavior that appears to violate End user license agreements, including providing product keys or links to pirated software.
Unsolicited bulk mail or bulk advertising. Any link to or advocacy of virus, spyware, malware, or phishing sites. Any other inappropriate content or behavior as defined by the Terms of Use or Code of Conduct. Any image, link, or discussion related to child pornography, child nudity, or other child abuse or exploitation. Details required : characters remaining Cancel Submit. Restart your system and it will boot just fine, but you will have two events in the Event Viewer System log:.
Then reboot into the Recovery Console and put in a "corrupt" drvmain. Reboot normally and XP will boot just fine with the same two messages in the Event Viewer System log and a third message:.
So you have verified that XP will boot just fine if the drvmain. The problem with troubleshooting the message is nobody tells any details about how the system got into this condition in the first place - what happened prior to the incident of not booting? Editing the registry will not help - unless you edited the registry beforehand and messed it up somehow. Running fixmbr will not help since there are no symptoms indicating a missing or corrupt MBR and the Microsoft engaged Support Engineer "expert" fails to warn that if your system has a built in Recovery Partition from the factory, you will not be able to use it after running fixmbr.
These are just more of their wild goose chases when they have no idea what the problem is or how to fix it. There is something else wrong and without knowing what happened prior or any other system details all you can do is start guessing and trying things, or pursuing wild goose chases and I tend not to waste time on such things.
Thank you in advance for your help, and hopefully someone here can shed some light on this! This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
I have the same question 7. Report abuse. Details required :. Ntldr, then, loads the two files that make up the core of XP: Ntoskrnl. These files must be located in theSystem32 folder. You can improve your booting time of windows xp just by using startup manager. Windows XP and Vista. The following files are optional when starting Windows XP: Ntbootdd. Dual booting means two operating system installed on PC. Dual booting is only a term you can install more than one operating system on one PC.
There is a process called Dual Booting, but it requires two hard drives. Just search for "how to dual boot windows vista and windows XP? Because windows 7 has stablity updates the same as windows vista dose, windows xp uses unsupported service packs.
All Windows XP discs are bootable anyway, and it is very unlikely to be worthwhile installing Windows XP on a machine that isn't capable of booting from a CD. INI z. Windows 7 automatically recognises XP and allows you to install in a different partition and while booting it presents with a menu from which you can choose XP or 7.
Other than using more disc space to contain both operating systems, there are no inherent disadvantages. Windows XP is a general name given to sevearl operating systems released by Microsft in the early 's. Yes, it is called dual booting. By dual-booting. You install them both to the same computer and choose between them at boot. Gypsum partitions are created for interior solutions, not on Windows XP.
Step 1: Partition the hard disk. Step 2: Format the hard disk and install Windows XP. Log in. Windows 7. Study now. See answer 1. Best Answer. To understand my sentence well: GPOs are forced in synchronous mode. Imagine your boot time.. If correct, your profile is loaded:. The user thinks Windows is ready.. All startup entries loaded: — the ones in msconfig, like Office Communicator and Adobe Reader, etc… — the ones in the RunOnce Registry key of course, only one time — the ones in the Run Registry key forever… — the startup folder.
ALL of these items are performance killers and can and should be avoided. Your user is probably already checking his emails at that time, unconsciously swearing at Outlook for being slow while basically Windows is still not finished booting simply because you asked it to….
Skip to content Aha you made it. Windows is loading! Thank you Kernel! Winlogon Phase : This phase in the boot process is where I have found lots of misconfigurations. If you are domain joined you need to query the DNS of your AD Site to get the SRV record of the nearest domain controller… Not to mention the Computer account still needs to initiate authentication against that domain controller… You can say this takes a bit of time..
Just for the sake if the blog page, I will cover the GPOs in a next topic. The ntuser. Explorer Init this phase initializes the firstrun setup configuring IE etc… an then shows the desktop.
PostBoot Phase: All startup entries loaded: — the ones in msconfig, like Office Communicator and Adobe Reader, etc… — the ones in the RunOnce Registry key of course, only one time — the ones in the Run Registry key forever… — the startup folder ALL of these items are performance killers and can and should be avoided.
Like this: Like Loading
0コメント