For me, ebase hangs upon starting up regardless of what applications are
running.  I am using the runtime version.  There is no disk thrashing,
but it looks like ebase or something it depends on is caught in a tight
loop, starving the rest of the system.  

My problem may not be the same as A. Kalatiitananda's, of course.

-Kevin

Walt Daniels wrote:
> 
> -----Original Message-----
> From: Walt Daniels [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 17, 2001 11:27 PM
> To: ebase newbies; A. Kalatiitananda; Dave Shaw
> Subject: RE: [NEWBIES] ebase always crashes
> 
> My first reaction for unexplained crashes is to increase the memory
> allocation of the application that is crashing. I don't know how to
> do that for Wintel machines. Maybe someone else can chime in. Are you
> using FileMaker or the runtime when this happens?
> --
> Dave Shaw       Northwest Classics, Inc
> tel: 206-954-7526    fax: 206-625-1338
> -
> ------------------
> Wintel machines get that right unlike a Mac which always crashes if there is
> not enough memory. Wintel will just use virtual memory (possibly flogging
> the disk to death) until it runs out of disk space or some very large amount
> (maybe 2G) of virtual memory. However if you use too much of several types
> of special purpose memory (like most Adobe products) you will run these out
> of space and most likely crash many applications running simultaneously. The
> cure is to run fewer simultaneous programs. FileMaker does not seem to use
> much of GDI Free or User Free so it is usually not the cause of problems. I
> doubt if it make any difference whether you are running runtime or FileMaker
> in terms of memory usage. You can look at the system resources by right
> clicking on MyComputer, selecting properties, and selecting the Performance
> tab and looking at the System free %. If you are over 80% you are
> approaching the danger zone. All this system resource crap is gone in Win2k.
> 
> ---
> You are currently subscribed to support as: [EMAIL PROTECTED]
> To unsubscribe send a blank email to [EMAIL PROTECTED]

---
You are currently subscribed to support as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]

Reply via email to