Thanks Andreas,
That helped!  You pointed out where I should look and why.  It turns out in 
my efforts to "objectify" the VM code, I had inadvertently put 
specialObjectsOop in the Image object as well as the Memory object within the image.  Once I 
got rid of the duplication, I'm clean all the way thru reading in the image 
and intializing it!  On to the interpreter!

Thanks again,
S

PS - This list definitely has the most useful/helpful information and 
people on it.

---- On Fri Feb  6 00:28:30 1998, Andreas Raab said ------

>> under BeOS specialObjectsOop = 2094925144 (which is the value 
>> of bytesToShift).
>
>That's not ok. The interpreter code says
>
>  specialObjectsOop += bytesToShift;
>
>and as long as the image has not been saved based upon startOfMemory = 0
>specialObjectsOop cannot be equal to bytesToShift.
>
>> startOfMemory = 2147553280 under BeOS (0x80011000).
>
>And this don't work. If specialObjectsOop < startOfMemory you're doomed to
>get access violations.
>
>> I need another pair of eyes...anyone see anything screwy?
>
>Well ... maybe you've accidentally modified the interpreter source?!
>That's the only idea I have right now.
>
>Hope this helps,
>  Andreas
>-- 
>Linear algebra is your friend - Trigonometry is your enemy.
>+===== Andreas Raab ============= (raab at isg.cs.uni-magdeburg.de) =====+
>I Department of Simulation and Graphics      Phone: +49 391 671 8065  I
>I University of Magdeburg, Germany           Fax:   +49 391 671 1164  I
>+=============< http://isgwww.cs.uni-magdeburg.de/~raab >=============+
>
>
-------------------------------------------------
VisualNewt Software: http://www.VisualNewt.com/
Maker of Newt'sPaper(tm) the Premier Newton(R)
MessagePad(tm) News Reader.

-----------Sent by BeOS--------------------------