PDA

View Full Version : Laptop Start Up Problems


YOUNEK
September 10th, 2002, 08:56 AM
I have win/me come up when I start my laptop when I hold dwn the ctrl key it list normal, bootlog, safe mode and step by step confirmation.

I dont know the correct way to answer the (y) or (n) questions on the confirmation.
So I push safe mode.
When I do this it comes up with a Windows Protection Error= Restart- System Halted.
I do not have a Start up Disk for Win/me .

Could anyone tell me how I can resolve this problem?
I have been to the website of other sites with no help what so ever and I am tired of dealing w/this problem.
I would love to get my Laptop up and running again.

Please Help
Younek@webtv.netI do have the win/me cd but the cd wont run it will just go to the a drive when a disk is present.

AnnMarie
September 10th, 2002, 09:20 AM
Hi YOUNEK - welcome to CTH. Can you please give us a little more information. The make and model of your laptop and as much information on the background to your problem as you can. For example, what you were doing when the problem first happened, did the problem co-incide with the installation of new software or hardware, anything that might help us to help you. Can you boot to windows?

enat66
September 10th, 2002, 09:53 PM
try asking a friend who has windows ME to give you their boot disk. (I think that will work if someone knows it won't please say so, It's worth a shot)

Theoran
September 11th, 2002, 06:49 AM
Windows Protection error messages can occur under any of the following conditions:
If a real-mode driver and a protected-mode driver are in conflict
If the registry is damaged
If either the Win.com file or the Command.com file are infected with a virus, or if either of the files are damaged
If a protected-mode driver is loaded from the System.ini file and the driver is already initialized
If there is a physical input/output (I/O) address conflict or a random access memory (RAM) address conflict
If there are incorrect complementary metal oxide semiconductor (CMOS) settings for a built-in peripheral device (such as cache settings, CPU timing, hard disks, and so on)
If the Plug and Play feature of the computer's basic input/output system (BIOS) is not working correctly
If the computer contains a malfunctioning cache or malfunctioning memory
If the computer's motherboard is not working properly
If you installed Microsoft Office 97 and you are using the Novell Client 32 software
To resolve a Windows Protection error message:
Start your computer in Safe Mode
If you do not receive the error message when you start your computer in Safe mode or when you shut down your computer from Safe mode, view one of the following articles:
Windows 95:
Troubleshooting Windows 95 Startup Problems (http://support.microsoft.com/support/kb/articles/Q136/3/37.ASP)
Troubleshooting Windows 95 Shutdown Problems (http://support.microsoft.com/support/kb/articles/Q145/9/26.ASP)
Windows 98:
Troubleshooting Windows 98 Startup Problems (http://support.microsoft.com/support/kb/articles/Q188/8/67.ASP)
Troubleshooting Windows 98 Shutdown Problems (http://support.microsoft.com/support/kb/articles/Q202/6/33.ASP)
Windows ME:
Troubleshooting Windows Me Startup Problems (http://support.microsoft.com/support/kb/articles/Q273/7/38.ASP)
Troubleshooting Windows Me Shutdown Problems (http://support.microsoft.com/support/kb/articles/Q273/7/46.ASP)
If your computer is a Plug and Play computer, reinstall Windows by using the setup /p I command
If you are using the Novell Client 32 software, remove it, and then install Microsoft Client for Novell Networks.
Verify that the computer's CMOS settings are correct. For information about how to change CMOS settings on your computer, view the computer's documentation or contact the computer manufacturer.
Install a "clean" copy of Windows in an empty folder. Choose the Custom installation option and do not allow Windows Setup to detect the hardware in your computer. Instead, install only a mouse, a VGA video adapter, and a keyboard.

IMPORTANT: If the error message still occurs, it is most likely caused by faulty hardware.