SCOUG-HELP Mailing List Archives

>> Next Message >>

Date:	Wed, 21 Jan 2004 00:42:43 PST8
From:	"i-lists" <i-lists@synass.net >
Reply-To:	scoug-help@scoug.com
To:	waynec@linkline.com
Subject:	SCOUG-Help: Re: BootOS2 / better into Maintenance Partition !

Content-Id: <1074696155-1-i-lists@synass.net>
Content-Transfer-Encoding: quoted-printable

Hi Wayne =

Do NOT worry about the "Installation Diskette" ...
=2E..they remain the same since OS/2 WARP 4 came !!!

While the "Installation Diskette", called Disk 0, remains the same, =

Disk 1 (containing the CONFIG.SYS) and Disk 2 got updated =

from IBM !!

Your BootOS2 installation will ask only for this "Installation =

Diskette / Disk 0" and not for the 2 other diskettes ...
=2E..your BootOS2 environment will be createt from your =

actual / present OS/2 !

I do agree with you about the concernings not to touch your =

running system !

But you ignored my, and also Steven's, hint to prepare =

A bootable maintenance partition !? Why ?

This MP would be much more easier and comfortable to use =

and you are not running into space problems !

Another comfort: Adding BootOS2 to your BootManager you =

can test and try immediately if it works or not ...
=2E.. also later in case of difficulties you do not need to search =

for the floppies !!

Attached you receive my CMD file to start BootOS/2 installation =

how I did it ...
=2E.. you have to adjust to your environment and needs.

- 2_D.cmd =

My BootOS2 software is in E:
Source if OS/2 is C:
and destination where to install BootOS2 is: D:

Do not hesitate: Come and ask again if you feel insecure !

Good luck and have a nice day
svobi

waynec@linkline.com on 20/01/2004 22:26:54
To: i-lists@synass.net
cc: =

Subject: BootOS2

Svobi, you said in a reply to my post on SCOUG: =

"Hi Wayne
Todays OS/2 files are quite big to fit on diskettes ! =

Why don't you prepare a small bootable Maintenance Partition
and install BootOS2 ?? =

It's more comfortable and faster to use and easier to get it running ;-)
Cheers, svobi" =

I took a look at BootOS2 and thought I'd start simple, so I made an
initial =

attempt at creating a 2-diskette bootable OS/2 by typing: =

bootos2 target=3DA 2disk =

but it immediately asked me to insert an install diskette 1 in the A:
drive. =

I thought at first it was just asking for a blank diskette, but it
wouldn't =

take that, so I am confused as to how this program works; I don't want
to =

screw up my existing system, and a new one based on the install
diskettes =

isn't going to help me much, since they aren't working. The verbiage
about =

the "source" parameter says all the stuff necessary to build the new =

bootable system has to be in one place, with no clue as to how you
manage =

that or whether the stuff is from the original install materials or the =

current production system . =

I appreciate your attempt to help, and I know I am probably making this =

tougher than it is, but I'm confused and the last thing I want to do is =

screw up my existing hard drive system. =

Wayne =

Wayne

************************************************
>>> Say NO to H T M L in Mail and News <<<
>>> A G A I N S T T E R R O R & W A R <<<
************************************************=

name="2_D.cmd"
Content-Id: <1074696155-2-i-lists@synass.net>
Content-Transfer-Encoding: quoted-printable
Content-Description: <2_D.cmd>
Content-Disposition: attachment; filename="2_D.cmd"

E:\os2\bootos2\926\bootos2 source=3DC:\os2\install\bootdisk target=3DD: typ=
e=3DWPS nls(001,us,850) rexx help vdm vga sysed swap=3DD:\bootos2 temp=3DD:=
\bootos2 trace format:HPFS ga400=1A=

Return to [ 21 | January | 2004 ]

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.