New BootSkin Pro Beta

Fix (hopefully) for those with English versions of Vista and non-US locales

It appears the true root of the problem has been for users with an English version of Vista that were using a non-US locale (such as the UK).  Unfortunately, the code that was looking for the location of the winload.exe.mui file ended looking in the wrong folder because it was assuming there would be a folder for that locale on the system, which there is not always.  However, there has been a beta released that should address this issue.  Please let us know if you are still having the same problems and whether you're using an English version of Vista or some other language version, and what locale you have set.

Update: There is a new beta that's been published for BootSkin Pro that should help alleviate some frustration.  However, there is one thing that has been discovered that will break BootSkin that is out of our control and is squarely on the shoulders of the user.  In the Regional and Language Options menu under Control Panel, there is the Administrative tab, under which allows you to change the "Language for non-Unicode programs" locale.  If this is set to a locale that you don't have a language pack installed for, then BootSkin won't be able to find the correct resources to edit.  This isn't a "bug" necessarily in BootSkin, so much as the way that locale settings are handled in Windows.  Please let us know of any further problems that changing this setting to the "correct" locale doesn't fix.  For users with English versions of Vista, you may have to set this locale to "English (United States)" if it isn't already.  You should be able to change the settings under the other tabs without incident so long as this setting under the Administrative tab is "correct."  Thank you for your patience!

42,173 views 36 replies | Pinned
Reply #1 Top

The new beta is working wonderfully here (York, UK) for me on Vista Ultimate x64. Many thanks for working on this one  to all the guys at StarDock, it's much appreciated.

Regards,   Peter

k6  

Reply #2 Top
The new beta is working great for me also, (Cornwall, UK. Vista Ultimate x 32), thanks for sorting it out for us on the other side of the Pond, much appreciated.
Reply #3 Top

It fails to apply skins on my system. Vista Home Premium x64, Swedish (sv-SE). :(

Reply #4 Top

Does it give an error when you apply?  Or do the bootskins not show up when you reboot?

Reply #6 Top

Do you have an international edition of Vista?  Or are you using an English version with a locale outside of the US?  What are your language and locale settings?

Reply #7 Top

The new version failes here too. It applies the skin without errors, but I just see the default screen. Running Vista 32bit Home German with German locale. On my English Vista 32bit Ultimate with German locale it works fine.

Regards

Thomas

Reply #8 Top

On my system it actually tells me that it fails (there was an error applying [skinname]). Which is progress, as the last version claimed to be successful.

Reply #9 Top

OK Same thing here (error appliyng skin) but I have to ask, How do you get the new beta version cause Im using Impulse and it still give me version 1.00.035 witch is not working on my Vista Ultimat 32bit version.

Reply #10 Top

Quoting petipit11, reply 9
OK Same thing here (error appliyng skin) but I have to ask, How do you get the new beta version cause Im using Impulse and it still give me version 1.00.035 witch is not working on my Vista Ultimat 32bit version.
make sure you have "show pre-release versions" checked.  It's on the blue  orb in the upper left)

Reply #11 Top

It's working, it's working!

Reply #12 Top

It's working, it's working!
A line from a movie?  A kid yelling it?

Reply #15 Top

Problems getting it to set skin(error appliyng skin)

Uk local, home premium

Also says their is an update available.

I install the update it then resetes its self and says their is an update.

 

What version number should it display??

Reply #17 Top

First of all the beta didn't show now it does but says error retrieving data so still now go, what a cock up.

Reply #18 Top

As of 1.01[b].024 it DOES work! for me!! Go stardock team! You make me happy. :)

 

Reply #19 Top

Quoting mickeko, reply 18
As of 1.01[b].024 it DOES work! for me!! Go stardock team! You make me happy.

That is good news.  :)

For everyone else still experiencing problems:

There is a new beta that's been published for BootSkin Pro that should help alleviate some frustration.  However, there is one thing that has been discovered that will break BootSkin that is out of our control and is squarely on the shoulders of the user.  In the Regional and Language Options menu under Control Panel, there is the Administrative tab, under which allows you to change the "Language for non-Unicode programs" locale.  If this is set to a locale that you don't have a language pack installed for, then BootSkin won't be able to find the correct resources to edit.  This isn't a "bug" necessarily in BootSkin, so much as the way that locale settings are handled in Windows.  Please let us know of any further problems that changing this setting to the "correct" locale doesn't fix.  For users with English versions of Vista, you may have to set this locale to "English (United States)" if it isn't already.  You should be able to change the settings under the other tabs without incident so long as this setting under the Administrative tab is "correct."  Thank you for your patience!

Reply #22 Top

After the update 1.01[b].025 not working for me,no matter what bootskin i apply, it boots up with  the Aurora from windows vista. Running Windows vista home premium, service pack 1, U/K edition. 32 bit.  looks like there are still serious problems with this software..

Reply #23 Top

I need more information about your locale settings to address your particular issue.  If you open the Regional and Language Options menu in Control Panel and look under the Administrative tab, what is set as your system locale in the "Language for non-Unicode programs" box?

Reply #24 Top

Update: There is a new beta that's been published for BootSkin Pro that should help alleviate some frustration.  However, there is one thing that has been discovered that will break BootSkin that is out of our control and is squarely on the shoulders of the user. 

LOL.  Obvioulsy all our fault for living outside the US and leaving the system settings as default  ;)  

Have changed the system locale and all is now ok.  Is this a temporary workaround until it is fixed or will you be expecting systems to be configured in this way permanently?  Changing system locales before to something different than the user locales has caused problems with applications like SQL Server, etc.

Reply #25 Top

O:)  

Operating System
    Platform:                Windows Vista ultimate
    Version:                 6.00.6001 (Service Pack 1)
    Language:                Dutch
    System locale:           Dutch
    User locale:             Dutch

Processor
    Class:                   Intel(R) Core(TM) Duo CPU      T2350  @ 1.86GHz
    Identifier:              GenuineIntel
    Number of processors:    2
    MMX available:           Yes
    SSE available:           Yes
    SSE2 available:          Yes
    SSE3 available:          Yes

Display
    Primary:                 1280x768x32

Memory
    Physical memory:         2.086,3 MB
    Paging memory available: 4.194,3 MB
    Virtual memory possible: 2.097,0 MB

:w00t: