Conference 7.286::atarist

351.0. "Help with Mark Will. "C"" by DSM::GOULD (Caress of Steel) Tue Dec 27 1988 14:01

Mark Williams C version 3.0.5

Well, I just bought myself a present. I got Mark Williams C. 
I am real excited about using it. Eventually I will be getting hard disk
drive. But for at least the next year I will only be using a 1040 ST with
one internal double sided floppy.

The documentation is great except for a few things, It lacks any real detailed
information about you are supposed to use the software with only a single
doiuble sided floppy. It mentions that you should make a RAM disk and keep
either the compiler or the MSH and MicroEmacs software in the RAM disk. It does
not explain really the correct way od oding this, whoch EXACT modules should
go in the RAM disk. It does not explain whoch would be better for for
performance or convenience. The book does a great job at introducing the system
and telling what ti will do. But is has no practical examples of a complete
environment. How things go together. 

For example, one the system is installed you end up with 3 disks,
the "sources", "compiler" and "commands". It really does not explain
each of these disks and their usage. If the "commands" are on one disk,
will I have to switch disks at some point when the compiler or MSH needs
them ? When would they need them, how do they fit into the scheme of things.

MY REAL IMPORTANT QUESTION IS THIS :
I want to create 2 systems :

I want to create an environment with just the compiler in a 500K RAM disk,
and my editor and shell on disk. that way programs are created on disk
and when i want to compile them i can place them in the RAM disk. If they
are too big, I can leave them on disk to be compiled. In all cases I want the
compiler to use the RAM disk as the temporary storage place while it compiles.
This is what I want to do. The documentation implies that you can do it
but it only mentions how to create a RAM disk, and explains that certain
parameters in the PROFILE will have to be changed. I need details.
I am confused because, the compiler needs other files that may not be in the
RAM disk at the time. How will it know where they are if it needs them ?
exactly which files to I keep in the RAM disk so the the compiling process is
completely independent of any other disks.
what size should I make the ram disk ?

The next thing,
I want to create an environment where the shell editor and source are in the RAM
disk. When I am ready to compile a program I just want to flip in the "compiler"
disk and away it goes, using the RAM disk again for temporary storage to speed
things up. A common problem, is what do I need to keep in the RAM disk. If
I store just the MSH and ME programs in the RAM disk, there are many commands
that the shell cannot perform cause the information is not there. For example
when I type HELP. The help stuff is on another disk. How exactly to I set
up this environment in a nice neat usable way.
what size should i make the ram disk ?

And about a Bootable RAM disk. Is it better to use these ?
Is there a way so that can have MSH come up automatically. The disk itself
has an auto file with RDY in it so the RAM disk boots automatically. Can I then
put MSH in an auto file within the RAM disk to have it boot up automatically ?


My guess is that the whole answer is within the PROFILE and how it is set up,
but how exactly do I set it up.

what is that darn disk "commands" used for ?
will i ever need the "sources" disk for anything unless i want to look at and
use the sources of the programs provided by the "C" compiler. like MSH or ME ?

Mark williams C has a disk formatter that creates 10 tracks instead of 9. it
is needed to make backups of the installation disks. Should I use this formatter
all the time for all the disks with Mark Williams C. Is there any harm ?

Are there any problems with using 1st word as my editor for "C" ?

Thanks for any help on any of the above questions...a newcomer,
Dave.

p.s. I am really excited about the "C" compiler. So far I love it,
     I am just lacking a bit in knowledge and the documentation needs
     a few more practical examples. But dont get me wrong, I LOVE IT !!    

    Thank you so much for all the fantastic information !!
    Your explanation was absolutely clear and very very helpful !!
    
    I "can see the light" and when I get back from NH in 2 days will
    be working and experimenting all weekend.
    
    I am so glad that I found this notes-file. Your one reply probably
    saved me weeks and weeks of phone calls and driving down to the
    store to bug the people I got the software from (who probably know
    nothing about it anyway).
    
    Anyway !!
    
    Thank you, and there is a good chance that I will have a few more
    questions after this weekend.
    
    Have a great New Year,
    
    
    Dave Gould