now i have patched my atheros wifi card an the xp driver
the links are her tiny.cc/hjdwB
thanks 2 all
How to > HP BIOS MiniPCI Fix- nc6000/others
Hi guys...
Some time ago (let's say more than a year) I tried to modify the BIOS of my old nc4000 laptop... unfortunately for me I screwed it up! and the laptop does not boot anymore... it keeps re-booting all the time and I'm not even able to see anything on the screen.
I've been looking from that day on for a solution on Internet.. I mean: how to recover the damn BIOS! all that I found is about recovering Phoneix BIOSes...
I tried all the possible solutions.. using an external USB floppy drive and no luck
Any IDEAS???
Thanks in advance,
Patricio
Some time ago (let's say more than a year) I tried to modify the BIOS of my old nc4000 laptop... unfortunately for me I screwed it up! and the laptop does not boot anymore... it keeps re-booting all the time and I'm not even able to see anything on the screen.
I've been looking from that day on for a solution on Internet.. I mean: how to recover the damn BIOS! all that I found is about recovering Phoneix BIOSes...
I tried all the possible solutions.. using an external USB floppy drive and no luck
Any IDEAS???
Thanks in advance,
Patricio
Hi All,
First of all thanks for looking into this problem! I really appreciate all your hard work.
But unfortunately I dont understand something.
I have a NC6000 and bios is F.15
I bought a wireless intel 2200BG card.
Of course I got the 104 message.
When I wanted to use the ADDCC tool I noticed that the string for my wifi card already is listed in the original bios!
(this is the complete string: PCI\VEN_8086&DEV_4220&SUBSYS_12F6103C&REV_05\)
So what do I need to adapt to get this working?
I'm confused.....
First of all thanks for looking into this problem! I really appreciate all your hard work.
But unfortunately I dont understand something.
I have a NC6000 and bios is F.15
I bought a wireless intel 2200BG card.
Of course I got the 104 message.
When I wanted to use the ADDCC tool I noticed that the string for my wifi card already is listed in the original bios!
(this is the complete string: PCI\VEN_8086&DEV_4220&SUBSYS_12F6103C&REV_05\)
So what do I need to adapt to get this working?
I'm confused.....
I have same problem. I want to use my nc6000 with a not whitelisted card. I make the changes on the bios file, but at the crc checksum corrigation point i'm stucked. The program say: Select another string. But i don't understand where form select it. I'm using F15 bios with PCI\VEN_168&DEV_0013&SUBSYS_2051168C&REV_01.Bastian wrote:Hi All,
First of all thanks for looking into this problem! I really appreciate all your hard work.
But unfortunately I dont understand something.
I have a NC6000 and bios is F.15
I bought a wireless intel 2200BG card.
Of course I got the 104 message.
When I wanted to use the ADDCC tool I noticed that the string for my wifi card already is listed in the original bios!
(this is the complete string: PCI\VEN_8086&DEV_4220&SUBSYS_12F6103C&REV_05\)
So what do I need to adapt to get this working?
I'm confused.....
Thanks for a help!
-
- New visitors - please read the rules.
- Posts: 7
- Joined: Fri Jul 10, 2009 1:17 pm
Hello. Please try and find the String Wake which is a part of Wake On Lan-like string and try to use it for checksum Correction Good Luck !
Hi!NetworkPro wrote:Hello. Please try and find the String Wake which is a part of Wake On Lan-like string and try to use it for checksum Correction Good Luck !
Thank you so much for the help! It's work like a charm
I am not that much interested in card whitelist at the moment (no need yet)
But what is interesting is the checksum correction (after SLIC change to 2.1)
semi does the example (first post page 5), but it is just checksum32
Same is nicely explained in this thread xtremesystems. org/forums/showthread.php?t=180607
But my HP BIOS checks CRC32
Anybody knows the way to correct CRC32 for modded HP BIOS - ftp.hp. com/pub/softpaq/sp41501-42000/sp41979.exe
Also using WinHex (no matter what hash method I chose) I can NOT get the same values like computed by ADDCC - anybody knows what ADDCC uses?
Thanks
sebus
But what is interesting is the checksum correction (after SLIC change to 2.1)
semi does the example (first post page 5), but it is just checksum32
Same is nicely explained in this thread xtremesystems. org/forums/showthread.php?t=180607
But my HP BIOS checks CRC32
Anybody knows the way to correct CRC32 for modded HP BIOS - ftp.hp. com/pub/softpaq/sp41501-42000/sp41979.exe
Also using WinHex (no matter what hash method I chose) I can NOT get the same values like computed by ADDCC - anybody knows what ADDCC uses?
Thanks
sebus
@ Sebus,
the 68YTT.BIN file looks like a "normaly" HP Compaq-Bios. There is
no CRC32 cheksum in it. Or show me exactly where!!
The checksum is a additive 4byte checksum. very simple...
Use the "new" ADDCC.
@ All my fellows,
there is a "new" ADDCC - V2. Muha
And here are some video tutorials...
Video.Tutorial.68BDD.V1
Video.Tutorial.68BDD.V2
Video.Tutorial.68DTH.V1
Video.Tutorial.68DTH.V2
cheers Semi
the 68YTT.BIN file looks like a "normaly" HP Compaq-Bios. There is
no CRC32 cheksum in it. Or show me exactly where!!
The checksum is a additive 4byte checksum. very simple...
Use the "new" ADDCC.
@ All my fellows,
there is a "new" ADDCC - V2. Muha
And here are some video tutorials...
Video.Tutorial.68BDD.V1
Video.Tutorial.68BDD.V2
Video.Tutorial.68DTH.V1
Video.Tutorial.68DTH.V2
cheers Semi
-
- New visitors - please read the rules.
- Posts: 7
- Joined: Fri Jul 10, 2009 1:17 pm
Thank you semi! This is the coolest!!! I hope it works good Oh and Video Tutorials oh this is GREAT!! THANKS so much!!
Hi thanks for nice work
Recently I was trying getting work my new wifi in nc8230 and got error massage 104 so starts looking on web and found another interesting way how to fix it.
1. Boot laptop to win and put it to sleep mode
2. replace your old wifi card module for new one
3. start/wakeup your lapy and let windows find new HW, install drivers, etc... Connect to any network, make sure it works.
4. now funny bits after you restart or switch of you will be expecting 104 unsupported device massage but there isn’t any and win will normally boot and everything still working. I did unplug charger and remove battery for while and when I replug back still work so can somebody explain how that is possible???
I’m not sure if this does work on all HP laptops or only nc8230
Recently I was trying getting work my new wifi in nc8230 and got error massage 104 so starts looking on web and found another interesting way how to fix it.
1. Boot laptop to win and put it to sleep mode
2. replace your old wifi card module for new one
3. start/wakeup your lapy and let windows find new HW, install drivers, etc... Connect to any network, make sure it works.
4. now funny bits after you restart or switch of you will be expecting 104 unsupported device massage but there isn’t any and win will normally boot and everything still working. I did unplug charger and remove battery for while and when I replug back still work so can somebody explain how that is possible???
I’m not sure if this does work on all HP laptops or only nc8230
I hope you can understand that this is completely overwhelming to read at all once. I have a Compaq nc6000 and trying to replace wireless card.
The card I have is an Xterasys XG-601. I have used the standby method to determine that: "ven_1260&DEV_3890&SUBSYS_001417CF".
I downloaded the f15 latest bios from the HP website (DOS floppy version). I have opened the .bin file with Cygnus (program suggested on page one).
I have found and replaced the first device in the whitelist with my device information.
Next, I used the HP USB boot utility to make a bootable USB stick and put the DOS flash files onto the USB drive. I was able to run the bios flash utility and update the bios from the edited .bin file..... the computer is NOT bricked and boots fine, except that my card is still not whitelisted. I get the same old 104 error.
I do not know what I am doing wrong. I saw a post from someone else that they followed these same directions and it worked on their nc6000.... but for somereason i still get the 104 error. Please help. What might I be doing wrong?
I went ahead and changed the first entry (for an Atheros card)
From this: 8C 16 13 00 11 F7 0E E5 00
To this for my device: 60 12 90 83 CF F7 17 14 00
At or arround lines 00006140 ~ 00006160
Please bear with me I do not work with hex very often at all. I havnt had any other errors in saving updating or flashing the bios, nor running the machine. I have no idea what this talk is about the checksum... all I know is, i added my device informaiton but am still getting the error 104 please remove wireless card message. Please help.
[/code]
The card I have is an Xterasys XG-601. I have used the standby method to determine that: "ven_1260&DEV_3890&SUBSYS_001417CF".
I downloaded the f15 latest bios from the HP website (DOS floppy version). I have opened the .bin file with Cygnus (program suggested on page one).
I have found and replaced the first device in the whitelist with my device information.
Next, I used the HP USB boot utility to make a bootable USB stick and put the DOS flash files onto the USB drive. I was able to run the bios flash utility and update the bios from the edited .bin file..... the computer is NOT bricked and boots fine, except that my card is still not whitelisted. I get the same old 104 error.
I do not know what I am doing wrong. I saw a post from someone else that they followed these same directions and it worked on their nc6000.... but for somereason i still get the 104 error. Please help. What might I be doing wrong?
I went ahead and changed the first entry (for an Atheros card)
From this: 8C 16 13 00 11 F7 0E E5 00
To this for my device: 60 12 90 83 CF F7 17 14 00
At or arround lines 00006140 ~ 00006160
Please bear with me I do not work with hex very often at all. I havnt had any other errors in saving updating or flashing the bios, nor running the machine. I have no idea what this talk is about the checksum... all I know is, i added my device informaiton but am still getting the error 104 please remove wireless card message. Please help.
[/code]
semi,
I am back at it again and this time I am trying your version 2.
When I use the "Find Whitelist" button the window that opens does not show the Backward, OK, or Forward buttons. I can tab to get to them and enter works but that is not the best.
I am not sure what shifting is needed for the "best" position.
Also sometimes I get everything looking right and do the final correction however the resulting checksum does not match the original.
BTW, is you video tutorials supposed to have audio?
- Fred
I am back at it again and this time I am trying your version 2.
When I use the "Find Whitelist" button the window that opens does not show the Backward, OK, or Forward buttons. I can tab to get to them and enter works but that is not the best.
I am not sure what shifting is needed for the "best" position.
Also sometimes I get everything looking right and do the final correction however the resulting checksum does not match the original.
BTW, is you video tutorials supposed to have audio?
- Fred
hey fred,
the "best" position is if the whole id is in it. The maximum length
is eight bytes plus one decompress byte. In worst case plus 4 bytes to
decompress, I've never seen this. I gave you 12 bytes to shift four bytewise.
If that is to rough you can shift bytewise. I've never used this option.
"Marty, you dont think fourth dimensional!"
The most newbie's choose the wrong 4 bytes for correct the checksum.
If you search the string "wake" you will maybe find it as shown down.
But if you choose exactly this 4 bytes its wrong. Checksum will be never
correctable. The right choose is directly below. If the values are suffice
to correct it is another question.
They are all bytes, except the "FF", allowed to change for fixing the checksum differences.
Good luck again...
Cheers semi
the "best" position is if the whole id is in it. The maximum length
is eight bytes plus one decompress byte. In worst case plus 4 bytes to
decompress, I've never seen this. I gave you 12 bytes to shift four bytewise.
If that is to rough you can shift bytewise. I've never used this option.
"Marty, you dont think fourth dimensional!"
The most newbie's choose the wrong 4 bytes for correct the checksum.
If you search the string "wake" you will maybe find it as shown down.
But if you choose exactly this 4 bytes its wrong. Checksum will be never
correctable. The right choose is directly below. If the values are suffice
to correct it is another question.
They are all bytes, except the "FF", allowed to change for fixing the checksum differences.
Good luck again...
Cheers semi