ponghy

First, thanks very much for your answer. However, I've read your thread, but I don't find the solution to my problem. My problem is I've the driver files in separate directories, not in I386 like you, and Setup don't find the driver files when needed (in text-setup mode). You said You have to change the source path in DOSNET.INF and TXTSETUP.SIF. And I asked you How?. I've tried several methods, including the [OptionalSrcDirs] section, but no go... Any clue?

an3k, please help. I cannot finish my XP SP3 CD. Thanks in advance.

Bump

an3k: Please, help me TIA.

-- Sorry, deleted. My mistake. Regards.

How?

Hi: I don't know how to use a specific directory for my integrated drivers rather than the I386 standard from the installation source. I've integrated the vmscsi disk driver as a test by adding the following lines: Step 1: Editing DOSNET.INF [Files] d1,vmscsi.sys Step 2: Editing TXTSETUP.SIF [SourceDisksFiles] vmscsi.sys = 1,,,,,,3_,4,1 [HardwareIdsDatabase] PCI\VEN_104B&DEV_1040 = "vmscsi" [SCSI.Load] vmscsi = vmscsi.sys, 4 [SCSI] vmscsi = "VMware SCSI Controller" File drivers are directly copied into the I386 directory: vmscsi.sys vmscsi.inf vmscsi.cat Everything is fine, but if I want to change the source folder to an another one, i.e., I386\drivers\vmscsi, by editing DOSNET.INF: [Directories] d5 = \I386\drivers\vmscsi [Files] d5,vmscsi.sys Then Setup don't find the driver. Also, I tried to add all driver files to DOSNET.INF: [Directories] d5 = \I386\drivers\vmscsi [Files] d5,vmscsi.sys d5,vmscsi.inf d5,vmscsi.cat But NO go Is it possible to put the drivers in another subdirectory that is NOT \I386 (on the source CD)?? For example, on I386\drivers\vmscsi. Thanks PS: Note I'm NOT using the WINNT.SIF answer file, and I don't want to use it (I know this is possible with the OemPnpDriversPath directive, but I don't want an answer file in order to respect the original Setup behavior).

Can you explain, step by step (for dummies), how to integrate SATA/RAID drivers directly into TXTSETUP.SIF without disabling the Recovery Console? I'm very, very interested. Thanks.

Anyone? I' like to correct part of the information said above: the repair option will be disabled because the existence of the WINNT.SIF file, not only the directive. In order to the repair option work (access to Recovery Console and so on), no answer file may exist.

Very interesting... I'm guessing if it is possible to achieve the same results posted in the Unattended Guide without adding the OemPnpDriversPath directive... The reason is if this directive is added to WINNT.SIF, repair option will be disabled, and I'd like to preserve this feature. Thanks.

Ok, thanks for your replies. Is harder than what I expected...

Ok, you're right. I see the patch is for .NET Framework 2.0, the "infamous" KB928365, the hardest patch to integrate in the .NET 2.0 installation, believe me (see my last posts in the Silent .NET Maker of Tomcat76 if and you'll understand). Since .NET 2.0 installation is driven by Windows Installer, you could try Windows Installer directives passed as arguments (a.k.a "public properties"). Try the following directive: REBOOT=S And this one: REBOOT=R (more agressive, suppress all kinds of reboots).

Anyone? Is this virtually impossible ?

Try to add the /Z switch to the "problematic" patch: ECHO Please wait... start /wait %PATHTOFILE%\KB928365-NET2-Fix.exe /Q /Z *** reboots after installing or near the end of installing this patch**** ECHO Done! /Z means "no restart", actually superseded by the new "/norestart" switch. Both have the same effect.

Post the first 5 lines of your HIVESFT.INF file. If you add coments, remember to put the semicolon symbol at the beginning of the comment, as this: ; This is a valid comment.