Being a newcomer to ADSM-L, could I trouble someone for a pointer to any FAQ
that's been developed?  Thanks in advance.

If the following are answered in the FAQ, please ignore; otherwise, I wonder
if anyone can shed some light or at least provide a "me too" with respect
to the following difficulties I've had with the ADSM 1.2.0 clients:

        - Windows client, Win3.1 over DOS 6, using FTP Software's
PC/TCP to provide WINSOCK.DLL, (i.e. using TCP/IP for comms) running
on Compaq 486's on a NW3.12 network: while ADSM Backup client works
fine, ADSM Scheduler client more often than not, on receiving the
correct node password and receiving scheduling info from the ADSM
server, abruptly drops out of Windows altogether.  Sometimes to a
"black screen of death"; sometimes to a DOS prompt and can start
Windows again; sometimes to a DOS prompt, but attempts to start
Windows again give a sharing violation on KRNL386.EXE.

        - NetWare Client, NW3.12, using TCPIP.NLM for comms, running
on hardware varying from a Compaq Prosignia VS to a Tandy 4000
(bleaghhh): both "LOAD DSMC INC" and "LOAD DSMC SCHED" (when scheduled
backup runs) have a TCP/IP failure part way through the incremental
backup.  When "LOAD DSMC INC" is rerun immediately, client skips files
already backed up, picks up where it left off, gets a sunstantially
smaller subset of the data, TCP/IP failure again.  Repeated trials
seem to show the total amount of files/data approaching a horizontal
asymptote.  My pet theory is that the client is running out of memory
in which to manage the file list.

--
Glenn Forbes Larratt x5474   LAN Specialist, Rice U, Systems & LAN Management
Glenn Forbes Larratt x5474   LAN Specialist, Rice U, Systems & LAN Management
The Lab Ratt (not briggs :-) "Get over it!" -the Eagles, Hell Freezes Over '94
glratt AT rice DOT edu (Internet)   http://is.rice.edu/~glratt  /  GE/MU/T/O 
d?(++) p
Neil Talian?                 c+(++) l u+ e- m* s+/+ n@ h- f+ !g w+(+++) t+ r y+