Alanoll

umm... to get a file from .dl_ or any .**_ type expand file.dl_ file.dll at a command prompt

wasn't indeo removed in SP1? or was it added? I remember one install I did, I forget if it was SP1, or RTM, but i had to find the indeo codecs. But one had them, the other didn't. As far as I remember anyway

The path only need to point to the directory where the INF file is located. Subfolders can be used, but the INF file must have the paths in it. If the drivers DON'T overwrite eachother, it is safe to put them all in one folder, instead of seperate folders. WindowsXP finds the best match when it searches. Also, if you use the 001_Chipset naming scheme, do keep in mine that you don't need Chipset, just the number. the Chipset is just for identification later on. Also keep in mind you don't have to give a path to each folder PnPDrvrs\1qwc68ww;PnPDrvrs\1qwc68ww\WIN2K;PnPDrvrs\1qwc68ww\WIN98;PnPDrvrs\1qwc68ww\WINNT;PnPDrvrs\1qwc68ww\WINNT\11AB;PnPDrvrs\1qwc68ww\WINNT\11ABG;PnPDrvrs\1qwc68ww\WINXP I'm guessing this is all one drive. You only need the path to the directory that has the driver you wish to use. In this case perhaps the one ending in WinXP?

Blast that SP2. Breaks all of Wraith's programs so far.

I wonder what would be trying to use it. I know you can unregister the file with regsvr32 /u iac25_32.ax But that won't unload it. Maybe do some experimenting with trying to find the program using it? What happens when you click "Retry" same error, or does it continue? (if it continues, maybe a SLEEP 5 is in order)

HKLM\Software\Microsoft\CurrentVersion\Runonce ? I'm not sure about this. But without actually looking, that's my guess. Or something similar. Or a self destroying batch file in the "StartUp" folder of the startmenu that delete's itself.

not all CDs contain it though. Even SP1 CDs

@Dark Cobra Now if only you had seen the number of times this particular subject has been brought up. I'm quite new at this, so forgive me if I'm slightly perturbed at repeated posts. When I was a normal user, I've always just wanted to delete the post, or give them a link and close it. But did I close this thread, I think not. and as for this Like said before, $OEM$ can not be scripted. If you wanted to change the process. BUT seeing as you've dissed me, I'm not as inclined to help all that much anymore. The ONLY way that I can think of at the moment, is to use Windows PE, and have a custom script that copies the files from CD to HDD from both CDs, and THEN starts the install from the new source. It would be like starting from a network share. Though thinking again, it doesn't have to be Windows PE, maybe DOS? As for helping, it's hard to help when you're not too specific. It's also hard to help, when people only reply (not particularly in this thread) "It doesn't work, Help." but they don't say what worked. Give any frame of reference or even begin to describe the problem. I most admit, I can be quite sarcastic at times, but anytime I say I'm going to close a thread, it RARELY happens. For this very reason, each thread is slightly different, and the user may explain themselves better in a future post. The ONLY times i have closed a thread is when the thread broke forum rules, in which case I was in my bounds. Oh, and I'm sorry this forum is nothing like neow1n. But hey, to each their own right? OT: I'll be going through when I get some time, adding more links to the "Threads of Interest". If anyone has suggestions, please post a reply in that thread, or PM me. They'll be added. And at the suggestion of the XtremeMac, I've deleted the posts that don't have any useful information. It's said when a user of the board, thinks so lowly of the mods that devote time to the board, and the mod tries to add a little humor (albeit bad humor) to lighten the mood. Next time, I'll be sure to do it in a thread with people I know won't get offended.

specify the iss file using -f1. setup.exe -s -f1"%PATHTOFILE%\setup.iss" also, If using a virtual machien, it won't instlal anyways as the installation requires there be a card present, or it will cancel out. And if you're installing from CD, you may want to try and specify the location to save a log file, as it might cancel out by that as well..use -f2 to use it. -f2"%systemdrive%\log.log"

sounds like you just created a brand new image file, instead of READING the first disk, THEN resizing it under options to 2.88 mbs, then adding the second. If you did follow the site exactly, and it's still not working.... I remember somewhere in WinImage the option of configuring the bootsector. Maybe find something helpful there?

open up the HIVESFT.INF file inside the I386 folder on that CD with Notepad. there should be a line right up at the top saying something like DriverVer=07/01/2001,5.1.2600.1106 if it has that, then yes it does have SP1. If the last 4 digits are higher, it's some version of SP2. If it's 0, then it does not include any servicepack.

what errors appear when you do it?

i personally don't like the FILESCD idea. It's just one more thing to debug when something goes wrong. If all it's to do is to copy over the files, then you can do it yourself. Then press the Make ISO button.

some people just never search properly. ATI Catalyst drivers use a InstallShield setup routine. Follow the instructions here http://unattended.msfn.org/xp/applications/installshield.htm If you wish to just have the drivers and non of the additonal stuff like smartgart or the control panel, you may prefer using the OEMPnPDriversPath method http://unattended.msfn.org/xp/drivers.htm

like this: http://www.msfn.org/board/index.php?showtopic=8381

in case you failed to noticed, but EVERYTIME i've posted, I've given you alink to a post that could help you. It's in the signature. (below this)

did you happen to use any type of "removing of components" program?

@paulrobert_a i sure hope winnt32.sif isn't the actual filename, and that was a typo when you posted. Should be called winnt.sif also, it goes in the BOOT folder your using, not the I386 folder.

define implement? think of it as a commandline tool, only graphical

uh.... wow, talk about saying you did somethign TOTALLY opposite of what I said to do. Even if your folders aren't in caps, type in the HEX editor in caps.

i see wraith was getting annoyed with it as well. @mukeshnuna we dun lik por enlish. I not unter stand u wen u typ lik dis.

old news here's another thread on the topic, with a few more commands you may find useful. http://www.msfn.org/board/index.php?showto...lors++in++batch as a side note, I find XPlode easier then batch files. both are pretty much the same (in arguments and whatnot).

you're doing something wrong. If XPlode even starts, then it will create the LOG, IF you copied what I sent earlier. And your paths are correct.

whatever folder I386 is in, $OEM$ goes along side it. As for the fullunattend related question....use ProvideDefault. All the options are in the ref.chm file in deploy.cab and judging form the fact taht you ahve XP-SS i'm going to guess you're using a guide not from MSFN. Perhaps TechHints? ::Edit Blast, [bM]Crusher beat me to it.....

BOOT is the CDSHell folder. CDSHell is the boot menu. Most people do one OS at a time, and add the entry to the boot menu. Longhorn requires you to change the BOOT folder for CDSHell to CDSH. It's easier then changing all the entries in Longhorn from BOOT to whatever.