I finally solved this problem, though I have no idea why the solution worked. The problem came down to the directx settings DirectDraw Acceleration and Direct3D Acceleration becoming disabled when WindowBlinds was running. (AGP Texture Acceleration for some reason is always disabled.) I reduced my AGP Aperture size to 32MB in the BIOS, and this cured the problem. (I tried various AGP Aperture sizes and one enabled Te
I use a driver cleaner; that's why I wrote that I 'nuked' the Catalyst drivers. Driver Cleaner Pro is essential. I've now found how to restore normal operation. By retesting PCI and AGP read and writes, the system comes up working properly with the PCI settings on and the AGP settings off. Somewhere WB is causing these settings to get screwed up, but that is not necessarily due to a fault in WB
I have another thought on this. There are two separate problems. 1) The bug somewhere that is causing the go-slow. 2) The fact that once the go-slow arises a nuke of Catalyst is needed to clear it. On point two I think that ATI could be storing a persistent flag in the registry once it gets its knickers in a twist, that only a clear-out of the registry resolves. </fo
I don't overclock. I have no confidence in ATI's software and would not buy another ATI card. I've switched to the latest Omega drivers; they are based on 5.12 so this might solve the problem. I've only seen the ati2dvag error since installing WB, but it is not a problem unless I fiddle with the ATI Smartgart and vpu settings. Could WB be pushing the 9200 hardware in 2D harder than a game pushes it in 3D? And where would ATI preserve the "throttle" state for i
I closed my system yesterday after running a session at the normal gui speed with WB. On booting today, the gui system was again glacial. I changed to the 'Classic' session and explorer crashed with an unhandled exception during the 'Please Wait' phase. I rebooted and the gui had changed to Classic, but was still running glacially. I changed to 'Classic' again in the WB control panel to be sure and rebooted. Same thing. Unloading WB makes no difference. <b
32 bit.
I don't know. Next time the slowdown occurs I will try it and post here. WB is currently running properly after a fresh reinstall of WB and Catalyst following the BSOD episode detailed elsewhere.
Those hex status numbers are supposed to be, and were written in the source as: C followed by six zeroes followed by 5, then in parentheses eight zeroes and eight zeroes.
stardockcrash Whilst changing skins in the WB control panel, during the 'Please Wait' screen, the monitor lost video a couple of times then the following blue screen occurred: Stop: c000021a {Fatal System Error} The Windows Logon Process system process terminated unexpectedly with
The same slowdown occurred yet again after I adjusted the WB settings. Is there anyone at Stardock able to help me solve this problem?
As I reported earlier, cpu idle was typically 80-90% I watch Process Explorer continuously, and cpu usage did not increase during the times that the graphical system was running slow. All other processes ran normally. The slowness was confined to the gui - screen refreshes, etc - making the system feel unusable. There was no message about VPU recover. Further, I run no extraneous services, and little more than the svchost stuff, explorer and procexp - and WB co
Thank you Neil. I'll try and explain it again. After installing WB, Windows slowed to a crawl. That was the subject of my first post. I got WB working properly after nuking then reinstalling the ATI Catalyst drivers as scorpio-logic suggested here. With a properly running system I then adjusted some settings in the WB panel. Immediately Windows slowed down again. This slow down did not occur after another reboot, it occured as soon as I adjusted the WB settin
I was fiddling with the WB configuration and again my system started running like a dog, after checking the two boxes on the System Information screen. I uninstalled the Radeon Catalyst drivers and unloaded WB on reboot. The system ran at the same low speed without the Catalyst drivers and without WB as it did WITH the Catalyst drivers AND WB. It is as if WB disables the 2D acceleration of the Catalyst drivers. Another reinstall of Catalyst fixed the problem, b
No I didn't uninstall the trial; that was probably my big mistake - I thought that an upgrade would occur. I did though nuke all of the Stardock stuff before reinstalling it the second time. Anyway I've just totally nuked all of the ATI software and reinstalled the drivers (without the Control Center) and all is well apart from the per pixel acceleration. Thank you all for your responses. I wonder if any Stardock staff can explain what happened (in technical te
Re Omega Drivers, the question is - why would the standard catalyst drivers fail in the five minutes between running the demo and running the full program? Is not the core WB code identical in both?
I'm not concerned about the pp shading at this stage. Still, it seems that paying for the full version has conferred no benefits, only, on the contrary, trashing my system. My computer is intolerably and unuseably slow since the upgrade to the full Window Blinds product but the demo version worked properly - apart from the pp shading of course - right up until I upgraded. I already have the 5.13 Catalyst drivers installed, but with the Control Center, not the Control Panel
I ran the trial WB5 and it was fine , using the Noire theme, with ppb switched off. Upgrading to the full version has caused my machine to slow to a crawl. It takes four seconds to scroll one page in Firefox, for example. CPU idle is about 80
Stardock Forums