CVF on Vista

[dannycat]

I've recently changed laptop from one running XP to one with Vista Home Premium(6.0.6000)whereI am currently developing a large application using CVF 6.6C. Everything works fine on XP but the program is very slow in placesusing the Vista laptop (which is faster and of generally higher spec). The IDE works fine (apart the Array Visualizer which never worked for long on XP anyway!) but occaisionally dies saying that it is not compaible with Vista. I have not managed to pinpoint the exact reason for the slowness but if I pause in the debugger it usually displays NTDLL! NVOGLV32! in the Disassembly window. I guess the NVOGLV32 is a OpenGL file (the program uses OpenGL to display graphics), but the piece of code is not actually doing any graphics operation. I find this very frustrating as I use the Vista laptopfor mainly fordevelopment work as it compiles and links faster.

Has anyone else experienced similar problems?

Does anyone have any suggestions on how to avoid this?

It is difficult to disable hardware acceleration which may be a possible cause.

Another possible cause is that the deallocation of allocatable arrays is causing the problem. This processappears slower on vista and sometimes a fatal error occurs stating that there is no available virtual memory where according to the Task Manager there is plenty.

I think my only option is to switch to IVF but thismay introduce more potential incompatibity issues with third party modules such as Lahey's SQLLIB and my not solve my original problem.

[jimdempseyatthecove]

There is something on the NVidia developers forum indicating problems with the Instrumented Driver as opposed to the Standard (non-Instrumented Driver). You might poke around with Google to find other information.

BTW, I use the Array Visualizer. Very happy with it...

Except for an annoying memory leak in ArrayView.exe. I solved it by having the application close an instance of ArrayView and reloading a new instance. Other than for screen blanking it works for me. I found it easier to do the graphs in Array Visualizer than in OpenGL. A major plus is ArrayView.exe runs as a separate process. On a multi-core system even a single threaded application can "automatically"distribute the computations to one application and the display work to a second application (multi-threading by way of multiple processes).

Jim Dempsey

[dannycat]

I have tracked down one of the causes of the problem. I rationalised the calls to glFlush to the front buffer and the program performed better, although not as well as on XP.