hobiecatter

Member
  • Content count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About hobiecatter

  1. Thanks Fernando, you've been a great help. I found that out just now too and read it. It seems that is the problem, but after reading that, I still don't understand why I am getting this and how to prevent it as these are SATA drives on XP, not SCSI But thanks for your help.
  2. well, I turned on my other hard drive (which has Vista installed) and booted into it with both HD's on. Opened up the boot.ini on the drive I just installed XP on and it says: [boot loader] timeout=1 default=signature(ca2d9e57)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] signature(ca2d9e57)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect When I change it to what you gave me: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect it will work. I just don't understand where the other one - signature(ca2d9e57) is coming from when I install.
  3. Thanks for your help, I too didn't think it would be related to nLite, but I'm puzzled. I only have one hard drive turned on, it only has one partition. Every time I've tried it, I did a format. I've tried both Quick and Regular format. It installs fine, but then during the reboot, it goes into a reboot cycle because the boot.ini is wrong. Like I said, I now I can edit the boot.ini and make it correct, but I am trying to test this CD and make sure everything works properly so the next time I install XP, I don't have to go through these hoops. If you are as stumped as I am at this point, I can make my own thread to keep this one on track as I don't want to mess this excellent thread up. thanks!
  4. Ok, I am able to get much further now. I can now use my nLite disc to install XP. However, for some reason it is creating the boot.ini with TWO systems: [boot loader] timeout=1 default=signature(ca2d9e57)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] signature(ca2d9e57)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect which is causing the computer to go through reboot cycles because it thinks there are two operating systems and the first one is invalid, so it just reboots. I know how to fix it (by editing the boot.ini) however, I want to have a good disc. The only thing I've done while creating this disc is: inserted SATA driver under boot unatended, the only thing I changed was I added the Windows Key. Then create, and burn. I have no other hard drives or partitions turned on when doing this. Anyone know why this would make a different boot.ini file?
  5. If you haven chosen the "Unattended Install", you should not hit F6.Have you tried to enable all possible AHCI Controllers while integrating the Intel textmode drivers with nLite? I understand you do not hit F6 while using a slipsreamed disc because the drivers load automatically. I don't think I wrote it clearly the first time. When I could not get it to work using the slipsreamed, I backed up and used a NON slipsreamed disc and installed a floppy to load the drivers off the floppy to see if that would work. Doing it this way, of course, I DO hit F6 to install the drivers, however, I was still getting the "cannot copy Unknown.sys" error. As for the drivers I picked off of the floppy, there were only four of them available. Two had a (mobile) in the name, so I skipped them and I tried the other two. One of them did not work at all. I tried again with the last one, and was able to recognize the drive, copy the files, then it got to the unkown.sys that it couldn't copy. I have searched all over the Dell forums, and others have had to slipsream the drivers or use a floppy, but none have had this .sys file that could not copy. I am not giving up though. Going to keep trying different things and will let you know what works.
  6. Fernando, Thanks for your help. Since I was getting the Unknown.sys cannot copy during install, I found a floppy drive and thought I'd try it the "old fashioned" way to see if that would even work, instead of slipstreaming the file. I get the same error "cannont copy Unknown.sys" even when using the floppy method. When doing the floppy method, you don't have any options of textmode or INF drivers. I have a Dell XPS 410, so I went to Dell's support page, downloaded the SATA exe driver for my computer, extracted it to the floppy. When I hit F6, and loaded the floppy, there were only four options, two were for mobile, the other two only one of which worked, and it was the one for my controller. I still got the same error with this method. Switching over to regular IDE (not needing to load the SATA drivers) installs fine. So, this is definately something to do with these drivers, just can't figure out what. I need to install in AHCI mode not regular IDE though because my other HD that has Vista only works in AHCI mode, and I will eventually be dual booting.
  7. Excellent write up. I did this slipsream the other day, but just now came across this post. I am running one drive, but trying to run AHCI mode and install XP Pro. Before slipstreaming, It would not detect the drive of course. I slipstreamed the drives exactly how you have in your guide, the only difference is the source cd was not a clean one, but a disc I slipstreamed SP2 in a few months ago. Does this matter that it was an nlite created disc even though the only thing changed was slipstreamed SP2 in? OK, so here is my problem. The slipstream must have worked, becuase it recognized the drive during setup, I created and formatted a partition, and sucessfully copied all of the XP setup files to the BRAND NEW hard drive. Just before the reboot, it says cannot copy file Uknown.sys and lets me canel or skip. Next, it reboots your computer to finish the install. It reboots, but after the POST screen, it reboots again and continues this reboot cycle. Any ideas? This computer was working fine with exact same configuration before I RMA'ed the drive, so I know it's not the bios or connectors or anything. From reading around, it looks to me that it loads the controller driver during the initial start, allowing my SATA drive to work, but then it will not copy the driver to the hard drive, not allowing it to boot. I don't know what Unkown.sys is, but others have the same problem, only named different things .sys I loaded used the drive as a slave an loaded up with my Vista drive and copied over the files iastor.inf iaahci.inf and iastor.sys over to the new hd that has the preinstall files copied on it into the i386 folder. No dice. Still does the same thing. Any one can help?