Hi All,
I've got a Phoenix BIOS v.4.06 Rev.1.16 for an Siemens D1217 board.
Since it is an OEM-Version no Ident-Number is supplied in the BIOS.
Now I'm looking for a tool to flash an Ident-Number in the BIOS.
Does anybody know where to find such a tool.
Thanks everybody oin advance.
Yours
Tobias
Flashing Ident-Number in BIOS
If you are looking for a tool to edit a BIOS message at start-up, such as MODBIN for the Award BIOS, there is not one for the Phoenix BIOS.
Tested patched BIOSes. Untested patched BIOSes.
Emails *will* be ignored unless the subject line starts "Wim's BIOS forum"
Emails *will* be ignored unless the subject line starts "Wim's BIOS forum"
Hi NickS,
Thanks for your reply.
I'm not trying to change the startup message.
My problem is that in this particular motherboard the BIOS Ident-Number together with the NICs MAC-Address forms the computer's GUID.
Without an individual Ident-Number, however, all GUIDs are the same, which really ruins my efforts to do an automated install via PXE-Protocol.
Yours
Tobias
Thanks for your reply.
I'm not trying to change the startup message.
My problem is that in this particular motherboard the BIOS Ident-Number together with the NICs MAC-Address forms the computer's GUID.
Without an individual Ident-Number, however, all GUIDs are the same, which really ruins my efforts to do an automated install via PXE-Protocol.
Yours
Tobias
But the NIC's MAC address *should be* unique, so the GUIDs should be unique...
Tested patched BIOSes. Untested patched BIOSes.
Emails *will* be ignored unless the subject line starts "Wim's BIOS forum"
Emails *will* be ignored unless the subject line starts "Wim's BIOS forum"
Yes, there should be no two network cards with the same MAC address.
Patched and tested BIOSes are at http://wims.rainbow-software.org
UniFlash - Flash anything anywhere
UniFlash - Flash anything anywhere
Hi All,
yes I know. And my cards' MAC-Addresses *are* unique.
I sniffed the DHCP-Discover packets to confirm it. The MAC-Address is correctly transmitted, however the GUID in the DHCP-Discover packet is *really* always the same.
This thing with the GUID being calculated from the MAC-Address and the BIOS Ident-Number was brought up by a Siemens TechSupport Guy.
Yours
Tobias
yes I know. And my cards' MAC-Addresses *are* unique.
I sniffed the DHCP-Discover packets to confirm it. The MAC-Address is correctly transmitted, however the GUID in the DHCP-Discover packet is *really* always the same.
This thing with the GUID being calculated from the MAC-Address and the BIOS Ident-Number was brought up by a Siemens TechSupport Guy.
Yours
Tobias
Have a look at the following URL for editing the Phoenix BIOS:
http://www.wimsbios.com/phpBB2/viewtopic.php?t=2294
http://www.wimsbios.com/phpBB2/viewtopic.php?t=2294
Hi guys,
I'm having this exact same problem.
The mainboards are ASRock 775VM8.
I'm running version 1.40.
Just to summarize:
All computers get the same GUID which makes networkinstalls impossible. They do have unique MAC-addresses but the GUID is not being generated by that even if it is supposed to.
I'm thankful for any tips you guys might have.
*First post, this seems to be a very cool forum with a lot of knownledge*
Update: I contacted ASRock and asked for a solution and they provided me with a BETA BIOS (Version 1.40E) which did fix the problem. I asked if I could post the BIOS here but they said No. So if you are having this problem, contact ASRock at Asrock_TSD@asrock.com.tw.
I hope this helps someone
I'm having this exact same problem.
The mainboards are ASRock 775VM8.
I'm running version 1.40.
Just to summarize:
All computers get the same GUID which makes networkinstalls impossible. They do have unique MAC-addresses but the GUID is not being generated by that even if it is supposed to.
I'm thankful for any tips you guys might have.
*First post, this seems to be a very cool forum with a lot of knownledge*
Update: I contacted ASRock and asked for a solution and they provided me with a BETA BIOS (Version 1.40E) which did fix the problem. I asked if I could post the BIOS here but they said No. So if you are having this problem, contact ASRock at Asrock_TSD@asrock.com.tw.
I hope this helps someone