Ghost Solution Suite

 View Only
  • 1.  Internal Stack Overflow System Halted

    Posted Aug 31, 2015 04:13 PM

    Hello,

    I am trying to use GhostCast to install images on Toshiba Tec WillPOS C10s.  I have created a network boot disc using PC-DOS but when I boot with it I get an Internal Stack Overflow System Error after I select multicast.  I have tried using both PC-DOS and MS-DOS ghost boot drives and neither work for me.  Any thoughts on what my next step should be?

     

    Thank you,

    Matt



  • 2.  RE: Internal Stack Overflow System Halted

    Posted Sep 01, 2015 10:00 AM

    PC/MSDOS are unable to handle modern hardware such as SATA, so you might need to enable hard disk compatibility mode in the bios to have even half a chance of working with DOS.  You don't mention whether you are using Ghost 2.5 or the newly released Ghost 3.0 but both are really intended to work with WinPE rather than DOS, so your next step should be to create a WinPE boot environment to run Ghost under. The Ghost boot wizard will help you with that.



  • 3.  RE: Internal Stack Overflow System Halted

    Posted Sep 01, 2015 10:51 AM

    Hello EdT,

     

    Thanks for your response.  I am using GSS 2.5.  I had stopped using windows PE because I found it alot slower then PC/MSDOS to load on the machines.  I did create a new boot drive with Windows PE in this case and found that it hangs on "attempting to connect to ghost cast session".  I have tried multiple machines and they all behave the same.

     

    Thank you,

    Matt



  • 4.  RE: Internal Stack Overflow System Halted

    Posted Sep 01, 2015 02:33 PM

    After playing around with it some more I have noticed that when I boot with Windows PE is comes up with local IP address 127.0.0.1 even if I try to assign an IP instead of using DHCP.  I have made sure the correct drivers are included in the profile but it still isn't getting an IP.  Any thoughts?

     

    Matt



  • 5.  RE: Internal Stack Overflow System Halted
    Best Answer

    Posted Sep 01, 2015 03:41 PM

    The problem you are seeing is caused by the drivers not working for your NIC chipset. The version of WinPE used in Ghost 2.5 is based on the Vista kernel, so you need to add Vista 32 bit drivers - is this what you have done?  Also, I note reference to an Intel chipset. Which one is it?  The Intel 82579 is particularly difficult to get working drivers for, but searching the forum on 82579 should bring up past postings pointing to drivers that work with WinPE V2.  If it is a different Intel chipset, just Google on the chipset number and follow the postings. The i270 chipset has no Vista drivers but one of our users (Terry Bu) has published a couple of articles on how to get Ghost 2.5 working with WinPE 3, which requires Win 7 drivers.



  • 6.  RE: Internal Stack Overflow System Halted

    Posted Sep 02, 2015 09:17 AM

    Hello EdT,

    Thank you!  The Chipset is 82567V-3.  I was able to find the correct drivers (I think) with the help of one of your old posts and one from a symantec employee

    Testing procedure link:

    https://www-secure.symantec.com/connect/forums/symantec-ghost-1151-picking-loopback-address-optiplex780s

    Updated drivers link:

    https://www-secure.symantec.com/connect/downloads/latest-vista-version-drivers-use-gss

     

    It now obtains an IP except the IP it obtains is not what I expected.  I recieved 169.254.62.0 when I was expecting something like 192.168.0,10.....  If I try to proceed I get GhostCast Write Error 1944.

    If I try on another machine type I don't have this issue.  I also don't run into this if I assign the IP manually.  Bottom line is if I assign the IP in my boot disk it sucessfully Ghost Casts!

    Thank you,

    Matt



  • 7.  RE: Internal Stack Overflow System Halted

    Posted Sep 02, 2015 10:04 AM

    I suspect there must be two different DHCP servers visible to your machine. 192.168.x.x is one of the non-routable IP addresses which you typically find in home setups or if you have a broadband/ADSL router on your network. The other address looks like an address from your corporate LAN. No doubt the gateway address in each case was different also, and possibly the subnet mask too.

    Bottom line is that using a fixed IP address avoids you having to track down the source of the spurious IP address, but you may want to do that anyway, if only to avoid future issues.