prathapml

This time, nvidia has really gone idiotic. They have compressed the files that are part of the driver. This is useful if you keep the drivers on HDD without further compressing it. But when you compress your entire driver set (which might include nForce, ATi, intel, etc drivers) once again, you see that this foolishness by nvidia increases your driver archive's total size by 5 MB. The reason is, that the nVidia files ended up having double compression. This is how I fixed it: 1. Download v66.93 drivers (US English) from nVidia driver download. 2. Extract it into a folder. 3. Either observe what the below code does, and do it yourself (recommended) --OR-- a. copy/paste the below code into notepad. TITLE nVidia 66.93 driver cleanup @echo off ECHO undoing the idiotic compression PAUSE md expanded expand *.*_ expanded del /Q *.*_ cd expanded ren *.dl_ *.dll ren *.tv_ *.tvp ren *.sy_ *.sys ren *.ex_ *.exe ren *.cf_ *.cfg ren *.hl_ *.hlp ren *.cp_ *.cpl ren *.xm_ *.xml move /Y *.* .. cd .. rd expanded ECHO deleting useless setup utility del setup.skin del setup.iss del setup.inx del setup.ini del setup.ibt del setup.exe del setup.bmp del layout.bin del engine32.cab del data2.cab del data1.cab del data1.hdrb. Save in the folder where you extracted the driver, as "reduce-size.cmd". c. Double-click on it to run it. d. I can only confirm that the above code will run properly on winxp (you might need to modify the code for other OSes). 4. The files that are Setup files will be deleted by using above code (because you know that you will use the OEMpnpDriversPath method which is satisfied enough with the INFs and driver files). 5. At the end of the process, you should have a total of 42 files occupying 24.5 MB (none of them compressed). 6. Now compress the same thing (as a collective set of drivers) and you'll be surprised to see total size reduced! Since I did the above for myself, I thought more people would be interested in the same. So enjoy! Please reply in the thread, if you found this useful.

source New WinXP enabled version of Avalon up on MSDN The Avalon team has dropped a new Customer Technology Preview (CTP) release that is now enabled to run on XP and above. This version runs on Whidbey Beta 2 (build 2.0.40607.51), which is older than the most recent Whidbey CTP (released in October). Those two versions of Whidbey probably won't mix well, so I'd recommend installing on your Beta 2 machine. The Avalon team has been working really hard to get this build going, congrats to them!

source Microsoft gives developers a glimpse of Avalon Although the next version of Windows is still about two years from release, Microsoft on Friday offered developers an early look at the new graphics engine that will accompany it. The Redmond, Wash.-based software powerhouse released what it calls a "community technology preview" of the Avalon presentation engine for Windows. It's not a full beta, or test, version, but rather an incomplete set of code that lets developers test certain features and pass along their thoughts to Microsoft. "It's basically a build that has a couple new features that we want to test out with customers," said John Montgomery, a director in Microsoft's developer division. "This is just our way of getting feedback." Avalon was originally envisioned as a core feature of Longhorn, the next version of Windows. It will still be a part of that operating system, but it will also be made available as an add-on for users of Windows XP and Windows Server 2003. The main purpose of the new technology preview is to test Microsoft's ability to bring Avalon to its older operating systems. Microsoft has done community previews in the past, typically with developer-centered programs such as Visual Studio. The company created one earlier this year for its "Whitehorse" modeling tools. Avalon is a key part of Windows' future, but it is something the average computer user will never touch directly. Instead, it's an improved method of dealing with graphics, designed to let developers write snazzier-looking applications. So far, Microsoft hopes it will be able to bring most of the features envisioned for Avalon onto its older operating systems, Montgomery said. The main difference is that newer graphics drivers in Longhorn allow for better performance and newer hardware. With Windows XP or Windows Server 2003, users might see slower performance, fewer shades of gray or less 3D animation, Montgomery said. But, he said, developers wanted the support for older operating systems because it means they can write programs for Avalon that can be used by existing PCs, as opposed to only the machines that run Longhorn. "The goal is give developers a consistent set of APIs," or application programming interfaces, Montgomery said. The code Microsoft is releasing Friday is pretty rough, Montgomery said. Its release is limited to developers who subscribe to the Microsoft Developer Network, and the company warns customers not to use it even on a primary development computer, with there being every likelihood of bugs and a pretty good chance developers will want to reinstall their system once they're done using the Avalon preview. A beta of Avalon is slated for next summer, along with the first beta of Longhorn. Final versions of Longhorn and Avalon are expected in the second half of 2006.

source Microsoft on Friday released a new preview of the presentation subsystem of its upcoming Longhorn version of Windows. The Redmond, Wash., software giant released a CTP (community technology preview) of Avalon, the presentation subsystem of Longhorn, to gauge developer opinion on the technology's applicability on Windows XP and Windows Server 2003, said John Montgomery, director of marketing in Microsoft's developer division. The company released the technology to the MSDN (Microsoft Developer Network), Montgomery said. Microsoft Corp. initially said Avalon would be available only on Longhorn, but in September the company said it would be available for Windows Server 2003 and Windows XP—but not until 2006. Click here to read about Microsoft sharpening its software factory vision. Of the new Avalon CTP, Montgomery said: "This is a build we want to get into customers' hands. We wanted to get feedback on two key areas: what is Avalon going to be like on XP and Windows Server 2003." In addition, Montgomery said that when Microsoft announced its plans to put Avalon and the Indigo communications subsystem on the two additional platforms, the company also placed Avalon, Indigo and Longhorn on different build schedules. Last month, Microsoft released CTPs for SQL Server 2005 and for the upcoming Microsoft framework, and tools for building customized, domain-specific language designers. Avalon features XAML (Extensible Application Markup Language), an XML-based language developed by Microsoft for building presentation-layer and user-interface technology.

Check if this does the job: %windir%\System32\RunDll32.exe advpack.dll,LaunchINFSection %windir%\INF\msnmsn.inf,msnexplr.Uninstall

If its Windows XP (with SP1 or higher) or Windows 2000 (SP3 or higher) that you're talking about, you have a glut of options: 1. Use nLite (its forum is right here on MSFN) to rip IE out from the install source itself. So that you never get to see its ugly face (even to uninstall it) again. 2. Use the "iexplore=off" component value in winnt.sif (does the same as below, but unattended) 3. This one's for an existing installation, Go to: Control Panel >> Add/Remove Programs >> Set Program Access and Defaults (this one will only just remove shortcuts to it, IE will still stay) 4. XPlite can remove IE from an existing installation (not perfect, its risky) 5. Don't care about the other possibilities.

@Yzowl I changed the INFs that you posted, some more. Posted the results in this topic: link

Thanks to RyanVM and Yzöwl, finally here's a set of INFs for all 3 major (non-IE) browsers. (Maxthon, Mozilla and Opera) It allows to remember path and put entries in the start menu (like how the normal installer does). You just need to RAR/SFX the installed folder of these browsers, and silently extract them during windows silent install. You need to put these browsers to respectively mentioned folders: Maxthon (v1.1.067) at %ProgramFiles%\Maxthon Opera (v7.60p3) at %ProgramFiles%\Opera75 Firefox (v1.0) at %ProgramFiles%\Mozilla\Firefox Thunderbird (v0.9) at %ProgramFiles%\Mozilla\Thunderbird The shortcuts (.lnk) at %AllUsersProfile%\Start Menu\Programs Then, you can just directly have these INFs run thru batch-files, with this command: rundll32 setupapi,InstallHinfSection DefaultInstall 128 %systemdrive%\install\browsers\FILE_NAME_HERE.infThese INFs give details to the registry for being able to set them as Browser clients. Then, in your registry tweaks, you need to choose which of these you want as default browser/mail-client. Example is below: ;Set the Start Menu sticky apps [HKEY_CURRENT_USER\Software\Clients\mail] @="Mozilla Thunderbird" ;---- AND now for browser [HKEY_CURRENT_USER\Software\Clients\StartMenuInternet] @="Opera.exe" --OR-- @="Maxthon.exe" --OR-- @="firefox.exe" The intention behind this topic, is to have the desired browser/mail-client set as default in the start menu (top-left section) without having to manually do anything after install. browser_INF.zip

ha ha.... MS has always made crap statements. I'm using oobeinfo.ini with no problems. I've posted in detail about it here: link to topic. We can't really see what could be wrong elsewhere with your CD - can only just say our own experiences and then hope that you'd be willing to spend enough time to do it for your purpose as well.

I really can only tell you to search for the main thread that deals with oobeinfo.ini - and follow what's there. Maybe there was a slight user-error. That thread will tell you all you need to know about it.

Thanks. My god... such a quick response! Do you ever rest?

A lot of strange things happen. As for hyunkeru, I think there's a nero reg-tweak to *FORCE* display all speeds (from min. to max. supported by burner). Try searching.

That one's another good way too. But I don't use it since I hate floppies (they don't last for more that 5 days) and want them to die!

mmmm....... (I'm not complaining, just notifying what needed to be changed) some comments were needed, and then the protocols section was located in the wrong place (in both the 1`st and 2nd INF). Here's the corrected version. And also, the .reg below needs to be added to the INF! MOZ-Missed out.reg: (please add these keys as well, to the corrected INF that I've attached.) Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\Mozilla Thunderbird\InstallInfo] "IconsVisible"=dword:00000000 "ReinstallCommand"="\"C:\\Program Files\\Mozilla\\Thunderbird\\thunderbird.exe\" -silent -nosplash -setDefaultMail"Thanks for your efforts - this one's gotta be the simplest way to install Moz ff/tb. And then, Could you make an INF of the Opera code that I've posted above as well? mozilla.inf

Yeah, that's a good sign. Google's POP access I'm using - but Yahoo! too? A good reason for yahoo users to not move.

I suggest you specify the username in the file. Yes you won't be able to change it - but I say, do it so you can understand how it works. At the next step, you can make the username change-able. Yes, it is a long climb to do what you're trying - but its not too difficult. Just *START* at step 1, you will reach step 10 after some time. If you refuse to start walking, you'll never reach where you want to go!

I don't think its possible. I just do the standard "export entire folder" then delete the keys I don't need.

Well, first use the oobeinfo.ini method in the way I said (the simpler direct way, 5 posts above). Once you start to do it, you'll understand it. You made a user-controlled winnt.sif, right? You need to execute the batch-file at whatever time you are having that user-controlled winnt.sif applied. Execute it through cmdlines. And you need to create the batch-file yourself - to get the user to input a variable (you know command-line scripting?)

There's an INF in the VALUEADD folder, which you need to install to get NetBEUI protocol, unattended. And as for restricting sites, you could use windows firewall configuration. (edit netfw.inf in I386) Even better is to install ZoneAlarm or some such firewall at your network's gateway, and restrict all sites except for specified ones.

Yes, now its clearer. I still say you can use oobeinfo.ini. In this case, don't have the oobeinfo.ini existing already - you should have it created dynamically. If you don't want auto-logon, you need to create atleast 2 user accounts. So create a batch-file that asks for user to input user-name, and then that username should be taken as %useradd% variable. So then, consider that %useradd% is now equal to the word Adiel. So then continue the batch-file with these commands: echo [UserInfo] >> %systemroot%\System32\OOBE\oobeinfo.ini echo Identity001="any_other_name" >> %systemroot%\System32\OOBE\oobeinfo.ini echo Identity002="%useradd%" >> %systemroot%\System32\OOBE\oobeinfo.ini(remember, until the above commands, the oobeinfo.ini file should not already exist) And then, this (the above commands/batch-files) should be executed before first-boot. That's because the OOBE is executed at first-boot. Maybe you can execute the commands at T-12 (or even before that thru WinPE or whatever).

@MCT No, that's not it. @hyunkeru There's some media that have upper/lower limits to being burned. For example, my 24x CD-RW media refuses to be written-to at any speed slower than 16x. So similarly, maybe your media can't go below 4x. Try a different brand/box of DVD-Rs.

Well, I directly block out unwanted sites, by "restrict"ing them from the HOSTS file. Go here for an updated list: http://www.mvps.org/winhelp2002/

Well, I guess paid user-support centres are present, if you need someone to "monitor" your calls. Otherwise, this is a forum, where other people like you visit - and if they know an answer to what you're asking, they reply. And for them to reply, you need to make it worth their while: Make your post easy to understand, be polite, and do not ask before searching if it has already been answered.

If you're trying to run msconfig on win2k - no, it won't run because there's no msconfig on windows 2000. But if its WinXP you're trying this on, maybe msconfig.exe got deleted for some reason. You can de-compress it and restore it from the install CD.

He means to say, if you got a G2 (gnutella2) link, you'd be in heavenly speeds (or very lucky or something of the sort, I guess). Yup, shareaza rules!