From: Sherlock on
Any ideas.. a work around.

I have XP at the office and Windows 7 - 64bit at home.
Using the same repo, same path etc.... I get very different
performance when compiling.. but not the way you would think it should
be.

I find the 64bit Windows 7 with VO .. at times painful to use.
An example I have say a LIBRARY that I want to create the DLL and then
connect either the libary source of the DLL to my main EXE... the
process starts off fine but towards the end of the compile cycle..
you get some NO RESPONDING on the caption bar. Sometimes nothing
happens and just sits there and the CPU usuage is ZERO.
I have not control of the compile dialog window and if I want say 3-5
minutes it will eventually finish.

I have found by trial an error if I click on programs and back
sometime it will "wake up " from its hibernation.

Searching Google re similar issues this seems to be well know.

Has anybody else had this problem and what did they do to resolve it.
To me it is like the RESOURCE COMPILER which runs in the background is
hung for awhile.

Phil McGuinness
From: Geoff Schaller on
Phil.

Not related. I have used W7 64 bit with VO ages and it is fine. There is
something else afoot in your PC. AV maybe?

Geoff


"Sherlock" <sherlock(a)sherlock.com.au> wrote in message
news:0d284b66-59d4-47b4-b30f-211fdbc3bb47(a)a9g2000prd.googlegroups.com:

> Any ideas.. a work around.
>
> I have XP at the office and Windows 7 - 64bit at home.
> Using the same repo, same path etc.... I get very different
> performance when compiling.. but not the way you would think it should
> be.
>
> I find the 64bit Windows 7 with VO .. at times painful to use.
> An example I have say a LIBRARY that I want to create the DLL and then
> connect either the libary source of the DLL to my main EXE... the
> process starts off fine but towards the end of the compile cycle..
> you get some NO RESPONDING on the caption bar. Sometimes nothing
> happens and just sits there and the CPU usuage is ZERO.
> I have not control of the compile dialog window and if I want say 3-5
> minutes it will eventually finish.
>
> I have found by trial an error if I click on programs and back
> sometime it will "wake up " from its hibernation.
>
> Searching Google re similar issues this seems to be well know.
>
> Has anybody else had this problem and what did they do to resolve it.
> To me it is like the RESOURCE COMPILER which runs in the background is
> hung for awhile.
>
> Phil McGuinness

From: Ginny Caughey on
Geoff,

I agree. If anything my compiles are faster, but my machine has a lot of RAM
and SS disk.

--

Ginny Caughey
www.wasteworks.com




From: Robert van der Hulst on
Hi Sherlock,
On Sun, 20 Jun 2010, at 18:26:49 [GMT -0700 (PDT)] (which was 3:26 where I live)
you wrote about: 'Windows 7 - 64bit and slow compiling VO2.8 build 2836'

> I have XP at the office and Windows 7 - 64bit at home.
> Using the same repo, same path etc.... I get very different
> performance when compiling.. but not the way you would think it should
> be.

> I find the 64bit Windows 7 with VO .. at times painful to use.
> An example I have say a LIBRARY that I want to create the DLL and then
> connect either the libary source of the DLL to my main EXE... the
> process starts off fine but towards the end of the compile cycle..
> you get some NO RESPONDING on the caption bar. Sometimes nothing
> happens and just sits there and the CPU usuage is ZERO.
> I have not control of the compile dialog window and if I want say 3-5
> minutes it will eventually finish.

> I have found by trial an error if I click on programs and back
> sometime it will "wake up " from its hibernation.

> Searching Google re similar issues this seems to be well know.

> Has anybody else had this problem and what did they do to resolve it.
> To me it is like the RESOURCE COMPILER which runs in the background is
> hung for awhile.

In which folder is VO installed ?

--
Robert van der Hulst
AKA Mr. Data
Vo2Jet & Vo2Ado Support
VO & Vulcan.NET Development Team
www.heliks.nl

From: Sherlock on
Geoff

Using Microsoft Essentials.. on the AV side..

Phil