QBSnap
4 messages in this thread
I reported a problem a while ago with QBSNAP where it would leave FAST
memory horrible fragmented, so much that QBT wouldn't run properly on my
Q105S drive (GVPII Controller w/ 2M fast ram). I have to do a NoFastMem
before doing a QBSnap and everything turns out ok. I have a stock A2000
with BB. Has this problem been fixed?
John
John,
Double check to make sure you have the 1.5 version of Quarterback Tools. I
don't see anything in the notes that relates to this particular problem but
the No Fast Mem clue should be helpful.
Randy Brooks
Central Coast Software
a division of New Horizons Software, Inc.
Yes, I definitely have version 1.5 of QB. Further analysis of the problem,
however, shows that memory is being released, it just seems to be
fragmented. Running the "avail" command before a qbsnap and running
"avail" after shows that the amount of free memory for both chip and fast
have not changed but the "largest" chunk went from 1.7M to about 400K. Can
anyone else duplicate this?
John
John,
We haven't been able to duplicate the effect on any of the machines here in
the office, though I suspect that this is due to their all having
contiguous fast ram. I will try and duplicate this effect with my machine
at home that has your basic mix and match memory architecture. I have had
reports that running NoFastMem before and after running QBSnap helps in
this regard but don't hold me to it.
Randy Brooks
Central Coast Software