SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, 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.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 02 | May | 2003 ]

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


Date: Fri, 2 May 2003 20:53:03 PDT7
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: BOOT.OS2 Question...?I

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

In <200305021831.3059373.7@scoug.com>, on 05/02/03
at 06:31 PM, "Harry Motin" said:

>If you use files from the CD (uncheck the "Use files from the disk if
>they exist" option) then there is no size problem. If you select to use
>the hard drive files, most likely there will be a size problem.

There may be no size problem, but there may be a function problem. :-)

My POV is that I don't do this often enough to spend much time worrying
the problem. I only update the diskettes after major system changes.
Then I back up the originals with savddskf just in case the masters get
corrupted.

As you note, there are many ways to work around most problems that might
come up when creating or updating the diskettes.

Steven

>I use the files from the hard drive and I had a size problem, when I
>first tried it. I examined the drivers loaded by the CONFIG.SYS file
>(Diskette 1) and decided what ones I did not need for my system (I
>selected maybe 4 or 5 of the largest ones). Then I temporarily replaced
>them with 0 size files on my hard drive. I then let the OS/2 utility
>create the 4 diskettes. Naturally, it placed 0 size driver files on
>Diskette 1 and/or 2. I then edited the CONFIG.SYS to remove the
>references to these drivers. Finally, I erased the 0 size drivers from
>Diskettes 1 and 2.

>Lastly, I created a REXX script to automate the entire process.

>Something like the above has to be done, if you use the newer driver
>files on your hard drive for the OS/2 utility diskettes. I assume that
>the same is true for the BOOTOS2 diskettes.
>HCM

--
---------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.37 #10183 Warp4/FP15/14.085_W4
www.scoug.com irc.webbnet.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 << >> Next Message >>

Return to [ 02 | May | 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.