>This could be because Qliberator is not able to run under SMSQ
properly ; or
Unlikely, I never had a problem like this (I use it all the time)
>it could be because QPC2v2 doesn't like Qliberator; or
I refer the honourable gentleman to the reply given above ;-)
>it could be both; or
>it could be me being a complete idiot :o( ;or
Knowing you, I doubt it ;-)
>something else altogether
>
>but .....
>
>Start QPC2v2 and from a clean boot, (800 by 600 res, high colour
mode) do
>the following :
>
>lrespr win1_qlib_qlib_sys
>qlib_use win1_qlib_, win1_qlib_
Is this the only way to install QLiberator, or are there separate
files for the compiler (must admit I use qlib_sys)
>This loads and configure QLiberator, then the stuff for Screen
Snatcher 2
>....
>
>dev_use 2, win1_source_ss2_
>lrespr dev2_snatch_cde
>lrespr dev2_snatch_cfg
>
>The _cde file is an EP3 appendix file holding the required menu and
code
>file to be compiled into the application,
>the _cfg file is a BASCONFIG file holding the config block for the
>application - again, to be compiled in.
Some versions of Basconfig have a stack error after you have used the
extensions to fetch the values, but as you and I fixed various
problems with it, I guess we can discount that.
>Load the application ....
>
>qload dev2_snatch
>
>and compile it ....
>
>liberate
>set the options (no windows, +line numbers etc)
>source file = dev2_snatch_sav
>object file = dev2_snatch_obj
>
>No errors reported.
>
>Run it ......
>
>ex dev2_snatch_obj
>
>it works fine, except that it doesn't vanish from the screen when the
>activate loose item is hit - I wonder why ?
>
>Change a line in the source file - makes no difference which one,
then save
>it ...
>
>qsave dev2_snatch
>dev2_snatch_sav exists, overwrite Y/N
>select Y to overwrite
>
>ALT P to find and pick the same version of QLiberator again for a
recompile
>Hit the COMPILE loose item
>
>All of a sudden, I get a screenful of 'ambiguous name' errors. All
relating
>to Q_ERR_ON/Q_ERR_OFF/Q_ERR/QX etc. The problem stays if I reset the
whole
>plot, and reload everything as above - now I cannot even compile it
the
>first time.
This does indeed sound like the problems I reported a few days ago
when trying to use MAX_CON in a procedure or function - some very
strange and illogical things happened. I have noticed that if stack
errors are introduced, SMSQ/E does seem to have more problems than
QDOS did, although very often QDOS would just pretend nothing happened
and crash later when you had little idea what you'd done wrong -
SMSQ/E appears a little more fussy sometimes, but it's on the whole
just that it's better at accurately reporting problems. If things seem
to work fine on a 'clean' system it would seem to imply something like
a crawling stack error.
>I am one very puzzled (and p*ss*d off) programmer I can tell you.
>Does QLiberator work under SMSQ - I've seen mentions of using bit 31
in
>addresses etc, but my experiences today have been horrendous - I've
wasted a
>lunch hour and two (yes two) tea breaks trying to re-compile this
program !
Never mind, you can have the TOR NT4 system at work which has driven
me up the wall this week (although mustn't complain, the problems mean
I'll have a nice bit of overtime this month) and I'll compile your
program!
(BTW, QPC2 v2 seems to work fine on the NT4 system, running OK from
CD-ROM, as long as I don't try to save any configuration changes of
course)
>(I'm going off Malcolm now as well - he suggested the changed :o) -
joke !)
Are you sulking Malcolm ;-)
--
Dilwyn Jones
[EMAIL PROTECTED]
http://www.soft.net.uk/dj/index.html
