--------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: ECG00011 Date: 08/11/97 From: CHARLES RING Time: 12:26pm \/To: MIKE BILOW (Read 3 times) Subj: RG58 ? MB> Charles Ring wrote in a message to Mike Bilow: CM>>> RG58A/U is recommended.. RG58 is not quite up to spec. MB>> In fact, the "A" indicates the type of jacket insulation, which MB>> is irrelevant for Ethernet use unless you are burying the MB>> cable underground. These old military designators were actually MB>> formally dropped over 30 years ago, but the terms have survived MB>> by custom. Higher quality manufacturers such as Belden usually MB>> just use their own numbering system. CR>> The "A" mainly indicates a stranded center conductor - much CR>> more survivable if there's even slight flexing. MB> That's not what it says in my copy of "Reference Data for Radio MB> Engineers." Military RG-58 -- these designations were all part of the MB> old Joint Army-Navy ("JAN") system in the U.S. -- had 19 strands MB> making up the center conductor. Most network coax uses a solid center MB> conductor because it is easier to affix the connectors using crimp MB> methods. You must solder the connectors onto stranded coax, and most MB> network technicians these days would have no clue how to solder MB> something. The technique is not simple, and the military published a MB> little manual explaining in detail how to solder connectors onto coax. I come from the other side: I've used various kinds of coax far longer than I've had anything to do with computers, and always use solder connectors. When I think of RG-58, I have Belden 8240 (solid) in mind, and with RG-58A it's Belden 8259 (stranded). I normally use 8259 for Ethernet and have no problems unless I mess up the soldering (the easiest mistake is to position the center conductor wrong). With large radio transmitters on site I can't get away with using lousy coax. --- * Origin: W3NU Online Sharon, PA (412) 346-5535 (1:2601/100) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: ECG00012 Date: 08/11/97 From: DAVE BARRON Time: 12:18am \/To: KRIS O'SHEA (Read 3 times) Subj: RG58 ? Hi Kris, KO>What are the limits of it's rangr, then. I am not going to use it for very KO>long distances, just from one room to another. Depends on your ethernet boards and RG58 usually has a /U (or whatever) suffix which indicates it's attenuation at given frequencies. Anyway, you can happily run all over your house without problem. :-) Dave --- ViaMAIL!/WC4 v1.30 * Origin: Ooh! MultiLine BBS, London. 0181-395-3108 (2:254/233) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: ECG00013 Date: 08/09/97 From: HERBERT GRAF Time: 07:42pm \/To: EVO (Read 3 times) Subj: Email on a LAN -=> Quoting Evo to Simon Huggins <=- Ev> @TID: FastEcho 1.45 19100 Ev> @NOTE: IceEdit 2.35 [Eval] [77] Ev> @REPLY: 1:342/1017.0 33dfe2aa Ev> @MSGID: 2:250/210.45 59839392 Ev> @PID: RA 2.5 1161 Boo! > I've got win95 on all three machines and at the moment they each pick > up their own mail separately at different times of the day. It seems a > bit wasteful so I want to automate it as above. > Is this possible using the Microsoft Mail postoffice thing? How do I > set it up? Ev> Well, you can use 'the postoffice thing' to setup each user, but I Ev> doubt this will solve your problem because when a user attempts to Ev> collect mail, it doesnt collect everyone else's mail as well. Ev> You need to get a copy of Microsoft Exchange Server (reg WinNT 4 Svr Ev> tho) or I know Pegasus Mail can check multiple PoPs at once - netscape Ev> Communicator 4 might as well but not sure. If you was to use Pegasus Ev> or Communicator you would have to set up the folder which stores the Ev> mail in as a shared folder so all computers have access to it and also Ev> setup the location to the folders. IE4.0 preview 2 has multiple POP account capabilities. TTYL ___ Blue Wave/386 v2.30 --- Platinum Xpress/Win/Wildcat5! v2.0 * Origin: Bits & Bytes BBS - Toronto, Ont. 416- 532-1784 1:25 (1:250/350) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: ECG00014 Date: 08/11/97 From: HERBERT GRAF Time: 04:54pm \/To: GREG MACLELLAN (Read 3 times) Subj: private subnet ip? -=> Quoting Greg Maclellan to All <=- GM> @MSGID: 1:249/174.0 33ee17d8 GM> what's the subnet that's reserved for private nets? 192.68.* ? i GM> forget. I *THINK* its 192.168.61, I might be wrong though, anyways that's what I use on my net and it works. TTYL ___ Blue Wave/386 v2.30 --- Platinum Xpress/Win/Wildcat5! v2.0 * Origin: The Horizon Bulletin Board 905-855-7934 (1:250/348) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: ECG00015 Date: 08/12/97 From: MIKE BILOW Time: 07:47am \/To: IAN MOOTE (Read 3 times) Subj: Jumpers on Network Adapt Ian Moote wrote in a message to Mike Bilow: MB> length in hundreds of meters. Therefore, 10Base-5 (Thick Ethernet) MB> can go up to 500 meters, while 10Base-2 (Thin Ethernet) can go up to MB> 200 meters. IM> I didn't know that. How does that work for 10baseT? I've always wondered that myself. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: ECG00016 Date: 08/12/97 From: MIKE BILOW Time: 07:47am \/To: MICHAEL FOX (Read 3 times) Subj: throughput Michael Fox wrote in a message to Mike Bilow: MB> Ethernet is inherently half-duplex. MF> Oh well I did say, I could be wrong... though something comes MF> to mind. MF> Our 100mbps cards at work are running full duplex to the hubs MF> as when they are at half duplex transfers are too slow for the MF> high speed lan segment they sit on. Unless you use a switching hub, an Ethernet concentrator simply repeats whatever electrical signal is on any input to all outputs. Although UTP Ethernet cards have a transmit pair and a receive pair, any transmitter will see its own data coming back in real time on the receive pair. It is more common to see switching hubs on 100 Mbps than on 10 Mbps, but it is still awfully expensive. If you need the speed, then you pay the money. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: ECG00017 Date: 08/12/97 From: MIKE BILOW Time: 09:54pm \/To: CHARLES RING (Read 3 times) Subj: RG58 ? Charles Ring wrote in a message to Mike Bilow: MB> That's not what it says in my copy of "Reference Data for Radio MB> Engineers." Military RG-58 -- these designations were all part of the MB> old Joint Army-Navy ("JAN") system in the U.S. -- had 19 strands MB> making up the center conductor. Most network coax uses a solid center MB> conductor because it is easier to affix the connectors using crimp MB> methods. You must solder the connectors onto stranded coax, and most MB> network technicians these days would have no clue how to solder MB> something. The technique is not simple, and the military published a MB> little manual explaining in detail how to solder connectors onto coax. CR> I come from the other side: I've used various kinds of coax CR> far longer than I've had anything to do with computers, and CR> always use solder connectors. When I think of RG-58, I have CR> Belden 8240 (solid) in mind, and with RG-58A it's Belden CR> 8259 (stranded). I normally use 8259 for Ethernet and have CR> no problems unless I mess up the soldering (the easiest CR> mistake is to position the center conductor wrong). I was actually called in by a friend of mine to solder two BNC connectors onto a very long run that was going across the street. I showed up with a Weller temperture controlled iron and 63/37 paste-free solder. The connectors went on in about 10 minutes, and he was amazed, saying "We worked on this for days!" CR> With large radio transmitters on site I can't get away with CR> using lousy coax. Actually, I would consider fiber. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: ECH00000 Date: 08/10/97 From: LEE ARONER Time: 03:06pm \/To: MIKE BILOW (Read 3 times) Subj: Transfer stops occasional MB> Jarkko Laiho wrote in a message to All: JL> I'm having problems with my two-card network (both are SMC JL> 8003EP:s). While testing file transfers, it goes well for a MB> Are you by any chance hanging either card on IRQ 7? If so, change it. Is that because of the default LPT1 assignment to that IRQ? LRA -- SPEED 2.00 #2720: You know you're dieting when postage stamps taste good. --- Platinum Xpress/Win/Wildcat5! v2.0 * Origin: Grey Matter * Seattle, WA * 1:343/210 * (206) 528-1941 (1:343/210) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: ECH00001 Date: 08/10/97 From: LEE ARONER Time: 03:11pm \/To: MIKE BILOW (Read 3 times) Subj: Transfer stops occasional MB> Jarkko Laiho wrote in a message to Mike Bilow: >> The cards are 8-bit, 8kb RAM buffer size. The software >> should be okay (lsl, smc8000 and ipxodi), the net.cfg is >> similar in both machines too (except for the interrupt, >> which is... different :)). > Are you by any chance hanging either card on IRQ 7? If so, > change it. JL> No... but what makes IRQ 7 that special? MB> Two things. First, it is often assumed to be owned by LPT1 even if it is not. > Second, it is the dumping ground for transients on other IRQ lines which are > shorter than the rated recognition time, so IRQ 7 will frequently be signalled > to software if some card on another IRQ is defective. Wow! What an interesting tidbit. Explains a lot of odd little things over the years....Is this the default behaviour of the PIC? LRA -- SPEED 2.00 #2720: I don't want it now, I want it RIGHT now! --- Platinum Xpress/Win/Wildcat5! v2.0 * Origin: Grey Matter * Seattle, WA * 1:343/210 * (206) 528-1941 (1:343/210) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: ECH00002 Date: 08/08/97 From: RICHARD TOWN Time: 08:32am \/To: MIKE BILOW (Read 3 times) Subj: Peer-Peer Network Suggestions. -=> Quoting Mike Bilow to Dean Hamstead <=- MB> Windows 3.11 and Windows for Workgroups 3.11 are completely different. There was a Windows for Workgroups 3.1 too MB> Windows 3.11 is quite common. It came with a lot of new machines, and MB> was available as a free upgrade to Windows 3.10 from Microsoft. WW0981.EXE [05] Microsoft(R) WW0981: WINDOWS(TM) REFRESH FILES to update Win3.1 to Win3.11 Revision Date: 2/94 Available for FReq or d/load from origin rgdZ Richard --- FMail/386 1.02 * Origin: Another message via PackLink +44(0)1812972486 (2:254/235)