using the recovery console have you used 'fixboot' and 'fixmbr'? Run these first then chkdsk after a reboot. Next check the hard drive is being 'seen' in the BIOS, if it is download a hard drive diag tool for you drive and run the full test to make sure the hard drive isn't about to fail. Maxtor do a 'general purpose' one if you are unable to find the Hard drive makers diagnostic tool.
just a wild thought: when you installed a 2nd os and reduced the windows partition, maybe the partition resizing wasn't done correctly and now the windows bootloader can't find and load all of the necessary windows modules?
I'm cheating... I'm replying to all who offer help (greatly appreciated) in one post.
madx:
Tried the cd system32 .exe to .old and then the copy c:\windows\system32\dllcache\ntoskrnl.exe ...command string.
no dice, "the system cannot find the file specified"
I didn't see a suggestion from mcafee where was/is it.
networkassociate:
did the "fixboot" all that did was write a new boot sector, so still uable to check HD or install any HD dianostic tools.
thanhvn:
there is only one OS on the "box", where the 2nd partition came from I haven't a clue. But I did see that it is ONLY 38KB in size w/37KB available.
As Paul Harvey would say..."and now the rest of the story"
The Laptop is not mine, it belong to a friends of ours 13 years old son.
He could of by chance done it but I doubt it. I don't know if Dell shipped that way or what? Again I would not think so, what good is a 38KB partition?
Still in a quandry as to the "fix" on this port-a-box...problem still exist.
Any more suggestion...I'm open to just about anything at this point!!!!!!!!!!!!!!
The hard disk may not be failing. It seems that he/the child has possibly messed with the boot.ini file; the second partition of 1 Kb seems to point to that possibility.
Maybe by overwriting the current boot.ini file from a boot.ini off a floppy might have it boot to windows; it seems he's booting to the 38 Kb partition so that overwrite is probably not sufficient in itself. Possibly using the diskpart command from the recovery console to delete the small partition will have to come in to play with or without the overwrite.
networkassociate or anybody, If you have experience with this you can take it from here. If I'm off track let me know.
If this is the first time you’ve seen this stop error screen, restart your computer. If this screen appears again, follow these steps:
Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any windows updates you might need.
If the problem continues, disable or remove any newly installed hardware or software. Disable BIOS Memory options such as caching or shadowing. If you need to use SAFE MODE to remove or disable components, restart your computer, press F8 to select Advance Setup Options, and then Select Safe Mode:
Blue Screen! Neither esc, enter, CTL-ALT-DEL would shut down or restart computer, had to shut (HOT) down via power button.
Rebooted from CD got same message.
F8 will not work…all I get is a lot of loud beeps.
NO new software or hardware has been installed.
Entered back into recovery Console, Tried too run Windows setup, with the second “ R”, (restore), got his msg...another BLUE SCREEN.
“A problem has been detected and windows has been shut down to prevent damage to your computer.
Check for viruses on your computer. Remove any newly installed hard drives or hard drive controllers. Check you hard drive to make sure it is properly configured and terminated.
Run chkdsk /f to check for hard drive corruption, and then restart your computer.
Your system is 'stuck' in the 38-kb partition. Don't know what caused this. A boot sector virus possibly but I don't think so. If you have a reference floppy disk (aka rescue disk), (you can make one from an option on any AV program) you could run it on the system if it has a floppy drive.
As I mentioned before I think your only recovery is to delete the small parttion with the diskpart command in the Recovery Console as shown in the following link.
You could try the MBR fix as already mentioned first; both of these options have significant risk but I have nothing else to give you. I've reached the outposts of my limited knowledge
networkassociat
56 Posts
0
May 5th, 2005 15:00
maxd
2 Intern
•
2.4K Posts
0
May 5th, 2005 15:00
With Method 3, I suggest this:
cd system32
ren ntoskrnl.exe ntoskrnl.old
expand d:\i386\ntkrnlmp..ex_ c:\windows\system32
ren ntkrnlmp.exe ntoskrnl.exe
maxd
2 Intern
•
2.4K Posts
0
May 5th, 2005 16:00
cd system32
ren ntoskrnl.exe ntoskrnl.old
copy c:\windows\system32\dllcache\ntoskrnl.exe c:\windows\system32
exit
mcafee's suggestion may well work; I don't know.
Q. Do you have a dual-boot setup on your machine ?
thanhvn
75 Posts
0
May 5th, 2005 19:00
stridier
3 Posts
0
May 6th, 2005 00:00
networkassociat
56 Posts
0
May 6th, 2005 05:00
networkassociat
56 Posts
0
May 6th, 2005 05:00
maxd
2 Intern
•
2.4K Posts
0
May 6th, 2005 13:00
The hard disk may not be failing. It seems that he/the child has possibly messed with the boot.ini file; the second partition of 1 Kb seems to point to that possibility.
Maybe by overwriting the current boot.ini file from a boot.ini off a floppy might have it boot to windows; it seems he's booting to the 38 Kb partition so that overwrite is probably not sufficient in itself. Possibly using the diskpart command from the recovery console to delete the small partition will have to come in to play with or without the overwrite.
networkassociate or anybody, If you have experience with this you can take it from here. If I'm off track let me know.
stridier
3 Posts
0
May 10th, 2005 20:00
Correction.
If a DELL person is out there IE Moderator, and you know the solution....PLEASE respond,
I have tried all listed below to no avail, problem just seem to be excalating.
I am about to just reinstall, but still wonder is the 2 partitions are really neccessary,
one for FAT 32 (small partition) and another for NTSF.
See above and below for original problem/error message, what I've done to try to correct the problem and results NOT accomplished.
Please assistance requested...............HELP!
Well guys I've tried all the suggestions alas I am still not getting any way.
Here is the new "stuff" that pops up...maybe that'll give a better clue;
Ntoskrl.exe missing saga continues.
Finally got it to run the CHKDSK /R. got this msg at the end.
“A problem has been detected and window has shut down to prevent damage to your computer.
The problem seems to be caused by the following file: PARTMGR.SYS.
DRIVER_UNLOAD_WITHOUT_CANCELLING_PERDING_OPERATION
If this is the first time you’ve seen this stop error screen, restart your computer. If this screen appears again, follow these steps:
Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any windows updates you might need.
If the problem continues, disable or remove any newly installed hardware or software. Disable BIOS Memory options such as caching or shadowing. If you need to use SAFE MODE to remove or disable components, restart your computer, press F8 to select Advance Setup Options, and then Select Safe Mode:
Technical Information:
***STOP: 0X000000CE (0XF94EA667, 0X00000000, 0XF94EA667, 0x00000000)
partsmgr.sys”
Blue Screen! Neither esc, enter, CTL-ALT-DEL would shut down or restart computer, had to shut (HOT) down via power button.
Rebooted from CD got same message.
F8 will not work…all I get is a lot of loud beeps.
NO new software or hardware has been installed.
Entered back into recovery Console, Tried too run Windows setup, with the second “ R”, (restore), got his msg...another BLUE SCREEN.
“A problem has been detected and windows has been shut down to prevent damage to your computer.
Check for viruses on your computer. Remove any newly installed hard drives or hard drive controllers. Check you hard drive to make sure it is properly configured and terminated.
Run chkdsk /f to check for hard drive corruption, and then restart your computer.
Technical Information:
***STOP: 0X0000007B (0XF9687640, 0XC00000034, 0X00000000, 0X00000000)”
Again had to HOT shut down.
Rebooted from CD went to Recovery Console, tried the chkdsk /f got the invalid parameters msg. Did the chkdsk /? And it only show the /p and the /r
HELP!
Message Edited by stridier on 05-15-2005 09:59 AM
Message Edited by stridier on 05-15-2005 10:02 AM
maxd
2 Intern
•
2.4K Posts
0
May 10th, 2005 21:00
These are my best thoughts:
Your system is 'stuck' in the 38-kb partition. Don't know what caused this. A boot sector virus possibly but I don't think so. If you have a reference floppy disk (aka rescue disk), (you can make one from an option on any AV program) you could run it on the system if it has a floppy drive.
As I mentioned before I think your only recovery is to delete the small parttion with the diskpart command in the Recovery Console as shown in the following link.
You could try the MBR fix as already mentioned first; both of these options have significant risk but I have nothing else to give you. I've reached the outposts of my limited knowledge
http://www.webtree.ca/windowsxp/repair_xp.htm#How%20Partition%20using%20the%20Recovery%20Console: