One of the functions of UPnP is opening ports on routers, modems, etc at the request of applications when they need to receive incoming connections. Tor relays can utilize it as can torrent, file sharing software, anything that uses P2P technology. It's likely that some games require it as well. For the average user, it allows them to use such applications without needing to know how to open and/or forward ports manually. It effectively allows applications to create paths for their traffic through firewalls. The big issue is the potential for misuse, eg a compromised application, trojan, etc. A while back, Flash Player could be exploited to use it maliciously. IMO, the ability to open or forward ports in their router is something a user should know how to do. Regarding WPF, I generally disable it, then re-enable it when I'm done.
Regarding SandBoxie and sandboxed browsers. When a browser is run in a sandbox, configuration changes are also made in the sandbox, not in the original files. If that sandbox is emptied when the browser is closed, those changes and settings are lost. This is a major issue with extensions like NoScript and Request Policy. On a unsandboxed XP unit running SeaMonkey, the Request Policy extension stores its settings in Code: C:\Documents and Settings\{UserName}\Application Data\Mozilla\SeaMonkey\Profiles\{8randomcharacters}.default\prefs.js On the virtual test system with the sandbox on the RamDrive (drive G on my test unit) the path to the sandboxed copy becomes Code: G:\Sandbox\{UserName}\DefaultBox\user\current\Application Data\Mozilla\SeaMonkey\Profiles\{8randomcharacters}.default\prefs.js In order to save permissions set in Request Policy and other extensions, the prefs.js file needs to be recovered. You can either do this manually or use the SandBoxie quick recovery option. Automating the quick recovery will require setting exceptions to the file types you're asked about. It may be possible to have the delete command execute a batch file that first recovers that file, then invokes the standard delete command. Have yet to test this idea.
@noone_particular. You could also instead of using quick recovery set Sandboxie to use Direct Access (OpenFilePath) to the prefs.js file. This setting essentially punches a hole in the sandbox, at that particular file location so any changes will be saved outside the sandbox.
I was hoping that there was a better way. When I added the path to the folder containing prefs.js to quick recovery, I was prompted for every file in the folder. Can OpenFilePath be used with just a single file? Could you post the proper syntax for the entry the user would need to make? I was somewhat disappointed to find that RP stored its settings in prefs.js. From a privacy/security perspective, it would have been preferable for it to use a separate file. Although I've used SandBoxie to prevent usage tracks from being saved, the browsers that I ran there were already configured. I haven't tried to save specific settings and extension configurations from within the sandbox. My concern is this. By giving a sandboxed instance of the browser write access to prefs.js, can undesired or potentially malicious changed end up being saved with the user unaware? By doing this, are we creating an exploitable hole in the sandbox?
The File Access > Direct Access can apply to a file or folder. Just input the location path (in this case prefs.js) by clicking on the Add button in Direct Access. [DefaultBox] OpenFilePath=%AppData%\Moonchild Productions\Pale Moon\Profiles\<random 8 character>.default\prefs.js // e.g. of Pale Moon browser. Replace Pale Moon with browser you use. // This also seemed to work in PM. OpenFilePath=palemoon.exe,*\prefs.js* // Replace palemoon.exe with name of browser executable you use. Note: For security reasons, this setting does not apply when the program executable file resides within the sandbox. This means that (potentially malicious) software downloaded into your computer and executed, cannot take advantage of this setting. (source: Sandboxie-OpenFilePath page) I use another app that supposedly adds protection to extensions running in the browser. The Quick Recovery method does list the files located in the Profiles folder and you then would recover the prefs.js file (replace the existing file with this one) to same folder to keep any changes. [DefaultBox] RecoverFolder=C:\Documents and Settings\<UserName>\Application Data\Mozilla\SeaMonkey\Profiles\<random 8 character>.default // Recover prefs.js file from the list to same folder.
OK, just to refresh, Ive done everything most of us know about to make a browser the default plus the "Set program Access and defaults" . FF says it IS the default browser and IE still stubbornly insists that it is ( when I hit SBXE quicklaunch). As far as command line stuff, well, I have always associated that with the black screen in command prompt. I wasn't aware you could "put a command line into the field in the shortcut properties" so I've learned something. Back to post #525, after a few trials and error messages, I finally got it to work. Now Sandboxie loads FF. In Sandboxies Resource Access > File Access > Blocked Access, I navigated to Main IE Folder in Programs, and just put that in. Was that the correct way to do this or was I supposed to put in IE exe only? Sandboxie seems to have added the bolded part "C:\Program Files\Internet Explorer\Device\Mup\ " ... What does that mean?
From Post 546 Yes to both. Unlike FF (27) IE6 doesn't actually tell you if it is or is not the default B but just gives you the option to check if it is, which of course I've left unchecked. I'll give M$ the benefit of the doubt in that should the box be ticked, I'll assume it would lead to a dialog box giving you the option to make it the default.
What is \Device\Mup\ Sandboxie Settings Popup message: Windows file sharing can be used to circumvent Blocked File Access settings. Therefore, a setting was added to block access to the Windows file sharing service. http://forums.sandboxie.com/phpBB3/viewtopic.php?p=40923 The shortcut command I have for my default browser: "C:\Program Files\Sandboxie\Start.exe" default_browser (Target field) "C:\Program Files\Sandboxie" (Start in field) The other command posted should work as well. In Blocked Access (ClosedFilePath) you can either select the IE folder or iexplore.exe Setting this will only prevent IE from starting when right-clicking & selecting run sandboxed from the list of sandboxes that you applied the setting to. Just clicking (not right clicking & run sandboxed) on the IE Icon will start IE unsandboxed. You could also put IE in Sandboxie 'Program Alerts' to notify you when IE is launched outside any sandbox. If you want to prevent IE from starting altogether: Putting iexplore.exe in 'Forced Programs' and 'Blocked Access' settings would prevent IE from starting even when just clicking on the IE icon. As you mentioned though, 'Forced Programs' is not available in the free version.
Thanks for your tips. Really appreciated! Haven't followed your link yet, but yes, I forgot to mention that popup was exactly what I saw. My Shortcut looks exactly like yours above. I simply didn't have time to note every action I did, much less know what I did in chronological order, but that seemed to be the only way I could get it to work. @noone_particular ...... that means it must have been a great app. I spent some time and sadly all I could come up with was multitudes of hits referring to changing postal addresses and when I tried to narrow it down by putting "utility", I got changing address for power company and the like. There's no problem at all with all of my (authentic) product codes/keys. The packaging and disks are stored away safely. However, I'm not going to risk having M$ on my back for activation, (yet) which I'll probably get prompted for if the hardware changes are "substantial". No one seems to know exactly what M$'s "substantial" refers to, from one major component, to a number of "lesser" components or anything in between. Once the need for activation is in place, I have a time limit to get it sorted. I've decided since excel is pretty important to me, I'm going to check out the possibility that the computer still might be OK. Capacitors look fine and a friend gave me a 300W PSU yesterday which should be enough for whats in it. Gotta sort the initial problem of why the front power button isn't working. Hoping its just a case of re-seating the plug or something. It is more than capable for office jobs. Exploring the free alternatives, they are either strangleware or have adware or other things you need to install like java.
It is. It was called COA2. PC Magazine still has it. Development stopped shortly after XP was released. http://www.pcmag.com/article2/0,2817,7822,00.asp Notice on the page it says that the Installer does not work with XP SP2.
That counts me out as I don't do online transactions. I didn't realize it was paid. I'm on SP3. From what I can understand, rather than shift a program it sets up pointers to it, (kinda in line with its title). In my case I would be solely dependent on having the (2nd) drive with the program on it in place. I've been doing some more digging about all this and it seems if I can even boot XP Pro from current computer (hardware drivers like graphics card may cause conflicts) it most certainly will trigger re-activation. Seems OEMs are not only tied to hardware specs, but unique IDs. Can't find conclusively whether phone activation is even doable for XP and/or XP Office now. Guess I'll have to ask them and see. I've NEVER re-installed the OS in 12 years, and therefore never had to reactivate. They certainly couldn't accuse me of overstepping the mark with multiple installs. Well in hindsight I would have paid the extra for a retail version if I knew at the time my OS and Office, was totally dependent on unique hardware.
I've never done a phone activation. The last online activation I did was last year. I used a Dell reinstall disk in VPC and forced activation through Tor. If you can install that drive as a slave and image it, you can get it back to where it started if activation becomes a problem. I haven't tried it but isn't there a repair option on the CD?
Been a while, but don't recall doing a phone activation. I know when formating and reinstalling the OS I did a online activation. I seem to recall a reg tweak which told Windows (MS) it's already been activated.
Regarding both the OS and Office XP CDs they are the full install legit ones with the holograms on them and the keys on the their covers, BUT the rub seems to be they're OEMs. I know you can do repairs (never done one) but cant remember whether you needed the disk or not. Just before the PSU went belly up, I was getting ready to backup again. Earlier, I did a back up with Aomei, but looking further into it on Wilders here, I've come to be dubious about it's reliability and other issues. Another member put me onto a preferred version of Macrium Reflect Free 4.2.3638. I have the installer, but didn't get it installed before the incident. I have the XP Pro drive as a Primary Slave right now. A few questions. The XP Pro System Partition was C: and has now become D: Is that going to make any difference in an Image? I'm only learning about imaging. Imaging an OS not in use as opposed to one you're using, is there any difference, or any caveats?
Ive been digging into this for hours, and the more you look the more possibilities there seems to be. XP is different to later OSes. OEMs are different to retail and pre-activation MIGHT be tied to your BIOS rather than hardware profile. My custom made system was pre-activated.
There are eight hardware changes they watch in XP http://en.wikipedia.org/wiki/Microsoft_Product_Activation Long ago, someplace, I read that if you change one or two things, reactivation will not trigger. Changing a harddrive on OEM laptop twice did not trigger it for me.
It is always better to do a "cold" image from a bootable media or another OS. I always have two or more OSes installed on my computers and image one from the other. Aomei works best with newer versions of Windows but I've had no problems with Xp as long as I use sector by sector backup and restore. The earlier versions failed to image the Xp boot sector correctly in the default imaging mode. They might have fixed this by now but I haven't tested it. I don't use Aomei for my older Xp computers, I use Powerquest Drive Image 2002 and image and restore Xp from Windows 2000. I'm not sure how the Xp pro disk being D: will affect imaging and restoration. It would have been much better to image the disk before it was put in as a slave drive but how it will be affected depends on how the active system is accessing it. Windows has a tendency to mess up other Windows systems. It might just boot as C: if it was made the master disk but it might have some issues. I would keep the Aomei image. It might be useful if there are problems with the original system disk. I've never tried to activate Xp from TOR. I'm impressed that it worked. MS does log IPs used for activation. I've done several Xp VMs recently and activated online through a VPN. No issues at all and I found that once you create a VM using one platform, you can do multiple installs and use the same product key. From the activation viewpoint, it is the same hardware. I created three different XP VMs, two from old Xp pro installations using Paragon Virtualization Manager and one from the XP mode base VHD for Windows 7 Xp mode. The Xp Mode disk was nice because it was a clean Xp system and had SP3 slipstreamed. I did the same VMs on two platforms, Virtualbox and Virtual PC 2007. I just needed two Product keys for 6 VMs.
Great overview. I agree with these sentiments: This is a prized example of speaking with a forked tongue:Your privacy has either been violated or it has not...it is either intrusive or it is not. If MS are being "somewhat" secretive aka vague, I think we can safely assume they are being umm secretive.
Thanks for weighing in on this MisterB. Im tempted to carry on the conversation regarding Aomei in the "backup imaging & disk mgmt" forum. For me, with a strong focus on keeping XP for reasons discussed within this thread, plus the part Aomei may have to play in this means I'll carry on here for now. Yes the bootsector issue was what worried me some. I've actually done 2 Backups, but I don't recall the settings I used. I *think* one of them was the sector by sector option. I don't want to install it on this System and I'm not sure if I can check some way just navigating a "cold" system. I wondered about the Drive Letter assignment arrangement and your comments confirm what I thought. Booting in this system is going to be risky. In any case, with a different Mobo MS for sure will require me to reactivate which at this point I want to avoid like the plague. The best option would be to see first see how my computer will perform with a working PSU and to rectify the dead front power button issue. Hopefully nothing too major. If all is well I'll be in a much better position to do imaging and so forth. Going the VM route sounds a great way to go, but I know nothing about it and haven't pursued that avenue because I don't have enough RAM. (512MB) It's unlikely I will be in a position where that will change. At a pinch I may be able to wrangle 1Gig but that's not a given and that's assuming the RAM is OK after the incident.
I don't know where forum policy would stand on posting instructions on how to route activation through Tor. I'm surprised that they weren't blocking exit IPs. As for the CDs, I'm not sure what the CD I'm using really is. It is a Dell CD. It calls itself a reinstallation CD but it doesn't seem to be hardware specific. I've used it on a couple of physical systems and half a dozen virtual systems. It always requires me to enter a product key. Oddly enough, the key on the PC it came with doesn't work but the key from another Dell PC does. @Reality XP has issues with the drive letter changing. When I converted this box to dual boot, XP gave me a very hard time. I've also found that some updates for it seem to be hard coded for drive C. If at all possible, try to boot the old hard drive from the same position it originally was in, using the same drive letter it used before. XP does seem touchy regarding how you change a drive letter. It's better if you can change it from within the OS instead of using a separate application or OS. Issues like this along with "activation" are the main reasons that I don't like XP and newer systems. By comparison, my modified 98 unit doesn't care if I move it or change the hardware. It adapts, reboots, and goes on like nothing happened without complaining to MS that the hardware changed. I've been wondering about Win 2000, whether it's as picky about hardware changes, and whether it's possible to recombine it with XP and gain XPs improvements without importing its problems. Regarding imaging software, I wouldn't rely on an application that runs from within Windows. The OS should be dormant when being imaged. I've had good results with an Acronis rescue CD which is basically a single purpose linux OS. Regardless of what you choose, you should try out its restore abilities at least once before you actually need it. If you have a spare hard drive, try it there. I haven't found the size of the partition to be a major issue, as long as the image fits. OTOH, the type and location of that partition are details that XP doesn't like changed. Regarding the power button issue, I'd suspect that this was part of a power supply problem. Does your BIOS have options for controlling that buttons behavior? If yes, a corrupted BIOS could also cause that problem. Regarding MS Office, is activation or a lack of an install CD the issue? I don't have it so I can't see what's required to move it from one PC to another. The closest I can get is that oxymoron called Microsoft Works, which does include an old version of Excel. I might be able to install it on one virtual XP, then slave another copy of XP to the system and see if it can be moved.
Doesn't the online registration include the re-activation of Windows XP? If I type in the Run command field: oobe/msoobe /a This brings up the Windows Product Activation Window. In my case though, Windows is already activated. Didn't verify if the reg tweak would work even though the key is there, but has no data value. Regarding Drive letters and changes. Usually on the Master (C: ) drive resides the Windows OS, but haven't tried installing it on slave drive. I imagine Windows would probably have issues. In my former dual boot since I have 2 internal drives I just left Windows on the Master and Linux on the slave. I've had great success with using Macrium Free version 5 for imaging backups and restores. Built the PE bootable rescue CD/DVD and so far no issues using it.
I've never had to do a re-activation. Regarding msoobe /a, that is the command for activating Windows. On the test unit, I launched it via SocksCap which connected it to Tor's socks proxy port. I installed Kerio before this to block all other traffic. Worked like a charm. Haven't experimented with that registry tweak. Hopefully I won't have to ever reinstall XP again. I have images of bare installs of XP for both the physical and virtual systems.
I don't like the idea of another reinstall and re-activation. Was wondering though, what major Windows components besides IE were you able to remove without any issues. Between using the Add/Remove Windows Components (MS hides some components) using nlite and XPlite (still on trial version) I would still like to remove more components. I want to be able to use a third-party media player and keep probably the editors. Mostly interested in bare installs of physical system.
Didn't you say you had one of those volume licences? That's probably why but as I inferred earlier, working out M$ and all its variants regarding product keys and activation is a rabbit warren of possibilities. IOW it seems to be a hit and miss affair. Thanks for your take on this noone. Appreciated. All the more reason I ABSOLUTELY WON'T be booting the XP Pro System while the disk it resides on is still in the computer Im using and which was initially put in for recovery of my files. Booting from it was just a thought. Even if I shifted to the Primary Master I wont be booting it. As for 98, , I remember a certain person called noone_particular wondering if I was joking when I expressed some interest in it. Seriously, I think I better say I'm still joking. While my XP Pro is sitting there doing nothing, it's not causing any harm. Sit there it will until the hardware issues are explored. Thanks. Im not sure if the BIOS does. I was looking for my Mobo manual last night and it's around somewhere but strangely I can't put my hand on it. After avoiding the excess baggage type sites I finally managed to locate one from Asus. I'll have a look soon. I'm simply too embarrassed to elaborate on the PSU, but I will if you guys are too curious to contain yourselves.. That said, I can almost say 100% sure the two were totally separate issues. I have all the Legit install CDs. 2 for M$ Office (Small business) and one for XPPro SP1 all with their holograms. Now, I'm curious about the License agreement written on the Office CD covers. It says not to separate out the individual programs and that they all must be installed on ONE computer. It doesn't say that that computer has to be the original computer it was installed on. It just might be movable. Any experimentation to explore possibilities are welcome. I know on this computer ( my mums) there is a suite of non professional or more cut down type programs, it includes Word, but not Excel. Not sure what its called and for that I can't find the install disks and I'm not sure if there ever was. Back to my hardware issues. Unlike the dead PSU, the one Ive installed doesn't include a 2 wired (yellow and black) 3 pin (female) connector which plugs in near the main power plug on the Mobo. I searched online and some people said it wasn't necessary and was just a CPU probe. I wasn't satisfied and wanted to check the manual. For my Mobo it looks like it is necessary. Not taking any chances. I'll have to wait and see if I can source another PSU someone can lend me with that connection. In the meantime it will just have to sit there.
I've never bought Windows or a new PC. I picked up a PC at a yard sale. The disk came with it. As for the power supply, I'm the wrong person to advise you. I've done very little with the actual hardware beyond swapping drives or adding cards. Knock on wood, I've seen almost no hardware failures here.
