[watchingdt]

im not sure u get it, it boots fine, asks me to press any key, then says loading blabla(no blue screen yet) then all i see is a black screen with nothing written on it for ever...
also, im on a laptop(compal fl90) and yes all ym hardware is fine.
im gonna try the solution with just text mode drivers, and its obviously something with the cd since it didnt work at all, then i switched the way the iso was recorded and now it loads in windows, now lets see if with textmode only it loads in dos.

[Fernando 1]

watchingdt, on May 5 2008, 05:48 PM, said:

im not sure u get it, it boots fine, asks me to press any key, then says loading blabla(no blue screen yet) then all i see is a black screen with nothing written on it for ever...

If you don't even come to the point where your hdd is detected (or not), you obviously have a problem with your nLited CD.
You can verify it, if you try to boot off the original XP CD.

[JuggaloNick27]

Hi, I am having problems with this exact thing. I have an HP PAvillion a6077c TV PC andI have been trying this over and over and when it pulls up the destination to install XP it shows two drives (C and D), but it says they are both 130gb when really they are 190 and 170....last time I tried installing on the D I had to use recovery discs to bring my computer back up. Any advice?

This post has been edited by JuggaloNick27: 08 May 2008 - 08:00 PM

[Fernando 1]

JuggaloNick27, on May 9 2008, 02:48 AM, said:

Hi, I am having problems with this exact thing. I have an HP PAvillion a6077c TV PC andI have been trying this over and over and when it pulls up the destination to install XP it shows two drives (C and D), but it says they are both 130gb when really they are 190 and 170....last time I tried installing on the D I had to use recovery discs to bring my computer back up. Any advice?

Maybe the XP Setup just "sees" 130 GB, but will be able to use the whole space.
It should not be a problem to get XP installed onto your computer. Look here.

[JuggaloNick27]

I have tried installing onto the shown drives that are 130 and all it does is mess everything up. I have to use recovery discs to get back to where I am. As far as the site you gave me...I found that before I ever came to this site. I am stuck and I am not sure why. It seems others with my system have done it, but I just cant seem to get it.

[Fernando 1]

JuggaloNick27, on May 9 2008, 09:43 PM, said:

I have tried installing onto the shown drives that are 130 and all it does is mess everything up. I have to use recovery discs to get back to where I am. As far as the site you gave me...I found that before I ever came to this site. I am stuck and I am not sure why. It seems others with my system have done it, but I just cant seem to get it.

Everyone with a suitable Intel S-ATA Controller is able to get XP installed. You must have done something wrong.
If you don't want to have any stress, you should just go into the BIOS and set the S-ATA Controllers, where yor hdd is connected, to "IDE mode".
Then you will be able to get XP installed without loading/integrating any separate textmode drivers.

If you want to continue to get XP installed by using the AHCI features of your on-board S-ATA Controllers, you should try it again from scratch: Backup your datas and format your hdd with NTFS system.
Furthermore you should give some more informations about your hardware, for example the number and sorts of hdd's.

[StuartLiu]

Hello. I'm using Asus P4B-M motherboard with initio (INIC-162x SATA) controllers.
I integrated XP sp3, original SP2, Text mode drivers using nLite version 1.4.5

Everything looked fined. I can enter the windows installation, I can detect my SATA drive, and the installation process had already copied files to my disk, and ask me to reboot.

The strange things happened here: After reboot, windows screen appeared (with that status bar), but after about 10 seconds, blue screen appeared and showed error code 0x0000007b. I search the net and find that this error may be due to wrong SATA drivers. My question is how this could happened since my computer already recognized the drive? or should I include both PNP and TXT mode driver?

Many thanks!

[Fernando 1]

StuartLiu, on May 13 2008, 11:30 AM, said:

Hello. I'm using Asus P4B-M motherboard with initio (INIC-162x SATA) controllers.

If your S-ATA drives are connected to these controllers, you have to integrate the INIC-162x S-ATA drivers.

Quote

I integrated XP sp3, original SP2, Text mode drivers using nLite version 1.4.5

You certainly mean, that you have integrated SP3 into an XP SP2 CD, don't you? It wouldn't make any sense to integrate SP2 and SP3.

Quote

The strange things happened here: After reboot, windows screen appeared (with that status bar), but after about 10 seconds, blue screen appeared and showed error code 0x0000007b. I search the net and find that this error may be due to wrong SATA drivers. My question is how this could happened since my computer already recognized the drive? or should I include both PNP and TXT mode driver?

No, you only should integrate the correct S-ATA drivers (from the Controller manufacturer, where your hdd's are connected) as TEXTMODE drivers.

[zowel]

Hi

I didn't see this guide and just ran through the process myself. It seems to be working okay, but now I have a question:

From the guide, Part (2) : Step (4)

Quote

When you come up to the task "Drivers", hit the "Insert" button, use the "Single driver" option and point to the content of the driver package you have downloaded and extracted at first step. Click onto one of the shown INF files (it doesn't matter which one).

Judging by the fact that it says it doesn't matter which INF file is clicked on when via the "Single driver" option, I'm guessing it also doesn't matter if one clicked on "Mulitiple driver folder" option instead rather than "single dirver"?

After I had extracted the drivers and found there were two INF files, I guessed that the folder option was more appropriate. On the next screen, just selected the two relevant controllers from the list of 10 or so.

Seems to have worked, so is the proper way to select "single" next time?

[Chrysalis]

Nice guide even tho its an old post I will raise some points.

Intel controller in raid mode does not need a raid array and intel actually reccomend this for single drive configs as well as raid since its the same as ahci except it will support future raid use without an OS reinstall.

I added my intel drivers on my new sp3 cd and I notice nlite is telling me I should disable the use of OEM Preinstall $OEM$ folder which I have always been using fine in the past and I dont remember nlite having this warning before, is there a known real problem by integrating text drivers at the same time as using OEM preinstall? --edit-- I misunderstood it says not to use it when using f6 method, I wonder if thats the problem the other poster had then.

This post has been edited by Chrysalis: 18 May 2008 - 02:24 PM

[Fernando 1]

zowel, on May 13 2008, 06:46 PM, said:

From the guide, Part (2) : Step (4)

Quote

When you come up to the task "Drivers", hit the "Insert" button, use the "Single driver" option and point to the content of the driver package you have downloaded and extracted at first step. Click onto one of the shown INF files (it doesn't matter which one).

Judging by the fact that it says it doesn't matter which INF file is clicked on when via the "Single driver" option, I'm guessing it also doesn't matter if one clicked on "Mulitiple driver folder" option instead rather than "single dirver"?

You can use the "Multiple driver" button as well, but you have to pay more attention as with the "Single driver" option (to prevent, that you get more drivers integrated than you want).

Quote

After I had extracted the drivers and found there were two INF files, I guessed that the folder option was more appropriate. On the next screen, just selected the two relevant controllers from the list of 10 or so.
Seems to have worked, so is the proper way to select "single" next time?

Yes.

Chrysalis, on May 18 2008, 09:21 PM, said:

Intel controller in raid mode does not need a raid array and intel actually reccomend this for single drive configs as well as raid since its the same as ahci except it will support future raid use without an OS reinstall.

Thanks for this additional information.

Quote

I added my intel drivers on my new sp3 cd and I notice nlite is telling me I should disable the use of OEM Preinstall $OEM$ folder which I have always been using fine in the past and I dont remember nlite having this warning before, is there a known real problem by integrating text drivers at the same time as using OEM preinstall? --edit-- I misunderstood it says not to use it when using f6 method, I wonder if thats the problem the other poster had then.

There is no problem at all, if you have integrated the textmode drivers.
You are right regarding the F6/floppy driver loading option. OEM Preinstall should be disabled in this case.

[Chrysalis]

not tested it yet on the pc that has the intel controller only in virtual pc to make sure the cd actually works, the first time I downloaded your 64bit drivers ooops and I got a corrupt sys error on the driver, but now with 32bit that error is gone. I should be testing on this pc (different drive but on intel controller) before end of the week hopefully. Thanks for having the drivers as it would have been a pain to extract from intels floppy iso.

[steveboy]

Howdy, new member here. I think it's amazing the effort people here go to to help others with problems -- I hope I'm as useful in my own areas of expertise.

Unfortunately, installing an OS isn't one of them. I've read this entire thread looking for info that will fix my install problem, but haven't been able to find it.

I just bought a used Acer Aspire 9800 laptop running Vista Ultimate. I need XP Pro for its reliability using high-end music apps, so I used Nlite to put together a slipstream disc incorporating the drivers from the Acer driver disk as well. I have been able to get the install to read the hard drives, format, and begin installation, but no matter what I do, the install hangs at the first reboot -- not even a BSOD, just black screen.

I made sure I used the Intel 8280GHM controller drivers the mobo uses. I have no options in BIOS regarding SATA drives (disabling AHCI, for instance); the Phoenix BIOS is very rudimentary and doesn't allow much user flexibility (can someone explain why I can buy a desktop and be allowed to tinker with it as if it is truly mine, but laptops are sold as if they really still belong to the manufacturer).

Because the install hangs at the same point every time, I suspect that there is a key driver missing, or an element in the drive recognition process I'm overlooking, but I can't figure out what it might be. I'm operating at about the edge of my knowledge and ability here. I'm getting desperate because I just found out the Vista image disks I made aren't bootable (if they require a working Vista to restore my Vista, I'm not sure what use they are), and the OEM Vista install disk that came with the laptop is a nonbootable upgrade. So now I don't have much choice about XP if I want this thing to be anything but a very large doorstop.

Any help is enormously appreciated, and many thanks in advance!

--steve

[Fernando 1]

steveboy, on May 27 2008, 08:43 AM, said:

I just bought a used Acer Aspire 9800 laptop running Vista Ultimate. I need XP Pro for its reliability using high-end music apps, so I used Nlite to put together a slipstream disc incorporating the drivers from the Acer driver disk as well. I have been able to get the install to read the hard drives, format, and begin installation, but no matter what I do, the install hangs at the first reboot -- not even a BSOD, just black screen.

Hi Steve,
since your hdd has been detected by Windows XP Setup, you obviously had integrated the correct Intel S-ATA AHCI Controller driver. I think, that your issue was caused by another driver you had integrated.
My recommendation:
Create a new nLited XP CD with just the integrated Intel S-ATA drivers. Don't add any other driver.
If the installation should fail, try to additionally integrate the Intel INF (=chipset) drivers as PnP drivers.
Once Windows XP is up, you can install the other needed drivers for your system.

Good luck!
Fernando

[steveboy]

I'll do just that and let you know -- thank you again!

--steve

[steveboy]

I tried an install with just the Intel SATA driver. Got a BSOD on the first reboot, but after that it went to the exactly the same pattern as before: boot XP, "startup is restarting your computer," black screen.

I downloaded the Intel PNP files from your link in your terrific tutorial, but when I tried to open it I get the message "This computer does not meet the minimum requirements for installation of the software." I will try on another computer and see if I can just copy over th extracted files.

[steveboy]

I figured it out in a totally inexplicable way, but maybe the knowledge will benefit others with the same problem. My laptop has 2 2GB RAM sticks. Something about the way it was hanging on boot reminded me of previous RAM issues I've had on other PCs. I had a feeling the install wasn't recognizing the RAM, or was conflicting with it somehow. So on a hunch I yanked the RAM and reinstalled a 1 GB stick. Bingo: the install completed!

I'm installing mfgr drivers now and will see if I can reinstall the 4GB RAM after XP is in and updated. Meantime, though, maybe this will help someone else. Thank you for your help, Fernando!

--steve

[Fernando 1]

steveboy, on May 27 2008, 08:03 PM, said:

I figured it out in a totally inexplicable way, but maybe the knowledge will benefit others with the same problem. My laptop has 2 2GB RAM sticks. Something about the way it was hanging on boot reminded me of previous RAM issues I've had on other PCs. I had a feeling the install wasn't recognizing the RAM, or was conflicting with it somehow. So on a hunch I yanked the RAM and reinstalled a 1 GB stick. Bingo: the install completed!

I'm installing mfgr drivers now and will see if I can reinstall the 4GB RAM after XP is in and updated. Meantime, though, maybe this will help someone else. Thank you for your help, Fernando!

This is a known issue of any 32bit Windows OS, if you try to install it with 4GB of RAM.

[Haruspex]

Hi Fernando 1, can you update the intel raid/ahci drivers if you have the time?

In case you didn't know Intel recently update them to version 8.2.0.1001

[Fernando 1]

Haruspex, on Jun 3 2008, 01:25 PM, said:

Hi Fernando 1, can you update the intel raid/ahci drivers if you have the time?
In case you didn't know Intel recently update them to version 8.2.0.1001

Thanks for your suggestion. I have already recognized the new Intel textmode drivers, but since I am not at home for a while, the users of my guide have to wait some days.
I will update the linked drivers next week, when I am at home again.

CU
Fernando