home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
C!T ROM 2
/
ctrom_ii_b.zip
/
ctrom_ii_b
/
PROGRAM
/
CLIPPER
/
FUN_EX
/
README.1ST
< prev
next >
Wrap
Text File
|
1993-09-19
|
3KB
|
72 lines
TO: All Funcky II (and Exospace) Users
FM: Paul Taylor - S T Research Pty Ltd
CIS 100033,1424
The enclosed program 'TESTFUN.PRG' should cause a GP fault if you
link with the Exospace linker.
The problem appears to be that the fOpen function is 'occasionaly'
passing incorrect parameters to the 'strcpyn function in Funcky and
memory gets corrupted.
This should effect any low level file access as well as the Funcky
C_MAX??? functions that use fOpen to read form files etc... You can
search the map file produced by ExoSpace and look for 'FOPEN' to
see..
ALSO: I would expect that it 'should' cause an eventual system
crash if linked with a standard linker due to memory
corruption. But in this case it may be a long long time
before it bombs.
If this example bombs for you then try the following:
The work-around that works for me is to use the 'fOpen' function
from CLIPPER.LIB rather than the one in FUNCKYCL.LIB
If you make a copy of FUNCKYCL.LIB then use the following command:
LIB FUNCKYCL *-FOPEN
This will extract Funcky's fopen function from the library and
places a copy of fopen.obj in the current directory (to be safe).
Next, run MAKTEST (you should get a mult defined symbol 'fClose') and
then run FUNTEST again. This time it should not bomb.
WARNING: This worked for me and I have submitted it so that others
with the same problem may save some frustration.
WARNING: If you use the Funcky error trap/handler I expect that calls
to the Funcky error handler will not be made as you are not
using the Funcky fOpen function any longer.
WARNING: There may be other differences between the Clipper fOpen &
the Funcky fOpen functions so BEWARE...
MY THANKS TO: Joshua at dLesko
...for his friendly support and information. I have advised dLesko
of my findings and are confident that they will look into it.
MY CRITICISM TO: The Exospace Support Person (not CA)
...who sounded like a broken record and "refused" to answer even the
simplest of questions and in the end, gave me incorrect advice <to get
rid of me?>.
I paid $500 to buy Exospace rather than wait for CA $99 version. The
manual acknowledges the 'value of support' and they pledge to provide
good support. They lied!
I would appreciate e-mail as to your findings. Hope it helps...
Paul