Sweet a month after the first post and still no resolution!! Awesome support Stardock, I'll make it so all my friends buy your products and recieve the exact same level of support I've gotten!
No, this is the ONLY Stardock product I have installed. And apparently I'm magically thinking this up, huh?
Well, I think I know what's causing the problem now, apparently it's enabling Large Icons in the effects menu; however, it's caused by WB continuously making the icons small, and each time I enabled Large Icons, that's when it grows. But how to fix it, that's another story...
Well I switch to a single Dell 2405FPW LCD and the issue continues. THAT in itself should point to a WB5 problem.
Sorry Lantec, but that did not work, same thing as usual. It wont get as worse as before, but it's still annoying as to have to keep changing each setting each time.
Ok, so i'm noticing something else that's bugging the hell out of me. For some strange reason, my icons keep reverting back to small icons, even though I have "Use Large Icons" enabled. And sometimes if I check that box and hit apply, it doesn't always apply...
Skins as in WB5 themes. That's what I mean.
And yet, I don't have IP installed. I don't think it's the shell style really, as people with the same skin as I'm using, would be having the same problem.
I've tried plenty of skins actually, but I'm more partial to the Vista ones. The only real thing I have in my msconfig is the nvidia cp app (which is the little icon that sits on the taskbar/clock), plus a few apps that I want to load on startup (MSN Messenger, GAIM, Ad Muncher). *edit* Neil, if you can truly solve this, I would definitely take back all the comments I made about the poor support, and be truly appreciative about i
While that would be a good idea, I really think that nVidia would say "go contact SD, as this isn't our problem". It's not the card I have that's the issue, I believe it's the drivers from nVidia that's interacting with WB5 (or shall I say, WB5 interacting with the nVidia drivers).
The icon issue is the only major issue I have with WB. And I still find it hard to believe that even though I've mentioned at least a dozen or so times now, that this issue did not happen until I installed WB5, usually points to the fact that, it's a WB's issue. And since I'm not the only one who has this problem, don't you think that's something then? The only thing in common we have, is an nVidia card, which is exactly what I have said in the past, interaction with nVidi
But seriously, why would it be an issue with dual monitors? there's nothing special or unique about my system, and here's the specs: Asus A8N SLI Premium AMD Athlon64 X2 4400+ 2.2Ghz Dual Core 2GB Corsair DDR400 RAM 256MB XFX GeForce 7900GT Western Digital Raptor 74GB 10,000RPM, WD 200GB, WD 320GB HDA Digital X-Plosion 7.1 DTS Co
Oi Vey, I HAVE installed the default drivers, and it's NOT an issue with the "modified" drivers I'm using at the moment. As I said, if it was an issue with dual monitor setups (two CRT's), don't you think that SD should have coded for that? I mean, dual monitor setups aren't that uncommon now a days. I know that $20 is not a lot, but you expect to get at least some sort of good service, or else I could have easily just downloaded a cr
Ok, really, How would disabling my second monitor magically fix this problem? IF it is an issue with dual monitors and WB5, then maybe they should have coded the program to actually work with it. I have plenty of other complaints with WB, but these are completely minor in comparison to this. And seriously, if I knew what I was talking about, don't you think that I would have already done this basic troubleshooting??? I told you guys already, I'm upset about this becu
Now seriously, if this issue does not happen UNTIL I install WB5, doesn't that point to it being a WB5 problem??? And honestly, I wont take my second monitor down because it's a WindowBlinds issue. Seriously people, I know what the hell I'm talking about there, I've been using computers for ages. Put two and two together, how can this be a Windows issue if it doesn't happen until WB5 is installed? As I said before, I
Well I find it really funny that not even support@stardock.com has offered support to me, or responded to my e-mails. I'm getting extremely fed up with with, and the lack of support for this product really makes me not want to use this damn damn product anymore. what a waste of $20 indeed. Thanks for
Well I find it really funny that not even support@stardock.com has offered support to me, or responded to my e-mails. I'm getting extremely fed up with with, and the lack of support for this product really makes me not want to use this damn damn product anymore. what a waste of $20 indeed.
Well I find it really funny that not even support@stardock.com has offered support to me, or responded to my e-mails. I'm getting extremely fed up with with, and the lack of support for this product really makes me not want to use this damn damn product anymore. what a waste of $20 indeed.
It's a customized driver (only the INF is modified actually), but I have had the exact same issue on standard nVidia drivers, so that's not the issue.
Well, I rebooted my PC after doing that "fix" and it seemed to work, however...After each reboot, the number keeps growing, so it's a "fix", but not a permanent fix. So it is an issue with WB5.
Ok, that fix did not work for me. So I'm out of ideas now. It's anyone's guess now. Sigh, this is really pissing me off
BTW, I use the "Icons" view in Explorer, it's perfectly fine if I use Tile or another view.
Again, I'll try these when I get home in about an hour, and will report back. If this fixes it, I truly appreciate you figuring this out. To the WB people, please see if you can find out what's causing this, as it does not happen until WB is installed. Thanks again
well now, if that's the case, what's the default value it should be? And I can honestly say that I have not messed with any of those settings before, so it has to be something with WB5 causing this as the issue does not occur until WB5 is installed. I will test it when I get home to verify if it works or not. Thanks.