nLite for dual usage: IDE or Sata installation

[skybox]

Hello

I wonder if after "nLited" the new XP cd with Sata driver, would it be possible to use this new XP cd to install XP into IDE harddisk at another time? It's like dual usage installer that I can use to install XP to IDE or Sata harddisk.

Thank you.

[Guest]

Yes

[jaclaz]

Yes

To expand on it :

http://homepages.tesco.net/J.deBoynePollard/FGA/questions-with-yes-or-no-answers.html

The theory is simple.

A "normal" XP install CD has a "database" of drivers.

During install, the setup detects hardware and tries to find in this "database" the "right" driver.

So, when you add a driver to an XP CD, all you do is to add an entry in this "database", the resulting CD will work EXACTLY as before BUT will be able to install ALSO the particular driver you added.

Check also the BTS driverpacks:

http://driverpacks.net/

jaclaz

[skybox]

Hello

I have successfully created the ISO with the ICH8 Sata driver.

I tested the ISO in VirtualBox and ran into problem:

When use the default Storage option in VB to set the IDE Primary Master and IDE Secondary Master, the ISO is able to run until the point when it was about to let user select parition and format. It BSOD with acpi.sys error message. (see attachment)

However, when Sata Controller is added to the Storage, it can move beyond that point.

I am running VB on a P3 PC and I know the original CD would work with the default Storage option selected.

Please point out to me where I went wrong.

Thank you.

[johnhc]

Hello

I have successfully created the ISO with the ICH8 Sata driver.

I tested the ISO in VirtualBox and ran into problem:

When use the default Storage option in VB to set the IDE Primary Master and IDE Secondary Master, the ISO is able to run until the point when it was about to let user select parition and format. It BSOD with acpi.sys error message. (see attachment)

However, when Sata Controller is added to the Storage, it can move beyond that point.

I am running VB on a P3 PC and I know the original CD would work with the default Storage option selected.

Please point out to me where I went wrong.

Thank you.

skybox, without your Last Session.ini, as requested in BOLD RED letters above, we have little chance of guessing. IF VB is anything like VMware Player (that I use) it does not use your drivers but has its own set of virtual drivers. Enjoy, John.

[skybox]

skybox, without your Last Session.ini, as requested in BOLD RED letters above, we have little chance of guessing. IF VB is anything like VMware Player (that I use) it does not use your drivers but has its own set of virtual drivers. Enjoy, John.

Hello

I am sorry as I thought the error screen capture would be enough. The ini file is now attached.

Thank you once more.

Last Session.ini

[Sp0iLedBrAt]

skybox, why don't you give a try to Fernando1's modded Intel drivers? They are are the same thing, with a few lines erased (for booting from floppy) to increase success rates.

Cheers

[johnhc]

Hello

I am sorry as I thought the error screen capture would be enough. The ini file is now attached.

Thank you once more.

skybox, thanks for the Last Session. Yours is very simple and I see nothing that could cause your BSOD. I do agree with Sp0iLedBrAt that you should try Fernando 1's driver. He is the driver expert here. Using all those various versions of the driver is asking for trouble. If all the driver files (xxx.sys) have the same name, then only the last one is used. If it is not the corrected one then your install (on HW) will not work. These driver issues are not your VB problem, however, since VB will use it own virtual drivers. Did you run nLite more than once against the same source? You should always start with a fresh copy of your CD files/folder and run nLite only once doing all your work. I am curious why you did not integrate SP3? Where did your source come from and what type is it - OEM, Retail, Recovery or ...? You might try removing all your drivers (starting with a fresh source copy) and installing on VB. Please let us know what your learn. Enjoy, John.

[skybox]

skybox, thanks for the Last Session. Yours is very simple and I see nothing that could cause your BSOD. I do agree with Sp0iLedBrAt that you should try Fernando 1's driver. He is the driver expert here. Using all those various versions of the driver is asking for trouble. If all the driver files (xxx.sys) have the same name, then only the last one is used. If it is not the corrected one then your install (on HW) will not work. These driver issues are not your VB problem, however, since VB will use it own virtual drivers. Did you run nLite more than once against the same source? You should always start with a fresh copy of your CD files/folder and run nLite only once doing all your work. I am curious why you did not integrate SP3? Where did your source come from and what type is it - OEM, Retail, Recovery or ...? You might try removing all your drivers (starting with a fresh source copy) and installing on VB. Please let us know what your learn. Enjoy, John.

Hello

"The drivers you're using are the culprits" look for this line here: http://forums.virtualbox.org/viewtopic.php?f=2&t=29628&p=133692&hilit=ich8#p133692

that was the pointer 'cos things worked when I tried Intel Storage Manager 7.8 driver.

Back to nlite

modded 32-bit ICH6-10 ver 9.6.0.1014: VB-IDE, VB-Sata, VMPlayer -> BSOD

modded 32-bit 8.9.6.1002: VB-IDE, VB-Sata, VMPlayer -> OK

So, driver from certain version won't work.

The next thing to do is to install the nlited cd to the real physical ICH8 system.

Lastly, thank you to all who gave pointers.

Edited October 22, 2010 by skybox

[cdob]

Try Intel (RST) 10.0.0.1046 WHQL too.

[skybox]

Try Intel (RST) 10.0.0.1046 WHQL too.

Tested using 1 driver from the mentioned package and did not BSOD.

I downloaded the package from station-driver.com 'cos unable to find it at Intel.

Regards.

[cdob]

did not BSOD.

At VMware and different real hardware:

iastor.sys 9.x BSOD ocassionally at IDE mode.

iastor.sys 8.x and 10.x does work fine.

Overall:

Avoid iastor.sys 9.x at dual usage XP installations.

Use iastor.sys 8.x or 10.x