Jump to content











Photo

Useful info for WinPEs, Wimboot and Compact installs

wimboot compact portables winpe

  • Please log in to reply
9 replies to this topic

#1 alacran

alacran

    Gold Member

  • .script developer
  • 1440 posts
  •  
    Mexico

Posted 4 days ago

Portable programs are very usefull when booting from a WinPE and a Wimboot or a Compact install, when having them outside of our bootable WinPE/Wimboot/Compact (real or virtual) drive.

 

WinPEs: In this case it is even better if your Portables are compressed and self extractable (SFX) as long as they will be expanded usually to %Sytemdrive%\Temp or %Sytem%\Temp folder, in this case both located on X:, wich is the RAM drive where the boot.wim is loaded.

 

For additional info to create your own SFX programs see this topic on Post No. 5: http://reboot.pro/to...utable-from-pe/, the topic also includes links to download some SFX I have made.

 

On Wimboot or Compact install booting: The previous approach is not very useful as the SFX will extract to C:\Temp or C:\Windows\Temp folders depending the SFX creator.  And this will affect adversily our limited espace available when filedisk booting or our available RAM when RAMbooting.

In this case is preferable keep the portables uncompressed ouside the Wimboot or Compact install drive, but in some cases this means a lot of space.

 

Creating a compressed folder (on Compact mode [file by file]) using Wof_compress:

 

Then to save space on NTFS drives we can compress our Portables folder using Wof_Compress by wimb to save space and latter defragment the drive where this folder is located with Deffragler or Winconting, but this may be a very long procedure if this drive is very big, also we need to remember if latter we want to copy the compressed folder Portables to another location, it will be copied but UNcompressed.

 

Creating a compressed folder (on Compact mode [file by file]) using wimlib:

 

But I remembered some time ago a not very well known/used option of wimlib-imagex, by Eric Biggers, also available on its unoficial GUI wimlib-clc, (by retokener), both let us make a WIM image (compressed or uncompressed) of the content of a folder too, and latter extract the info into the WIM file, to an existing target Folder. with our selected compression This way we can apply the content allready compressed to any NTFS drive. This also avoids the free space fragmentation on the drive. See attached picture.

 

NOTE: if the folder doesn't exist, we need to create the folder first.

 

It is necessary to remember any compressed info using Wof_Compress or wimlib-clc can not be read by 7, 8.0 and 8.1, unless the OS accesing the info has the wof.sys or wofadk.sys installed. Win 8.1 Update 1 and 10 already have wof.sys integrated.

 

To install wofadk.sys on 7, 8.0 and 8.1, just download and run WinNTSetup by JFX

 

Or from my old post: http://reboot.pro/to...10/#entry210893

 

If for some reason, we want to install the wofadk.sys driver without installing WinNTSetup, it can be downloaded with GetWaikTools from JFX and to install it, it is just put it into Windows\System32\drivers folder and run the attached reg file and reboot the OS.

 

alacran

Attached Files

Get WAIK Tools w/o downloading the huge ISO's by JFX

 

Script to include wofadk.sys on your ChrisPEs: http://reboot.pro/fi...-wofadk-script/

To add wofadk.sys to your old WinPEs see: http://reboot.pro/to...-sd-or-microsd/

 

NOTE: Win10XPE_x64 allready has wof.sys

 

Maybe latter I remember some other things I have tested and make new post on this topic.

 

EDIT: added a picture of my Aplications  (Aplicaciones in Spanish) folder that is Compact LZX (applied using wimlib) located on my UEFI_MULTI (+Ventoy +agFM) by wimb, on a bootable MicroSD 32 GB.

 

alacran

Attached Files



#2 wimb

wimb

    Platinum Member

  • Developer
  • 2907 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 4 days ago

Nice, but it is WinPE instead of 5x used here WimPE  ;)



#3 alacran

alacran

    Gold Member

  • .script developer
  • 1440 posts
  •  
    Mexico

Posted 4 days ago

 My stupid fast typing. Thanks wimb, already fixed.

 

alacran



#4 gbrao

gbrao

    Frequent Member

  • Advanced user
  • 390 posts
  •  
    India

Posted 4 days ago

I'm just getting my feet wet with wof-compress.

 

What are the implications of not using a exclusion list when wof-compressing a drive ?

 

I had a wim of windows 10, lited, with apps etc. I used wimlib to apply the wim to a drive with --compact=lzx.

 

I recreated the Boot folder without any compression. Windows booted fine.

 

EDIT : there were no archives (zip, wim, etc) any no images (except the windows images) in that wim.

 

-----------------------------------------------------------

 

Is there a easy way to tell if a file is wof compressed (in explorer)? Files with regular NTFS compression can be shown in color and have a attribute bit.



#5 alacran

alacran

    Gold Member

  • .script developer
  • 1440 posts
  •  
    Mexico

Posted 4 days ago

Better run all your test on a VHD.

 

When appling a WIM file index by means of Dism or wimlib they use the internal exclucion list into Windows\System32\WimbootCompress.ini

WimbootCompress.ini already exist into the OS from 8.1 Update 1 to 10

 

Go to Windows\System32\WimbootCompress.ini, and open it with notepad to take a look, there you will find [PrepopulateList] used during install, all listed in this section will be full size files, during Capture the [ExclusionList] section is all that will not be copied to the WIM file.

 

Also Dism and wimlib have internal ExclusionList embeded into them, and wimlib also has a internal PrepopulateList none as complete as WimbootCompress.ini can be.

 

Also Wof_Compress by wimb has their own default lists and if you select Use Wof_Comppress Tool then additionaly the internal Windows\System32\WimbootCompress.ini is used (if available). But for questions about Wof_Compress by wimb better go to its topic: http://reboot.pro/to...0-wof-compress/

 

No, no colored files on this case, on Compact installs if you select a file from 10 and open file properties, when it is compressed the used size on disk is smaller than the file size.

 

On Wimboot VHD open the VHD with 7-zip and if a file size is 0 then it is only a Pointer to the coupled source WIM file.

 

alacran


  • gbrao likes this

#6 gbrao

gbrao

    Frequent Member

  • Advanced user
  • 390 posts
  •  
    India

Posted 4 days ago

Better run all your test on a VHD.

 

When appling a WIM file index by means of Dism or wimlib they use the internal exclucion list into Windows\System32\WimbootCompress.ini

WimbootCompress.ini already exist into the OS from 8.1 Update 1 to 10

...

alacran

Hi, thanks.

I have a old PC that I use to play around with. So I can use a partition rather than VHD.

Re WimbootCompress.ini, that file is used only for wimboot  or for any wimlib apply ? I wasn't using wimboot in the example I posted earlier.



#7 alacran

alacran

    Gold Member

  • .script developer
  • 1440 posts
  •  
    Mexico

Posted 4 days ago

Don't let the name confuse you, it was originaly created on 8.1 Update 1 for wimboot install, and that's the reazon of the name, but a file with same name, is also used on 10 for compact installs using Dism or wimlib, but actually when using a modded WimbootCompress.ini there has been some problems when using Dism and/or imagex.

The Windows API used do not work fine with some drivers as SvBus.sys driver (required only for RAMboot using grub4dos), the drivers for your printer, (if any), etc (in conclusion all drivers not included into the original install.wim on the original install CD/DVD/USB downloaded) and that's why wimlib is recommended, it do not have this issues and follow instructions on WimbootCompress.ini strictly during capture and apply.

 

alacran
 



#8 alacran

alacran

    Gold Member

  • .script developer
  • 1440 posts
  •  
    Mexico

Posted 2 days ago

If we like to have some order on the info we keep into our PC and have several folders to store files by category as: Portables, Isos, etc.     It is not a bad idea to add them to the context menu >>> "Send to" that opens when we select a file or folder and make a right click on it.

 

Only thing we need to do is create the required shorcuts on our desk and copy them to this folder located on:

 

C:\Users\USER_NAME\AppData\Roaming\Microsoft\Windows\SendTo

 

The Appdata folder is a hiden folder, so to be able to see it we need to enable on File Explorer the option show hiden files, folders an hiden units.   A shorcut for it is attached, to make things easier.

 

All shortcuts we add there will apear on the right click context menu, including shorcuts to drives or some programs like Wincontig, wimlib-clc, etc.

 

When we send any file, folder or drive to Winconting it will open having it selected and ready to verify if it is fragmented and/or defragment it.

 

If we send a WIM file to wimlib-clc it will open and will have the WIM file selected and ready to run any of the program options as Apply/Extract/Verify/Optimize, etc.

 

Not all programs will function this way when we send to them a file or folder, you will have to check and find those that are capable to work this way.

 

To let this shortcut work on any PC it was created with a relative path to SendTo folder, wich is valid for any user name. I have used it from 7 to 10.

 

NOTE: On 10 OS the shortcut to wimlib-clc has to be "Run as admin" as in attached photo.

 

Also included in the attachment is a shortcut with a relative path to Disk Management or Disk Manager to open it directly from our desk, I have used it from 7 to 10,. it is very useful to have it on our portables when booting from WinPEs too.

 

And this other two also included: DirectX Diag and Task Scheduler,    I have used this two also from 7 to 10.

 

I decided to make this shortcuts for my use some time ago to have them easy available when needed.

 

They were named originaly in Spanish, but for this post  were renamed in English, but as any shortcut just rename them as you prefer.

 

Hope they can be of some use for some users.

 

alacran

Attached Files



#9 alacran

alacran

    Gold Member

  • .script developer
  • 1440 posts
  •  
    Mexico

Posted A day ago

Yesterday I saw a topic on MSFN Forums related to a free little old portable program DBC Task Manager, there was not a link for the program, then just made a search for it and found a link on MajorGeek: https://www.majorgee...sk_manager.html

 

EDIT: On next post the program + some batch files to copy required dll is attached.

 

 

Author: DBC Studio
Date: 05/28/2015 09:14 AM
Size: 1.10 MB
License: Freeware
Requires: Win 8/Win 7

MajorGeek says: DBC Task Manager provides the user with the look and feel of the Windows 8 task manager while still running on Windows 7. No need for installation, so if you decide that you prefer the Windows 7 task manager you can revert back without anything important being changed or modified.

DBC Task Manager is a task manager application that is similar to Windows 8 task manager and can run on Windows 7.

 

 

And there is a comment from a user (from 2 years ago):

 

 

Authors link is dead but it's saved with archive.org

https://disq.us/url?...c0&cuid=2068243

x86 & x64 included in download.

 

Then I downloaded it just to test it on my running 7x64 and in fact it gives the info as 8.x does it (attached picture),

 

Latter decided to check if it runs from 7x86-WinPE & 7x64-WinPE as a full portable, the program does not run as it is, requires pdh.dll, it was very easy to solve this just copied it from 7x64  C:\Windows\System32\pdh.dll to the x64 folder of the program (same is valid but copying to x86 if you have 7x86 OS), in this case as I wanted to check also the x86 version of the program I copied from 7x64 C:\Windows\SysWOW64\pdh.dll to the x86 folder of the program,

 

Now it runs fine as a full portable from 7x86 and 7x64 WinPEs.

 

I assume adding the required dll from respective OS can also work with 8.x x86 & x64 WinPEs, I wasn't able to test this as I don't have any, when tested on Win10XPE_x64 (it already has the required dll) it runs fine too.

Also tested on ChrisPE-10x64 (adding the respective dll in the tool folder x86 or x64). And it also worked fine too.

 

NOTE: Tested it works on 7 and 10 x86 & x64 WinPEs.  Of course some info can't be gotten on PE, since certain processes are not same as on a real OS, then that info is not available.

 

EDIT: On next post the program + some batch files to copy required dll is attached.

 

alacran

Attached Files



#10 alacran

alacran

    Gold Member

  • .script developer
  • 1440 posts
  •  
    Mexico

Posted A day ago

For your convenice and to make things easier, I created DBC Task Manager.zip (attached) the two links to program page were deleted as that page do not exist anymore and added three little batch files, just extract it to your OS desktop and run required *.bat file to copy pdh.dll to respective x86 or x64 folder, this will make the tool fully portable and ready to work on a WinPE environment.

 

NOTES:

  • Run the *.bat is only required if you are planning to run the program as a fully portable from a WinPE.
  • Remember Win10XPE_x64 already has pdh.dll for x86 and x64 so no need to run the *.bat file in this case too.
  • If you ran the *.bat on Win7 OS, the progam will also work on a higher version WinPE, as I already tested running it on ChrisPE-10x64.
  • Of course some info can't be gotten on PE, since certain processes are not same as on a real OS, then that info is not available.
  • It may be possible the program doesn't open first time you run it, just close it and run it again, it has to upadate its DBCTaskman.CFG file, once done it works fine.

 

alacran

Attached Files







Also tagged with one or more of these keywords: wimboot, compact, portables, winpe

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users