Primo ramdisk 5.5 patch

Fix bug: Possible conflicts with certain drivers, especially intel wireless drivers, causing these drivers not working or BSOD. Fix bug: The GUI program possibly freezes while saving the image file or running other time-consuming operations. Fix bug: The modification time of an image file is not updated after the program saves the ramdisk content to the image file. Fix bug: Ramdisks did not save their content to image files at computer shutdown when Windows Fast Startup is enabled.

Fix bug: Some disk contents might not been saved to the image file in time during timing save. Allow to keep original copy when creating a junction point.

Reduce the real storage size of a flat image file. Version 5. Optimize: Computer reboot is not required for activating the program if no virtual disk is created. Optimize: Remove the warning mark in Windows device manager when program is in safe mode or expired. Multilingual version supports Japanese, Slovak and Indonesian. Minor tweaks. Support mounting the image files on-the-fly. Fix bug: Program hangs while saving the image file, if last saving was not successful.

Fix bug: Hybrid-disk may occupy lots of memory while copying large files in Windows Server R2. Fix bug: Slow memory allocation on Windows 8.

Fix bug: Cannot change custom folder names from lowercase to uppercase and vice versa. Minor improvements on user interface. Quick Load feature. Greatly improve performance on bit Windows. Fix bug: Input text gets truncated when typing beyond the combo box in the utilities dialog. Change behavior: When deleting a junction point, copy files back to the mount point by default.

Change behavior: When creating a new virtual disk, pre-set its disk size based on current available memory amount instead of a fixed value MB.

The associated image file will be also corrupted. Fix bug: image files or substance files cannot be loaded during computer boot-up if these files are located on external USB etc. Improve junction tool: Allow to automatically move files from mount points to target paths when creating junctions.

Allow to automatically copy files back from target paths to mount points when deleting junctions. Add history feature. Other minor improvements. This bug also corrupts the image file. For ESXi, booting from a USB key means the host will not create a scratch partition, even if the drive has ample capacity to support it. This behavior is called out in the installation and setup guide on page Click to access vsphere-esxi-vcenter-serverinstallation-setup-guide.

When installing on USB or SD devices, the installer attempts to allocate a scratch region on an available local disk or datastore. So while I can direct logs to a remote syslog server, patch installation can be problematic because the RAMDisk is not large enough to stage and install a rollup as large as ESXi 5.

The good news is you can create additional RAMDisk partitions if your host has sufficient memory available and use it for various purposes, such as manually staging and installing patches for the hypervisor. After the host rebooted, the RAMDisk was deleted which automated cleanup for me. Disclaimer: Follow these procedures at your own risk and responsibility!

There are multiple ways to update ESXi hosts. I am simply providing a method I came up with on my own. The output from the above command is used to select the desired profile to install from the depot. Get image profiles, select the one to install. You can correlate the build level to the patch level at the following KB:. Verify the RAMDisk no longer exists, which validates the cleanup was automatic since they do not persist across reboots.

Given the esxcli command can be executed via the vCLI e. PowerCLI , it should be possible to script these procedures to automate the process and make it more scalable!

You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email.