Winrar 32 E 64 Bits
Stephanie Dejoode
I have a problem finding the correct way to unrar multiple files with the help of Winrar command.
With a button, I managed to unrar them all, but all in the same time. It's not very efficient...
The best solution is to unrar them sequentialy, but I can't find the correct winrar command to do this.
The best thing to do is get WinRAR working on its own using hand-made command-lines and file-list text files from a Command Prompt (i.e. Opus is not involvemed at all) and then once you have something that works, turn that into an Opus button.
Seems the useage of the @listfiles param is poorly documented by WinRAR. In all of the command line useage examples it SEEMS like you're supposed to be able to use @listfiles with ANY rar command... but as you've seen trying x or e for extracts seems to process the listfile incorrectly. BOGUS on WinRAR...
Anyhow... in the related 'Buttons and Toolbars' thread you posted in first, I think you mentioned that you liked how the WinRAR context menu handled the extract? If so... try creating a toolbar Menu that runs the following Opus function in a button under the menu:
Note!!! If you're doing this with a toolbar... you have to place a Menu item on the actual toolbar, and then add the function above to a Button under that menu... otherwise, the toolbar probably won't show the Context menu items provided by WinRar, since the list is instantiated based on what file types you've got selected, and the toolbar doesn't "refresh" AFTER you select RAR files subsequently to opening a lister... But a button 'under' the menu item will call the extension handler as you expand the menu while RAR files are selected...
By the way, your solution is quite good, but we came back to the same solution as the right click context menu, so I can't specify automatically an extract path.
For now, I prefer using @sync "C:\Program Files\WinRAR\WinRAR.exe" x f "E:\tmp\", because it does the job very well (just have the always on top Opus window ruining a bit the thing, but I'll survive).
Anyway, you might consider using the default extract path in WinRAR's Options->Settings? Then, if you use the Extract files... item from the context menu, it will default to that path the same as if you'd set the path as a command line arg... You DO still get an extract confirmation dialog... but can just hit and the operation continues...
Yes, the context menu uses an undocumented switch to pass additional
archive names. But it is not carefully tested with all possible RAR
commands and switches. Also its syntax is not well designed. Maybe
we'll fix these issues in the future and make a documented option
for this purpose.
7zip and Peazip are better alternatives to winzip or winrar. winzip/winrar require you to manage licensing while 7zip and peazip are both freeware fully approved for use in corporate and home environments. 7zip is my personal favorite but Peazip seems to be more friendly for end users
Hello i am new here and i have a few questions if it is possible to take a file and rar it with winrar with a command, is there any guide because i searched but didnt find anything clear. So is there any command because couldnt find anything in helpfile.
First it runs Winrar from it's directory which is assumed to be in @ProgramFilesDir ("C:\Program Files" for example) with the parameters "a" - as the command for add or compress, "C:\Destination" - as the destination file , "C:\Source" - for the source files or folder (watch the other switches for recursively compression of entire folder and it's sub-items). In short, I don't understand it completely myself but it's just add this C:\Source to C:\Destination rar file using the a command.
do u know any way to write paths without main C? i use the prog with a usb stick and the path changes every time i put it on other computer since sometimes it is "d:\gamefiles\filr.txt" or "h:\gamefiles\filr.txt" or "e:\gamefiles\filr.txt"
I know it may seem confusing but testing is the way to go if you're not sure, read the help file about these functions, some return arrays some may return an empty string. Also, preform a check so you won't get unpredictable results. Sorry, I can't be of help ;]
I'm not really sure if this needs a bug report because it shouldn't be handling things this way, a feature request to implement error checking and notification that's not there, or just a helpful guide for anyone else who seemed to come up dry searching.
When you try to launch a game instead of the game opening either
A: The file opens in the default program instead (for me it was winrar)
or
B: The emulator launches and for me gives an "Uncorrectable data at sector 0" error sending me to the Saturn dashboard. Instead of unzipping the rom to the temp folder to launch as it's supposed to, it unzips in the rom parent directory (and leaves a mess)!
Both of these scenarios were happening to me on some systems and I had no idea. Sega CD worked great in retroarch but Saturn in retroarch did not work. Bin/iso/Cue were named correctly in the cue/file. 3do would just open the rar file quietly. Debug logging was turned on but there was ZERO indication of issues in the logs. Removing and re-adding my Saturn platform did nothing.
Solution:
3do: I apparently never added the 4do core to retroarch- oops!
Shouldn't this normally pop an error of some type if the platform was marked as roms / or matching an "emulator required" scraper?
Sega Saturn: I had to add the core to retroarch after setting up the emulator. Even after selecting it in the drop down, it didn't like beetle. I set the core to mednafen_snes, closed out, "launched" a game, then went back and set the core to mednafen_saturn again. After this, my games started extracting to the proper location and launching successfully.
My searches I ran just came up with "I reinstalled", had XML issues, or problems with the rom files themselves. but it looks like it's much simpler to solve. This looks like something specific within LB.
Not really as there is no right or wrong emulator. Launchbox allows you to use any emulator or Retroarch core you like, it also has no built in "knowledge" of what emulators are for what systems or file types that they use, it just does as its told. If you dont tell it a core as in the case of your 3DO it cant load a rom as it essentially doesnt know how to as a emulator hasnt been specified.
Essentially its on the user to make sure that a emulator supports a system and that that emulator also supports the file type being loaded, Launchbox has no preconceptions here and will simply try to do what you ask it to. Launchbox also doesnt know if a rom has failed to load, it simply passes it off to the emulator per the settings you have set, it has no way to know whether or not once passed if that rom loaded OK or not, its done its job at that point and if the rom fails to load that will be in the emulators log file and not Launcbox's.
I feel like there might be a mix here too though. why did the unzip extract directory change based on lack of emulator or specific retroarch core?
Also, if LB unzipped a rom, shouldn't it do a files present success check prior to launching the rom? (in case of corrupt file, full drive, etc).
Also, in the case of 3do - it was imported as a rom and had no associated emulator. Wouldn't that be easy to tell and pop a message "Warning, no emulator associated with platform". If it has nothing to do after opening the file, shouldn't that notify in some way to console? Nevermind to the debug log.
Maybe a checkbox similar to Zinc if that's actually an intended configuration?
I am getting .zip files as well as .rar files from my source location. While i am able to unzip the .zip files using unpack content processor , i am not able to extract the .rar files. I even tried compress component processor but seems that too doesn't support .rar files. How should i extract the .rar files ? install winrar in root folder and then call it using execute stream processor ?
I realize this topic is a bit old, but I have this same problem to solve. I am struggling with setting the unrar in the ExecuteStreamCommand process, then having the decompressed files returned in the output on the stream for additional processing. I am getting broken pipe errors and unrar cmd ended in nonzero errors. How exactly do I set this up so that it works just like Nifi's native UnpackContent process? Thank you.
@Phil_I_AM
Always best tot start a new question rather than commenting on an old post. Will get you better traction that way from the community.
The reason NiFi does not have native processor that can handle rar files is because there does not appear to be java native libraries available to do this. -8391
You may consider filtering and writing your rar files to a flow specific directory on disk and then use the ExecuteStreamCommand processor to unpack that rar in that directory. You could have a new flow that uses the listFile (configured to ignore files with rar extension) and FetchFile processor to monitor that directory for new files and consume them for further processing.