Messages

1

Support and Feedback / Re: Server Busy Warning in 7Zip & Store Edition

« on: May 24, 2025, 18:24:12 »

"I do not get a crash.. But MC can crash because you are trying to do lots of things with ti while it is waiting and when the wait is over it tries to do a lot of things at the same time"

It only crashes if I click on Switch To but if I click on Retry nothing happens.

"Adding files to an existing 7Z is currently not supported. There was some issue with that, But t is on the list."

I see, for safety's sake I'm only going to compress with zip now, it's safer because it has wider support, I've even tested it with other managers out of curiosity and the same error happens.

Safe yes, Difference is that store edition is a bit behind the version on the site, because it is messier and require more to get it up there. But the plan is to update Store edition also when next version is release ( 15.5 )

Okay, that said, I'll consider downloading the Windows Store version on my laptop. Thanks for your support.

2

Support and Feedback / Server Busy Warning in 7Zip & Store Edition

« on: May 22, 2025, 23:19:29 »

Hello,

1 - In MultiCommander, when I want to compress files with 7zip, I drag the files into the compressed folder.  When I do this, a window opens with the message Server Busy followed by the buttons Switch To, Retry, and Cancel (Cancel cannot be selected). Even with this window open, the compression takes place normally.

After the compression is complete, if I click on Switch To, the Multicommander crashes, I have to restart it, when I click on Retry, nothing happens.

Does anyone know what kind of problem this is or is there a plugin to compress inside 7zip with MultiCommander so that I don't have to open it from the outside? It works with other zip formats but in 7zip I can't throw any files into the compressed folder, I get a message saying that "this operation is not supported."

2 - Is it safe to download the Store Edition version from the Microsoft store, it says it's the same version but in the update history it looks out of date compared to what's on the official site.