said:
>in mass over to the other partition. Then I edited my config.sys. I'm
>just flabbergasted that this was the answer!
Well, that is where the dump data pointed me.
>Now, I need to strip those 2 directories I copied over.
Yes. You copied a lot of extra files. Of course, on the good side you
can now set up almost any type of networking you want, even if you don't
need to.
>I decided to run mpts to make the adjustments, removing the peer & vpc
>for me. That didn't work, mpts got stuck in a loop and never loaded the
>config. So I edited protocol by hand, but i'm certainly no expert. I
>guess something is not right with one of the ini's or maybe config.sys.
If you are using the Java GUI MPTS, you probably need some blank lines at
the end of config.sys, protocol.ini and so forth. It's a known problem.
>Any ideas on how much of ibmcom & mpts I can remove? I'm thinking most
>of it but since I have room there maybe it isn't worth the effort.
You can remove a lot. You will know when you have removed too much when
you start get boot error messages or error reports in lantran.log.
I don't keep all that close track of what is common code and what is not,
but I'm always willing to guess.
>Here are the lines I added to the config.sys:
>DEVICE=z:\IBMCOM\PROTOCOL\LANPDD.OS2 <-- remove??
Not sure.
>DEVICE=z:\IBMCOM\PROTOCOL\LANVDD.OS2 <-- remove??
Yes.
>DEVICE=z:\IBMCOM\LANMSGDD.OS2 /I:z:\IBMCOM /S <-- remove??
Not sure.
>
>DEVICE=z:\IBMCOM\PROTMAN.OS2 /I:z:\IBMCOM
No.
>DEVICE=z:\MPTN\PROTOCOL\SOCKETSK.SYS
No.
>DEVICE=z:\MPTN\PROTOCOL\AFOS2.SYS
No.
>DEVICE=z:\MPTN\PROTOCOL\AFINETK.SYS
No.
>DEVICE=z:\MPTN\BIN\VDOSTCP.VDD
Yes. This the the DOS TCP/IP shim.
>DEVICE=z:\MPTN\PROTOCOL\AFNB.SYS /S:100 /C:225 /N:21 <--
>remove??
Yes. It's for NETBIOS.
>RUN=z:\MPTN\BIN\AFNBINI.EXE <--
>remove??
Yes. More NETBIOS.
>RUN=z:\MPTN\BIN\CNTRL.EXE <--
>remove??
No. It's the TCP/IP daemon.
>CALL=z:\OS2\CMD.EXE /Q /C z:\MPTN\BIN\MPTSTART.CMD >NUL
>RUN=z:\IBMCOM\PROTOCOL\NBTCP.EXE <--
>remove??
Yes. It's for NETBIOS over TCPIP.
>RUN=z:\MPTN\BIN\VDOSCTL.EXE
Yes. It's DOS TCP/IP support.
>REM *** 3c905 nic driver ***
>DEVICE=z:\IBMCOM\MACS\EL90X.OS2
>Thanks, it really feels good to have a successful ending.
Now you can point the fellow over on the Possi list in the right
direction. I can't say for sure that you both have the same problem, but
it's definitely the first thing to check out.
BTW, did fixing the TCP/IP stack fix PMDLL?
Regards,
Steven
--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.41 #10183 Warp4/FP15/14.093c_W4
www.scoug.com irc.webbnet.info irc.fyrelizard.org #scoug (Wed 7pm PST)
----------------------------------------------------------------------
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"rollin@scoug.com".
=====================================================
<< Previous Message <<
Return to [ 03 |
May |
2004 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.