[comp.sys.amiga] vd0: on nearly minimal machine

fish@sun.uucp (Lorenz Fish) (06/24/87)

	Help needed with vd0: creation!
	I have recently acquired a 512K Amiga1000 with
	one (count 'em! one) floppy drive and to relieve
	some of the bother of reboots I have been trying to
	get vd0: to work. I have the device description
	and am able to run 'mount vd0:' with no complaints.
	I am unable to access the device, though. If I
	do 'dir vd0:' next I get

	Cannot get information about vd0:. Insufficient free store.

	Does this mean what it sounds like? Am I doomed to 
	'copy' essential commands to ram: each reboot until
	I get more RAM? (yeah, I know, and/or another disk drive...)

	Anyone got any tips on how to make this work on a 
	near-minimal system?
	Thanks in advance!

	Lorenz Fish   
	uucp:{anywhere}!sun!fish
	The preceding message is mine, you hear!?

perry@well.UUCP (Perry S. Kivolowitz) (06/24/87)

Did you make sure that the BufMemType is not set to 5? Make it 3
(this field is the flag to an allocmem that the system does - no
way around it since 1.2 will crash if you tell it to use NO buf-
fers).

Perry

bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt) (06/25/87)

> Did you make sure that the BufMemType is not set to 5? Make it 3
> [or it won't work on a machine with only 512k]
> Perry

Why not 1?  5 says "FAST, PUBLIC memory only".  3 says "CHIP, PUBLIC only"
and 1 says "Whatever PUBLIC memory you have".  At VD0: time this will
be fast, if you have any!
It's just one less setting that needs to be fiddled with to move <->
to other configurations of the Amiga.


Jab at Commodore -> There needs to be a new type: HYBRID for you_know_what.

|\ /|  . Ack!
{o O} . 
( " )	bryce@cogsci.berkeley.EDU -or- usbvax!cogsci!bryce
  U	Single tasking?  Just say *NO!*

Tip of the day:  The Gamma 1 and Release V1.2 kickstart disks *must* be
different because of that "V1.2" on the "Insert Workbench" screen.  Yet
the have identical revs for exec AND the $00FC00?? firmware image.  Not
even the minor rev was bumped.