|
| Why did eCS 2.0 RC2 populate Config.Sys w/Wrong Boot Drive Letter? |
 |
Tue, 02 Oct 2007 16:28:01 -040 |
Just by accident, I discovered that the install of eCS 2.0 RC2 on the
O-Drive for some reason has populated many of the Config.Sys entries to
point to C-Drive where my eCS 1.2R was already installed.
Examples of lines in my O-Drive system that point to the C-Drive:
~~~~~~~ ~~~~~~~
>-------------------------------------------------------------------
> These entries are in O:\CONFIG.SYS
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM /S
>DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
>--------------------------- 25 LINE(S) NOT DISPLAYED --
>DEVICE=C:\IBMCOM\MACS\GENM32W.OS2
>DEVICE=C:\IBMCOM\MACS\GENM32W.OS2
>--------------------------- 31 LINE(S) NOT DISPLAYED --
>DEVICE=C:\OS2\BOOT\ASPIROUT.SYS
>---------------------------
>LIBPATH=.;. . . C:\MPTN\DLL;C:\IBMCOM\DLL;...
>SET PATH=. . . ;C:\MPTN\BIN;C:\IBMCOM;...
>SET DPATH=C:\MPTN;C:\IBMCOM; . . .
>SET HELP=C:\MPTN;C:\MPTN\HELP; . . .
>---------------------------
>SET NLSPATH=C:\MPTN\MSG\NLS\%N;C:\TCPIP\msg\ENUS850\%N; . . .
>---------------------------
>SET ETC=C:\MPTN\ETC
>---------------------------
>SET SOMBASE=C:\OS2
>SET SOMRUNTIME=C:\OS2\DLL; . . .
>---------------------------
>CALL=C:\IBMCOM\PROTOCOL\NETBIND.EXE
>RUN=C:\IBMCOM\LANMSGEX.EXE
>---------------------------
>DEVICE=C:\MPTN\PROTOCOL\SOCKETSK.SYS
>DEVICE=C:\MPTN\PROTOCOL\AFOS2.SYS
>DEVICE=C:\MPTN\PROTOCOL\AFINETK.SYS
>DEVICE=C:\MPTN\BIN\VDOSTCP.VDD
>RUN=C:\MPTN\BIN\CNTRL.EXE
>CALL=O:\OS2\CMD.EXE /Q /C C:\MPTN\BIN\MPTSTART.CMD >NUL
>RUN=C:\MPTN\BIN\VDOSCTL.EXE
>---------------------------
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Questions:
1) WHY would the install process point to the C-Drive instead
of pointing to the equivalent/correct directories on the
O-Drive?
2) While things do seem to be running [mostly] OK, I've got to
believe this is a time-bomb waiting to explode. So, how do
I FIX this without destroying BOTH platforms?
FWIW: The only possible connection that might be made between the
O-Drive and the C-Drive is that I use the C-Drive to download packages,
updates, tools, etc. And, eCSMT is located on the C-Drive.
OTOH, because the O-Drive is not a GA level, I've never attempted to
use eCSMT to update the O-Drive.
Any suggestions will be greatly appreciated!
TIA,
|
| Post Reply
|
| Re: Why did eCS 2.0 RC2 populate Config.Sys w/Wrong Boot Drive Letter? |
 |
Tue, 02 Oct 2007 22:59:27 +020 |
On 02.10.07 22:28, Carl Gehr wrote:
> Just by accident, I discovered that the install of eCS 2.0 RC2 on
> the O-Drive for some reason has populated many of the Config.Sys
> entries to point to C-Drive where my eCS 1.2R was already installed.
>
> DEVICE=C:\OS2\BOOT\ASPIROUT.SYS
I can't believe this one was added by the installer. I had to add it
myself.
I suggest to install eCS 2.0rc2 again and then see what happens.
--
|
| Post Reply
|
| Re: Why did eCS 2.0 RC2 populate Config.Sys w/Wrong Boot Drive Letter? |
 |
Wed, 03 Oct 2007 01:00:11 +010 |
Hi Carl
Carl Gehr wrote:
> Just by accident, I discovered that the install of eCS 2.0 RC2 on the
> O-Drive for some reason has populated many of the Config.Sys entries to
> point to C-Drive where my eCS 1.2R was already installed.
>
> Examples of lines in my O-Drive system that point to the C-Drive:
> ~~~~~~~ ~~~~~~~
> >-------------------------------------------------------------------
> > These entries are in O:\CONFIG.SYS
> >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM /S
> >DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
> >--------------------------- 25 LINE(S) NOT DISPLAYED --
> >DEVICE=C:\IBMCOM\MACS\GENM32W.OS2
> >DEVICE=C:\IBMCOM\MACS\GENM32W.OS2
> >--------------------------- 31 LINE(S) NOT DISPLAYED --
> >DEVICE=C:\OS2\BOOT\ASPIROUT.SYS
> >---------------------------
> >LIBPATH=.;. . . C:\MPTN\DLL;C:\IBMCOM\DLL;...
> >SET PATH=. . . ;C:\MPTN\BIN;C:\IBMCOM;...
> >SET DPATH=C:\MPTN;C:\IBMCOM; . . .
> >SET HELP=C:\MPTN;C:\MPTN\HELP; . . .
> >---------------------------
> >SET NLSPATH=C:\MPTN\MSG\NLS\%N;C:\TCPIP\msg\ENUS850\%N; . . .
> >---------------------------
> >SET ETC=C:\MPTN\ETC
> >---------------------------
> >SET SOMBASE=C:\OS2
> >SET SOMRUNTIME=C:\OS2\DLL; . . .
> >---------------------------
> >CALL=C:\IBMCOM\PROTOCOL\NETBIND.EXE
> >RUN=C:\IBMCOM\LANMSGEX.EXE
> >---------------------------
> >DEVICE=C:\MPTN\PROTOCOL\SOCKETSK.SYS
> >DEVICE=C:\MPTN\PROTOCOL\AFOS2.SYS
> >DEVICE=C:\MPTN\PROTOCOL\AFINETK.SYS
> >DEVICE=C:\MPTN\BIN\VDOSTCP.VDD
> >RUN=C:\MPTN\BIN\CNTRL.EXE
> >CALL=O:\OS2\CMD.EXE /Q /C C:\MPTN\BIN\MPTSTART.CMD >NUL
> >RUN=C:\MPTN\BIN\VDOSCTL.EXE
> >---------------------------
> >
> >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
> Questions:
> 1) WHY would the install process point to the C-Drive instead
> of pointing to the equivalent/correct directories on the
> O-Drive?
>
I have not tried rc2 myself but this is the 1st post with this problem.
Is it possible that you copied a chunk of the C:\config.sys when copying
required driver entries?
> 2) While things do seem to be running [mostly] OK, I've got to
> believe this is a time-bomb waiting to explode. So, how do
> I FIX this without destroying BOTH platforms?
>
If (big word) the problem only applies to config.sys entries then I
suggest editing all C:\ entries to O:\ (Replace tool).
Might be worth nosing through the INI files just to make sure nothing in
there points to C:\ instead of O:\
Regards
Pete
> FWIW: The only possible connection that might be made between the
> O-Drive and the C-Drive is that I use the C-Drive to download packages,
> updates, tools, etc. And, eCSMT is located on the C-Drive.
>
> OTOH, because the O-Drive is not a GA level, I've never attempted to
> use eCSMT to update the O-Drive.
>
> Any suggestions will be greatly appreciated!
>
> TIA,
|
| Post Reply
|
| Re: Why did eCS 2.0 RC2 populate Config.Sys w/Wrong Boot Drive Letter? |
 |
Fri, 05 Oct 2007 21:22:30 -040 |
Peter Brown wrote:
> Hi Carl
>
> Carl Gehr wrote:
>> Just by accident, I discovered that the install of eCS 2.0 RC2 on the
>> O-Drive for some reason has populated many of the Config.Sys entries
to
>> point to C-Drive where my eCS 1.2R was already installed.
>>
>> Examples of lines in my O-Drive system that point to the C-Drive:
>> ~~~~~~~ ~~~~~~~
>>
>-------------------------------------------------------------------
>> > These entries are in O:\CONFIG.SYS
>>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> >DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM /S
>> >DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
>> >--------------------------- 25 LINE(S) NOT DISPLAYED --
>> >DEVICE=C:\IBMCOM\MACS\GENM32W.OS2
>> >DEVICE=C:\IBMCOM\MACS\GENM32W.OS2
>> >--------------------------- 31 LINE(S) NOT DISPLAYED --
>> >DEVICE=C:\OS2\BOOT\ASPIROUT.SYS
>> >---------------------------
>> >LIBPATH=.;. . . C:\MPTN\DLL;C:\IBMCOM\DLL;...
>> >SET PATH=. . . ;C:\MPTN\BIN;C:\IBMCOM;...
>> >SET DPATH=C:\MPTN;C:\IBMCOM; . . .
>> >SET HELP=C:\MPTN;C:\MPTN\HELP; . . .
>> >---------------------------
>> >SET NLSPATH=C:\MPTN\MSG\NLS\%N;C:\TCPIP\msg\ENUS850\%N; . . .
>> >---------------------------
>> >SET ETC=C:\MPTN\ETC
>> >---------------------------
>> >SET SOMBASE=C:\OS2
>> >SET SOMRUNTIME=C:\OS2\DLL; . . .
>> >---------------------------
>> >CALL=C:\IBMCOM\PROTOCOL\NETBIND.EXE
>> >RUN=C:\IBMCOM\LANMSGEX.EXE
>> >---------------------------
>> >DEVICE=C:\MPTN\PROTOCOL\SOCKETSK.SYS
>> >DEVICE=C:\MPTN\PROTOCOL\AFOS2.SYS
>> >DEVICE=C:\MPTN\PROTOCOL\AFINETK.SYS
>> >DEVICE=C:\MPTN\BIN\VDOSTCP.VDD
>> >RUN=C:\MPTN\BIN\CNTRL.EXE
>> >CALL=O:\OS2\CMD.EXE /Q /C C:\MPTN\BIN\MPTSTART.CMD >NUL
>> >RUN=C:\MPTN\BIN\VDOSCTL.EXE
>> >---------------------------
>> >
>>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>>
>> Questions:
>> 1) WHY would the install process point to the C-Drive instead
>> of pointing to the equivalent/correct directories on the
>> O-Drive?
>>
>
>
> I have not tried rc2 myself but this is the 1st post with this problem.
>
> Is it possible that you copied a chunk of the C:\config.sys when copying
> required driver entries?
>
>
>
>> 2) While things do seem to be running [mostly] OK, I've got to
>> believe this is a time-bomb waiting to explode. So, how do
>> I FIX this without destroying BOTH platforms?
>>
>
>
> If (big word) the problem only applies to config.sys entries then I
> suggest editing all C:\ entries to O:\ (Replace tool).
>
> Might be worth nosing through the INI files just to make sure nothing in
> there points to C:\ instead of O:\
>
> Regards
>
> Pete
Thanks for the comments, Pete.
First, I'm not the type that jumps into editing Config.Sys except for a
couple of specific areas where I have no choice. e.g., I have the OS/2
COBOL and PL/I compilers and they do not correctly install using the
tools provided with the compiler. I've had to deal with this for years,
so I'm quite confident about what I'm doing there.
The thing that is particularly interesting is that virtually every entry
[that is, directory and subdirectory] that has the wrong drive is also
related to networking in some way. e.g., MPTN, IBMCOM [The SOM related
entries are tied into the two compilers, but the modifications I had to
make were all on the F-Drive, because that's where the compilers are
installed. And, all I did was _add_ entries and make sure they were
behind the system directories. So, at least, it is very unlikely that I
made changes from O to C.
The one or two possibilities, other than the install, that I can think
of might be MPTS changes and/or GenMac install. I've had to make a
bunch of changes in these areas trying to get this TPad T60 working.
Can you think of any way those updates/installs could cause something
like this?
Thanks, again,
|
| Post Reply
|
| Re: Why did eCS 2.0 RC2 populate Config.Sys w/Wrong Boot Drive Letter? |
 |
Fri, 05 Oct 2007 22:34:36 -040 |
On 10/05/07 09:22 pm Carl Gehr wrote:
> The thing that is particularly interesting is that virtually every entry
> [that is, directory and subdirectory] that has the wrong drive is also
> related to networking in some way. e.g., MPTN, IBMCOM [The SOM related
> entries are tied into the two compilers, but the modifications I had to
> make were all on the F-Drive, because that's where the compilers are
> installed. And, all I did was _add_ entries and make sure they were
> behind the system directories. So, at least, it is very unlikely that I
> made changes from O to C.
>
> The one or two possibilities, other than the install, that I can think
> of might be MPTS changes and/or GenMac install. I've had to make a
> bunch of changes in these areas trying to get this TPad T60 working. Can
> you think of any way those updates/installs could cause something like
> this?
Recently I changed network adapters using MPTS. The setup I wanted to
change is on E:, but when I wanted to save the changes, only Q: and U:
showed as preselected. I highlighted E: as well, then found that the
changed lines in E:\CONFIG.SYS contained references to Q: instead of to
E:. So something in MPTS is screwy.
-=-
|
| Post Reply
|
|
|