Ver Greeneyes

Possibly the same place where IE6 got its flash dll. Your best bets would be RyanVM's update pack (which includes Flash) or Shark's switchless Flash installer for IE. Edit: after a quick search, try here: C:\WINDOWS\system32\Macromed\Flash If it isn't there, the file you want is an ocx file, not a dll, and there's a Flash Player Helper executable as well.

As far as I can see from your posts, both the setting and the tweak have to do with the -library-, as you noted. Adding files to the playlist rather then playing them is just the way WMP works I think, don't know if there's a setting for it (but the setting you talked about isn't it)

Not a solution (and rather painstaking, I'd imagine), but maybe you could have a look to see what RyanVM does to install it in his Update Pack? (or you could use the update pack, of course) The installation procedure he uses was recently revised, so apparently installing it for IE -is- a pain.

Hi, I didn't have any luck getting your installer to work (possibly because of too much nLiting) so after finally managing to download it (please host it elsewhere, it took like 10 tries before I got an uncorrupted file!) I modified it to use an INF.. seems to work fine now. If you're interested, the download is below. I compressed it with Winrar, using these switches: Setup=shockwave_installer.msi /qn Setup=rundll32.exe advpack.dll,LaunchINFSection Install.inf,DefaultInstall TempMode Silent=1 Overwrite=1 Get it here. MD5: DA5C4B52F6A73E3CF37558116372D3C1

A reboot is needed between installing 1.1 and 3.0 for whatever reason.. so install 1.1 from SVCPack and 3.0 from RunOnceEx.

You may want to have a look at this topic as well.

No, you cannot slipstream them; it messes up the windows setup. Integrate the switchless installers RogueSpear made with nLite. (see my previous post for a link)

If the optical disc drive you're using to install windows from can read the format, yes. To simplify that, all reasonably new drives should be able to read atleast +/-R and +/-RW.

Try here for several of those. You have to register to download them, but that's free. The website might go down soon, so get 'm while they're there..

Apparently. That's from the aspi32.pdf included with the original installer. For the rest, all I know is that the Adaptec ASPI layer is as close to 'the standard' as you can get. I don't know how it compares to Nero's.

Speaking of the Image Resizer, the latest version is 1.0.11, not 1.0.9. You can find this version here.

Boooggy, your download page still lists the version as 8.313 which might lead to some confusion Thanks for the addon!

Aha, I don't know what those are so I can safely remove it

Well I don't know about MediaMonkey, but I've never had any trouble running OOo, and I remove those components entirely.

Did you see my posting?In it I used two methods. Does the first look familiar at all? Um.. oops?

The previous version of Ryan's pack, which should be based on the October release, should work on Windows 2000 as well. So far as I know these updates are just for managed code, which is (as I understand it) specifically updated SDK-related code that certain (very) new games use. However, since there have been so many updates and fixes to DirectX, it seems that you can completely integrate DirectX 9.0c with this update. Either that or it's easier to make the update with the whole thing and that's just what Ryan released. Either way, that's probably why your version number didn't change. About the size difference, try extracting the two versions. I don't have them here so I can't test it, but I read over at RyanVM's forum that 7-zip does a phenominal job of compressing this particular pack. It's quite possible that it has more difficulty with the newer version. Edit: By the way, cheers on solving the 55% hang problem ^_^

Here's another method that's a bit more versatile because it allows you to place a shortcut anywhere. Unfortunately it's less well documented. Below I'll give the simplest possible example for using this method; this will create a shortcut called Shortcut to the file "test.exe" located in %SYSTEMDRIVE%\test and will place this shortcut in %SYSTEMDRIVE%\shortcut. [Version] Signature = $Windows NT$ [DefaultInstall] UpdateInis = Shortcut [Shortcut] setup.ini,progman.groups,,Location=%24%\shortcut setup.ini,Location,,"Shortcut,%24%\test\test.exe" Here %24% equals %SYSTEMDRIVE% (but beware: some inf environment variables do not work at all times during windows setup; for instance 16384 which is supposed to point to the Desktop -does not- work when you integrate an inf into your Windows CD). Now, the first step is obviously the UpdateInis section in DefaultInstall; but if you could work with the above methods I won't need to explain that. Secondly, we get to the syntax for the UpdateInis section. There are some things to note about this but here are the basics: First comes the line setup.ini,progman.groups,,Location=%24%\shortcut which always has the syntax setup.ini,progman.groups,,[variable name]=[location of the folder where the shortcut is to be placed] Simple, right? Then the next line setup.ini,Location,,"Shortcut,%24%\test\test.exe" has the syntax setup.ini,[variable name],,[shortcut creation syntax surrounded by quotes] The syntax for shortcut creation is a bit more complicated, but here it is: [LinkTitle],[Target],[icon_file],[icon_index],[Profile],[start In],[Description] Of those, I only used the first two above, and for your average shortcuts that's enough. Okay, so, fine. We can create shortcuts anywhere, huzzah. But wait, there's a catch. What if we have directories (or file names, for that matter) which contain spaces? "Just use quotes", you might think, but unfortunately it's not that simple. In fact I can't tell you the exact rules, but I've found experimentally that for the simplest form, using only the first two parts of the syntax, you need to surround the target with -six-, that's 6, pairs of double quotes, or it will not work. Note that this is not true for the first line in the inf, as my next example will show. If I wanted to make a quicklaunch shortcut called "Somewhat more compolicated" to a file in my My Documents folder called "Somewhat more complicated.exe", here's how to do it. [Version] Signature = $Windows NT$ [DefaultInstall] UpdateInis = Shortcut [Shortcut] setup.ini,progman.groups,,QLaunch=%16410%\Microsoft\Internet Explorer\Quick Launch setup.ini,QLaunch,,"Somewhat more complicated,""""""%53%\My Documents\Somewhat more complicated.exe""""""" Note the seven quotes at the end; this is because I'm not using the other sections so I'm ending the syntax there. Of course there's no real point in using this method for a quicklaunch shortcut (though I think it's easier after you get used to it) except that it seems to create shortcuts that only contain the needed information, so they're usually smaller Hope this helps, below are some links with more info: http://www.microsoft.com/technet/prodtechn...p.mspx?mfr=true http://www.microsoft.com/technet/prodtechn...f.mspx?mfr=true http://www.robvanderwoude.com/shortcutinf.html

A complete rewrite seems a bit much nLite could simply look in the log and if any errors are found write them to some file; the last session.ini could work since nLite has the syntax for that anyway.

Hey guys, I just noticed this post. I don't have time to check it out right now, but if you could confirm that this is what's going on nuhi should be able to fix it easily enough..

Sorry, but I completely started from scratch with 1.3 so that can't be it...

It's just that I noticed the unattended section has changed a bit in nLite 1.3.. And I set a workgroup too as you can see. It's a long shot but.. I've got everything working now with 1.2.1 and I have to get some work done; I'll get back to testing tomorrow and see if I can nail this down.

I just finished an nLite with 1.2.1 with the exact same settings (but none of the new components removed, of course) and it works fine. If MelTraX above me is right, this is a general problem that 1.3 is having on our systems and not related to us removing the new components. Edit: MelTraX, I'm wondering about something.. Are you assigning your computer to a specific workgroup?

Good to hear my idea worked - sorry I can't really help you beyond that, as I said I don't have Windows 2k... I'll keep an eye on this topic though, hope you figure it out!

Nope, I just tried adding myself as a new user (besides the Administrator account) and it still fails to log me on.. This must have something to do with a component I'm removing, but I don't know what. Can you guys check it out for me?

If the PM wasn't too private, let us know what you find