I was able to restore an old hard drive and boot from there, hooking the bad
C drive as a second. Now I have found a file in "WINDOWS/pss" folder called
"boot.ini.backup". Is this the file I need to delete?
:
In theory it can work. Have fun trying. You need a windows CD.
--
--------------------------------------------------------------------------------------------------
Read David defending the concept of violence.
http://margokingston.typepad.com/harry_version_2/2005/10/entering_the_ga.html#more
=================================================
command prompt option only takes me to "A:\>". I guess it takes you to dos,
but I can't get into C drive, keeps telling me wrong drive specification.
Can't get anywhere from there, not that fluent in compter usage. I know
alot, but no formal training in anything like this.
I downloaded the three versions of the boot disk stuff, can I just pack what
all would be going to the floppy onto a cd? I am running XP Home with SP2
added, so which one would I use? I have plenty of cds, but no floppys here.
The pc crashed is at home, had to come to the office to continue working on
it. I might have a windows cd availablefrom somone, won't know untill later
today.
:
You need an XP CD. What is that command prompt option. Is that a recovery console?
--
--------------------------------------------------------------------------------------------------
Read David defending the concept of violence.
http://margokingston.typepad.com/harry_version_2/2005/10/entering_the_ga.html#more
=================================================
delete boot.ini from the hard drive? I could if it would boot. Can that be
done from DOS, if so how can I get it to boo to dos?
My floppy drive is shot, but it will boot from cd, can I save it to cd and
go that route?
:
Can you edit files on the disk? You need to edit or delete (only if Win is in a folder called windows or winnt) boot.ini.
What is
boot to comand prompt from cd
option.
Recovery console available from floppy boot here (
http://support.microsoft.com/kb/310994). Else find a windows CD. Ask your neighbour.
--
--------------------------------------------------------------------------------------------------
Read David defending the concept of violence.
http://margokingston.typepad.com/harry_version_2/2005/10/entering_the_ga.html#more
=================================================
ok, I will try that, but now my problem is it will not boot at all. I set it
to boot into safe mode using the msconfig utility, now it will not boot up at
all using any option from the F8 screen or the failed boot screen. I need to
get it out of this loop now, how can I do that? I do not have a windows disk
to boot from, only the restore disks from the mfg. The only options I get
are "restore" and "boot to comand prompt from cd". If at all possible I want
to try avoiding restoring it again. Thanks for any help you can provide.
:
Type verifier in Start Run, follow the wizard but choose All Drivers. This will slow down your computer and cause more blue screen crashes but will pinpoint what is causing the crash (if the original error message didn't). Once you fix it you rerun verifier and turn it off.
If you can't start after enabling verifier
choose Last Known Good Configuration at the Failed Boot menu (which will
start without verifier).
You will be creating a crash dump file in c:\windows\minidump every blue screen. Make sure you are set to record minidumps (Small Memory Dumps) - type it in Help to see how.
Then
If you have the XP SP2 Security Update CD (else see
http://www.microsoft.com/whdc/Âdevtools/debugging/symbolpkg.mÂspx
)
Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS
Download
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
Load the crash dump file into windbg
and read what it says. You may need to tell it where the symbols are. Read it.
Type
!Analyze -v
into Windbg's command line.
(this will hopefully tell you the faulty component)
If the above is too technical then email the crash dump files to david @ mvps.org. Don't send me lots of them. Just the one from your last crash after you turn verifier on. And only one per mail.
You can look up specific details here
http://msdn.microsoft.com/library/d..._ea8b9fd0-2d81-4a04-a7ed-c1c6a80bd501.xml.asp
If it indicates faulty memory might be the cause you can get a memory tester
here
http://oca.microsoft.com/en/wiÂndiag.asp
If it mentions a core windows system file, meaning it a MS fix is required,
upload a minidump to
http://oca.microsoft.com
Also try typing the main error code in Help while online (ie,
Stop 0x50
and also try in the 8 digit form
stop 0x00000050)
and if there are too many hits use a filename if available. Generally memory
addresses are different for each computer (as each computer has a different
mix of drivers) so parameters that are memory addresses aren't that useful for searching, but NTStatus codes are (plus you can look them up here
http://cvs.sourceforge.net/viewcvs.py/mingw/w32api/include/ddk/ntstatus.h?rev=1.2).
If this doesn't work try
Get your XP CD and install Windows Support Tools.
Type in start run after installing and rebooting
pstat > "%userprofile%\desktop\driverlÂist.txt"
The last table in this file is a list of loaded drivers. Other things apart
from hardware uses drivers. Post the list of drivers (the last table only -
REPEAT THE LAST TABLE O N L Y ) or match the fault address to the driver.
This will allow you to match memory addresses to a driver.
--
--------------------------------------------------------------------------------------------------
Read David defending the concept of violence.
http://margokingston.typepad.com/harry_version_2/2005/10/entering_the_ga.html#more
=================================================
trying to boot in regular safe mode and safemode with command proompt I get:
Stop: 0x0000000A (0F8FC1354, 0x000000FF, 0x00000001, 0x804E2E41).
trying to boot to safe mode with networking I get: Stop: 0x0000000A
(0F8FC5354, 0x000000FF, 0x00000001, 0x804E2E41).
That is all the info I can think to give you, if you need other info just
ask me and I will provide.
:
Why are you spoon feeding the information????????????
Give it all!!!!!!!!
try getting to safe mode by using Msconfig utility. then select safe boot
:
"IRQL_NOT_LESS_OR_EQUAL"
I even have the "technical details" too if needed.
:
What is your exact error message?
:
Tried all recommended, but nothing seems out of the ordinary. This ONLY
happens when I try to boot to safe mode, boots normaly otherwise. I am
baffled as to where to begin to try to troubleshoot this.
