'MSG' Line 62 B708 error message (AREV Specific)
At 25 MAY 2000 10:11:23AM Trevor McDonald wrote:
On 2 of 150 systems running identical sofware on random occasions system halts and reports
'MSG' Line 62 B708 Subroutine Contains Invalid Header Call Aborted
Line 62 "MSG' Broke Because a Runtime error was encountered
Both systems operate under DOS 6.22 and Arev 3.1
Nothing is tracable - if anyone could advise the details of Line 62 in MSG it would help to trace the problem
At 25 MAY 2000 10:16AM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
This is unusual - MSG is normally compiled without linemarks. Could you edit the $MSG code and report back the version number at the end of the code along with any other date/time info?
World Leaders in all things RevSoft
At 25 MAY 2000 10:20AM Don Miller - C3 Inc. wrote:
Trevor..
Usually this is a result of not enough memory or misallocated memory.
Check to make sure that you start the app with /M4096X option on the workstation and make sure that you have EMS enabled on the machine. If DOS 6.22, check CONFIG.SYS / AUTOEXEC.BAT. Other items are user network access rights. Sometimes a machine BIOS wil mis-report the CPU / Math Co-processor which can cause strange behavior.
Don Miller
C3 Inc.
At 25 MAY 2000 11:22AM Steve Smith wrote:
Sounds like
(a) your system uses a different version of MSG - try reloading a clean AREV and copy the object to your faulty system
(b) you have a corrupt version of the native AREV MSG (although the fault should occur every time under these conditions)
© you have source code in sysobj by mistake for a routine which is called by MSG
(d) a TSR or memory resident program is corrupting something
(e) you have faulty RAM on the PC, or else RAM-based BIOS in a region reserved for expanded memory, or a network card with an address which intersects some of AREV's memory, or not enough memory.
(f) you have a fault in your expanded memory - try using the /XM4096
command line parameter for AREV.EXE, or else disable expanded memory all together if possible.
Steve
At 25 MAY 2000 12:14PM Larry Wilson - TARDIS Systems, Inc. wrote:
Is it possible that these are old 386 machines? If so, run AREV with the /E option and try that.
At 25 MAY 2000 07:00PM Trevor McDonald wrote:
Thank you Gentlemen, I think the memory issue may be the problem and I will try your tips and report back. Neither of the machines are 386 based.
$MSG reports version 3.1.43