CMD Mod / PowerPacker issue.

[Siginet]

I am the one who created PowerPacker

I have been trying to figure out a bug that one of my beta testers had run into for about a week. No matter what we did we could not figure out why he was having an issue.

We just found out that the cmd mod and a tool I use in my program called BootFolder.exe where not working well together. As soon as he uninstalled the CMD mod all worked fine.

I just wanted to point out the issue. I haven't used Xpize yet... but it sounds very interesting. Hopefully maybe you can use my program as a test tool to find out why cmd mod does not like it. I noticed most people never had a problem with cmd mod... so that makes it hard to fix an error. At least with my tool you can see if you can re-create the issue.

[XPero]

Thanks for reporting. It seems that this issues with the CMD mod cannot be fixed. I will include it again in XPize 4, but it will be unchecked by default and a warning message will be shown.

[Siginet]

I also released a newer version of PowerPacker which will probably be compatiable with CMD Mod. The new version of PowerPacker does not use .NET... so I don't think it should have an issue anymore.

Fixing weird little bugs is so much fun isn't it XPero? hehe!

[XPero]

It is indeed But I would prefer Microsoft to do their job well Thanks for the news and good luck with your app. I will try it soon.

[Siginet]

I have XPize installed on my computer now. It looks very nice! I even installed the cmd mod to test out Windows XP PowerPacker and it seems to work just fine.

Thanks!

[XPero]

Great news! I have to test your app, but I'm having a busy summer

[SiMoNsAyS]

that's nice!