Ghost Bootup Problem

[gmc8757]

Hey Guys,

I have a network book disk made from barts bootdisks. I've used it in the past, and it works great. Except now, I'm trying to ghost a gx520 dell. After booting up to dos, load the network drivers, map a network drive, run ghost.exe from the networked drive, ghost comes up, after a few seconds, 2 black lines pop up saying "An internal stack overflow has caused this session to be haulted. Change the STACKS settings in your config.sys file, and then try again."

I changed settings based on this post Here, but it didn't work. Any ideas?

Thanks a lot.
Joe

 

[rcalzada51]

A Stack Overflow can sometimes be caused by a bad memory module. Try swapping out the memory for "known" good memory and try it again.

 

[gmc8757]

Hey,
I tried the same disc in other computers just now and get the same error. They were all brand new and work.

I was wondering if there was any switch I could use like "ghost -fni" or something like that.

 

[mrbill14]

Here's some information on the STACKS= command in the config.sys file. You may want to put this line in (or edit it if it's already there).


STACKS=0,0 The stacks line was first used in MS-DOS 3.2 and was used to swap the stack whenever an asynchronous hardware interrupt occurred. Later in MS-DOS 3.3 the line STACKS=0,0 was added into the config.sys. In special circumstances, this line was changed to STACKS=9,128.
The STACKS statement has a range of 8-64, 32-512. If a higher value is entered you will receive a FATAL : Internal Stack Failure, System Halted error message.

 

[gmc8757]

I really appreciate your help, but i have no clue what stacks are or what they do.

This is what my config.sys file looks like on the boot cd. Do you ahve any suggestions as what to change?
------------------------------------------------------------------



[menu]
menuitem=AUTO, Boot with emm386 (most compatible)
menuitem=MAX, Boot with emm386 (max memory)
menuitem=NOEMM, Boot without emm386
menuitem=CLEAN, Clean boot
menudefault=AUTO,5

[AUTO]
switches=/f
break=off
dos=high,umb
files=20
buffers=20
lastdrive=z
device=\bin\himem.sys /testmemff /v
device=\bin\emm386.exe /v x=d000-d8ff h=128 noems notr
shell=\command.com /e:1024 /p
devicehigh=\bin\ifshlp.sys

[MAX]
switches=/f
break=off
dos=high,umb
files=20
buffers=20
lastdrive=z
device=\bin\himem.sys /testmemff /v
device=\bin\emm386.exe /v h=128 noems
shell=\command.com /e:1024 /p
devicehigh=\bin\ifshlp.sys

[NOEMM]
switches=/f
break=off
dos=high,umb
files=20
buffers=20
lastdrive=z
device=\bin\himem.sys /testmemff /v
shell=\command.com /e:1024 /p
device=\bin\ifshlp.sys

[CLEAN]
shell=\command.com /p

STACKS=64,512
FILES=60
BUFFERS=40
----------------------------------------
I added STACKS=64,512
FILES=60
BUFFERS=40
based on the post I read somewhere. No clue if that's what i needed(i guess not since it didn't work).
Thanks alot.

 

[gmc8757]

I just tried:
STACKS=32,512
FILES=60
BUFFERS=40

and it gave the same error.

I'm sure there's something i can change.

 

[mrbill14]

Hmmm... maybe something with the version of Ghost. Or a corrupt file (?).

Did you try this file on a different PC? This would eliminate (or point to) one possibility or the other...

A note for the STACKS variable:

Note: STACKS= only affects hardware interrupts. If the stack being overflowed (trying to store too much information) is internal to an application, this will probably not solve the problem.

 

[mrbill14]

Sorry, didn't read the post were you already tried it on a different PC.

If this 520 has SATA drives, make sure you updated Ghost. I found this out the hard way... had Ghost 8 (or 2003, whatever you want to call it) and had to actually do a LiveUpdate on the installed product so it would see the SATA drives.

If Ghost sees your HD, chances are it's already updated.

 

[gmc8757]

Yea, i'm able to ghost the machine no problem using the UBCD (ultimate boot cd) load up to windows on live cd, map drive, and ghost. However, this is a lot longer process then just booting to dos like we always did. I'd reall like to get this dos ghost going, i'll keep trying. Thanks for your input.