viol8r

OK, sorry

MCT, I see in your sig your running a Audigy 2 zs on a IS7. I'm currently using the built in audio on the IS7, you see much improvement in gaming audio? I haven't decided whether to spend the extra cash for the Audigy or stay with what I've got.

I know and tried. I didn't have the hours it took to weed through all the interesting topics I came accross and when I tried the search, well that list would have been hours too. Plus I'm lazy and I know some honorable person would help me out

OK, got my network all setup, 3 PCs connected to a Linksys router. I'm able to access the other two PCs from mine, but I would like to be able to monitor(spy) and control the other two from mine. Like a virtual desktop I guess. Let me know any suggestions. Thanks

This is what I used everesthome151 /SILENT /SP- It installs, but I still see the progress bar.

Moved all entries in unattend.txt [MassStorageDrivers] "Intel(R) 82801ER SATA RAID Controller" = OEM [OEMBootFiles] iaStor.inf iaStor.sys iaStor.cat Txtsetup.oem to winnt.sif, removed unattend.txt file and tried real life test and got an error with the following: "File txtsetup.oem caused an unexpected error(18) at line 1747 in d:\xpsprtm\base\boot\setup\oemdisk.c

If it helps, here's my winnt.sif and unattend.txt files. One other thing, I put a cabbed file of all iastor.* files and txtsetup.oe_, and an uncompressed file of each in my drivers folder. If there is any particular test you want me to try, just let me know. winnt.sif.txt UNATTEND.TXT

Here are my txtsetup files, the orginal; txtsetup.old and my working version; txtsetup.oem(had to add .txt to attach to post). I've commented in my working file what I changed. After I installed using my Xp CD and F6 with the drivers disk, I found which SATA/RAID controller I had, so I focused on just that one(82801ER). TXTSETUPOEM.txt TXTSETUPold.txt

Originally I had tried it by adding RAID manually. I used Michael Hollinger's guide to add the SATA/RAID drivers. http://www.msfn.org/board/index.php?showtopic=32151&st= I've tested this UA install using MS Virtual PC before I added the SATA/RAID, and everything went fine. Everything seemed to go fine until the install was complete and Windows rebooted, it should have ran my RunOnceEx.cmd, but instead I got the BSOD. Then I tried it again, but I can't remember what I changed(I think I messed with the entries in txtsetup.sif), but I got the following errors; "File txtsetup.oem caused an unexpected error(18) at line 1747 in d:\xpsprtm\base\boot\setup\oemdisk.c press any key to continue" Then I get "Section Files.SCSI.iaStor of the INF file is invalid" After I hit Enter, I get: "File caused an unexpected error(0) at line 2166 in d:\xpsprtm\base\boot\setup\oemdisk.c That is when I decided to try the Driverspacks. So: 1. I used BASE 5.02.7 and Mass Storage 5.02.1 2. I had several duplicate entries related to iastor, so I removed them all. 3. Then manually added to txtsetup.sif: [sourceDisksFiles] iaStor.sys = 100,,,,,,3_,4,1,,,1,4 [HardwareIdsDatabase] PCI\VEN_8086&DEV_24DF&CC_0104 = "iaStor" [sCSI.Load] iaStor = iaStor.sys,4 [sCSI] iaStor = "Intel® 82801ER SATA RAID Controller" 4. Tested on real PC OK. I have modified my txtsetup.oem to match the entries in txtsetup.sif(they did not match previously). I have both a winnt.sif and an unattend.txt file. I'll see what else I can find when I get home.

Yes I do, should I not? I got that from Intel website: http://www.intel.com/support/chipsets/iaa_...b/CS-009344.htm I removed it from winnst.sif when I was getting errors, but then my RAID drive wasn't recognized. So I added it to unattended.txt per Intel when I made the changes to txtsetup.sif and txtsetup.oem. When I get home tonight, I might be able to try a couple different things to see if I can isolate what fixed my problem.

Tested fully, actually I'm currently using it now. After manually modifying the txtsetup a few times and using the driverspack, I had found several different references to iastor, so just to clean it up, I had deleted them and started over. I don't know if this fixed my problem or not. Like I said, I think my fix came from editing txtsetup.oem the one thing I wasn't sure if I needed to mess with early on in this endevour. My guess was that txtsetup.oem was a reference for what needed input into txtsetup.sif. I forgot to mention that I edited my unattend.txt file too, looks like this; [Unattended] [MassStorageDrivers] "Intel(R) 82801ER SATA RAID Controller" = OEM [OEMBootFiles] iaStor.inf iaStor.sys iaStor.cat Txtsetup.oem

With less than 2 hours before my MS Virtual PC Trial expires, I got it to work. I used the BTS Driverspack, but since I didn't need wireless LAN drivers and graphics drivers in pack B, I deleted those. Then ran the slipstreamer.cmd file with no errors, this was with BASE 5.02.7. After copying the required files to my XPUA directory and running the Run_me.cmd, I trimmed down the drivers to only those I needed to save space(my XPUA barely fit on a DVD). I also modified the OemPnPDriversPath for my respective drivers. I had done this before and had errors installing, always something with txtsetup, so I went into txtsetup.sif and deleted any entry containing reference to iastor. BTW, I'm installing on an ABIT IS7(865 chipset) with two Intel SATA ports only. Then I added the following to txtsetup.sif [SourceDisksFiles] iaStor.sys = 100,,,,,,3_,4,1,,,1,4 [HardwareIdsDatabase] PCI\VEN_8086&DEV_24DF&CC_0104 = "iaStor" [SCSI.Load] iaStor = iaStor.sys,4 [SCSI] iaStor = "Intel(R) 82801ER SATA RAID Controller" I think I really made the difference in my txtsetup.oem, although I could be wrong. Here is what it looks like now [Disks] disk1 = "Intel Application Accelerator driver", iaStor.sys, \ [Defaults] scsi = iaStor ;----------- Component Section ----------- [scsi] iaStor_ICH6R = "Intel(R) 82801FR SATA RAID Controller" iaStor_ICH6R = "Intel(R) 82801FR SATA RAID Controller" iaAHCI_ICH6R = "Intel(R) 82801FR SATA AHCI Controller" iaStor = "Intel(R) 82801ER SATA RAID Controller" iaStor_ICH5RHR = "Intel(R) 6300ESB SATA RAID Controller" ;------------------------------------------- [Files.scsi.iaStor] driver = disk1, iaStor.sys, iaStor inf = disk1, iaStor.inf catalog = disk1, iaStor.cat [Files.scsi.iaStor_ICH6R] driver = disk1, iaStor.sys, iaStor inf = disk1, iaStor.inf catalog = disk1, iaStor.cat [Files.scsi.iaAHCI_ICH6R] driver = disk1, iaStor.sys, iaStor inf = disk1, iaAHCI.inf catalog = disk1, iaAHCI.cat [Files.scsi.iaStor_ICH5R] driver = disk1, iaStor.sys, iaStor inf = disk1, iaStor.inf catalog = disk1, iaStor.cat [Files.scsi.iaStor_ICH5RHR] driver = disk1, iaStor.sys, iaStor inf = disk1, iaStor.inf catalog = disk1, iaStor.cat ;------------------------------------------- [Config.iaStor] value = "", tag, REG_DWORD, 1b value = "", ErrorControl, REG_DWORD, 1 value = "", Group, REG_SZ, "SCSI miniport" value = "", Start, REG_DWORD, 0 value = "", Type, REG_DWORD, 1 ;------------------------------------------------------- [HardwareIds.scsi.iaStor_ICH6R] id = "PCI\VEN_8086&DEV_2652&CC_0104","iaStor" [HardwareIds.scsi.iaStor_ICH6R] id = "PCI\VEN_8086&DEV_2652&CC_0104","iaStor" [HardwareIds.scsi.iaAHCI_ICH6R] id = "PCI\VEN_8086&DEV_2652&CC_0106","iaStor" [HardwareIds.scsi.iaStor] id = "PCI\VEN_8086&DEV_24DF&CC_0104","iaStor" [HardwareIds.scsi.iaStor_ICH5RHR] id = "PCI\VEN_8086&DEV_25B0&CC_0104","iaStor" I modified the ones for my particular hardware the "82801ER, PCI\VEN_8086&DEV_24DF&CC_0104" to match what was in txtsetup.sif. I hope this helps anyone that may have similar problems.

We got a bit off topic, but I finally got it to work. As I said previously, when I installed from my original XP CD to my new RAID drive, the bootable drive ended up being 'G', with my IDE drives still 'C' and 'D'. Now that I got my UA DVD working, it lists the RAID drive as 'C' and my old IDE drives as 'D' and 'E'. So I won't need to change them anyway.

I'll give this a try once my install works; How to change a drive letter To change an existing drive letter on a drive, on a partition, or on a volume, follow these steps: 1. Log on as Administrator or as a member of the Administrators group. 2. Click Start, click Control Panel, and then click Performance and Maintenance. 3. Click Administrative Tools, double-click Computer Management, and then click Disk Management in the left pane. 4. Right-click the drive, the partition, the logical drive, or the volume that you want to assign a drive letter to, and then click Change Drive Letter and Paths. 5. Click Change. 6. Click Assign the following drive letter if it is not already selected, click the drive letter that you want to use, and then click OK. 7. Click Yes when you are prompted to confirm the drive letter change. The drive letter of the drive, the partition, or the volume that you specified is changed, and the new drive letter appears in the appropriate drive, partition, or volume in the Disk Management tool. From http://support.microsoft.com/default.aspx?...;307844&sd=tech

I did it the old fashion way with my original XP CD just to rule a few things out and Xp installed fine. So I'm not going to give up, probably work with the BTS Driverpacks for now. One thing I did notice after I installed Xp on my RAID drive, my HD IDE drives C and D are still the same drive letter, DVD drives are E and F and my new RAID drive with Xp is drive G, I haven't checked yet, but I'm sure there's a way to make my G drive look like the C drive, correct?