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 [ 11 | October | 2002 ]

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


Date: Fri, 11 Oct 2002 19:03:51 PST7
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Correct formula for BOOTOS2 + eCS ?

=====================================================
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 <3DA781A7.5E781A62@pacbell.net>, on 10/11/02
at 04:58 PM, "J. R. Fox" said:

>subsequent time as I found them. (A stock eCS install places BOOTOS2
>under \TVoice\Wiseprog\BootECS , where I think it is very unlikely
>to work "out-of-the-box." For convenience sake, I gave it its own

You are wrong about this.

> BOOTOS2 2Disk=A Source=P:\BootECS\Required VDM Help Trace

>and let 'er rip. Attempts 4 & 5 failed due to insufficient disk space.
>O.K., I could have left out VDM and Help, but the \DLL, \Install, and
>\MDOS directories created under \OS2 on Disk one are empty. The obvious

Makes sense that it would fail. You are trying to stuff about 10MB of
files on 2 diskettes. Keep it simple and try:

bootos2 source=P:\BootECS\Required target=A: format:fat ga400

It will be tight, but it should fit.

>larger kernel . . . and I gather we would need the later kernel for
>things like supporting LVM. Or maybe the 2-Disk option is no longer
>possible with a 4.5 level Warp ?

I would not worry about about disk count, until you have a working set of
diskettes.

>One other thing is that I deliberately fashioned a pared-down Config.Sys
>specifically for this set, and placed it in the "Required" directory
>where it's supposed to go, yet BOOTOS2 ignored it, insisting on putting
>all sorts of unnecessary stuff (like all the Internet networking stuff)
>into a large Config.Sys on Disk 1. That never happened when I made these
>sets for W3 or W4.

The moral here is don't do that. Don't try to break the rules until you
have success following the rules.

Steven

--
---------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.35 #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 [ 11 | October | 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.