SCOUG-HELP Mailing List Archives

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

Date:	Mon, 14 Oct 2002 04:21:19 PST7
From:	Harry Chris Motin <hmotin@attglobal.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: config.sys

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

Thanks for your input and thoughts. One thing I've learned about
software. We all have our own particular likes and dislikes, our own way
of doing it.

The method that I gave Butch is essentially how I do it (although I use
Back Again/2000 and GTU Sentry). I never did like the OS/2 built-in
archive method. However, I am going to re-read your information verrry
carefully. I may glean something for me to use.

I think you are right that anyone with a different backup/restore method
should offer it up as a suggestion.

Thanks for your help
HCM
____________________________________________________________________________

"Info2SYNass.NET" wrote:
>
> Hi Harry, hello everbody
> I appreciate very much your efforts with the REXX scripts for
> saving
> important files ;-)
>
> Myself I do not like very much the offline backups and restores
> ;-(
> We better should learn and show the features OS/2 does include
> ;-))
>
> Every OS/2 Warp has a reliable way to save its important system
> files !
>
> It is its own archive and you find it under WPS Properties !!
>
> Unfortunately like many other good things with OS/2 it
> is prepared insufficiently !!!
>
> After OS/2 is installed it creates the first archive which is
> displayed as
> 0 = Zero while booting under "Recovery Choices"
>
> Hint:
> The WPS properties tab "Archive" shows 3 possible settings:
>
> 1) A button to activate archiving
>
> I suggest not to activate permanently !
> If you save a malfunctioning or misbehavioring system soon one is
> stucked ;-(
>
> My use of this button is very specific:
> Before I am going to do experiments with unknown stuff I am doing
> an archive
> to be sure to have a working roll back !
>
> 2) A path, where to save the archives
>
> Normally, this is stored in the OS/2 system partition
> x:\OS2\Archives but could be on
> ones data partition instead with setting that specific path i.e.
> my direction: H\OS2\Archives
> to be included in a more frequent backup procedure ;-)
>
> 3) A button for Displaying the Recovery Choices
>
> With todays fast systems I always activate this button and set
> for 3 seconds !
> So I do not have to wait too long for my system otherwise it is
> long enough
> to select a specific choice if necessary.
>
> Very important is also to add some more entries of important
> files to the file OS2.KEY !
> With all your important entries in this OS2.KEY file one need to
> do an archive run
> very frequently to keep 3 generations plus a basic generation = 4
> archives, ie like:
>
> 1) Archive created 10.10.2002 10.10.22
> 2) Archive created 01.10.2002 10.01.34
> 3) Archive created 30.09.2002 09.30.34
> 0) Original archive from INSTALL created 30.09.2002 09.00.06
>
> Another hint:
> With ARCINST one can replace the archive stored under 0 = zero !
> You see mine was created on September 30iest before monthly
> backups ;-)
> Why to do so ?
>
> The first archive (the first one after system installation or any
> previous one may not
> contain newer drivers i.e. your newer SCSI adapter and booting
> with F2 one will get
> some error messages therefor.
>
> Another trick:
> If you check the archives entries you will see a match between
> date and time !
> That is my control function ;-) If date is October 1st then time
> has to be 10 and 01 !!
> This shows that I did this specific archive run ...
> ... if these two do not match I may have forgotten to switch off
> the archiving button
> and so I may not use that errorously archived generation !!!
>
> Well, I will stop here.
> I am sure if one uses the archiving system like I have learnt ...
> ... one will not suffer to get ones system running after problems
> very fast again ;-)
>
> If one has any suggestions I appreciate every input for a more
> better solution ;-))
>
> Regards, svobi
>
> PS- one more add-on:
>
> On and off I had gotten a CHKDSK after some system problems with
> a message
> displayed that "scenter.cfg or dll" (!?) had some problems !
> Since then I am doing some manual copy of these 2 files to a
> location off the
> system partition !!
> I this error happens I do need to restore these two files only !!!
>
> hmotin@attglobal.net on 14.10.2002 03.56.49
> Please respond to scoug-help@scoug.com
> To: scoug-help@scoug.com
> cc:
> Subject: SCOUG-Help: config.sys
>
> Butch,
>
> If you do not have a reliable way to back up your important
> system files
> (like the CONFIG.SYS and OS2.INI files), attached please find 4
> scripts
> that you can use to help you with that task.
>
> Use the REXX program, BUTCH.CMD, to copy (back up) the following
> files:
>
> 1. CONFIG.SYS
> 2. ...,\Desktop\*.*
> 3. ...,\OS2\OS2.INI
> 4. ...,\OS2\OS2SYS.INI
> 5. ...,\OS2\DLL\SCENTER.CFG
> 6. ...,\OS2\DLL\DOCK*.CFG
>
> It will copy up to 20 generations of these files. It creates the
> following folders on your boot drive (I believe your boot drive is
> "C:\", right?):
>
> C:\BUTCH
> C:\BUTCH\Desktop
> C:\BUTCH\Desktop\Backup_01
> C:\BUTCH\Desktop\Backup_02
> C:\BUTCH\Desktop\Backup_03
> ...,
> ...,
> C:\BUTCH\Desktop\Backup_20
>
> The most recent, backed up generation will be in
> "C:\BUTCH\Desktop\Backup_01". After that, the next recent will be
> in
> "C:\BUTCH\Desktop\Backup_02", etc., etc.
>
> When you run the program, it erases everything in
> "C:\BUTCH\Desktop\Backup_20" and moves everything else down one.
> "C:\BUTCH\Desktop\Backup_19" becames "C:\BUTCH\Desktop\Backup_20",
> "C:\BUTCH\Desktop\Backup_18" becomes
> "C:\BUTCH\Desktop\Backup_19", etc.
> Finally, the backup that it makes is stored in
> "C:\BUTCH\Desktop\Backup_01".
>
> You MUST place BUTCH.CMD somewhere on your boot partition
> (anywhere on
> the C:\ drive). DO NOT place it on D:\, or E:\, etc. If you do,
> it will
> NOT work.
>
> Next, the 3 programs, BUTCH1.CMD, BUTCH2.CMD and BUTCH3.CMD, are
> OS/2
> batch file programs. Use them to restore the following files to
> your
> system:
>
> Batch Program Restore Files
> BUTCH1.CMD OS2.INI, OS2SYS.INI
>
> BUTCH2.CMD CONFIG.SYS
>
> BUTCH3.CMD Desktop\*.*
>
> These 3 programs are designed to use from a floppy diskette. The
> idea is
> that you cannot boot your system, because of some problem with
> these
> files. Or, perhaps you can boot, but your desktop is wiped out/in
> error,
> etc. If so, you boot up a minimal OS/2 system, using your OS/2
> utility
> diskettes (I assume that you do not have an OS/2 maintenance
> partition
> on your system and that you boot from floppies, when you have
> trouble).
>
> So therefore, you boot up a minimal OS/2 system from the utility
> diskettes. Then, you switch to the diskette that has BUTCH1.CMD,
> BUTCH2.CMD and BUTCH3.CMD. Using these you restore from the
> archived
> generations that you made with BUTCH.CMD. For example, suppose
> you want
> to restore your CONFIG.SYS file, saved in
> C:\BUTCH\Desktop\Backup_03. If
> so, you type and enter "BUTCH2.CMD 03" on the commandline
> (without the
> quotes). If you want to restore the desktop files saved in
> C:\BUTCH\Desktop\Backup_19, you type and enter "BUTCH3.CMD 19" on
> the
> commandline. If you want to restore the OS2.INI and OS2SYS.INI
> files,
> stored on C:\BUTCH\Desktop\Backup_05, you type and enter
> "BUTCH1.CMD
> 05".
>
> If you use a maintenance partition, you can save these 3 programs,
> BUTCH1.CMD, BUTCH2.CMD and BUTCH3.CMD anywhere on that partition
> and use
> them from there. You have to go to an OS/2 commandline to use
> them. Use
> a full screen commandline, not a windowed commandline. These 3
> programs
> are batch file programs, not REXX programs. If you are using the
> utility
> diskettes, REXX will not be available in your minimal OS/2
> system. But
> batch programs will work there. That's why they are batch
> programs!
>
> Well, you can use these programs, or not! It's your choice.
> Notice that
> I did not write a batch program to restore the
> ...,\OS2\DLL\SCENTER.CFG
> and ..,\OS2\DLL\DOCK*.CFG files. You can do that, if you like,
> using the
> BUTCH1.CMD, BUTCH2.CMD and BUTCH3.CMD examples.
>
> HCM
> __________________________________________________________________
> ___________
>
> Steven Levine wrote:
> >
> > =====================================================
> > 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 <3DA82A7F.B7E6C8DC@attglobal.net>, on 10/12/02
> > at 05:58 AM, Harry Chris Motin said:
> >
> > >the Main Menu. Learn something NEW everyday. However, it is
> essential, I
> > >believe, that Butch load the CONFIG.SYS into an Editor without
> any word
> > >wrapping!!!! He wants to see each and every line as a single
> line, so
> > >that he knows where each one begins (at the far left-hand
> side) and where
> > >it ends (at the end of that line on the right).
> >
> > This I agree with, although since almost all editors will wrap
> lines, I
> > would say that Butch needs to be sure that word wrapping is
> turned off.
> >
> > FWIW, with EPM, there's no way to prevent word wrapping at
> character 1699.
> > Fortunately, I've never seen a config.sys line this long. I
> don't know
> > what E's line length limit is.
> >
> > >Steven, I assume you also mean to copy the, CONFIG.SYS,
> OS2.INI and
> > >OS2SYS.INI files, too. Unless Butch has a backup program,
> perhaps the
> >
> > These are included. To be able to fully restore the Desktop
> you need
> > copies of:
> >
> > os2.ini
> > os2sys.ini
> > config.sys
> > scenter.cfg
> > dock*.cfg
> >
> > as a bare minumum. It can be useful to back up additional
> files, even
> > though they are not part of the Desktop, per se. Svobi's list
> is a pretty
> > good one. I capture even more using Unimaint's Supplemental
> Backup. The
> > file compression is useful and the files retain their original
> names.
> > This make it easier to restore one or two, on demand.
> >
> > >easiest way for him to make a backup of ALL the essential
> files is to use
> > >XCOPY with the options to copy subdirectories, empty
> directories, hidden
> > >files, system files and read only files. That way he will make
> an exact
> > >copy of "C:\Desktop\..."
> >
> > True, but Unimaint does all this with less fuss, as does
> RoboSave.
> >
> > 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".
> >
> > =====================================================
>
> Attachment #1 : BUTCH.CMD
> Content type : text/plain
> The attachment is located at the bottom of the message.
>
> Attachment #2 : BUTCH1.CMD
> Content type : text/plain
> The attachment is located at the bottom of the message.
>
> Attachment #3 : BUTCH2.CMD
> Content type : text/plain
> The attachment is located at the bottom of the message.
>
> Attachment #4 : BUTCH3.CMD
> Content type : text/plain
> The attachment is located at the bottom of the message.
> - BUTCH.CMD - BUTCH1.CMD - BUTCH2.CMD - BUTCH3.CMD
>
> ************************************************************
> *** >>> Say NO to HTML in Mail and News <<< ***
> *** ++++++++++++++++++++++++++++++++++++++++++++++++ ***
> *** >>> AGAINST TERROR +++ AGAINST WAR <<< ***
> ************************************************************
>
> ------------------------------------------------------------------------
> Name: BUTCH.CMD
> BUTCH.CMD Type: Plain Text (text/plain)
> Encoding: 8bit
> Description:
>
> Name: BUTCH1.CMD
> BUTCH1.CMD Type: Plain Text (text/plain)
> Encoding: 8bit
> Description:
>
> Name: BUTCH2.CMD
> BUTCH2.CMD Type: Plain Text (text/plain)
> Encoding: 8bit
> Description:
>
> Name: BUTCH3.CMD
> BUTCH3.CMD Type: Plain Text (text/plain)
> Encoding: 8bit
> Description:

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

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

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

Return to [ 14 | October | 2002 ]

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.