shaun@sauron.OZ (Shaun ARundell) (05/19/86)
I am using Lightspeed C on a standard duel 400k disk
fat mac. I have been trying to work out what is best to
put on a ram disk. The system and finder or Lightspeed
itself and some libaries ?. Anybody figured out a good
solution.
Thanks in Advance
\XX Shaun Arundell ARPA: munnari!sauron.oz!shaun@SEISMO
\X Technical Support UUCP: seismo!munnari!sauron.oz!shaun
XXXXX \XXXX GOULD COMPUTERS ACS: shaun@sauron.oz
XXXXX /XXXX
/X Telephone STD: (02) 957-2522
/XX ISD: +61 2 957-2522 dubois@uwmacc.UUCP (Paul DuBois) (05/19/86)
> I am using Lightspeed C on a standard duel 400k disk > fat mac. I have been trying to work out what is best to > put on a ram disk. The system and finder or Lightspeed > itself and some libaries ?. Anybody figured out a good > solution. I've been wondering this myself. Lightspeed doesn't run at all with itself and a system in the ramdisk. It doesn't do much with just itself in the ramdisk (couldn't compile anything without running out of memory). I (currently) put a system, a minifinder, and MacTraps in the ramdisk (just over 100K). The minifinder is set to show only a minifinder (you do this by installing one, then selecting it and installing another one). Boot this disk. Click the minifinder "Drive" button until you get Ramdisk, then double-click the minifinder. This makes the mac forget about the system on the boot disk and use the one in the ram disk. Eject the boot disk. On another disk I keep Lightspeed, and all the standard #include libraries, and still have a fair amount of room. Since the boot disk is ejected and the system is in the ram disk, I can still put a data disk in one of the drives. If I run a program on another disk that has a system on it, I can still run the ramdisk Minifinder to reinitialize the ramdisk system. It seems to me that it would be better to leave MacTraps on the disk with Lightspeed in it and use some space in the ramdisk for *part* of Lightspeed. My idea - which I haven't got around to trying - is to move some of Lightspeed's CODE resources into the system that gets put on the ramdisk and delete them from the Lightspeed application. Would this work - or does the segment loader only load CODEs that actually come from the executing application? If it would work, this would be a way of getting part of Lightspeed to speed up (virtually instantaneous swapping of the hacked segments) and still having enough memory to do something useful... -- | Paul DuBois {allegra,ihnp4,seismo}!uwvax!uwmacc!dubois --+-- | Doth the hawk fly by thy wisdom, and stretch her wings | toward the south? Job 39:26