Ah, so it's just the wrong SDK i got then?
I stupidly made the incorrect assumption that as it came up as 'Android 1.0' rather than 'Android 1.5' that I'd need the v1.0 SDK. I realise now that this was particularly daft - why make it so obvious?
So it's just a case of when the 'Android 1.0' device turns up and Windows asks you for drivers, point it to the relevant folder in the SDK, and go from there?
Wish I'd brought my laptop to work now - I could have tried this.