A Guide to BIOS OC HP 8600gs with drivers ABOVE 169.04

LOL

fair enough.

I even found the biometric reader....n i c e !!

 

biometric reader?

 

well, I found the part number: EM717AAR, but it is no where on the web...inc HP....shizer!

 

You guy's knows where is the X16 video card is located, I looked at the service manual and couldn't find it?

 

My DV6500 with 128 megs memory (8400M GS) is oc'd to 584\547\1168
and stable!

 

WTG! sounds like you got the hang of things now.

 

Here is a screen grab from the DV6500.

It would seem that the 128 meg version is VERY oc'able.

I wonder why....

 

I lowered the settings, I will test them before making the BIOS change.

The DV6500 has the same F.45 upgrade as the DV9500....

 

i cant even get that high on memory with my card.

 

I wasn't even going to bother with the DV6500, it is a glorified VCR for the Sony LCD TV connected to it but when I saw the same BIOS update and RivaTuner worked, I thought I'd give it a try. The most this computer does is play downloaded episodes of DS9/Voyager, SGI and BSG on the TV.

Tough life it has.

 

ought..., bios give me a post beep at boot and no display now
any ID how to reflash now?

 

i watch all them shows!...lol

 

what did you do....

 

I edit the oprom1 the same as oprom2 and flashed the new f45 made bios
and ....
I did flash without editing the oprom1 and it worked fine..
now I need to see at least set up but all i get is no display
work fine but back screen (tried external vga, no result)

 

you used the wrong file...

oprom2 only and not touch the oprom1

 

fastest way to see if you can get lucky is...take out battery, unplug power cord and take out cmos battery....

if that doesn't work...your gonna need to make a bootable cd and do a dos flash

 

Why would you edit both files?

 

yes why?? tell me...
well even with a rescue disk: no display, just waiting to clear cmos now
I will post back shortly..

 

ergo this: Re: A Guide to BIOS OC HP 8600gs with drivers ABOVE 169.04
fastest way to see if you can get lucky is..

 

I wasn't trying to be sarcastic, just curious because I thought about doing the same thing when i did mine, a way to be sure I had the correct file but I went with my gut and followed the steps given, which didn't say not to do both but by the same token, it doesn't say to do both.

 

lets hope we get very lucky here....

and you can try the fn +f4 a few times to see if it will kick in your external monitor

 

Step 7) Open nibitor and then go down the list of OPROM files that you have saved to your desktop. I believe nibitor will only read 1 OPROM file without giving you errors, and this one will display your correct default stocks for your card.

 

nothing yet..

 

I red Step 7) but edited the 2 oprom they both said nvidia..
anyway..

 

not sure if i understand correctly...

1: you edited oprom1
2: you edited oprom2
3: then flashed bios
4: no screen on boot

is this correct?

 

yeap - I got 1 long beep and 2 short beep on boot -
I can boot up from my cd with a minipe but the screen is back.

 

trying ext monitor now, if I coud see on a ext monitor I can reflash so easy with my minipe..

 

tuff break, because i just opened like 3 different oprom1.rom files and not one of them say nvidia. they all say device id:0427. so that already is not a good thing...

 

The external VGA should work.

If not, I seem to remember in the old days a way of flashing via a floppy.

Can this be done here?

 

hmm, can you tell if the computer boots to the OS even though it isn't visable? If so, make a batch file on another computer, burn to CD and make it autorun. Then insert it into your CD drive after a point when you think it is in Windows and let it reflash. It is a complicated procedure but it would work.

 

no luck on a external monitor - I'm running out of ID now.
not sure what the boot beep mean: 1 long 2 shorts
the func f4 doesn't work for Ext monitor.

I can flash so easy if I could see....
maybe a boot cd with autorun bios flash could be made
I don't know how to write that script.

 

yea, me either....still over here thinking of something else you can try

 

maybe it's time for the HP call.....

 

Does it load the OS?? can you tell by listening to the HDD if it loads the OS?

Did you have it set to make a sound once in Windows?

Does the NUM Lock and Caps Lock key still light up indicating they are on?

If they do, I'd say it isn't locked up, just not displaying.

In that case, think back to how your computer behaves when it loads
the OS, presumably Windows. You need some sort of sign it is in Windows, perhaps have it autoplay a music CD?

As for creating a batch file...I made some years ago...I'll see what I can find.

 

try pulling the memory....

 

http://www.computerhope.com/batch.htm#01

 

Thanks a lot guys for all your insights - just back from lunch..
the keypad look like it's locked and get unlock in bios - no sign from the HD light that is working toward OS boot. just puzzling
will try to strip HD and see..
thanks for the batch file site.

 

Here is the problem: post bios beep explained
1 long, 2 short Indicates a video error has occurred and the BIOS cannot initialize the video screen to display any additional information

exactly what I have..

 

Will try to find some info about to flash bios with a dos cd boot auto mode
like you said Zenica..

This is the only solution right now: autoflash from boot cd

 

I haven't had to make one in a long time, since Windows 98 but I
know it can be done. There are programs out there that can do it
for you as well, they act like "installers" or a *.exe file.
http://en.wikibooks.org/wiki/Blender_3D:_Noob_to_Pro/Making_exe
http://www.instantexe.com/

 

You would need something that can be set to autorun so that
it starts when told to by a batch file.

To give you an idea, you need a CD that has DOS, or a boot CD.
(John, Acronis can make this for us, perhaps it can be tweaked?)
On the boot CD will be a batch file set to start on boot, from a file
like autoexec.bat. This batch file to point to the flashing utility and
tell it to start. After that, it will do its thing and reboot. One glitch I see
is the flashing utility prompts you at some point and I know the response
can be put into the batch file but I don't know how.

 

I think a simple autoexec.bat with the right script should do it

I'm close to get all the tools to make one..

 

No luck.. going to repair

 

shizer.

What happened? or what did it do?
How did you try it?

 

I tryed hard to recover and flash a new bios from dos.. I even use a recovery crash bios from phoenix no luck...

best guess don't ever edit the OPROM1.. all I can say that it could be tied to Bios display setup..

learn hard..

Back to OC in 12 days....

 

Damn.

Well, it is a lesson not soon forgotten.

My Mom always says, education is expensive.

I had hoped a CD boot method would work.

 

Oh man, i'm sorry to hear that. When it comes to anything with the bios, everyone should be careful to follow every step of guides correctly, and take every precaution whenever possible. Like i said before, if you follow the guide step by step, its fairly safe to flash back to default clocks from windows if you accidentally overclock too much, but editing other parts of the bios without knowing what they are is just a recipe for disaster. I guess its how it goes though with anything. I took the risk of experimenting with bios versions and the editor, and johnkzzz took the risk of trying my method with the 512 cards. Now we know not to EVER touch that oprom1 file. I'll go ahead and edit the first post to make that very clear for others who will want to try this out.

Hope everything works out in the end. You can always tell them that you had a power failure (battery was taken out) when you were trying to update your bios, and see if they buy it.

 

i got it, but not sure if it will work or if you can get your hands on any of this stuff...

but, you can get a usb or pcmcia video card or even a port replicator and see if it will boot thru

 

say knives, i tried to get at the cpu settings, but i cant... i havent given up on it yet..but did see a few interesting things in there and i did make a few changes.... nothing major mind you....

 

Actually, i havent been able to edit anything major myself either. It seems that the route we would have to approach it from would be to extract parts of the bios and use another program that can read in and alter those values, similarly to how nibitor does for the vbios. I dont think we'll find a way to simply change values within the editor. If there is a way to 'unlock' features with a 0, 1 type of function, thats probably as far as we can go.

by the way, i think i recall you saying you lowered your graphic card's voltages in nibitor. Were you able to test for instabilities or lower temperatures as a result of it? It would probably only be noticeable under full load.