SCOUG-HELP Mailing List Archives
Return to [ 24 |
June |
2003 ]
<< Previous Message <<
>> Next Message >>
Content Type: text/plain
=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================
Steven,
Thanks for your offer of help. Without the attached files I'll repeat this message on SCOUG-HELP and look for the continuing dialog there.
Of the six files you requested 3 (config.sys, startup.cmd, and lantran.log) exist on the OS/2 boot drive which is J:\ . Ibmlan.ini does exist on drive I:\ibmlan. Protocol.ini does exist on I:\ibmcom. Those are attached. There are two setup.cmd files which seem pertinent. One is in I:\mptn\bin attached as 1Setup.cmd. The other is in I:\tcpip\dos\bin attached as 2setup.cmd.
I remember last year getting advice to keep MPTN out of the OS/2 boot drive. Drive I: is set up with sd's of IBMCOM, IBMLAN, IBMLANLK, MPTN, RSUin, and tcpip. The problem as I gave up on it last year was summarized in two emails the text of which follow.
>>>> Where can I find detailed instruction on configuring MPTS and TCP/IP to
>>>> provide file and print sharing on an OS/2 box with a LAN hosted by a
>>>> WinXP box and also serving a WinME box?
>>>>
>>>> The Win machines work properly with each other. The OS/2 box does
>>>> accomplish ICS communication with the XP box which provides internet
>>>> access via a satellite feed. My OS/2 mail and browser clients work well
>>>> across that feed.
>>>>
>>>> The OS/2 box does not see the shared files on the XP or ME boxes and vice
>>>> versa.
>>>>
>>>> I am at Warp4 fix15 with MPTS 5.12 and TCP/IP services updated per the
>>>> November 2001 version of WarpUP.
>>>>
>>>> I have installed MPTS religiously per Frank Field's 1998 PEER.HTM
>>>> instructions and all seems well. I have created the HOST file on the XP
>>>> machine and reset "lmannounce" in the XP registry to 1. But I'm missing
>>>> something. Some switch must be set the wrong way or address wrong and I
>>>> can't find it.
>>>>
>>>> RokNRob's "Surviving with OS/2 in a Sea of Windows" indicates that the
>>>> MPTS installation provides an online book "Network Adapters and Protocol
>>>> Services Guide" in an Assistance folder inside the Information Folder
>>>> under Tasks. I can't find any of those.
and,
>NETVIEW \\lanhostname yields "The Requester service is >Starting", followed
>by the SYS2070 error (problem loading code) >followed by a seemingly
>endless series of dots on the "... >service is Starting" line.
>>Effort to log in through the connections folder yields
>>"Requester is starting" followed by a SYS 2070 error followed by
>>a NET2140 error ((Internal LAN software error).
That's all that's new, Steve. What follows is your response to my inquiry initiating this year's effort to get file and print sharing to operate between my OS/2 box (Micron P133 with SCSI drives) and my "mshome" network host box running Windows XP with ICS (Dell Dimension 8200).
Thanks, Ken
>>From: "Steven Levine"
>>Date: Thu, 19 Jun 2003 22:25:25 -0700
>>To: kfh777@earthlink.net
>>In-Reply-To:
>>Subject: Re: Clean up OS/2
>>X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v2.37/37
>>Message-Id:
>In , on 06/19/03
> at 12:04 PM, kfh777@earthlink.net said:
>>I'm at fix 15 on OS/2 Warp 4. Years ago I did not originally install
>>networking. When I tried to add it last year it would not go. I can
>>share the internet connection from my newer WinXP box but cannot achieve
>>print and file sharing. A program (whose name I have now forgotten is
>>reported as broken).
>>I've been anticipating a whole new OS/2 re-install to achieve networking.
>>Most of you seem to have moved on to e-ComStation. Does that make more
>>sense and would it work to achieve file and print sharing when done over
>>a broken OS/2?
>eComStation is an excellent upgrade if you want or need what it
>provides. I use it, just not yet on this box. That said, if you
>have no compelling need to upgrade at this time, there's no reason
>why you can't install network on your existing Warp4 box. It's
>just a matter of a few workarounds to handle situations that were
>unforseen in 1995.
>What I would prefer is that you join the SCOUG-Help mailing list
>and we do the work there. You don't need to be a SCOUG member to
>join the list, although new members are always welcome. :-) This
>way others can learn from your experience.
>To get started, I'll need to see copies of:
> config.sys
> setup.cmd
> startup.cmd
> protocol.ini
> ibmlan.ini
> lantran.log
>Some of these may not exist. Just let me know.
>Steven
--
-----------------------------------------------------------
K.F.Hammer Associates Ken Hammer
management consultations Barnet, VT 05821
-----------------------------------------------------------
=====================================================
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 <<
>> Next Message >>
Return to [ 24 |
June |
2003 ]
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.
|