From: weber@rhrk.uni-kl.de (Christoph Weber-Fahr [KIT])
Subject: Re: Novell CD-NET ODI problems
Organization: University of Kaiserslautern, Germany
Date: Mon, 7 Sep 1992 18:21:18 GMT

Hello,

Michael Schaarwaechter <MISC@ZB.UB.UNI-DORTMUND.DE> writes:

>We have several problems using ODI drivers with Meridian Data CD_NET.
>If anyone can help me.......

The chances are better, if you try it in bit.listserv.novell
(=NOVELL@SUVM mailing list) or comp.sys.novell. 
Anyway...

>First our Workstation (AST and Tandon) configuration:

>DOS 5.0,
>HIMEM, EMM386, SMARTDRV.EXE all newest versions shipped with
>Windows 3.1.
>LSL,    Ver 1.21,   7662 Bytes, 10.3.92
>(special card driver, different network cards)
>IPXODI, Ver. 1.2,  20903 Bytes, 10.3.92
>NETX,   Ver. 3.26, 52443 Bytes, 10.3.92

>Older EMM386, SMARTDRV.SYS, IPXODI, NETX show the same problems.

>NET.CFG is available and loaded.

What does it contain ?

>We have two fileservers running Novell 3.11.

>Following the problem(s):

>1.) The keyboardrate resets to boot-default when a SEND msg arrives
>With this NETXversion the beep while SENDs arrive occurs TWO times (one
>high, one low).

Novell delivers an appropriate patch for netx. Apply it. If you don't have
it, look into the dosup5.zip at ftp.uni-kl.de, pub/pc/novell.

>2.) Sometimes (not repeatable) the DOS DIR command fails until the next
>boot. This happens only on Networkdrives. All other commands are ok,
>programs will be executed normally. On local floppydrives sometimes the
>first access fails, the second try works.

No Idea. Are you sure, that you have file-scan rights granted ? Also try
the show-dots parameter in the net.cfg.

>3.) Clipperapplications return sometimes "Not enough memory" (with about
>600 kB free). SET CLIPPER=E000 has no effect.

Maybe the want to swap ? Does it depend on who runs them ? 
Its quite hard to create temp-files, if you have R F rights only :-)

>4.) Some workstations doesn't show the second problem but boot from
>time to time (aargh!).

That looks like memory conflict.
Check you memory setup. Carefully exclude all areas by proper emmexclude
statements (in Windows system.ini) resp. x= arguments in device=emm386.sys
line in config.sys.

>5.) In out network integrated are three CD-servers running Meridian Data
>CD-NET Ver. 4.3 / 4.2 (IPX peer to peer). The drivers can be loaded and
>unloaded on stations running IPX (linked) and NETX. On stations running ODI
>drivers the first try works, loading the drivers a second time will hang
>the PC when trying to run MSCDEX.

Sorry, I can just guess here - I've never used that Meridian software.
Are you sure that it hangs? Just let it run for, say, 10 minutes. Maybe some 
excessive timeouts occur...

Check carefully the Meridian installation stuff. Maybe you need more buffer-
memory or more spx-connections etc..

>The Drivers are:
>NWDRIVER (Meridian Data IPX Driver for connection to CD-servers)
>LOAD_EX (Meridian Data), which starts MSCDEX removable.

>All this appears ONLY on workstations with ODI drivers. The same
>workstations worked fine with "normal" IPX before.
>Why ODI?
>First: To use our new IP-Router
>Second: To use Windows 3.1 without new-linking the IPX.

Third: because Novell's support of the linked stuff will be abandoned

Regards

Christoph Weber-Fahr

-- 
  Christoph Weber-Fahr                  |  E-Mail:  weber@rhrk.uni-kl.de 
  Universitaet Kaiserslautern,  KIT     |  S-Mail:  Postfach 3049
  Tel. 0631/205-3391                    |           D-6750 Kaiserslautern
--------------------------  My personal opinion only    ---------------------
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU