memory still has a closed program

[rondi]

When i initially open Adobe Reader (6.0) in WXP Home, it takes around
10 seconds to open. i then close it, and open another .pdf file and
it takes about 1 second. I assume it opens so quickly is because it's
still in cache---True?? this happens with lots of programs.

Does this mean memory is not being freed up after a program is
closed? is this why after an hour or so on the putr it seems to get
slower? Is there a way to Not have programs saved in memory and
therefore make my putr faster???

thanks,
ron

Please insert an E between the n & t, to reply via email.

 

[Jim in Canada]

When i initially open Adobe Reader (6.0) in WXP Home, it takes around
10 seconds to open. i then close it, and open another .pdf file and
it takes about 1 second. I assume it opens so quickly is because it's
still in cache---True?? this happens with lots of programs.

Possibly. Depends on how much RAM you have. Isn't it nice to have Acrobat
Reader pop up in 1 second rather than 10? Faster multi tasking. You can
speed it up a bit by turning off the splash screen in it's options.

Does this mean memory is not being freed up after a program is
closed? is this why after an hour or so on the putr it seems to get
slower? Is there a way to Not have programs saved in memory and
therefore make my putr faster???

If another program requires the RAM then XP clears out what isn't being used
and frees it up for other programs. Unused RAM is wasted RAM. As for after
an hour your computer getting slower. If you do a lot of Quick Time viewing,
Real Player (they launch quick-launch programs that runs in the background)
they will load enough memory resident (different than cache) programs to
slow a computer.

Could also be loaded "Spy-ware" programs slowing your system. Install
"Spybot Search & Destroy" and regularly run it to remove them from your
system. I think it is at the safer networking org website.

My P4 1gig RAM computer has been on for over a week straight now with no
slow down.

 

[Ken Blake, MVP]

In

When i initially open Adobe Reader (6.0) in WXP Home, it takes around
10 seconds to open.

Try this:

Adobe Reader Speed-Up 1.14

http://fileforum.betanews.com/detail.php3?fid=1069854583

[[Adobe Reader Speed-Up significantly decreases the amount of
time required for Adobe Reader 6.0 to start by disabling most of
the least used plugins.]]

 

[Gord Dibben]

Ken

Amazing!!

Cut opening time to a blink.

Thanks for the URL.

Gord (not OP, just a lurker)

In

When i initially open Adobe Reader (6.0) in WXP Home, it takes around
10 seconds to open.

Try this:

Adobe Reader Speed-Up 1.14

http://fileforum.betanews.com/detail.php3?fid=1069854583

[[Adobe Reader Speed-Up significantly decreases the amount of
time required for Adobe Reader 6.0 to start by disabling most of
the least used plugins.]]

 

[Ken Blake, MVP]

In

Ken

Amazing!!

Cut opening time to a blink.

Thanks for the URL.

Gord (not OP, just a lurker)

You're welcome. Glad to help.

--
Ken Blake - Microsoft MVP Windows: Shell/User
Please reply to the newsgroup

In

When i initially open Adobe Reader (6.0) in WXP Home, it takes
around 10 seconds to open.

Try this:

Adobe Reader Speed-Up 1.14

http://fileforum.betanews.com/detail.php3?fid=1069854583

[[Adobe Reader Speed-Up significantly decreases the amount of
time required for Adobe Reader 6.0 to start by disabling most of
the least used plugins.]]

 

[rondi]

Thanks for the help and the Speed-UP url.

I use Search Bot & Destroy about every other week. my memory is
488mb.

There used to be a problem with Win95 or 98 called "memory leakage" i
think, which caused memory to kinda get reduced until restarted. i
know that's a long time ago and XP should have it fixed---but i just
thought maybe there was a setting somewhere i had missed.

ron

rondi <[email protected]> happily wrote the world on Sun, 28 Mar 2004 09:29:55 -0800:

When i initially open Adobe Reader (6.0) in WXP Home, it takes around
10 seconds to open. i then close it, and open another .pdf file and
it takes about 1 second. I assume it opens so quickly is because it's
still in cache---True?? this happens with lots of programs.

Does this mean memory is not being freed up after a program is
closed? is this why after an hour or so on the putr it seems to get
slower? Is there a way to Not have programs saved in memory and
therefore make my putr faster???

thanks,
ron

Please insert an E between the n & t, to reply via email.

Please insert an E between the n & t, to reply via email.

 

[Alex Nichol]

When i initially open Adobe Reader (6.0) in WXP Home, it takes around
10 seconds to open. i then close it, and open another .pdf file and
it takes about 1 second. I assume it opens so quickly is because it's
still in cache---True?? this happens with lots of programs.

Does this mean memory is not being freed up after a program is
closed?

When a program exits, the system retains its code in Memory in case it
gets wanted again - when it is there and ready, saving time, as you
noticed. But it is only retained until some better use turns up - like
your loading another program, when it is instantly dropped. The system
is doing its best to find *some* use for RAM all of the time - even if
it is very much a 'just in case' one like this. The retention time
depends very much on how heavily loaded your RAM is - on a large RAM,
lightly loaded, a program's code may stick around quite a time.

 

[rondi]

Great explaination--thanks.

is there a way to "force" a reload from the hdd?? kinda like refresh
on MSIE while holding down the shift key.

i ask this because there are times when some of my programs just
don't work right. these are programs which run using the internet. i
have tried to disconnect inet and then reconnect. sometimes this
works, but most of the time it does not. So if i could "force" a
reload, at least i could see if somehow the program did not initialize
correctly or???

thanks,
ron

When a program exits, the system retains its code in Memory in case it
gets wanted again - when it is there and ready, saving time, as you
noticed. But it is only retained until some better use turns up - like
your loading another program, when it is instantly dropped. The system
is doing its best to find *some* use for RAM all of the time - even if
it is very much a 'just in case' one like this. The retention time
depends very much on how heavily loaded your RAM is - on a large RAM,
lightly loaded, a program's code may stick around quite a time.

Please insert an E between the n & t, to reply via email.

 

[rondi]

Great explaination--thanks.

is there a way to "force" a reload from the hdd?? kinda like refresh
on MSIE while holding down the shift key.

i ask this because there are times when some of my programs just
don't work right. these are programs which run using the internet. i
have tried to disconnect inet and then reconnect. sometimes this
works, but most of the time it does not. So if i could "force" a
reload, at least i could see if somehow the program did not initialize
correctly or???

sorry if this was posted before---i looked for it and it was no
downloaded, nor was there a reply...

thanks,
ron

When a program exits, the system retains its code in Memory in case it
gets wanted again - when it is there and ready, saving time, as you
noticed. But it is only retained until some better use turns up - like
your loading another program, when it is instantly dropped. The system
is doing its best to find *some* use for RAM all of the time - even if
it is very much a 'just in case' one like this. The retention time
depends very much on how heavily loaded your RAM is - on a large RAM,
lightly loaded, a program's code may stick around quite a time.

Please insert an E between the n & t, to reply via email.

 

[Alex Nichol]

is there a way to "force" a reload from the hdd?? kinda like refresh
on MSIE while holding down the shift key.

Short of a reboot, the only thing is to take steps to push it out. One
of the 'free up RAM' programs that are around can be made to do this -
I'd suggest the one that is in the tune up section of TweakXP. BUT use
it just for testing the problem; do *not* use these things as a regular
thing. They are just producing a spurious cosmetic 'feel good' and may
do it by pushing other things into page file unnecessarily - the file
has been known to run away as a result