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 [ 26 | January | 2004 ]

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


Date: Mon, 26 Jan 2004 13:26:42 PST8
From: "i-lists" <i-lists@synass.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Archive boot, was Checkini hang / Robosave !?

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

Hello

>There is an old saying, at least older than ANY version of OS/2,
>
> If it ain't broke, don't fix it!

OK, that's true ;-)

The difficulty nowadays is that I even do not know =

if these elder SW are working properly with the OS =

versions appearing after the SW's date !!

>Just because RoboSave doesn't have a recent date doesn't mean it =

>doesn't work. How old is the OS/2 Archive backup methodology???

Changing from WARP version 3 to version 4 I assume the respective =

files have been adjusted to match the system's new data ;-)

>Just like you need to edit the OS2.KEY file to add files necessary for =

>your particular system, the RoboSave profile must be modified with the =

>same information to make it a viable WPS backup method. You have to
know =

>AND SPECIFY what you need to back up with either method or else the =

>backup will be useless.

EXACT !!

The OS2.KEY indeed is far away from a good set !
Years ago I found some interesting hints and suggestions in a book =

named: OS2 Warp V4 in Team !!
I followed their recommendations and you SCOUGians were very helpful
too ;-))
=

>I, too, have used RoboSave for years and it has bailed me out on more =

>than on occasion.

OK, this sounds good and I can say the same for my =

WPS builtin archive tool too.

However: I am not fixed to this backup / restore method !
If one finds ie ROBOSAVE is better than the builtin WPS archive system =

I am open for givin it a try ...
=2E.. but I do check actuality, appearing, content and ReadMe's of this =

new tool before running into troubles !

Thanks for your comments ;-)
svobi

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

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

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 [ 26 | January | 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.