Jump to content











Photo
- - - - -

Making the smallest Win10 install (Wimboot mode) on 512 MB VHD

wimboot ramboot

Best Answer alacran , 20 March 2019 - 11:53 AM

Well, I think now this thread has all info, I'm going to make a summary of all relevant post you need to follow to be able to Create and Ramboot from a Wimboot VHD and also how to make a compressed copy (to keep as backup) of the coupled files required to wimboot.

 

I started this thread thinking the smallest the best, and was able to run a 512 MB VHD, as the name of the thread says, but during the development of this thread I change my mind and decided that a 1.5 GB VHD is a good size to load a VHD in RAM on an acceptable time, and this size VHD is also capable to Ramboot on PCs with a minimum of 4 GB of RAM.

 

Introductory info and required programs: http://reboot.pro/to...hd/#entry209470

 

Making the VHD: http://reboot.pro/to...hd/#entry209472

 

Optionally apply unnatend.xml, services modifications and control Telemetry during install: http://reboot.pro/to...hd/#entry209480

 

Install your programs, SVBus driver and Capture Wimboot Image: http://reboot.pro/to...hd/#entry209483

 

Apply Wimboot Image to a 1.5 VHD: http://reboot.pro/to...hd/#entry209485

 

Installing your Wimboot VHD on a USB device and Ramboot: http://reboot.pro/to...hd/#entry209488

 

You may consider this as an Hybrid Ramboot: http://reboot.pro/to...hd/#entry209518

 

Selecting to use wimlib on WinNTSetup: http://reboot.pro/to...hd/#entry209568

 

What I put on my VHD: http://reboot.pro/to...hd/#entry209602

 

Improve Portability: http://reboot.pro/to...e-4#entry209809

 

EDIT: I finally found some info about the WimBootCompress.ini file located on WinNTSetup\Tools\, see: https://wimlib.net/f...wtopic.php?t=16

 

Custom WimBootCompress.ini: http://reboot.pro/to...e-4#entry209815

 

cdob comments: http://reboot.pro/to...e-4#entry209834

 

Making copies of coupled files (VHD + wimboot wim file) for backup pourposes: http://reboot.pro/to...e-5#entry209917

 

cdob suggestion for redirect on the VHD the path to source wim file: http://reboot.pro/to...e-6#entry209947

 

Custom WimBootCompress-2019-03-18.ini: http://reboot.pro/to...e-6#entry209949

 

WimBootCompress.ini very last version from 2020-05-18: http://reboot.pro/to...e-9#entry214854

 

karyonix suggestion for redirect on the VHD the path to source wim file: http://reboot.pro/to...e-6#entry209952

 

More cdob comments: http://reboot.pro/to...e-6#entry209976

 

Redirect the VHD path to wimboot wim file is finally a success: http://reboot.pro/to...e-6#entry209979

 

NOTE: When relocating the files, edit the BCD(s) may be required, better check to be sure all will work fine.

 

EDIT: If for any reason you want to reduce the source wim file see: http://reboot.pro/to...zx-compression/

 

New version of WinNTSetup with new features, for more info see: http://reboot.pro/to...-beta-1-update/

 

Capture and apply Windows Full Flash Update (FFU) images: http://reboot.pro/to...ate-ffu-images/

 

DismMountService (DMS) a GUI for Dism by Retokener: http://reboot.pro/to...-mount-service/

 

Procedure to make Wimboot VHDs using DMS: http://reboot.pro/to...-4#entry213355 

 

Useful info for WinPEs, Wimboot and Compact installs: http://reboot.pro/to...mpact-installs/

 

Hope this can be of any help for some of our members.

 

Best Regards

 

alacran

Go to the full post


  • Please log in to reply
245 replies to this topic

#201 bin

bin

    Newbie

  • Members
  • 12 posts
  •  
    United States

Posted 24 February 2020 - 05:56 AM

Cool, Alacran,

Although there are a lot of information here and I was not able to follow the steps closely. In a stage that I was not able to follow through. However, I was able to load the whole Windows 8.1 system into the RAM as in my poster (which was Blackbalfur‘s hope):

http://reboot.pro/to...am-memory-disk/

With that been done, I was convened that the SVBus was working at least (sorry for the honest statement). So I was able to think it over with your suggestion for the PDF document. I realized what I was missed.

So I was able to do it today with manually doing all the steps.

I was about to make a Windows 8.1 with Microsoft Office, make the system a server run in a 6 GB Intel i5 laptop without display (shattered) and in a 16 GB USB flash drive (The laptop has no internal hard drive). The new Dell laptop does not allow me to deploy Windows 8.1 except latest Windows 10, which you had suggested but I prefer Windows 8.1 for now. With the USBD hidden and only Ram Disk running, I have not been made to know that any virus can do anything with that on a daily schedule rebooting.

The Backend WimBoot file was 5.5 GB and the front-end VHD was 2,000,000,000 bytes (made from VHDtool.exe with “vhdtool.exe /create FileNameX.VHD 1999999488”). Made 200 MB .GZ from of the above ready VHD. While running, the system shows 4GB RAM (out of the 6GB machine).

I am able to remote to the server for writing with Microsoft Word from any of my devices.

E.G. If from my phone, I had Bluetooth mouse and keyboard, casting the screen to any latest TV is on road, I will be able to continue my writing.

I still have no clue how to upload a picture to this site, once I figure out, I will upload a picture of this.

This is awesome, I’ve been looking for this for a while, with all the help information here, I am not able to make a system to help me on most of my need.

What you and those dudes here had done are wonderful and greatly helping others. This is one of the never lands that serves us with unique joy and satisfaction. 

Good work and thanks for sharing.

Bin
 



#202 alacran

alacran

    Gold Member

  • .script developer
  • 1603 posts
  •  
    Mexico

Posted 24 February 2020 - 10:24 PM

@ bin

 

I read your mentioned topic some days ago before the forum failure, it was a good exercise.

 

I'm glad you were able to Ramboot a 2 GB Win8.1 Wimboot VHD coupled to a 5.5 GB WIM file.

 

 

The Backend WimBoot file was 5.5 GB and the front-end VHD was 2,000,000,000 bytes (made from VHDtool.exe with “vhdtool.exe /create FileNameX.VHD 1999999488”). Made 200 MB .GZ from of the above ready VHD. While running, the system shows 4GB RAM (out of the 6GB machine).

 

The 200 MB .gz compressed VHD expands to 2 GB during loading in RAM wich is fine, so your PC uses 2 GB to load on RAM the VHD + 4 GB available = 6 GB (total memory on the PC), then all is working fine.

 

Compressing the VHD main pourposses are: Save espace on the USB device and also load it faster on RAM, see this topic: http://reboot.pro/to...-faster-on-ram/

 

Also for additional info about VHDs see this topic: http://reboot.pro/to...ks/#entry213473

 

When you Ramboot the VHD, every time it runs it is in its pristine state no changes remain, including viruses.

 

When I said:

 

 

NOTE: It is better to run this programs under Win10

 

I mean your Wimboot VHD + coupled WIM file can be any Windows version from Win7 (on Win7 only Ultimate or Enterprice are VHD native bootables) to Win10, as long it can boot on the especific hardware, but it is better to run the two suggested programs (VHD_WIMBOOT & UEFI_MULTI) under a Win10 environment, of course you can use a Win10XPE_x64 too (recommended).

 

By the way if you want to have access to all partitions of multipartitioned USB sticks on Win8.x and Win7, (as Win10 does now starting with v1703), you may install diskmod from Karyonix, before capture as Wimboot, http://reboot.pro/fi...le/617-diskmod/

 

The Wimboot  VHD can be compressed as a .gz file as you did but it is a long time consuming procedure, or using lz4_compressor wich is faster (my prefered option), it takes just a few minutes, grub4dos 0.46a can use any of this 2 options.       

 

Let me tell you, people like you who appreciate the info in this forum, and give positive comments is all the forum members need to continue sharing their findings or developments.

 

About attach a picture or a file, you need to have certain number of post (don't remember how many), in order to be able to do it, all you need is click on More Reply Options button (when making a new post) or Use Full Editor (when editing a post, also certain number of post is required) and then select the picture, zip or 7z file and upload it.

 

Your friend

 

alacran



#203 alacran

alacran

    Gold Member

  • .script developer
  • 1603 posts
  •  
    Mexico

Posted 29 May 2020 - 01:23 PM

This is my WimBootCompress.ini very last version from 2020-05-18:

Spoiler


This two lines were added (this files belong to my Portable PartitionWizard free):

\Windows\System32\pwdrvio.sys
\Windows\System32\pwdspio.sys

I made a portable version of PartitionWizard free, and if for any reason I run it from the VHD when booting as filedisk when adding drivers, before capturing it as Wimboot, this two files are added and if they are not on the WimBootCompress.ini list they will be installed on the Wimboot VHD only as pointers, and then the VHD will not boot (if they are present as pointers), as they need to be loaded during boot process.

Of course if you don't boot a portable or installed version of PartitionWizard free, or if you just deleted this two files on your OS install before capture, you will not have this issue and those two lines may be erased (as I decided first), but some time latter I had troubles again and decided to keep them on the list, if you let them remain in the list they will not cause any harm and you are playing on the safe side.


alacran

Attached Files



#204 antonino61

antonino61

    Silver Member

  • Advanced user
  • 855 posts
  •  
    Italy

Posted 29 May 2020 - 02:19 PM

Hi Alacrán, I also tried out your last wimbootcompress.ini, without pwdr's.sys, of course. works wonderfully. I had to uncompact boot\bcd and winload.exe to make it boot ok, though. Now I wanna try to gzip and compare with *.lz4 and let u know asap.



#205 antonino61

antonino61

    Silver Member

  • Advanced user
  • 855 posts
  •  
    Italy

Posted 29 May 2020 - 02:33 PM

Well, I can see that it is taking a lot longer, but I can wait and see.



#206 alacran

alacran

    Gold Member

  • .script developer
  • 1603 posts
  •  
    Mexico

Posted 29 May 2020 - 05:37 PM

Hi Alacrán, I also tried out your last wimbootcompress.ini, without pwdr's.sys, of course. works wonderfully. I had to uncompact boot\bcd and winload.exe to make it boot ok, though. Now I wanna try to gzip and compare with *.lz4 and let u know asap.

 

*winload* and \Boot\BCD are included on the 2020-05-18 WimBootCompress.ini

 

About *.gz versus *.lz4 compression comparative it was done long time ago: http://reboot.pro/to...-faster-on-ram/

 

alacran



#207 antonino61

antonino61

    Silver Member

  • Advanced user
  • 855 posts
  •  
    Italy

Posted 29 May 2020 - 10:09 PM

as regards the compression of the files I mentioned, it must be something wrong on my end, not ur fault. as for gz vs lz4, u want a laugh? I got a 32gb intel optane stick for a present from a not-so-competent friend and "a caballo regalado ...". so I had to ... use it anyway. As I do not have traditional hdds, the only thing I could think of was to place it on my mobo and use it as boot disk (the automation of its proper function has been completely blocked and the driver is the same as an nvme proper. u cant imagine the speed of ramloading on my proper nvme (my 2nd drive) with the 4.5 nvme-patched g4d. Unfortunately this version of g4d does not see my optane mem stick as nvme (who could blame it?). so If I have the same file on both drives, the one on the second drive is the only one seen as bootable. this g4d (4.5) cant seem to boot from .lz4, so the only alternative I have is .gz if I wanna save space, unless u r of another idea. I have many options for sure. BTW, the intel optane memory stick is still the quickest "disk" on my system.



#208 alacran

alacran

    Gold Member

  • .script developer
  • 1603 posts
  •  
    Mexico

Posted 30 May 2020 - 09:15 AM

If with the new hardware on your PC you can't get any improvement using "grub4dos 0.45c + the nvme patch" (as not taking advantage of nvme patch), then why use that old and limited version?

 

Use grub4dos 0.46a and you will be able to use *.lz4 compressed VHDs, wich are compressed faster, resulting *.lz4 files are smaller and also load faster on RAM, than using *.gz compression as it's proven on: http://reboot.pro/to...faster-on-ram/ 

 

grub4dos 0.46a last version released on 2020-03-04 link, this version is working fine so far: http://dl.grub4dos.c...a-2020-02-29.7z

 

alacran


  • antonino61 likes this

#209 antonino61

antonino61

    Silver Member

  • Advanced user
  • 855 posts
  •  
    Italy

Posted 30 May 2020 - 12:21 PM

Because it still does take advantage of the old hardware (2nd drive) which still is there. it can load 4gb in ram in just 1-2 secs. and I still see no quicker loading than any other config. My dream would be a patch revision on g4d 4.5 or even better a fresh patch on g4d 4.6 that would "consider" also my intel optane memory stick as nvme. as of now, I think I could still load lz4 on g4d 4.5, but without the nvme string in menu.lst (not much of a difference in time, probably a slight difference in space, since I squeeze my front-end vhd to 500 megs or less anyway, at least here). Just to give u an idea of comparisons here, I still resort to resmon.exe to figure out which loading mode I am on, by checking the reserved space, if I have forgotten how I loaded the system in that session). Again, the ideal would be to have a patch for my optane (1st) drive, considering the small spaces we all (some more, some less) have managed to bring our windows systems to. Consider that so many ppl who have made the mistake of buying intel optane memory sticks and find them of little use as a cache memory stick now could still do as I did (use them as 1st drives) - less wear and tear for other drives, greater speed, comfortable seating of wims and vhds, etc.



#210 antonino61

antonino61

    Silver Member

  • Advanced user
  • 855 posts
  •  
    Italy

Posted 31 May 2020 - 10:13 AM

@Alacrán

have u ever tried fastest 8-word-size gzip? try it out and compare it with lz4 compression time. I did, and it compressed in seconds - not much of a difference in space occupied from ultra max-word size gzip and still can boot from my new hardware, without the nvme string of course. not much of a difference in loading time from a 4gb full vhd on my nvme-proper drive either. it is just a matter of seconds or less.



#211 alacran

alacran

    Gold Member

  • .script developer
  • 1603 posts
  •  
    Mexico

Posted 31 May 2020 - 04:55 PM

Good to know you found a workaround that fits your preferences/likes.

 

alacran



#212 antonino61

antonino61

    Silver Member

  • Advanced user
  • 855 posts
  •  
    Italy

Posted 31 May 2020 - 09:08 PM

Thanx Alacrán. Since u so much enthuse at my finding my workarounds that suit my preferences, would u pls tell me what prevents nvme patch on the latest version of g4d? would u also suggest the most convenient version of wimbootcompress.ini for normal non-usb booting? I remember ur briefing me on the compression exclusion and inclusion and prepopulation list kinda thing, but I am afraid of making editing mistakes, so I would at least start from a consolidated non-usb-oriented version. 

and, btw, of couse, thanx in advance for your patience.



#213 alacran

alacran

    Gold Member

  • .script developer
  • 1603 posts
  •  
    Mexico

Posted 01 June 2020 - 06:09 AM

@ antonino61

 

 

what prevents nvme patch on the latest version of g4d?

 

Simple it was made for v0.45c not for v0.46a wich has many internal differences, then it do not apply to it.

 

 

would u also suggest the most convenient version of wimbootcompress.ini for normal non-usb booting?

 

Use the version included in untouched install ISO, but then you will have to make (and latter include into that) your own list of drivers related to your hardware and external devices, it is complicated and time consuming, that's why I prefer to have this line on my custom version:

 

\Windows\System32\drivers\*.sys

 

This way all drivers will be included as real files not pointers.

 

 

I remember ur briefing me on the compression exclusion and inclusion and prepopulation list kinda thing, but I am afraid of making editing mistakes

 

[CompressionExclusionList] >>> Enables you to define the specific files and folders, and also to specify file types, to exclude when you use the /Compress argument.  Usually you will not change anything under this section.

 

[PrepopulateList] >>> Enables you to define the files and folders to copy to install path as real files, not pointers when you use the /Apply + /Wimboot option.  Additions made to this section will help improve bootavility, but will increase the size of the content copied to the Wimboot install path (our Wimboot VHD).

 

[ExclusionList] >>> Enables you to define the files and folders to exclude when you use the /Capture option.   Additions made to this section will help reduce WIM image size as an example \Recovery\* all located into folder Recovery will not be copied and compressed into the WIM image.

 

alacran



#214 antonino61

antonino61

    Silver Member

  • Advanced user
  • 855 posts
  •  
    Italy

Posted 01 June 2020 - 11:05 AM

thanx, Alacrán. now, will I put the original wimbootcompress.ini (with \Windows\System32\drivers\*.sys where u said to put it) in vhd_wimboot and wof_compress folders before capturing and applying and compacting respectively instead of the wimb ones?

BTW, the original wimbootcompress.ini ends with the following list

[PinningFolderList]

\Windows\System32\config
\Windows\System32\DriverStore
\Windows\WinSxS
 
[CompressionFolderList]
\Windows\System32\WinEvt\Logs
\Windows\Installer
 
???
 
my winsxs folder is oprekin's version's (only 90 megs (less than 60megs on disk)), which I usually place in \windows instead of the original if the original is bulky (5gb or so). it works on the same builds (ex. 19041). it stays intact. it does not seem to work on different builds, though.


#215 alacran

alacran

    Gold Member

  • .script developer
  • 1603 posts
  •  
    Mexico

Posted 01 June 2020 - 02:44 PM

[PinningFolderList]

\Windows\System32\config
\Windows\System32\DriverStore
\Windows\WinSxS
 
wimlib-imagex wich is the internal software used for capture and apply on VHD_WIMBOOT do not interact with this section and give a message you can sefely ignore or just delete this part if you prefer.
 
Attached the lite version for Win10 only put it into \Windows\System32\, it is same as VHD_WIMBOOT-28\makebtWimBootCompress-W10X.ini with only \Windows\System32\drivers\*.sys line added.
 
alacran

Attached Files


  • wimb likes this

#216 antonino61

antonino61

    Silver Member

  • Advanced user
  • 855 posts
  •  
    Italy

Posted 01 June 2020 - 03:20 PM

thank u ever so much alacrán. c u in a bit, with what I will have found about xpress4k.



#217 antonino61

antonino61

    Silver Member

  • Advanced user
  • 855 posts
  •  
    Italy

Posted 01 June 2020 - 05:47 PM

so, here is what I found:

 

with your winbootcompress.ini, which yields the smallest *.wim, neither wimb's wimboot nor winntsetup in anyway whatever (all options red) would apply the image. only wimb's wimboot captures my full vhd but then, as I said, refuses to apply what it has just captured. so I resorted to dism_tool, which showed the errors in the corrupt compression table (perfc009.dat -6 and perfstring*.ini). I had to delete both to make dism_tool capture the vhd into wim, and got 2 wims, one fast (presumably xpress4k, 3.3gb) and one max (presumably lzx, 3.03gb), which wimb's wimboot eventually applied to w10x*1.vhd and w10x*2.vhd respectively, both the same size that I gave (1gb), presumably both lzx. then I gzipped both: 93megs vs 134megs. 



#218 alacran

alacran

    Gold Member

  • .script developer
  • 1603 posts
  •  
    Mexico

Posted 01 June 2020 - 07:46 PM

As you are not starting from a fresh install and you are recapturing a previous in use Wimboot VHD + all additional changes you have made to it, it is not possible to determine where or what could be the reason for the issues.

 

Better start the procedure since the begining, with a fresh install + new WimBootCompress.ini and its respective first Wimboot capture and apply, using only last version of VHD_WIMBOOT for capture (with LZX option unselected to use 4K compression or selected to use LZX compression on the captured WIM image) and latter apply to the Wimboot VHD of your prefered size.

 

If you do all the steps as recommended all should work fine, if you introduce any variation to the procedure, please don't ask for comments or help since nobody will be able to reproduce your issues and then nobody could find the cause of any issue.

 

alacran



#219 antonino61

antonino61

    Silver Member

  • Advanced user
  • 855 posts
  •  
    Italy

Posted 01 June 2020 - 11:40 PM

no more issues. all latest versions here, apart from 4.5 g4d for the reasons I already explained. the quickest here seems to be xpress4k wim plus its applied vhd (1meg, the smallest possible for what wimb envisaged) - change the name of wim for de-attaching vhd momentarily - xpress4k compact the deattached vhd to the greatest possible free space - eject it and restore the wim to its original filename in order to update the combo - clean local boot entries with bootice - gzip the vhd the fastest 8-word size way and launch the vhd without the nvme patch line. it will go slow only for the used space, later to rocket to the end of 1024k and launch it quickly and issuelessly, and it does so from new hardware (d:\, the optane stick). from take it or leave it. 



#220 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15527 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 02 June 2020 - 01:04 PM

so, here is what I found:

 

with your winbootcompress.ini, which yields the smallest *.wim, neither wimb's wimboot nor winntsetup in anyway whatever (all options red) would apply the image. only wimb's wimboot captures my full vhd but then, as I said, refuses to apply what it has just captured. so I resorted to dism_tool, which showed the errors in the corrupt compression table (perfc009.dat -6 and perfstring*.ini). I had to delete both to make dism_tool capture the vhd into wim, and got 2 wims, one fast (presumably xpress4k, 3.3gb) and one max (presumably lzx, 3.03gb), which wimb's wimboot eventually applied to w10x*1.vhd and w10x*2.vhd respectively, both the same size that I gave (1gb), presumably both lzx. then I gzipped both: 93megs vs 134megs. 

 

 

 

no more issues. all latest versions here, apart from 4.5 g4d for the reasons I already explained. the quickest here seems to be xpress4k wim plus its applied vhd (1meg, the smallest possible for what wimb envisaged) - change the name of wim for de-attaching vhd momentarily - xpress4k compact the deattached vhd to the greatest possible free space - eject it and restore the wim to its original filename in order to update the combo - clean local boot entries with bootice - gzip the vhd the fastest 8-word size way and launch the vhd without the nvme patch line. it will go slow only for the used space, later to rocket to the end of 1024k and launch it quickly and issuelessly, and it does so from new hardware (d:\, the optane stick). from take it or leave it. 

 

Just when I thought that Vogon's poetry was still the third worst in the universe. :(

Paula Nancy Millstone Jennings of Sussex should feel threatened.

 

:duff:

Wonko



#221 alacran

alacran

    Gold Member

  • .script developer
  • 1603 posts
  •  
    Mexico

Posted 02 June 2020 - 02:07 PM

To me that sounds like:

 

It is neither square nor round but quite the opposite.

 

alacran



#222 antonino61

antonino61

    Silver Member

  • Advanced user
  • 855 posts
  •  
    Italy

Posted 02 June 2020 - 02:22 PM

I appreciate your sense of humor,wonko, but just out of curiosity, have you noticed that my 2 posts have different times and many a test were carried out in between that might justify the apparent contradiction? I do abstractly appreciate alacran's zeal in telling me to start all over again owing to a couple of meaningless files that I have already got rid of, to obtain in a day's work what I already have and justify his otherwise impossible comments ... Please, do trust even the most incompetent. I don't think my saying that the differences between the various booting configs amount to just seconds timewise and something more sensible spacewise is baloney. Plus, if I tell anyone that gzipping the fastest 8-word-size way is quicker than lz4'ing, either believe it or try it yourself.

#223 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15527 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 02 June 2020 - 05:55 PM

I appreciate your sense of humor,wonko, but just out of curiosity, have you noticed that my 2 posts have different times and many a test were carried out in between that might justify the apparent contradiction? 

 

Sure, the point was that neither of them are understandable, so, no contradiction can be found, let alone any need to justify it.

 

 

Please, do trust even the most incompetent. I don't think my saying that the differences between the various booting configs amount to just seconds timewise and something more sensible spacewise is baloney. Plus, if I tell anyone that gzipping the fastest 8-word-size way is quicker than lz4'ing, either believe it or try it yourself.

I would trust you, not because of your incompetence, but rather because I believe that you are good-willing and earnest in your reports :) , again the point remains the fact that they appear as semi-random babbling and/or - sometimes - as plain showing off.

 

Noone, and I mean noone, including the most experts here would be able to replicate what you did based on your posts, not even putting together bits and pieces scattered on n other threads, which is fine, mind you, it is not actually compulsory to post things that make sense and that are repeatable (though it usually helps in having conversations).

 

The risk (please read as certainty) is that of ending in monologues *like*:

http://reboot.pro/to...lladafluff-out/

 

Not a problem at all, but in case you didn't notice, now you know.

 

:duff:

Wonko

 

 

;



#224 antonino61

antonino61

    Silver Member

  • Advanced user
  • 855 posts
  •  
    Italy

Posted 02 June 2020 - 06:24 PM

R u sure they are not repeatable? I do repeat them, at least on 3 machines. And you claim u cannot repeat them on 1? Come on...want me to repeat get all of the fluff out in Italian or do I upset you? What to me is meaningful of it all here is to have squeezed windows almost to the essential, to have sped it up, to have "mitigated" it thru many stratagems, to have customized and stabilized it almost "the Mac way", so much so that I have been running the same version for months at the speed and efficiency of the first setup day and u call that unrepeatable? Most of this, thanks to some of u. If you or someone else can manage to get all of the fluff out any more consequentially than I have done so far, please do and show instead of dismissing what u seem to dislike.

#225 antonino61

antonino61

    Silver Member

  • Advanced user
  • 855 posts
  •  
    Italy

Posted 02 June 2020 - 06:31 PM

Sorry if I have pressed the multiquote button accidentally.



Also tagged with one or more of these keywords: wimboot, ramboot

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users