The shareware version of WB5 will only enable per pixel on the 4 per pixel skins included. Any other per pixel skin will act just like it does on machines which do not support per pixel borders. So if you downloaded the arrow skin, it will work, but without per pixel borders.
Neil Banfield
Are you finding firefox is showing up with no titlebar?
jsawiuk: I would guess the server is still processing upgrades. Unsure why it is taking quite that long. I will get the status of the e-mail sending checked & post here to let you know.
Izzee: a 9800 does support per pixel. You can see if your drivers are ok by going to the system information page in wbconfig. Try the aura skin and you should see per pixel alpha running just fine on your PC (without nagging you about it as its an included skin)
You should be able to install on all 3 computers. If you have a problem & hit an activation limit at any time, you can e-mail [email protected] who should be able to reset it for you. Each sig.bin is per machine though, so you cannot take the sig.bin from one PC and use it on another.
Out of interest, if you reboot & then do ctrl-alt-del on the secondary keyboard, can you then use multiplicity to enter into the username & password box? After you have done that, you should be able to fix it by following the instructions below. It seems you have a security setting enabled. Run gpedit.msc. Go to local computer policy->computer configuration->windows settings->security settings->local policies->security option. Then
Which skins do this?
Lotherius: an interesting question. I will check for you what happens.
Please install SmartException (free part of SDC) and see if it catches any info on the crash. If you set WB to use no skin (classic), does the problem still happen?
Look for a .cmd file autorunning on your PC - use msconfig. Thats why sig.bin is locked.
Which beta build were you using?
You should not need to activate WB on different accounts assuming WB is installed in the same directory for all users (I.e you just installed WB once on the PC and then just run wbconfig on the other users) If you still have activation issues, please e-mail [email protected]
Sorry, could you post dates & sizes of just the files please.
Please post a directory listing of your WindowBlinds directory
Shell menu?
Wbconfig fails to run? Please post a directory listing of your WindowBlinds directory.
Fauhler: that is the correct install directory on 64 bit.
Denon36 is waiting for the free update mail.
The 32 bit installer will install the 64 bit version on a 64 bit OS.
Izzee: If it comes up every time you change skin then you are trying to apply a per pixel skin. What is the name of the skin you are trying to apply?
#145, The free upgrade is provided to people who purchased it from 1st September 2005. Before that its a $15 upgrade fee.
It seems it may take a few hours for all the accounts to be updated and e-mails to be sent.
Izzee: The one at bootup is to remind you that you are using the shareware build and how many days you have left. Its called a nag screen for a reason! How many times do you reboot if its causing such an annoyance? The purpose of the shareware version is to give you a taste of the application and then for you to purchase it if you like it.
dscroggie: Use https://www.stardock.com/support.asp and enter your details and you should get sent the latest links along with your serial number.
There are 2 different popups. One says in plain text that the per pixel in this skin is not supported in the shareware version. The 2nd (which appears at bootup) has the price & a list of features. So if you keep on getting the per pixel popup then its because you are trying to use a skin which is a per pixel skin, but is not one of the permitted ones in WB5 shareware.