SUCCESS OK I deleted the last line of code like you said, and the archive extrracted itself into the self named folder, but did not move into it. No error window, no nothing!
I can see why you are confused about this. I copy and pasted this image from the first post where I showed the intial error window. I did not copy this from it actually happening at that moment when I made the post (i.e. while I was messing with the test archive) I'm sorry for the confusion.
Hey Guys,
I dont want to irritate you all on the board, but I wanted to try screwing around with various things for a while to see if I could understand what was causing my problems with WinRAR and extracting files from compressed archives, but I still can't figure out what the hell the problem is.
For anyone that wasn't around for my last go around, one of my most beloved functions I have been able to incorporate into DOpus was the option on my right click context menu for any compressed archive to extract the archive into a folder named using the archive's name, and then move the archive file itself into said folder. Out of the blue one day, WinRAR began giving me sh*t by popping up a window when I would use this function that's titled "Winrar diagnostic messages" and it would have nothing other than the phrase "no archives found" in the window. Now heres the weird part - everything still functions properly. The archive is extracted into a new folder that is named using that archive's name, and the archive file itself is moved into said folder. But The damn diagnostic window message continues to pop up!
I have tried so many permutations of this issue to figure out where the issue lies and I'm still just not sure. I had a hunch for a while that it may have to do with Default program settings, and maybe my defaults were screwed up somehow. Nope. Maybe WinRAR is corrupted. Reinstalled, reinstalled again using new download of program file. Nope. Maybe EVERY SINGLE ARCHIVE I HAVE ON MY COMPUTER IS CORRUPTED. Tested every archive I use with Winrar itself and 7zip that if I am simply extracting the archive to a folder named from the archive, no issues arise. Maybe I had a virus? Nope. Maybe DOpus install is corrupted? Nope, reinstalled and same behavior. I've skowered the internet for help with this and the only thing I find pertaining to this diagnostic message is 1000 youtube videos that claim to have the answer to the problem until you open the video and they ALL tell you to use 7zip instead of WinRAR. Gee, thanks. I've tried different ways of writing the script, using the CREATEFOLDER version that was recommended to me, and then the original MOVE version. Same effect. I tried using unRAR.exe instead of WinRAR.exe. Nope.
The error seems to be dealing with moving the file into the directory, as the decompressing feature works without error using the same means (using a script through DOPus, not through WinRAR program interface).
Does anyone have any recommendations ? Please? Thanks for any help.
Splash3313 Opus 13
Firstly what script you using secondly what version of winrar you using and what version of Dopus you using?
my apologies. To both of you. I'll dig up the old thread.
cd {sourcepath}
"/programfiles\WinRAR\WinRAR.exe" x "{f}" "{o|noext}"
Copy MOVE HERE CREATEFOLDER "{file|noext}"
cd {sourcepath}
"/programfiles\WinRAR\WinRAR.exe" x "{f}" "{o|noext}"
Copy MOVE TO ".{file|noext}"
WinRAR -7.11
DOpus - 13.14.10 beta
Thereās nothing wrong with Opus or WinRAR. The issue lies in your self-inflicted confusion. Address that first, and everything will fall into place.
so you're saying that I'm not experiencing that I'm experiencing?
I actually just discovered something interesting. It doesn't give this window for .7z when i use the same command. Does anyone know what this may indicate?
I am convinced this is a default program problem within DOpus. I can't figure out why Archive group shows only 5 file types in there, when I have over 15 in the Archive. WinRAR reports that this behavior happens with the "No Archive found" message when the program does not see an archive because of file type issues. I'm convinced this is where the problem lies I just don't know how to fix it
The Archives file type group in Opus has no effect on what WinRAR thinks is or isn't an archive.
Opus can handle RAR archives, but you're using WinRAR instead of Opus for this, so the Archives file type group isn't really involved (unless the action you're doing is triggered via a double-click action specified in the file type group, or similar).
Ok Leo. LXP is convinced im "confused" about something, and I've chased all the possibilities I can figure out with file types to no avail. I have copied your code. LXP's code, every code on here and it does the same thing. If you guys are convinced I'm the problem, what am I doing wrong? I just spent the last hour using GROK to diagnose this issue and it can't get winrar to stop throwing that window either. I've capitulated and switched to the in house archive management.
It bugs the hell out of me that I'm being looked at like i'm an idiot when I've followed everyones recommendations. Perhaps it is Opus and I've found some odd bug that the beta doesn't play well with winrar? Nope, has to be my stupidity.
This is the code i am running - the "Runs fine here without error" one
cd {sourcepath}
"/programfiles\WinRAR\WinRAR.exe" x "{f}" "{o|noext}"
Copy MOVE HERE CREATEFOLDER "{file|noext}"
and it causes this:
Please dont insinuate I'm stupid. Please tell me where I am so clearly going wrong here.
I think the problem comes from the fact that you're mixing internal Opus commands (such as the last one) and external program calls (such as WinRAR).
As soon as the WinRAR call gets executed, you then move to the last command which moves the archive to the newly created folder ... and WinRAR can not find it anymore, so it tells you "No archive found".
You can try this instead (even if it would be even better to let Opus extract the archive without relying to a direct call to WinRAR.exe):
cd {sourcepath}
@sync: "/programfiles\WinRAR\WinRAR.exe" x "{f}" "{o|noext}"
Copy MOVE HERE CREATEFOLDER "{file|noext}"
This 
.
If you test with a larger archive, youāll see the file gets moved even before WinRAR starts decompressing it. Thatās probably why some donāt notice the issueāsmall archives finish decompressing before the move happens.
1 Like
It appears that WinRAR throws the "no archives" error when it encounters issues with the target folder. Specifically, it requires the full path along with a trailing backslash to function correctly.
Well, let WinRAR's wish be our command:
@nofilenamequoting
@nodeselect
"/programfiles\WinRAR\WinRAR.exe" x "{filepath$}" "{sourcepath}{file$|noext}\"
Copy MOVE FILE="{filepath$}" TO="{sourcepath}{file$|noext}"
3 Likes
True. My bad. I thought the sync was making Opus wait WinRAR finished. I was just (un)lucky with my quick test.
Next answer by @lxp seems to work fine (tested with a 1.7 Gb rar file).
Yes @lxp good catch!
I was thinking of moving the archive before decompression, which would also workāthough Iām not sure why Travibe wants to move it to the target folder afterward and whether it makes any difference to move it before or after.
But since they say it was working fine before, Iām curious what changed and where (Opus or WinRAR?) 
Good question... without the trailing backslash, I get the UAC dialog, followed by the error message. Maybe that's somehow related to WinRAR's recently added/changed Propagate Mark of the Web option that caused some discussions.
I don't think anything in the last Opus betas could have caused this, especially since it worked before, and I never got the error until today after trying a bit.
On the other hand, the leak is rarely where you see the water dripping 
OK so I wanted to share my absolute jubilation over fixing the issue this entire post is about. I came across a setting within Preferences "File Operations/Options" - "Deselect files used in functions", and just below this option is "Postpone file deselection until end of function".
I disabled the second option, the "Postpone file deselection until end of function", and miraculously, the warning no longer appears from WinRAR with the "No Archives found" window. I can't tell you all how ecstatic I am. I have been tinkering around with Preferences and other things, so I can't technically say 100% this was the cure for it, but I believe it is, after reading the email from the software developers and their interpretation of the error WinRAR was throwing.
I don't know why this all is the way it is, though, because I have never seen this option before and have not manipulated it, so I'm not certain why this needs to be changed to go back to the behavior I was experiencing in the past. Who knows. I don't really care, I'm just beyond happy to no longer see that damn window.
1 Like