Antonino

well, attaboy jfx, I can only confirm ur advice has proven right!!! could u think of some appx that still want deleting or would that be preposterous? the only caveat I can think of, just if I wanna be a stickler, is that the space warning sign still appears (even with the compact config, unless u give it some 5gb, but that is just a detail compared to my most recent discovery. Keep it up and brief us all the more often!

Sorry JFX, I now know what u mean, I think I have found both options that u mentioned, and it is a pity I haven't implemented them so far. better late than never. Wonderful advice anyway, i figure, in a bit to confirm.

Tx 4 ur reply. Pls tell me how i can practically enable these features that seem very useful. As this is the 1st time i have learned of them, my post envisaged that one installs and then points to an lzx.bat. if u tell me how, from now on, i can use the tool to do these things, i would pretty much appreciate it. Tx in advance.

the feature u were asking about is not inside the tool, sorry for not being any clearer, my fault, it is a .bat that I have somewhere on my hd and I used this slot only to make the tool point to it on a post-install basis. as for the reg file u r asking about now, there are plenty of them in the miniwin section of the tool, these are definitely integrated in the tool, along with a lot of .txt files which list all things to take out and can be found in the remove subfolder. u would be better off perusing each of them lest u should take out things that u would have needed. I also suggest that u should write a .txt of ur own listing all files that u want in. u can name the file whatever u like (mine is my software.txt). it contains all paths to files u want in. all paths are precedee by ! , which will have the highest processing priority (the file on the path will not be deleted if the path is preceded by !, which acts as a ; and has the highest priority. I keep this kind of file mainly to prevent the tool from deleting the files listed. as long as a txt file is in the remove directory and contains paths to files, it will be processed. so, u will find 3 types of beginning of lines in the txt scripts: 1. \blablabla\ ... 2. ;\blablabla\... 3. !\blablabla\... if the same file is concerned it will be deleted as 1 dictates, and 2 can do nothing, unless the tool finds a 3, which will be looking for at the outset to be sure. without 3, the file would be lost and gone by operation 1, and 2 can do nothing to prevent the deletion. if operation 2 is ahead of operation 1, the files will not be deleted; to be on the safest side, u put type 3 instructions in ur txt and those files will be safe. if something is still unclear to u, do not hesitate to ask any further.

the i:\ in the above example is of course the letter indicating the drive the system is being installed to. i do not know which 1 urs is in ur specific case.

yes, there is one, provided ur disk or vhd has enough space for the initial installation proper, as it is impossible to compact while installing. if the space is insufficient, then winntsetup will warn you that the installation cannot proceed. if u do not get any warning when u click the setup button, then u can proceed to insert an lzx universal command (compact /c /s /a /i /exe:lzx "i:\*") in the last slot of the setup window to run on an ex-post-facto basis, as the compacting procedure can only take place after the system is installed. to be on the safe side I suggest u should have at least 10gb free to start it all, then u can install and compact and if u r good enough to reduce the system, u can reach as little as 1 to 1.5gb used disk space. with 400megs slack space, u must be good to go.

getting back to the driverstore repository, one can also make the nvidia driver subfolder all the smaller with a regfile that will also forceinstall every new version without using any further space than a few hundred megs. I have found out that for graphic acceleration and blender (and even nvidia encoding) to work one does not need all that plethora of files and folders that would amount to 1.70gb (required by the installation of the driverpack only). of course, it is a force-install procedure, so u cannot (yet, at least) expect the driver to appear as installed, but with a little manual replacement of the crucial files in the driverstore repository and windows\system32 subfolders the new version is active de facto. the regfile must be made from a system where the new version is conventionally installed, though, and all this should be carried out on a per-version basis. the most important gains of it all, at least for the time being, are low disk space usage and a much neater registry when nvidia successive installations that have accumulated through the months or years are gotten rid of in seconds. we hope that this empiricist approach that has been the only one possible so far will pave the way for a more orthodox automation of the procedure. pls feel free to ask how it is done.

so the problem is no problem, if I am not mistaken - a problem-less problem.

sorry if I butt in, but ...., if it all can't be done in one move, can u not first integrate and then miniwin? me, I first integrate, then customize the whole install to suit my needs and liking, and then, when I am over with I miniwin. I think it is safer this way, insomuch as we have good control and command of what we r doing.

anybody interested in a further reduction of the driverstore repository?

wow!!! thank u ever so much, jfx.

sorry to butt in, but i am worndering what the above scripts r for. i would use them if they were worth my while doing so.

caveat for those of u who use drivergenius. here below is a list of syswow64 files (most of them dlls, for that matter) that let it work even in miniwinned versions: !\Windows\SysWOW64\advapi32.dll !\Windows\SysWOW64\advpack.dll !\Windows\SysWOW64\AppResolver.dll !\Windows\SysWOW64\BCP47Langs.dll !\Windows\SysWOW64\bcrypt.dll !\Windows\SysWOW64\bcryptprimitives.dll !\Windows\SysWOW64\cfgmgr32.dll !\Windows\SysWOW64\clbcatq.dll !\Windows\SysWOW64\combase.dll !\Windows\SysWOW64\coml2.dll !\Windows\SysWOW64\CoreMessaging.dll !\Windows\SysWOW64\CoreUIComponents.dll !\Windows\SysWOW64\crypt32.dll !\Windows\SysWOW64\d3d11.dll !\Windows\SysWOW64\DataExchange.dll !\Windows\SysWOW64\dcomp.dll !\Windows\SysWOW64\devobj.dll !\Windows\SysWOW64\dnsapi.dll !\Windows\SysWOW64\dwmapi.dll !\Windows\SysWOW64\DWrite.dll !\Windows\SysWOW64\dxgi.dll !\Windows\SysWOW64\edputil.dll !\Windows\SysWOW64\FWPUCLNT.dll !\Windows\SysWOW64\gdi32.dll !\Windows\SysWOW64\gdi32full.dll !\Windows\SysWOW64\iertutil.dll !\Windows\SysWOW64\imm32.dll !\Windows\SysWOW64\IPHLPAPI.dll !\Windows\SysWOW64\kernel.appcore.dll !\Windows\SysWOW64\kernel32.dll !\Windows\SysWOW64\KernelBase.dll !\Windows\SysWOW64\mpr.dll !\Windows\SysWOW64\msasn1.dll !\Windows\SysWOW64\msctf.dll !\Windows\SysWOW64\msimg32.dll !\Windows\SysWOW64\msvbvm60.dll !\Windows\SysWOW64\msvbvm60.dll !\Windows\SysWOW64\msvcp_win.dll !\Windows\SysWOW64\msvcrt.dll !\Windows\SysWOW64\mswsock.dll !\Windows\SysWOW64\msxml6.dll !\Windows\SysWOW64\msxml6r.dll !\Windows\SysWOW64\netutils.dll !\Windows\SysWOW64\nsi.dll !\Windows\SysWOW64\ntdll.dll !\Windows\SysWOW64\ntmarta.dll !\Windows\SysWOW64\ole32.dll !\Windows\SysWOW64\oleacc.dll !\Windows\SysWOW64\oleaccrc.dll !\Windows\SysWOW64\oleaut32.dll !\Windows\SysWOW64\oledlg.dll !\Windows\SysWOW64\olepro32.dll !\Windows\SysWOW64\OnDemandConnRouteHelper.dll !\Windows\SysWOW64\OneCoreCommonProxyStub.dll !\Windows\SysWOW64\OneCoreUAPCommonProxyStub.dll !\Windows\SysWOW64\profapi.dll !\Windows\SysWOW64\propsys.dll !\Windows\SysWOW64\rasadhlp.dll !\Windows\SysWOW64\rpcrt4.dll !\Windows\SysWOW64\scrrun.dll !\Windows\SysWOW64\sechost.dll !\Windows\SysWOW64\setupapi.dll !\Windows\SysWOW64\SHCore.dll !\Windows\SysWOW64\shell32.dll !\Windows\SysWOW64\shlwapi.dll !\Windows\SysWOW64\slc.dll !\Windows\SysWOW64\sppc.dll !\Windows\SysWOW64\srvcli.dll !\Windows\SysWOW64\sspicli.dll !\Windows\SysWOW64\stdole2.tlb !\Windows\SysWOW64\sxs.dll !\Windows\SysWOW64\TextInputFramework.dll !\Windows\SysWOW64\TextShaping.dll !\Windows\SysWOW64\twinapi.appcore.dll !\Windows\SysWOW64\ucrtbase.dll !\Windows\SysWOW64\urlmon.dll !\Windows\SysWOW64\user32.dll !\Windows\SysWOW64\userenv.dll !\Windows\SysWOW64\uxtheme.dll !\Windows\SysWOW64\version.dll !\Windows\SysWOW64\win32u.dll !\Windows\SysWOW64\Windows.StateRepositoryPS.dll !\Windows\SysWOW64\windows.storage.dll !\Windows\SysWOW64\WindowsCodecs.dll !\Windows\SysWOW64\winhttp.dll !\Windows\SysWOW64\wininet.dll !\Windows\SysWOW64\winmm.dll !\Windows\SysWOW64\winnsi.dll !\Windows\SysWOW64\winspool.drv !\Windows\SysWOW64\winsta.dll !\Windows\SysWOW64\wintrust.dll !\Windows\SysWOW64\WinTypes.dll !\Windows\SysWOW64\wldp.dll !\Windows\SysWOW64\ws2_32.dll !\Windows\SysWOW64\ws2help.dll !\Windows\SysWOW64\wshom.ocx !\Windows\SysWOW64\wsock32.dll !\Windows\SysWOW64\wtsapi32.dll I checked the list with process explorer while driver genius was still on, so these are the files that the sofware "invokes" or expects to find in syswow64.

tx jfk, it works fine and is a little quicker.

Hi folks, is there anyone who can tell me what service to leave intact for the laptop to find wi-fi instead of ethernet? I need it on vacation, when I have no ethernet facility and can use only wi-fi, which disappears on the laptop when I run my ethernet-supporting desktop script. If anyone tells me which service it is, then I will modify my laptop script. tx in advance.

I would just like to know how I can generalize a username that is different in several os vhds, so that the content of its subfolders (which are the same name) can be reached no matter what username. Like windir for windows or something in the case of a general user standing for each and everyone of them. I guess there are standard folders in a %...% fashion.

would any1 pls tell me how to generalize, say, antonino in a path for a script that won't take x:\users\%username%\appdata ... for a general username? tx in advance

tx jfx, I have now realized how svbus gives letters to drives, the first drive letter available until u tell it to do otherwise by specifying another drive letter.

would anyone pls tell me whether svbus can load a folder into ram

error message? 80042302 - that must be the vss one, and yes, i did optimize it away.

tx 4 ur answer to the latter question. the former issue regards trying to capture (whether wim or esd) an online os (c:\) vhd. of course, if u want to capture a vhd as d:\ or e:\ or whatever but c:\, it does work. I am talking of the functions that can be called by clicking the startup-like icon on the top right corner of the winntsetup initial mask.

tx 4 ur prompt reply, jfx. Nice job, pretty much nimbler and more viable than the previous version, so much so that ventured to try duplicating an online vhd. No dice, as has always been the case with all versions so far, if I am not mistaken. Is it technically impossible or inconvenient to make it possible, or is it a matter of time before it becomes possible? btw, esd capturing has worked fine so far (I am also referring to previous versions), but when reapplying it, say, a couple of days later, won't complete, so one has to convert it into a wim file and then everything goes fine. are u planning to improve esd applying in the near future?

Hi JFX, while feeling almost unable to wait to try the final version, I would like to know whether u have made any changes in the miniwin remove folder, the one containing the scripts. Tx in advance 4 ur reply

Listen hear u, pundits and laymen, tx 2 my boisterous supervision and virgus' (or virgus's, as u like it) painstaking toil, we r in a position 2 announce, and provide, a few scripts that can speed up the pre-miniwin customization process, which would namely get from a couple of hours (in my case, for instance) down to a couple of minutes! The good thing is that these batch files are in and of themselves customizable, which could Cater for each and every1's tastes. Should any1 happen to be interested in the scripts, pls do not hesitate to ask virgus or me.

bugfix version concerning what else, apart from ReFS? if it is only about ReFS, I'll stick to the previous version for the time being.