--------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: EEE00001 Date: 09/26/97 From: THOMAS W. MUELLER Time: 10:07pm \/To: DOUG REYNOLDS (Read 1 times) Subj: WARP 3 [non-connect] & Windows 95 Tach Doug! am 22 Sep 97 um 17:07:06 schrieb Doug Reynolds an Jonathan de Boyne Pollard: JdBP>> The answer is simple. The *non*-Connect flavour of OS/2 Warp 3 comes JdBP>> without either TCP/IP or LAN Server networking software, so you have JdBP>> to buy it. TCP/IP for OS/2 and LAN Requester for OS/2 are both JdBP>> available as standalone products from IBM. DR> ic. well, this version came with a bonus pack that had TCP/IP with DR> it....... The bonus pack has no TCP/IP support for network cards. MfG :-) Thomas Antworten bitte an 2:2454/117.1. Please reply to 2:2454/117.1. --- MxXEd/2 1.00 * Origin: Shuttle to Heaven BBS (2:254/283.117) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: EEE00002 Date: 10/09/97 From: DOUG REYNOLDS Time: 10:05am \/To: BILL HLIWA (Read 1 times) Subj: Win95 to Warp connect BH> A more basic question .... how do you install netbeui on the warp box? OS/2 uses netbios which is pretty much the same or is the same as netbeui. the maverick # http://www.microserve.net/~mav/ # mav@microserve.net ... Dolby of Borg: They blinded me with irrevelance. --- Telegard/2 v3.08.b08/mL * Origin: the rebel multiline 1X % 3.100Gs % 412/459.7290 (1:2610/0) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: EEE00003 Date: 10/08/97 From: TONY LANGDON Time: 08:29am \/To: JIM TRULOCK (Read 1 times) Subj: Possible Network It's 04 Oct 97 01:44:00, We'll return to Jim Trulock and Tony Langdon's discussion of Possible Network JT> Is it better, then, to simply install TCP/IP on both computers, and JT> leave out the IBMPEER network? Or should both be installed. I would JT> also like to do work on my machine from mom's from time to time. You need both TCP/IP and IBMPEER on your machine. They perform quite different functions. TCP/IP is a transport which is required for Internet access. IBMPEER is a network client and server for sharing files, printers and modems. It can use TCP/IP or another protocol (e.g NetBIOS/NetBEUI or IPX/SPX) to carry its data. As for remotely accessing your machine, you'll need remote control software such as OS2You/PM2You or similar if you want to control the GUI. For text mode control, there are many options with varying levels of functionality. JT> Ok, so do I need to set up both machines with a default IP address ... JT> like 255.255.255.1 and 255.255.255.2, and just have each one routed to These won't work. I'd suggest 192.168.1.1 and 192.168.1.2, netmask of 255.255.255.0 JT> the dynamic address I get when In-Joy would connect to my provider. JT> (As you can probably tell, I know absolutely nothing about networking JT> outside of what I've read here. ) I'm not sure of the correct way to interface your LAN with InJoy. It's a case of reading the docs (I have officially allocated IP addresses here and at work, use a proxy server instead of IP masquerading). TL> I believe this is possible with a NET LOGON command in the startup TL> sequence somewhere. JT> Hmm ... just checked and I can't find a LOGON command for the NET JT> command. ;( You're right. :-( I'm not sure of the OS/2 equivalent (been using too much Windoze lately ;-) ). ... I used to be a terrible flirt, but I'm much better at it now. --- FMail/386 1.02 * Origin: The Bridge - Remote Sysop. (3:635/728.18) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: EEF00000 Date: 10/10/97 From: MIKE TRIPP Time: 12:03pm \/To: PETE KASPER (Read 1 times) Subj: OS/2 Hello Pete. 10 Oct 97 05:26, Pete Kasper wrote to All: PK> I was just wondering is OS/2 still being produced or is it a PK> dead thing? It's a dead puppy. The last time IBM updated it was at least 3 days ago. :) .\\ike --- GoldED/2 2.50+ * Origin: -=[ TechKnowledgy at Work ]=- (1:382/61.1) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: EEF00001 Date: 10/10/97 From: PETE KASPER Time: 05:26am \/To: ALL (Read 1 times) Subj: OS/2 Hello, I was just wondering is OS/2 still being produced or is it a dead thing? --- Maximus 3.01 * Origin: BitByters BBS, Rockland ON, Can. (613)446-7773 v34, (1:163/215) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: EEF00002 Date: 10/10/97 From: ALEC HERRMANN Time: 12:56am \/To: JIM TRULOCK (Read 1 times) Subj: Possible Network Hello Jim, Replying to a message of Tony Langdon to Jim Trulock: TL>> I believe this is possible with a NET LOGON command in the startup TL>> sequence somewhere. JT>> Hmm ... just checked and I can't find a LOGON command for the NET JT>> command. ;( TL> You're right. :-( I'm not sure of the OS/2 equivalent (been using too TL> much Windoze lately ;-) ). The OS/2 logon command is simply LOGON (the executable is LOGON.EXE); there is no NET in front of it. Run LOGON /? to get the command line parameters for LOGON. 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: EEF00003 Date: 10/09/97 From: TONY LANGDON Time: 11:32am \/To: DAVID RICHARDSON (Read 1 times) Subj: Win95 to Warp connect It's 03 Oct 97 21:47:38, We'll return to David Richardson and LEE ARONER's discussion of Win95 to Warp connect DR> Volume in Drive M has no label DR> Directory of M:\ DR> FILE NOT FOUND DR> 409,665,536 Bytes Free DR> The bytes free is correct.. It kinda works but mostly don't. DR> Everything works fine when I'm booted to Windows 95 on both machines DR> that *I think* rules out hardware.. DR> Does anybody have any ideas... I've exhausted mine :-( Have you checked the access controls? You might need to allow access to the drive in OS/2 Peer. I've found that not giving access in directories results in an empty listing when viewed from a connected Win 95 machine. ... It's mind over matter - it you don't mind, it don't matter. --- FMail/386 1.02 * Origin: The Bridge - Remote Sysop. (3:635/728.18) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: EEG00000 Date: 10/11/97 From: GORAN ERIKSSON Time: 03:01pm \/To: ALL (Read 1 times) Subj: Rename I'm running a workstation with Lantastic for OS/2 on a network with a number of MS-DOS Lantastic peer-to-peer servers. Since I have many sharable disk partitions on the network I want to connect each server to one and only one drive on the OS/2 workstation (e.g. NET USE Z: \\GET002 where GET002 is one of my MS-DOS servers). I then find that RENAME (both from OS/2 and DOS windows on the OS/2 workstation) won't work as expected. In the audit log below I've been working from GET001 (the OS/2 workstation) onto GET002 (one of the MS-DOS servers). I've connected \\GET002 to Z: on GET001 and logged on to directory Z:\CDISK\HELP. There I create a file called M. Then I do a REN M M1. The audit log looks like below. Note that it seems that the workstation tried to give the file the new name \CDISK\CDISK\HELP\M1. That directory doesn't exist on the server and isn't created as a result of the rename command. The OS/2 command interpreter (both in OS/2 and DOS mode) reports that the rename command fails. If I create the directory C:\CDISK\HELP on the MS-DOS server and retry the rename operation the file C:\HELP\M is moved to C:\CDISK\HELP\M1. I welcome all suggestions how I could get this thing to work as one would expect. And no, connecting each server partition to a separate drive designator on the workstation is no viable option. (But it solves the problem when i try it.) I've tried Lantastic 5, 6 as well as 7 on the MS-DOS server but the problem stays there all the same. A 97.10.11 13:35:51 GET001 GET001 L \CDISK\HELP\M A 97.10.11 13:35:51 GET001 GET001 L \CDISK\HELP\M A 97.10.11 13:35:51 GET001 GET001 L \CDISK\HELP\M A 97.10.11 13:35:51 GET001 GET001 L \CDISK\HELP\M A 97.10.11 13:35:51 GET001 GET001 N \CDISK\HELP\M A 97.10.11 13:35:51 GET001 GET001 N \CDISK\CDISK\HELP\m1 --- * Origin: GET, Lidingo, Sweden, +46-8-7655670 (2:201/505) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: EEG00001 Date: 10/10/97 From: LEE ARONER Time: 12:18am \/To: TONY LANGDON (Read 1 times) Subj: Pinball.sys FS> NTFS_001.ZIP ~283Kb. LA> Frank, no can freq. I'll look around on the web/ftp for that file LA> name, or is it a local special ? TL> Do a search on the words "HPFS" and "Windows NT",you should find it > (That's how I got it). Already did. LRA -- SPEED 2.00 #2720: I've finally got this ficts, fics, fixd ... --- Platinum Xpress/Win/Wildcat5! v2.0 * Origin: Grey Matter * Seattle, WA * 1:343/210 * (206) 528-1941 (1:343/210) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: EEG00002 Date: 10/10/97 From: LEE ARONER Time: 12:20am \/To: BILL HLIWA (Read 1 times) Subj: Win95 to Warp connect > I have Warp v3 connect and Windows 95b set to the same > workgroup with Netbeui... BH> A more basic question .... how do you install netbeui on the warp box? > > I use samba on linux boxes and they live happily with the Win95 boxes. Would > be nice to allow the OS/2 boxes to join in the fun. It's the standard Netbios. NetBUEI stands for "NetBios User Enhanced Interface" or some such silly MS acronym. LRA -- SPEED 2.00 #2720: Heisenberg may have been here. --- Platinum Xpress/Win/Wildcat5! v2.0 * Origin: Grey Matter * Seattle, WA * 1:343/210 * (206) 528-1941 (1:343/210)