CNOTE2.TXT

**********
C notes II
**********  

These are some hints to using C-Power 128.

Written as subsequent file to another 
cnotes.txt file in this D/L section.

1.  LIB.C on the program diskette is for
the C-64 version and will never work as
it is written.  (Ashamed to admit it took
me MONTHS to figure this out!).  The SYS
call in the GETCH function must have a
BANK location included.  It should read:

getch()
{
    char a, x, y;

    do
        sys (15, 0xffe4, &a, &x, &y);
    while (a == 0);
    return a;
}

This is an obscure little error, but would
crash the LIB program every time!  There
has been a BASIC C library manager written
and published by The TRANSACTOR, but it
is so much nicer to have it run under the
shell program.

2.  There are multiple edit buffers for
ED and CED.  You call them from the CMD:
prompt with 'go xxxx' where xxxx is your
chosen name for the buffers other than MAIN
and PASTE which the system sets-up.  Use
'list' from the 'cmd:' prompt to see the 
available buffers.

3.  You can cut & paste from any buffer!
By using [run/stop] + cursor movement to
tag the text you want to move then F5 to 
cut it to the 'PASTE' buffer.  From here 
you can 'go' to any buffer and then F6 
will paste the buffer at the cursor location.
You CAN NOT edit or 'go' to the PASTE 
buffer.

4.  Example of above...editing in MAIN
area and you can't remember how to use 
a command or function.  'Go' to 'help',
'get' a file off the disk that uses the
function you need, cut the specific text,
'go' back to 'main' and paste in the text
you taged.

5.  'setu' without parameters will list
the defined storage devices including the
available RAMDISKS.

6.  You can modify the SHELL program to
define the function keys to suit your
needs and resave it to disk w/o problems.

7.  The manual mentions a "built in 'run'
command".  In fact, this does not exist!
Part of the document problem is that the
128 docs are poorly rewritten 64 docs,
with even the index pages wrong!  To rerun
a program, just type the name again, if it
is in memory, it runs without reloading. 

8. I have tried to get the compiler to work
with the '-p' option to access my 1581 as
device 10, but it continues to go to device
8 for the main compiler program.  If anyone
can figure this out, I'd appreciate the
secret.

9.  If you are using this C compiler, and
have figured out some undocumented goody
please make it known to the rest of us!
I have the version prior to PROLINE's
sell-out to Spinnaker and the documentation
is worse than "skimpy".  They offered a BBS
in Canada that was supposed to have updates,
advice, and help that I could never reach. 
I would love to know how the documentation
is with Spinaker's version.  Is it worth
buying a new version to get better use from
the software???

10.  These may seem trivial to an old C
programmer, but for a NOVICE like me, were
major roadblocks to getting started!

M. Tucker Brawner [73455,1440]