Xref: utzoo comp.sys.amiga.tech:871 comp.sys.amiga:19547
Path: utzoo!utgpu!water!watmath!clyde!bellcore!rutgers!rochester!ur-tut!dpvc
From: dpvc@ur-tut (Davide P. Cervone)
Newsgroups: comp.sys.amiga.tech,comp.sys.amiga
Subject: Re: DiskObject
Message-ID: <2135@ur-tut.UUCP>
Date: 31 May 88 18:02:02 GMT
References: <4725@watdcsu.waterloo.edu> <54486@sun.uucp> <4751@watdcsu.waterloo.edu>
Reply-To: dpvc@tut.cc.rochester.edu.UUCP (Davide P. Cervone)
Distribution: na
Organization: Univ. of Rochester Computing Center
Lines: 22

In article <4751@watdcsu.waterloo.edu> debate2@watdcsu.waterloo.edu (Dave Oh) writes:
>Ok... What if I were to call dobj=GetDiskObject(disk); ?
>The GetDiskObject call returns a pointer to FAST ram, for gadget, diskobject
>and image... I've tried to CopyMem(&dobj->do_Gadget.GadgetRender,&nimage,
>sizeof(struct Image)); and I get a lock up!  Even in Manx SDB.

But doesn't CopyMem use the blitter to move the memory?  If so, then you
CAN'T use it to move your image from FAST memory to CHIP.  You'll need to
have the CPU do the memory move, not the blitter.  There probably is a Manx 
library routine that does this (like movemem or something).

>I figured that even thought the GetDiskObject returns FAST Ram memory,
>All I'd have to do is just copymem it to another Image struct Allocated in
>CHIP ram, and then redirect the dobj->do_Gadget.GadgetRender pointer to my
>new Image struct.  this didn't work...

It should, provided you use the CPU to copy the memory instead of the blitter.

If I'm wrong about CopyMem using the blitter, then you can ignore this message.

Davide P. Cervone
dpvc@tut.cc.rochester.edu