May be I didn't catch something but pointer to address 0x1ffa0000 seems to me bit strange, because I can't imagine m505 with more then 1GB(yes one gigabyte) of RAM.
"kcorey" <[EMAIL PROTECTED]> wrote in message news:95906@palm-dev-forum... > > Hi All, > > I'm looking for some advice here. > > My app is now big enough that I've needed to start using multi-segmented > code. > > My environment is WinXP, running falch.net studio 2.6.2, Pose 3.4, m505 > ROMs emulating a 515 device. > > So, everything is working up to a point, and I decide to add some > functions. > > Lo and behold, when I do I start getting the dreaded DISP16 errors. > > So, I go into my headers and start putting some functions into the > second segment. > > Now everything will compile just fine, but when I run it, it access > memory location 0x1ffa0000, which crashes the machine. > > FWIW, when I run different ROMs in the emulator (Sony 760C/NR70/Handera > 330/Palm Vx/IIx, etc) it works just fine. it also works on an actual > Visor Prism...it just dies running the 505 ROM. > > Upon further inspection, when I call WinGetDisplayWindow, it returns a > valid handle. I then call WinGetBitmap to get my BitmapType structure, > and that seems to return something valid and then finally I call > BitmapGetBits, which returns 0x1ffa0000. > > After reading the documentation, I hit upon the 'indirect' bit which > allegedly reports that the pointer returned points to a location in > memory that contains the bitmap data. > > So, I take a look at the memory address 0x1ffa0000, but it's all zeroed > out, so this cannot be the location of the bits. > > So, clearly I'm not understanding (quite) a bit of stuff here. I'm > thinking that this indirect bit of the BitMapPtr is the key somehow. > > Can anyone shed any light here? > > -Ken > > > > > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
