also what does your msdos.sys look like? it is a hidden file so you will have to run attrib msdos.sys -s -h -r so you can look at it and possibly edit it if need be...all os this is possible if you can get the system to boot from the startup disk
got a HP xt963 system here that just will not start windows. system turns on makes the usuall noises then goes to a black screen and will set there about 20 min then shows the message:
windows could not start because the following file is missing or corrupt
<windows root>\system32\hal.dll...
depending on your os boot to dos and run scandisk and allow it to fix your free space...granted 20gig is not going to show as 20 gig but 17.2 is a little low
while in dos type
edit config.sys
and then put a
REM
in front of the lines that deal with these files, any sound drivers listed in config.sys or autoexec.bat are for dos support only not windows..it shouldnt keep you from booting to windows
I do not believe you can edit any ntfs partion using dos...it will not be able to see it...there may be some software out to allow it but im not sure what it is
Operating System Not Found" Error Message When You Start the Computer
http://support.microsoft.com/default.aspx?scid=kb;en-us;321626&FR=1&PA=1&SD=HSCH
go into the bios and set it to boot from the harddrive only...if it still gets stuck disconnect the harddrive and set it to boot with a floppy and see what happens
the checksum error usually indicates a dead battery unless the battery was removed..which you said you did. did you see this checksum error after that? I have never seen one that would keep the system from powering on though...dont know if it is possible or not but there might be a problem with...
a couple of things you could have tried first before reinstalling everything
How to Recover from a Corrupted Registry That Prevents Windows XP from Starting
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q307545
HOW TO: Start the System Restore Tool from a Command Prompt in Windows XP...
What i would do is gointo msconfig startup and shut down all apps and in services anything not pertaining to microsoft and see if they reappear..then if they dont start putting stuff back 1 at a time to see which is causing the files to be created and then maybe we can work from there
i tried what mot98 suggested on a windows me machine and it didnt work...finally found a site somewhere talking about it that said the method above would only work on a domain, not a stand alone
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.