"reset BIOS Settings"

gonlaz · 05-07-2006, 07:22 PM

This is the advice I get when having a "This device is disabled because the firmware of the device did not give it the required resources. (Code 29)" Issue.

How safe is this? I know how to get into BIOS for other things, but I am a bit afraid to reset the BIOS settings for fear of somehow being locked out of my cheap little computer. All I want to do is enable the LPT 1 for my new printer.

I have reset configuration settings as an option, would this be the correct choice?

gonlaz · 05-07-2006, 07:25 PM

P.S. Here's my motherboard type, if it's important to this topic:

INTEL Type: AL 440LX (tested to comply, etc)

05-07-2006, 08:11 PM

Most of the time hardware incompetibilities are fixed by BIOS updates. Resetting BIOS is not harmful or hard in anymeans. To reset BIOS you can ;

1-take out the motherboard battery for 10-15 mins ( computer unplugged )
2-reset it by the cmos clear jumper on the mother board.

To update BIOS you will have to download the BIOS update from the manufacturers website and apply it. It is a very simple but delicate process. This information below might help you understand the BIOS update concept.

Quote:

In 90% of cases, a BIOS update is released to address a problem with a particular piece of hardware or software.
Therefore, the new BIOS gives the system some new (different) parameters to work with. Newer BIOS'es contain all fixes from previous versions. If the fix list of a new BIOS does NOT address any of problems that you may have, it is unreasonable to update BIOS only for sake of it, because you may be using a combination of hardware/software that is incompatible and not yet tested with the BIOS version you're upgrading to.
It is recommended to refrain from updating BIOS without a good reason. If you don't see your problem listed in the fix list, do not update BIOS and update your software or do something less dangerous.
And finally, some 10% of BIOS updates contain new CPU ID strings and code enhancements (ACPI, etc.). For those an update is recommended only when it is necessary (i.e. the processor ID does not display properly, the system must have ACPI, etc.).
A typical situation occurs when a user wants to update BIOS because the new version supports a CPU he/she "plans" to buy sometime in the future. With some bad luck, the user ends up with a wrong BIOS (wrong PCB, or chipset, or I/O or all of them) and consequently damaged BIOS chip.

Looks like the motherboard is pretty old and intel no longer provides help or releases BIOS updates for it. I am thinking its time for an upgrade. But you still may try a BIOS update. If you havent done it before I would recommend someone experienced to do it.

Regards.

gonlaz · 05-08-2006, 11:36 AM

Thank you for the reply. I went ahead and reset the settings, and voila! My LPT port was there and it works well now. I just have to figure out my monitor problem.

05-07-2006, 07:22 PM	#1 (permalink)
gonlaz Registered User Join Date: Oct 2003 Location: I live in Texas Posts: 66 OS: Windows XP Professional	"reset BIOS Settings" This is the advice I get when having a "This device is disabled because the firmware of the device did not give it the required resources. (Code 29)" Issue. How safe is this? I know how to get into BIOS for other things, but I am a bit afraid to reset the BIOS settings for fear of somehow being locked out of my cheap little computer. All I want to do is enable the LPT 1 for my new printer. I have reset configuration settings as an option, would this be the correct choice?

05-07-2006, 07:25 PM	#2 (permalink)
gonlaz Registered User Join Date: Oct 2003 Location: I live in Texas Posts: 66 OS: Windows XP Professional	P.S. Here's my motherboard type, if it's important to this topic: INTEL Type: AL 440LX (tested to comply, etc)

05-08-2006, 11:36 AM	#4 (permalink)
gonlaz Registered User Join Date: Oct 2003 Location: I live in Texas Posts: 66 OS: Windows XP Professional	Thank you for the reply. I went ahead and reset the settings, and voila! My LPT port was there and it works well now. I just have to figure out my monitor problem.