Evenin',

Is there anyone out there (well, besides me and 2 others I know of. :) thats still running Ezycom under OS/2?

Trav'ler

... Quartzsite, AZ: Avg age 80. The home of 'Drive-by shoutings.'

--- Ezycom V2.01b001 00F90258
* Origin: The Shaman's Inn - Quartzsite, Az (1:114/635)

Is there anyone out there (well, besides me and 2 others I
know of. :) thats still running Ezycom under OS/2?

i dunno...

this is to let you know that the echo is working between us, though :wink:

)\/(ark


* Origin: (1:3634/12)

Quoting Patrick Vittori to All
Subj. Ezycom & OS/2, dated 06-May-2003 21:47

Is there anyone out there (well, besides me and 2 others I know of.
:) thats still running Ezycom under OS/2?

Guess I don't count, thinking I'm one of the two. :)

Cheers...
Gordon Lewicky (Pdk)

email glewicky@telus.net http://milkyway.tzo.com


--- EzyBlueWave/2 V2.01b001 00F90260
* Origin: Milky Way, Langley, BC [604] 532-4367 (1:153/307)

Once upon a time, out on MARS.

While reading the mail, wispering this:

Is there anyone out there (well, besides me and 2 others I know of. :) tha

ts

still running Ezycom under OS/2?

Haven't heard anyone... I'm using WildCat! (Dos) and Warp3 fp42
.......

Chris Martin, The MARS Station BBS

* WCE 2.1G1/2419 * God Bless America, but God help Canada to put up with the

--- ViaMAIL!/WC v1.60d
* Origin: From an Echo heard on MARS. Call to be transported. (1:219/308)

Evenin' Mark,

know of. :) thats still running Ezycom under OS/2?

i dunno...

/sigh/ Dunno why not. Been running Ezy on this box since '97 and its bee solid.

this is to let you know that the echo is working between us, though :wink:

Oh darn... I don't think I got this msg. <BWG>

Laters!

Patrick

... For me, insanity is not a disease. Its a *hobby*.

--- Ezycom V2.01b001 00F90258
* Origin: The Shaman's Inn - Quartzsite, Az (1:114/635)

Quoting Gordon Lewicky to Patrick Vittori <=-

Quoting Patrick Vittori to All
Subj. Ezycom & OS/2, dated 06-May-2003 21:47

Is there anyone out there (well, besides me and 2 others I know of.
:) thats still running Ezycom under OS/2?

Guess I don't count, thinking I'm one of the two. :)

I'm here too. But I won't have the BBS running under OS/2 until I can
get TCP/IP (and the serial ports!) to coexist with the Netware client.
I can have one or the other, but not both. :-(


--- FMailX 1.60
* Origin: Shadowgard (1:105/50)

Afternoon,

Is there anyone out there (well, besides me and 2 others I know of.
:) thats still running Ezycom under OS/2?

Guess I don't count, thinking I'm one of the two. :)

Hehee... Yup, you and Paul Sanders be the only ones *I* know of.

I'd be interested in finding out just -how- one goes about getting Ezy to acknowledge SIO's vmodem sos I can go telnetable. I can get Bink to "see" the incoming call, but Ezy.... /sigh/ Shes ah no see the carrier (of course there ain't one. :/ ).

Anyhoo, either here or via email would help answer the question.

Patrick

... Coffee & a computer running OS/2. Who needs anything else?

--- Ezycom V2.01b001 00F90258
* Origin: The Shaman's Inn - Quartzsite, Az (1:114/635)

*** Quoting Leonard Erickson to Gordon Lewicky dated 05-08-03 ***

I'm here too. But I won't have the BBS running under OS/2 until I can
get TCP/IP (and the serial ports!) to coexist with the Netware client.
I can have one or the other, but not both. :-(

Leonard,

Might I ask why you need the Netware client??
I didnt think there was many companies still using it.

Rich
I-Net turtil@frontiernet.net


... It's The Gophers And The Rabbits! They're Conspiring...
---
* Origin: Turtil's Pond BBS. Monroe NY 845-783-2106 (1:2624/50)

Hi Patrick,

Is there anyone out there (well, besides me and 2 others
I know of. :) thats still running Ezycom under OS/2?

Well I'm actually running EleBBS but I have Ezycom still setup to run under OS/2 so in a way I do... Why what's the problem?

Lata,
Wayne

---
* Origin: Bad News BBS 4 Telnet Lines - badnewsbbs.darktech.org (3:633/690)

Hello Leonard!

08 May 03 02:02, Leonard Erickson wrote to Gordon Lewicky:

I'm here too. But I won't have the BBS running under OS/2 until I can
get TCP/IP (and the serial ports!) to coexist with the Netware client.
I can have one or the other, but not both. :-(

Have you tried reconfiguring the protocols with MPTS adding Netware first? I seem to recall having some issues with coexistence if the TCP/IP was added/configured before the Netware myself.

.\\ike

--- GoldED 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Quoting Patrick Vittori to Gordon Lewicky
Subj. Ezycom & OS/2, dated 08-May-2003 13:05

I'd be interested in finding out just -how- one goes about getting
Ezy to acknowledge SIO's vmodem sos I can go telnetable. I can get
Bink to "see" the incoming call, but Ezy.... /sigh/ Shes ah no see the carrier (of course there ain't one. :/ ).
Anyhoo, either here or via email would help answer the question.

1st of many long emails (I'm sure) is on it's way. :)

Cheers...
Gordon Lewicky (Pdk)

email glewicky@telus.net http://milkyway.tzo.com


--- EzyBlueWave/2 V2.01b001 00F90260
* Origin: Milky Way, Langley, BC [604] 532-4367 (1:153/307)

Mornin' Wayne,

I know of. :) thats still running Ezycom under OS/2?

Well I'm actually running EleBBS but I have Ezycom still setup to run under OS/2 so in a way I do... Why what's the problem?

/shocked look.../ TWO BBSs?!? What a concept!!! <G>

Don't know if'n you saw the reply to Gordon L. or not, but I'm having fits trying to get vmodem and Ezy to link. I run BT/2
2.60XE/Gamma 6 (async) as the frontend and -it- sees the telnet call (vmodem set for com4), but the BBS software barfs when it doesn't find a carrier.

I understand the fact that OS/2 starts comport numbers and DOS com numbers report back differently, but even making those
adjustments didn't get the prob solved.

BTW, which ver of Ezy do you have installed? Theres a v2.00 out now. :)

Patrick

... DOS developer's original sin: max usable memory by DOS = 640K.

--- Ezycom V2.01b001 00F90258
* Origin: The Shaman's Inn - Quartzsite, Az (1:114/635)

Evenin' Gordon,

I'd be interested in finding out just -how- one goes about getting
Ezy to acknowledge SIO's vmodem sos I can go telnetable. I can get

1st of many long emails (I'm sure) is on it's way. :)

Got the first one today, read it, but haven't had a chance to act on it. 3 more weeks of intense wood working before I get a break for a few days. Then its on to stained glass... Somewheres in there I -hope- to get a little computer time. Trouble with a home-based business is that you _never_ leave work. :/

Patrick

--- Ezycom V2.01b001 00F90258
* Origin: The Shaman's Inn - Quartzsite, Az (1:114/635)

Quoting Rich Wonneberger to Leonard Erickson <=-

*** Quoting Leonard Erickson to Gordon Lewicky dated 05-08-03 ***

I'm here too. But I won't have the BBS running under OS/2 until I can
get TCP/IP (and the serial ports!) to coexist with the Netware client.
I can have one or the other, but not both. :-(

Leonard,

Might I ask why you need the Netware client??
I didnt think there was many companies still using it.

I'm using it because I have a Netware server. I have it because it's
the easist way to handle DOS, OS/2, Windows (and if I ever get the
ethernet card fixed) Macs on one server.

Basicly, without the Netware client the DOS box *can't* access the
files for the BBS, and other stuff, all of which reside on the Netware
server.

Also, my printer srerver works with Netware, but not with Windows
(except thru the Netware client on a Windows box).

--- FMailX 1.60
* Origin: Shadowgard (1:105/50)

Quoting Mike Tripp to Leonard Erickson <=-

Hello Leonard!

08 May 03 02:02, Leonard Erickson wrote to Gordon Lewicky:

I'm here too. But I won't have the BBS running under OS/2 until I can
get TCP/IP (and the serial ports!) to coexist with the Netware client.
I can have one or the other, but not both. :-(

Have you tried reconfiguring the protocols with MPTS adding Netware
first? I seem to recall having some issues with coexistence if the
TCP/IP was added/configured before the Netware myself.

I've got Netware working (been working for years). But my local OS/2
gurus don't know anything about Netware, and none of the attempts by
them or buy me get T CP/IP working.

One got TCP/IP working by redoing the config.sys, but with that
config.sys, Netware won't work.

--- FMailX 1.60
* Origin: Shadowgard (1:105/50)

Quoting Patrick Vittori to Gordon Lewicky
Subj. Ezycom & OS/2, dated 09-May-2003 21:14

Hi Patrick,

few days. Then its on to stained glass... Somewheres in there I -hope-
to get a little computer time. Trouble with a home-based business is
that you _never_ leave work. :/

Know all about home based working. Just holler when yer ready. :)

Cheers...
Gordon Lewicky (Pdk)

email glewicky@telus.net http://milkyway.tzo.com


--- EzyBlueWave/2 V2.01b001 00F90260
* Origin: Milky Way, Langley, BC [604] 532-4367 (1:153/307)

Hello Leonard!

10 May 03 02:24, Leonard Erickson wrote to Mike Tripp:

Have you tried reconfiguring the protocols with MPTS adding
Netware first? I seem to recall having some issues with
coexistence if the TCP/IP was added/configured before the Netware
myself.

I've got Netware working (been working for years).

I am referring to configuring the OS/2 Netware client...not the Novell server.

But my local OS/2 gurus don't know anything about Netware, and
none of the attempts by them or buy me get T CP/IP working.

One got TCP/IP working by redoing the config.sys, but with that config.sys, Netware won't work.

Trying to get there by hacking CONFIG.SYS is definitely "the hard way", particularly for a multiprotocol setup. You can have all the correct statements but in the wrong sequence (including out-of-sequence with other non-networking-related lines) and still not get there from here. You may end up needing to know the differences between ODI vs NDIS and shims between, Netware-specific PROTOCOL.INI statements, edit NIC-specific .NIFs, etc. If your gurus don't have Netware experience, they will probably not be guru enough
for this particular approach to this particular exercise.

Try running MPTS(.exe) instead. MPTS stands for "MultiProtocol Transport Services" and is intended to facilitate exactly what you're trying to do. It is the closest equivalent that OS/2 has to the GUI dialogue you'd find in the the "Networking" control panel in MS, ie: Pick a NIC from this list; Pick a protocol from that list; Connect a selected protocol to a selected NIC. It will then make and save all the appropriate changes to the appropriate files (including CONFIG.SYS) for you, hiding much of the complexity of the issues above.

While this route is a lot simpler, it is not without quirks of its own depending on the exact NIC & protocols involved. The suggestion that I was trying to make was: when selecting protocols and attaching them to the NIC (in the MPTS configuration tool)...select the Netware protocol (they don't label it
"IPX/SPX", but "IBM Netware Requester" or some such) prior to selecting the IBM
TCP/IP and attaching it to the same adapter. Depending on the NIC involved, I have seen both protocols fail or only the TCP/IP work after selecting the two protocols and attaching them in the reverse order.

Sorry for assuming that you were hung from the same tree as I was, since I noticed the same rope around your neck. :)

.\\ike

--- GoldED 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Quoting Mike Tripp to Leonard Erickson <=-

Have you tried reconfiguring the protocols with MPTS adding
Netware first? I seem to recall having some issues with
coexistence if the TCP/IP was added/configured before the Netware
myself.

I've got Netware working (been working for years).

I am referring to configuring the OS/2 Netware client...not the Novell server.

But my local OS/2 gurus don't know anything about Netware, and
none of the attempts by them or buy me get T CP/IP working.

One got TCP/IP working by redoing the config.sys, but with that config.sys, Netware won't work.

Trying to get there by hacking CONFIG.SYS is definitely "the hard
way", particularly for a multiprotocol setup. You can have all the correct statements but in the wrong sequence (including
out-of-sequence with other non-networking-related lines) and still not
get there from here. You may end up needing to know the differences between ODI vs NDIS and shims between, Netware-specific PROTOCOL.INI statements, edit NIC-specific .NIFs, etc. If your gurus don't have Netware experience, they will probably not be guru enough for this particular approach to this particular exercise.

Well, according to MPTS I've *already* got TCP/IP installed.

[E100BODI].....
0 - IBM OS/2 NETBIOS
2 - IBM Netware Requester Support
1 - IBM TCP/IP

So according to you, I should change the numbers on the last two?

--- FMailX 1.60
* Origin: Shadowgard (1:105/50)

Hello Leonard!

11 May 03 21:12, Leonard Erickson wrote to Mike Tripp:

[E100BODI].....
0 - IBM OS/2 NETBIOS
2 - IBM Netware Requester Support
1 - IBM TCP/IP

So according to you, I should change the numbers on the last two?

You didn't mention the third protocol earlier, so I can't tell you what will make or break you with the three-way mix...no experience taming this particular
pile. As a WAG, I would try the sequence: Netware, Netbios, TCP/IP.

.\\ike

--- GoldED 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Quoting Mike Tripp to Leonard Erickson <=-

Hello Leonard!

11 May 03 21:12, Leonard Erickson wrote to Mike Tripp:

[E100BODI].....
0 - IBM OS/2 NETBIOS
2 - IBM Netware Requester Support
1 - IBM TCP/IP

So according to you, I should change the numbers on the last two?

You didn't mention the third protocol earlier, so I can't tell you
what will make or break you with the three-way mix...no experience
taming this particular pile. As a WAG, I would try the sequence:
Netware, Netbios, TCP/IP.

I *think* Netware needs the NETBIOS, but I wouldn't swear to it.


--- FMailX 1.60
* Origin: Shadowgard (1:105/50)

Hello Leonard!

11 May 03 21:12, Leonard Erickson wrote to Mike Tripp:

[E100BODI].....
0 - IBM OS/2 NETBIOS
2 - IBM Netware Requester Support
1 - IBM TCP/IP

So according to you, I should change the numbers on the last two?

You didn't mention the third protocol earlier, so I can't tell you
what will make or break you with the three-way mix...no experience
taming this particular pile. As a WAG, I would try the sequence:
Netware, Netbios, TCP/IP.

I just made a couple quick tries. Using MPTN to change the numbers around had the following results:

0 Netware
1 NETBIOS
2 TCP/IP

Errored during processing of config.sys because the Netware requester couldn't find Netbios. And neither Netware *nor* TCP/IP connected to anything.

0 Netbios
1 Netware
2 TCP/IP

Booted ok, but still couldn't connect to Netware server or to the Internet.

BTW, the non-working versions of the CONFIG.SYS were noticably *longer* than the one where Netware works.

I've saved the files, and still have the one where TCP/IP works, but Netware doesn't. I'll be running them thru a file compare utility looking for differences later.

BTW, I seem to vaguely recall being told that using MPTN to modify network setup was just about guarnteed to make a mess...?

--- FMailX 1.60
* Origin: Shadowshack (1:105/50)

Further info:

Working Config.sys:
DEVICE=C:\IBMCOM\LANMSGDD.OSS2 /I:C:\IBMCOM /S
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM

Non-working:
DEVICE=C:\IBMCOM\PROTOCOL\LAANPDD.OS2
DEVICE=C:\IBMCOM\PROTOCOL\LANVDD.OS2
DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM /S
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM

Working:
DEVICE=C:\NETWARE\E100BODI.SYS

Non-working:
DEVICE=C:\IBMCOM\PROTOCOL\ODDI2NDI.OS2
REM DEVICE=C:\NETWARE\E100BODI.SYS

And for the versions that had Netware working and TCP/IP working:

Netware:
BASEDEV=IBMKBD.SYS
DEVICE=C::\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM /S
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
DEVICE=C:\OS2\BOOT\TESTCFG.SYS

TCP/IP:
BASEDEV=IBMKBD.SYS
DEVICE=C::\IBMCOM\PROTOCOL\LANPDD.OS2
DEVICE=C:\IBMCOM\PROTOCOL\LANVDD.OS2
DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM /S
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
DEVICE=C:\OS2\BOOT\TESTCFG.SYS

Netware:
DEVICE=C:\NETWARE\VIPX.SYS
DEVICE=C:\NETWARE\VSHELL.SYS GLOBAL

TCP/IP:
rem DEVICE=C:\NETWARE\VIPX.SSYS
rem DEVICE=C:\NETWARE\VSHELL.SYS GLOBAL

Netware:
DEVINFO=KBD,US,C:\OS2\KEYBOOARD.DCP
DEVINFO=SCR,VGA,C:\OS2\BOOT\VIOTBL.DCP
SET VIO_VGA=DEVICE(BVHVGA)
SET SOMDPORT=4096

TCP/IP:
DEVINFO=KBD,US,C:\OS2\KEYBOOARD.DCP
SET SOMDPORT=4096

Netware:
RUN=C:\MMOS2\QRYMMCD.EXE
CAALL=C:\IBMCOM\PROTOCOL\NETBIND.EXE
RUN=C:\IBMCOM\LANMSGEX.EXE
SET NLSPATH=C:\MPTN\MSG\NLS\%N;c:\tcpip\msg\enus850\%N;
SET ETC=C:\MPTN\ETC
DEVICE=C:\MPTN\PROTOCOL\SOCKETS.SYS /v
DEVICE=C:\MPTN\PROTOCOL\AFOS2.SYS /v
DEVICE=C:\MPTN\PROTOCOL\AFINET.SYS /v
DEVICE=C:\MPTN\PROTOCOL\IFNDDIS.SYS /v
RUN=C:\MPTN\BIN\CNTRL.EXE
CCALL=C:\OS2\CMD.EXE /Q /C C:\MPTN\BIN\MPTSTART.CMD DEVICE=C:\IBMCOM\PROTOCOL\NETBEUI.OS2

TCP/IP:
RUN=C:\MMOS2\QRYMMCD.EXE
SEET NLSPATH=C:\MPTN\MSG\NLS\%N;c:\tcpip\msg\enus850\%N;
SET ETC=C:\MPTN\ETC
CALL=C:\IBMCOM\PROTOCOL\NETBIND.EXE
RUN=C:\IBMCOM\LANMSGEX.EXE
DEVICE=C:\MPTN\PROTOCOL\SOCKETS.SYS
DEVICE=C:\MPTN\PROTOCOL\AFOS2.SYS
DEVICE=C:\MPTN\PROTOCOL\AFINET.SYS
DEVICE=C:\MPTN\PROTOCOL\IFNDDIS.SYS
RUN=C:\MPTN\BIN\CNTRL.EXE
CCALL=C:\OS2\CMD.EXE /Q /C C:\MPTN\BIN\MPTSTART.CMD >NUL DEVICE=C:\IBMCOM\PROTOCOL\NETBEUI.OS2

Netware:
REM --- NetWare Requester staatements BEGIN ---
SET NWLANGUAGE=ENGLISH
DEVICE=C:\NETWARE\LSL.SYS
RUN=C:\NETWARE\DDAEMON.EXE
REM -- ODI-Driver Files BEGIIN --
DEVICE=C:\NETWARE\E100BODI.SYS
REM -- ODI-Driver Files END --
REM DEVICE=C:\NETWARE\ROUTE.SYS
rem DEVICE=C:\NETWARE\ODINSUP.SYS
DEVICE=C:\NETWARE\IPX.SYS
DEVICE=C:\NETWARE\SPX.SYS
RUN=C:\NETWARE\SPDAEMON.EXE
rem DEVICE=C:\NETWARE\NMPIPE.SYS
rem DEVICE=C:\NETWARE\NPSERVEER.SYS
rem RUN=C:\NETWARE\NPDAEMON.EXE
DEVICE=C:\NETWARE\NWREQ.SYS
IFS=C:\NETWARE\NWIFS.IFS
RUN=C:\NETWARE\NWDAEMON.EXE
rem DEVICE=C:\NETWARE\NETBIOS.SYS
rem RUN=C:\NETWARE\NBDAEMON.EXE
DEVICE=C:\OS2\MDOS\LPTDD.SYS
RUN=C:\NETWARE\NWTOOLS.EXE C:\NETWARE\BOOT.NWS AUTOEXIT
REM --- NetWare Requester statements END ---
IFS=C:\IBMLAN\NETPROG\NETWKSTA.200 /I:C:\IBMLAN /N DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2
rem DEVICE=C:\IBMCOM\MACS\E100B.OS2
SET I18NDIR=C:\IBMI18N
RUN=C:\IBMLAN\NETPROG\LSDAEMON.EXE
DEVICE=C:\IBMLAN\NETPROG\VNETAPI.OS2
RUN=C:\IBMLAN\NETPROG\VNRMINIT.EXE
SET NWDBPATH=C:\IBMLAN\NETPROG
SET LANINSTEP=Z:\CID\IMG\ibmpeer
DEVICE=c:\tcpip\bin\vdostcp.vdd
DEVICE=c:\tcpip\bin\vdostcp.sys
RUN=c:\tcpip\bin\VDOSCTL.EXE
SET SWING_HOME=C:\JAVA11\Swing
DEVICE=C:\MGA\OS2\KMGAX64.SYS
SET MGA=C:\MGA\OS2
SET VIO_MGA=DEVICE(BVHVGA,BMGAX64)
SET VIDEO_DEVICES=VIO_MGA
DEVICE=C:\OS2\MDOS\VVGA.SYS
DEVICE=C:\OS2\MDOS\VMGAX64.SYS
DEVICE =C:\OAD\IOMGTOOL.SYS

TCP/IP:
REM --- NetWare Requester staatements BEGIN ---
SET NWLANGUAGE=ENGLISH
rem DEVICE=C:\NETWARE\LSL.SYS
rem RUN=C:\NETWARE\DDAEMON.EXE
REM -- ODI-Driver Files BEGIIN --
rem DEVICE=C:\NETWARE\E100BODI.SYS
REM -- ODI-Driver Files END --
REM DEVICE=C:\NETWARE\ROUTE.SYS
REM DEVICE=C:\NETWARE\ODINSUP.SYS
rem DEVICE=C:\NETWARE\IPX.SYS
rem DEVICE=C:\NETWARE\SPX.SYS
rem RUN=C:\NETWARE\SPDAEMON.EXE
REM DEVICE=C:\NETWARE\NMPIPE.SYS
REM DEVICE=C:\NETWARE\NPSERVVER.SYS
REM RUN=C:\NETWARE\NPDAEMON.EXE
rem DEVICE=C:\NETWARE\NWREQ.SYS
rem IFS=C:\NETWARE\NWIFS.IFS
rem RUN=C:\NETWARE\NWDAEMON.EXE
REM DEVICE=C:\NETWARE\NETBIOS.SYS
REM RUN=C:\NETWARE\NBDAEMON.EXE
DEVICE=C:\OS2\MDOS\LPTDD.SYS
rem RUN=C:\NETWARE\NWTOOLS.EXE C:\NETWARE\BOOT.NWS AUTOEXIT
REM --- NetWare Requester statements END ---
IFS=C:\IBMLAN\NETPROG\NETWKSTA.200 /I:C:\IBMLAN /N
SET I18NDIR=C:\IBMI18N
RUN=C:\IBMLAN\NETPROG\LSDAEMON.EXE
DEVICE=C:\IBMLAN\NETPROG\VNETAPI.OS2
RUN=C:\IBMLAN\NETPROG\VNRMINIT.EXE
SET NWDBPATH=C:\IBMLAN\NETPROG
SET LANINSTEP=Z:\CID\IMG\ibmpeer
DEVICE=c:\tcpip\bin\vdostcp.vdd
DEVICE=c:\tcpip\bin\vdostcp.sys
RUN=c:\tcpip\bin\VDOSCTL.EXE
SET SWING_HOME=C:\JAVA11\Swing
DEVICE=C:\OAD\IOMGTOOL.SYS
BASEDEV=IBMATAPI.FLT
DEVINFO=SCR,VGA,C:\OS2\BOOT\VIOTBL.DCP
SET VIDEO_DEVICES=VIO_MGA
SET DISPLAYTYPE=VGA
SET VIO_VGA=DEVICE(BVHVGA)
DEVICE=C:\MGA\OS2\KMGAX64.SYS
SET MGA=C:\MGA\OS2
SET VIO_MGA=DEVICE(BVHVGA,BMGAX64)
DEVICE=C:\OS2\MDOS\VVGA.SYS
DEVICE=C:\OS2\MDOS\VMGAX64.SYS
DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2
DEVICE=C:\IBMCOM\MACS\E100B.OS2 /v

--- FMailX 1.60
* Origin: Shadowgard (1:105/50)

Hello Leonard!

13 May 03 07:07, Leonard Erickson wrote to Mike Tripp:

I *think* Netware needs the NETBIOS, but I wouldn't swear to it.

Not "No" but "Hell no!". :)

It's never been on here for more than a bit experimentation, and it definitely bound things up whenever it was the third member of a party. I believe I managed to get NETBIOS + NETWARE combo going, but peer stuff took forever to initialize and I never spent any meaningful time playing with it simply because
I couldn't stand the interminable wait during bootup. I also think I managed to successfully get myself out of a jam by getting a CID install going from a shared CD in another box with NETBIOS only. So I'm no NETBIOS protocol expert...as I've never managed to accomplish anything meaningful with it here.

Netware clients do provide netbios API support to apps that know it (I think I have a DOS chat proggy here that uses it), but we're not talking about the same
thing as storage/printer peer sharing.

.\\ike

--- GoldED 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Hello Leonard!

13 May 03 08:04, Leonard Erickson wrote to Mike Tripp:

0 Netware
1 NETBIOS
2 TCP/IP

0 Netbios
1 Netware
2 TCP/IP

Booted ok, but still couldn't connect to Netware server or to the Internet.

0 Netware
0 TCP/IP

is what is working here for years now, but it has worked with 0 and 1 for logical adapter numbers in the past.

A few more possible hacks/clarifications:

Clear the slate by removing everything in reverse order...ie, each protocol, and then the NIC. Then go through the process of adding NIC, add Netware Requester, configure Netware Requester, add TCP/IP. Don't just play with the "change number" button to give them new logical numbers.

Be sure to "edit" the Netware protocol settings and put "no" in the token-ring fields and "yes" in the ethernet fields for frame-types. They like to default to just the opposite of what they need to be sometimes. Manually typing in the
MAC address coule make or break with some of the older 8-bit ISA SMC and 3Com cards, so you can always try that while you're in there if you've written it down somewhere. Assuming an ODI NIC driver rather than NDIS, you should end up
with an \IBMCOM\PROTOCOL.INI that looks something like:

=== Cut ===
[PROT_MAN]

DRIVERNAME = PROTMAN$

[IBMLXCFG]

ODI2NDI_nif = ODI2NDI.NIF
TCPIP_nif = TCPIP.NIF
E100BEO2_nif = E100BEO2.nif

[ODI2NDI_nif]

DriverName = odi2ndi$
Bindings = E100BEO2_nif
NETADDRESS = "00d0b73ea414"
TOKEN-RING = "no"
TOKEN-RING_SNAP = "no"
ETHERNET_802.3 = "yes"
ETHERNET_802.2 = "yes"
ETHERNET_II = "yes"
ETHERNET_SNAP = "yes"
TRACE = 0x0

[TCPIP_nif]

DriverName = TCPIP$
Bindings = E100BEO2_nif

[E100BEO2_nif]

DriverName = E100B$

=== Cut ===

I'll be happy to email/netmail a CONFIG.SYS over to you with the sensitive bits
mangled if you think it'd do you any good, but I'm sure there's no shortage of examples on the www these days. The hard part is making any sense out of them... :)

BTW, the non-working versions of the CONFIG.SYS were noticably
*longer* than the one where Netware works.

One where both work at the same time could be longer still... <gd&r>

I've saved the files, and still have the one where TCP/IP works,
but Netware doesn't. I'll be running them thru a file compare
utility looking for differences later.

You may not find much of value. From my hack-by-hand experience, for multi-protocol, the sequence can be more critical than the content.

BTW, I seem to vaguely recall being told that using MPTN to modify
network setup was just about guarnteed to make a mess...?

When it fails, it fails miserably. When it works, it works (fairly) painlessly. There is nothing painless about the manual route. You can basically "remove" everything in MPTS and lose the corresponding mess, if it fails miserably. Unless you need to peer, dump the NETBIOS out of the equation and go for two. If NETBIOS is a must, I won't have much "guru value" for you...sorry.

.\\ike

--- GoldED 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Hello Leonard!

13 May 03 22:56, Leonard Erickson wrote to Mike Tripp:

Working Config.sys:
DEVICE=C:\IBMCOM\LANMSGDD.OSS2 /I:C:\IBMCOM /S DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM

Non-working:
DEVICE=C:\IBMCOM\PROTOCOL\LAANPDD.OS2
DEVICE=C:\IBMCOM\PROTOCOL\LANVDD.OS2
DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM /S
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM

Check your inbound for CONFIG.MJT...if a sample without Peer Services will do you any good. If you need all 3, then I would suggest trying 2 protocol combos
first, considering order added unique, and then test both protocols. Then do the same by adding the third protocol to the two-protocol combos that passed.

Consider TCP/IP to be the "no brainer" since you actually feed it settings later, elsewhere. Peer and Netware can fail to talk, even though they are correctly installed and loaded, due simply to bad settings that are stored externally from CONFIG.SYS.

.\\ike

--- GoldED 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Quoting Mike Tripp to Leonard Erickson <=-

Hello Leonard!

13 May 03 07:07, Leonard Erickson wrote to Mike Tripp:

I *think* Netware needs the NETBIOS, but I wouldn't swear to it.

Not "No" but "Hell no!". :)

It's never been on here for more than a bit experimentation, and it definitely bound things up whenever it was the third member of a
party. I believe I managed to get NETBIOS + NETWARE combo going, but
peer stuff took forever to initialize and I never spent any meaningful time playing with it simply because I couldn't stand the interminable
wait during bootup.

Well, the Netware *client* install installs it. And I got an error
message from the Netware requester during boot when Netbios loaded
*after* it.

I don't run Netware in peer-to-peer mode. I have a Netware *server*.

Netware clients do provide netbios API support to apps that know it (I think I have a DOS chat proggy here that uses it), but we're not
talking about the same thing as storage/printer peer sharing.

Again, this is the Netware client for talking to as Netware *server*,
not the Personal Netware peer-to-peer client. Very different animals.


--- FMailX 1.60
* Origin: Shadowgard (1:105/50)

Quoting Mike Tripp to Leonard Erickson <=-

Hello Leonard!

13 May 03 22:56, Leonard Erickson wrote to Mike Tripp:

Working Config.sys:
DEVICE=C:\IBMCOM\LANMSGDD.OSS2 /I:C:\IBMCOM /S DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM

Non-working:
DEVICE=C:\IBMCOM\PROTOCOL\LAANPDD.OS2
DEVICE=C:\IBMCOM\PROTOCOL\LANVDD.OS2
DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM /S
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM

Check your inbound for CONFIG.MJT...if a sample without Peer Services
will do you any good.

Well, for starters, I want Netware access to the server. And TCP/IP connectivity to the Internet. After that, trying to get peering to the
Windows boxes working would be nice.

Consider TCP/IP to be the "no brainer" since you actually feed it
settings later, elsewhere. Peer and Netware can fail to talk, even
though they are correctly installed and loaded, due simply to bad
settings that are stored externally from CONFIG.SYS.

Want me to zip up some config files so you can check them for dumb mistakes?

I can email them to you, or I can use Irex from a Windows box.

--- FMailX 1.60
* Origin: Shadowgard (1:105/50)

Hello Leonard!

15 May 03 02:47, Leonard Erickson wrote to Mike Tripp:

a party. I believe I managed to get NETBIOS + NETWARE combo
going, but peer stuff took forever to initialize and I never
spent any meaningful time playing with it simply because I
couldn't stand the interminable wait during bootup.

Well, the Netware *client* install installs it. And I got an error
message from the Netware requester during boot when Netbios loaded
*after* it.

I understand how you could get that misperception...but in fact you are installing MPTS, which offers (as the name suggests) multiple protocols, including several that have nothing whatsoever to do with the Netware requester. IBM OS/2 NETBIOS is one of those. It is there to support IBM Peer Services, =not= the Netware Requester.

Again, this is the Netware client for talking to as Netware *server*,
not the Personal Netware peer-to-peer client. Very different animals.

Understood...and also not available for OS/2...so, no confusion here. The only
references I've been making to "peer" are IBM's.

.\\ike

--- GoldED 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Hello Leonard!

15 May 03 02:57, Leonard Erickson wrote to Mike Tripp:

Well, for starters, I want Netware access to the server. And TCP/IP connectivity to the Internet. After that, trying to get peering to the Windows boxes working would be nice.

Great. So your priorities were identical to mine...so try my method at least once: Use the "remove" buttons to clear out all of the existing protocol and adapter selections in MPTS and start over by reselecting your NIC, adding "IBM Netware Requester support", "edit" IBM Netware Requester support to add your MAC address info and verify the yes/no setting for the frame-types, then select
"IBM TCP/IP" from the protocol window, exit/update CONFIG.SYS, reboot, and cross fingers.

If, for any reason, at any time, something that refers to NETBIOS, NetBIOS, netbios, or NETBEUI shows up in the list while you're configuring...REMOVE it immediately. If anything =else= from the 6 or so protocols listed shows up in the bottom "current configuration" window, feel free to go ahead and highlight it and hit "remove", too. :)

Want me to zip up some config files so you can check them for dumb mistakes?

I can email them to you, or I can use Irex from a Windows box.

Trying to convince you that you were wasting your time in there in the first place is where I joined this thread... :)

Now that I'm clear that you'd be satisfied with exactly what is running here, try my exact method of getting there, and you have my CONFIG.SYS for cross-reference.

.\\ike

--- GoldED 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)