🚀 go-pugleaf

We all know about using LockResource() as the equivalent of GlobalLock()
to keep a resource put.  We also all know that you should use GlobalWire()
instead of GlobalLock() if you're going to be keeping the resource locked
for a long time.  Now, it seems to me that there should be some equivalent
WireResource() call to relocate the resource into the bottom of memory
and lock it there.

Since there isn't a call like this, I've tried just passing
GlobalWire() a handle to a resource and keeping my fingers crossed.
This seems to work OK as long as access the resource immediately
before this to insure that it is currently loaded.

Now, am I courting disaster by doing this?  I sometimes have to lock
these resources for hours (and don't flame me on that... I really do
need to have them locked) and I hate the thought of leaving them
fragmenting memory space.

-- 
Jim Seidman (Drax), the accidental engineer.
"It doesn't have to work... they'll be paralyzed just from laughing at me."
							- Dr. Who, _Shada_
UUCP: ames!vsi1!hsv3!jls	         INTERNET: hsv3.UUCP!jls@apple.com