SCOUG-HELP Mailing List Archives
Return to [ 04 |
July |
2002 ]
<< 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.
=====================================================
Hello
You use a OS/2 Warp Installation CD-ROM from mid of nineties ...
... you use the most accurate Warp4IU diskette set from end of
nineties !
Without "set copyfromfloppy=1" your installation process will
install the
files from the, partially already, obsolete CD-ROM !!
You need the entry *set copyfromflopy=1" to make sure that your
installation
is getting the more accurate files from your newly created
floppies !!!
Rick Meig's Config Info Tool says:
------------------------------------------------------------------
---------------------------------
SET COPYFROMFLOPPY=1
If OS/2 should install updated drivers during an installation
from the
Installation disks and not from CD this statement must reside in
the
config.sys on Installationdisk 1
------------------------------------------------------------------
---------------------------------
Good luck, svobi
xowatson@concentric.net on 04.07.2002 17.19.44
Please respond to scoug-help@scoug.com
To: scoug-help@scoug.com
cc:
Subject: SCOUG-Help: Basic Help
On 4 Jul 2002 at 7:11, Harry Chris Motin wrote:
> SET COPYFROMFLOPPY=1
> I am not sure why you have that in the CONFIG.SYS file of your
up and
> running and installed OS/2.
I had forgotten about that one, too, looked it up and the first
hit was
from the esteemed Mr Warren at
http://www.scoug.com/Terry/w4inst/hints.htm. I think Harry's
right,
Butch probably doesn't need it.
Using an Alternate Device Driver
In some cases you need to use a different version of a device
driver that is normally included in the OS/2 installation set.
For
example, the FD16-700.ADD driver does not work correctly on
certain combinations of the FD1680 controller and Micropolis
2217 SCSI disk drive (this problem first appeared in Warp 3.0)
but the OS/2 2.11 driver does work ok. For this install, it was
necessary to copy the install diskette 1 and then overlay the
driver with the 2.11 version.
To make sure that the non-standard driver is used throughout the
install process, you add the following statement to the
CONFIG.SYS file:
SET COPYFROMFLOPPY=1
With this statement, you will be prompted to reinsert diskettes 1
and 2 at the end of the first install phase. NOTE:You should
still
verify at the end of all install phases that the correct driver
is
present on your hard drive in the apprpriate directory (usually
OS2\BOOT).
************************************************************
*** >>> Say NO to HTML in Mail and News <<< ***
*** ++++++++++++++++++++++++++++++++++++++++++++++++ ***
*** >>> AGAINST TERROR +++ AGAINST WAR <<< ***
************************************************************
=====================================================
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 [ 04 |
July |
2002 ]
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.
|