Seeking advice on installing a new hard drive
Does anyone have any advice on the following scenario:
My mate has two small (we're talking tiny) hard drives in his tower - one is 10 gig the other 6 gig. His CPU is quite decent and works well for his needs, he has plenty of RAM and a reasonable processor speed so I have offered him my old 40 gig HDD. What is our best option?
Should I (can I?) install the 40 gig as a third hard drive, and if so, do I run one of the drives off the CD/DVD drive as a slave or is there a better way? Or should I get rid of the current slave HDD (6 gig) and replace it with the 40 giga?
Also, at some stage I would like to get his O/S onto the larger, quicker drive. Any suggestions on the best way to do this, should I clone/copy his current master across to the new drive or re-install the O/S and just copy his files across?
Any advice will be greatly appreciated....
My mate has two small (we're talking tiny) hard drives in his tower - one is 10 gig the other 6 gig. His CPU is quite decent and works well for his needs, he has plenty of RAM and a reasonable processor speed so I have offered him my old 40 gig HDD. What is our best option?
Should I (can I?) install the 40 gig as a third hard drive, and if so, do I run one of the drives off the CD/DVD drive as a slave or is there a better way? Or should I get rid of the current slave HDD (6 gig) and replace it with the 40 giga?
Also, at some stage I would like to get his O/S onto the larger, quicker drive. Any suggestions on the best way to do this, should I clone/copy his current master across to the new drive or re-install the O/S and just copy his files across?
Any advice will be greatly appreciated....
0
Comments
Use ghost or another imaging program to image the OS to the new drive then copy the data over
Also, there's nothing like a clean install. Starting fresh, tweaking, adding all the must have software....call me weird, but it I love it.
Thanks again,
B
Of course you go Tex on us and put in a drive controler card and run any number that your heart desires (and wallet can afford).
Off topic for a sec, can I just say to Tex, I've read quite a few philosophies in my time but your signature takes the cake man!!!!!
Tex
as many as you can connect into it, but you can only have somthng like 23 volumes ( what windows can store stuff on ). minimum volume size is 8MB, biggest XP can do is 2TB, unless you have a version of server 2000 SP4 or server 2003 which supports LBA 64, in which case its 512TB lol
I'd be lucky to ever use 1TB.
Thanks for your feedback Armo.
This happens if I choose safe mode also........any ideas or suggestions????
Do I maybe have to do the install while the hard drive is connected to his motherboard????
when you install windows, it configures itself on the hardware in the machine, it communicates to the machine though the HAL.dll ( which you'll see alot of people will have troubles with ) if the HAL cant communicate with the hardware XP will not run, and the only real way to rebuild the HAL is to do at minimum a repair install of XP, or a full blown reinstall... unless the hardware is exactly the same in both machines.
you will have to have the drive connected to the motherboard you intend to use the hard drive with.
OMG
Tex
Also, the reason I was unsure was cos I've put other hard drives into other towers twice before and they've booted up no worries(O/S - Windows98SE & Windows2000), mainly to retreive files or folders. I apologise if my ignorance annoyed you Tex.
Thanks Armo for the constructive advice.....
My rule of thumb is never convert dos partitions to ntfs. Back your data up properly and format the partition the right way. Then copy the files.
But maximizing the performance of my box's may be more important to me then you also.
Tex
You screw up the performance of the drive doing this.
As in don't do it. Is that clear?
backup the data. Format the partition properly with ntfs. then copy the data back.
I can't make it much clearer.
Converting from DOS to NTFS is a bad idea. BAD IDEA. And I told you EXACTLY what you needed to do and WHY it was a bad idea.
If you can not understand this I really doubt you are going to understand the technical details and underlying principles of what actualy happens on the conversion and why its bad. It phucks up the performance. don't do it. Just leave it at that!
I told you exactly what to do to fix it right?
Not sure how else to help you mate? I mean this is about as simple as this can be explained. You gotta work with us so we can help you.
Conversion BAD! No DO! Makes disk very SLOW!
Tex
That was the problem here.
Look I am not being a smart aazz but.... Man this would be much easier for all of us in the future if you didnt assume stuff like this. Your just not real knowledgable right now. And we want to help ya but....
ASK this type of question first.
The answer was simple. XP sees fat32 fine and just copy them. You made the problem way more complicated by assuming stuff like this.
We now have a couple pages of posts about converting fat32 to ntfs that you couldnt understand, have no relevance to solving your problem anyway.
Again no one is picking on you. Just ask the basic questions first and quit assuming stuff. Its just getting you in trouble. We are ALWAYS happy and willing to help. But sometimes those basic assumptions your making are flawed. Don't worry though as the good news is that you will get better at this the more you read here and the more you listen. Lots of our long time regulars came here as complete NOOB's that could barely turn on their computer without help. And now they are very strong technicaly. They know all about installing, repairing and tuning XP, watercooling and overclocking etc... And to be honest it's been fun to watch them grow in their abilitys. We all actually enjoy this and enjoy leading the newbies into the future.
Best of Luck!
Tex