--------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: E2N00010 Date: 02/17/97 From: DAVE HATCH Time: 07:59pm \/To: BEN (Read 3 times) Subj: 10baseT help On Feb 11 22:43 97, Ben of 1:246/53.2 wrote: B> *** Quoting Arthur Marsh to Ben dated 02-05-97 *** >> B> Why is there a MINIMUM cable lenth?..... i HAVE to have (If >> B> i were to use it) a 8 foot cable or more? >> >> Microdyne recommmend a minimum cable length for a 100Base-TX cross-over >> cable. B> Hehehehehhe.... Force you to spend more???? :))) Nope - applied physics. Speed of light propagation, and minimum settle time for the interface. Same for the old 10Base2. Minimum length of coax - only a meter, since it's not pushed anywhere near as hard as the new 100 stuff. Regards, Dave Hatch. --- Msgedsq 3.20 * Origin: DealBlue Pro Support (3:711/808) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: E2N00011 Date: 02/17/97 From: DAVE HATCH Time: 08:01pm \/To: ERIC TAM (Read 3 times) Subj: RPL Problem ET> Today, I try to setup a diskless workstation. I follow all the ET> instruction in the NW4.1 online documentation. At the end, I ET> reboot the diskless workstation and it pump up this error message. ET> RPL-ROM-ERR: 50 The board cannot be found. ET> Can someboby help. Yup. The Prom is trying to tell you that the configuration you've set on the interface card isn't the one (or range of) configuration it can use. You need the docs for the Prom, as related to the card. Odds on, there's a required configuration. (OTOH, it -could- be that the card's defective, and the port decoder has failed. Doubt it VERY much. Much more likely just misconfigured.) Regards, Dave Hatch. --- Msgedsq 3.20 * Origin: DealBlue Pro Support (3:711/808) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: E2N00012 Date: 02/17/97 From: DAVE HATCH Time: 08:08pm \/To: MICHAEL CALLERY (Read 3 times) Subj: Upgrade 3.11 to 3.12 - help/comments/? On Feb 12 21:21 97, Michael Callery of 1:396/17.37 wrote: MC> After having my 3.12 upgrade on the shelf for over a year I made the MC> decision to actually perform the upgrade. I've heard stories both pro MC> and con on this and I'm throwing my experience out here for comments MC> and/or help. The current word is that it's now pretty stable, and a reasonable way to go. (WHEN it's patched to the current level - not before. Get that patch kit and apply it. The latest I see in my Novlib inbound is 312ptA.exe - so it's at least up to that level.) MC> The server is an ALR Power Pro DX2/50 with 50 megs and a 4 gig MC> Microspolic SCSI connected to a SCSI card of who's name I cannot MC> remember. I have a second 1540 running my tape drive and my NIC is an MC> Eagle NC3200 ESDI. Sounds a reasonable mix. MC> The 3.12 upgrade appeared flawless and my system ran fine for four MC> days, as long as my user count didn't exceed about 10 or 12 people. MC> When that happened, communications to the server failed. MC> When I say failed, it simply stopped. NO error messages on the MC> console, no red leds on my hubs, no failed hubs, nada, nothing, zilch. MC> I tried looking at a variety of solutions, but ended up re-installing my MC> 3.11 software back on top of my 3.12 and the system ran fine the entire MC> day. Being a lazy man, well...:-) (BTW - patch level is NOT optional on 3.11. There are _deadly_ bugs in the unpatched issue. Either patch level D, or the current definitive set recommended. If it's D, _don't_ install it all holus bolus.) MC> I tend to think is was some updated driver that conflicted, but now MC> I have to ask the question if its even worth trying to debug all this. With the patch kit, you shouldn't have to. My latest 3.12 installations sit and run by the month, no problems. (Mind you, one of the 3.11's with patch level D judiciously fitted ran for as long as it's been since D first came out, without reboot or even looking at. :-) MC> I am certainly open to any comments and/or suggestions from those of MC> you that have gone through this, I'd certainly appreciate any/all MC> comments. There's a few. Regards, Dave Hatch. --- Msgedsq 3.20 * Origin: DealBlue Pro Support (3:711/808) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: E2N00013 Date: 02/18/97 From: ARTHUR MARSH Time: 06:17pm \/To: JEFF SMITH (Read 3 times) Subj: Re: SCSI bus hangs On Sun 16 Feb at 23:25 Jeff Smith (1:282/1031) wrote to Arthur Marsh: JS> I had a problem with SCSI resets here. It turned out JS> to be a SCSI HD overheating problem. We have a small, fast, household fan blowing air through where some cover plates used to be across the Quantum XP34300 HDD. The last SCSI bus reset happened when Discview was loading some CD-ROM indexes. --- msgedsq 2.1 * Origin: Camelot Swamp MJCNA, Hawthorndene, Sth Australia (3:800/812) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: E2N00014 Date: 02/18/97 From: ARTHUR MARSH Time: 06:20pm \/To: DAVID WROBEL (Read 3 times) Subj: Re: Scsi Bus Hangs On Sun 16 Feb at 00:02 David Wrobel (1:107/605@FIDONET) wrote to David Roper: DW> My discussion on this issue is the consequences of DW> making a "Bus Master" - the consequences of which are DW> different for which BUS it's implimented for. Right, that's one reason I was looking to use SCSI HBA's that used the same .DSK driver. --- msgedsq 2.1 * Origin: Camelot Swamp MJCNA, Hawthorndene, Sth Australia (3:800/812) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: E2N00015 Date: 02/18/97 From: ARTHUR MARSH Time: 09:28pm \/To: DAVE HATCH (Read 3 times) Subj: 10baseT help On Mon 17 Feb at 19:59 Dave Hatch (3:711/808@fidonet) wrote to Ben: >> Microdyne recommmend a minimum cable length for a >> 100Base-TX cross-over >> cable. B> Hehehehehhe.... Force you to spend more???? :))) DH> Nope - applied physics. Speed of light propagation, and DH> minimum settle time for the interface. DH> Same for the old 10Base2. Minimum length of coax - only a DH> meter, since it's not pushed anywhere near as hard as the DH> new 100 stuff. ...and people claim that physics is irrelevant. I had some interesting discussion with our friend Mr Nitzsche about what WAN connectors to use for MPR - the modulation and clocking scheme used become useful considerations when running at 2 Mbit/s serial or with long cables. EIA-530 or G.703 are probably most appropriate for 2 Mbit/s operation, depending on what is supported by the WAN card and NTU. --- msgedsq 2.1 * Origin: Camelot Swamp MJCNA, Hawthorndene, Sth Australia (3:800/812) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: E2N00016 Date: 02/17/97 From: RICHARD JARY Time: 08:18pm \/To: SALVADOR ASTURIAS (Read 3 times) Subj: Netware v3.11 server TIME prob SA> Anyway, thanks again. By the way, it's set time. I tried SET SA> DATE, and it doesn't do anything. At least, not for v3.11. Short term memory loss at this end :-) I'll have to up the refresh rate! Richard --- Msgedsq 3.20 * Origin: Internet: jary@sydney.DIALix.com.au (3:711/445) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: E2N00017 Date: 02/16/97 From: MARTIN ROODENBURG Time: 12:08pm \/To: MIKE MORAIS (Read 3 times) Subj: Licenses? Hello Mike, > I've been reading my CNE Study Guide, and I've come across a > problem. The book states that included with the Netware package > is a License disk. For each server installed, you must provide a > valid license as provided on the disk, but you can only use a single > license disk on a single server - you can't use the same license > disk twice in the same network. My question is, how do you go about > installing other licenses when you want to install multiple servers > on a network (assuming you only have a single License disk)? If you only have 1 License disk, you can only use one server on one network, not more. If you want to experiment, you could setup a server without license disk (you will get a '1-user' installation) besides a normally licensed server. Using multiple servers on the same network requires multiple license, simple as that. Bye, Martin. --- * Origin: It's hard to make original origins, so I don't (2:285/101.12) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: E2N00018 Date: 02/18/97 From: GUY DESAUTELS Time: 03:09am \/To: ALL (Read 3 times) Subj: Chat on Novell 3.12??? We have Novell 3.12 and Windows 3.1 at our school; I know there is a chat program for WFWG and Lantastic. The question is whether there is a chat program/application for Novell 3.12?? Thanks --- ifmail v.2.8c * Origin: SMVS (2:281/10@fidonet) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: E2N00019 Date: 02/17/97 From: MARK SILER Time: 09:06pm \/To: ALL (Read 3 times) Subj: 3 DOS computers, 1 Printer & a Novell Ne21:06:3502/17/97 I need to know how to share a printer between 3 DOS computers. They are on the companies network (Netware 3.12). What's the best way of doing this? Please send replies to siler@atlantic.net Thanks! --- ifmail v.2.8c * Origin: Internet Connect Company +1(352)375-2912, USA (2:281/10@fidonet)