hardrive question

[cobalt6700]

ok then guys. im very quickly running out of space. my my windows hardrive (40 gig) is virtually full....and i wouldnt mind going over to SATA-II. so, how do i put my current windows (as it is) onto the new drive, without reinstalling windblows?

thanks guys :thumb:

gaz

edit - can you also run a SATA-II on a SATA-I port?

[Leeum]

You'll have to reinstall Windows if you go for a new hard drive. SATA-II is back compatible with original SATA so no worries there.

[Psykotik]

It depends on whether you're using an SATA drive at the moment Gaz.

If you are then you can simply use Norton Ghost or similar software to copy your partition across to the new drive and it should work as it does now.
I'd personally do a new install anyway though as it gives you chance to sort out all of the crap that you don't relly need. :-)

[jaguarking11]

Its called norton ghost. Find a older version Like 8.2 or something. Then you make a startup floppy and before you boot with it you install the new hdd. Boot up and clone over the new one.

And the sata 2drives should work on sata1 port but will perform as fast as the slowest component. Should not be a problem though.


Also how the hell do you survive with a 40gig drive? Ive been running a 250gig and a 100gig drive and the 250 is almost full and the 100 only has like 30gigs free. (no its not pron, I have a server for that with a 160gig drive in it)
Personaly I havent run less than 80gigs since the early p3 era. I remember paying 180bux for a 80gig drive. now I paid less than 100 for 250gigs. yeash times have changed.


EDIT: been beaten.

[Darv]

Will ghosting actually work? Don't you need extra drivers for SATA drives.

Regardless it's always a good idea to re-install windows every so often and you won't get any problems that way.

[Psykotik]

As long as Gaz is running an SATA drive now (the chance is remote going on the small capacity figure) then ghosting a partition across will be fine as the SATA controller drivers are already installed. The same applies to an SATA II drive installed on the same port.

Edit: No he's not running an SATA drive, I've just seen his thread in the Trading forum, so no Gaz, you'll have to do a clean install :-)

[Squelch]

Unless the SATA is native to the bios and not an addon it won't work with ghost. It seems several of the partition copying progs don't know about SATA yet.

[kurabii]

as a PC tech yes norton ghost does resize drive speed and calibrate quite nicely i ghosted a 70gb ATA hdd to a 250 SATA3 HDD. and it went nicely.

its only one norton product i trust :).

ESA

[cobalt6700]

uhhhh

ok.

:rolleyes:

so. ok reason i water to use a sataII drive on a sataI port is because i only have one sataII port, and the sataII drives seem to be cheaper, and then when i upgrade they will be better blah blah.

ok

reinstalling shouldnt be a problem. ill just have to fill up the 120gig with most of the stuff i want to keep, and then trasfer it over when i have installed the new stuff.

is there much of a preformace change?

thanks guys....

gaz

[Pug]

HDClone 3. (http://www.miray.de/products/sat.hdclone.html)

Get the drivers into windows and roll back your SATA/SCSI controllers to default MS ones before you image it. :thumb:

[cobalt6700]

HDClone 3. (http://www.miray.de/products/sat.hdclone.html)

Get the drivers into windows and roll back your SATA/SCSI controllers to default MS ones before you image it. :thumb:

uhhh. i dont have any sata/scsi devices.

and get which drivers?

:confused:

[Pug]

uhhh. i dont have any sata/scsi devices.

and get which drivers?

:confused:
:blink:

/me re-reads first post.

You're considering going to a SATA (I/II) device, yes?
Windows treats the SATA controller as a SCSI device in Device Manager.

If you don't have the drivers installed for that controller, you'll more than likely get a STOP error on boot into windows when you've imaged the drive if you try to boot from it.

Connect the SATA drive up (when/if you get it).
Install the drivers for the SATA(SCSI) controller to the installation on the PATA drive before cloning it.
Clone it, disconnect the PATA drive and boot cleanly into windows, then update your controller drivers again.

I've done pretty much what you're planning to do.
This is the easy way (and allows you to keep your Windows installation intact with no need for a re-install).

Am I missing something? :mellow:

[cobalt6700]

:blink:

/me re-reads first post.

You're considering going to a SATA (I/II) device, yes?
Windows treats the SATA controller as a SCSI device in Device Manager.

If you don't have the drivers installed for that controller, you'll more than likely get a STOP error on boot into windows when you've imaged the drive if you try to boot from it.

Connect the SATA drive up (when/if you get it).
Install the drivers for the SATA(SCSI) controller to the installation on the PATA drive before cloning it.
Clone it, disconnect the PATA drive and boot cleanly into windows, then update your controller drivers again.

I've done pretty much what you're planning to do.
This is the easy way (and allows you to keep your Windows installation intact with no need for a re-install).

Am I missing something? :mellow:

ahhh haaa! :D

no i get that now. (look im a drummer ok, its not my fault, as the titile suggests)

thanks guys....

friday there coming. YEY!

gaz

[Pug]

Lol! XD
I didn't think it was me.

[fivecheebs]

Pug's way is probably easiest (i didnt know that the windows drivers for SATA would work like that TBH), but i can offer an alternative. Ghost the image and get it onto the new drive. Then reinstall windows over the top of the exisitng install (repair not using the recovery console) and use the F6 drivers with the new install.

[cobalt6700]

ohhhh

can i just plug in the sata drive and it will reconise it? or am i gunn ahave to install drivers before it will see it?

so cheebs....just to make sure ive got it right..

i can install the drivers for the sata drive on the orignial windows, then plug the sata drives in, and then ghost the image across, then turn off, unplug the pata drives, boot using the windows CD, and at the start of the repair press F6 for the thridparty scsi/sata drivers, and then carry on from there?

i dont know why im having problems understanding this,its really pissing me off. :angry:

thanks for the help tho guys :thumb:

.........c'mon harddrives! :D

[fivecheebs]

so cheebs....just to make sure ive got it right..

i can install the drivers for the sata drive on the orignial windows, then plug the sata drives in, and then ghost the image across, then turn off, unplug the pata drives, boot using the windows CD, and at the start of the repair press F6 for the thridparty scsi/sata drivers, and then carry on from there?

Almost. When you boot from the windows CD, before it does any file copying it will ask you to "press F6 to install any third party SCSI controllers". Thats when you do it. If you get to the point where it asks where to insall before you have done the F6 bit you've got too far. You'll need a floppy drive for that bit BTW.

You could integrate the drivers (with nLite or similar) with the windows CD to avoid the need of a floppy.

[Da_Rude_Baboon]

Almost. When you boot from the windows CD, before it does any file copying it will ask you to "press F6 to install any third party SCSI controllers".

btw it doesnt ask for the drivers immediatly after you press F6, so if you press it and nothing appears to have happened, dont worry. ;-)

[cobalt6700]

You'll need a floppy drive for that bit BTW.

You could integrate the drivers (with nLite or similar) with the windows CD to avoid the need of a floppy.

uhhhh.....that means ill have to find a floppy drive. and link it up.

so if im installing the drivers first (just before the repair) do i still need to install drivers in windblows? :huh:

gaz

[fivecheebs]

hehe, probably. You need to get the ghost image on the second drive before you can repair it.

[cobalt6700]

:duh:

as you can tell im not tooo with it today.

ill get there. im meant to be revising again, but im just not getting it. maby all the alchahol and women and ticktac's are getting to me ^_^

[Pug]

Pug's way is probably easiest:nods:

I found it quick & painless. :-)
Did it whilst on the phone to Steve, 17GB PATA to 160GB SATA.
IIRC, I booted with UBCD which had HDClone2 on it (which didn't support SATA) and ran HDClone3 from the source drive (although I may have resorted to a FDD, as I recall searching for a usable diskette).
Done in no time. :magic:

I'm sure I had problems trying cheebs's method with my first SATA drive but it was ages ago when I tried it, so may have involved more factors.

Handy tip to speed things up after any hardware changes like this -

Add a new user environment variable of devmgr_show_nonpresent_devices and set the value to 1;
open device manager and put a tick in Show Hidden Devices;
then delete any greyed out entries.Enjoy a speedy boot.

[Fibbles]

I've installed my SATA drives w/out needing a floppy from drivers. With my i875 Abit IC7 Maxx 3 and all of my NF4 chipsets I just attached the HDD to the mobo, added power and both my BIOS and Windows saw the drives.

It was a different story on my VIA KT890 chipset based Abit AX8 though. The BIOS refused to see the SATA HDD's and while F6 for Windows worked, when Windows would restart to continue the installation, the BIOS would refuse to see the drives, screwing me over. I was able to get the drive installed under Windows by using an IDE drive as the system drive, but they were fried by the SATA controller (I lost a 74gb Raptor and a 300gb Maxtor).

[Greeny]

Intel chipset doesn't need SATA drivers for the ICH SATA controller channels, it supports the drives natively like their PATA drives, hence no need for drivers so the ghosting/cloning process is much simplified.

[Fibbles]

Intel chipset doesn't need SATA drivers for the ICH SATA controller channels, it supports the drives natively like their PATA drives, hence no need for drivers so the ghosting/cloning process is much simplified.

But I know people that have Intel chipsets and have needed drivers. A guy I know was having major SATA issues with his NF3 250gb chipset too :huh:

I was under the impression that it was Windows that didn't have SATA support, regardless of wether or not your BIOS sees the drives.

[Greeny]

Most of the SATA drive controllers on motherboards are implimentations of Silicon Image controllers, Highpoint controllers or other proprietary controllers such as the NForce chipset. All of these need drivers and are tricky or impossible to access easily from Dos enviroment or similar.

More than likely the Intel board in question had a 3rd party controller grafted onto it to handle the SATA drives or was an Nforce chipset board.

[cobalt6700]

Handy tip to speed things up after any hardware changes like this -

Add a new user environment variable of devmgr_show_nonpresent_devices and set the value to 1;
open device manager and put a tick in Show Hidden Devices;
then delete any greyed out entries.Enjoy a speedy boot.

and where the hell do i put that? :huh:

[Greeny]

Go to device manager and simply pick "view>show hidden devices" instead.

[Pug]

Go to device manager and simply pick "view>show hidden devices" instead.
Nuh-uh (that's the next step ;-)).
That just shows hidden devices connected to the machine.
By setting this environment variable, you'll display whatever's previously been connected too. :magic:
Try it.


Gaz - I think you can do it through the Run dialogue by typing -
set devmgr_show_nonpresent_devices=1
(at least I think that's the correct syntax)

I do it by System Properties -> Advanced -> Environment Variables -> New
For the Variable Name, enter the text devmgr_show_nonpresent_devices, for the value, enter 1. :-)

[cobalt6700]

ok ive done it...and its seems to have done bugger all (for the moment)

[Pug]

ok ive done it...and its seems to have done bugger all (for the moment)
Hmm, let me just highlight a section of my original statement...
Handy tip to speed things up after any hardware changes like this - :slap:
:-p

[cobalt6700]

hehehee...

OHH OHH! there coming tomorrow!!!

yey! :D

[cobalt6700]

ok guys
got the new hardrives.

but HDclone says its going to delete all my data off the target drive......:h34r:

[fillip]

But, if your target drive is your new drive, then there shouldn't be any data to delete anyway.

[cobalt6700]

:duh:

:wallbash:

why cant i get it right.

thanks fill! :D

[cobalt6700]

ok...hdclone cant see my SATA drive...ffs :rant:

edit - its all good now...i had to fiiddle with some bios settings

gaz