SIW - System Information for Windows (already in PAF)

So it installs and runs fine, just as with the regular version (which I believe is also inherently portable). I've tested a few of the features and it works as expected, no crashes or system instability. It seems like settings are stored in siw_init.xml.

I did note that the license permits use only for personal, not business use (you must buy a business license to use this on work computers). Not sure if that is a legal stumbling block or not. The application actually pops up a window (I'm at work) telling you that it looks like you're using SIW in a corporate environment and asks you to buy a license (you can cancel the request).

Another minor issue and I don't know how big of a deal this is, it would appear that the launcher is actually the application executable. There's no actual app in the app folder. It looks like SIW.exe has just been renamed SIWPortable.exe. (not actually quite true if I compare the regular zipped original exe with the portable apps version they are different sizes, so there is some kind of difference)

One other minor thing, and again I don't know if this is a big deal or not, but there is a built in version checker to see if you have the latest version or not. Based on using a prior version that I had, it automatically downloads the latest version if you choose to do so. I know normally for portable apps, these built in updaters can often break things (because they don't put the files in the right folders). I guess with SIW this isn't a big deal since there is only one executable and it's in the root portable app folder. I suppose this might be a problem ig the launcher and app must be separate, which goes back to the issue above.

This may all be moot, so sorry if it's unnecessary verbiage. Bottom line is the portable apps version seems to function just fine.

Yeah, it'll require a fix on the file names (we require the name as generated by the PA.c Installer for consistency) but I mean more from an app perspective testing it.

Thanks for doing the regshot. I forgot about it. I think there should be a launcher to remove the folder. Empty or not it is still leaving a folder behind which I had previously been disallowed. Also I personally don't like the idea of leaving behind a folder on every pc I use SIW on.

It will make an xml file if you go into Tools/Options, and thankfully place it into the same folder as siw.exe.

The question now comes up if that xml file needs to live in a Data subdirectory since it is a configuration file and should survive updates.

I agree with horusofoz - no folder left behind. (Isn't that a US federal law?)

I don't see anything in the TEMP folder here. Is it always the same filename? The app seems to run fine without leaving any traces (I've been using the standalone version for a while now). The XML config file in DefaultData isn't moved on first run but, as noted, when you save a new one from Tools/Options it's written to the main directory (with the EXE) and read from there.

These are just minor format things which are easily corrected. Perhaps it would be OK to get an online installer/launcher package together using the standalone version downloadable from the author's site if there's some interest in having it in the correct format. Let me know and I'll post a dev test. But it does require admin rights.