G
Guest
dear newsgroup,
i am using xp pro sp2 mobo asus a7v333 (raid - but raid function is not
used) parallel ata controllers.
recently i added 160 gb hdd. ntfs formatted with partition magic. hdd is
seen by mobo bios but not seen by windows after booting. when i put this 160
gb in usb 2.0 external enclosure and connected it to my mobo usb 2.0 port -
windows recognised it. when i put it back in again (doesn't matter which
controllers/ata cables) windows would not recognise the drive.
just in case it is drive/cable specific, borrowed my friend 200 gb hdd and
his ata cables - similar results: recognised at bios level but not by windows
when it is inside but recognised when it is connected via external usb 2.0
enclosure.
just in case it is mobo firmware issue - checked with asus site to make sure
mobo firmware is up to date - it is.
i want this drive to be an internal drive. would appreciate advice/help as
to what is going on here and any solution to this.
thank you,
jes
i am using xp pro sp2 mobo asus a7v333 (raid - but raid function is not
used) parallel ata controllers.
recently i added 160 gb hdd. ntfs formatted with partition magic. hdd is
seen by mobo bios but not seen by windows after booting. when i put this 160
gb in usb 2.0 external enclosure and connected it to my mobo usb 2.0 port -
windows recognised it. when i put it back in again (doesn't matter which
controllers/ata cables) windows would not recognise the drive.
just in case it is drive/cable specific, borrowed my friend 200 gb hdd and
his ata cables - similar results: recognised at bios level but not by windows
when it is inside but recognised when it is connected via external usb 2.0
enclosure.
just in case it is mobo firmware issue - checked with asus site to make sure
mobo firmware is up to date - it is.
i want this drive to be an internal drive. would appreciate advice/help as
to what is going on here and any solution to this.
thank you,
jes