🚀 go-pugleaf

maas@dutiws.twi.tudelft.nl (Frank Maas) writes:


>First of all, I know this is probably not the correct group for this question,
>but I really didn't find a group that suited the subject. And since it is
>about a MS-DOS driver...

comp.protocols.nfs or comp.protocols.tcp-ip.ibmpc

>Problem:
>	Currently I'm using a LAN which is connected to both an Unix server and
>	an OS/2 server. The first can be reached when I load PC-NFS on my 
>	machine. To reach the latter, I have to load NETBEUI (Lan Manager).
>	Since I have to access both servers (Unix for E-Mail, connections to the
>	world :-), etc; OS/2 for NOTES, Programs, etc), I have to reboot my
>	machine each time I want to do something on the other server. Concurrent
>	access is not possible.

Wrong. Both Lan Manager and PC-NFS can be installed over an NDIS (tm) Driver. 
In fact Lan Manager demands it. By combining the Protocol.INI files this
should be possible, Unfortunatly PC-NFS and Lan Manager do not get on (Sun
say they are looking into this). Alternativly PC/TCP will co-reside with
both versions of Lan Manager an provides better connectivity to the Unix
world.

>What I want:
>	A driver that implements both the NETBEUI and the PC-NFS layer. So,
>	NOTES (which has to use NETBEUI) sees NETBEUI, and telnet sees PC-NFS
>	(or TCP/IP to be correct).
>	MS Windows should see PC-NFS when MSW is set up for PC-NFS and it 
>	should see NETBEUI when it is set up for NETBEUI.

With PC/TCP you set up Windows to See NetBeui, The PC/TCP NFS drives are
just there and for applications like Telent Windows does not care. PC/TCP
also results in a reduced memory impact since you don't need the TSR's
RTM etc.  

>So the question(s):
>	Does such a driver exist?
	The Driver exists and you are using it (NDIS).
>	Did you have the same problem and solved it differently?
	For PC-NFS the problems are known and not solved, it works
	with other TCP/IP and NFS implementations for DOS.
>	Do you see other solutions?

	A TCP/IP stack that is intended to interoperate with other Network software.

>You can follow-up to this article, but if this is the wrong place, you could 
>also mail me.

>With Regards (and Best Whishes for '93),

>Frank Maas (e-mail: maas@dutiws.twi.tudelft.nl)

Steven Vincent				steven@unipalm.co.uk
(Note we sell both PC-NFS and PC/TCP).

maas@dutiws.twi.tudelft.nl (Frank Maas) writes:

>What I want:
>	A driver that implements both the NETBEUI and the PC-NFS layer. So,
>	NOTES (which has to use NETBEUI) sees NETBEUI, and telnet sees PC-NFS
>	(or TCP/IP to be correct).
>	MS Windows should see PC-NFS when MSW is set up for PC-NFS and it 
>	should see NETBEUI when it is set up for NETBEUI.

>So the question(s):
 We use NETBEUI and TCPIP protocols together with Microsoft's TCPIP
Utilities. The Utilities contain Telnet, FTP, RCP and RSH. With these
you can unload the protocol you do not use without booting the
PC. You can also choose to have both protocols loaded. Hope this helps.

All the best,
Kwame      kod@ktas.dk