Zargon Zargon

WindowBlinds 6.3 Support Thread

WindowBlinds 6.3 Support Thread

Please post any issues or questions for the community about WindowBlinds 6.3 here.

WindowBlinds 6.30 Release
------------------------
This release for WindowBlinds 6.30 adds new skinning options for layer blend modes. See the betas of SkinStudio 6.30 to check that out.

Support for a number of blending modes for layers
Breadcrumb bar text positioning no longer changes depending on if the window is maximized
Do not shift text when button pressed skin option (edit in SKS)
64 bit has had some tweaks to handle bad sizing of the addressbar
Shadow effect now works on very transparent things like the diamond taskbar clock text.

77,405 views 124 replies
Reply #53 Top

Quoting Neil, reply 2
6.29 is the beta of 6.3
End of Neil's quote
Thanks Guys I Didn't Realise That 6.29 Is The 6.3 Version Silly Me Anyway Thanks For Your Replies  :D

Reply #54 Top

WindowBlinds 6.30 has been released!

Reply #55 Top

I download today from SDC ( not impulse ) the windowblind 6.30.094 , everything ok , but after restart it seems that the version is the  6.2 ( built 61*86 )

My OS is Xp service pack 3 Greek version

 

 

Reply #56 Top
I upgraded to 6.3 today and any program that uses MS's .NET framework 2.0 crashes when trying to open a browse window. Example: Launched XML Notepad 2007 then clicked on the open icon to open an XML file and I get this: See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Runtime.InteropServices.SEHException: External component has thrown an exception.
at System.Windows.Forms.FileDialogNative.IFileDialog.Show(IntPtr parent)
at System.Windows.Forms.FileDialog.RunDialogVista(IntPtr hWndOwner)
at System.Windows.Forms.CommonDialog.ShowDialog(IWin32Window owner)
at XmlNotepad.FormMain.Open()
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
XmlNotepad
Assembly Version: 2.5.2798.17143
Win32 Version: 2.5.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/XML%20Notepad%202007/XmlNotepad.exe
----------------------------------------
Microsoft.XmlNotepad
Assembly Version: 2.5.2798.17141
Win32 Version: 2.5.2798.17141
CodeBase: file:///C:/Program%20Files%20(x86)/XML%20Notepad%202007/Microsoft.XmlNotepad.DLL
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data.SqlXml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Data.SqlXml/2.0.0.0__b77a5c561934e089/System.Data.SqlXml.dll
----------------------------------------
System.Xml.Xsl.CompiledQuery.1
Assembly Version: 0.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Data.SqlXml/2.0.0.0__b77a5c561934e089/System.Data.SqlXml.dll
----------------------------------------
Microsoft.mshtml
Assembly Version: 7.0.3300.0
Win32 Version: 7.0.3300.0
CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:



When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
This also happens when trying to do a Save as in Handebrake. If I removed the theme in WindowBlinds and use Aero everything works fine.

Reply #58 Top

6.30 has been republished tonight to hopefully correct that .net issue on 64-bit. And to prevent downloads from looping with SDC installs.

Kris

Reply #59 Top

Vista Ultimate 64 bit. I'm re-installing now. Will let you know how it goes.

 Update:

 

It works

Reply #60 Top

I am so pi****d

 

When will you guys the udpates right with impulse and XP

 

AGAIN (3rd timeminimum now) after updating wb6 I get an error message on startup  about wb needing another bootup and as always the stupid impulse routine didn't copy wblind.dll and wbserv.dll to the place it should on startup

 

I never had those problems with sdc -whats up with stardock - I am complaining about this every other update -you know what, Impulse is leaving my machine - that peace of software stinks !!!!

 

Ruben

Reply #61 Top

6,3 broke the XP64 support I'm afraid, the frames around the windows just stopped working.

Reply #62 Top

We do not support 64 bit XP as an OS I am afraid, but we are seeing if we can make it install 6.2 files on XP 64 instead.

Reply #63 Top

Sorry, but I understood XP x64 support was added with the update to 6.1. :S

 

 

I wouldn't be bothered with it if it wasn't for that pesky hardware issue those nforce 4 chips are having, preventing me from using Vista.

Reply #64 Top

I had to remove 6.3 from my Windows XP 64 bit system, screwed up my toolbars, 100% cpu usage and visual studio crashes.

Reply #65 Top

I had to remove 6.3 from my Windows XP 64 bit system, screwed up my toolbars, 100% cpu usage and visual studio crashes.
End of quote

 

From 2 replies above the one you have posted, by Neil Banfield, WB Dev.

 

We do not support 64 bit XP as an OS I am afraid, but we are seeing if we can make it install 6.2 files on XP 64 instead.
End of quote

Reply #66 Top

plzzz help me i bought wb 6.2 enhanced last month it was working fine last week just to upgrade it i installed impulse and upgraded it then no problem .. i just wanted to try my colours think green n installed ...  theN I  unistalled it ...

along with it.. it seem windowblinds also uninstalled ... then i reinstalled it but i couldnt activate it... when i enter the activation key it says error in activation... after complete uninstallation of mycolours the green icons of all my folders also not  getting chang....  .... plzz somebody help me...

Reply #67 Top

i reinstalled my colours ... & uninstalled it.... then installed SD central and installed window blinds from sd central and activated it...  now its working fine for me..............  i would like to suggest all to install windowblinds through stardock central.. and product activation also soo smooth....

Reply #68 Top
Well somone better tell Neil that the product page says they do support 64 bit and they did since 6.1 here are the system requirements of the  main page fix it I paid for it.
 
 
System Requirements
Windows Vista (32-bit or 64-bit) or Windows XP/2003
Windows 2000/ME/98 users can use WindowBlinds Classic (v4.6).
Minimum screen resolution: 1024 width and 768 height
60MB free drive space
256MB RAM
Reply #69 Top

It doesn't specify about XP 64bit, but it does support Vista 64bit.

Reply #70 Top

i have a problem with the right-click menus, they just turn black, on any skin

WindowBlinds version : WindowBlinds 6.3 (build 67 x86)

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
Your machine supports per pixel borders on WindowBlinds skins.

(Monitor Plug and Play) 1 is attached to NVIDIA GeForce 6150SE

Wblind.dll         2008/09/17 08:05:20
Wbsrv.dll         2008/09/16 08:44:42
Wbconfig.exe         2008/09/16 08:44:32
Wbload.exe         2008/04/26 16:14:14
Wbhelp.dll         2008/04/26 16:14:07
Wbui.dll         2008/04/26 16:14:05
Tray.dll              2008/04/26 16:14:21
Screen.exe         2008/07/15 11:31:09

A screenshot of the menu on desktop:

Reply #71 Top

What other applications do you have running on your PC?

Do you have ay tools running which make menus semi transparent (apart from WB)?

Reply #72 Top

i have vista inspirat 2, but the semi tranparence is disabled, i think the problem has to do with the shell default themes and windowblinds, when i "pause" the processes with the alacrity pc (including the shell themes but no windowblinds) the problem is temporaly solved

Reply #73 Top

Im having a problem with it skinning text in IE (see pic) is there a way to stop this without changing the system colors?

Reply #74 Top

Why isn't there a "revert to default" button somewhere?
If I install and apply one skin, then does the same with a second and a third, somehow the result is a combination of the three.
It is seriously annoying as currently it's almost needed to reimage the drive between skins to get rid of the garbage inbetween.

For instance, the image below shows a thingy left by either the Azul3D or the Dark Knight skin which for now seems to require
an image restore to remove. (applying another skin doesn't remove it):

Annoying

Reply #75 Top

hardalis: that image will change on new explorer windows or when you restart your pc.