Path: utzoo!utgpu!water!watmath!clyde!att!ihlpm!jmdavis
From: jmdavis@ihlpm.ATT.COM (Davis)
Newsgroups: comp.sys.amiga
Subject: Pushing ASSIGN to the limit?
Message-ID: <2259@ihlpm.ATT.COM>
Date: 23 Aug 88 22:39:00 GMT
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 32


In an effort to ease the pain in changing all programs that access
RAM: to VD0: or RAD: (when it comes out) I was wondering if I could
simply do an:
	ASSIGN RAM: VD0:

I could test this myself, but I can't convince myself that even if
it is successful after 10 mins of testing that it will be successful
in all circumstances.

Along the same lines, can I do an
	ASSIGN DH0: VD0:
so that I have access to my ram disk inside of DPaintII. (Boy their file
requester sure is brain dead!) BTW, I don't have a hard disk.

(And what if I ASSIGN my DF1: somewhere else? Can I do it?)

---------

I can guess that any assign involving a mounted physical device can
sense that fact and act accordingly (whatever that means)

	{You didn't want to assign DF0: you really meant WorkBench:}
	
I am fully prepared to get rid of Ram.Handler. Will this make RAM:
always be a logical device and solve my problem?

-- 
________________________________________
					|	Mike Davis
					|	..!att!ihlpm!jmdavis
				 	|_________________________