Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[SHAD0Wdump]

Lately my computer has been hanging at the Emachines logo screen where I can access BOOT settings and BIOS settings, I've gone into both and discovered that, at times, the computer simply doesn't detect the BOOT program(chip? whatever). Strangely enough, I can start the computer with my external harddrive on, when it gets to the logo screen it becomes completely unresponsive, I then unplug the computer, plug it back in, turn off the external, then start my computer again, and for some reason it detects the BOOT again.

 I'm wondering about solutions, would a simple cleaning be it? My computer hasn't been cleaned for some time. Perhaps there is a hard disk solution? Or will I need to download a BOOT program to a flash drive(or get a BOOT disk, but the onboard disk drive is non-functional). I'm worried if I do the flash drive thing it will be all for naught because I might run into the same problem as with my external.

Please help me out here, I wouldn't want to lose you guys. O(

[Volatar]

I am currently working with Shad0w on this problem via Steam chat.

[Siquo]

Might be onboard battery, or just dust. Dust can do the strangest stuff.

But if you feel uncomfortable taking everything apart, cleaning it, reapplying your thermal paste, and putting it all back together, you should still do it. Follow the precautions (should be findable on the internet), remember what was connected to where, and you'll be fine

[SHAD0Wdump]

We are planning on... I think it was resetting the CMOS? Something like that.
 If I disappear, either yell at Volatar or assume my PC just decided to kick it.

[Volatar]

Yeah. Resetting the CMOS. We worked through pretty much all the other ideas I have on fixing it.

We have established that booting with the external HDD turned off is a consistent workaround.

[Siquo]

The external HD might be drawing too much power?

[Simmura McCrea]

Might be confusing the external HD and the internal's drive letters and looking for your OS on the external and going "Nope, not there. Not gonna check that other one". I'd expect something like that from Windows.

[romawillx]

1. floppy or CD-ROM. Disk Boot Failure can arise from number of sources. some reasons are corrupt bootable disk.
2. order of devices to boot from in BIOS setting
3. problem with IDE port of motherboard and many more.Check if the disk is properly inserted and is working fine. check all cabling connections in the computer system.
4. failing cable will produce these errors. Check if disk is not having any scratches and dust on it. If dust is there remove it and reinsert the disk and restart the system.
5. Check for your BIOS setting. Check for the order of devices to boot from.
6. A weak SMP could also be a reason. Check your battery for power supply.
7. Check your BIOS battery. A dead Bios Battery will also cause the same problem.
8. Remove your RAM from the motherboard and clean it with a piece of cloth and reinsert it properly onto the motherboard. Restart the system.

[Nikov]

...Emachines logo screen...

That there's your trouble, mister.

Also yeah, your computer is trying to boot from the external, probably since its recognizing it as a 'floppy disk drive' and the boot order usually prioritizes floppy disks over the hard disk (so if you need to boot with a disk, it knows that automatically, otherwise leave the disk out and boot normal. Yes, I'm old enough to remember making 3.25in boot disks for high performance games). Go into Setup, look for boot order, and make it boot from the hard disk first. This isn't a problem with Windows you silly Machipsters, since Windows isn't even being asked to start by the time this problem happens. Don't dick around with taking apart your car when its just a flat tire. Sure, nothing bad happens if you do it right, but rarely does it do any good and there's always that risk you screw something up.

[eerr]

I fear Nikov might be too late.

[Nikov]

Noooooooo!

[SHAD0Wdump]

Oh, right, forgot about this thread.

Anyway, after some fussing around with Volatar and the BIOS we disabled the 'removable media'(I think) search priority, we also switched to a more detailed launch screen.

However we did not actually discover what the real issue was, I've lately been shutting down my computer each night since then with no incident. It has booted every time, however I also havn't been running any programs from the external.(although I have been copying to it)
 My plan of attack right now is to continue shutting down my computer without using the external for more than copying, then if I still don't encounter the problem after a while I'll attempt to run a certain program I've become suspicious of, Project 64. If that causes it to happen again I'll attempt to run some other program if I can get it to boot again. If THAT causes a BOOT failure than it probably has something to do with the external iteself, if not, then it's P64 somehow causing it. And if P64 doesn't cause it to happen, then I suppose I'll consider the problem fixed by disabling the removable media priority.

[Nikov]

...oooh. Oh.

Yep, 'swhat I thought.

[ed boy]

Something similar happens with our computer.

If you try booting it up when the printer is switched on, it won't work. Booting it up with the printer off and then switching it on is fine, though. I don't think it has to do with boot order, as my dad works in IT support and that would be the first thing he tries.