Question : Adding a modified sysprep.inf file to a Ghost image via Ghost Explorer not functioning properly

I've been using Symantec's Ghost product for years now and have been looking forward for the version that has a functioning ability to add files to an NTFS filesystem image.  That day seems to be here, but I am experiencing odd behavior that has me a bit worried.

I have one image that I use for all of my systems, Dell GX270, GX280, D600, D610, HP Compaq NC6400, NW8440 etc etc..  I created the image this way off the bat using sysprep.  My company is moving to a new desktop standard in the coming months, and I figured this was the golden opportunity to take advantage of the latest version of ghost explorer 11 to edit the GHO file by adding the various drivers of the new system to my Temp/Drivers directory, and editing the oemPnPdriversPath to reflect the new drivers for this system.

I added the new drivers just fine, I was please to see them all in their respective directories with a simple right-click/Add procedure.  I extracted the Sysprep.inf, add all of the information I needed and peformed the very same add method.

That was the history, now here is the problem:
When I extract this very same sysprep.inf file that I added to test that it was indeed there, the file is missing all important information.  The only info that remains in the file is the middle of it, which is the long list of the -BMSD command (Mass Storage Section).  It is apparent that this feature is broken and Live update says I am up to date...  I'm concerned that any files I've added to this image are possibly corrupt/not in their entirety.

Has anyone experienced similar problems, know why this is happening, and/or have a resolution?  This seems like a very neat feature that is included as part of the programs functionality that does not seem to work.

Answer : Adding a modified sysprep.inf file to a Ghost image via Ghost Explorer not functioning properly

Sorry guys, I had contacted Symantec regarding this a while ago and found that they did indeed fix this issue and they gave me a new unreleased build with the fix.  This only effects files that you are extracting, when you input files into your image via ghost explorer they should be fine, but if you were to immediately extract that same file it would appear inaccurate.  So for my purpose there really was no problem as the files I were putting in were fine.