Ok, here's what happend to me. I installed a bios savior on my A7N8X2.0 Deluxe. I flashed the bios savior to 1007 uber. When windows restarted i found that there is an entry in the network adapters section of the device manager that says "1394 net adapter #2" and it has a yellow exclamation next to it. The error code is "This device cannot start. (Code 10)". Now, my firewire does work fine and i don't seem to have any problems except for that error message.
So i used a method to find my NVMAC and NVGUID for the bios savior chip. It showed the same number for both; in fact all were the same digit. This is most likely why there is the flag for the 1394 net adapter.
Then I swithched the bios savior back to the original bios and used the same method to see what the NVMAC and NVGUID were for the original bios. They are both different (as they are supposed to be and had varied digits).
Now, since with the bios savior chip both numbers are the same (all the same digit) should I reflash the bios savior chip with: awdflash yourbios.bin /py/sn/cc/cd/cp/nvmac:XXXXXXXXXXXX/nvguid:XXXXXXXXXXXXXXXX/wb/e
using the addresses from the original bios.
I don't want to screw up anything as the network and firewire are working fine it's just that error message that bugs me. I do aparently have the option with the uber bios to change the Machine MAC(NV) address. Could i just change that address there and having a different could get rid of the flag in the device manager?
So i used a method to find my NVMAC and NVGUID for the bios savior chip. It showed the same number for both; in fact all were the same digit. This is most likely why there is the flag for the 1394 net adapter.
Then I swithched the bios savior back to the original bios and used the same method to see what the NVMAC and NVGUID were for the original bios. They are both different (as they are supposed to be and had varied digits).
Now, since with the bios savior chip both numbers are the same (all the same digit) should I reflash the bios savior chip with: awdflash yourbios.bin /py/sn/cc/cd/cp/nvmac:XXXXXXXXXXXX/nvguid:XXXXXXXXXXXXXXXX/wb/e
using the addresses from the original bios.
I don't want to screw up anything as the network and firewire are working fine it's just that error message that bugs me. I do aparently have the option with the uber bios to change the Machine MAC(NV) address. Could i just change that address there and having a different could get rid of the flag in the device manager?
Facebook
Twitter