Text 56, 80 rader
Skriven 2005-01-24 10:27:05 av da Silva, Joe (1:2320/105.999)
Ärende: RE: protman.dos and DR DOS
==================================
From: "da Silva, Joe" <Joe.daSilva@ampymetering.com.au>

I seem to recall some beta packet drivers for Intel ethernet cards
at Crynwyr (not in the main packet driver collection, one of the
"stand alone" packages).

As for M$ NDIS stuff, we use MS Client here with DR-DOS 7.02+.
Yes, it is a memory hog, and periodically steals a few milliseconds
of CPU time (which can affect polled I/O with some applications),
but other than that, works fairly well in Basic mode. In Full mode,
it is an even worse memory hog, is certainly less stable, and from
memory (no pun intended), corrupts some of the interrupt vectors.

At Simtel, I seem to recall some SMB/NDIS network client shareware
from some Irish company circa 1998, although I've never tried it, so
I can't say if it works, etc. I find Simtel impossible to navigate these
days (no browse capability, last time I checked), so I don't bother
with it any more (a shame really, they used to be the first place I'd
go to to search for software).

Joe.

PS. A couple more little tidbits about my PNW experimentation :

I found an older NE2000.COM (IIRC, version 1.54, circa 1993) in
a Novell archive called "dosup9a.exe". This doesn't have the bugs
I reported for the 1996 (2.10) version. It also uses 1K less memory.

Of the various components used in PNW, only the server component
seems to make use of DPMS, so if you aren't using DPMS with
any other driver/TSR, don't bother loading it for a client-only boot.

> -----Original Message-----
> From:	Veit Kannegieser [SMTP:vk@Informatik.TU-Cottbus.DE]
> Sent:	Sunday, January 23, 2005 7:45 AM
> To:	opendos-list
> Subject:	protman.dos and DR DOS
> 
> I remember there was a conflict (including court..) that
> protman.dos does bad things to memory when running onb DR DOS.
> On my new notebook, it causes a hang. 
> Does anyone have an idea, workaround, alternative to using NDIS?
> Network Chip is an Intel Gigabit chip. 
> Intel does not seem to provide packet drivers for it,
> only NDIS and ODI drivers. Tried e1000odi.com+odipkt.com, 
> but no success so far. 
> 
> Goal is to have either IBM DOS Lan Services
> (\CID\SERVER\IBMLS\IBM500D1..4\) or NCSA telnet, arachne, ...
> (packet driver) running.
> 
> -- 
> Veit Kannegieser



-------------------------------------------------------------------------------------------------------

This email (including any attachment) is confidential. If you are not the
intended recipient,
you must not disclose or use this email or the information contained herein for
any purpose.
If you have received this email in error, please immediately advise us by reply
and delete this email.
This email may not be altered, forwarded or re-issued without our consent. AMPY
Email Metering is
not responsible for any changes made to this email or the effect of any changes
on the email’s meaning.
It is the responsibility of the recipient to scan this email for viruses and
faults prior to processing.
AMPY Email Metering shall not be liable for any loss or damage caused by this
email from transmission,
viruses, faults or the use of data accompanying this message. AMPY Email
Metering reserves all its
rights, including copyright,in this email.



--- Internet Rex 2.29
 * Origin: The gateway at Capitol City Online (1:2320/105.999)