Posted: Tue Mar 16, 2004 3:02 pm
Hi
IMHO inserting the code at the beginning of the BIOS routines is a bit risky.
You never know, if there are parts of the Bios, which do not like being speeded up or cached (We've seen M$ and Borland getting probs with faster CPUs).
I would put it at the very end, just before booting.
This place could be a bit harder to find. Some Bioses are stored compressed and get decompressed by a tiny loader module at start and executet from memory.
You may think about this as well:
Why not putting it into any adapter rom?
ISA-Nics are pretty cheap and do usually provide a socket for a Bootrom.
IIRC The Adapter scan is done rather late, so most of the Bios has already been executet. An adapter Bios contains a few special Bytes at start, a checksum (IIRC) and then your code. There should be a description to be found on the net somewhere.
Best: If you have any problems, just remove the nic and you are back to normal.
Bye
Thomas
IMHO inserting the code at the beginning of the BIOS routines is a bit risky.
You never know, if there are parts of the Bios, which do not like being speeded up or cached (We've seen M$ and Borland getting probs with faster CPUs).
I would put it at the very end, just before booting.
This place could be a bit harder to find. Some Bioses are stored compressed and get decompressed by a tiny loader module at start and executet from memory.
You may think about this as well:
Why not putting it into any adapter rom?
ISA-Nics are pretty cheap and do usually provide a socket for a Bootrom.
IIRC The Adapter scan is done rather late, so most of the Bios has already been executet. An adapter Bios contains a few special Bytes at start, a checksum (IIRC) and then your code. There should be a description to be found on the net somewhere.
Best: If you have any problems, just remove the nic and you are back to normal.
Bye
Thomas