Hallo, Arthur!
AM>>You need to rename your sys:system\autoexec.ncf to
AM>>something like sys:system\autoexe2.ncf, then create a
AM>>c:\server.312\autoexec.ncf.
WS>> [...]
WS>> Works fine. But this whole stuff is obsolete with the LOADER
WS>> patch inside  311PTG.EXE.
AM>Oh right, but we're still using the above with good results on a very
AM>up-to-date with patches NW 3.12 machine.
I won't argue about that. In fact I'm a little bit sorry about the loader  
patch. This workaround with C:\SERVER.312\AUTOEXEC.NCF was always good to  
impress costumers, even for most CNEs I met. No wonder: The study guides  
for NetWare 3.x don't explain it.
Just two remarks:
I wouldn't rename SYS:SYSTEM\AUTOEXEC.NCF. It works fine  (just delete the  
lines including the server name and IPX internal network number) and  
software installation routines will find autoexec.ncf to change everything  
inside for their needs (ArcServe, LANDesk etc.). Otherwise the routines  
will create a new Autoexec.ncf ...
The loader patch will fix the YEAR2000-problem for NetWare.
Ciao
Walter
--- CrossPoint v3.11 R
---------------