Antonino

yes there is, and it is what alacrán and jfx would probably call "brute force", a deletion of both files from the disk and keys from the registry. just delete all occurrences.

so does that mean we will have no choice between wimlib and wimgapi? can we at least use the latter if that is the case?

jfyi, reboot.pro is back down again; woops, now it is back up again

My dear Jfx, I have just checked with reboot.pro, and ... after so many problems with the website software update, they seem to wanna "start the ball rolling back again". the only thing of it is they want some contribution on our part, which can amount to just €10 per head, if there are as many of us as are needed to cover the expense. the greater our number, the lesser our contribution. since we have worked on wimbooting for years, we would like to still have your sense for synthesis and poignancy which has stood us in good stead for so long. As I and a few others are of the opinion that minwinning is not just a curiosity, but it can also be used for ordinary activity, it would be wonderful to join our knowledge and experience for keeping vhd's so small and still self-sufficient. To do so, I suggest that we should keep a neat modular linux-like database listing which services and dlls are needed for which various apps to still work in our minwinned vhd's. Considering my windows-reducing efforts so far, I started a decade ago with a vision from a discovery of file and folder junctions, trying to limit vhd content to just the files and folders needed to reach the desktop interface. all other files and folders I moved outside the vhd, junctioned it all back in and went on like this for years, until I discovered reboot.pro and met Wimb the Flying Dutchman. He briefed me into stopping junctioning files and folders out and back in again, as he had already envisaged a procedure called wimbooting, whereby the wim pointed to a vhd full of pointers that would guarantee the full funcioning of the system, pretty much the same as I was doing with junction, only a lot cleaner and more sensible. Then the rest has seen us all engaged in trying to reduce vhd more and more until u have come up with your knowledgeable brute-force-assisted minwin that we use today. As I was saying earlier, I have never relinquished using minwinned vhd's ordinarily, customizing my system to my advantage and liking before reducing it. the reduction has not always been so spick&span, so to speak, and I had to see what was to be retained in order for my favorite software to keep working. I have also reused my junctions on those components that not every vhd user shares with me (net framework all installed and junctioned out and back into c:\, and the same goes for my nvidia driver which can stay out of the vhd with its 1.7gigs of stuff - no reason to keep it on c:\). If we just could detect, single out and record what we have found out of services and dlls as to the functions typical of each of them, we could seriously think of using reduced vhd's to full capacity. Don't you think?

great jfx, what u suggest is what I have done so far; what I was advocating is actually changing the default x: drive letter - is it hardcoded in the exe file or can I go to a txt or ini file and change it in there?

sorry about changing the subject - would anyone tell me how to change the default x: vhd drive into any other one when creating it in winntsetup? me, I would be better off having i: as the default vhd drive instead.

u referring to the whole folder and subfolders and files I presume. me I have tried !ing all those entries wherever I found I had them \ed, but there is still something that prevents winntsetup from loading system 0x3 and software 0x3. what else coud it be? oh btw, there is another one that cannot derive from users\default\ntuser.dat, so I guess I will have to revise the list and ! the \users\default entry as well. btw, no issues instead if I delete some files in the config after it has loaded the registry, on an ex-post-facto basis.

it sometimes does the same to me, I wonder what files or directories should not be deleted to avoid this from happening

Sorry, I do not know how to delete my new account, as I recovered my old password and username and was able to sign back in, I do not need a new name.

Hi jfx, this is still Antonino, I am afraid I had to sign back up for my browser's apparently having lost my pw to enter here. I would like to know if winntsetup can take reg add and reg delete batch files anywhere in minwin. If anyone else has an answer to that, pls do not hesitate, as I am trying a couple of reg files and see if I can integrate them into the minwinning stage. Or else, I will keep doing it on an ex-post-facto basis. Thanx in advance

thank u ever so much jfx, the interface and service tests were successful, but the reg file would not want to merge. the access point was detected, but when I entered the pw and pressed next it left me with an error message of the kind. the exception unknown software exception (0xc0000002) in the application at location 0x00007FFF69AE051C.

well, folks, I can see that many people's needs expressed here so far suggest that a databank be kept which consists of all files and folders and drivers and stuff on a per-app or per-feature linux-like module basis to help each other with the features we do want to keep. otherwise we have to go by trial and error, which is not the best idea, as jfx suggests. I see that I am not the only one here with these whimsical needs, and I have been quibbling as to what the starting point might be. reboot.pro keeps an old but still valuable record of all applets that one does not want to do without, and this winntsetup here can still be a wonderful outpost for picky sticklers like us. even winntsetup was started with certain criteria as to what to leave intact and what to take out, which is a good start but then each one of us wants some further tailoring to one's needs. pls let me know what u think of the idea.

@JFX still about wifi, now I am just after checking my wife's laptop in device manager, and I see the wifi thing perfectly installed if that is what u mean, but still on the top right corner of the screen I am faced with the globe icon and no access to any wifi list as would be the case with normal full-install pre-minwin service. the os does not seem to care to even look for wifi points around. the hardware, as I said earlier, is ok.

@jfx I never did install wifi facility, it came automatically with full windows setup, in the form of ethernet on my PC and of wifi on the laptop, probably depending on what it found. When I minwin the full install on the former, everything's ok; when I do it on the latter I lose the wifi thing, and can only connect thru the cable. Now what shall I do to reinstall wifi and/or regain the wifi facility? Or alternatively, which lines shall I "!" in order to keep it?

For a start, Happy New Year to y'all!!! Then, I beg anyone who is conversant with txt files in the winntsetup remove subfolder to check my hopefully appropriate wifi.txt to make sure windows detects and manages wifi connections in the area. I have devoted quite a few years to finetuning my ethernet-connected workstation, but when I apply my txtfiles for non-deletion to my wife's non-etehernet-connected laptop, the wifi stuff disappears after miniwinning. if u pls check what is missing or what is reduntant for the purpose of wifi connection alternative to non-existing ethernet, I would very much appreciate it. Thanx in advance wifi.txt

thanks, jfx, the ini thing reads pretty handy. @Atari800XL u read like the wanna-do-things-first-off type, and this is understandable. now how much space would u gain out of not having winre.wim anymore beforehand? nice curiosity, but to make things even quicker, we can take advantage of this wonderful winntsetup thing that lets u take out whatever u like even from the biggest iso; u obtain a wim file with all the customization whatsoever (things u want out out and things u want in in). then u can use wim2iso and have ur iso as u like it, the only difference being whatever mod or customization u can think of is not done beforehand; it is done afterwards.

@atari I wish I could help you. Let's see if I have understood correctly. do u mean u cannot get rid of winre.wim for the wrapping up of an iso file? Me, I usually make wim's which are more practical, less formal and almost do not complain any. @JFX As my mysoftware.txt from the remove folder onf the minwin thing is getting real plethoric, I would like to know what characters I could use for commenting only, say, one line at the beginning and another at the end of each series of do-not-delete strings (!\...), which the file mostly consists of. together with virgus, we are trying to systematize this list with some sort of explanation for each block of strings. I do not want my comments for him to get in the way of the ordinary winntsetup process. thanx in advance

BTW, if u want to keep smartphone visibility and functionality (data transfer) from ur miniwin, all u have to do is place the following lines on any *txt in the remove folder (mine is mysoftware.txt, upon jfx's learned suggestion). for those vhd's u have already reduced, I am afraid u might have lost that functionality, in which case u can regain it by copying the following directories from the original *.wim u have started from to the *.vhd concerned. !\Windows\System32\drivers\UMDF !\Windows\System32\DriverStore\FileRepository\wpdmtp* !\Windows\WinSxS\amd64_dual_wpdmtp* !\Windows\WinSxS\amd64_wpdmtp*

sorry, I really do not know what the problem might be, now I am typing from a fresh 15gb which has rambooted ok, so I believe it must be something to do with the vhd reducing process. have I deleted the wrong file? if so, what is the wrong file. could it be some math against the geometry of the vhd that I am not aware of?

a question for whomever may answer: I have the nv_... subfolder which sits in d:\ and is junctioned back in c:\windows\system32\driverstore\filerepository and changes its name every nvidia update (practically once a month or so). the name nv_... gets changed by nvidia install, there is no telling in advance which name it will be given. In order to install the update, nvidia dictates that the free space on c.\ be around 1,70gb, or else I cannot bring the install to a completion ("not enough space" is what I get by right clicking on the nvidia driver in the device manager, actually where I have asked for the update). the junction is apparently not seen, so I might as well have the world of space on d:\ (the real final destination of the nv_... subfolder), but the install will still not complete unless I leave a gb1.70-something space on c.\. as a result of this I am left with a 3.50gb vhd, which filediskboots ok but will not ramdiskboot, unless I reduce the vhd to a 2.50gb size. unless any of u has an effective suggestion, the whole nvidia-updating scenario is such that I have to bulge the vhd to a 3.50gb size, get the driver installed and shrink the vhd back to a minimum of 2.50gb if I wanna ramboot it. of course no issue if I filediskboot. I would never have seen the problem if nvidia had let me install its repo (nv_...) driver on a disk other than c:\. any solution or workaround?

my dear dimo, this time it is vlc setup ???

no dimo i did download it but it is not nthelper.exe, it is 7zip

sorry dimo, but I cannot see the update, nor can I see the screenshot

right u r, but if u copy your vhd someplace else, does it not take even less to complete?

my dear dimo, I have managed to get hold of the nthelper folder in the temp folder, and moved it to someplace more appropriate and lasting. now how do I use it? I mean what do I do after running the exe? me, I don't get the mask u show here; what is interesting and packed on an AIO basis is actually what I was able to see in data., which might enjoy an automation process, if only I could see how to call any of them, including winntsetup, from the disk list box. if u do not advise me, I will not venture into anything seriously wrong. the disk list box is the fartherst thing I have managed to go so far.