brynn:Thanks for the links to the lists. Am I to assume from their existence that developers basically don't hang out in these forums? Anyhoo...
By "main installation disk" you mean your hard drive? What do you mean by "finite number of writes"?
For the technical skinny on SSD's see their Wikipedia entry,
https://en.wikipedia.org/wiki/Solid-state_drive , but here are the basics you ask about:
I have multiple drives on my system (which I built myself), not just one. Most are the old-style ATA platter hard disks, but my Windows boot drive is a new type called "solid state disk" (SSD), which is not a set of genuine disks that spin around, but rather a solid-state circuit. This new type of drive is much faster than the old disk type, but it does have a few drawbacks. One of the most significant is that it can perform only a limited number of writes before it fails. The old-style ATA disks are not subject to this limitation: as long as the mechanical parts of the drive continue to perform, i.e. the read-write arms and heads and the spinning mechanism don't wear out, your writes are unlimited. But with SSDs, as the Wikipedia page notes, "Each block of a flash-based SSD can only be erased (and therefore written) a limited number of times before it fails." The drive's firmware attempts to ensure that writes are distributed evenly over the disk so that no single sector is written to more times than any other, and therefore the drive will last longer. But ultimately the limit will be reached, and the drive will no longer work.
What this works out to is that ATA hard-disk failure is usually mechanical, whereas SSD failure is electronic, and one of the ways this occurs is when the write limit is reached to even a single block of the drive--I'm pretty sure that even just a single block will screw the drive. Therefore it behooves one to reduce the number of read-writes to an SSD, and the best way to do that on a Windoze system is to offload temp directories of all kinds, including cache folders, to an older-style platter disk. At some point in the future SSDs will have a sufficient number of read-writes that this will doubtless no longer be much of a concern, but we haven't reached that point yet.
And let me say that I looooooove my SSD. It makes things a lot faster even than the old Western Digital Raptor series of speed-demon ATA drives, and more stable into the bargain.
what are you going to do when MS moves Windows into the cloud?
Same thing as you. Actually from everything I've heard or read about Win10, M$ has already made the registry and the OS in general a lot more difficult to deal with and customize, so I've already decided that once Win7 is no longer a tenable OS--and hopefully we won't get there for another five or six years yet--my next home system will be exclusively a Linux box. I probably won't try to dual-boot because with UEFI instead of BIOS, dual-booting has become more complicated. I'm not an IT pro, just a "power user", so I don't want to take the time to learn about the new issues raised by UEFI if I don't have to. This will probably mean I have to limit gaming solely to games that will run on Linux, but that's the way it goes. I've wanted to go Linux for quite a while now but a bit of experimentation revealed that the learning curve is just too steep. Can't justify the time until I'm forced to it. But that time will eventually come.
it works from a USB drive. Wouldn't that be your best solution?
Unfortunately not. I put the portable version on a flash drive and it ran, but it still hard-coded all working directories to C:\.
Moini:Thanks for the info. Symbolic links may well be the way to go, but I'd like to try the scripting first, as it will work directly with Inkscape instead of employing Windows as an intermediary. So, can I ask for two clarifications?
1. You're talking about a standard DOS-style startup batch file, not some special Inkscape macro language, right? (Hopefully not Windows Scripting Host, as I have no idea how to work with that.)
2. I took a look at the manual's section on command-line options and the command you adduce is nowhere to be found. Therefore I have no doubt that I'll need more help. To get further details on how to set this up, am I really going to have to subscribe to the lists to which brynn kindly links, or is there a developer's forum somewhere else I can ask on? Or might the launchpad site which opens from the Inkscape Help menu be a good place to ask? I'm not sure IRC is a good way to get scripting help--too complicated an issue; and I haven't used a listserv in so many ages that I've forgotten how, and also I have to say that I don't look forward to yet more stuff cluttering my inbox. Don't get me wrong, I'll do it if necessary. Just asking.