Discussion Locked

win95 doesn't Normal boot..caught in reb

0 helpful
21 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Working on a HP Vectra VLi8 that has worked in the past but will not boot now. No new software added within last month and no usual devices attached.

It gets past the splash screen to the 'Starting Windows 95...' and then hangs for about 30 seconds then reboots. The PC will boot into Safe Mode and I tried disabling Network and Display drivers.

Interestingly the most recent bootlog shows failures to load fonts. Is this the possible cause? Corrupt System.ini? Any suggestions would be appreciated.

Thanks.

21 replies

by dmiles

This may cause a problem as you stated,so you can use the boot disk and reinstall the System.ini,and the other files,then update the service packs.
If you can boot into safe mode you might be able to do a step by step configuration.

by 9878445

a corrupt fonts folder may be the cause. I have never seen that reboot a machine though. Get tweak UI from microsoft and get the machine into safe mode and use tweak UI and have it repair the fonts folder. If that doesn't fix it if you are technically inclined you can remove all the pc cards in the system except for video and disconnect all your disk drives except the hard drive. if that fixes it add the devices back in 1 by 1 till you find the offending device

by 9878445

I would suspect that corrupt fonts could be an issue I have never seen that reboot a pc but I would obtain Tweak UI from Microsoft or a friend install it and use its font folder repair option, if that doesnt fix it and you are feeling technically savvy remove all pc cards besides video and disconnect all drives besides the hard drive if that fixes it add the drives in abd the cards in 1 by 1 untill you find the offending device.

by clover252525

Reboot your computer and as soon as the memory check is done, press (and keep pressing) F8 to bring up the Startup Menu. One of the options is Step-by-Step confirmation (should be just under Safe Mode). Chose that and go right through until the system stops. It should detect what driver or program has caused the problem to reboot.

clover

by tconklin

I had this happen once when I chanked the system fonts. Boot into Safe mode and change the default system fonts to something generic like Times New Roman. reboot. It's worth a shot, easier than a reload.

by mallen

Does the system have a NIC? If so, you might try removing it. I have had systems in the past caught in this 'boot loop' and the NIC seems to be the problem.

If the system boots when you remove the NIC, I would try replacing it.

Good luck.

by eramirez

While in safe mode go to >my computer>control panel>system>device manager. Disable as many devices as you can. Reboot, If system boots
turn on devices until you find the offender. If it doesn't boot make a pot of coffee because its gonna be a longday.

by chrisengland2

Long story short - it IS a problem with how many fonts are being loaded on a normal Windows boot. If you have a bootdisk that has CDROM drivers, boot from that and run Windows setup over the top of your existing Operating System. It will keep your system and settings virtually intact and let you boot back into Windows after the process is complete. Choose to repair and replace missing or corrupted files when prompted, and install to the same directory as your current Windows installation. If you don't have a bootable floppy with CDROM drivers, boot to "Safe Mode - Command Prompt Only" by pressing the F8 key before Windows starts, and then install DOS-Mode CDROM drivers from the disk that came with your CDROM drive. Reboot when it's finished, press the F8 key again, and choose "Command Prompt", and then run Windows setup from your Windows9X CDROM.

by feniks

I've seen a bad sound card driver cause a reboot loop on two seperate occasions. I was able to boot into safe mode and reinstall the driver to fix the problem.

by frank.torre

Reboot, hit F8 and go into step-by-step confirmation, hit ESC for both config.sys and autoexec.bat. I had a similar experience with a Sony VAIO and discovered that the HP DeskJet printer driver was the problem.

This discussion is closed to new replies.