The following issues have been resolved in LiveUpdate 3 for Symantec Ghost Solution Suite 2.5 (build 2165):

• Resolved a problem with the check image functionality when used on an image with an image all partition. Previously this could result in data being written to first drive.

• Resolved a problem with using GDisk32 to wipe all drives attached to a computer, but excluding USB or firewire drives. Previously this could result in the USB or firewire drive being erased also.

• Added support for cloning EXT2/3 volumes which are formatted with large inodes.

• Resolved a problem which prevented Firewire / IEEE 1394 drives being used with Ghost under DOS.

• Resolved a problem where -lockinfo from ghost.exe showed different information than -lockinfo for ghost32.exe.

• Resolved a problem where the image file description could be truncated.

• Resolved a problem where editing a Linux image with GhostExplorer could corrupt the image in some cases.

• Resolved a problem where GhostExplorer couldn't handle linux partitions created by the DCL tools.

• Resolved a GhostExplorer error when adding empty folders.

The following issues have been resolved in LiveUpdate 2 for Symantec Ghost Solution Suite 2.5 (build 2141):

• Resolved a problem where some machines could fail to boot after entering a Virtual Partition, and a manual interventionwith a CD/DVD or USB boot disk would be necessary to restore it.

• Resolved an issue where under some conditions Ghost Boot Partition (GBP) could become unusable, causing system to fallback to using a VP instead.

• Improved client’s server discovery for Console operations, and resolved an issue where client sometimes failed to contact the WINS server on networks where multicast discovery is not possible.

• Resolved a few issues around Ghost’s handling of metadata for EXT3 filesystems, which could result in “fsck” reporting errors on the restored image (such as superblock write time and i_blocks count inconsistencies).

• Changed the way that additional user files are added to USB/CD media by Ghost Boot Wizard when building WinPE-based packages, placing them outside of the WinPE WIM file (previously it would pack them into the WIM file, increasing its size, and causing problems loading on machines without sufficient RAM to load it in full).

• Resolved a problem which prevented RIS packages created by Ghost Boot Wizard (GBW) from booting on the target client machines.

• Resolved an issue where Static IP configuration in Ghost Boot Wizard (GBW) was not being applied to the WinPE-based Ghost Boot Partition (GBP) packages, continuing using DHCP when booted.

• Resolved a problem where on some versions of Windows (where Shell API does not return correct common folder paths for certain locales) Ghost Boot Wizard (GBW) could fail to locate its data files (e.g. drivers, WinPE packages, etc.)

• Resolved an issue where floppy media created by Ghost Boot Wizard (GBW) would  sometimes end up containing corrupted files.

• Updated drive mapping code in WinPE pre-OS (“/setosdrives”) to restore driver letters for CD and USB devices.

• Better support for various newer hardware with the updated Thinstation Linux pre-OS image (kernel 2.6.25.13, read/write TFS support).

• Resolved “low virtual memory” errors when running Ghost under custom WinPE v1.6.

• Resolved an issue where after Ghost image restore unable to use the Windows Recovery Console until it is re-installed (i.e. “winnt32 /cmdcons”).

• Resolved a problem where the DOS-based client (ngctdos) could inadvertently downgrade the MBR to older version after leaving the Virtual Partition, which would not be able to support some newer hardware.

• Improved DeployAnywhere™ executable size and processing speed.

• Updated several WinPE drivers to newer version (Broadcom 570x XP/Vista, Intel Pro 1000 Vista - previous driver did not work on new IBM machines).

• Resolved a problem where Ghost would fail with error “651, Unable to locate next span”, when the specified source or destination file path is 3 characters or less (working if specified through an equivalent path being 4 or more characters long).

The following issues have been resolved in LiveUpdate 1 for Symantec Ghost Solution Suite 2.5 (build 2125):

• Resolved an issue where refreshing WinPE or editing the drivers included by WinPE, could prevent DeployAnywhere™ from operating.

• Ghost Boot Wizard now warns the user if MSXML6 is not installed. This is a prerequisite for build WinPE boot packages.

• Resolved a problem which could prevent a network boot floppy created by Ghost Boot Wizard from booting when using the UNDI driver.

• Resolved a problem which could cause error code 0x2 or 0x103 when adding drivers to WinPE.

• Resolved a problem with WinPE 1-click virtual partitions which could sometimes cause the error “no formatted partitions were found on the source drive” when running Ghost.

• Ghost Boot Wizard now warns the user when overwriting an existing driver with a new version.

How to resolve "Drivers could not be found in the PreOS for the following devices"

The product support tab at http://www.symantec.com/business/theme.jsp?themeid... says that Windows 7 support will be delivered in Q1 2010 via LiveUpdate 5.  Has a LiveUpdate 4 been released?  We don't see it advertised in LiveUpdate. Do we have to call to obtain it? Thanks in advance for any replies!

LiveUpdate 4 was nothing more than a combined roll-up of the previous three LiveUpdates, to deal with the user confusion that surrounded the fact that the previous three LUs had to be downloaded and applied in sequence, but was not intended to contain any additional updates beyond those already released. The LiveUpdate package for this was produced and QAed for release but did not apparently end up going live for download (for reasons not under our control at Ghost R&D).

Since we did produce an LU4 package, and go through all the associated process to get it released, it was conceivable that it might end up being released - whether supplied to customers by technical support, or some other factor - and so the next update was designated LU5 as a result.