Hello all - I've been following the discussion here with some interest, as I am also the not-so-proud owner of a Presario C700 series (C762NR) laptop, as well. After spending a number of hours cozying up to HP and talking with outside experts, I've uncovered a few facts of interest I thought I'd summarize here:
1) HP has created more than its share of confusion by naming different BIOS revisions for different laptop series with the same Letter & Number designations; ie., BIOS revision F.27 for the dv6000 series is a completely different (and INCOMPATIBLE) file from revision F.27 for the Presario C700 series - this can be easily proven by looking at the unpatched files on HP's website, which in this case even demonstrates a fundamental shift in copy protection, as well - the dv6000 files are all .WHP formatted, while the C700 files are all InsyderH20 compressed and encrypted. DON"T make this mistake - if you are able to actually flash your laptop BIOS with the wrong patched BIOS file, welcome to brick city!
2) I have yet to run across a comprehensive, concise one-stop guide to flashing the Atheros/Broadcom WiFi cards to match the whitelisted values for each laptop series. There are bits and pieces scattered over a number of forum topics, which can be a daunting proposition to research. I am in the process of compiling the data I can verify- someone with more programming proficiency will have to take the lead; I'm willing to help if we can really assemble this all in one place. My reason for this? It's far less tedious and less of an adventure in returning a dead motherboard, if all you've done is foul up your removable WiFi card - if you brick the BIOS, your bad day has just begun.
3) HP (and Intel's Insyde) have indicated they will continue to convert all new laptop designs to the closed architecure of the "locked and secured" BIOS - so development of good decompilation and editing tools for these BIOS images should be a priority - not just to further WiFi deployment, but for all "internal peripherals" at risk of becoming inaccessible.
4) The programming community here is comprised of some of the best and brightest minds outside Apple (and maybe inside, too...); I'd like to thank all of them for their longstanding devotion and contrbutions to this project. What is still needed is a better "roadmap", to allow more users to more easily locate the topics that affect them, and "drill down" to discover an existing solution more quickly. (An "executive summary", perhaps, at the top of each subject listing?).
Just a few musings -
I'll post again when I've had a chance to better organize some of the data I've mentioned ($ where my mouth is, as they say...)