1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Previously installed software will NOT reinstall!

Discussion in 'Legacy Windows' started by Graham Newey, 2005/08/31.

  1. 2005/09/09
    BillyBob Lifetime Subscription

    BillyBob Inactive

    Joined:
    2002/01/07
    Messages:
    6,048
    Likes Received:
    0
    The RB00x.cab files are located in the C:\Windows\Sysbckup folder.

    Windows keeps 5 of them.

    If you booted the machine this morning Windows made a RB005.cab file dated today. Or at least it should have.

    Now you made all of the changes, additions or corrections it is ALREADY out of date. And the four previous ones will be also.

    You should be able to delete it. Restart Windows and it will make a new one which will be up to date.

    That is one area where I have NEVER seen Win98 fail. I find it far more reliable than the Restore point ( which seems to have a mind of its own ) in XP.

    Or if you wish you can wait till tomorrow and let it make one of its own. Then delete the other four.

    After doing all the work you have I myself would delete all of them. But I am more familiar with it as I have been doing it since 98 was installed.

    But it would still be a good idea to check and see that they are getting made. And if they are not then check to be sure ScanRegistry is loading at startup. But if they are there then you should be OK.

    Yes. They are SUPPOSED to be. But the machine MUST BE at least restarted one per day. I forgot one time and left the machine on over night.And then ckecked and one was not made for the day. A restart took care of that.

    But you as the User should check to make sure they are.

    BillyBob
     
  2. 2005/09/09
    goddez1

    goddez1 Inactive

    Joined:
    2002/01/12
    Messages:
    2,975
    Likes Received:
    49
    Hi Grahmn,
    Great news indeed! Glad Canon support was so helpful and your problems have been taken care of by the new CD.

    As for scanreg and the registry backups (referred to as rb***.cabs) perhaps this will help. I think you previously expressed little or no understanding of restoring the registry (to a time that predates a problem) using scanreg /restore.
    See:http://support.microsoft.com/defaul...kb;EN-US;183887
    SUMMARY
    Description of the Windows Registry Checker Tool (Scanreg.exe)
    When you start your computer successfully, the Windows Registry Checker tool (Scanreg.exe) creates a backup of system files and registry configuration information (including user account information, protocol bindings, software program settings, and user preferences) once daily. Files that Windows Registry Checker backs up include System.dat, User.dat, System.ini, and Win.ini. This article describes the Windows Registry Checker tool. These backups will be stored in the \windows\sysbackup folder as rb***.cab files where *** is a number between 001 and 005 (5 days/dated backups are kept by default). If you have a registry, a bootup, or a corrupted/missing (monitored) system file problem, all you normally need to do is to boot to a DOS prompt, type and and enter the command scanreg /restore and then choose from the 5 available backups, one that predates the problem.

    This information is also handy: "how to add additional critical files via sredit ":
    http://www.wintrouble.net/discus/messages/53/137.html This is very easy to use. With SREdit.Exe, you can make the following changes to the way that ScanReg runs:
    You can specify the directory or directories where ScanReg stores its backup copies of the Registry. You can set the maximum number of backup copies allowed as well as select additional system files (such as AutoExec.Bat, Config.Sys, or Msdos.sys) to be backed up.


    A perk of having these backups is....
    You can extract individual files from these, either manually yourself (simple locate the *.cabs and double click on them to open) or via system file checker (sfc.exe). This can also be done using dos commands at the c prompt, should you find yourself having to do this.

    If they are old (such as may be the case for those that shutdown their systems infrequently) and your relatively certain you have no current problems, you can use registry checker and make fresh a backup or two.
    From the start button>runline type scanregw.exe and hit enter. Then check the folder where the backups are stored and make sure there is a new backup. At least you will have an updated backup of the current monitored system files and another alternative for restoring corrupted or missing system files or restoring registry settings. While not an ideal form of backup, this can be handy (in many cases) and in a pinch will pull your tush out of a bind. It's saved mine on occasion.

    Things to be aware of, consider, and learn how to do........
    * "when to use it ".
    * "what you may risk losing should the backups predate any new installations or updates" you have done.
    *what you risk restoring should these hold viral/malware or corrupt files.
    *When they should be dumped or deleted and new current ones made.


    The archives of past posts have plenty more information if your interested. BillyBob is stressing the importance of keeping these backups in mind, making sure your cleaning the older ones out and when this should be done plus making new ones and when this should be done, along with checking to make sure they are being made in the first place.

    You can make fresh ones anytime you choose by:
    From the start button>runline type scanregw.exe and hit enter.

    If your worried or unsure about over writing the current *.cabs you have, you can copy these and store them in another folder of your choosing (made by you). You'll have, for lack of a better description, a backup of the backups. There are steps that can be taken to replace or exchange these should the need ever arise. On a personal note, I use to do this but have never had an occasion where I've had to use the older backups. Through time, possibly complacency and a false sense of needlessness I have stopped doing this (meaning the copying and pasting of backups of my backups). I do however clean out the older cabs and manually make new ones, particularly after any virus/malware/adware cleanups or as part of my regular maintenance routine, before installing new apps or updates and after, (once I'm sure everything is okay) and before any major registry editing and "goofing off in ", exploration tweaks, changes or deletions.

    For some this would seem like an added nusiance or another task to worry about doing but the benefits and security far out way any nusiance. Any of these procedures only take seconds to do and if made often enough become a habit done automatically. They will save your tooshie on occasion.
     
    Last edited: 2005/09/10

  3. to hide this advert.

  4. 2005/09/12
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Been away for the weekend - glad to return to news of your success :)
     
  5. 2005/09/12
    BillyBob Lifetime Subscription

    BillyBob Inactive

    Joined:
    2002/01/07
    Messages:
    6,048
    Likes Received:
    0
    Thank you goddez1

    I had apparently overlooked/forgotten about this post untll today.

    BillyBob
     
  6. 2005/09/16
    Graham Newey

    Graham Newey Inactive Thread Starter

    Joined:
    2002/01/08
    Messages:
    61
    Likes Received:
    0
    Previously installed software will NOT reinstall!!

    Just a final note of thanks to you all for your help, particularly BillyBob and goddez1.

    I am now fast becoming an expert on the use of the "System File Checker" and "Windows Registry Checker" tools----NOT!!!!!

    And all I wanted to do was frame a couple of photos!!!

    Thanks again,

    Regards,

    Graham
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.