Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ll-xn!mit-eddie!uw-beaver!tikal!transys!baron
From: baron@transys.UUCP (Joe Portman)
Newsgroups: comp.sys.atari.st
Subject: Re: Mark Williams C 2.0 (plus request for benchmark help)
Message-ID: <322@transys.UUCP>
Date: Thu, 7-May-87 15:11:19 EDT
Article-I.D.: transys.322
Posted: Thu May  7 15:11:19 1987
Date-Received: Sat, 9-May-87 16:38:41 EDT
References: <136@xrxns.UUCP>
Reply-To: baron@transys.UUCP (Joe Portman)
Organization: TransSystems Inc. Bellevue, WA
Lines: 64


In article <136@xrxns.UUCP> toml@xrxns.UUCP (Tom Love) writes:
[much deleted]
>
>also:  the installation procedures are ok for a hard disk or dual
>floppy system, but are an incredible, frustrating pain on a single floppy
>(e.g. 1040stf) system.  multiple swaps *per file* are performed, and we're
>talking *lots* of files.  there is a lot of room for user confusion.  i 
>suspect that appropriate use of a ram disk at install time could make this
>much more reasonable, but this is not supported by their installer.  

	The installer I used specifically tells you to install a ram disk.
	On disk number one of the installation floppies there is a sample
	rdydisk.ram info file. I loaded that, went to the desktop and installed
	the disk as drive C. After that, back into the install and away we
	go. Total install time: about 12 minutes. 
	
	I tried to install about twice before I realized the installer was
	looking for drive C as the ramdisk. This is probably a bug.


>this sort
>of brings up another issue, the appropriateness of this compiler for "small"
>systems, e.g. 520 with ss drives, either 520 or 1040 without a hard disk.
>single sided drives are supported, but i don't think i'd want to try it. and
>though work on a single floppy is supposedly possible, i haven't succeeded
>at the install yet, and even when i do succeed a lot of the convenience of
>having the msh commands and everything available at once will be impaired on
>a single disk system.
	
	A 520 SS system is probably not suitable for development work without
	at least a ram upgrade.

	I have a 1040STf and a single DSDD floppy.
	I created a boot disk with just the compiler passes, cpp and
	a couple of often used commands (msh, me and grep). When I boot with
	MSH in \AUTO I have a special PROFILE that copies the entire disk
	to the ram disk.

	I then put the compiler disk created by install in the drive and cd 
	to the ram disk.
	
	With the compiler passes in ram, there is still about 100k or so left
	for a source file on a 400k ramdisk. This is plenty for a lot of 
	applications, in fact I am amazed at how much can be done on a single
	drive system. When I need a special command, I simply swap the commands
	disk in and away I go. If you want it to, you can make the shell prompt
	you for the commands by adding drive b: to the PATH variable. The shell
	will search ram, drive a: and then ask for drive b:.

	Incidentally, with the shareware FORMAT2 program, you can format a disk
	to hold 820k. With this extra space you can add a lot of commands to
	your compiler disk, thus eliminating swaps.

	I have'nt completely customized my setup yet, I just realized that with
	the compiler passes in ram, I don't need them on the compiler disk any
	more.

	Oh well, bottom line: Single drive development is very practical using
	MWC.

	[goes on to say much good about MWC]

	I agree. For the price (I paid 114.50) I believe it is a super value.