🚀 go-pugleaf

In article <1991Oct8.132924.17344@news.cs.indiana.edu> mikes@iuvax.cs.indiana.edu (Michael Squires) writes:
>Has anyone successfully connected to a Novell network from ODT-DOS (DOS Merge)
>using the ability of DOS Merge to access a card?  I've been able to get
>ODT-DOS to attach to a server using a 3C501 and the Clarkson packet driver
>interface but the login directory does not appear as expected.  I've tried
>to use a WD8003E which does not use DMA (following the excellent posting
>on this subject recently) but that has not worked at all, probably have
>one or more of the parameters wrong.  I understand that there is also a
>third party solution.
>-- 
>
>Mike Squires (mikes@iuvax.cs.indiana.edu)     812 855 3974 (w) 812 333 6564 (h)
>mikes@iuvax.cs.indiana.edu          546 N Park Ridge Rd., Bloomington, IN 47408

I have not heard of someone actually doing this.
You can reduce the possible problems by first setting up a bootable
DOS floppy with all the needed drivers, etc, so that the Novell
access works when you boot the entire machine from the floppy.
This step is critical, because you first have to know that you
have configured everything correctly.  Then, once this works,
reboot Unix, and then try booting the floppy under Merge, with all
the needed device attachments.  E.g.:  "dos -l +anovell"
If at this point it does not work anymore, then you can investigate
possible problems with your "novell" device attachment specification
in /etc/dosdev.  Make sure that no Unix driver is trying to use the
device also.  If you can get it to work in this way, the next step
is to try to get it to work when starting a normal DOS session, by
putting the right stuff in your config.sys and autoexec.bat files.
I don't know how Novell does it's stuff, but there could be conflicts
with Merge's method of providing access to the Unix filesystem and
Novell's method of providing file service.

Let us know if you get it working.  Good Luck!
--------------------------------------------------------------------- 
David Peet
peet@locus.COM                                                     
Locus Computing Corporation, Los Angeles                               
---------------------------------------------------------------------
Disclaimer: Normally my statements are my own, and not do not
necessarily reflect those of Locus, but maybe this time they do,
but then again, maybe not.
---------------------------------------------------------------------