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?

Well, no luck so far. Used BTS Driverspack and still had problems, moving on to here: http://www.msfn.org/board/index.php?showtopic=26161&st=520#

After I install the BTS driverpack, should Winnt.sif include something like this: [MassStorageDrivers] "Intel(R) 82801FR SATA RAID Controller" = OEM [OEMBootFiles] iaStor.inf iaStor.sys iaStor.cat Txtsetup.oem (Found this at http://www.intel.com/support/chipsets/iaa_.../CS-009344.htm) Anyway, it looks like it added the drivers path and all the drivers, TXTSETUP.SIF was also updated. update Well, tried this and when it was time to pick a partition, the RAID drive wasn't there, just my IDE1 master and slave. So, I tried it with the [MassStorageDrivers] info and it found my RAID drive, but I got another unexpected error(18) at line xxxx in d:\xpsprtm\xx. I think I'll take a harder look at TXTSETUP.OEM, I don't know if I'm supposed to do anything with it yet.

I got the same error, I didn't need the Graphics driver pack B, so I deleted it, then it went fine. This is my first try with the driver packs, previously had been trying it manually. All my drivers were installing OK, except I got the same BSOD when I added RAID drivers; http://www.msfn.org/board/index.php?showtopic=39581 Going to try and install with the driver packs now.

Now that I'm sober, let's try this again. I did search, but for the wrong problem I guess. I didn't realize F6 was not an option unattended. I used Michael Hollinger's guide to add the SATA/RIAD 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 this time until the install was complete and Windows rebooted, it should have ran my RunOnceEx.cmd, but instead I got a blue screen with an error. Don't remember what it said for sure, there was some windows error, could be a virus, blah, blah, I remember three hex addresses at the end of it. After that, I decided to try the F6 for the heck of it. Which I know now won't work. I'll burn another DVD and give it a try again. I'll record the error this time. Updated OK, this time I double checked my TXTSETUP.OEM(which I did not edit) and TXTSETUP.SIF files, everything looks right. I have my TXTSETUP.SIF in my Root\I386 directory with the TXTSETUP.OEM and RAID/SATA drivers located in Root\$OEM$\$1\drivers\002_raid. Tried to install but received 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 press any key to continue" Then it starts to copy windows files. Which I ended up cancelling. If nobody has any ideas, I'll probably try the driverpacks next.

Using the info I've found on these forums, I've added what I thought was the neccessary data to my UA to install on a RAID setup. But I missed something. I just added 2 new SATA drives on my ABIT IS7(ICH5R controller). Enabled SATA mode and setup the drives in RAID 0. Thought my UA was setup correctly, but was getting errors copying files, so I tried the RAID drivers on floppy disk so, when I installed WinXP, I pressed F6 to install the drivers and did so when prompted. Then after I selected the partition to install WinXP, it says it's going to start copying files, right away I get an error copying iaStor.sys. I hit enter a few times to retry and nothing so I hit ESC to skip, then I get another of the iaStor(.inf or .cat) files can't be copied so I skip again with the third iaStor file and get an error. After skipping those files, the rest of XP installs but I end up with a blue screen and an error(forgot what it said, it was half a page long) and it reboots continuously. Any ideas what I did wrong?

I've completed my WinXP UA and tested using MS Virtual PC. Now that I've got that behind me, my next step is to replace the IDE HD with two SATA drives in RAID 0. So using the info I've found here, I've added everything I think I need to do the RAID install unattended but would like to test it first. Just want to make sure I'm not going to screw up my PC.

During my UA Install, Windows Media Encoder 9 and Windows Media Player 10 do not get installed. From my RunOnceEx.cmd REG ADD %KEY%\040 /VE /D "Windows Media Encoder 9" /f REG ADD %KEY%\040 /V 1 /D "%systemdrive%\Apps\wmencoder\WMEncoder9.exe /Q:A /R:N /f REG ADD %KEY%\050 /VE /D "Windows Media Player 10" /f REG ADD %KEY%\050 /V 1 /D "\"%systemdrive%\Apps\WMP10\MP10Setup.exe\" /q:A /c:"setup_wm.exe /Q /R:N /DisallowSystemRestore" /f Anyone see an error here?

I want to enable Forced Logoff in my unattended install. By running the program gpedit.msc it is found in Local Computer Policy\Computer Configuration\Windows Settings\Security Settings\Local Policies under Network Security. I have found this in my registry HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\EnableForcedLogOff Currently REG_DWORD is 1, but it is not enable. Does 1 or 0 indicate enabled?

Would this be it? HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\EnableForcedLogOff On my box, REG_DWORD is 1, which I thought would be enabled, but I don't have it enabled.

I got it to work in my batch_file using the following; ECHO Please wait... start /wait %systemdrive%\install\Applications\MSAntispy\MicrosoftAntiSpywareInstall.exe /s /a /s /v"/qb" ECHO Please wait... start /wait %systemdrive%\"Microsoft AntiSpyware.msi" /quiet Note: If I remember correctly, I removed a space or two in the original file name MicrosoftAntiSpywareInstall.exe so I didn't have to use " "s.