Couldn''t Lock Memory for PLay/Record devive -Sound Forge - PC

Subject:Couldn''t Lock Memory for PLay/Record devive Posted by: omarsheriff1 Date:2/14/2001 2:47:27 PM i get this message all the time... i'm told to cancel running apps as my memeory is low... I DON'T HAVE ANY OTHER APPS RUNNING!!! it seems that my program only works when it wants to... can you help me???
Subject:RE: Couldn''''t Lock Memory for PLay/Record devive Reply by: JAZ Date:2/19/2001 11:36:29 AM Hi, Sounds like your PC might be running out of "System Resources" - I get this kind of similar problem sometimes running a print job under Internet Explorer (all versions), even with 512 MB of memory and absolutely nothing else running - the GDI fault wipes out all knowlwdge of any printers after that, requiring a reboot. You might try running "start\accessories\system tools\resource meter" and watch as memory is dispatched all over the place, while not much is running. Seems the problem is that chunks of temporary memory get used but not returned properly by an app or WIN, so SF slowly starves. Only thing you can do is to exit, maybe reboot, to clean up the fragmentation. However, you might try looking at the TASK BAR (bottom right), and kill some of those harmless looking background tasks that get loaded at every boot & fragment memory - like Virus Checker, etc etc. Unloading them from the task bar right after booting, might give you more memory resources, for that boot session. If you have insufficent DRAM to begin with, this may help - unload everything that is not specifically required during that session. Maybe even SF lost track of some memory chunks, and is strangling itself. Good luck.

Hi,
Sounds like your PC might be running out of "System
Resources" - I get this kind of similar problem sometimes
running a print job under Internet Explorer (all versions),
even with 512 MB of memory and absolutely nothing else
running - the GDI fault wipes out all knowlwdge of any
printers after that, requiring a reboot.
You might try running "start\accessories\system
tools\resource meter" and watch as memory is dispatched all
over the place, while not much is running. Seems the
problem is that chunks of temporary memory get used but not
returned properly by an app or WIN, so SF slowly starves.
Only thing you can do is to exit, maybe reboot, to clean up
the fragmentation.
However, you might try looking at the TASK BAR (bottom
right), and kill some of those harmless looking background
tasks that get loaded at every boot & fragment memory -
like Virus Checker, etc etc. Unloading them from the task
bar right after booting, might give you more memory
resources, for that boot session. If you have insufficent
DRAM to begin with, this may help - unload everything that
is not specifically required during that session. Maybe
even SF lost track of some memory chunks, and is strangling
itself.
Good luck.