Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site wanginst.UUCP
Path: utzoo!linus!wanginst!vishniac
From: vishniac@wanginst.UUCP (Ephraim Vishniac)
Newsgroups: net.micro.mac
Subject: Re: Re: LW & RamDisk
Message-ID: <925@wanginst.UUCP>
Date: Mon, 12-Aug-85 09:27:18 EDT
Article-I.D.: wanginst.925
Posted: Mon Aug 12 09:27:18 1985
Date-Received: Wed, 14-Aug-85 01:24:50 EDT
References: <764@lll-crg.ARPA> <13991@apple.UUCP> <2223@ut-ngp.UTEXAS>
Distribution: net
Organization: Wang Institute, Tyngsboro, Ma.  01879
Lines: 28

> 
> >It sounds like a lack of memory.  The LaserWriter software does not
> >spool to the disk, which means that printing on the LaserWriter
> >requires more memory.  (That's why most applications cannot print on
> >the LaserWriter from a 128K Macintosh right now.)  You should try
> >reducing the RAMDisk size by about 20-30K and try printing again.
> 
> I believe that the problem with "RamStart" is that it uses the same
> driver (volume?) reference number that AppleTalk does?  Has anyone
> fixed/patched this?  Does anyone know where/if the source is available?
>
Ramdisks are described by the finder as being on AppleTalk (instead of
being "internal" or "external") because of their *drive* number.  So far
as I've tested, 1 = Internal, 2 = External, anything else = AppleTalk by
default.  The driver number is irrelevant - decently written drivers will
function with any driver number assigned.  Volume reference numbers are
assigned by the system when the volume is first mounted.  They are not
chosen by the driver.

I believe Larry's original diagnosis (lack of memory) is the correct one.
I recall a note from Stew Rubenstein in this newsgroup pointing out that
128K Macs cannot run a LaserWriter.

 
-- 
Ephraim Vishniac
  [apollo, bbncca, cadmus, decvax, harvard, linus, masscomp]!wanginst!vishniac
  vishniac%Wang-Inst@Csnet-Relay