Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!phad.hsc.usc.edu!kmartin From: kmartin@phad.hsc.usc.edu (Kenneth J. Martin) Newsgroups: comp.sys.novell Subject: Re: (none) Message-ID: <29517@usc> Date: 22 Jan 91 23:52:56 GMT References: <1991Jan17.201641.15736@bronze.ucs.indiana.edu> Sender: news@usc Organization: University of Southern California, Los Angeles, CA Lines: 55 Nntp-Posting-Host: phad.hsc.usc.edu In article <1991Jan17.201641.15736@bronze.ucs.indiana.edu> mckimg@bronze.ucs.indiana.edu (Geoffrey McKim) writes: >Has anybody else had a similar problem to what we are having? > >A preliminary conclusion that I have reached is that the Macintosh >Printing VAP's released with MacVAP's 2.0 do not work properly with the >new "3C505 with AT/1 (v4.11)" driver distributed on the LAN_DRV_180 with MacVAP's >2.0. > >We have had: > > 1. no problems running the 4.11 3C505 driver with the file service > VAP's only. > 2. no problems running the old "3C505 (Assy 2012) with Appletalk" > driver with full MacVAP 2.0 print and file services > >The symptom is that the server merely hangs -- no ABEND, no chance to go >into the Novell debugger, etc. A simple unrecoverable hang. I have also >tried this with several machines (although all of the same type). The >hardware we are using is: > > Empac 386 > Adaptech SCSI controller > 3C505 (2012) Ethernet board > >If anyone else has seen symptoms similar to this, I would be greatly >appreciative in hearing about it. Hey yeh, we had a similar problem. We have: Unipac 386 Future Domain SCSI controller 3c505 (2012) Ethernet card Our problem was this: The 4.11 lan drivers/appletalk with the full mac vap installed, would hang durring boot after the "Novell cold boot loader" was displayed. The old 3.21 (I think that's the version) lan drivers/appletalk worked fine with the full mac vap installed. So we went with the old drivers. Since then, we have updated our Future Domain SCSI drivers, and then both the old and new versions of the lan drivers would hang durring boot. A call to Future Domain suggusted changing our bus speed to 8MHz (we were running at 10MHz). That seemed to fix it for the old lan driver, but I haven't had the chance or desire to try it with the new 4.11 driver. If it works, don't fix it. Oh, by the way, this was with macvap 2.0 and SFT 2.15c -- Kenneth J. Martin | Norris Medical Library Lan Administrator | University of Southern California Internet: kmartin@phad.hsc.usc.edu | 2003 Zonal Ave. Compu$erv: 72557,3157 | Los Angeles,CA 90033