Not sure what if anything would need to change to support x64. Probably should just install I would think. Nothing would be 'optimized' for x64, and in particular the par2 commandline wouldnt benefit.
Unless there is some change to how shell extensions work or something.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There must be a change to how the shell extensions work. It installed fine but doesn't show up as a right click option for rar or par files using the default xml config doc.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yea, I don't have an x64 install or Vista so I'm a bit hamstrung for testing these. I will look at maybe doing some Virtual Machine testing, but that's going to be fairly time consuming and going to take up a lot of disk space to get going.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have Vista (32 bit) on my Notebook and an 64Bit Virtual Machine, but there is no Development Envronment enstalled jet. I'm very busy last weeks, but I'll try to do this next days so I can test whats wrong there...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I finally installed Vista x64 on a system I just built out. I am getting one error I need to resolve (some weird malloc(4) error that if I hit ignore in the debugger the app works fine). Hopefully I will have a release later today.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So my analysis was a little premature. The issue is at this point that the Windows Explorer (x64 app) won't show the context menus while Directory Opus 8+ will show them because it is a 32 bit app. I'll need to figure out what the differences are between x64 and x32 shell extensions are.
I figured this out when I was trying to figure out why TortoiseSVN wasn't showing up in DO :)
I will have to see if there is some way to do both in a single app, otherwise I will need to release 2 versions.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So yea, x64 is going to be a pain. I will release a version shortly that will work with 32 bit file managers like Directory Opus or the 32bit explorer in the WOW64 folder soon that fixes a bug that caused it to crash in those situations on an x64 box.
Otherwise, I have a version that is compiling to x64, but getting everything registered properly, etc. will be a challenge. I am no COM expert. Right now it crashes before it even gets to my code :P
Alas, it is unlikely that a single version will ever be usuable across 32/64 as the way ExQueues works is by passing the marshalled HMENU handle from shell extension to the executable, and from what I'm gathering, HMENU is now 64 bit on x64 and 32bit on the other. I would most likely need to use some other form of communication besides COM to do that, though I could be mistaken.
So again, your best bet is to use Directory Opus, Explorer 32bit or some other 32 bit file manager in x64 for the time being. If you don't want to wait for me to get the bug fix release out, you can just copy config.default.xml to config.xml in your AppData/Roaming/ExQueues folder. The bug was I was deleting something before I was done with it, which I got away with on 32 bit but not 64.
I recommend Directory Opus anyway, as it allows you to set up those DDE drag and drop features that mean you don't need to use the context menu, you can just use shift-drop or the like.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have written some batch files and tcl scripts that use DDE (just as in DOpus) to queue up files. All that is needed after the install of TCL 8.5 & Exqueues is to create SendTo links to the batch files. Not all features are supported but repair/extract here, to subdirectory, and browse for folder work as well as they always did.
If there is any interest and the mod approves I would be happy to upload them to the forum.
If anyone is interested
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Feel free to post in the forums or if you need me to put something in the repo I can do that too.
I keep thinking I will have time one of these days to rewrite this in something more modern, but I just never find the time, and the thought of digging back into the Windows COM/DDE stuff is ugly, lol.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK.
I have consolidated the batch files into a single file and the TCL scripts into a single script.
I have compiled the batch file into an EXE using Bat To Exe Converter (Keeps the Console window from popping up.) and the TCL script into a standalone EXE using MyTCL. (TCL no longer needs to be installed.)
I have used Fast Explorer Context Menu Extension DLL to create a dedicated context menu.
I have modified the ExQueues Config.xml, adding a DDE command to "Repair Only".
Installation is much less painful now. Just copy all the files to ExQueues program folder and import a Reg file into the registry. (Config file will have to be copied to the Appdata folder also.)
Since there is always a possibility that some other APP is using the Fast Explorer DLL I will also include the SendTo Shortcuts.
There are now working menus for "Repair Only" "Repair & Extract Here" "Repair & Extract to a Derived Folder" "Repair & Extract to Browse For Folder" and "Move". All commands work with the testing I have done in a single explorer view and also search results that may contain multiple locations. For now the derived folder is based on the PAR2 file name and the context menu is visible for any file and folder type. The context menu works on both 64bit file managers and 32bit file managers. I have also replaced the par2.exe and the unrar.dll with 64bit versions. (PAR2 verifying and repair is much faster)
I plan to create menus for creating parity sets. (Including support for recursive actions)
Also, I have never heard of anyone using ExQueues for anything but repairing and extracting so I am researching other possible uses. (Multimedia conversions, file transfers, and other archive manipulations etc.)
Please keep in mind that I am NOT a programmer. I came up with this through research, trial and error, and just plain stubbornness.
If that all sounds good I will upload the stuff after work tomorrow. If you think it is worthy I guess putting it in the repo would be pretty cool too.
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Any chance you will get around to adding a version for x64 windows?
Not sure what if anything would need to change to support x64. Probably should just install I would think. Nothing would be 'optimized' for x64, and in particular the par2 commandline wouldnt benefit.
Unless there is some change to how shell extensions work or something.
There must be a change to how the shell extensions work. It installed fine but doesn't show up as a right click option for rar or par files using the default xml config doc.
Yea, I don't have an x64 install or Vista so I'm a bit hamstrung for testing these. I will look at maybe doing some Virtual Machine testing, but that's going to be fairly time consuming and going to take up a lot of disk space to get going.
I have Vista (32 bit) on my Notebook and an 64Bit Virtual Machine, but there is no Development Envronment enstalled jet. I'm very busy last weeks, but I'll try to do this next days so I can test whats wrong there...
I finally installed Vista x64 on a system I just built out. I am getting one error I need to resolve (some weird malloc(4) error that if I hit ignore in the debugger the app works fine). Hopefully I will have a release later today.
So my analysis was a little premature. The issue is at this point that the Windows Explorer (x64 app) won't show the context menus while Directory Opus 8+ will show them because it is a 32 bit app. I'll need to figure out what the differences are between x64 and x32 shell extensions are.
I figured this out when I was trying to figure out why TortoiseSVN wasn't showing up in DO :)
I will have to see if there is some way to do both in a single app, otherwise I will need to release 2 versions.
So yea, x64 is going to be a pain. I will release a version shortly that will work with 32 bit file managers like Directory Opus or the 32bit explorer in the WOW64 folder soon that fixes a bug that caused it to crash in those situations on an x64 box.
Otherwise, I have a version that is compiling to x64, but getting everything registered properly, etc. will be a challenge. I am no COM expert. Right now it crashes before it even gets to my code :P
Alas, it is unlikely that a single version will ever be usuable across 32/64 as the way ExQueues works is by passing the marshalled HMENU handle from shell extension to the executable, and from what I'm gathering, HMENU is now 64 bit on x64 and 32bit on the other. I would most likely need to use some other form of communication besides COM to do that, though I could be mistaken.
So again, your best bet is to use Directory Opus, Explorer 32bit or some other 32 bit file manager in x64 for the time being. If you don't want to wait for me to get the bug fix release out, you can just copy config.default.xml to config.xml in your AppData/Roaming/ExQueues folder. The bug was I was deleting something before I was done with it, which I got away with on 32 bit but not 64.
I recommend Directory Opus anyway, as it allows you to set up those DDE drag and drop features that mean you don't need to use the context menu, you can just use shift-drop or the like.
Not sure if this is appropriate…
I run Win7 x64.
I have written some batch files and tcl scripts that use DDE (just as in DOpus) to queue up files. All that is needed after the install of TCL 8.5 & Exqueues is to create SendTo links to the batch files. Not all features are supported but repair/extract here, to subdirectory, and browse for folder work as well as they always did.
If there is any interest and the mod approves I would be happy to upload them to the forum.
If anyone is interested
Feel free to post in the forums or if you need me to put something in the repo I can do that too.
I keep thinking I will have time one of these days to rewrite this in something more modern, but I just never find the time, and the thought of digging back into the Windows COM/DDE stuff is ugly, lol.
OK.
I have consolidated the batch files into a single file and the TCL scripts into a single script.
I have compiled the batch file into an EXE using Bat To Exe Converter (Keeps the Console window from popping up.) and the TCL script into a standalone EXE using MyTCL. (TCL no longer needs to be installed.)
I have used Fast Explorer Context Menu Extension DLL to create a dedicated context menu.
I have modified the ExQueues Config.xml, adding a DDE command to "Repair Only".
Installation is much less painful now. Just copy all the files to ExQueues program folder and import a Reg file into the registry. (Config file will have to be copied to the Appdata folder also.)
Since there is always a possibility that some other APP is using the Fast Explorer DLL I will also include the SendTo Shortcuts.
There are now working menus for "Repair Only" "Repair & Extract Here" "Repair & Extract to a Derived Folder" "Repair & Extract to Browse For Folder" and "Move". All commands work with the testing I have done in a single explorer view and also search results that may contain multiple locations. For now the derived folder is based on the PAR2 file name and the context menu is visible for any file and folder type. The context menu works on both 64bit file managers and 32bit file managers. I have also replaced the par2.exe and the unrar.dll with 64bit versions. (PAR2 verifying and repair is much faster)
I plan to create menus for creating parity sets. (Including support for recursive actions)
Also, I have never heard of anyone using ExQueues for anything but repairing and extracting so I am researching other possible uses. (Multimedia conversions, file transfers, and other archive manipulations etc.)
Please keep in mind that I am NOT a programmer. I came up with this through research, trial and error, and just plain stubbornness.
If that all sounds good I will upload the stuff after work tomorrow. If you think it is worthy I guess putting it in the repo would be pretty cool too.
Thanks.
Here you go.
ExQueues_x64_Project.rar