RyanVM

It'd probably be easier to just remove their entries from txtsetup.sif. Yes, they're Indeo Codec files. For what it's worth, most 3rd party codec packs come with that anyway.

No, that's the point. txtsetup.sif references them but they AREN'T there. It's up to MS to fix the bug and they're working on it.

I think you're right. And I also think we'll find out if that's truly the case very soon

One costs more than the other . Seriously, cost is the only difference. And as is the case for most if not all OEM software, it must be bought with hardware (of course, many online resellers use very liberal definitions of "hardware" to sell it by packaging it with a $0.05 screw or something).

Can you give me a link to the product page and/or drivers?

I haven't figured out how to run Drivers.exe from the CD yet, though I think Alanoll's method might be needed. For now, I just have it in the $OEM$\$1 folder to run from the hard drive called as ".\Drivers.exe".

That was refuted by MS the day after that article came out. It's untrue.

Look in the unattended forum at the nLite thread. If you want to just slipstream it, follow the same procedure as for slipstreaming SP1 (there's plenty of guides only a google search away).

That sounds right. It was so long ago (last fall) I've honestly forgotten how I did it.

Haha. I recently converted my batch files over to run the stuff directly from the CD. Working like a charm so far and it certainly makes textmode setup go faster!

I'll take a look into it. It's possible I need to add some PnPIDs.

I'm an expert in drivers now . One of the reasons I like this place so much (apart from the wealth of information contained) is the fact that the majority of the people here have their egos in check. It really does make things better around here (and the moderators do a good job of keeping things in order as well). If I can actually get the Creative drivers to work, I'll probably start a thread about it in the Drivers forum (and I'll probably let Bashrat know too since he's working on that sound drivers package).

I think read about it here. Do a seach of the forums and see what turns up.

You need to specify the directory to extract to in the SFX settings. Look at the bottom of the third page of the pinned "Solved..." thread by Alanoll in the Drivers forum. I posted all the info for how to create the SFX archive which works for me.

I'm looking forward to seeing what RC2 contains. EDIT: I just checked my bug report status. It's a known issue with the Indeo Codec files and the status on it is fixed, so we shall see what RC2 brings .

You're calling it wrong. Call it with the same syntax as cmdlines.txt.

That actually goes to confirm my suspicion. I can tell you for fact that the newer builds of SP2 are the only ones to exhibit this behavior (2096 and 2120 - 2055 and 2080 didn't). I can also tell you for fact that for sure build 2096 (RC1) does NOT have those files in it (as in, I extracted the exe and searched for them - including within the CAB files). My guess is either they meant to include them (hence the txtsetup.sif references to them) and somehow the files got lost from the distribution some time between builds 2080 and 2096, or they meant to remove them (hence the missing files) but forgot to remove their corresponding txtsetup.sif entries upon doing so. The latter seems more plausible to me since I don't know how files would just "disappear" from a release.

I'm not sure exactly what you're asking - do you want to dual boot with Win98SE? I'm not sure how to set that up with an unattended install. If you simply want to be able to format the drive (I'm assuming want to go from FAT32 to NTFS), the only way is to delete the partition you want to install to and recreate it. You'll then be given the option of what file system you want to format it with.

I think most of it applies the same way (key word being think), but I know there are some differences (hence why most automated scripts/programs don't work correctly with Win2K).

So basically you're overridding it's detection mechanism and forcing it to install the driver for that monitor (which you know to be correct in that circumstance). However, you still run into the aformentioned issue if you install XP on another computer with a different monitor because it's going to install that monitor on their computer as well and could potentially end up putting invalid displays settings on their computer.

I stand corrected then . Thanks for the heads up.

It sounds to me like the ISO was made with incorrect parameters. An easy to make a guaranteed correct ISO is to use the MSFN batch file for WinXP. You can get it over at http://unattended.msfn.org/

The easy way to discover the registry setting for something is to use a "snapshot" program like Advanced Registry Tracer, which will allow you to take before and after shots of your registry and compare the two for differences (in other words, take a shot of the registry, make the setting change that you want to discover, take another shot, then have it compare the two for the difference). And as Bâshrat pointed out, some of the settings you want to change can be configured in your winnt.sif file rather than through registry entries.

Do a Google search for the Microsoft Baseline Security Analyzer (MBSA). That program will tell you if you're missing any updates. Along with that, you could always run WindowsUpdate and see if it's recommending you install anything.

It would be helpful if you'd tell us what file you were having errors in. Along with that (since it's probably winnt.sif), copy/paste your winnt.sif here so we can see it. It's impossible to give help if you don't give us any information. We're not mind readers.