🚀 go-pugleaf

In article <1984@calmasd.CALMA.UUCP> cjn@calmasd.UUCP (Cheryl Nemeth) writes:
>RamStart doesn't seem to work at all with the cache enabled.  It also seems
>that this combination wouldn't be extremely usefull, as the cache would
>probably end up cacheing part of the ramdisk.  
>
True. Although mine works, it subtracts the cache size from the ramdisk
size leaving no space on the ramdisk. It bombs if it runs into the size
problem while attempting to load the system to the ramdisk.
>Why is it that my version of RamStart seems to work fine with my Plus
>with no patches whatsoever?

The unpatched version 1.21 works with the Mac+ except when attempting to
autostart. At the point where it hands off to the copied system it 
bombs.
Creating a Ramdisk automatically, but without a system or finder in it works. 
Creating a Ramdisk manually, copying system and finder to it, and launching
the finder works.

Only attempting to autoboot a Ramdisk fails.

The new HFS compatible Ramstart 1.23 seems to work fine in all modes.

-- 
 Jim Budler
 Advanced Micro Devices, Inc.
 (408) 749-5806
 Usenet: {ucbvax,decwrl,ihnp4,allegra,intelca}!amdcad!jimb
 Compuserve:	72415,1200

Once and for all: I like my Macintosh