1 GB WD Caviar Green 3.0 Gbps detecting as 33mb in Bios

[Twistd_frk]

I recently bought a WD Green Caviar 1 TB http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=5324&p_created=&p_cats=185&p_cv=1.185&p_pv=2.294&p_prods=227%2C294 After plugging in the HDD it's detecting as 33MB in my BIOS

I'm a beginner at best

System Config
Core 2 Duo: E4400
Gigabyte GA-945GZM-S2 Motherboardhttp://www.gigabyte.com/products/product-page.aspx?pid=2603#ov
Windows 7 Ultimate 32 Bit

Actions Taken
1) Have Read http://forum.hddguru.com/lost-partition-hitachi-1gb-hdt721010sla360-t15662.html?hilit=33mb#p104304
However I didn't understand how to use HxD
2) Have Tried HDD Capacity Restore , Doesn't work Error Message :" Hard Drive is not accessible or damaged in some way, Therefore capacity can't be recovered. Please try and run this program from another platform"
3) I'm logged in as Administrator
4) As per the Gigabyte Website I have the latest BIOS(Is there any way to confirm it, Because I did download the latest bios and install it, just want to be certain)

[N.C.]

Try to check the drive with MHDD (Boot CD version) and post here the result.

Maybe someone can help.

Janos

[fzabkar]

Try HDAT2:
http://www.hdat2.com/download.html

See Q1 in the FAQ:
http://www.hdat2.com/hdat2_faq.html

[Twistd_frk]

I have no idea how this happened. I got back from work to try the solutions provided by both of you, and I realized that I had disconnected my dvd drive's power supply while plugging in the new hard drive because of a bad sata power adapter, so I reconnected it and shuffled around the power cables to be able to burn a boot-able disc for HDAT and was checking the connections in BIOS and my HDD shows 1000GB now.

So it's working now.. and I didn't do a damn thing yet

Would be great if anyone can shed some light as how it worked on it's own

But an any case, thanks for the quick response appreciate it.

[fzabkar]

I suppose it had something to do with a change in boot order, or a general change in the order of your storage devices. Regardless, it's still a BIOS quirk.