PROTECTED] On Behalf Of
Kurt Kaufman
Sent: Saturday, October 29, 2005 5:08 AM
To: use-revolution@lists.runrev.com
Subject: Re: 2.6.1 very slow on Win XP?
Thanks to all who replied.
I am using no anti-virus software, and it's a pretty basic
Win XP SP1 installation.
I have a feeling that, aside
From: Chipp Walters [EMAIL PROTECTED]
Subject: Re: 2.6.1 very slow on Win XP?
To: How to use Revolution use-revolution@lists.runrev.com
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Thanks, Chip; I'll try that.
Chipp Walters wrote:
[...]
Easy to fix
Rev. 2.6.1 is *very* slow to startup on my 2 gHz Win XP box (at the point at
which menus and plugins are loaded it appears to all but hang). Also,
opening stacks and saving stacks is slow, but not always---depends on the
stack.
Standard 2.6.1 installation; no 3rd-party add-ons, etc. I do not
: 2.6.1 very slow on Win XP?
Rev. 2.6.1 is *very* slow to startup on my 2 gHz Win XP box
(at the point at which menus and plugins are loaded it
appears to all but hang). Also, opening stacks and saving
stacks is slow, but not always---depends on the stack.
Standard 2.6.1 installation; no 3rd
Kurt Kaufman wrote:
Rev. 2.6.1 is *very* slow to startup on my 2 gHz Win XP box (at the
point at which menus and plugins are loaded it appears to all but hang).
Also, opening stacks and saving stacks is slow, but not always---depends
on the stack.
Do you have a virus-checking utility that
Kurt Kaufman wrote:
Rev. 2.6.1 is *very* slow to startup on my 2 gHz Win XP box (at the
point at which menus and plugins are loaded it appears to all but hang).
One change between 2.6 and 2.6.1 is that QuickTime is loaded during
startup of 2.6.1 rather than on first switch from select to
Thanks to all who replied.
I am using no anti-virus software, and it's a pretty basic Win XP SP1
installation.
I have a feeling that, aside from the intial startup delay, it might be due
to the fact that the stacks I'm running open other stacks across a local
network. There's always a bit of a
Kurt Kaufman wrote:
Also, I opened a copy of a stack previously opened from across the
network; and I forgot that Rev does not necessarily release resources
and settings when a stack is closed. Maybe it got something confused
Kurt, that's your problem. Rev is trying to connect to that
