From: Rob B. <rb...@qu...> - 2001-08-03 19:27:08
|
At 3:20 PM -0400 8/3/01, Ryan Casey wrote: >> At 2:18 PM -0400 8/3/01, Ryan Casey wrote: > ><snip> > >> >Does Mac Classic have virtual (disk cache) memory at all? Should I just >> >give up and work on the OSX port (especially with OS10.1 coming out >soon)? >> >> Yes - open up the memory control panel, enable virtual memory, set it >as >> high as you like and reboot. However all this is doing, is setting the >> size of the single address space which all apps share on OS9 or earlier. >> OS9 and earlier still have partitions and you would have to change that as >> well. > >*sigh* Apparently I missed that section. I did see the part about how much >physical RAM I had, but not the spinbox below... > >Anyway, it was 32 and I upped it to 100. I rebooted, and set my app to use >1000 (default) to 100000 (preferred) memory. I was then able to load 3 sets >of 61 images...more than should be needed. Now, after I check tbcload to be >sure it works, I should be able to release a Mac 9 version, and move on to >finishing Solaris and OSX. Thank you! Excellent - simple memory hog problem and not something more subtle or evil... >> Another thing to do is make sure you have MacsBug installed, then you >> can do a "stdlog" command which will dump a fairly detailed machine state >> to a log file at the time of failure. This includes a stack crawl and >heap >> dump which can be inspected after the fact. The 'hc' command can be >> invoked to check heap integrity periodically also. > >For future reference, are these free? Do you have a location for them? I >am really not a Mac person, I just managed to get one next to me to look at >this, since people have been clamoring for a Mac port for a while. Yeah, MacsBug is free off the Apple site. I'll mail you a URL after lunch.. -- Rob Barris Quicksilver Software Inc. rb...@qu... |