| |
| ivBox1000
Fireware update |
| ivBox 2007/05/22 update |
ŔɮצWşŮ: ivBox_ECN_20070522
ivBox firmware upgrade procedure:
1. De-compress the file ˇu ivBox_ECN_20070522.zip ˇv , you would get the folder ˇu ISU V1.05 Program ˇv
2. Using PING command under DOS environment and confirm the acknowledgement from the IP address of specific ivBox.
3. Using TextEdit or equivalent editor modify the IP address on file ˇu startup.txt ˇv in ˇu ISU V1.05 Program ˇv . Make sure ˇ@the IP address is same as the specific ivBox on setp 2).
4. Executive the program ˇu Isu-oct5.exe ˇv , you would find the field of Current Drive Version is ˇu 1.43 ˇv . If it's not ˇu 1.43 ˇ@ˇ@ˇv , you should stop the procedure, and contact with your vender.
5. Press ˇu Browser ˇv button, select the file ˇu Isu.HEX ˇv in the folder ˇu V1.43-V1.51 ˇv .
6. Press ˇu upgrade ˇv button, wait the progress bar from 0% to 100%, and show the message dialog box ˇu upgrade ˇ@complete! ˇv . Please patience, this step will take about 6 minutes or more.
7. Exit the ISU program and reset the ivBox.
8. Using PING command to check its activate of specific ivBox. Executive the ISU program to verify the Current Drive ˇ@Version is 1.51. |
| ivBox 2006/11/08 update |
|
ŔɮצWşŮ: ivBox_ECN_20061108
ivBox firmware upgrade procedure:
1. De-compress the file ˇuivBox_ECN_20061108.zipˇv, you would get the folder ˇuISU V1.05 Programˇv.
2. Using PING command under DOS environment and confirm the acknowledgement from the IP address of specific ivBox.
3. Using TextEdit or equivalent editor modify the IP address on file ˇustartup.txtˇv in ˇuISU V1.05 Programˇv. Make sure the IP address is same as the specific ivBox on setp 2).
4. Executive the program ˇuIsu-oct5.exeˇv, you would find the field of Current Drive Version is ˇu1.42ˇv. If itˇzs not ˇu1.42ˇv, you should stop the procedure, and contact with your vender.
5. Press ˇuBrowserˇv button, select the file ˇuIsu.HEXˇv in the folder ˇuV1.42-V1.43ˇv.
6. Press ˇuupgradeˇv button, wait the progress bar from 0% to 100%, and show the message dialog box ˇuupgrade complete!ˇv. Please patience, this step will take about 6 minutes or more.
7. Exit the ISU program and reset the ivBox.
8. Using PING command to check its activate of specific ivBox. Executive the ISU program to verify the Current Drive Version is 1.43.
Client Applications upgrade procedure:
1. Please reference the webpage http://www.innovationuniverse.com/english/htm/driver-ivbox-update-2.htm
2. Check the version number of Client Applications, including: OV Management tool, Rule Management Tool and Alert Console.
3. If the version number is equal or grater then 3.0.1.44100, no need to upgrade.
4. If the version number is 3.0.1.42xxx, you should execute the ˇu3.0.1.44010_Patch_QA1ˇv before next step.
5. Execute the ˇuHotfix-3.0.1.44140_QA2ˇv, to upgrade all Client Applications.
6. Restart the computer what you installed the Client Applications in it. Verify the version number of Client Applications. |
| ivBox 2006/10/04 update |
 3.0.1.44010__QA2ˇ@ˇ@ˇ@ˇ@3.0.1.44020__QA1ˇ@ˇ@ˇ@Hotfix_3.0.1.44140_QA2ˇ@ˇ@ˇ@3.0.1.44010_patch_QA1ˇ@ˇ@ˇ@3.0.1.44100_hotfix_QA1ˇ@ˇ@ˇ@Hotfix_3.0.1.44150_QA1
Keep NEWEST release of your OV applications
ˇ@ˇ@ˇ@A. Verify the current version of OV applications
ˇ@ˇ@ˇ@ˇ@1. Launch the application (OMT, RMT and/or Alert Console)
ˇ@ˇ@ˇ@ˇ@2. Pull the HELP->ABOUT at the manual
ˇ@ˇ@ˇ@ˇ@3. Check the current version as the format 3.0.1 .44100
-
ˇ@4. The tail 5 digit is the release number of current version
B. Release number start 2 digit is less than 42, Please contact with your ivBox vender
C. Release number start with 42, should be upgrade to release 44000 first
ˇ@ 1. Stop all the service on the OMT
ˇ@ 2. Shut down all the applications of OV, including OMT, RMT & Alert Console.
ˇ@ 3. Launch the Patch program what named ˇuPatch_3.0_To_ 3.0.1 .batˇv of ˇu3.0.1.44010_Patch_QA 1.zipˇv
ˇ@ 4. Verify the version of OV applications, should be 3.0.1 .44000 for all
D. Upgrade 44000 to 44100
ˇ@ 1.Stop all the service on the OMT
ˇ@ 2. Shut down all the applications of OV, including OMT, RMT & Alert Console.
ˇ@ 3. Step-by-step launch the following Hotfix programs:
ˇ@ˇ@ˇuHotfix.batˇv of ˇu 3.0.1 .44010_Hotfix_QA 2.zipˇv
ˇ@ˇ@ˇuHotfix.batˇv of ˇu 3.0.1 .44020_Hotfix_QA 1.zipˇv
ˇ@ˇ@ˇuHotfix.batˇv of ˇu 3.0.1 .44100_Hotfix_QA 1.zipˇv
ˇ@ 4. Verify the version of OV applications, should be:
ˇ@ˇ@OMT 3.0.1 .44070
ˇ@ˇ@RMT 3.0.1 .44100
ˇ@ˇ@Alert Console 3.0.1 .44070
E. Upgrade 44100 to 44140
ˇ@ 1. Stop all the service on the OMT
ˇ@ 2. Shut down all the applications of OV, including OMT, RMT & Alert Console.
ˇ@ 3. Launch the Hotfix programs named ˇuHotfix.batˇv of ˇu 3.0.1 .441400_Hotfix_QA 2.zipˇv
ˇ@ 4. Verify the version of OV applications, should be:
ˇ@ˇ@OMT 3.0.1 .44130
ˇ@ˇ@RMT 3.0.1 .44140
ˇ@ˇ@Alert Console 3.0.1 .44110
F. If the current version/release is equal or higher than 3.0.1 .44140,
ˇ@Congratulation, you are under the NEWEST situation, nothing need to do.
|
|
