2006-02-02 07:47 PM
2006-01-31 02:24 AM
Yes, I've just written a *very* small file which compiles just peachy, using the default build settings and a 32-bit number. Annoyingly I noticed some changes between the lkf files and corrected these in the original- which made no difference.
Unfortunately I cannot post the full project as it is nearly a complete product (this morning I got it 'e' and 'E' marked).2006-01-31 03:09 AM
I've also uninstalled all previous versions of the compiler and reinstalled the 16K version. This has had no effect. I notice that by default the registry key linking to the libraries has not been used; I have therefore manually added this which again has no effect. If I manually move the libraries around the error message changes to ''Could not open libfs.st7'', so obviously the file is there. I wonder if the file could have been corrupted, perhaps during the download? Even MD5 isn't infallible. Do you have a current version you could post to this forum?
2006-01-31 03:27 AM
I am using the full version which will be a differant number.
I do know of a few customers who are using the 16K version with no problems, is there no way of you uploading a testcase to look at ? Regards sjo2006-01-31 04:01 AM
Well, the library compiles fine in another program I wrote specifically to test this functionality so it appears the problem is something to do with this application. Sorry sjo, even though you appear to be an FAE for ST I just can't release this code. I will contact COSMIC and see if they have any suggestions.
Thanks for all your help.2006-01-31 09:05 PM
2006-02-02 07:47 PM
for those who have been following this thread, the problem was due to a missing module in the libraries within the 16k compiler.
This has now been fixed. Regards, Luca (Cosmic)