The title speaks for itself ;)
This new version of the UPX addin has a new name: "EXE Packer AddIn v2.00". The full source is included.
I'll be making a tiny update soon, to support WinAsm 3.0.0.3 new CURRENTPROJECTINFO structure (I'm currently getting the project type directly from the .wap file).
I also have some other updates in mind, but none in the near future.
Tell me what you think so far! :)
EDIT: Attachment updated (2.0.0.1)
EDIT: Attachment updated (2.0.1.0)
EDIT: Attachment updated (2.0.1.1)
EDIT: Attachment updated (2.0.1.2)
This new version of the UPX addin has a new name: "EXE Packer AddIn v2.00". The full source is included.
I'll be making a tiny update soon, to support WinAsm 3.0.0.3 new CURRENTPROJECTINFO structure (I'm currently getting the project type directly from the .wap file).
I also have some other updates in mind, but none in the near future.
Tell me what you think so far! :)
EDIT: Attachment updated (2.0.0.1)
EDIT: Attachment updated (2.0.1.0)
EDIT: Attachment updated (2.0.1.1)
EDIT: Attachment updated (2.0.1.2)
Hi QvasiModo,
I don't know what i did wrong, but even after rebuild the project i cannot see the packer in my addin list :(
Got WinASM 3.0.0.3 & XP pro....
Any idea ?
I don't know what i did wrong, but even after rebuild the project i cannot see the packer in my addin list :(
Got WinASM 3.0.0.3 & XP pro....
Any idea ?
Hi,
Same problem here. I 've already PM'ed Qvasimodo. Let's wait for him :grin:
akyprian
Same problem here. I 've already PM'ed Qvasimodo. Let's wait for him :grin:
akyprian
Hi, PhoBos and akyprian. Thanks for the feedback :)
:confused:
I don't have XP to test it, but my first guess is it has something to do with the manifest file. Please try removing it and rebuilding, to see what happens.
Also I don't know what the error code 0x36B1 means (the winerr addin shows no string for that one).
Sorry I can't be of more help... :(
:confused:
I don't have XP to test it, but my first guess is it has something to do with the manifest file. Please try removing it and rebuilding, to see what happens.
Also I don't know what the error code 0x36B1 means (the winerr addin shows no string for that one).
Sorry I can't be of more help... :(
New upload on top.
- Changed the manifest script, let's see how XP chews this one.
- Small bugfix: now the "Pack" item at the "Make" menu is grayed when no project is loaded.
Pls tell me if it works now :)
- Changed the manifest script, let's see how XP chews this one.
- Small bugfix: now the "Pack" item at the "Make" menu is grayed when no project is loaded.
Pls tell me if it works now :)
' Morning :)
Well QvasiModo, i'm afraid it's not working here :(
Same prb than before....
PhoBos
Well QvasiModo, i'm afraid it's not working here :(
Same prb than before....
PhoBos
Hi,
It doesn't work for me either.
From winerr addin:
0x36B1=This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.
Regards,
akyprian
It doesn't work for me either.
From winerr addin:
0x36B1=This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.
Regards,
akyprian
The error description seems to confirm the problem is in the manifest. Both because Win98 doesn't have that error description, and I had some bug reports for the AddManifest addin for RadAsm about some people getting that error when running programs with buggy manifests. The problem is, this time I don't know what I've done wrong with the script... :confused:
Please try to remove the manifest altogether, to see what happens... :(
Please try to remove the manifest altogether, to see what happens... :(
After trying everything, even ripping the manifest from an existing addin to check out it's manifest, I turned to the most obvious course of action: to open the xml file in IE. If it can read xml files, it can certainly check their syntax.
This was the problem: since I couldn't add the manifest directly as a string in the script, I copied and pasted it from an existing rc into an xml file. But I forgot to remove the extra double quotes! No wonder it wasn't working...
:stupid:
Anyway, I've updated the attachment with the new version (2.0.1.0). It has some minor changes in the GUI, but the most important change is the addition of "Profiles". That way you can keep predefined settings for different packers. I thought it would be useful if you want to try several of them, to see which one gives you the better compression rate.
Let's see how well it does now :)
This was the problem: since I couldn't add the manifest directly as a string in the script, I copied and pasted it from an existing rc into an xml file. But I forgot to remove the extra double quotes! No wonder it wasn't working...
:stupid:
Anyway, I've updated the attachment with the new version (2.0.1.0). It has some minor changes in the GUI, but the most important change is the addition of "Profiles". That way you can keep predefined settings for different packers. I thought it would be useful if you want to try several of them, to see which one gives you the better compression rate.
Let's see how well it does now :)
@PhoBos:
While trying to figure out what was wrong with the addin, I compared my xml script with the one I found in the WABuildEX.dll addin. They turned out to be identical, which only contributed to my confusion :grin:
I'm wondering if that addin doesn't have a problem with XP styles too... :confused:
Here's my corrected version, using ResHacker:
While trying to figure out what was wrong with the addin, I compared my xml script with the one I found in the WABuildEX.dll addin. They turned out to be identical, which only contributed to my confusion :grin:
I'm wondering if that addin doesn't have a problem with XP styles too... :confused:
Here's my corrected version, using ResHacker:
Hi Qvasimodo,
I am glad you (probably) solved the problem. The earliest I can test it is on Wednesday. Sorry!
Regards,
akyprian
I am glad you (probably) solved the problem. The earliest I can test it is on Wednesday. Sorry!
Regards,
akyprian
Hi again,
Unfortunately there was a problem in your xml file. I used my own xml and everything is OK. Also there was a problem with your GetOpenFileName Filter string that I fixed. Here is the working version (with your source modified).
Regards and thanks for this useful Add-In,
akyprian
Shall I upload to my site?
Unfortunately there was a problem in your xml file. I used my own xml and everything is OK. Also there was a problem with your GetOpenFileName Filter string that I fixed. Here is the working version (with your source modified).
Regards and thanks for this useful Add-In,
akyprian
Shall I upload to my site?
Sorry I didn't reply before, I've been ill this past few days and couldn't leave my bed, let alone going to a cybercafe :P
Sure, no problem, upload it whenever you want :)
I'll be checking out the new source to (finally) learn what I've done wrong with the xml.
Sure, no problem, upload it whenever you want :)
I'll be checking out the new source to (finally) learn what I've done wrong with the xml.
Version 2.0.1.2. Small bugfix and changes. :)
New upload on top.
New upload on top.
Thanks,
Will be uploaded to my site soon.
Regards,
akyprian
Will be uploaded to my site soon.
Regards,
akyprian