wurzl100

Hi community, after 5 days of trying to integrate my VIA SATA driver it works now. I didnt do it by Nlite or Driverpacks because everything went wrong. I saw a file from Microsofts Knowledge Base with which I proceeded and now Windows XP is installing unattended. The Problem I have is the following: Within the DOS based setup, when the files are copied to the harddisk it takes unusually long. For 10 Minutes nothing happens, and in the grey colored bar on the bottom of the screen where usually the copied files are displayed is nothing. After around 10 Minutes Windows is starting to copy the files. After this problem the setup is proceeding normal. When I install it with my CD there is no time Problem. Does anybody know how I could fix this problem ? Thanks in advance wurzl100

Hi, thanks for you answer, but after my last post here in the forum (maybe 3 days ago) I got messages via mail, I have to use driverpacks because it was not working with nlite. The details are in my last post. Now I used Driverpacks and I should use Nlite again. 5 or 6 days I am trying now to get this board to run but there is no way and no help. ***confused***

Is this really possible that nobody knows anything ?

Hi community, because my unattended tftp installation doesnt work with help of nlite i decided to give "driverpacks" a chance. The Problem is to integrate my VIA Raid driver. I prepared a Windows XPSP2 folder with the help of driverpacks, means I slipstreamed the drivers with method 2. My question is now, what files do I have to edit, and what folders I have to make. Do I need the Folder "Textmode" within the Folder I386 ? Where do I have to put the txtsetup.oem file ? What changes I have to make in the unattend.txt file ? Do I have to make changes in the txtsetup.sif file ? I appreciate every answer ! Best regards wurzl100

Hi friends, I am very confused because of a unattended installation problem I cant solve by my own. My Infrastructure: I use an "Eisfair" Server http://www.eisfair.org/ which is configured as a RIS Server (means Samba, TFTP, DHCP...) My Problem is to install a Computer with a VIA RAID Controller (the driver file is called viamraid.sys) I have a WINXP_SP2 Image, that I extracted to my harddisk. Then I was using NLite to integrate the RAID driver files and was burning an image. With help of this image, made by NLite it was possible to install this computer without any Problems via unattended CD. So now, sure that is has to work I extracted the Windows Image again and used NLite again only to integrate the RAID Driver files. Additionally I was proceeding with this Microsoft Artice Microsoft Guideand after this modifications I was transfering the modificated i386 folder onto my servers share. The computer was booting well (without any bluescreen I got before I was including the RAID drivers) and it transfered the install files to the Harddisk. When it finished the Problem began. Its booting and runs chdisk. When checkdisk is ready it says "I have to repair some problems at the filesystem" and the computer is rebooting. This Problem I have NOT when I use the unattended CD although there should be no problem between both i386 folders (that one on CD oder that one on my Server share). When it starts again checkdisk is running again and now there are no Problems with the file system. But when Windows starts to make the filellist to transfer there are a lot of messages like: "Could not transfer file xyz" Press Enter to Repeat, ESC to jump over this file oder F3 to stop the instalation process" and it always begins with "The file cbidf2k.sys cant be transfered" Press...... My Board is an ASUS "K8V-X SE" Everything I tried was not successfully. HERE I HAVE TO SAY THAT MY HARDDISK IS OK...NO PROBLEM TO INSTALL WINDOWS VIA A UNATTENDED CD (I only say this to prevent users to think the chdisk problem has something to do with a defective harddrive.) Here is my unattend.txt file (only the relevant part) ;SetupMgrTag [Data] AutoPartition=1 MsDosInitiated="0" UnattendedInstall="Yes" [Unattended] DriverSigningPolicy=Ignore UnattendMode=DefaultHide FileSystem=ConvertNTFS ExtendOemPartition=1 OemSkipEula=Yes OemPreinstall=Yes TargetPath=\WINDOWS UnattendSwitch=Yes [MassStorageDrivers] "IDE CD-ROM (ATAPI 1.2)/PCI IDE-Controller"="RETAIL" "VIA RAID Controller(Windows XP)"="OEM" [OEMBootFiles] viamraid.sys viamraid.inf viamraid.cat txtsetup.oem Here is my txtsetup.oem file # [Disks] d1 = "VIA RAID Combo Driver Diskette", \viamraid.sys, \ [Defaults] scsi = VIARAID_MULTIPLE_XP [scsi] VIARAID_MULTIPLE_XP = "VIA RAID Controller(Windows XP)" [Files.scsi.VIARAID_MULTIPLE_XP] driver = d1, viamraid.sys, VIAMRAID_NT5 inf = d1, viamraid.inf ## Cat file directive. It should be marked with non-digital signed driver catalog = d1, viamraid.cat [HardwareIds.scsi.VIARAID_MULTIPLE_XP] id = "PCI\VEN_1106&DEV_3249","viamraid" id = "PCI\VEN_1106&DEV_3149","viamraid" id = "PCI\VEN_1106&DEV_3164","viamraid" [Config.VIAMRAID_NT5] value = Parameters\PnpInterface, 5, REG_DWORD, 1 This is my file structure: i386 --->$OEM$ ----------->Textmode ----------------------->TXTSETUP.OEM ----------------------->viamraid.cat ----------------------->viamraid.sys ----------------------->viamraid.inf This is my txtsetup.sif file (only the relevant parts) [SCSI] viamraid = "VIA RAID Controller(Windows XP)" I hope somebody can help me !! Thanks a lot Best regards wurzl100 EDIT 1: I made a test especially regarding the first file it cant find called cbidf2k.sys First I letted the computer start via PXE and Windows copied the the files to the harddisk. Then the computer was rebooting. Now I startet with a DOS Bootdisk and was looking to the drive C: There was now a folder called $WIN_NT$.~BT. I changed into this folder and there was the file CBIDF2K.SY_ Now I startet the Computer by Harddisk and Checkdisk was saying again that there are problems which are repaired now. Windows rebootet again and I startet again with the DOS Disk. The file CBIDF2K.SY_ was still existing, but when I was booting again by harddisk it says again "The file bcidf2k.sys couldnt be transfered". So I think It has really something to do with the RAID Driver after the first reboot. Maybe somebody can help me.