(thanks to Ricardo for last minute testing, Stan for testing/patience with WSS + VAIO compatibility, Microsoft C++ dev. lead for WinSxS support, etc.)
Prerequisites:
- Microsoft Visual C++ 2005 Redistributable Package
- Internet Explorer 7
- Wireless LAN API (KB918997) (VAIOXP users only)
- Windows Media Player 11 (Windows Sidebar users)
Please read the documentation before and after installation!
- Documentation (rev. 4)
- Preview Build 2 rev. 3 build 4 (for Windows XP) [Dial-up Users] | [High-speed mirror]
- Preview Build 2 rev. 3 build 4 (for Windows Server 2003) [Dial-up Users] | [High-speed mirror]
- Application Compatibility Matrix
- Full Windows Sidebar Styler support in-box
- Full Windows Vista Sidebar RTM support in-box, including WPF gadgets (using WSS above)
- Added code for developers to "detect" VAIO
- WiX built installer! (MSI)
- Added additional API; Now support Texas Hold'Em in-box
- Added digital signatures on all libraries
- Added some preliminary code for preview build #3...
(updated January 20th, 11:11pm EST)
Q. How do I contact you guys?
A. Before using the means below, please make sure you file a bug.
1. VAIO Developers: zoronax or rafael @ fromvistatoxp.com
2. Windows Sidebar Styler 2.0 issues: http://www.stoyanoff.info/contact/
Q. The documentation (r4) refers to a manifest.xml file being present in the root VAIO folder. Where is it?
A. This has been fixed in revision 5, to be released later. You'll find the manifest.xml file in the Libraries\ folder. Do not move it.
Q. How do I register Sidebar's DLLs (sbdrop/wlsvcs)? I receive the error: The specified module could not be found.
A. This error is a result of one of the following reasons:
1. regsvr32.exe and/or regsvr32.exe.manifest are missing from the Sidebar folder
2. The regsvr32.exe.manifest is missing/incorrectly named
3. Visual C++ 2005 Redist. not installed
Q. How do I fix my currency gadget (square issue)?
A. We are trying to reproduce this behavior. Please contact us!
Q. How do I fix my Sidebar after installing Windows Sidebar Styler 2.0 (freezes and/or error)?
A. We are trying to reproduce this behavior with the help of the developer. Please contact us!
Workaround: Delete both sfc.dll and SidebarWpfExt.dll files from the Sidebar directory.
Q. How do I get WPF-powered gadgets working? -or- Why am I receiving a "Sidebar failed to initialize" error?
A. Please make sure you read all documentation. The .Net Framework 3.0 is required for WPF functionalities on non-Vista platforms. If you still have problems, please contact us!
Q. Why is my Slideshow gadget in Sidebar acting wierd (zoomed in too much, blurred, etc.)
A. This may be a bug with our IShellImageFactory interface implementation. Please contact us!
Q. Can I use more than one Sidebar at a time?
A. No.
Q. Can I hack Sidebar to run more than one instance of itself?
A. No.
Q. Why do I need to install the Wireless API update? I don't have bloody wireless!
A. This requirement is only enforced for VAIOXP users. We're sorry to impose such a requirement, however to keep our code light and less error-prone, we remove support for functionalities that Microsoft backports.
Q. Ok, why enforce the Wireless API update requirement on XP only? What about those pesky Windows Server 2003 users?
A. Microsoft has not released (nor plans to) the Wireless API update for any other platform.
Q. Can I use beta, RC#, and/or final keys?
A. Keys need to be matched with media. The use of beta keys is not supported, although release candidate builds should work. If you have issues, please contact us.
Q. What is the replacement for the __ShowPKDialog function (vslc.dll)?
A. There is no replacement. That function was temporary.
Q. Ok, how do I input a key post-setup?
A. You can't with this build, sorry. Please uninstall VAIO Preview Build #2 and reinstall.
Q. Is store.bin compatible with data.bin?
A. Yes, absolutely. The file name was altered for cosmetic reasons.
Q. Why is my shell extension not being registered? I tried to register it manually and received the error:
This application has failed to start because the application configuration is incorrect
A. Please install the VC++ runtimes, as indicated in the prerequisites section. We tried to eliminate this prerequisite by merging the runtimes into our MSI. We missed ATL and its policies, however, causing this behavior.

Sign In
Register
Help
This topic is locked


MultiQuote













