It sounds like you guys managed to figure this out (thanks, Tom!).
Can I get a copy of a new kernel to try? When/where?
Thanks!
- Pat
P.S. http://freedos.sourceforge.net/kernel/README.html is
inaccessible.
---
This SF.Net email is
Bart,
Int21/IoControl XYZ
-- driver
-- Int21/GetVect, Setvect
the problem with this is that int28 handlers will now end up on the error
stack instead of the disk api stack. So if an int28-TSR such as THELP
causes a critical error, the critical error will end up on its own
On Sat, 1 May 2004, tom ehlert wrote:
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
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
Johnson Lam schreef:
I got the same problem when trying MSCLIENT, it does work under
FDXXMS+UMBPCI (try it), but fail with HIMEM+EMM386. I'm quite sure the
memory manager and hardware not so compatible especially Network
Interface Card.
try HIMEM + UMBPCI (there's even a 3.57beta7 version at the
Hello Johnson,
JL I got the same problem when trying MSCLIENT, it does work under
JL FDXXMS+UMBPCI (try it), but fail with HIMEM+EMM386. I'm quite sure the
JL memory manager and hardware not so compatible especially Network
JL Interface Card.
Freedos EMM386 doesn't support VDS yet, and NET.EXE
Erwin Veermans [EMAIL PROTECTED] writes:
Wild guess:
Did you try switches=/E in config.sys?
Some people were reporting issues with latest kernel that
could be reverted with the /E-switch. Browse this list
for more info ...
No effect. Also, this happens with both the 2.0.33 and 2.0.34
On Mon, 26 Apr 2004 09:27:31 +0200, you wrote:
Hello Tom,
try
LH /L: NET INIT
to force loading of network driver into low memory.
Thank you Tom, now the MSCLIENT work, you are really a genius :-)
Rgds,
Johnson.
---
This SF.net email is
Michael Devore [EMAIL PROTECTED] writes:
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
On 25 Apr 2004 18:10:17 -0400, you wrote:
Hi Patrick,
With FreeDOS (ke2034_32), it crashes as I described: The driver loads,
but when tinyrfc.exe tries to obtain a DHCP lease, it gets an invalid
opcode.
You report faster than me.
I got the same problem when trying MSCLIENT, it does work under
10 matches
Mail list logo
