HOME | DD
Voynich-Manuscript — Longhorn Evolution 2.99
Published: 2010-10-10 13:47:36 +0000 UTC; Views: 19294; Favourites: 30; Downloads: 3802
Redirect to original
Description
U P D A T E ! ! !crashed msstyle solved !
I really have to apologize for any inconveniences my vs has caused to any one, who tried it. It has been my mistake and will take care for this in the future for all coming releases.
I really hope there are no issues left or problems unsolved.
Just if anyone is interested of the reason for the problems: I have used an outdated version of vsb with saving bugs. I didn't had any problems using this theme and so I thought it's OK and released it.
I am really sorry that I have used deviants as my guinea pig unintentionally.
#############################
This is Longhorn Evolution 3.0 by SunBeam2000 - but modded. There's no need to replace any dll-files except a patched uxtheme.dll.
If you need further information, then have a look here: [link]
I have asked for permission. If you want to make further modifications, you have to ask SunBeam2000 first.
Related content
Comments: 39
Thank you for making a theme that looks nice and doesn't require me to potentially destroy my system with .dll replacements.
👍: 0 ⏩: 1
I really appreciate folks like you that takes the time to create something beautiful 4 us, so that we can a more interesting desktop! And your work is an art form! Thank you and have nice day!
👍: 0 ⏩: 1
Thank you for the comment, but I have just modified SunBeam2000's art for a more custom look. The main credits go to him.
👍: 0 ⏩: 0
yeah...if people are having problems,....its usually because of your version of vista style builder.........
👍: 0 ⏩: 1
I haven't got messages for a corrupt vs for a week. I think this version is working well.
👍: 0 ⏩: 0
what was in details the cause of the bugs: you used 1.4 version and forgot to put: in appdata-roaming-vsb, in Settings.ini: after [Settings]: FirstImageId=508??
👍: 0 ⏩: 1
I haven't heard of this bug, but when I was told about this solution, I have put this text inside the Settings.ini and then I resaved the vs.
Strangely it does not helped very much. SunBeam was so helpfull, that he has resaved my work with vsb 1.6 and then it was o.k.
👍: 0 ⏩: 1
yes Sunbeam is an as!!
👍: 0 ⏩: 0
It looks great! I always liked the longhorn themes but never cared for the oversized back button placeholder. It's nice to finally see one that don't have that.
👍: 0 ⏩: 0
"I am not starting to apologize"
So from this logic, when you crash your car into another car, will you only make an apology AFTER the other car comes out of the body shop and is all fixed? Right...
👍: 0 ⏩: 0
I am very calm. Nor am I offending you. A mistake is a mistake, I see no problem with that. But hiding messages from people (which were NOT offensive) and then talking about how are you going to 'neglect' me, while you just crashed people's PC's is not the way to go on my planet... but I can see it doesn't work for you that way. So like I said, you can have your VS. It is end of discussion for me. If you can't see what I mean, I surely can't make you see it.
👍: 0 ⏩: 0
Hehe, you can keep your VS. Crashed several people's PC's and not even a word of apology!
👍: 0 ⏩: 1
Please calm down and dont offend me any more. I am not starting to apologize because I dont know if its really working on other pcs except my one. I have only one machine to try it. As soon as i am sure there are no more problems left i will apology for any problems caused by this VS.
👍: 0 ⏩: 0
Indeed this theme was made on Vista Style Builder v1.4 and all images have been saved starting at 10000 instead of 508, which will result in many bugs including a log on loop that will require you to boot in safe mode to remove the theme, there is a fix for version 1.4 to stop that happening but I strongly recommend upgrading to Windows Style Builder v1.5, also 1.6 should be released very soon so maybe even just use the fix for 1.4 until it's released.
Anyone who has Windows Style Builder 1.5 can open the theme and then save it again and it will number the images correctly.
If you want to find out how to use aply the fix for 1.4 then have a look Here
👍: 0 ⏩: 1
Thanks a lot for your link.
👍: 0 ⏩: 0
I think your problem is that you used older version of vsb,theme wouldn work for me neither (total freeze had to use restore) then i opened it in vsb 1.5 and saved (just changed font),now work like a charm
👍: 0 ⏩: 0
Look, sorry but I see that came across kind of harsh. I didn't mean to do that. But I was only trying to prevent others from using the VS until you fixed it or looked into it. In the mean time I think you should take it down until you get to the bottom of the issue. I'm sure it's a very good vs mod once you get it to work properly.
Regards,
troubada
👍: 0 ⏩: 0
OK, you hide one of my posts -- don't do this. I am warning users as to prevent what happened to me from happening to them. You have upload problems, sunBEAM is saying you have a faulty save, and I am telling you it locked up my entire system. So censor your own release instead of my posts! That's that, I'm done commenting here.
👍: 0 ⏩: 0
Win Style Builder may have a save bug in it, but this also tells me that Voynich did not apply the VS after his final save, which is a big no-no and amounts to releasing an untested VS.
👍: 0 ⏩: 1
I have to neglect you, I have applied this theme after saving it. And it worked. The strange thing is that some don't have problems and others have.
👍: 0 ⏩: 0
sunBEAM, I understand what you're saying, but I could not even start any app... nothing would work, I couldn't open any explorer windows, and when I clicked to open any app, nothing would happen. So I would not advise people try this 3d party app approach as it may not work for them and they'd be stuck with a non-functional OS.
When I could not get anything to work inside Windows, I logged off to see if things would be accessible after logging back on, which made it impossible for me to even log on anymore... It was stuck in a loop and I couldn't get in Windows anymore. So please people, don't install this VS until the author has fixed it.
👍: 0 ⏩: 0
thank god u just save my os from disaster lol troubada! i wl not download use it for sure!
👍: 0 ⏩: 0
OK, I'm gonna flat out advise people NOT to use this.
When I applied the 3.1 theme, it went OK. When I applied the 3.0 variant, explorer went haywire and I could not access anything. Tried logging out, logging back on. Nothing. I had to put in a LivePE to boot into that so I could delete your Longhorn theme files, so it would revert to windows classic (non-aero) interface upon reboot.
I just had spent 4 or 5 hours doing a reinstall and was about the make a system backup, when I thought, hmm, let me check out DA and see if there are any more VS's to include... Mistake!
Dude, are you sure you know what you're doing??? Something is badly flawed in your VS. Luckily I had to know-how to fix it.
👍: 0 ⏩: 1
it's not so strange as it seems.. there was a safe bug in WSB when saving the finished theme.. should be fixed soon by the author..
i selected the unintentional corrupted theme by a 3rd party app, and i could easily switch back without any error or even reinstall everything..
👍: 0 ⏩: 0
Doesn't work for me. I keep thrown back to the previously used theme.
👍: 0 ⏩: 1
What do you mean with "Doesn't work for me". Don't you like it or is it really not working ?
👍: 0 ⏩: 1
I use the theme Soft7, when I try to apply your theme, I get returned to Soft7 all the time. All other themes I have installed can be activated without problems.
👍: 0 ⏩: 0
looks very nice, want to test it..
but probably there's something wrong with the download file?
winrar opens extracts 0 kb files and shows an error. i have no problems with winrar and 7z files..
👍: 0 ⏩: 1
Yes, a little bit strange. I have previously received a note, where a deviant mentions a corrupt download file. I have downloaded it and opened it, but it has worked. So I have uploaded a normal zip-File. It's much bigger, but this time it should work.
👍: 0 ⏩: 1
it works now and it looks fine...
(just resaved the theme with WSB and everything's ok)
nice work again..
👍: 0 ⏩: 0