prathapml Posted November 20, 2004 Share Posted November 20, 2004 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 offECHO undoing the idiotic compressionPAUSEmd expandedexpand *.*_ expandeddel /Q *.*_cd expandedren *.dl_ *.dllren *.tv_ *.tvpren *.sy_ *.sysren *.ex_ *.exeren *.cf_ *.cfgren *.hl_ *.hlpren *.cp_ *.cplren *.xm_ *.xmlmove /Y *.* ..cd ..rd expandedECHO deleting useless setup utilitydel setup.skindel setup.issdel setup.inxdel setup.inidel setup.ibtdel setup.exedel setup.bmpdel layout.bindel engine32.cabdel data2.cabdel data1.cabdel 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. Link to comment Share on other sites More sharing options...
prathapml Posted November 20, 2004 Author Share Posted November 20, 2004 You can actually use this idea for other drivers as well, which use a pattern of *.DL_ (for example) in its files. That way, when you finally compress it, the end result is a smaller archive.ATTENTION:Bashrat the Sneaky, please do not forget to do this method, if your next video driverpack is going to contain nVidia drivers of v66.93 or higher. Link to comment Share on other sites More sharing options...
Lucius Snow Posted November 20, 2004 Share Posted November 20, 2004 Little question kinda off topic ...About nVidia drivers, i'd like to gain some space in the chipset utility. In \Ethernet\NAM, there's a setup.exe which takes 26 MB. I don't know exactly what it is but it doesn't seem to be drivers. Can i remove it and run the setup utility safely ? I have nVidia hardware here to check. Thanks. Link to comment Share on other sites More sharing options...
Kelsenellenelvian Posted November 20, 2004 Share Posted November 20, 2004 What if I want to keep the setup for un-attended install? Just keep the setup stuff right? Link to comment Share on other sites More sharing options...
prathapml Posted November 20, 2004 Author Share Posted November 20, 2004 What if I want to keep the setup for un-attended install? Just keep the setup stuff right?Nope. Dump the setup stuff. That's needed only for a manual install (which too can directly be done thru INF selection if you aren't n00b).Delete the setup stuff, and just continue your normal method (the "OEMpnpDriversPath=" method).@Lucius SnowThat NRM folder can be deleted. That is the configuration folder for the integrated ethernet chip in nForce3-based MoBos (those are 64-bit boards). If you're having an nForce2 board (like me), that folder is positively a waste of space. Link to comment Share on other sites More sharing options...
Bâshrat the Sneaky Posted November 21, 2004 Share Posted November 21, 2004 I'll bookmark this topic, Prathapml! Thanks for the info! Link to comment Share on other sites More sharing options...
Mekrel Posted November 21, 2004 Share Posted November 21, 2004 Woot, thanks Prathapml, works brilliant Link to comment Share on other sites More sharing options...
Shinkei Posted November 22, 2004 Share Posted November 22, 2004 will this install the control panels? Link to comment Share on other sites More sharing options...
Yzöwl Posted November 22, 2004 Share Posted November 22, 2004 I've just tried OCedHrt's inf.exe tool on the 66.93 folder and only get 13 (14 if I add the other inf) files in the folder. This only comes to 9.11 MB (9,560,471 bytes), does anyone know if the list is complete for install or not.NV4_DISP.CATnv4_disp.dl_nv4_disp.infnv4_mini.sy_nv4disp2.infnvcod.dl_nvcpl.dl_nvcpl.hl_nvmctray.dl_nvnt4cpl.dl_nvoglnt.dl_nvsvc32.ex_nvwcplen.hl_nvwddi.dl_The reason I ask is because unfortunately, this was the only driver folder I had, upon which the tool worked, but it is less than half the original size. Link to comment Share on other sites More sharing options...
prathapml Posted November 22, 2004 Author Share Posted November 22, 2004 will this install the control panels?Yes, it will install the nVidia Control Panel, without needing the setup files.the "OEMpnpDriversPath=" method is the one you should use, to get your drivers detected by windows. (details here - http://unattended.msfn.org/xp/drivers.htmHoping that helps....@YzöwlSomething surely wrong there. You must get 42 files remaining after clean-up (all the below files are essential). For your benefit, here's an output of the folder's file names:gfx-driver\---nVidiaFolder PATH listing- advanced.tvp aliagp.sys cad.tvp dcc.tvp default.tvp finance.tvp hpqvdisp.dll keystone.exe modes.txt nv4disp2.inf nv4_disp.cat nv4_disp.dll nv4_disp.inf nv4_mini.sys nvappbar.exe nvapps.xml nvcod.dll nvcpl.dll nvcpl.hlp nvdccapp.cfg NVDisp.nvu nvdspsch.exe nvgfx.dll nvids.cfg nview.dll nviewx.dll nvmctray.dll nvnt4cpl.dll nvoglnt.dll nvshell.dll nvsvc32.exe nvsysrot.dll nvtsext.dll nvtuicpl.cpl nvudisp.exe nvwcplen.hlp nvwddi.dll nvwdmcpl.dll nvwimg.dll nvwsapps.cfg nwiz.exe Readme.txt No subfolders exist Link to comment Share on other sites More sharing options...
Bâshrat the Sneaky Posted November 22, 2004 Share Posted November 22, 2004 I guess you can delete the Readme.txt as well Maybe the Modes.txt too? And very maybe nvapps.xml? Link to comment Share on other sites More sharing options...
Lucius Snow Posted November 22, 2004 Share Posted November 22, 2004 @ prathapml : I'm thinking of using your great tool to integrate the Forceware drivers. But i've been using the international ones. Do you think installing the english US version on a non-english OS wouldn't make troubles ? Thanks. Link to comment Share on other sites More sharing options...
prathapml Posted November 22, 2004 Author Share Posted November 22, 2004 I guess you can delete the Readme.txt as well Yes. But I keep it simply because 2 KB of useful info was good to have. <Modes.txt> and <nvapps.xml> ? No, those are needed files. Deleting them will cause problems in the driver's control panel.@Lucius SnowWell, I haven't created any tool of the sort you say. Its just a batch-file that I posted, so that you'd get an idea of what needs to be done by seeing it. I think the batch-file would work with international driver as well (but I'm not sure, please test and tell me). Even if the batch-file was not working fine with international version, what you can do is to manually do what those commands do, by yourself.You're right - using the US English version of driver, on non-English OS *WILL* give trouble. Link to comment Share on other sites More sharing options...
Lucius Snow Posted November 22, 2004 Share Posted November 22, 2004 @Lucius SnowWell, I haven't created any tool of the sort you say. Its just a batch-file that I posted, so that you'd get an idea of what needs to be done by seeing it. I think the batch-file would work with international driver as well (but I'm not sure, please test and tell me). Even if the batch-file was not working fine with international version, what you can do is to manually do what those commands do, by yourself.You're right - using the US English version of driver, on non-English OS *WILL* give trouble.Alright. I'll post you the results once i test my CD on a PC with a nVidia videocard. Cheers Link to comment Share on other sites More sharing options...
Yzöwl Posted November 22, 2004 Share Posted November 22, 2004 @YzöwlSomething surely wrong there. You must get 42 files remaining after clean-up (all the below files are essential). For your benefit, here's an output of the folder's file names:gfx-driver\---nVidiaFolder PATH listing- advanced.tvp aliagp.sys cad.tvp dcc.tvp default.tvp finance.tvp hpqvdisp.dll keystone.exe modes.txt nv4disp2.inf nv4_disp.cat nv4_disp.dll nv4_disp.inf nv4_mini.sys nvappbar.exe nvapps.xml nvcod.dll nvcpl.dll nvcpl.hlp nvdccapp.cfg NVDisp.nvu nvdspsch.exe nvgfx.dll nvids.cfg nview.dll nviewx.dll nvmctray.dll nvnt4cpl.dll nvoglnt.dll nvshell.dll nvsvc32.exe nvsysrot.dll nvtsext.dll nvtuicpl.cpl nvudisp.exe nvwcplen.hlp nvwddi.dll nvwdmcpl.dll nvwimg.dll nvwsapps.cfg nwiz.exe Readme.txt No subfolders existThanks for the confirmation, unfortunately the tool I tested works, but it doesn't obviously do a thorough enough job.It only checks the [sourceDisksFiles] section of the inf and copies out the files in that section.Looking through the both infs, I have verified that these are the only files mentionedNV4_DISP.CATnv4_disp.dllnv4_mini.sysnvcod.dllnvcpl.dllnvcpl.hlpnvmctray.dllnvnt4cpl.dllnvoglnt.dllnvsvc32.exenvwcplen.hlpnvwddi.dllWhere is the tool going wrong? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now