> Now, my users are reporting that the boot disk no longer works on
> machines which have Intel gigabit (PRO/1000) networking hardware.
Problem:
Intel PRO1000 network driver E1000.DOS does
Int21/IoControl XYZ
--> driver
--> Int21/GetVect, Setvect
this will reuse the same DOS stack and crash immediately.
this issue might be also closed by making GetVect/SetVect true reintrant,
but it's a good idea to protect the stack anyway.
[entry.asm, 286]
; call number. Finally, all others run on the disk stack.
; They are evaluated in that order.
+ cmp byte [_InDOS],0
+ jne int21_onerrorstack
cmp byte [_ErrorMode],0
je int21_2
int21_onerrorstack:
mov cx,_error_tos
********
better solution would protect the both stacks individually.
left as exercise to the reader
> Or you can download my boot disk itself as a 1.44M floppy image:
> http://unattended.sourceforge.net/testing/ e1000.img
one floppy for each adapter - how boring ;)
see http://www.nu2.nu/bootdisk/network how this should be done.
http://www.drivesnapshot.de/en/makebootdisk.htm is another example ;)
tom
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Freedos-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
