IBM ImageUltra Builder 2.01 Web Update 5 -------------------------------------------------------------------------- Overview -------------------------------------------------------------------------- This package will install the IBM ImageUltra Builder 2.01 Web Update 5 software on your system. In addition to the new fixes contained in Web Update 5, this package also includes all previous ImageUltra Builder 2.01 Web Updates (#1, #2, #3 and #4). This package requires that you have IBM ImageUltra Builder 2.01 and optionally one or more of the previous Web Updates already installed on your system. -------------------------------------------------------------------------- Downloading the update -------------------------------------------------------------------------- 1. Click the file link to download the file from the Web page. 2. When prompted, select a drive and directory in which to save the downloaded file. -------------------------------------------------------------------------- Installing the update -------------------------------------------------------------------------- 1. Click Start, select Find or Search, then click Files or Folders. 2. Type iubupdate1b8.exe in the search field, then click Find Now. This will locate the iubupdate1b8.exe file you just downloaded. 3. Double-click the iubupdate1b8.exe icon. 4. Click Next. Read the license agreement. 5. Click Next if you accept the terms in the license agreement. 6. Follow the instructions to complete the installation. -------------------------------------------------------------------------- Problems fixed by this update -------------------------------------------------------------------------- Web Update 5 fixes ================== 1. Fix problem promoting a map to gold when all modules inside it are gold (map was not promoted). 2. IUWork modules do not work in Windows 2000 3. Fix the problem when installing the full version of ImageUltra Builder on top of an evaluation version does not upgrade the repository to the full version. -------------------------------------------------------------------------- Problems fixed by previous updates that are also included in this update: -------------------------------------------------------------------------- Web Update 1 fixes ================== 1. The installation order of Service Partition modules (modules with Target Partition set to "Service") are not correct even if the install sequence is being set in the basemap. 2. Only one PreMenu or PostMenu utility module is getting executed regardless of how many PreMenu and PostMenu modules are included in the basemap. 3. Adding filters to Customer First Boot modules causes the first boot hook to fail with an error message. 4. When a module build is cancelled or encounters an error, an empty dialog box is displayed with the title "Would you like to recopy the image file %s". The only option is to select Done. 5. ImageUltra Builder generates a program failure (GPF) when trying to unset a menu item as a System Menu. 6. ImageUltra Builder does not allow different parameters on the multiple copies of the same filter module under a menu item. If more than one of the same filter module are added to a menu item, then whenever different parameters are applied to one filter module, they are also applied to the other module. 7. ImageUltra Builder allows sorting of "Service Partition" modules as customer first boot modules, even though the Service Partition modules do not install during customer first boot. 8. If the IUB deploy diskette is not used to deploy images over the network, "file not found" errors are seen and problems with displaying the "deploy is done" screen occurs. Also, if the deploy process must resize the Service Partition, the process may halt. However, if you press Enter, the process continues as normal. 9. When using an IUB network deploy diskette, a "Drive Not Ready" error message may appear while connecting to the network. This occurs if you are using a Thinkpad with an empty USB floppy drive and a bootable network deploy CD. 10. The built-in ImageUltra filter modules "File Exists" and "File Not Exists" may hang system if the /a switch is used. 11. Distribution CDs attempt to connect to the network unnecessarily. 12. When copying and pasting multiple modules (using Ctrl-C and Ctrl-V) multiple times rapidly, an error message is displayed indicating “Unable to create file” - “This file already exists”. This is message is due to 2 threads creating concurrently trying to create a module with the same name. 13. When trying to build a module from within a container, ImageUltra Builder causes a program failure (GPF). 14. When there are more than 10 UserData fields, the values do not always get entered or prompted for correctly. Also, using the WRITEINI tool does not always retrieve the correct value. 15. When using the built-in ImageUltra Convert to NTFS module, sometimes the ImageUltra process will stop during Audit Boot or simply not convert the primary C partition to NTFS. 16. Maps lose their gold state when imported. 17. The module install sequence gets out of order when deleting a module from a map that is specified in the install sequence. 18. The subdirectory structure for Base OS and Base OS Partitioning modules is not saved. When creating a Base OS or Base OS Partitioning module, if any files exist in subdirectories under the source directory, those subdirectories and files will not be stored in the module (and will not be restored in the image). 19. If I have two filters (of the same type) on a menu item and edit the parameters for each one, it works opposite from what you expect. If I modify one and then modify the other, it applies the changes to the one I already changed. 20. Large maps conversions can take a long time (during the deploy process). 21. Menu Preview (DOE) goes to full screen when under WinXP (but not under Windows 2000). 22. When performing network installs, there is no way to set the domain that the user logs onto to during the install. As a result, network installs do not work where a server is used that requires the domain name upon login. 23. Import source path from module files (.CRI). 24. Do not allow a map to be appear in the netsync table more than once as the deployed map. Web Update 2 fixes ================== 1. Performance problems refreshing views when folders contain more than a thousand module. Web Update 3 fixes ================== 1. ImageUltra Builder received database errors after running for extended periods of time and required the application to be closed and re-opened to access the repository. This problem only occurred when accessing a network based repository and the network connection was unstable (occasionally interrupted). 2. Problems deploying ImageUltra images to systems with "Rapid Restore 4.0", also known as "IBM Rescue and Recovery with Rapid Restore 4.0". ******************************************************** *** IMPORTANT NOTE FOR RAPID RESTORE ULTRA 3.0 USERS *** ******************************************************** If you are deploying Rapid Restore Ultra 3.0 using ImageUltra Builder, you must do the following: - Open each base map that includes your RAPID RESTORE ULTRA 3.0 module. - In each map, add the new module "ImageUltra 2.0 - Boot Manager" to the root of your map. - Save your map. - Now, you can beginning deploying that map again. ********************************************************* *** IMPORTANT NOTES FOR RAPID RESTORE ULTRA 4.0 USERS *** ********************************************************* - If you are deploying Rapid Restore Ultra 4.0 using ImageUltra Builder, make sure you do NOT include the "ImageUltra 2.0 - Boot Manager" module in any of your base maps that include your Rapid Restore Ultra 4.0 module. Doing so will cause your deploy and install process to fail. - Rapid Restore Ultra 4.0 will NOT function properly (backups will not work) when Rapid Restore Ultra 4.0 is deployed using ImageUltra Builder under the following conditions: - You are deploying to an IBM system with the IBM Rescue and Recovery environment in the service partition (as installed by manufacturing). - You are deploying using a service partition install (not using a direct network install). - The base map you are deploying has the "Delete all" image cleanup option. Web Update 4 fixes ================== 1. Update hardware detection (HIIT) to work with unicode INF files. 2. When deploying a delete-all image, the boot manager (BMGR) tries to boot to the service partition (which is not there), thus requiring a manual reboot. 3. When setting AutoLogonCount in the sysprep.inf, IUWORK does not log back in. 4. Application error occurs when importing Simplified Chinese images. 5. Fix 127 character limit on DOS commands. 6. Improve performance when comparing modules (to determine whether modules already in the service partition need updating from the repository). 7. Improve performance when converting maps during the deploy process. 8. Add additional logging to the stamp.log file. 9. Suppress "unsupported command" messages when deploying and installing. 10. When promoting a map or container, give the option to automatically promote all modules referenced by that map or container. 11. Make the properties dialogs larger to allow easier viewing of data. 12. Make sure map comments are imported. 13. Allow the user to manually add a DOMAIN setting in the PROFILE.INI of a deployt diskette so that when windows tries to re-connect to the network (during a network install) the DOMAIN setting will be used in the NET USE command. This is required for customers who use a Domain Controller to control user permissions. 14. When windows tries to re-connect to the network during a network install and the NET USE command is too long for SPAWN, then the NET USE command does not re-connect successfully. 15. When a user tries to deploy or restore a system that has gone into hibernation mode, then PowerQuest EasyRestore will fail. 16. Fix a problem using variables in a basemap. End of Document