Ricsi wrote: >>so this is not the problem. (IMHO it's a frame problem ... do you have frames turned on ??)<< Ricsi, I just went into ARACHNE.CFG and changed Frames to No and got the same result --- it crashed with the same message. So, I would assume that the problem is something different than frames. It seems that Michael P. has gone into a defensive position regarding memory problems, certain that there aren't any problems. I thought/hoped that when he made his second trip to San Jose last year to correct some memory problems that he would acknowledge that there *may* be some. Roger Turk Tucson, Arizona USA
- Real Bug : (was Memory Allocation Error v. 1.60b2... Clarence Verge
- Re: Memory Allocation Error v. 1.60b2 Glenn McCorkle
- Memory Allocation Error v. 1.60b2 Richard Menedetter
- Re: Memory Allocation Error v. 1.60b2 Clarence Verge
- Memory Allocation Error v. 1.60b2 Richard Menedetter
- Re: Memory Allocation Error v. 1.60b2 Clarence Verge
- Re: Memory Allocation Error v. 1.60b2 Kali McLaughlin
- Re: Memory Allocation Error v. 1.60b2 Roger Turk
- Re: Memory Allocation Error v. 1.60b2 L.D. Best
- Re: Memory Allocation Error v. 1.60b2 Roger Turk
- Re: Memory Allocation Error v. 1.60b2 Samuel W. Heywood
- Re: Memory Allocation Error v. 1.60b2 Bernie
- Re: Memory Allocation Error v. 1.60b2 L.D. Best
- Re: Memory Allocation Error v. 1.60b2 L.D. Best
- Re: Memory Allocation Error v. 1.60b2 Glenn McCorkle
- Re: Memory Allocation Error v. 1.60b2 Glenn McCorkle
- Re: Memory Allocation Error v. 1.60b2 Clarence Verge
- Re: Memory Allocation Error v. 1.60b2 Samuel W. Heywood
- Re: Memory Allocation Error v. 1.60b2 Bernie
- Re: Memory Allocation Error v. 1.60b2 Glenn McCorkle
