Ghost Code 19903

Posted on 2009-02-22
Last Modified: 2013-12-02
I'm using Ghost Solution Suite 2.0
I want to gather an image of a  Client Machine. PXE booting work fine. Ghost Client and Driver loads fine. No problem there...
Once the multicast starts, a dialog appears saying " Ghostcast session failed with ghostcode error 19903.."
This thin DOS client that Symantec have chosen to "cling" on, is annoying to say the least.
Having done some reading on other forums, it appers the problem may be memory related.
I've tried recreating the boot files using  MSDOS (win98 se) and adding the following lines into


No go. Same error.
Help appreciated
Thanks in advance
Question by:Beeshoring
    LVL 63

    Expert Comment

    1) Do you have the latest GSS 2.02 or 2.5 ?

    2) Have you tried doing a Local Netork backup via a bootable Ghost CD to see if that works OK ?

    I hope this helps !
    LVL 3

    Author Comment

    Apologies for the late reply.
    GSS 2.02 seems to equate to build
    The Ghost32.exe version on my CD says (Its' a compiled CD made by my former company)

    I will try the CD as suggested, now that I  have the NIC drivers.
    LVL 1

    Accepted Solution

    Not sure If you've managed to solve this yet but the solution I found was to use the newest version of the MS-Dos (not the pc dos version) himem.sys file that I could find.  I just injected it into the ghost.dsk vfi and it worked quite happily.  

    Its worth noting that I also had no luck using any of the extra switches for loading things into higher memory or making dos load high, not even things like emm386 allowed me to access larger amounts of memory.  Looks like its a flaw with the way pcdos tries to access extended memory.

    This link might give you some extra background info which you dont *really* need but its handy to have:

    So yeah long story short, inject the newest msdos version of himem.sys into your pcdos virtual floppy and things should be apples.

    This fix worked for me on 2.0, 2.02 and 2.5 versions of the solution suite.  Let me know how you get on.

    Expert Comment

    Don't know if this will help anybody, but I had the exact same thing happen to me. Without all the tech talk and wasted explanation, to make things easier for the next person. I had to take a copy of the Himem.sys file from a Windows 98 boot disk that was larger than the himem.sys file that is injected with the msdos version from ghost. Once I injected the 33kb size file over the 14kb size one that came in ghost, I was able to get my image from the Ghostcast session. Good Luck!
    LVL 3

    Author Comment

    Thanks Jeffb67 and MrDynomyte. Ok I'll take both your suggestions into account and give it a try. I've been using imageX and WDS which seems to offer many more options. Saying that I've got the Symantec licences so it would be a shame not to use them.  Will let you know how I get on.
    LVL 3

    Author Comment

    The himem.sys from the Win98 boot disk did the trick

    Featured Post

    Enabling OSINT in Activity Based Intelligence

    Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

    Join & Write a Comment

    This article is an update and follow-up of my previous article:   Storage 101: common concepts in the IT enterprise storage This time, I expand on more frequently used storage concepts.
    The Delta outage: 650 cancelled flights, more than 1200 delayed flights, thousands of frustrated customers, tens of millions of dollars in damages – plus untold reputational damage to one of the world’s most trusted airlines. All due to a catastroph…
    This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…
    This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

    745 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    15 Experts available now in Live!

    Get 1:1 Help Now