7zip Viewer
Gaetane Eary
I open the archive inside 7zip, then double-click a file inside the archive to open it with the associated application, and I get "File not found" errors in the app (for example opening a image in Windows Photo Viewer).
This provides an official tool which does not require any installation. The executable 7zzs can be used out of the box and is portable. It also seems to have the same syntax as p7zip (at least for simple stuff). E.g. 7zzs x archive.7z to extract. (Add it to your $PATH in order for 7zzs to work or use the full path e.g. /directory/containing/the/executable/7zzs)
I updated 7-ZIP to the latest version 9.2, but when I try to open e.g. jpg from zip archive I always get a message "Windows Photo Viewer can't open this picture because either this picture is deleted, or it's in a location that isn't available."
The Program1 (some photo file handler) calls another Program2 (windows photo viewer) and closes Program1. But 7-Zip waits only Program1. So it deletes image from temp folder. I plan to fix that problem in future.
Oddly this seems to work fine on my pc but not the one I mentioned above. Has anyone encountered this and have any suggestions? I suppose I will try to re-install 7zip but short of that I'm not sure why I am seeing this behavior.
I then reassociated XML files with first Windows Notepad and then FireFox and had no problem viewing the opened XML file in either of them (because the temp file wasn't deleted until AFTER Notepad/FireFox were closed).
I have exactly the same problem since I moved to Vista. From my observations it seems to me that the temporary extraction is breaking up before the progress bar made it to the end. I have no idea what the reason might be and any hints to solve this annoying problem are appreciated.
My guess is that 7-zip watches the process that is created to open the file, and when that process ends, it deletes the file. And still guessing: when IE is already open, the new process just passes a message to the old one and then exits immediately.
I have tried opening in the online Autodesk viewer, Navisworks (manage and freedom), renaming the file to ZIP to see if it reads anything, Inventor, AutoCAD, reinstalling Design Review on my PC, renaming to DWFx, DWG, opening in Vault preview (after checking into Vault), and also opening in Internet Explorer (invokes ADR).
Please let us know if you have encountered other means to recover a corrupted DWF, and if you have any way to view the markups under the W2D file (if you need a sample, use 7zip on any DWF and check its subfolders for one).
Thank you!
You must run 7-Zip File Manager in administrator mode. Right-click the icon of 7-Zip File Manager, and then click Run as administrator.Then you can change file associations and some other options.
You can get big difference in compression ratio for different sorting methods,if dictionary size is smaller than total size of files.If there are similar files in different folders, the sorting "by type" can provide better compression ratio in some cases.
Note that sorting "by type" has some drawbacks.For example, NTFS volumes use sorting order "by name", so if an archive uses another sorting, then the speed of some operations for files with unusual order can fall on HDD devices (HDDs have low speed for "seek" operations).
If you have such archive, please don't call the 7-Zip developers about it.Instead try to find the program that was used to create the archive and inform the developers of that program that their software is not ZIP-compatible.
7-Zip doesn't know folder path of drop target.Only Windows Explorer knows exact drop target.And Windows Explorer needs files (drag source) as decompressed files on disk.So 7-Zip extracts files from archive to temp folder and then 7-Zip notifies Windows Explorer about paths of these temp files.Then Windows Explorer copies these files to drop target folder.
You're probably using a *.* wildcard. 7-Zip doesn't use the operating system's wildcard mask parser, and consequently treats *.* as any file that has an extension. To process all files you must use the * wildcard instead or omit the wildcard altogether.
7-Zip stores only relative paths of files (without drive letter prefix).You can change current folder to folder that is common for all files that you want to compress and then you can use relative paths:
32-bit Windows allocates only 2 GB of virtual space per one application. Also that block of 2 GB can be fragmented (for example, by some DLL file), so 7-Zip can't allocate one big contiguous block of virtual space.There are no such limitations in 64-bit Windows. So you can use any dictionary in Windows x64, if you have required amount of physical RAM.
There are some possible cases when archive is corrupted:
- You can open archive and you can see the list of files, but when you press Extract or Test command, there are some errors: Data Error or CRC Error.
- When you open archive, you get message "Can not open file 'a.7z' as archive"
One way is to use the 7z.dll or 7za.dll (available from sf.net for download). The 7za.dll works via COM interfaces. It, however, doesn't use standard COM interfaces for creating objects. You can find a small example in "CPP\7zip\UI\Client7z" folder in the source code. A full example is 7-Zip itself, since 7-Zip works via this dll also. There are other applications that use 7za.dll such as WinRAR, PowerArchiver and others.
Since 7-Zip is licensed under the GNU LGPL you must follow the rules of that license. In brief, it means that any LGPL'ed code must remain licensed under the LGPL. For instance, you can change the code from 7-Zip or write a wrapper for some codefrom 7-Zip and compile it into a DLL; but, the source code of that DLL (including your modifications / additions / wrapper) must be licensed under the LGPL or GPL.Any other code in your application can be licensed as you wish.This scheme allows users and developers to change LGPL'ed code and recompilethat DLL. That is the idea of free software. Read more here: can also read about the LZMA SDK, which is available under a more liberal license.
I had a corrupted VDI file (according to countless VDI-viewer programs I've used with cryptic errors like invalid handle, no file selected, please format disk) and I was not able to open the file, even with VirtualBox. I tried to convert it using the VirtualBox command line tools, with no success. I tried mounting it to a new virtual machine, tried mounting it with ImDisk, no dice. I read four Microsoft TechNet articles, downloaded their utilities and tried countless things; no success.
If you didn't close the window and you're still getting an error, try extracting each sub-folder individually. Also make sure that you have enough local hard drive space to copy the files to, even if you are copying them just to an external disk, as 7zip copies them first to your local disk. If the files are highly compressible, you might be able to get away with using NTFS compression for the AppData/temp folder so that when 7zip extracts the files locally, it'll compress them so that it can copy them over to your other disk.
You can explore your vmdk image right inside your browser. Select the files that you want to extract and extract them to the desired location. Not just vmdk, you can use VMXRay for looking into and extracting files from RAW, QEMU/KVM QCOW2, Virtualbox VDI, and ISO images. ext2, ext3, FAT and NTFS are current supported file systems. You can also use this to recover deleted photos from raw dumps of your camera's SD card, for example.
You can use ImDisk to mount VDI file as a local drive in Windows. Follow this virtualbox forum thread and become happy )) Also you can convert VDI to VHD and use default Windows Disk manager to mount VHD (described here)
File Viewer Plus is the universal file viewer for Windows. Why pay for dozens of software programs when you only need one? Install File Viewer Plus, and you'll be able open 400 file types with a single app.
c80f0f1006