The Portable Freeware Collection Forums

Well, if you keep every application you use in your sandbox, you depend on the sandbox. In case something damages the sandbox, you simply don't want to recreate it from stratch. :( Hmm, i didn't explain this complete enough. What i meant was that every application gets its own sandbox, similiar to ...

I think that some of you are continuing to miss the issue with viruses. You that think you understand the basic principles of trust and computing...never trust anything unless you are buying a machine and never loading any software...period. And a malware scanner can tell you if a software is trust...

As m^(2), i dislike all antivirus apps (and also firewalls, but thats a different topic). Reasons in my case: - false sense of security (biggest security issue actually is the user behind the machine) - too many false positives - unclear purpose. Virusses almost dont exist anymore today, so their jo...

BTW, how do you know what goes to disk and what doesn't? There are mutiple ways to do it, but a simple one that works even if the used taskmanager doesn't give detailed information, is this: Add up all the commited vmem of all processes. Then look at how much RAM is free (again, actually partially ...

As explained in what I linked, it's only trimming of a working set, not swapping memory out. Windows (or any other reasonable OS) never swaps memory out unless it's necessary, MS programmers are not that dumb. Sadly, thats not what i see in practice. Neither on my machines nor on other's machines. ...

Depends on what kind of memory -usage you're looking at. Normally, when apps get minimized, they swap a good chunk of their memory to disk - they still use that memory, just not now, so that data gets swapped to disk, so that other currently active applications can use it. On WinXP, windows is very ...

Very out of date software is a huge security threat... This popular myth is based on the preassumtion that updates do not introduce new invasive features and new technologies that can easily be abused (in other words: the preassumption is that the updated software will be more secure). Unfortunatel...

My proposal for the problem would be this: Normal maximum update-rate per application is once per month. However, if an app updates less often, it can accumulate a buffer of up to 3 updates. Thus, an app that does not put up an update for 3 months, would be able to trigger 3 updates in quick success...

Oh dear, a lemming. Okay, i'll refute this one post and them simply dont bother. Lets first tackle your win7 problems. My proposal is: Don't use computers that run vista or seven. It sux. Some may say that XP is old, but that doesnt say anything about efficiency. Windows XP is the oldest still suppo...

Correct. If an application just puts everything into the app dir as an executable and multiple "Dynamically Linked Libraries" (DLLs), that would work just as well, but for portability, just downloading a statically linked app is easier, because you dont need to figure out IF the dev actual...

Lets first tackle your win7 problems. My proposal is: Don't use computers that run vista or seven. It sux. Some may say that XP is old, but that doesnt say anything about efficiency. Some may say that xp looks less fancy, but only a moron would accept fancyness if it comes bundled with much more pro...

Sounds good. However, an option may not even be needed. One could just dump the in-ram db to disk in long intervals IF changes were made - i.e., every hour. That should for most situations provide enough crash-robustness. P.S.: I myself am a PStart user. I tried out asuite about a year ago, but went...

Keep in mind that a database behaves very differently to XML or configfiles. SQLite doesn't automatically compact the DB, unless the coder regularily instructs it to VACUUM. Next up, if you start to use the DB like a DB... that is, to frequently commit small changes (like, i.e. usage stats of apps),...

Sorry, but this is simply untrue information. Dynamic linking means that libraries which an application needs, are stored in seperate files (think "DLLs"). When the application is launched (or in some cases afterwards), these libs are then attached (linked) to the application. It's called ...

Current subdiscussion split off to here:
http://www.portablefreeware.com/forums/ ... f=1&t=6763