It sounds like you are not releasing the chuck of memory each time you use it... You need to do a "MemPtrUnlock(variablename)" when your loop is over - that is, when you are done reading or writing your chunk of memory.. I remember reading about this type of problem in the PDF docs, but never have ran into it myself... You need to make sure to match each lock with an Unlock... Paul >
- OS2.0 and Category Select Elia Freedman
- Re: OS2.0 and Category Select Paul Taylor
- Re: OS2.0 and Category Select Paul Taylor
- RE: OS2.0 and Category Select Elia Freedman
- Re: OS2.0 and Category Select Dave Lippincott
- RE: OS2.0 and Category Select Elia Freedman
- Re:OS2.0 and Category Select John Schettino
