dbTalk Databases Forums  

d3/Linux 7.2.1 Frame out of Range error

comp.databases.pick comp.databases.pick


Discuss d3/Linux 7.2.1 Frame out of Range error in the comp.databases.pick forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Dale
 
Posts: n/a

Default d3/Linux 7.2.1 Frame out of Range error - 02-08-2007 , 04:05 PM






Does anyone know what the message:
Frame Out of Range ; reg= 14 @ au.format.outx:05B

is about?

I have been using the update hotkey functionality quite successfully
of the last little while. A few things that I could do is format the
source code I'm editing, change a line casing (upper case to lower
case and visa versa).

But today I'm getting these aborts and no patches or changes have
happened to the ABS, monitor, or Flash BASIC.

The only 'major' work done on the system was I deleted a few stale
accounts and restore live data accounts into some testing accounts so
I could work with up to date data.

Now I'm getting these aborts for to good reason that I know of.

As far as I can tell the system is now getting confused when I pass
the item back from the calling program using: access(3) = item and
then executing the RETURN in the subroutine. I've tried both FLASHED
and non-flashed versions with the same results.

tia

Dale


Reply With Quote
  #2  
Old   
Dale
 
Posts: n/a

Default Re: d3/Linux 7.2.1 Frame out of Range error - 02-09-2007 , 11:22 AM






On Feb 8, 2:05 pm, "Dale" <dale_bened... (AT) flightcraft (DOT) ca> wrote:
Quote:
Does anyone know what the message:
Frame Out of Range ; reg= 14 @ au.format.outx:05B

is about?

I have been using the update hotkey functionality quite successfully
of the last little while. A few things that I could do is format the
source code I'm editing, change a line casing (upper case to lower
case and visa versa).

But today I'm getting these aborts and no patches or changes have
happened to the ABS, monitor, or Flash BASIC.

The only 'major' work done on the system was I deleted a few stale
accounts and restore live data accounts into some testing accounts so
I could work with up to date data.

Now I'm getting these aborts for to good reason that I know of.

As far as I can tell the system is now getting confused when I pass
the item back from the calling program using: access(3) = item and
then executing the RETURN in the subroutine. I've tried both FLASHED
and non-flashed versions with the same results.

tia

Dale
Well, no one wants to wade in here and throw out some ideas for me.

The one thing I did do is add another hot-key process to the program
file. I removed that hot-key entry from the data-pointer and
viola!!! all the processes that were aborting are now working....
again.

I assumed that the trigger was the 'ACCESS(3) = ITEM' because the new
process I added passed the updated item back that way and was aborting
until, to work around the problem, I stacked the update processor key
strokes using ACCESS(21) =

Gawd, I love how my hair is turning grey.

Regards,

Dale



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.