Result := Result or IsNviewModuleRunning(AHandle, AProcessEntry. While Process32Next(AHandle, AProcessEntry) do Result := Result or IsNviewModuleRunning(AHandle, AProcessEntry.th32ProcessID) If SameStr(AProcessEntry.szExeFile, ExtractFileName(ParamStr(0))) then If Process32First(AHandle, AProcessEntry) then While Module32Next(AHandle, AModuleEntry) doĪHandle := CreateToolhelp32Snapshot(TH32CS_SNAPALL, 0) If SameStr(AModuleEntry.szModule, 'nview.dll') then If Module32First(AHandle, AModuleEntry) then The only "solution" that I found was to look for nView and advise the user to turn it off using the code below: function CheckForNview: Boolean įunction IsNviewModuleRunning(AHandle: THandle AProcessId: DWord): Boolean ĪModuleEntry.dwSize := SizeOf(AModuleEntry) ĪModuleEntry.th32ProcessID := AProcessId Looking at the stack trace from madExcept I could see that the application froze in nview.dll. The Delphi application stopped responding without any obvious reason. Unfortunately my laptop can't be updated to the latest version so I can't easily test with it. Has anyone else seen this issue? I've verified it with an older version of nView, but a customer with the latest version has the issue whenever he tries to move the main form or resize it. The application will move to the other monitor and any hidden forms will be visible. Choose to send the application to a different monitor. Show or ShowModal the form, then close it (form needs to have been shown at least once). Start any Delphi application with secondary forms that will be hidden when they are closed. Use a multi-monitor system with NVidia nView desktop manager. The problem can also be seen using just the IDE (show a non-docked window, close it and then choose to send the Delphi IDE to a different monitor.) The previously hidden forms are in an unresponsive state and can't be closed. Basically nView seems to 'unhide' hidden secondary forms when moving an application between monitors. ( 5.I've recently had a customer report an issue with my applications and NVidia nView desktop manager. Pieter's version may perform quite differently. NOTE: I use a home-grown inf (especially modded & tweaked for DELL's Inspiron 5150), which can be found HERE. These results can be discussed in the Benchmark Section of the Forum over HERE. But if you do spot it, I'd be interested in hearing. It's very rare so don't waste time looking for it. It's almost certainly a driver glitch and, since I've never seen it reported, I'd like to find out if it's a bug or if it's due to one of my tweaks. Now, when scrolling web pages, I'm seeing something very similar, where the browser's border occasionally leaves small lines on the text as the page scrolls up and down. Years ago there was a problem called "mouse droppings" where moving the mouse cursor around the screen would leave small lines or individual dark pixels behind. I've noticed one visual flaw with both 61.12 and 61.21.Also just a note, this won't affect your driver version, and even updating the driver won't get rid of NView. Enjoy If you have any problems, let me know. I might go back and rerun some earlier versions to see how they compare, but I suspect there's no real performance impact from either change. The install should complete, and to access the nView control panel, go to Control Panel -> Appearance and Personalization -> NVIDIA nView Desktop Manager. ![]() I don't know what the performance impact, if any, might be. Since my previous 61.12 benchmark, I've installed the Dell Inspiron 5150's new A34 BIOS and DirectX 9.0c.Note The get-EventViewer function will only allow you to view. ![]() You will need to re-enter the function each time you open a new PowerShell window. You can now use the command get-EventViewer at the PowerShell prompt to view your Custom Views. The tiny drop in scores isn't significant and may just be due to whatever was happening in the background on my laptop during the test. To work around this issue, copy and paste the following function into a PowerShell window and run it.
0 Comments
Leave a Reply. |