Sometimes when i load the F25 plug it says there is not enough memory to start but other times it just starts fine yet i haven't changed anything why is this happing?

Macs (sorry to admit this) have not a very smart memory handling, so, if you launch EVO after another program, some of the RAM used by the program may not have been freed for EVO. So try to use EVO just after having restarted your computer. Say me whether it works or not.

------------------
M'enfin!
Y'a personne qui parle français ici?

Actually, the problem is not with EVO itself, but the plug-in size. The plug-in adds resources that require EVO to need more memory. You see, the graphics and data that come with EVO run fine on the amount of memory normally, however, a plug-in will require EVO to need more memory.

To fix this, easy. Go to the info windows (command i) or File--> Get info and go to memory in the info window. From there just increase the amount of RAM EVO uses. You may need to experiment a little.

------------------
mikeeJ | Proud member of the vast right-wing conspiracy | zergess@yahoo.com
"The more corrupt the state, the more numerous the laws." - Tacitus

Quote

Originally posted by Soviet mikee:
**Actually, the problem is not with EVO itself, but the plug-in size. The plug-in adds resources that require EVO to need more memory. You see, the graphics and data that come with EVO run fine on the amount of memory normally, however, a plug-in will require EVO to need more memory.

To fix this, easy. Go to the info windows (command i) or File--> Get info and go to memory in the info window. From there just increase the amount of RAM EVO uses. You may need to experiment a little.

**

he said sometimes - not always.

------------------
DeAdBoY-
(url="http://"http://www.grybs.com/harzius")Harzius Productions(/url)
(url="http://"http://www.IcedEarth.com")Iced Earth(/url)

Quote

Originally posted by DeAdBoY:
**he said sometimes - not always.

**

And? The most likely cause is a need for more RAM.

------------------
mikeeJ | Proud member of the vast right-wing conspiracy | zergess@yahoo.com
"The more corrupt the state, the more numerous the laws." - Tacitus

Quote

Originally posted by Zacha Pedro:
(B)if you launch EVO after another program, some of the RAM used by the program may not have been freed for EVO.B)

Not really true. Macs memory allocation is based on a fixed block size. If an application's memory hasnt been released then the maximum block size isnt avalible. To see how it allocates, pick up peek-a-boo from (url="http://"http://www.clarkwoodsoftware.com/")http://www.clarkwoodsoftware.com/(/url)

But the real problem is that a macintosh application under the classic enviroment cannot allocate its own memory - you have to tell the OS how much memory to allocate.

If you experiance memory problems in EV, click on the application and press command-i, go to memory (in the popup menu at the top of the window in 8.5+) and increase the ammount there.

------------------
--sitharus
The cure for writer's cramp is writer's block. - Inigo DeLeon
(url="http://"mailto:sitharus@ureach.com")mailto:sitharus@ureach.com(/url)sitharus@ureach.com

Quote

Originally posted by blackhole: Not really true.

It's perfectly true. If you start up your computer and run apps for a few hours (launching and quitting helps), both the total free memory and the largest free block tend to get smaller by the end, even after quitting everything again. The only way to stop it is to restart, though MacOSPurge might help in some circumstances.

The other main problem is fragmentation, where the total free mem hasn't changed and the largest block got smaller, but you can usually just quit apps in the opposite order of launch to minimize this effect.

PeekABoo (as mentioned) or MemMapper work well to see how ram is allocated, but you can usually figure out just how bad things are by glancing at the about this mac window (if the total doesn't equal that used by the apps and the largest free block, try quitting apps or restarting to get enough for whatever you are doing).

Quote

macintosh application under the classic enviroment cannot allocate its own memory - you have to tell the OS how much memory to allocate.

Yes, they can, but Apple, in its "wisdom", said not to because they thought it might hurt the user experience if someone opened an app then ran out of memory while using it.(like that doesn't happen already or that getting instructed to manually allocate memory is any better)

------------------
-- Nikolaus Wegner

I have never had problems with memory... If an application doesn't start,just increase it's memory as described before.

------------------
(url="http://"http://www.wwiiplug.f2s.com/")WW2 Plug-in for EVO(/url)
Plug-in I'm working on with a couple of others.

Quote

Originally posted by nwegner:
Yes, they can, but Apple, in its "wisdom", said not to because they thought it might hurt the user experience if someone opened an app then ran out of memory while using it

It's one of these things. If it's really a problem then you just get The Reaper from (url="http://"http://www.akua.com")www.akua.com(/url). It's called 'Tempory memory', and should be used as that. Web browsers often use it. The problems occur when the system heap cannot expand any more, so the allocation API fails.

As for the memory fragmentation - yep, true. The largest avalible block is just that, the largest block avalible. If you have a small memory resident application that you open with a large application open, chances are that it will open in the middle of your memory. This causes fragmentation, and can be cured by quitting the offending application.

As for the largest avalible block thing - the system heap seems to grow readily but not shrink afterwards.

At least MacOS memory is truely protected, unlike this PC I am using. I dont think that crashing IE should crash the OS. IE crashes too much.

------------------
--sitharus
The cure for writer's cramp is writer's block. - Inigo DeLeon
(url="http://"mailto:sitharus@ureach.com")mailto:sitharus@ureach.com(/url)sitharus@ureach.com