Homebrew unpacking moonshell2 skins

[twiztidsinz]

Well I did have a false hope that maybe it could have somehow been me and my .bat making skills...but nope, it still doesn't work on my computer (as my previous tests on my computer have horribly told me).

What does happen then? What OS do you have?

(the skinname must be without spaces)

MakeSkin.exe crashes.

I'll take some screenshots and show you the problems... but I don't think it will help any.

 

[CannonFoddr]

Well I did have a false hope that maybe it could have somehow been me and my .bat making skills...but nope, it still doesn't work on my computer (as my previous tests on my computer have horribly told me).

What does happen then? What OS do you have?

(the skinname must be without spaces)

Well I've got XP Pro 32-bit & the skins I've been trying are 'nekoskin.skn' and 'default.skn' - & as you see there's no spaces in the names

What happens is I see a quick flash of a window (I think it's the same window you see when you MAKE a skin) and that's it - nothing else

> Tried it through CMD (Command Prompt), 'Drop-&-Drag' and even through different BAT's files
> Tried it in different folders - even the root directory of c: drive, in case it was because of long path names
> Tried it on a VERY old laptop, that has virtually NO software installed (Just the OS & a memory manager) just in case there was a security program (Firewall/Antivirus) stopping it from running
> Tried it ALSO with Delphi (v4 - that's the 'newest' version I've got) installed - just in case the file calls a specific delphi DLL or something that I haven't got installed
> Looking through the 'source' code - I see a few references of ZLIB, so found a zlib.dll & installed that - just in case

Surely if it uses a ZLIB routine to Compress - surely there's a ZLIB 'Uncompress' routine somewhere that will do the job.
Even if some1 made a seperate Window App - it MIGHT be better than struggling with a DOS command program

 

[jurassicplayer]

Well I did have a false hope that maybe it could have somehow been me and my .bat making skills...but nope, it still doesn't work on my computer (as my previous tests on my computer have horribly told me).

What does happen then? What OS do you have?

(the skinname must be without spaces)

xD Don't worry, I know how to use the command line. The makeskin.exe is just really wonky. Seems to work on some few computers, yours and maybe one or two others that have tried, but it just doesn't seem to want to work for the rest of us xD. I didn't quite have the ability to test out the makeskin.exe as extensively as Cannonfoddr, but as far as we know, we have no idea what is wrong with our computers xD.

 

[twiztidsinz]

Also, localization doesn't seem to make any difference.
I've run it through AppLocale in Japanese, Korean, Simplified Chinese and Traditional Chinese with no difference in the functionality.

 

[Dark^'^Knigh]

Ive got headache

edit: now we have to put an anti-piracy on our skins now XD, jk.

That is what I worry about too xD. Unfortunately, I can't think of a way to stop it apart from modifying our current skins so that it DOESN'T work with the makeskin.exe...

Why on earth did you two give this guy links to files & info, if you did not want him to succeed in his quest? I find it very interesting though, that you guys are trying to get it to work yourselves anyway.

 

[jurassicplayer]

Why on earth did you two give this guy links to files & info, if you did not want him to succeed in his quest? I find it very interesting though, that you guys are trying to get it to work yourselves anyway.

xD its because the two of us are companions in the lack of a DS to see what the skins look like. This is why my previewer is important to me (since I decided to actually make a skin again). Also, the power of curiosity compels me to attempt figuring out why the hell it doesn't work on my computer.

 

[twiztidsinz]

Why on earth did you two give this guy links to files & info, if you did not want him to succeed in his quest? I find it very interesting though, that you guys are trying to get it to work yourselves anyway.

Because not everyone wants the source of their skins distributed.

And just because you don't mind Skin A's source being distributed, doesn't mean you will want Skin B's source distributed.

 

[jurassicplayer]

Why on earth did you two give this guy links to files & info, if you did not want him to succeed in his quest? I find it very interesting though, that you guys are trying to get it to work yourselves anyway.

Because not everyone wants the source of their skins distributed.

And just because you don't mind Skin A's source being distributed, doesn't mean you will want Skin B's source distributed.

xD I'm also planning on adding a little extra to attempt keeping my stuff from being distributed (a middle class nub might be able to figure out what I am going to do, but definitely not the freshies).

 

[CannonFoddr]

@ twiztidsinz: I notice you seem to have Visual Studio (Basic/C#/.NET??) installed - so I looked up the error code (0xC000005) & found this little titbit

The Stop 0x50 message indicates that requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0x50 messages.

Possible Resolutions:

• If you added new hardware recently, remove and replace the hardware to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the hardware manufacturer to determine if the component has failed.

• Stop 0x50 messages can also occur after installing faulty drivers or system services. If the file name is listed, you need to disable, remove, or roll back that driver. If not, disable the recently installed service or application to determine if this resolves the error. If this does not resolve the problem, contact the hardware manufacturer for updates. Using updated drivers and software is especially important for network interface cards, video adapters, backup programs, multimedia applications, antivirus scanners, and CD mastering tools. If an updated driver is not available, attempt to use a driver from a similar device in the same family. For example, if printing to a Model 1100C printer causes Stop 0x50 errors, using a printer driver meant for a Model 1100A or Model 1000 might temporarily resolve the problem.

One person has suggested looking at the error logs to see if there's any more details to WHY it's happening

Not sure what it's called it Vista or Win7, but in XP you find logs under 'Event Viewer'
(Right click 'My Computer' > 'Manage' & select 'Event Viewer' from the left)

I don't get any errors at all like that - so don't know what My reason is

 

[twiztidsinz]

Here's all the info I could get out of the Error Log:

Spoiler: Event 1000, Application Error

CODELog Name:ÂÂÂÂÂÂApplication
Source:ÂÂÂÂÂÂÂÂApplication Error
Date:ÂÂÂÂÂÂÂÂÂÂ3/27/2010 10:01:02 AM
Event ID:ÂÂÂÂÂÂ1000
Task Category: (100)
Level:ÂÂÂÂÂÂÂÂ Error
Keywords:ÂÂÂÂÂÂClassic
User:ÂÂÂÂÂÂÂÂÂÂN/A
Computer:ÂÂÂÂÂÂDruzil
Description:
Faulting application name: MakeSkin.exe, version: 0.0.0.0, time stamp: 0x2a425e19
Faulting module name: MakeSkin.exe, version: 0.0.0.0, time stamp: 0x2a425e19
Exception code: 0xc0000005
Fault offset: 0x0000c3b9
Faulting process id: 0x109c
Faulting application start time: 0x01cacdb5eedc8d24
Faulting application path: C:\Users\XXXXX\Desktop\MakeSkin.exe
Faulting module path: C:\Users\XXXXX\Desktop\MakeSkin.exe
Report Id: 2d4fe10e-39a9-11df-b45b-00076147d892
Event Xml:

ÂÂ
ÂÂÂÂ
ÂÂÂÂ1000
ÂÂÂÂ2
ÂÂÂÂ100
ÂÂÂÂ0x80000000000000
ÂÂÂÂ
ÂÂÂÂ8730
ÂÂÂÂApplication
ÂÂÂÂDruzil
ÂÂÂÂ
ÂÂ
ÂÂ
ÂÂÂÂMakeSkin.exe
ÂÂÂÂ0.0.0.0
ÂÂÂÂ2a425e19
ÂÂÂÂMakeSkin.exe
ÂÂÂÂ0.0.0.0
ÂÂÂÂ2a425e19
ÂÂÂÂc0000005
ÂÂÂÂ0000c3b9
ÂÂÂÂ109c
ÂÂÂÂ01cacdb5eedc8d24
ÂÂÂÂC:\Users\XXXXX\Desktop\MakeSkin.exe
ÂÂÂÂC:\Users\XXXXX\Desktop\MakeSkin.exe
ÂÂÂÂ2d4fe10e-39a9-11df-b45b-00076147d892
ÂÂ

 

[CannonFoddr]

'fraid that doesn't help much - it all points back to Makeskin can't do 'something'

A little more searching & it seems that 0x109c faults within Visual Studio COULD be due to 'Visual Studio 2008 SP1' and something called 'Power Commands' (This article) so it could be the problem with you

EDIT: Hmm that's a point to consider... To those who manage to get it running - do YOU have any Visual programming languages installed (Basic/C/Delphi/.NET etc) ???
If so which one's ?? - perhaps that's part of my problem, what with constant CCleaner usage etc - perhaps I've 'removed' something that Makeskin needs
(I now know that Makeskin 'writes' something to registry when I tried 'compatibility mode' - Comodo Firewall pops up a warning message stating the fact)

 

[twiztidsinz]

'fraid that doesn't help much - it all points back to Makeskin can't do 'something'

A little more searching & it seems that 0x109c faults within Visual Studio COULD be due to 'Visual Studio 2008 SP1' and something called 'Power Commands' (This article) so it could be the problem with you

EDIT: Hmm that's a point to consider... To those who manage to get it running - do YOU have any Visual programming languages installed (Basic/C/Delphi/.NET etc) ???
If so which one's ?? - perhaps that's part of my problem, what with constant CCleaner usage etc - perhaps I've 'removed' something that Makeskin needs
(I now know that Makeskin 'writes' something to registry when I tried 'compatibility mode' - Comodo Firewall pops up a warning message stating the fact)

Well... the issue with it not running happened both before and after installing Visual Studio 2008.
I don't believe that I have the SP1 installed. I also do not use anything like CCleaner.

I'll test it on another computer in a minute.
Tried it on an almost brand new install of Windows 7 Ultimate, and it crashes the same as I've posted before.

 

[798-Icebird]

I have updated the package with the new version of twiztidsinz's script and a makeskin_default_forGlobalLanguages.bat that works the same.

I can really not find an answer for the people who cant get it to work. Even with a clean install it doesn't work for some people while everything runs fine @ my PC

--EDIT-- LOL I forgot the link: http://filetrip.net/f10098-Moonshell2-skin...1-2-PROPER.html

 

[twiztidsinz]

Thanks Icebird..... but I'm an idiot and sent you my testing code that "works" but does not function.

Here is the proper, working, non-test code:

@echo off
cls
echo.
set skin=
set /p skin=Enter the name of the skin:
set skin=%skin:.skn=%
makeskin.exe -d %skin%.skn

Enjoy!

 

[798-Icebird]

Thanks Icebird..... but I'm an idiot and sent you my testing code that "works" but does not function.

Here is the proper, working, non-test code:

@echo off
cls
echo.
set skin=
set /p skin=Enter the name of the skin:
set skin=%skin:.skn=%
makeskin.exe -d %skin%.skn

Enjoy!

Noticed it already

But how did you get it to work while it first didn't work to you?

 

[jurassicplayer]

Maybe he just put in a random file name, since it seems that while the makeskin doesn't decompile stuff for me, it does leave a folder and almost looks like it acts like normal (makes a folder but since it can't decompile anything, there is nothing in the folder).

 

[twiztidsinz]

Noticed it already

But how did you get it to work while it first didn't work to you?

I still can't unpack skins... the app crashes on me
But by setting it to echo the command, it will show me what command will run, and when it looks correct, then I give it a few final tests and let it crash.


I wish I could get it working, but it seems that the Moonshell tools aren't the best written apps around

I'm currently having an issue with the MakeSplash app.

 

[Mbmax]

Hi there.
Don't know if this can help, but in case.
I have reached Carpfish, the author of the modded makeskin.exe a few weeks ago.
I was very interested in his tool because the ez5 kernel 2.0 use skin compiled with moonlight's makeskin type 3 (msh2.0b5).
The goal was to add to ez skin forger the ability to unpack skin files.

So Carpfish built me a new version of makeskin.exe which was able to unpack skin type 3, but something weird happened during beta test.
His version was working greatly on several chinese windows xp but not on european windows XP.

After long time a searching this damn bug Carpfish at last found it. It was tied to the file name lenght used on some files in the skin.
He has modified some lines in his delphi 5 code and compiled a new version. All went fine after that.

Don't know if you are experiencing the same problem on this version of makeskin, but in case please try the one packaged in EZ Skin Forger R65 on filetrip.

As it is for moonshell type 3 skin, please hexedit the .skn file header and change type 5 to type 3 to see if it run correctly and unpack stuff without error.

Tell me if it's ok, i can ask Carpfish to fix the type 5 makeskin version.

 

[jurassicplayer]

Mbmax, give my credits to Carpfish xD! It works for me now.

 

[twiztidsinz]

Don't know if you are experiencing the same problem on this version of makeskin, but in case please try the one packaged in EZ Skin Forger R65 on filetrip.

As it is for moonshell type 3 skin, please hexedit the .skn file header and change type 5 to type 3 to see if it run correctly and unpack stuff without error.

Tell me if it's ok, i can ask Carpfish to fix the type 5 makeskin version.

http://filetrip.net/f10099-Ez-Skin-Forger-R65.html
Lazy link for people to test.

I'll reply in a few if it works.

OMG! IT WORKS!!



I noticed by changing "type 3" (74 79 70 65 2E 33) to "type 5" (74 79 70 65 2E 35), it unpacked "type 5" skins no problem...
Is there any way to make it "universal" where it doesn't check the skin type?

Or would that cause problems?