Quote:
|
Originally Posted by XFS03
Quote:
|
Originally Posted by nffc
That is the right model. Any differences internally would have been production-line / BoM differences but the spec should be equivalent.
UDMA mode 2 is evidently the maximum that combination, in that state, can support. AFAIK, there's no way of changing it in XP.
Recover the PC - yeah... using the disks supplied (with a Ghost image) not an XP disk. With an emachines it probably won't make much difference.
|
I still find it strange that it is not listed under the eTower range, as it is clearly labelled (once on the front & twice on the back) as an eTower 310. Naturally, when I wanted to find out more about it on the internet, this is what I searched for, & when it came up with no hits, I was a bit suprised!
Perhaps I have a unique machine sitting in front of me. Perhaps it's a "one-off"  . Having said that, my sister did tell me that it was a display model they bought, as they didn't have any others in stock.
It also seems strange to use a chipset with UDMA4 capabilities, but limit it to UDMA2. Having said that, I wonder how much difference in transfer speed this will actually make in practice. I just wanted to get the most out of it before she passes it on. I have doubled the memory from 128M to 256M & it's amazing how much difference that has made.
I should have realised what you meant by "recover", as I have got the recovery disc here, but it is Windows ME based, so I won't be using it. |
Fair point - but if you restore with the ME / Ghost image, and it's working in UDMA4, you know it's driver-related - which is tbh my main suspicion.
It is pretty much nailed the 310 - I have no tools to check the s/n on an Emachines but there is no difference between an "etower 310" and a 310 - they're labelled differently in US/UK anyway so it will be DSG labelling not the emachines.
As far as the info on the PCSC site states (which is the same as we get!) it's an Intel 810 chipset for which drivers can be found
here - unfortunately, there is no information on what behaviour the specific HW combination exhibits in XP, as it's a bundled ME machine. The chipset driver is a generic driver for all OS and for all MBs on that set, so it should work.
You could re-set the Bios defaults but I don't think it's Bios-level or hardware related.
Alternatively strip the three IDE controllers as well as the HD's drivers and optical drive in Device Manager, reboot and let it re-detect, see what that does?