homiebrah

Not sure, but I would like to know where the updated ref.chm file came from.

HighMAT is the only one that shows as needing to be installed. No beta updates.

Only one is really an update (HighMAT). The other two are nice to have, with .NET being the bigger of the two in terms of usefulness.

Get modfype here: http://unattended.msfn.org/xp/hacked_files.htm Get uxtheme.dll here: http://vortex2050.dyndns.org:8080/reposito...atches/Uxtheme/

The winnt.sif entry in the Unattended Guide does work. However, the IEPopup does not. At least in my case.

Gawd, this thread sounds like it belongs over on ieXbeta.

If you've installed DX 9.0c, or plan to through SVCPACK.INF for later, then take 839643 off the list. It is not required with 9.0c.

Majority of the questions come from the XP side, is why. However, my second sentence applies to 2K as well. 9.0c will not require the DX hotfix.

I get the computer name problem when running it in VMWare with bridged networking. It detects the name already in use and creates a new one.

SP2 will incorporate 9.0c, so once it goes out for general release, there will be need to get it into XPCREATE. Nor the associated hotfixes for it. Should be sometime this coming week for release.

Won't need all this crap with SP2 out now.

I've had problems with the ASMS folder caused by a bad image/burn. Fix it by re-imaging or reburning.

Well, you could always run a batch file to run the next 10, then shutdown.exe, then another batch file and so on. I.E.... RunOnceEx.cmd calls 10 files. Next to last line calls for RunOnceEx2.cmd to run. Last line calls for shutdown.exe to run.

Another link in case anyone needs the current, or passed ones...

Another satisfied MSFN customer served.

Amazing how the link opens up to MS' home page...

Yup, mine generates an error lin Line 47 of winnt.sif in both VMWare and live. The ref.chm that comes with SP2 does not even mention it, nor the Windows Firewall.

Try this: http://www.kbalertz.com/Feedback_295823.aspx

If you're not sure, put a PAUSE statement in after each install and test it that way.

Unless a modified uxtheme.dl_ is being used. It will generate an entry in the setuperr.log.

Check these out for your problem. Might try some punctuation in the future, as your problem is one continuous run... http://www.google.com/search?num=100&hl=en...ted&btnG=Search

Take the start command out. Should look like this: "%systemdrive%\Windows\System32\AppLog\RunOnceEx.cmd" Make sure that the file is in the location specified, otherwise it will error out.

http://gosh.msfnhosting.com/infs.htm

You won't be able to slip service packs in NT. That option wasn't available until Windows 2000 was released. You might checking the TechNet security page on Microsoft's site for a complete list of hoyfixes. Or, you can use the MSBA to tell you what you need.

If the machine is new, one should have come with it. Recovery CDs are great, but not needed if you have access to an OS CD somewhere.