IcemanND

Have not yet heard anything back from microsoft. Currently the only solutions are posted in opening post or the hotfix integrate tool, or one of the othe cd creation tools here. As soon as M$ replaies I will post the info here.

what happens if you point them to a different ports instead of all of them to LPT1:?

The Ongoing saga: Apparently my case was escalated with M$ after I questioned the statement that the updates were not final. Here is the latest response. names and case numbers were changed. I have just finish taking his snapshots, I did one whith 885835 first and another with 885250 first, the exact same error, but just for his reference. I actually installed the hotfixes in different orders, one numerically the other but release date. Will post any response.

remove the set statement from the cdrom and basedir lines. Set WshShell = WScript.CreateObject ("WScript.Shell") Set Ag = Wscript.Arguments ' Process command line arguments if Ag.count < 2 Then WScript.Echo "Command Line Error. Need <CDROM> <Base Dir>" & vbcrlf WScript.Quit End if cdrom = Ag.item(0) basedir = Ag.item(1) ' execute program WshShell.Run (basedir & "\COMPONENT\LOOKOUT\LookOut120.exe /S") ' wait for startup and then start sending keystrokes WScript.Sleep 5000 WshShell.SendKeys "{SPACE}" ' Wait for install to finish WScript.Sleep 10000 ' Quit WScript.Quit

search for textmode driver on the forum. If that doesn't help let us know what scsi controller you are trying to install.

if you run a hotfix with the /L switch it will tell you what hotfixes are installed.

I have same controller though mine is setup as raid. You should only have to change the [HardwareIdsDatabase] info, and the description in [sCSI] below for yours. (highlighted in red) I don't know if this is the best way, just that it works. compress iastor.sys with makecab and place in i386. create $oem$\drivers\iaa place all drivers from floppy in this folder. iaStor.sys iaStor.inf iaStor.cat iaAHCI.inf iaAHCI.cat txtsetup.oem (Be sure you have drivers that work if you use F6 during install. I found that the floppy creation utility provided by Intel did not work for mine, I had to use the drivers which where in the inf update for the chipset.) added to i386\winnnt.sif OemPreinstall=Yes OemPnpDriversPath = "DRIVERS\IAA;" DriverSigningPolicy = ignore added to i386\txtsetup.sif (info found in txtsetup.oem) A note to others who see this, I don't know why but what is highlighted in blue above by default in txtsetup.oem is 'iaStor_ICH6R' if I left it this way the controller was not detected, but when shortened to 'iaStor' it worked fine.

Well in an attempt to find a solution I brought this up with M$ and rcvd the following response. 2 is kind of scary: Actually, both the hotfixes are not of the final version. Yet they have released it anyhow. So would that make them BETA?

post your answer file, and directory structure for us to take a look at and how are you pushing this to machines.

when you say it doesn't do noth does it do only the nic, video or does that vary?

Which is exactly what I needed to do set the default printer. The printers were already installed in the image just had to set the appropriate default. All I needed was a line in runonce, not a app and a line in runonce.

where was that 2 years ago when I had to set default printers duing syspreped ghost deployments. I ended up writeing an app to do it all i needed was : rundll32 printui.dll,PrintUIEntry /y /n "printer1" Thanks Ghost82

the more stars they have just says they waste way too much time hanging around here lets see 118 post to go to get to 500, no wait this will make 117, time to go waste more time.....

Have you tried downloading drivers from VIA? They appear to have just updated the driver for their usb chips, depending upon you VIA chip number. Says to install it after the Windows driver is loaded. http://www.viaarena.com/downloads/drivers/...USB2_V260-L.zip

What firewire adapter are you using, and what chipset? I have four systems all running xp sp2 with 1394a and 1394b and have not had any issues using the native drivers with xp sp2. And is it a firewire adapter issue or a peripheral issue? ie port drivers install and work but devices don't when plugged in?

sounds like a job for bartpe

Full Instructions: EDIT: Moved to first post

I didn't want to have to rewrite it again just for people like you who don't like backslashes. Seems I am learning from the past.

don't know it's just the way the integrate switch method seems to do it. possibly a little faster but you'll have to decide for yourself.

Since I wrote DetectCD.exe I have had requests for a similar utility for removable drives. So I rewrote & renamed DetectCD to DetectDrive. It Now Detects all drive attached to a system (except A:) and creates a permanent environment variable. Usage: DetectDrive {options} Options: HELP Shows help this screen BACKSLASH Return value has backslash 'C:\', default is no backslash 'C:' REMOVABLE Create variable for all removable drives except A:, i.e usb, firewire, etc. REMOVABLE# FIXED Create variable for all fixed disk drives, FIXED# REMOTE Create Variable for all Remote or network drives, REMOTE# CDROM Create Variable for all CD-Rom drives, CDROM# RAMDISK Create Variable for all RamDrives, RAMDRIVE# ALL All variables will be created # will be replaced with a number corresponding to the order in which the drive is lettered starting with 1 for each group. DetectDrive Fixed CDROM Removable Backslash returns the following on my system in the environment variables FIXED1=C:\ FIXED2=D:\ FIXED3=F:\ CDROM1=E:\ CDROM2=M:\ REMOVEABLE1=G:\ You can use as many switches as desired. But at least one must be selected other than BACKSLASH EDIT: IMPORTANT NOTE: 4/7/2006 You will not see the variables created until you open a new cmd window, but if you go to 'System Properties -> advanced -> environment variables' they should be listed there. Since the variables are directly written to the registry they are not available to the calling CMD script. DetectDrive.exe

if you follow the instructions from above when you integrate the single hotfix and then remove the svcpack folder the integration puts the exe and the cat in that folder with the dat file you need to get the info from.

Here are the file names from when we downloaded Windows PE maybe they will help. SW CD Windows PE 2004 WINNT English #1 -2.exe SW CD Windows PE 2004 WINNT English #1 Non-specific.exe

if you want to have it install the way it should install when you use the integrate switch then edit the hfint.dat file, copy the exe and cat file associated with whichever fix you did and away you go. Otherwise you can just do the update via svppack.inf as described elsewhere on the forum.

Just finished testing the previously posted method: (works fine) Though it would be nice if M$ fixed the problem so this f***en around wasn't neccesary.

with the following installed: KB887472 KB887797 KB867282 KB873333 KB873339 KB885250 KB885836 KB886185 KB888113 KB888302 KB890047 KB890175 KB891781 this is what windowsupdates looks like: kb885835 still neede. (@eirogge - maybe its only still needed for the english version)