SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Thu, 1 May 2003 16:43:27 PDT7
From:	Peter Skye <pskye@peterskye.com >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: files not found

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.
=====================================================

Butch Langel wrote:
>
> My next move was to start in revovery mode. I selected
> the 0 option ( original settings) and started up. Now
> when I start the system I am getting these error messages:
>
> SYS1718 Sustem cannot find the file C:\MPTN\PROTOCOL\IFNDIS.SYS specified
> in the DEVICE statement on line 21 of the CONFIG.SYS file.
> Line 121 is ignored. Press enter to continue.
>
> SYS1718 System cannot find the file C:\tcpip\bin\vdostcp.vdd specified
> in the DEVICE statement on line 140 of the CONFIG.SYS file.
> Line 140 is ignored. Press enter to continue.
>
> SYS1718 System cannot find the file C:\TCPIP\BIN\VDOSCTL.EXE specified
> in the DEVICE statement on line 142 of the CONFIG.SYS file
> Line 142 is ignored. Press enter to continue.

Butch,

I *think* your "0 option" boot is using one of the alternate
CONFIG.SYS files -- probably CONFIG.X but possibly CONFIG.M.

Look at the lines 121, 140 and 142 in your CONFIG.SYS,
CONFIG.X and CONFIG.M files and see which of them is the
one with these error lines.

CONFIG.X and CONFIG.M are in \OS2\BOOT\. EPM has a line
counter so you don't have to count the lines manually.

If these alternate CONFIG.* files aren't kept up-to-date
with your CONFIG.SYS some _very_ bad things can happen.
For example, if they contain references to old drivers
for your hard drive (the old ones didn't work about 4 GB)
you can destroy your partition table. (This can happen
if, for example, you've been using Dani's drivers which
have different names so the old drivers are still on
your boot drive.) My synchronization method is real
simple -- I sort the files to temporary files and then
compare their contents.

As for why your system won't boot after doing an Archive,
I don't know. Restoring the OS2*.INI files from a backup
might fix it. But remember that you _can't_ restore the
OS2*.INI files from a backup when they are in use (i.e.
you've booted from that drive) because the files are
kept in memory; copying the old backups over the OS2*.INI
files won't help because when you shut down your system
the copies in memory will overwrite the files again,
overwriting the new "copies". Either boot to a different
partition or boot from floppies.

- Peter

=====================================================

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".

=====================================================

Return to [ 01 | May | 2003 ]

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.