The Un-Official Proxomitron Forum

Full Version: mediafire downloads
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
on some of those programs that "force" an install into "program files", i've bumped into times that if i install an "antiquated" version first, then install the "latest-and-greatest" on top of it, that the "antiquated" version will 'allow' me to install somewhere OTHER than "program files", then the upgrade stays in that non-prog-files folder...

i suppose it's really not "that" important (so long as your firewall has "parenting abilities") to avoid 'program files' - i'm just too freakin' paranoid to put something where every trojan-writer on the planet "expects" it to be, so to speak, lol...

in addition to LiberKey, give this one a try -

as for "creating" my own portables, the office has access to (albeit an older version) "VMware Thinstall" [now called ThinApp] - though i only use it for the "tricky" portablizing that freebie "sandboxies" can't "wrap around"... i use JauntePE for most -
(Aug. 24, 2010 01:54 AM)fpout Wrote: [ -> ]I'm amazed at the susceptibility of Proxo about Header-filters' names!

Quote:Don't import "URL:" style header filters into this config without editing!
They have a special status which lets the header filters sort order swap
between two states, making the order in which the filters match unpredictable.

Converting a "URL:" filter to one that doesn't interfere is easy:

[HTTP headers]
Out = TRUE
Key = "URL: Kill (Out)"
Match = ""
Replace = "\k"

[HTTP headers]
Out = TRUE
Key = "!-|||||||||||| URL: Kill (Out)"
URL = ""
Replace = "\k"

If you need to match the protocol, there is a global variable "uProt" for that:
URL = "$TST(uProt=http:)"
JJoe, thanks for refreshing my memory about Sidki's config Readme.txt ! I did study it with attention, but that was years ago, and just as all that old school material, seems it has gradually vanished in my head ...
My fault ! It's clearly explained there, and I was inattentive when I imported Inminente's Ghostery filter for Test. A that time, it was just for a temporary test, and, as it worked, I just left it in my config and then forgot to finalize it properly.
No more mystery.
You're right, leaving Outpost in ProgFiles is a strong potential weakness. If I find some time, I'll try your trick.

What I understood from your post is that I must:
1- cleany uninstall all of it
2- first install some obsolte old version
3- install the good one OVER the old one and choose "D:\util\Outpost\" (for instance) for install location
... is that correct ?

** Just threw a brief glance to : - Seems promising, whith lots of progs, I will dig it, indeed.

** Am not too fond of Thinstall: I have a portable version of Office 2003 - works well, but thinstall leaves lots of temporary data, files, folders in "C:\Documents and Settings\j\Application Data\Thinstall\Microsoft Office Professional Edition 2003\" between sessions, which I do not overlike.

** AutoHotkey is very neat to portabilize any application, but requires you to record ALL the changes the appli does in Windows registry during it's run, using REGSHOT for example, and then you have to create the file.reg in the portable folder (simple).

** I didn't know about - JauntePE - but I just threw a very superficial look at google, and the 3-lines summary I got lets me guess it's some kind of Automatic in the portabilization process, doesn't require intervention in the registry, isn't it ?
Slipped it in my bookmaks for further investigation.
Thank you.
i don't know if that trick will do the trick for Outpost...
give 'er a try and report back - but let's start that in a new non-sidki thread, we've kinda landed in the wrong spot with the "tangent" Big Teeth...
Pages: 1 2
Reference URL's