Hi all,

On 11/1/2007 I got my email with the link for 5_5.51.025_06.19.2007 since I run XPx64 and did not read the fine print for WB6. I hesitate to load WB6 again since SDC would not convert back to 5.x even though 5.x was archived.

So, pls tell me WB6 supports XPx64 for real... not that I don't believe you folks but the post that it works was uploaded <7 days since I got the email back from support. Support did not say, oh by the way...

Pls Let me know


btw, I'm a licensed XPx64 user and astonished at the perception many x64 users are pirates. Yes, I bought it OEM, and yes, I built my system the way I wanted it rather than make sacrifices to the packaging gods

I think x64 is more of a 'bones only' OS and I like that. I hope that Windows 7 will be even less bony than XPx64. Also, isn't everything going to x64 in Windows 7? I'm planning on building a new system in 2009-2010 with Windows 7 so I chose not to downgrade to Vista (sorry) 'upgrade'

I understand that solid state drives (ssd) will take over as the hard drive of choice and will require at least a x64 lane highway to utilize the speed efficiently. Along with Process Streaming....

I thought Vista was an interim release, like ME?? that's what I read, anyway.

Will we have this same discussion for the folks using Vistax64 in 2010? I'm surprised it took a thread and a headcount to provide ongoing customer service. I taught customer service for years and that's not it.

And that's my .21%

Ward

WB 6.01_enh supports XPx64 for real.

Thanks Psoriac! I'll download immediately

I know this is an old thread, but I just wanted to thank you guys directly for adding XP 64-bit support. As an avid graphics designer, I found Vista x64 Ultimate to be significantly slower on my system than XP64. My resources would constantly rise to 100% usage, 3DMax was a pain to get working, along with many of my games (most of which wouldn't even run without a significant amount tweaking, and even then I got a framerate drop of almost 40% over XP - 24fps in Gothic 3 on XP on maximum settings at 1024x768 as compared to 15fps in Vista using the same settings), and to top it all off, I couldn't even get drivers for some of my hardware because x64 Vista FORCES you to use signed drivers. So therefore, I won't be upgrading to Vista anytime soon. Bottom line: Don't get Vista if you intend to do anything that puts any stress on your machine.

And, if you REALLY want to get technical, here's a list of changes you'll have to make to your old XP apps to get them to work without errors in Vista.

Remove SendKeys calls and replace them with API code.
Use the HKEY_CURRENT_USER in the registry for the settings of your application. Do not write to HKEY_LOCAL_MACHINE.
If you are using ADO use 2.8 and above in your application.
If you are using XML use XML version 3.0 and above in your application
If you are using the PlaySound API, if your wave files are not PCM but mpeg layer-3 make sure your mpeg wave files are Stereo and not Mono.
If you need the Printer Setup dialog either using the Common Dialog Control, or by using the API functions, the dialog will not return the correct number of copies. The dialog will always return 1 on Vista. The way around this bug is to create your own Printer Setup dialog box and when you get the correct number of copies you will have to send to the printer multiple times to print out multiple copies. Here is a link that discusses this issue in details.
Relocate settings files, data files etc into "Common Files" (C:\Users\Public) instead of "Program Files". You should use the API calls to locate these folders because the folders are in different paths for different machines and OSs.
Per-user settings should be in a separate file located under "Application Data" and this should also be requested of the OS in the same manner.
For "Common Files" ask for ssfCOMMONDATA (or CSIDL_COMMON_APPDATA).
For "Application Data" ask for ssfAPPDATA (or CSIDL_APPDATA). To properly use these filesystem locations you are supposed to create a subdirectory for your "company name" and under that another for your "application name." Then put your settings or data under that.
Any working "document" files that are meant to be found and manipulated by the user (i.e. via Explorer) should be placed into CSIDL_PERSONAL ("My Documents") or CSIDL_COMMON_DOCUMENTS ("All Users\Documents").
DeleteSetting no longer works without a key. e.g. DeleteSetting "Mytestprogram, "General" fails to delete anything and gives an error. but DeleteSetting "Mytestprogram, "General","keyname" works fine. It seems that key is no longer Optional in: DeleteSetting appname, section[, key] as in documentation.

Thanks replaceme2 for your hard work. I use a lot of graphics software and wondered if Vista x64 would be better than XP x64. I have yet to see XP x64 crash and have pushed it well beyond my expectations of limits.

I am so glad Stardock supports this OS. I am still looking forward to 2012 to retool with the new Windows, SSDs, cloud computing, x256 etc. and I might even be a better artist by then

I am using Vista Ultimate x64 SP1 on two machines, one for video processing and one for photo processing. I use the Adobe CS3 suite (Premiere, After Effects, Photoshop, etc...). My Vista x64 machines are very stable and never crash. The only thing which make them crash is WindowBlinds causing Windows Explorer to stop working, and that about 25 times a day.

Hiya.

I just upgraded to the latest ObjectDesktop...but it won't let me DL "WindowBlinds" using that "Impulse" thingie. Am I correct in undersanding that if I was to use the 'old' "StarDock Central" I'd be able to DL the correct xp-64 compatible WindowBlinds? Should I just not use 'Impulse'? Or will they both work in conjunction?

(I've been away from OD for while...this new Impulse thing is totally new to me).

(PS: 0.21% use XP 64? If the "member no." listed in these forums is any indication, that would be about 630,000 people using XP 64-Bit... ).

Thanks!

Paul L. Ming

SDC should work fine.

If you are looking for anything just click WWW Link I found this site really interesting and time saving. have a nice searching.... ENJOY!!!!!!!

It's great to hear about continued support for XP x64. As ReplaceMe2 stated, Vista is just not ready for prime time yet. And why anyone would use the 32bit version(s) given that it eats half them addressable RAM in the first place is beyond me.

Anyone know about support for Object Desktop on XP x64 ?

Please add full support for MS Windows XP 64. I wiped my Vista off of my system because it was horrible. Vista has too many extra processes going on and thus lags the system when attempting to do actual work.

Please return XP 64 support now. Thank you.

Nope. It rewrites a lot of code. It's considered a new OS. Think of it like Windows 95. If you grab one of the first CDs of Windows 95 and try it without any patches, you'll find it's riddled with bugs, and a lot of people did indeed complain loudly about it.

Windows 7 will probably be like Windows 98. I'm guessing that a lot of people will just get the next version of Windows, which will not rewrite as much, but they'll feel better because they've been repeatedly told that Vista is flawed and that nothing will be fixed until the next version of Windows.

Which is pretty silly, because Microsoft is and will be fixing Vista.



PC Pete: Have you tried SP1 of Vista? The vast majority of file transfer issues should be fixed in the first service pack.

Yes, Microsoft is fixing Vista. Despite the naysayers, there is nothing really "fundamentally" wrong with it. It can be fixed, and they are working on the issues. My system is already vastly more stable than when Vista was first released.

BTW, all of my games work fine in 64 bit Vista, on both my GeForce 6800 and GeForce 9600. I don't have the slightest clue what gamers are whining about. I think most of them probably haven't been updating their drivers.

Windows Blinds 6 also works, although there still seems to be some theme switching bugs, especially when switching back to Aero. Switching back to Aero inevitably seems to cause DEP issues.



Most companies are using signing for their latest drivers anyways. I did have some troubles with a Bluetooth adapter, but for the most part I barely noticed the requirement. New hardware especially works great with Vista.

Signing drivers is good: It makes sure you have an uncorrupted copy of the drivers. In addition, if they have "WHQL" or "Certified for Windows Vista" on them, they have been tested for stability. It's Microsoft's attempt to try to get the hardware manufacturers' attention and try to get the drivers fixed.

The vast majority of "Vista issues" are really not Microsoft's fault: They are often the result of poor drivers released by hardware manufacturers.

FYI, check you video card drivers monthly. I don't know about ATI, but I do know that nVidia is cranking new drivers out almost monthly. The latest drivers will really solve the vast majority of complaints with 3D and gaming software.



This is very important! Microsoft locked down Program Files to prevent malicious (or poorly written) software from overwriting other software and causing system instability. Developers should be aware that Vista has a lot of under the hood rewrites and changes that are invisible to the user but very visible to the developer.

 

Seems like, here we go again.

 

http://img41.imageshack.us/img41/1072/wb7xp64.jpg

Why not report the problem before tossing threats.

https://forums.wincustomize.com/354999