My thanks to you Marcel, Rich and Per for your advice regarding this. The problem is now solved ... though I shall have to follow the sages' advice and get meself updated! It is a **big** boot - with many Procs. It seems that I was clumsy with the SB editor and accidentally renumbered (=relocated) a line of code, when I meant to delete it. Putting that right put things right.
------------------------ I am returning to QDOS after several (unavoidable) years away. I have a new Proc in the (QPC2) boot to call EXCHANGE from a command line. Below is some code that I wrote when I had SMSQ/E on a SGC. The code means nothing to me now however [age!]. Are such parameters/safeguards advisable in the QPC2 environment. Would anyone like to comment please?. 1600 : 1610 DEFine PROCedure XCH 1620 REMark ++++ EXECUTE XCHANGE +++++++++ jgh ++++++++++++++++++++++ 1630 REMark If TK2 then 'EX' may be used with param 'n' (as below) 1640 REMark Empirically (by 26 controlled tests in jgh '837K free' system) - 1650 REMark XCHANGE[itself] always grabs 297.5 + (n-64)K [wkg K] THUS - 1660 REMark IF n<64 n=64! XCEPT: n=0 XCH grabs some but not allRAM (517K in jgh) 1670 REMark n<0, XCH has no cursor!: (n-64) >availble RAM, QLlocks up ! 1680 REMark so, Max 'n' for jgh '837K free' system was 535 1690 : 1700 Xmem=750: Xpram$=INT((Xmem-297.5)+64) : REMark Use Notes above 313.5 1710 CLS #0:PRINT #0\\ TO 3;"Loading: XCHANGE"\" RAM Allocated: ";Xmem;'K' 1720 DATA_USE flp1_: EX XCHANGE;Xpram$: REMark IfNotTK2 use"exec", NO param. 1730 CLS #0 1740 : 1750 END DEFine XCH 1760 Can I scrap the parameter detail? - it works (?) now with - 'ex win1_exchange' Regards to all John in Wales (jgh) -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.430 / Virus Database: 268.15.6/566 - Release Date: 03/12/2006 16:36 _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
