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-General Mailing List Archives

Return to [ 21 | April | 1999 ]

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


Date: Wed, 21 Apr 1999 12:20:07 PST8PDT
From: Dallas Legan <dallasii@kincyb.com >
Reply-To: scoug-general@scoug.com
To: scoug-general@scoug.com
Subject: SCOUG-General: Re: Maintenance Partitions

With regard to what Dave Watson covered in the General Interest meeting
Sat. on maintenance partitions, by using Boot OS/2 twice and
some copying files around, it is possible make a set of 'Super' boot disks.
Some of the documentation in the notes Dave put up on his web page
discuss how it is good to have the maintenance partition on another
disk from where you normally boot, so it is available for the worst of
catastrophes. The problem is that if you are limited to just floppies
for the 'other disks' there isn't much room for tools for
getting you system back up.
What I found was that I could 'lock' in as a fixed drive and then
run Boot OS/2 on a parallel port Zip Disk and install on it.
The problem with this is that a parallel port Zip Disk is not normally
bootable, so I then created a bootable floppy with Boot OS/2,
and made sure it had all the BASEDEV drivers on it (and a few other
files I can't recall at the moment), the IFSs needed, and copied the
CONFIG.SYS file over. The main change needed for CONFIG.SYS was that
any parameters that needed a full path name had to point to the
Zip drive. So far, I've had to settle for Mshell, instead of
WPS, but I'm working on that.
Specifics will probably take some experimentation for differing
system configurations.
You might even want to put some communications tools on the
Zip disk to send for help with with.

I don't see that this can't be done with an IDE Zip, or some other
types of removable media. Use of 2 boot floppies may be needed if
one gets too crowded to hold it all.
Try to keep everything together, but just in case, put
disk images of the bootable floppies on the zip disk, in some
image format you might have access to if your OS/2 is not available.

Regards,
Dallas E. Legan II
(562) 862 - 4854 ext. '*'

L
E
G
A
N
@
A
C
M
.
O
R
G

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

To unsubscribe to this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-general".

For problems, contact the list owner at
"rollin@scoug.com".

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


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

Return to [ 21 | April | 1999 ]



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.