[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== Internal Stack Overflow error. (AREV Specific) ====
=== At 11 JAN 1999 03:43:09PM Matt Sorrell wrote: ===
 
{{tag>"AREV Specific"}}
 
<QUOTE>
HELP!!!



In one of our stores, a particular process generates a DOS error msg "Internal Stack Overflow.  System Halted."  This code runs just fine in all of our other stores.  The code has not been modified in several months, and has never generated this error before.



We are running AREV 3.12 on DOS 6.22, with a Novell 3.12 network.  The code does not call any assembler or C routines and only uses standard internal AREV functions, other than our own R/BASIC routines.  According to our techs, this store has all brand new hardware.



Also, we use UBI keyboard wedge scanners, and it is in a routine that is using this scanner that causes the problem.  The problem occurs on 2 out of 4 workstations.



the workstation boot of a boot image on the server, the do not have local hard drives.



I'm completely at a loss.



If anyone has any ideas, I would greatly appreciate it.



Thanks,



Matt Sorrell

msorrell@movgal.com
</QUOTE>
----

=== At 11 JAN 1999 05:05PM Steve Smith wrote:  ===

<QUOTE>Suggestions - swap the wedges to the other two PC's to see if you've got two OK and two bad wedges. This will tell you if you're looking at hardware or software. Sometimes wedges can deliver crap at the end of a scan sequence (filling the keyboard buffer and mess up the buffer pointers in the BIOS)



Are the keyboards on two machines PS2 connectors and on two standard 5-pin DIN connectors? This may be a factor. Check the Y-cables to the wedge are seated OK.



Are the network card addresses all set identically? 



Perhaps you could use a keyboard buffer expander to see if this helps.



Is there a TSR or device driver which operates to support the wedges at all?



Check the keyboard typematic delay rate set in the PC BIOS (if any).



Steve

stsm@ozemail.com.au

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=E49931EE58D2E17B852566F60071D06D|View this thread on the  forum...]]