On Tue, Oct 27, 2009 at 4:02 PM, Howard <[email protected]> wrote: <snip>
> Update from the eastern front (aka client). SystemRescueCD is the tool! > It has taken more time to get files backed up BEFORE resizing and the > obligatory defragmentation drill. Watching much paint dry. The good > news is that the client has had to be at the courthouse most of the day. > Step one of two complete; existing NTFS partition is now smaller. > Vfat partition is now expanding. More defragmentation to follow. > > Were it not for backing up data files, SystemRescueCD could have fixed > this situation in one pass yesterday afternoon. Thanks to all that > pointed it out and, more importantly, vouched that gparted would treat > NTFS kindly. Woohoo; step two complete. L8r. > > Howard Glad it worked! Backups are always good to have just in case. :-) Experience is a good teacher, just wish I listened more often at times... Some people highly recommend redirecting things like the "My Documents" folder to a separate partition, but it can be a pain on occasion. I have tried it and it has definite advantages. (I say at times a pain, because not every Windows program pays attention that these folders are no longer located in the "standard" place. They still use C:\Documents and Settings\username\ anyway.) To redirect them, you right click on these special folders, click properties, and on the Target tab point it elsewhere... In this case, not being a computer savvy end user... I don't know what pain it may cause in the future when he decides to install some uber-cool program that doesn't pay attention to the pointers, or what existing programs may do, but it can be redirected. I didn't know about mklink before, but suspect it's either a server OS thing or post-XP. XP Pro SP3 doesn't have the command available (at least in the default environment path), I doubt XP Home would have it and as pointed out in this case, it wouldn't link from FAT to NTFS. * Note: never underestimate the possible stupidity of an end user. Big block that comes up and says something like "ERROR, table INCIDENT out of allocated space, program aborted at line 1328.", and the program closes. (Ancient text based system; HP 3000; soon to RIP.) The user runs the program again to "add more data", over and over again. Then I get a call "The data I just entered isn't coming out on my report." I investigate and call them back in a couple of minutes. "Did you see an error message that said ...?" *:-) Paul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en -~----------~----~----~----~------~----~------~--~---
