[prev in list] [next in list] [prev in thread] [next in thread] 

List:       adsm-l
Subject:    PC-NFS unusable
From:       "Pete Tanenhaus, ADSM Client Development" <pt () VNET ! IBM ! COM>
Date:       1995-08-30 13:30:47
[Download RAW message or body]

The DOS client won't work because it requires a particular stacks realmode
socket library to be statically linked in, and we we currently only support
IBM TCP/IP and FTP Software TCP/IP stacks.
 
The Windows client dynamically loads the socket library from a DLL (Winsock),
so in theory any stack which implements Winsock should work, but past
experiences have indicated that many stacks require special customization/
configuration of Windows/DOS or the stack itself in order to work correctly.
 
We have not tested PC/NFS so I can't comment as to what type of special
configuration may be required for that particular stack.
 
Pete Tanenhaus
ADSM Development
----------------------------Original message----------------------------
Subject:      PC-NFS not usable?
 
>> Most of our ADSM users use PC/TCP but one of our users has PC-NFS as
>> IP-driver. He can do FTP to our server machine (VM), but the
>> ADSM Windows client and DOS client do not work with PC-NFS.
>> The windows client says 'connecting to server' and remains in that
>> situation forever. The DOS client says 'PC/TCP resident module
>> is not loaded; aborting program...'.
>>  re can I find the 'legal' IP-drivers for the DOS and Windows clients
>> annot find anything in de User's Guides and in the README file
>> the DOS client I only read something about PC/TCP and IBM TCP/IP.
[prev in list] [next in list] [prev in thread] [next in thread]