• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1935
  • Last Modified:

Ghost Code 19903

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
config.sys

DOS=HIGH,UMB

No go. Same error.
Help appreciated
Thanks in advance
0
Beeshoring
Asked:
Beeshoring
1 Solution
 
SysExpertCommented:
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 !
0
 
BeeshoringAuthor Commented:
Hi
Apologies for the late reply.
GSS 2.02 seems to equate to build 1.0.0.1573
The Ghost32.exe version on my CD says 1.0.0.1502. (Its' a compiled CD made by my former company)

I will try the CD as suggested, now that I  have the NIC drivers.
Thanks
0
 
jeffb67Commented:
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: http://www.symantec.com/connect/forums/ghostcast-session-setup-failed-ghostcode-19903

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.
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
MrDynomyteCommented:
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!
0
 
BeeshoringAuthor Commented:
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.
0
 
BeeshoringAuthor Commented:
The himem.sys from the Win98 boot disk did the trick
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now