Symbolic links are only available in Vista and later, but allow links across network shares. Hard links (for files) and junctions (for folders) have been available on ntfs since at least win2k, junctions can cross local volumes but hard links only work within a local volume. Hard links can be used to save space if you need the same file stored in more than one folder - e.g. if you were building a "x-in-1" windows install disk. Junctions can be used to redirect folders - this can be useful if you have limited space available on one volume but need a folder to appear there. http://en.wikipedia.org/wiki/NTFS_symbolic_link http://en.wikipedia.org/wiki/Hard_link dfhl duplicate file hard linker http://en.wikipedia.org/wiki/NTFS_junction_point sysinternals junction
Some unofficial versions of mkisofs have a -duplicates-once switch, which might save a little space if your windows install is from plain xp files rather than an image. But 400mb is a lot to cut, unless this is a x-in-1 project. http://www.boot-land.net/forums/index.php?showtopic=7281
A light mist isn't enough, you want to immerse it like a Cray2 for proper cooling. * * MSFN is not responsible if you use water rather than the recommended fluorocarbon coolant.
thegreenbow.com vpn client doesn't look free, and the kiwi and memtest links are crossed over. In "Disc mounting" you could add Imdisk http://www.ltr-data.se/opencode.html#ImDisk Thanks for the list.
You could try setting Image File Execution Options on cmd.exe - no idea if it would work though... Running procmon for the whole install might be a better bet.
You could use a virtual machine - set how much ram to allocate to the VM, then test your app on the remaining physical memory. Vmware server lets you prevent the VM from being swapped out, not sure about others.
You could set the victim pc use a dns server running on the other pc, or just edit the hosts file of the victim, if it really is just google you want to avoid.
I use an (htc) xda orbit, it takes most of a minute to boot, sometimes crashes or becomes unresponsive, and has to be switched on for the alarm to work. And yet, I'd buy another. I can't explain it...
If you actually want to monitor files and registry you could use InstallRite. But you might want to consider disk imaging software instead, quicker and cleaner than uninstalling stuff.
I'd stick with a single path, and don't play with mirroring ports or vlans or any of the other managed switch features until you know what they're for. Pretend it's an unmanaged switch for now