Blue Iris

Title: GetBI5v2.CMD (version 2.0)


What is GetBI5v2.CMD?
========================
GetBI5v2.CMD is a Windows batch file script that downloads the latest version Blue Iris 5's full version installer (Blueiris.exe), 32-bit Update (Update32.exe) and 64-bit Update (Update64.exe) from blueirissoftware.com and renames each one to include the version as part of the filename. Example:

Downloads ....... Renames to ................. Description
Blueiris.exe ...... Blueiris_v5.0.0.59.exe .... Full version installer
Update32.exe ... Update32_v5.0.0.59.exe .. Update for Blue Iris 5 32-bit
Update64.exe ... Update64_v5.0.0.59.exe .. Update for Blue Iris 5 64-bit

Since GetBI5v2.CMD can only determine the version after downloading each file, I only recommend running this batch file manually when you know there is a new version available.

The purpose of this batch file is help you download and maintain an archive of older versions of Blue Iris 5 installations and update files in the event that you need to roll back your current version of Blue Iris 5 to an earlier version.

How do I roll back Blue Iris 5 to an older version?

Scenario 1:
----------
In order to roll back your version to an earlier version, you do not need to re-install the full version of Blue Iris 5. You just need to find an early version of Update64_v5.xx.xx.xx.exe or Update32_v5.xx.xx.xx.exe and double click on it. In most cases, this is all you need to do to roll back Blue Iris 5 to an earlier version.

Scenario 2:
----------
This method adds restoring Blue Iris 5 settings from a previous version to the process. I created a batch file called BackupBI5v2.CMD to backup Blue Iris 5 settings using REGEDIT to a REG file that includes the version as part of the filename in the format of "Blueiris_v5.xx.xx.xx.reg". Double clicking on the "Blueiris_v5.xx.xx.xx.reg" file would write Blue Iris 5 settings for that version back to the Windows registry.

You can download BackupBI5v2.zip from https://blueirissoftware.com/forum/view ... 2a4719fe74.

Quick Steps

1. Navigate to the drive and folder location where you are storing your previous versions and backups of Blue Iris 5.
2. Double click on the Blueiris_v5.xx.xx.xx.reg file for the previous version of Blue Iris 5.
3. Double click on the Update64_v5.xx.xx.xx.exe or Update32_v5.xx.xx.xx.exe file for the previous version of Blue Iris 5.


Requirements
============
The Batch file GetBI5v2.CMD uses CURL to download files from http://blueirissoftware.com. If your computer has Windows 10 version 1803 or higher, then the OS now comes with a copy of CURL. If you have a different OS, then you will need to download CURL from:

https://curl.haxx.se/windows/

and copy CURL.EXE to C:\Windows\System32


Compatibility
=============
+ Windows 7
+ Windows 8/8.1
+ Windows 10


Download GetBI5v2.zip or previous versions
=====================================
* GetBI5v2.zip (Latest version) from https://drive.google.com/open?id=1Aa1B1 ... st--DZAks8


How to install GetBI5v2.CMD
=========================
1. Unzip "GetBI5v2.zip" to C:\. This will unpack GetBI5v2.cmd and "README for GetBI5v2.txt" files to following directory:

C:\Bat

FYI: If you want to put GetBI5v2.cmd in a different folder, you can.

2. To configure where you want GetBI5v2.cmd to store its downloads, open the batch file called GetBI5v2.CMD with notepad and just change the following line:

SET DEST=%USERPROFILE%\Desktop

3. Download and install CURL (If you're not running Windows 10 v1803 or higher)

a) Download CURL from https://curl.haxx.se/windows/
b) Copy CURL.EXE to C:\Windows\System32

Wow ! That is some good information ! Thanks for that

Why is the exported reg file exactly 1/2 the size of the manually exported perspective key ? maybe the regedit editor version ?

Tinman wrote: ↑Fri Jul 19, 2019 7:11 pm Why is the exported reg file exactly 1/2 the size of the manually exported perspective key ? maybe the regedit editor version ?

Sort of, we are both using the same version of REGEDIT, version 5.

However, when I used REGEDIT and specified /E for export and then specified :A, REGEDIT used an older version format because it was exporting the specified registry key and values in ANSI mode and not Unicode. As a result, the REG file ended up being half the size. I originally did this because another batch utility that I wrote could not handle the Unicode and saw double of every character in the REGEDIT export file, like:

HHEELLOO TTHHEERREE

For better compatibility for the future, I decided to change BackupBI5v2.CMD so the REGEDIT export method included the Unicode information in the REG file, which is the default format. I uploaded a new version to my Google drive. Thanks for pointing this out.

I basically edited BackupBI5v2.CMD and changed the line:

From: REGEDIT /E:A "%DEST%\%PROG%.reg" "%KEY%"
To: REGEDIT /E "%DEST%\%PROG%.reg" "%KEY%"

well it works fine...I did a full restore of my demo machine registry and compared it to a manual export and it matched perfectly. Was just curious as why and you have answered my question ! Thank You