Resolved Compaq d530 sff, bios will not update, bios settings will not be adjusted

Hello, this is my first post here. I repair windows XP problems but have run into a situation where I need some additional help.

I am working on a HP/Compaq d530s Small form factor PC

Pentium 4 2.8GHz
40 gig hard drive
2 gig ddr 400 ram

I am trying to adjust bios settings without success. I believe this particular system came from a school system where bios configuration was written in masse.

Two problems I would like to resolve: to successfully update bios #1
to have bios allow changes

What I have tried: Have cleared CMOS
attemped bios update through floppy and within windows using utilty called HPQ flash

both without success...process begins ok...then fails

seems I am locked out

Any thoughts?

 

Any particular reason why you want to update the BIOS? You should not do this unless you have a specific problem.

 

Wildfire, Thank you for your reply.

My desire to update the bios was specific to having the system potentially better recognize type and style of ram. It seem the memory controller is not properly identifying the ram memory. For instance it will show DDR 400 as 166MHZ and so forth.

Further...I do not find it acceptable to return a system to customer that I cannot adjust bios settings in. The bios allow you to view the settings but not change any values....

 

OK, regarding the inability to change settings I'd start by looking at your CMOS battery. It is an old system and quite likely that has failed.

Regarding the upgraded BIOS, where did you source it from? (link please but be aware this will need to be approved so be patient)

 

The cmos battery is operational and not the cause of problem. What is cause is what seems to be another device or chip onboard used for mass loading of redundant information across a school network.

The link I used was from the compaq and hp website....I do not suspect any issue with the link, since I tried multiple times ....it is not an odd third party link....was directly from HP site.

 

Fair enough, only other two things I can think off is dodgy RAM (I encountered a similar problem with a Dell system) or if you rule that out contact the previous owners for details to remove this security device/chip...

I'll direct you to our posting rules...

I believe your aforementioned "device or chip" would fit into the above category.

 

I am not circumventing any useful and intact security that pertains to this machine. As I had mentioned to you previously this machine was purchased from a computer recycling center and originated from a School network where many desktops were present and likely loaded together and configured together. HP has a system called "insight" that allows mass loading of bios onto multiple machines simultaneously, I suspect that this is the issue here and was looking for a way to make bios updates and changes possible so computer can be usefull. Operating system and hard drive are both new since this machine was used at a school and old hard drive was replaced. No security issue is present for previous owner. The school system upgraded all system and "recycled" old systems...this is one of the old systems

 

Security has several meanings stumptown, but since you believe HP installed the security system in place that should be your next port of call.

 

I found the solution. There is a jumper located next to the cmos clear button. It changes the machine from a local machine to network controlled machine for administrator control or local user contol so the computer can be used and configured either way. I pulled the jumper, cleared the cmos again, and then the update to bios was allowed. With the update, I was then able to update the chipset driver which granted a new smbus controller and memory controller.

I could not find the answer to this from forum or manufacture. When I got stumped I got out my magnifying glass and flashlight and searched the motherboard and found the jumper. I thought I would post it for those who need to make bios changes and might be in need of having their computer properly recognize the ram installed. I had tried 6 different pairs of ram prior to my first post on this topic to rule out a bad or improperly recognized set.

Happy computing

 

Glad to see you got it sorted, I hope you understand the confined area in we have to tread but since it wasn't a security (or chip/device) issue all is well