AlyredB

Reply to WindowBlinds 6.0 & XP x64 Support in WindowBlinds Stardock Forums

Yeah yeah Zubaz, I know... I was just posting my reply because you were using that marketing release to justify your point that there was nothing in there.. I know it's mostly the regular BS you'd hear from any software release. However, a few points do deserve mentioning. While many apps themselves haven't been optimized for x64 yet (because they need to be coded natively), Office 2007 is one that is, and it's probably one of the

Reply to WindowBlinds 6.0 & XP x64 Support in WindowBlinds Stardock Forums

Zubaz, what part of "Premier Performance", "Greater Flexibility", "Multiprocessing and multicore processor support" and "Increased reliability and security" does not offer benefit to the home user? Not to be a jerk, but those things are why I [B]do[/B] continue to use XP 64.

Reply to WindowBlinds 6.0 & XP x64 Support in WindowBlinds WinCustomize Forums

I'm curious how many of you actually own your x64 licenses considering the majority of them were sold to smaller OEM's (newegg system builder 3packs) or IT departments. Going by the number of licenses reported sold, as well as the group they were sold to I'm not surprised for the lacking support on the product. While many of the "scene" that have posted here using leetspeak probably don't own their licenses, that doesn't excuse Stardock of being res

Reply to A few noticed bugs in 3.49[b].009 in Bug Reports Stardock Forums

Hmm, I'm unable to switch into client mode; as soon as I get the error DX crashes completely -- I have to reload it. I'm of the same persuasion; it's probably the list mode that's causing the problem. Would be nice if there was another way to click to set this, like the ability to set the parent by right-clicking on the object. Regarding the cache issue, I didn't think of that. I'll give it a shot, but I suspect there might be problems because XP32's max memory size is about

A few noticed bugs in 3.49[b].009 in Bug Reports Stardock Forums

1. When trying to use the properties page (as I don't know where else to set this) to set an object as a child, once you select Yes DX will crash: AppName: desktopx builder.exe AppVer: 0.0.0.0 ModName: user32.dll ModVer: 5.1.2600.3099 Offset: 0002bae7 Objects that are already children seem to be fine, and when going back to the release version it allows this to be set correctly. Going back into the Beta and it crashes again. 2. the Object.Rotation namespace option seems to