You should use Universal Extractor. It extract files directly from many different types of installer packages.
Note that in order for Universal Extractor to operate on installers created using newer versions of InnoSetup, you should download the latest version of innounp, then extract innounp.exe and place it in the bin subfolder of Universal Extractor.
Alternatively, you can download and use the unofficial updated release of Universal Extractor.
For the purpose for this website, "stealth" means when an application is launched, used and terminated properly, it does not leave behind any entries in the registry or filesystem. Certain exceptions are permitted. For example, registry entries that are created/updated by Windows for the application (eg. MRU entries for dialog boxes, DirectX entries for DirectX-based apps), or temp files created in the official "Temp" folders are not taken into consideration. Note: "Stealth" does not mean non-traceability! In fact, it is quite unlikely you can hide your activities on a Windows machine from a capable system administrator.
Post it at the web forum! But before you do so, please search for the application name. If I have previously looked at the application and classified it as non-portable, it should appear in a box labeled "Non-portable apps" on the right side of the screen. Hover the mouse cursor over the application link and you will see further details in a text popup.
If you have problems viewing long titles (used for the text popup) in Firefox, this extension might help.
I typically look at 4 to 5 apps a day, less if family or day work demands more of my time. I process the submissions in no particular order, but I typically favor submissions which are already "written for me" i.e. synopsis, where settings are written to, system requirements, Unicode support etc. versus those in the manner of "I thought you might like to take a look at this app, though I am not sure if it is portable", or "This looks interesting, but I am not sure whether it touches the registry". Lowest preference are given to submissions in the form "This website looks interesting. I think all the software in it are portable".
To quote Roger Johansson (with his permission) from his posting on alt.comp.freeware:
> Would someone be so kind to explain why one would be against a program installing? I don't understand the issue here.
I have many favorite programs on the D: partition, and they continue to work no matter if Windows crashes, and needs to be re-installed, or if I change to another version of Windows.
I try to avoid using programs which have to be re-installed when I reinstall Windows. I use more and more programs which do not depend much on Windows to work.
Many of my favorite no-install programs are programs I have moved to another partition than it was installed to, and I test if it works well from there. Then it is fairly independent from Windows and I keep it.
On C: I only have Windows and a few programs which do not work un-installed, so when I have to repair or upgrade Windows I have to re-install those programs too. That is why I try to minimize the number of programs which need to be installed correctly to work. If I can find a program which is less fussy and works in all situations, even if I have moved its program folder to another drive, I prefer that program.
I typically extract the program and compare the before/after snapshot with RegShot to find out what was modified and where settings are written to. I also use Dependency Walker to check whether the EXE uses any particular runtime (eg. VB, .Net, Java) or special DLLs. Finally, when I have time, I will run the program again on a clean install of Windows XP (running in VirtualPC) to make sure it really works.
Sometimes, due to various reasons, I may miss out one or more of the steps. For that, I rely on users to email me and inform me of my oversight.
This appears to be a hardware issue. For more information, refer to Microsoft's USB Storage - FAQ for Driver and Hardware Developers and read the section on "What must I do to trigger Autorun on my USB storage device?" for more information. The conclusion is this: if your USB drive does not support it, you are pretty much out of luck.
Another solution is to resort to software. For example, there is a freeware called APO USB Autorun Suite that enables autorun for USB drives (thanks to Steve Towner and Dennis Lim for the recommendation). Another I found recently is BusRunner. Yet another one called AutoRun installs a small event handler to do the same thing.
But the software approach requires the software to be installed on every machine that you want this functionality enabled, and you need to leave the application running all the time. Hardly a perfect solution, but definitely cheaper than throwing away your USB drive and buying a new one!
Firstly, I am not too much of a command-line guy. I hate remembering the switches. Since this is a personal hobby, I prefer to review apps that interests me.
Secondly, command-line apps are pretty much always portable, so there is not much point listing them. There are plenty of sites out there that do that already.
Writing settings to the application folder is dangerous because you need to have admin rights on the machine and different users are stuck with each other's settings! Storing settings in the user profile folder also has the advantage that you could upgrade a program without losing its settings.
In a multi-user environment, it is indeed inappropriate to write settings in the application folder. However, portable apps are run from external USB flash drives or equivalent, so it is a personal device and writing settings to the application folder is therefore preferred. In addition, the admin rights requirement is no longer a concern since you have full access to the USB drive.
An application can cater to both multi-user environment and portability by checking with the user on startup (when it detects that the settings are not initialized yet) whether he wishes to write settings to the user profile folder or application folder. This should be relatively easy to implement, and makes no assumption on the user's preference. Underlying this mechanism is to check for a file eg. settings.ini in the application folder on startup. If the file exists, it write its settings to the application folder, otherwise to the user profile folder.
With regards to the issue of upgrading an application without losing its settings, you could just as easily upgrade a portable app without losing settings by avoiding the appropriate file(s). Some well-designed apps like Portable Firefox even has a explicit profile folder that you simply leave alone when copying over the new application files. This also has the added advantage of being able to easily maintain several versions of the same application, each with its own settings.