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 [ 28 | April | 2004 ]

<< Previous Message <<


Date: Wed, 28 Apr 2004 20:15:35 PDT7
From: "Harry Motin" <hmotin@sbcglobal.net >
Reply-To: scoug-help@scoug.com
To: < "scoug-help@scoug.com" > scoug-help@scoug.com >
Subject: SCOUG-Help: BA2k & maintenance partition

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

On Wed, 28 Apr 2004 17:23:15 PDT7, Jon Harrison wrote:

>The problem is running baiicr on the maintenance partition (or in
>my case, with a slimmed down WPS created with BootAble, running
>clrest) fails. baiicr fails for me with:

Perhaps I can help. I now use BA/2K server edition, version 3.0A. I previously used BA/2K workstation edition, version 3.0.

Up until a few weeks ago, I used BAIICR on 5 crash recovery diskettes, created by first making the 4 Warp utility diskettes
and then using the BackAgain utility to modify them into crash recovery diskettes. Since I've upgraded to ECS, I no longer
use the crash recovery diskette method, because that method now fails for me. The problem is that it does not place all of
the required files on the diskette, because there is not enough room (using the 1.4 MB diskettes). So, in my case I've
switched to bootAble, the bootable CD. And I now have the BA/2K program, itself, and not BAIICR, on the CD. When I boot to
the CD, its very fast. I have a slimmed down version of the WPS and I have the use of BA/2K, the full program, and not the
slimmed down BAIICR from a commandline. I couldn't be happier!

So, my question to you is: why are you attempting to use BAIICR on a bootAble CD? Why aren't you placing the full BA/2K
program on the CD, instead? I'm not certain how you determined which Back Again files to place on the CD, if you want to
use BAIICR. How did you do that, when the BackAgain crash recovery utility is designed to use diskettes and not a CD or a
maintenance partition?

Please note that bootAble has a very good configuration file for placing the required Back Again files on your CD so that you
have the full Back Again program on the CD. That configuration file worked for me with no modification. I think you should use
that approach.

Hope this helps!
HCM

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

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

Return to [ 28 | April | 2004 ]



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.