MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically.
Search the Community
Showing results for tags 'solid state'.
Found 1 result
Small SSDs are so cheap I thought one would be an interesting upgrade on my 'daily driver xp sp3 Dell 530s. Not so ... The machine is SATA so this should be plug/play ... right? Nope ... BIOS (up to date) detects the drive correctly. FDISK finds three partitions 1 & 3 are small, non-DOS. 2 is most of the drive, DOS. Reallocate to one primary DOS partition, FAT-32. (Like my real HDD for this machine.) Formats fine. Start to load XP from CD, it goes through the loading of files, etc. then crashes as soon as it touches the disk. "SESSION3" and a lot more stuff. The long code begins 0X20006F and the rest is 0X000000. The error message can be found with a web search but basically tells you what the text on the screen says "Something is wrong with your hardware. Take out any device you just installed and try again." Self explanatory but taking out my new drive isn't actually a solution to the problem of installing a new drive. More data to further confuse the picture. 1. I installed XP successfully using a Dell Dimension 2400. It runs FINE on that machine. I installed it on a total of five SSDs: Three were 2Gb ones -- too small for any more than a demo, but useful for that, I thought. The FIRST one of those actually came up fine on the 530s -- but I have mislaid that one. (Dummy ...) I also installed it on a couple of 16 Gb ssd's with the same (failure) result. All but one of the 16's were APACER, the odd one was SANYO, I believe. 2. For the fun of it I tried booting up one of the 2 Gb drives without doing anything to it: It came up, displayed an XP black screen, then went to a Windows Embedded logo, and finally to a hospital logon screen, which -- since I have no password -- was the end of the line. And probably wouldn't have gone anywhere interesting anyhow since it knew nothing of my keyboard or mouse. But what this says is that there's nothing inherently wrong with either the drives OR the Dell 530s. I have looked pretty broadly for more ideas, others who might have had this problem, etc., but no luck. Since the XP install causes an upchuck on the 530s I can do nothing more there. I can try to install the Dell 530 drivers on the SSD system running on the 2400: Often you can get away with that and at least the chipset and IDE ones might make a difference. Anyone got any more ideas? I've gotten more good advice on MSFN than all the rest together, so I thought it worth trying ... THANKS!