Ghost Virtual Directory
Hi All,
I'm having a problem with the "One Click Virtual Partition" image from within GBW .
I have tried creating the image as MS DOS and PC DOS, same failure.
The client it is booting up from is a new DELL T1500 with Broadcom Ndis driver that connects fine.
When the client runs the shortcut it reboots and starts the virtual floppy image, NIC driver loads fine etc but when it comes to the run
Ghost.exe it bombs out with the following message:
Abort!
Exiting due to a signal SIGABRT
Page fault at eip=0053f463, error=0006
(register details omitted here)
program=A:\ghost\ghost.exe
The same parameters run fine and connect to the Ghost Cast Server when booting from CD or USB and connecting to a Ghostcast session, I don't know why
the virtual partition image fails.
I have run in updates for GSS 2.5 b2125, b2141 and b2165. No other updates are available.
I would really like to get this to work as it would be a lot more effective for us to use this method of delivery from with login scripts rather than go out and update via bootable CDs/USB.
Any help would be appreciated,
Thanks
AlanS
PXE or different boot environment
AlanS,
It sounds like the one-click virtual partition may not work in that environment, for whatever reason. I would recommend a PXE setup to deliver the boot media. This would allow you to boot a machine without having to deal with physical media by choosing the Network Boot option in the boot menu. Here are instructions for setting this up:
How to use the 3Com Boot Services (and SolarWinds TFTP) with Symantec Ghost Solution Suite 2.5 using WinPE
http://service1.symantec.com/SUPPORT/on-technology.nsf/docid/2009060307534660
PXE is a very reliable and well-tested way to eliminate the need for physical boot media, and I highly recommend this.
Alternately, you could try a WinPE-based or Linux-based one-click virtual partition. Based on where it is failing, a different boot environment may work.
Thank you,
Randy
The fact that it bails out
The fact that it bails out right during program load indicates something really bad. It is possible that manufacture BIOS is not 100% compatible with the old method (DOS) of accessing memory or it may be due to 3rd party boot software installed.
In either case as Randall suggested you can try using Winpe one-click VP which works slightly different and quite likely will not have same issue.
The PE virtual image works a
The PE virtual image works a treat!
Thanks guys.
Excellent
Excellent! I'm glad that worked. WinPE is an excellent PreOS and works well with a variety of hardware.
Would you like to reply?
Login or Register to post your comment.