On Fri, 14 Jul 2006 00:38:46 -0700, "cfman" <
[email protected]>
Long post, so part 2 of 2
I want to relocate this Document & Settings folder from C drive to D drive
permanently. I want to relocate all data/document/personal to D drive
However I've noticed that folders such as "LocalSettings/Temp/*.*" tend to
have virus/adware/spyware etc.
Yep - you already know why moving all of D&S isn't the ticket
OK, this will go through the whole thing from before you install
Windows in the first place...
1) Decide what partitioning you want
You don't need two physical hard drives to separate the core software
installation from data and other content. You can partition a single
hard drive so that it appears to be multiple drives. Typically, you'd
create a porimary C: for the installation and an extended partition
containing logical drives for everything else.
I'l use the word "volume" from now on, to refer to partitions or
logical drives that can be accessed by a drive letter. Each volume
can use one of three file systems:
a) NTFS
- no data recovery or interactive repair tools
- no access from DOS, DOS mode or Win9x
- only choice if files are over 2G and 4G in size
- only choice if you want file-level user security
- efficient for small files
- efficient for large numbers of files per directory
- paging-efficient 4k clusters even if > 8G
b) FAT32
- good data recovery and interactive repair tools
- access from DOS mode and Win9x if < 137G
- no support for files over 4G (some contexts, 2G)
- XP can't create volumes over 32G (use other tools)
- paging-efficient 4k clusters only if < 8G
c) FAT16
- better data recovery and interactive repair tools
- access from DOS, DOS mode and Win9x if < 137G
- maximum volume size 2G (4G if only for NT OSs)
- tiny file system structures, but larger cluster sizes
See
http://cquirke.mvps.org/ntfs.htm
If data recovery is more important to you than being able to block
data access from other users, I'd avoid NTFS for data volumes. In
fact, because there's not even an interactive repair tool for NTFS, I
currently avoid NTFS altogether, and use a FAT32 C: just under 8G
(8174M) so that I have paging-friendly 4k clusters.
Plan what you will put where. For example, by keeping all core code
off volumes other than C:, I can disable System Restore on all volumes
other than C: - thus reducing head travel and overhead.
Plan your partitioning for speed. The further "away" the volume, the
slower the access may be if most activity is at the start of the drive
in C:. I keep C: small, so that no matter how fragmented it is, the
heads never have to travel very far, and the next volume is not too
far away. Next, I use a 2G FAT16 (!) logical D: for data, for ease of
data recovery; only small user data files go here. Then there's a
huge E: that starts pretty "close" to C: and goes on for most of the
drive, and then a small F: at the end for seldom-used crucials.
Plan for survivability and ease of maintenance. You're likely to
suffer crashes and bad exits, and that means having to wait while XP
auto-fixes/botches the file system on startup. If that's one huge C:,
you will wait for ever or you'll bad-exit (again) so you can Esc the
brief "I'm going to tie up the system for hours" prompt. If C: is
small, it will take a time short enough to live with, plus whatever
gets messed up won't mess up your data.
I apply the following to volumes C: to F:...
- C: core code and temp, small SR, allow AutoChk
- D: small user data, disable SR, disable AutoChk
- E: everything else, disable SR, disable AutoChk
- D: cold storage and backups, disable SR, disable AutoChk
If you want FAT32 volumes over 32G, you have to use better tools than
what XP provides. I use BING from
www.bootitng.com without installing
this as a boot manager, i.e. cancel install and do "partition work".
Due to bugs, the best DOS mode FDisk is limited to capacities < 100G,
while the standard FDisk from Win98SE and earlier fails around 50G.
2) Install your OS(s)
If you want to dual-boot to the DOS mode part of a Win9x, you can, as
long as you do not use that DOS mode over the 137G barrier. With the
partitioning I use, I use DOS mode's Scandisk to maintain C: and D:,
preferring it to ChkDsk/AutoChk because it allows interactive control.
To do this, you would first "install" the DOS mode to C:, e.g. by
booting the relevant DOS mode diskette and using Sys C:
I'd use the DOS mode from Win98SE, as it supports FAT32 and has an
effective EBD (Emergency Boot Disk). Anything older than Win95SR2
will not work with FAT32 and should be avoided.
Once your DOS mode is in place, you can install Windows XP and it will
preserve your previous OS as a bootable alternative. See also:
http://cquirke.mvps.org/multplan.htm
http://cquirke.mvps.org/multboot.htm
http://cquirke.mvps.org/multos.htm
Do not create multiple user accounts (more on that later)
NB: Do not do anything else after installing XP until (3) onwards!!
3) Set up your shell locations
Often (but not always) you can get Windows to track path changes by
right-dragging things around (rather than the usual Copy, Cut and
Paste) and then renaming them. The trick is to do this early, before
secondary path references have been derived from initial values!
First, we will de-bulk and them move "My Documents"
- start two instances on Windows Explorer and tile them
- navigate destination window into E:
- navigate source into D&S, user account, My Documents
- rt-drag "My Music" to E:, then rename "MUSIC"
- rt-drag "My Pictures" to E:, then rename "PICTURES"
- start Movie Maker, then exit it
- rt-drag "My Videos" to E:, then rename "VIDEOS"
- go up a level in your source window
- rt-drag "My Documents" to D:, then rename "DOCS"
- rt-click "My Documents" on desktop, Properties; set to D:\DOCS
Next, we will create and populate an E:\SUSPECT subtree for incoming
material, workspaces, and other high-risk things:
- navigate destination window to E:, create and enter SUSPECT folder
- navigate source window to Local Settings, App Data, Microsoft
- rt-drag "CD Burning" to E:\SUSPECT
- navigate to base of user account
- rt-drag "desktop" to E:\SUSPECT
- navigate to base of "AllUsers" user account
- rename "desktop" to "alldesk"
- rt-drag "alldesk" to E:\SUSPECT
- create new folder OEMAIL in E:\SUSPECT
- create new folder IMESS in E:\SUSPECT
- run OE; Tools, Options, Maint.., set mail store E:\SUSPECT\OEMAIL
- exit and run OE again, OK
- run MS Messenger; Tools, Options, Pref..; set E:\SUSPECT\IMESS
- delete "My Received Files" from D:\DOCS
- run IE; Tools, Options; set IE cache to 20M (don't relocate)
I don't use MS address book or Outlook, so if you want to do battle
with those data locations, insert your attempts here. I just walk
away from the whole mess and use Eudora instead...
- create location E:\SUSPECT\ATTACH
- install Eudora, choose Custom
- set data location as D:\DOCS\E-MAIL (it will create it)
- run Eudora; Tools, Options, Attachments; set E:\SUSPECT\ATTACH
- so safe mail can back up with DOCS, but risky attachments exluded
Finally, restart Windows and do some clean-up (be careful here!):
- run Regedit
- search for "\My "
- if reference is incorrect, change to point to new location
- the main one is setting IE to dump in E:\SUSPECT not D:\DOCS
Many 3rd-party apps will derive their paths from the shell paths you
fixed earlier - that's why it's best to do those changes first. You
can also apply these settings directly through their options, e.g. get
WinZip to use E:\SUSPECT\UNZIPPED not C:\UNZIPPED, Firefox to download
to E:\SUSPECT instead of Desktop, Winamp to rip music to E:\MUSIC
instead of "C:\My Music", etc. Fortunately, even if apps (or users)
do dump on the desktop, that's not in C: anymore, so no bloat.
I keep Temp and "Temporary Internet Files" for speed, though I trim
the size of "Temporary Internet Files"
4) Installing large apps and games
It's crucial to stop junk dumping in C: if you keep C: as small as I
do (i.e. as a 7.99G FAT32). All apps should be installed as "custom",
so that the installation path can be controlled. I install MS Office
and core deeply-integrated apps such as av and CD writing on C: for
speed, but all games, multimedia titles etc. go on E:
5) Debulking C: as Windows Updates pile up
Freshly-installed XP is highly exploitable, especially if pre-SP2. As
you apply Service Packs, patches and updates, the Windows subtree gets
bloated with old code files and so on - eventually, for every one
active file, the heads hgave to step over 3 to 4 "dead" ones.
Once again, you'd open and tile two Windows Explorers...
- navigate source to Windows base directory
- navigate destination to E:
- create and enter E:\XPSTORE
- rt-drag all (hidden) $NT... subtres to E:\XPSTORE
- rt-drag "ServicePackFiles" to E:\XPSTORE
- repeat the above after every update binge
- defrag now to consolidate free space
- defrag a week later to optimize renewed code
The above assumes you've set Windows Explorer to show all files, etc.
6) Multiple user accounts
Short answer: Don't.
Long answer: If you want to use multiple user accounts, then good luck
in figuring out how to set up the "default" account template so that
intelligent choices are used for shell folder locations and IE's web
cache size. By duuuuhfault it will be the same "all deeply-nested in
C:, and lumped together in My Documents" and "huuuge web cache".
Or you can run after these settings every time someone creates a new
user account so that Johnny can have a different wallpaper to Jenny.
------------ ----- --- -- - - - -
Drugs are usually safe. Inject? (Y/n)