TSGL: Slave drive not seen--solution

[Ron Grant]

Kind of like buying lumber,  A 2 X 4 is only 1 1/2 X 3 1/2.



Don Penlington wrote:
> The problem is solved.
>
> This dummy was seeing the slave drive all the time.
>
> What I was seeing in My Computer was C-Drive at 12 Gb and D-Drive at 145 
> Gb. This is what I thought I'd partitioned the new 160 Gb into--allowing 
> for a missing 3 Gb which you never see on the Hard Drive for the low-level 
> stuff .
>
> I therefore assumed that these were the 2 new partitions on the new 160Gb 
> drive.  Wrong.
>
> What I was actually seeing was the old (slave) drive (12Gb) plus the ENTIRE 
> new drive (145Gb). The coincidence of the new-size partition being the same 
> size as the old drive fooled me, coupled with the fact that there is 15Gb 
> missing on the new drive. As I'd installed XP on the C-Drive, in fact it 
> had installed on the slave drive (I didn't think this was allowed?) so the 
> original data got wiped in the process. Luckily it was of no great importance.
>
> The new drive is a Seagate Barracuda.
>
> It's not a restore disk, or anything of that sort--just a new unformatted 
> hard drive.
>
> When I started all over again after physically removing the old drive, 
> there was definitely only 145Gb of allowable space to partition. No 
> proprietary junk that's visible.
>
> Sheesh. 15Gb you don't get out of a nominal 160Gb. That's about 5 times the 
> size of XP.  I know there's all the SMART stuff etc, but surely that's not 
> that big. What on earth is taking up that much space?  Are we being 
> conned?  Is this normal? Or am I missing something?
>
> Don Penlington
>
>  From the Beach at Surfers Paradise in sunny Queensland.
> Computer tutorials, local scenery,  and other things at my website:
> http://users.tpg.com.au/deepend/index1.html
>
>
>