What exactly does a yellow "OVERFLOW" message in the lower right hand corner of my window mean? It appears when I'm running a script that captures info to a file in a dos-based communications package. I am not running windows, just dos 6.22.
Printable View
What exactly does a yellow "OVERFLOW" message in the lower right hand corner of my window mean? It appears when I'm running a script that captures info to a file in a dos-based communications package. I am not running windows, just dos 6.22.
overflow error
An error that occurs when calculated data cannot fit within the designated field. The result field is usually left blank or is filled with some symbol to flag the error condition.
The capture file is just an ascii text file. The routine has run successfully for many months. The computer happens to have had a motherboard replacement just prior to encountering this problem. Are there any settings that would be causing this to happen? Also, the most recent attempt resulted in an OVERRUN error.
Add this line in your config.sys file:
Stacks=9,256
First of all, thanks for hanging in there with me on this.
The config.sys file already has the STACKS=9,256 line in it. The workstation took a lightning hit, which is why it not only has a new motherboard, but a new modem and CD-ROM as well. The CD-ROM is set up as a device in config.sys, but I REMmed it out and still get the same OVERRUN message. I still suspect a conflict (perhaps between the modem and the communications program?), but don't know how to resolve it. Also, the script/file capture has completed successfully on the last two tries, even after the OVERRUN message appears. Any further thoughts?
How to Troubleshoot Windows Internal Stack Overflow Errors
http://support.microsoft.com/support.../Q145/7/99.asp
You say you're running only DOS, not Windows, and that the error happens while you are in the communications package. Since the error appears in the bottom-right corner and is yellow, that says to me that the error is not DOS generated but is coming from your comms program.
Could be that some buffer in your comms program is getting filled too quickly. Check the documentation for your comm program.
Another option to try is adding:
/E:2048
at the end os the "Shell=" line in your config.sys. If I have to many SET= commands in my boot at run a large bacth file iI get erors.
If you don't have it in your config.sys, add:
DEVICE=C:\COMMAND.COM /P /E:2048
Type:
COMMAND /?
for more info and range you can enter.
Dennis