/build/static/layout/Breadcrumb_cap_w.png

Convert compiled WiseScript (.exe) back to .wse

I have a compiled WiseScript (.exe) from an old .msi package that I want to reuse in a new .msi.
However, first I want to check it and (probably) make some small changes.

Is it possible to convert this file back to an editable .wse file?

If so, how?

Thanks
Roland

0 Comments   [ + ] Show comments

Answers (12)

Posted by: nheim 16 years ago
10th Degree Black Belt
0
Hi Roland,
try Universal Extractor: http://legroom.net/software/uniextract
Regards, Nick
Posted by: rpfenninger 16 years ago
Second Degree Green Belt
0
Hi Nick

Thanks for the link to this cool tool.
Unfortunately, it doesn't do the trick. [:(] It says that it supports Wise Installer Packages but is unable to extract the .wse.
Thanks anyway.

Roland
Posted by: anonymous_9363 16 years ago
Red Belt
0
Nick, All the UE does is extract files. It's just a front-end to a collection of utiltities for uncompressing archive files.
Posted by: nheim 16 years ago
10th Degree Black Belt
0
Hi folks,
don't know all formats of UE, but the collection is AFAIK the most impressive ever built.
VBScab, you are right, i think. Then we have to go a little bit to the underground to push it further... :-)
Try WiseDis.
Regards, Nick
Posted by: rpfenninger 16 years ago
Second Degree Green Belt
0
no luck with this one either
Posted by: neo2000 16 years ago
Purple Belt
0
Great minds think alike..! [:)]

I am still looking for the same thing.. Opened a topic about it a bit earlier, got some suggestions, however, same results -> the contents of the MSI get extracted, but not the WSE file.. Link to my topic.. http://itninja.com/question/updates-not-finishing7&mpage=1&key=旻

In my case, it's files compiled to exe..
Posted by: aogilmor 16 years ago
9th Degree Black Belt
0
Roland, I've had better luck with later versions of Wise (v7) as far as their extracting/conversion. You'll still need to clean it up though.

Just curious, what does the wse do and how come it can't just be done with an msi?

Good luck.
Posted by: rpfenninger 16 years ago
Second Degree Green Belt
0
Hi aogilmor

What do you mean by I've had better luck with later versions of Wise (v7) as far as their extracting/conversion..
Do you know a way to realize that? If so how? With the WiseDis tool?

Sometimes I just find it very comfortable and easy to add a WiseScript as a Custom Action (in this case edit an .ini entry depending on which user logging in).

I've found a tool called E_WISE but had no luck with that one either (saying unknown Wise Version).

Roland
Posted by: AngelD 16 years ago
Red Belt
0
Hi Roland,

If the WiseScript exe isn't that big have you tried open it with ex. notepad as you may find some useful information from that.

To extract files from the WiseScript EXEs if not prevented in some how isn't the switch /x or /c?
Posted by: WayneB 16 years ago
Blue Belt
0
Roland,

I've not tried this and I'm probably wrong but...
If you turn on debugging in windows does it not log the CA executable? Then you can cut and paste it from the log file.

Regards
Wayne
Posted by: AngelD 16 years ago
Red Belt
0
Wayne,

I think it depends on if the exe do some logging or call some Windows Installer function it-self but it's worth a try.
Posted by: rpfenninger 16 years ago
Second Degree Green Belt
0
Thanks to everyone for the replies.
However, none of the suggestions worked (couldn't extract files as there are none, notepad only showed up hieroglyphics and so on).
So it was the best for me to recreate the script.
And this time, I'll keep the editable .wse script file for sure [8D]

Cheers
Roland
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ