--------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E1P00000 Date: 01/19/97 From: ALEC HERRMANN Time: 09:16pm \/To: GERRY BRITTON (Read 0 times) Subj: peer to peer? Hello Gerry, Replying to a message of Gerry Britton to Alec Herrmann: GB> Alec, I've installed NE2000's on a Pentium 166 and an older GB> 486DX2-66. I've managed to get the cards recognized by Warp 4. GB> What do I do next to get peer-to-peer actually working? What stage are you at now? Do you have cabling installed? Have you completed installation of the networking software on both machines? What is the domain name that you chose for both machines? What are the workstation names you chose for both? What userid and password have you initially specified? Did you install Netbios support, TCP/IP support, or both? (Note - to get things working, it is simplest to use Netbios only in the ginning). Do both workstations start successfully? If you share (using the Connections -> Network -> Network Services -> Shared Resources and Network Connections -> Properties -> Shares Tab) one of your local drives, does it show up on the other machines Connections Tab (in the same folder location)? Regards, Alec --- FleetStreet 1.12 NR * Origin: The Nibble's Roost, Richmond BC 604-540-8048 (1:153/8086) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E1P00001 Date: 01/18/97 From: NEIL CROFT Time: 07:21am \/To: JIM WARGULA (Read 0 times) Subj: Shiva dial-up client Hiya Jim, On 13-01-97, whilst lying in the gutter of the information super highway, I heard Jim Wargula whispering to Neil Croft about Re: Shiva dial-up client, NC>> Is there a Shiva dial-up client to allow my OS/2 box at home to dial NC>> into work's Shive? JW> Yes there is! You have to have the appropriate network stacks loaded. I know, we got a reply from Shiva in the compuserve forum at work. /| / neil.croft@pillarbox.coracle.com / |/eil =o) 2:250/410 @ fidonet http://osiris.sunderland.ac.uk/~ca5cru/fido/pillarbox.html --- * Origin: The Pillarbox BBS +44-1709-517224 (2:250/410) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E1P00002 Date: 01/20/97 From: GERRY BRITTON Time: 08:52am \/To: ALEC HERRMANN (Read 0 times) Subj: peer to peer? AH>Hello Gerry, AH>Replying to a message of Gerry Britton to Alec Herrmann: GB> Alec, I've installed NE2000's on a Pentium 166 and an older GB> 486DX2-66. I've managed to get the cards recognized by Warp 4. GB> What do I do next to get peer-to-peer actually working? AH>What stage are you at now? Do you have cabling AH>installed? Done. AH> Have you completed installation of the AH>networking software on both machines? What is the Done. AH>domain name that you chose for both machines? What are AH>the workstation names you chose for both? What userid Simple names. "dad's machine" & "Pat's machine". AH>and password have you initially specified? Did you Also simple logon's & P-words. AH>install Netbios support, TCP/IP support, or both? AH>(Note - to get things working, it is simplest to use AH>Netbios only in the beginning). So I found out. I didn't install TCPIP on the second machine, only on the first. I confess I dunno why that's even required, if the second machine will be able to access the Inet stuff on the first machine. AH>Do both workstations start successfully? Here's a little prob. The 486DX2-66 is having a problem with the NE2000. It sees the driver, RAM location & interrupt etc, but can't load the driver. The NIC's EPROM is currently set at 0320h and IRQ 15. I've gotten TRAP 05's at various addresses. I'll be shifting the card to different slots today to try & eliminate this, but it's intermittent. AH>If you share (using the Connections -> Network -> AH>Network Services -> Shared Resources and Network AH>Connections -> Properties -> Shares Tab) one of your AH>local drives, does it show up on the other machines AH>Connections Tab (in the same folder location)? No. I can't see anything but this workstation. ___ * MR/2 2.26 NR * E-mail to gbritton@siwash.bc.ca --- Maximus 2.01wb * Origin: Basic'ly Computers: Mooo-ing Right Along. (1:153/9) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E1Q00000 Date: 01/19/97 From: BOSTJAN JANEZIC Time: 01:58pm \/To: HENRY HARTLEY (Read 0 times) Subj: IBM Lan Server and Win95 (1:109/347) Pozdrav! HH> I run an IBM Lan Server 4.0 network with OS/2, DOS and DOS/Win HH> workstations. I would like to add Win95 workstations but am having HH> trouble getting the test machine to find the network. The machine HH> worked fine in DOS and the NIC seems to be working fine. Win95 loads HH> the driver for the card and for "Microsoft Networks" but when I go to HH> the "Network Neighborhood", nothing. On Win95 use command 'find' and type name of workstation or server. Botjan --- Blue Wave/Max v2.20 [NR] * Origin: IBM OS/2 BBS - SLOUG FidoNet backbone (2:380/106) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E1Q00001 Date: 01/19/97 From: STEPHEN BOWYER Time: 02:02pm \/To: HARRY OLDENHUIS (Read 0 times) Subj: Problem with TRAP 000D when installing N14:02:0001/19/97 [Trap 000d when trying to finish the installation of Warp 4.1 for OS/2....] HO> This is the net.cfg file Please note Int is used inplace of IRQ I've tried the settings from your net.cfg and config.sys.... They didn't really help.... HO> The best way it to make up a dos boot disk with novel on it start HO> the server, then boot os/2 machine from a floppy if novel runs from HO> the floppy you have half of the problems solved you will need a dos HO> boot disk anyway, as you cant run netadmin via os/2 let me know how HO> you get on. How exactly would you suggest I put together the files on the disks for it? The best I can do is "Create Utility Diskettes" for OS/2 or a standard DOS boot disk (I don't see how that would help me with an HPFS partition anyway).... I'd be happy to hear any other suggestions/help.... Thanks.... Ste the Sysop - Bredbury BBS (0161 4306320) 2:250/133 @ FIDO and Mancunian BBS 2:250/136 @ FIDO voice chat anytime/anyone 0161 666 8057 ... Bredbury BBS is the *BEST* BBS in Bredbury! --- * Origin: Bredbury BBS (0161 430 6320) (2:250/133) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E1R00000 Date: 01/17/97 From: JOHN ANGELICO Time: 03:57pm \/To: TONY LANGDON (Read 0 times) Subj: Trap Errors While teleporting back from the Restaurant at the End of the Universe, I heard Tony say about Trap Errors: TL> TL> I use a fan/heatsink here, seems to do the trick, even in today's TL> TL> 37 degree C heat. :-) TL> TL> JA> Wow, where are you? We haven't had a decent summer like that for TL> JA> years! Now organising for a fan to go on top of the chip. TL> TL> Melbourne, last weekend. :-) TL> TL> JA> ! Origin: Melbourne PC User Group BBS (3:632/309) TL> ^^^^^^^^^^ TL> TL> Thought you would have noticed the heat too. ;) TL> I like it warmer than most so don't notice as much I guess. Sorry, I should have looked at your origin line, too. Ciao, John Angelico alias talldad@pobox.com.au ___ X KWQ/2 1.2i X T.A.R.D.I.S. - the ORIGINAL mobile phone! --- * Origin: Melbourne PC User Group BBS (3:632/309) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E1R00001 Date: 01/17/97 From: JOHN ANGELICO Time: 04:29pm \/To: GENNADY RASHKOVICH (Read 0 times) Subj: Trap Errors While teleporting back from the Restaurant at the End of the Universe, I heard Gennady say about Trap Errors: GR> JA> For the rest, I am still wondering about three things: GR> JA> 1) heat of the CPU chip (have tried the desktop unit in various GR> JA> positions to see if air can circulate better) GR> on-chip fan is good enough in any position. Good - I am organising one of them GR> JA> 2) network cards (do GR> JA> I need something genuine?) GR> Well, I saw a lot of LANs running with far-far-from-native clones ;) But do they run OK or have problems? ;) GR> JA> or 3) lack of disk space on my C: GR> JA> partition (only about 2Mb left out of 76; swapper of 12Mb and GR> JA> spooler both on D: drive but really only about 40Mb left there) GR> JA> [Sheesh and I used to be so happy with the XT, DOS and a 20Mb HDD!] GR> Well, I saw you posting about your trouble for a few days. GR> At first, traps 000c..000e with known-as-worked progs GR> tell that something is wrong with GR> memory|motherboard|DMA|Drivers<->hardware. But traps seem diminished with repositioning of the system unit... GR> I saw problems like yours with native OS/2 drivers for GR> NE2000-compatible cards and ne2000 clones. So - try to find GR> NS2000*.* - drivers for National Semicondactor netcards - GR> they didn't use DMA and memory page, and work well with a GR> lot of NE2000-compatible cards, including GR> chinese|taiwanese|corean clones. Of course, you'll check GR> IRQ, IOAddress, Ethernet address in Protocol.ini. Using defaults 300h and IRQ10. The network works (sl-o-ow at times... but) Could you explain need for this checking in PROTOCOL.INI, please? GR> GR> The second try is: GR> check whether your computers grounded well. Rather GR> often, net between computers with different voltage on GR> cases/grounds don't break down neither kill the cards, but GR> just going computers down to trap. Hmm, this is a new and useful thought. Where would I look for a grounding strap? Power supply? Chassis? What to look for? GR> And the third try is: GR> You shall try to experiment - change memory|motherboard GR> (if you can, of course). GR> Um, not so easy. May save that as a last resort. Thank you for the suggestions. Ciao, John Angelico alias talldad@pobox.com.au ___ X KWQ/2 1.2i X It was clearly and simply explained on page 542,839 of the docs. --- * Origin: Melbourne PC User Group BBS (3:632/309) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E1R00002 Date: 01/17/97 From: JOHN ANGELICO Time: 04:54pm \/To: GENNADY RASHKOVICH (Read 0 times) Subj: Net Messaging While teleporting back from the Restaurant at the End of the Universe, I overheard Gennady say to Erwin about Net Messaging: GR> Erwin Hogeweg wrote in a message to Hubert Atkinson: GR> [...] GR> HA> Can someone tell me how to turn off the "Network Messaging". GR> HA> Attempting to run a 2 node peer setup, and the auto start of net GR> HA> messaging just slows things down... GR> EH> Just remove the MESSENGER from the wrkservices in your IBMLAN.INI. GR> EH> ;wrkservices = MESSENGER,PEER GR> EH> wrkservices = PEER GR> It's only a part of solution. The real way is to delete "Network GR> Messaging" from startup folder _and_ to delete Messenger GR> from server's start list. GR> If you'll delete MESSENGER only - well, NM would be GR> started and then ended with loud cry "can't run without GR> Messenger server". So the time+memory would be used for a GR> time. GR> And can anyone tell me if there is anything else to substitute for Net Messsaging.. I find it too slow and (seemingly) single threaded, so it's a pain at the moment. Ciao, John Angelico alias talldad@pobox.com.au ___ X KWQ/2 1.2i X If at first you DO succeed, try not to look astonished. --- * Origin: Melbourne PC User Group BBS (3:632/309) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E1R00003 Date: 01/19/97 From: TONY LANGDON Time: 03:05am \/To: WAYNE DELISLE SR. (Read 0 times) Subj: Warp 3 and TCP/IP It's 17 Jan 97 06:28:00, We'll return to Wayne Delisle Sr. and Tony Langdon's discussion of Warp 3 and TCP/IP WDS> It's an Infotel NE2000 compatable 10-base-2 16 bit lan card. The dos WDS> diagnostics that came with it work fine and the lan hub recognizes it WDS> ok, but OS/2 can't seem to find it for some reason. What version of OS/2? I know that with Warp Connect 3, the NE2000 driver that comes with the system isn't really suitable, as most NE2000 clones are programmed I/O, and the driver for the Eagle NE2000 seems to assume shared memory. However, there are several NE2000 drivers out there on the Net that will work fine. I used one for one installation I did, and the card worked fine. You have to download the driver, stick it on a floppy and then select "other" when selecting a network card, and tell OS/2 that it's on drive A: FYI, the card I'm currently using came with OS/2 drivers, so that was the same (except for not having to download). :-) I'm not sure what the situation is with Warp 4 though... WDS> Hah well, my son is coming home from college for the weekend. He will WDS> probably figure it out in no time. Good luck. :-) ... DOS=HIGH....I wonder what drug it's using --- FMail/386 1.02 * Origin: The Bridge - Remote Sysop. (3:635/728.18) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E1R00004 Date: 01/21/97 From: ALEC HERRMANN Time: 01:04am \/To: GERRY BRITTON (Read 0 times) Subj: peer to peer? Hello Gerry, Replying to a message of Gerry Britton to Alec Herrmann: GB>> Alec, I've installed NE2000's on a Pentium 166 and an older GB>> 486DX2-66. I've managed to get the cards recognized by Warp 4. GB>> What do I do next to get peer-to-peer actually working? AH>> domain name that you chose for both machines? What are AH>> the workstation names you chose for both? What userid GB> Simple names. "dad's machine" & "Pat's machine". Actually, it sometimes makes it harder to find problems when the system does not work as expected. From past experience, I would suggest you change the names to something from 4 to 8 characters long, with no special symbols. I would suggest something like 'DADSRVR' and 'PATSRVR'. You can change the names later on to something more suitable once everything is working. If/when you start using the command line to connect to network drives, you will soon see what I mean. Typing 'NET USE X: \\DADSRVR\DRIVEC' is a lot easier than typing 'NET USE X: \\"dad's machine"\DRIVEC'. I have no idea if putting quotes around a machine name allows you to use spaces within the name in the command line. The domain name on both machines should be the same and make it simple as well - try something like 'HOMENET' for starters. AH>> and password have you initially specified? Did you GB> Also simple logon's & P-words. Have you set up the same logon names and passwords on both machines? I suggest doing so. AH>> Do both workstations start successfully? GB> Here's a little prob. The 486DX2-66 is having a problem with GB> the NE2000. It sees the driver, RAM location & interrupt GB> etc, but can't load the driver. The NIC's EPROM is currently GB> set at 0320h and IRQ 15. I've gotten TRAP 05's at various GB> addresses. I'll be shifting the card to different slots GB> today to try & eliminate this, but it's intermittent. You will have to get an error-free startup before going any further. Also try different interrupts - try 7 (if no 2nd parallel port or sound card there), or 10 or 11 (if no SCSI or other controllers there). AH>> If you share (using the Connections -> Network -> AH>> Network Services -> Shared Resources and Network AH>> Connections -> Properties -> Shares Tab) one of your AH>> local drives, does it show up on the other machines AH>> Connections Tab (in the same folder location)? GB> No. I can't see anything but this workstation. The network card drivers will have to load successfully before going any further. Regards, Alec --- FleetStreet 1.12 NR * Origin: The Nibble's Roost, Richmond BC 604-540-8048 (1:153/8086)