At 01:37 PM 4/25/2004 -0400, you wrote: >In the last major release of my project >(http://unattended.sourceforge.net/), I changed my network boot disk >to use FreeDOS instead of MS-DOS. > >Now, my users are reporting that the boot disk no longer works on >machines which have Intel gigabit (PRO/1000) networking hardware. > >I have one machine with such hardware, and I can confirm that Intel's >DOS network driver (e1000.dos) appears to be incompatible with >FreeDOS. You can download the latest version of this driver from >Intel's site: > > http://downloadfinder.intel.com/scripts-df/File_Filter.asp?FileName=PRODOS2.EXE > >Or you can download my boot disk itself as a 1.44M floppy image: > > http://unattended.sourceforge.net/testing/ e1000.img > >Although the problem is only reproducible if you have PRO/1000 network >hardware... > >Here is what I have observed. > >If I use a config.sys which is empty except for >"DEVICE=\net\ifshlp.sys", the driver loads fine. But when the boot >disk tries to use the driver to obtain a DHCP lease, it gets an >illegal opcode followed by a reboot. The reboot happens too quickly >for me to record the hex values.
Since you're failing without HIMEM or EMM386 loaded, you have to be hitting a kernel compatibility, agreed? It can't be a UMB conflict or a p-mode conflict or something failing in EMS/XMS/VCPI/DPMI calls. That actually narrows the field of suspects quite a lot. Just to be sure, you've tried the bare driver CONFIG.SYS on an MS-DOS system and it worked correctly? The info is a required data point in case the driver normally requires or expects HIMEM, etc. I don't do kernel work, but depending on how much you want to dig in the guts of the problem, you might want to grab the 386SWAT debugger and load it immediately after the driver, with nothing else. It should catch the exception and throw you into the 386SWAT debugger. I know you know assembly language pretty well, plus I can walk you through some basic tests there (obviously a suboptimal situation, but better than nothing). I could test a card here, but since the FreeDOS machine isn't normally hooked into any network, I'm not sure it would do much good. (Weird about about failing with EMM386 without NOEMS, though. But we can maybe fix that later.) ------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
