Path: chuka.playstation.co.uk!scea!peter_alau@playstation.sony.com From: Charles Nicholson Newsgroups: scee.yaroze.programming.3d_graphics,scee.yaroze.beginners,scea.yaroze.programming Subject: greets to all Date: Fri, 08 Jan 1999 15:40:32 -0500 Organization: SCEA News Server Lines: 31 Message-ID: <36966D40.47664F57@vassar.edu> NNTP-Posting-Host: toshiba-173-23.nycap.rr.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.07 [en] (Win95; U) Xref: chuka.playstation.co.uk scee.yaroze.programming.3d_graphics:1123 scee.yaroze.beginners:664 Hello all. Just got my Yaroze last week and i have my first official maddening problem with it. I wrote up a simple compression/file packing library that compresses multiple directories into one big .lib file so i don't have to reference everything with defines and offset values. This works fine on my pc (watcom, dos4gw), but it does the strangest thing when i port it to the Yaroze. It finds the correct offset to start decompressing from in the file (in mem.. it's at 80009000), it validates it by reading a signature off the beginning of the correct entry, but when i walk through it (i mean walk, no writes at ALL, just reading...) to decompress, the yaroze crashes. But it doesn't crash consistently. I threw a c file in and uncomp'd it, read it out, it worked fine. I threw a tim in there, it gets halfway through. It gets better. It's simple huffman compression (binary tree- the file format i have is "header, tree, data". What i was doing was setting a pointer in memory to the tree and the data, and uncompressing from there. What ended up working was creating two more pointers, mallocing in one the size of the tree and the other the size of the data. I memcpy'd the data from the file in memory to these malloc'd arrays, and now it works more frequently, but it still is not consistently functional. I am 100% on the compression/decompression routines and file formats, and i am POSITIVE that they function properly. can anyone tell me what on earth is going on? I figured i might have been walking over my code, but that starts at 80100000 and i know my data file is not that big (usually about 12k)... is there something about memory i just don't know? thanks a lot, talk to you all in the future.. -charles nicholson