[dsf3g]

I was having lots of difficulties with this install, maybe my experience will help others.

First off, I was using a very old XP disc, a pre-SP1 and trying to install using a Sony external USB DVD/RW drive. I kept getting blue-screened just a few minutes into the installation. I had tried using Nlite to slipstream XP2 and see if that worked any better, but the resulting disk showed me no love.

First thing I tried differently was turning off Run Protection and Fast Boot in the BIOS, just to eliminate factors that might be getting in my way.

Another guy on this forum also managed to install on his Mini 9 using a similarly old XP distribution by doing a manual slipstream following these instructions: http://redirectingat.com/?id=258X408...slipstream.asp.

I followed the instructions up to the point of slipstreaming the SP, then used nLite to create an .iso of the windows installation and used Nero to burn it to a CD-ROM.

IT WORKED!!!!! This CD booted and installed Windows SP2 on my Mini 9.

But... not so fast! When XP rebooted to finish the installation, it started reporting that it couldn't find files. The first missing file was: asms.

I ran a search and according to Microsoft, this happens when XP cannot communicate with your CD ROM reader. Now the Microsoft page recommends launching a command session and making some changes to the registry. That did not work, however, as I don't think regedit had even installed at this point. I did notice something curious: when I tried exploring my DVD Rom drive from the command line, I was able to!!! So the Mini 9 could see the DVD ROM drive and navigate to it, but XP could not yet! Wierd.

So I closed the command line and looked at the error message again, and that's when I noticed something odd: XP was trying to find the file using the directory path: CDRomO/i386. What would happen, I wondered, if I changed "CDRom0" to "d:"?

IT WORKED!!!

But there was one problem: now XP was prompting me for another missing file using the same odd path name?

"Oh, God," I thought... "I'm going to have to do this 1000 times aren't I?" Still, determined to finally get XP on my mini-9 I decided to see how long I could last doing this over, and over, and over....

Luckily, it didn't ask me to do this 1000 times. I'd say I had to do it, at most, some 10 or 15 times.

Hurrah! Success!

I then used the included Drivers CD to install the necessary drivers, and so far everthing seems to be going well. Next I'll install SP3 and my apps and be done with it... well.... at least until I decide to upgrade my stock 8GB SSD with a larger Runcore model.

[bbli2000]

Thanks. Exactly what I needed.

THANK YOU!!!!!!!

Originally Posted by dsf3g

I was having lots of difficulties with this install, maybe my experience will help others.

First off, I was using a very old XP disc, a pre-SP1 and trying to install using a Sony external USB DVD/RW drive. I kept getting blue-screened just a few minutes into the installation. I had tried using Nlite to slipstream XP2 and see if that worked any better, but the resulting disk showed me no love.

First thing I tried differently was turning off Run Protection and Fast Boot in the BIOS, just to eliminate factors that might be getting in my way.

Another guy on this forum also managed to install on his Mini 9 using a similarly old XP distribution by doing a manual slipstream following these instructions: http://redirectingat.com/?id=258X408...slipstream.asp.

I followed the instructions up to the point of slipstreaming the SP, then used nLite to create an .iso of the windows installation and used Nero to burn it to a CD-ROM.

IT WORKED!!!!! This CD booted and installed Windows SP2 on my Mini 9.

But... not so fast! When XP rebooted to finish the installation, it started reporting that it couldn't find files. The first missing file was: asms.

I ran a search and according to Microsoft, this happens when XP cannot communicate with your CD ROM reader. Now the Microsoft page recommends launching a command session and making some changes to the registry. That did not work, however, as I don't think regedit had even installed at this point. I did notice something curious: when I tried exploring my DVD Rom drive from the command line, I was able to!!! So the Mini 9 could see the DVD ROM drive and navigate to it, but XP could not yet! Wierd.

So I closed the command line and looked at the error message again, and that's when I noticed something odd: XP was trying to find the file using the directory path: CDRomO/i386. What would happen, I wondered, if I changed "CDRom0" to "d:"?

IT WORKED!!!

But there was one problem: now XP was prompting me for another missing file using the same odd path name?

"Oh, God, I thought... I'm going to have to do this 1000 times aren't I?" Still, determined to finally get XP on my mini-9 I decided to see how long I could last doing this over, and over, and over....

Luckily, it didn't ask me to do this 1000 times. I'd say I had to do it, at most, some 10 or 15 times.

Hurrah! Success!

I then used the included Drivers CD to install the necessary drivers, and so far everthing seems to be going well. Next I'll install SP3 and my apps and be done with it... well.... at least until I decide to upgrade my stock 8GB SSD with a larger Runcore model.

[dsf3g]

Glad I could be of help. I figured I couldn't be the only one having these issues.

[t525]

this is exactly what i had to do to keep it going and finally install windows xp pro onto my vostro a90.

[BuGz]

Originally Posted by dsf3g

I was having lots of difficulties with this install, maybe my experience will help others.

First off, I was using a very old XP disc, a pre-SP1 and trying to install using a Sony external USB DVD/RW drive. I kept getting blue-screened just a few minutes into the installation. I had tried using Nlite to slipstream XP2 and see if that worked any better, but the resulting disk showed me no love.

First thing I tried differently was turning off Run Protection and Fast Boot in the BIOS, just to eliminate factors that might be getting in my way.

Another guy on this forum also managed to install on his Mini 9 using a similarly old XP distribution by doing a manual slipstream following these instructions: http://redirectingat.com/?id=258X408...slipstream.asp.

I followed the instructions up to the point of slipstreaming the SP, then used nLite to create an .iso of the windows installation and used Nero to burn it to a CD-ROM.

IT WORKED!!!!! This CD booted and installed Windows SP2 on my Mini 9.

But... not so fast! When XP rebooted to finish the installation, it started reporting that it couldn't find files. The first missing file was: asms.

I ran a search and according to Microsoft, this happens when XP cannot communicate with your CD ROM reader. Now the Microsoft page recommends launching a command session and making some changes to the registry. That did not work, however, as I don't think regedit had even installed at this point. I did notice something curious: when I tried exploring my DVD Rom drive from the command line, I was able to!!! So the Mini 9 could see the DVD ROM drive and navigate to it, but XP could not yet! Wierd.

So I closed the command line and looked at the error message again, and that's when I noticed something odd: XP was trying to find the file using the directory path: CDRomO/i386. What would happen, I wondered, if I changed "CDRom0" to "d:"?

IT WORKED!!!

But there was one problem: now XP was prompting me for another missing file using the same odd path name?

"Oh, God," I thought... "I'm going to have to do this 1000 times aren't I?" Still, determined to finally get XP on my mini-9 I decided to see how long I could last doing this over, and over, and over....

Luckily, it didn't ask me to do this 1000 times. I'd say I had to do it, at most, some 10 or 15 times.

Hurrah! Success!

I then used the included Drivers CD to install the necessary drivers, and so far everthing seems to be going well. Next I'll install SP3 and my apps and be done with it... well.... at least until I decide to upgrade my stock 8GB SSD with a larger Runcore model.

Thanx heaps mate , i to had the same prob till now (grin) silly the about cd path names tho as i had to show the path d:\i386 instead of a str8 d:\ , but all is well now so cheers 4 da info