Sgt_Strider
Content Type
Profiles
Forums
Events
Posts posted by Sgt_Strider
-
-
Hi y'all!
What I'm about to explain is how you can add SATA/RAID drivers by editing only one file - TXTSETUP.SIF - which is placed in the I386 folder (C:\XPCD\i386\TXTSETUP.SIF). I've tested this method and it's bulletproof (atleast so far
)...First of all I want to thank the guy that posted THIS several years back (and it was for Windows 2000 back then), without that posting I would still be pounding my head against a brick-wall.
This post should cover whatever SATA controller out there - just test for yourself. The guy in the original posting mentioned above, is talking about an IBM ServerRaid driver/controller. The SATA driver I want to install is for the Intel® 82801GBM SATA AHCI Controller (Mobile ICH7M/DH).
Follow this guide step by step:
1. Comment out or remove anything under MassStorageDriver and OEMBootfiles you might have in WINNT.SIF.
2. Download the latest drivers (I'm using the current v6.x driver from Intel) and extract them.
3. Copy only the .SYS file (iastor.sys) to the C:\XPCD\I386 folder. Keep the other files - you'll need some information from them a little later. Note that it's important that the .SYS file is uncompressed.
4. In the C:\XPCD\I386 folder you must now open the file TXTSETUP.SIF in your favorite text-editor and do the following:
4.1 Under the section [sourceDisksFiles] add:
iastor.sys = 1,,,,,,_x,4,1
Remember to change the name of the sys file to the one you use! I put this on line 1653.
4.2 Under the section [HardwareIdsDatabase] add:
PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor"
You will find the information for your specific controller in the file TXTSETUP.OEM that you extracted with the driver. I put this on line 18800.
4.3 Under the section [sCSI.Load] add:
iastor = iastor.sys,4
Change the names iastor and iastor.sys to your file's name. I put this on line 19244.
4.4 Under the section [sCSI] add:
iastor = "Intel(R) 82801GBM SATA AHCI Controller (Mobile ICH7M/DH)"
Change the name iastor to your file's name. I think the name in "" can be whatever you like, but I used the same name used in TXTSETUP.OEM just in case. I put this on line 21586.
5. Save the file and exit. Burn the image and boot using the CD... Voila!
--------
Notes:
- No need to use the TEXTMODE folder. Just delete.
- No "The file txtsetup.oem caused an unexpected error (18)...blahblah" error message during installation. This is the real reason I'm now using this method.
- No need for ekstra files in the image - but you still need drivers defined in OemPnPDriversPath in WINNT.SIF. This explanation is only for the textmode and protected mode of the Windows XP Pro installation!
- No need for any entries in WINNT.SIF (except the one above).
- The only downside is that you actually have to edit the TXTSETUP.SIF file.
Tell me what you think - does it work for you as well?
@Philster: I think you can add all the different SATA drivers you want to, but I've only tested the one I documented here. Sharing is the thing!
@mjschug: You did what I said in number 3? I haven't tested this over a network installation, however, I will test this on RIS in a week or so (I hope). I will keep you updated on this.
@azaze1: Fixed! Thanks!
@LispWarez: Hmmm .. didn't see it!
Thanks for the guide, but I'm confused. Where do you place the drivers then? In the $OEM$\$1\drivers folder? Your post doesn't mention anything about placing the drivers. Or maybe I don't have to since this is modified and Windows XP will install its own driver?
0 -
hi Sgt_Strider! yup you can use HFSLIP for unattended install ... you may need to define it via winnt.sif ... as for $OEM$ directory, HFEXPERT feature can address it
WHat do you mean by HFExpert can address it?
0 -
So is this method actually working or you guys are still trying to debug it?
0 -
Are any of you guys using HFSlip for unattended install? I find it odd that the program say $OEM$ folders aren't necessary. Why is that the case? I used it and everything installed unattended.
0 -
@Sgt_Strider:
What exactly doesn't work? Is IE7 simply not installed? Do you get an error message?
For WMP11, use a program such as 7-Zip or WinRAR. Right-click on wmp11-windowsxp-x86-enu.exe and extract the contents into a folder. Rename the folder WMP11 and place the folder itself (i.e. not just the files) into HF.
Nevermind, after the computer rebooted, IE7 is up and running.
0 -
I'm using the latest version of HFSLIP, 1.21 and I can't get IE7 to install. I dump the IE7 exe file that I downloaded from MS into the HF folder and it doesn't work. Also, do you guys just place the WM11 file into the HF folder or you placed a modified WM11 file into the HF folder? If so, how do I make the modified WM11 file?
Here is my log:
HFSLIP Version - 61216
HFSLIP Path - C:\Hfslip\
OS in SOURCESS - XP SP2 English
Service Pack Slipstreamed
Drivers - DRIVER.CAB Updated
CD Install Path - Default
CDTAG - WIN51
===============================================================================
Files in your FIX folder:
Files in your HF folder:
IE7-WindowsXP-x86-enu.exe
KB835935-SP2-ENU.exe
WindowsMedia-KB911564-x86-ENU.exe
WindowsXP-KB873339-x86-ENU.exe
WindowsXP-KB885836-x86-ENU.exe
WindowsXP-KB886185-x86-enu.exe
WindowsXP-KB888302-x86-ENU.exe
WindowsXP-KB890859-x86-ENU.exe
WindowsXP-KB891781-x86-ENU.exe
WindowsXP-KB893756-x86-ENU.exe
WindowsXP-KB896358-x86-ENU.exe
WindowsXP-KB896423-x86-ENU.exe
WindowsXP-KB896424-x86-ENU.exe
WindowsXP-KB896428-x86-ENU.exe
WindowsXP-KB898461-x86-ENU.exe
WindowsXP-KB899587-x86-ENU.exe
WindowsXP-KB899591-x86-ENU.exe
WindowsXP-KB900485-v2-x86-ENU.exe
WindowsXP-KB900725-x86-ENU.exe
WindowsXP-KB901017-x86-ENU.exe
WindowsXP-KB901214-x86-ENU.exe
WindowsXP-KB902400-x86-ENU.exe
WindowsXP-KB904706-v2-x86-ENU.exe
WindowsXP-KB905414-x86-ENU.exe
WindowsXP-KB905749-x86-ENU.exe
WindowsXP-KB908519-x86-ENU.exe
WindowsXP-KB908531-v2-x86-ENU.exe
WindowsXP-KB910437-x86-ENU.exe
WindowsXP-KB911280-v2-x86-ENU.exe
WindowsXP-KB911562-x86-ENU.exe
WindowsXP-KB911567-x86-ENU.exe
WindowsXP-KB911927-x86-ENU.exe
WindowsXP-KB912919-x86-ENU.exe
WindowsXP-KB913580-x86-ENU.exe
WindowsXP-KB914388-x86-ENU.exe
WindowsXP-KB914389-x86-ENU.exe
WindowsXP-KB916595-x86-ENU.exe
WindowsXP-KB917422-x86-ENU.exe
WindowsXP-KB917953-x86-ENU.exe
WindowsXP-KB918439-x86-ENU.exe
WindowsXP-KB919007-x86-ENU.exe
WindowsXP-KB920213-x86-ENU.exe
WindowsXP-KB920214-x86-ENU.exe
WindowsXP-KB920670-x86-ENU.exe
WindowsXP-KB920683-x86-ENU.exe
WindowsXP-KB920685-x86-ENU.exe
WindowsXP-KB920872-x86-ENU.exe
WindowsXP-KB921398-x86-ENU.exe
WindowsXP-KB922582-x86-ENU.exe
WindowsXP-KB922616-x86-ENU.exe
WindowsXP-KB922819-x86-ENU.exe
WindowsXP-KB923191-x86-ENU.exe
WindowsXP-KB923414-x86-ENU.exe
WindowsXP-KB923980-x86-ENU.exe
WindowsXP-KB924191-x86-ENU.exe
WindowsXP-KB924270-x86-ENU.exe
Files in your HFCABS folder:
swflash.cab
Files in your HFSVCPACK folder:
Files in your HFSVCPACK_SW folder:
Files in your HFTOOLS folder:
bbie.exe
CDIMAGE.EXE
===============================================================================
HFSLIP run time: 23m08s
0 -
Hi Sgt_Strider
HFSLIP doesn't do unattended installs; it slipstreams hotfixes into a Windows installation source. Hotfixes are extracted, and the files inside them are copied into the source, replacing existing files. The *.cat files are copied over as well so Windows setup knows that the updated (or new) files are OK. During Windows setup, the necessary registry settings from the hotfix installation INFs are applied so Windows Update knows that they have been installed.
Silent installers, MSI files and some hotfixes are not slipstreamed; they're integrated into the SVCPACK folder to be installed at T-13.
Sorry.
Does HFSLIP follow Microsoft protocols in implementing these files? Or it breaks with certain protocols like what nlite does? That is what I really want to know.
0 -
The WAIK is for Vista, but you can make .WIM images of XP that you can then dump on machines via ximage. You still need to build a clean XP machine, sysprep it, and shut it down, before you can ximage it (just like Vista). However, it does not recognize or use any of the unattended files created by the WAIK (they're XML, and only used by Vista).
Didn't Microsoft released a utility for unattended installs not too long ago for Windows XP?
0 -
I got a quick question to ask you guys. Is the ISO created by HFSLIP the same as it would be if I followed the MSFN unattended guide? Is this ISO somehow inconsistent with Microsoft's standard and or break with the standard like nlite?
0 -
I'm getting the impression that this program will make things easier to install Windows XP unattended or I am wrong? I don't see many posts about this subject.
0 -
I second the IEAK suggestion, as this is the supported way of adding certain changes that otherwise get reset after a new user logs in.
How do you integrate IE7 via the IEAK method?
0 -
-
I know this may be a bit anal, but what font and sizes do you guys use to compose your e-mail? Do you try to ensure that all e-mails meet certain format criterias? Also do you guys enable the change in font colour when responding to e-mails? Or you leave it the same colour as when you first composed the message?
0 -
If your Gateway laptop needs the driver, then you should integrate it by using nLite.Um, I have no problems installing Windows XP Professional on my desktop using a SATA drive. It's just that my laptop requires the Gateway driver if I am to install Windows XP. I don't know why, but there are threads around MSFN that talk about the same thing. I thought Nlite would make the process easier as I'm having issues getting it to work.It is very easy to do: Open the section "Driver Integration" and point to any INF file of your Gateway driver folder (maybe the driver has to be unzipped).
If you see a file named TXTSETUP.OEM within the driver folder, you should integrate the driver as TEXTMODE driver (otherwise as PnP driver).
So you're sure Nlite will do everything that is in this thread?
http://www.msfn.org/board/index.php?showtopic=77999
The reason why I ask is because the process to slipstream the SATA drivers requires the modification of some files and I'm not sure if Nlite will do that.
0 -
Afaik VMWare does not really support SATA disks, maybe this is the reason why your SATA drives are not detected by using VMWare.
On the other hand there is the "real" Windows XP SP2, which gives full support for SATA (non-RAID) connections. So you probably don't need to integrate any driver.
Um, I have no problems installing Windows XP Professional on my desktop using a SATA drive. It's just that my laptop requires the Gateway driver if I am to install Windows XP. I don't know why, but there are threads around MSFN that talk about the same thing. I thought Nlite would make the process easier as I'm having issues getting it to work.
0 -
Unless you have a RAID system, you don't need to integrate any special SATA drivers.
If you want to integrate third party S-ATA drivers, you can do it. Just integrate them as PnP driver witin the "Driver Integration" section of nLite.
For further help we need to know the kind of S-ATA controller of your mainboard.
I'm not sure what the SATA controller is in my laptop. All I know is that Gateway provides the driver and I need the driver or else Windows XP cannot be installed. My laptop is a Gateway NX100.
0 -
I'm a newbie using Nlite and the problem is that I can't install Windows XP on my laptop without the SATA drivers that Gateway provides. How do I integrate it with Nlite easily? Thanks.
0 -
Hey guys, I'm just wondering how you're installing the update KB913433? I get an error when I try to nlite the update or integrate it with other methods. I think it has to do with the version of my Macromedia flash.
My post above is a bit old, but I could sure use some definitive answers. So if my Windows XP installation comes with the latest Flash, then I can't install that update? If that's the case, then why did ppl even post this as a requirement for SP2? I don't even have Flash slipstream into my CD.
0 -
Hey guys, I'm just wondering how you're installing the update KB913433? I get an error when I try to nlite the update or integrate it with other methods. I think it has to do with the version of my Macromedia flash.
0 -
Just wondering. Thanks!
0 -
nVidia does provide drivers for thier mobile GPU's; it's just that most are covered by the standard GeForce Forceware driver. The only one that differs is the GeForce Go 7800 GTX, which has its own separate Forceware driver.
To see the full listing of mobile GPUs supported by the Geforce Forceware driver, read through the NV4_DISP_GO.INF file's [strings] section after decompressing the downloaded driver file. This listing is from v81.98:
;Mobile GPU's by www.laptopvideo2go.com
NVIDIA_G70.DEV_0098.1 = "NVIDIA GeForce Go 7800 "
NVIDIA_G70.DEV_0099.1 = "NVIDIA GeForce Go 7800 GTX "
NVIDIA_G70.DEV_009C.1 = "NVIDIA Quadro FX 350M "
NVIDIA_G72.DEV_01D7.1 = "NVIDIA GeForce Go7300 "
NVIDIA_G72.DEV_01D8.1 = "NVIDIA GeForce Go7400 "
NVIDIA_G72.DEV_01DC.1 = "NVIDIA G72GLm "
NVIDIA_NV11.DEV_0112.1 = "NVIDIA GeForce2 Go "
NVIDIA_NV17.DEV_0174.1 = "NVIDIA GeForce4 440 Go "
NVIDIA_NV17.DEV_0175.1 = "NVIDIA GeForce4 420 Go "
NVIDIA_NV17.DEV_0176.1 = "NVIDIA GeForce4 420 Go 32M"
NVIDIA_NV17.DEV_0177.1 = "NVIDIA GeForce4 460 Go "
NVIDIA_NV17.DEV_0179.1 = "NVIDIA GeForce4 440 Go 64M "
NVIDIA_NV17.DEV_017C.1 = "NVIDIA Quadro4 500 GoGL "
NVIDIA_NV17.DEV_017D.1 = "NVIDIA GeForce4 410 Go 16M "
NVIDIA_NV18.DEV_0186.1 = "NVIDIA GeForce4 448 Go "
NVIDIA_NV18.DEV_0187.1 = "NVIDIA GeForce4 488 Go "
NVIDIA_NV18.DEV_018D.1 = "NVIDIA GeForce4 448 Go "
NVIDIA_NV28.DEV_0286.1 = "NVIDIA GeForce4 4200 Go "
NVIDIA_NV28.DEV_028C.1 = "NVIDIA Quadro4 700 GoGL "
NVIDIA_NV31.DEV_0316.1 = "NVIDIA NV31M "
NVIDIA_NV31.DEV_0317.1 = "NVIDIA NV31M Pro "
NVIDIA_NV31.DEV_031A.1 = "NVIDIA GeForce FX Go 5600 "
NVIDIA_NV31.DEV_031B.1 = "NVIDIA GeForce FX Go 5650 "
NVIDIA_NV31.DEV_031C.1 = "NVIDIA Quadro FX Go 700 "
NVIDIA_NV31.DEV_031D.1 = "NVIDIA NV31GLM "
NVIDIA_NV31.DEV_031E.1 = "NVIDIA NV31GLM Pro"
NVIDIA_NV31.DEV_031F.1 = "NVIDIA NV31GLM Pro "
NVIDIA_NV34.DEV_0324.1 = "NVIDIA GeForce FX Go 5200 "
NVIDIA_NV34.DEV_0325.1 = "NVIDIA GeForce FX Go 5250/5500 "
NVIDIA_NV34.DEV_0328.1 = "NVIDIA GeForce FX Go 5200 32/64M "
NVIDIA_NV34.DEV_0329.1 = "NVIDIA NV34MAP "
NVIDIA_NV34.DEV_032C.1 = "NVIDIA GeForce FX Go 53x0 "
NVIDIA_NV34.DEV_032D.1 = "NVIDIA GeForce FX Go 5100 "
NVIDIA_NV36.DEV_0347.1 = "NVIDIA GeForce FX Go 5700 "
NVIDIA_NV36.DEV_0348.1 = "NVIDIA GeForce FX Go 5700 "
NVIDIA_NV36.DEV_0349.1 = "NVIDIA NV36M Pro "
NVIDIA_NV36.DEV_034B.1 = "NVIDIA NV36MAP "
NVIDIA_NV36.DEV_034C.1 = "NVIDIA Quadro FX Go 1000 "
NVIDIA_NV41.DEV_00C8.1 = "NVIDIA GeForce Go 6800 "
NVIDIA_NV41.DEV_00C9.1 = "NVIDIA GeForce Go 6800 Ultra"
NVIDIA_NV41.DEV_00CC.1 = "NVIDIA Quadro FX Go 1400 "
NVIDIA_NV43.DEV_0144.1 = "NVIDIA GeForce Go 6600 "
NVIDIA_NV43.DEV_0146.1 = "NVIDIA GeForce Go 6200 TE/6600 TE "
NVIDIA_NV43.DEV_0148.1 = "NVIDIA GeForce Go 6600 "
NVIDIA_NV43.DEV_0149.1 = "NVIDIA GeForce Go 6600 GT "
NVIDIA_NV44.DEV_0164.1 = "NVIDIA GeForce Go 6200 "
NVIDIA_NV44.DEV_0166.1 = "NVIDIA GeForce Go 6250 "
NVIDIA_NV44.DEV_0167.1 = "NVIDIA GeForce Go 6200 "
NVIDIA_NV44.DEV_0168.1 = "NVIDIA GeForce Go 6400 "
NVIDIA_NV44.DEV_016B.1 = "NVIDIA NV44GLM "
NVIDIA_NV44.DEV_016C.1 = "NVIDIA NV44GLM "
NVIDIA_NV44.DEV_016D.1 = "NVIDIA NV44GLM "
NVIDIA_NV44.DEV_0228.1 = "NVIDIA NV44M "I'm asking how to install the driver unattendedly. The driver from nvidia' website cannot be installed unattendly on a mobile nvidia GPU.
0 -
I don't see it on google.
0 -
Nvidia doesn't provide drivers for their mobile GPU's. Just wondernig how you guys are unattendedly installing the vendor's driver?
0 -
I have been using Active Sync 4.2 using "/qb-! /norestart" switches. Since 4.1 was also msi package, this option will workd for it too.
Try it!
After uninstalling my activesync 4.2, I have installed Activesync 4.1 using
Microsoft_ActiveSync_4.1.msi /qb-! /norestart
It works!
It doesn't work for me either.
0
)...
Type 2 Fix goes into HF folder?
in HFSLIP
Posted
Hi, I'm just wondering if type 2 fixes like KB923789 goes into the HF folder? What about the Windows Malicious Software Removal tool?