How To Customize Hirens Boot Cd
Latarsha Dorrance
The next step to start on would be getting all your ISOs and CDs ready to transfer to the flash drive. As I mentioned earlier one of my main intentions of creating this drive was so I could get rid of my bulky CD case I seemed to be carrying everywhere. Using a software such as ImgBurn (free) you can create ISO files directly from CDs. HowToGeek has a good tutorial on how to this here. I saved all of these to a folder on my desktop named ISOs for easy organization.
If you choose that option instead of Try an Unlisted ISO, Yumi will install the Windows Vista/7/8 file to the root of the flash drive, and you DO NOT want that. It will work just fine if you install it as an unlisted ISO. So select Try an Unlisted ISO and then browse to your Windows ISO, then proceed with installation and you should see something similar to the image on the left. As you can see Yum is installing Windows 7 to D:\multiboot\ISOS\WIN7_MSDN.iso, which is what we want instead of having Yumi install it to the root of the flash drive. Continue to repeat this process for all the ISO files you want to install such as Windows and any other ISOs that are NOT listed in the Yumi list (Windows EXCLUDED). ALWAYS INSTALL WINDOWS ISO BY SELECTING TRY AN UNLISTED ISO.
yeah images are the way to go. you can put acronis on the sardu bootable along with hirens, break win 7 or ANY other images of systems with acronis down to 700mb pieces to all fit on fat32, all on one jumpdrive. #nasty
also to add: my disk is as follows: root> sardu menu and default files, all default hirens boot cd files, folder with exe files, folder with isos, driver pack solution windows executable (16gb by itself) then inside iso folder is acronis 2016 true image and universal boot, and 1 image of an xp system, win server 08 system, win 7 pro x86 and x64 system. after the image is installed on a system from acronis, you need to check achi/ide/raid setting in bios, and if still wont boot, run universal boot, then it should come up. then use driverpack solution (latest) to fill all the driver holes. then you should be fully up and running. rarely have i had to go find another driver on the manufacturers website and if i do, i will put that installable into the exe folder on my sardu disk, previously mentioned. this disk truly is the nastiest hack disk ive ever created and requires zero writing code or programming on my part. it may be one the most customized bootable, multi-faceted disks ever created. steve jobs and bill gates would probably want me to make them one, if they ever knew about it. ?
In case anyone isn't aware of Hiren's Boot CD (which I should have listed in the Windows programs thread, come to think of it, even though it's not strictly one program nor just for Windows) I thought I'd mention it here, since I've just been using it again (it's a real life saver as far as Windows is concerned).
It's a boot disc (like UBCD, which I used to use until I discovered H'sBCD) so it doesn't matter what version of Windows is on your hard drive (or how badly the hard drive's installation of Windows is corrupt), nor how much the hard drive is riddled with malware/viruses or other problems, since you're booting from HBCD instead of the hard drive. It contains every type of program you need to troubleshoot or fix a corrupt/infected Windows installation, unless of course the hard drive is physically damaged (in which case use HBCD to salvage as much data as possible, then bin the hard drive) or Windows is too corrupted to be fixed (in which case a re-install or format + re-install is your only real choice), and even comes with a quick booting minimal version of Windows XP so you can use the familiar Windows functions to copy data from the hard drive onto your own USB/network/hard drive, to rescue valuable data.
and put it on a CD-R/DVD-R, or USB stick - the latter is best, of course, since it's quicker to boot, plus it contains space for you to store rescuing data (depending on the size of the USB stick you use), and I use Universal USB Installer ( -as-1-2-3/) to put the HBCD to a USB stick.
UBCD4WIN (not the original UBCD) is at least closer to being legal, such as it generates a BartPE-based boot disc. Hiren's is basically a customized BartPE boot disc for which the generated ISO has been shared. If I remember right.
Okay, collector. But I definitely remember Hiren mentions from being banned back in the day on other forums. Perhaps instead what it does is bundle commercial software? There's something it does which is "naughty"...
I would use a trusted Linux distribution to be safe. If Hiren's boot CD has any non-free stuff, free, then why bother mentioning it? TBH I don't remember Hiren's boot CD being illegal a few years back; am I wrong?
As I said, PE is still MS proprietary and as such Hiren's was considered of questionable legality at the time. I am not arguing against your point about its controversy, I was only noting that it was PE, not XP. I believe that MS has since relaxed it stance on it and others use it now. This probably would not have happened if it had used regular XP. The latest nLite, vLIte uses the PE from the Vista installer instead of the one from XP.
Go back to the 10.x series and you've more warze. IIRC a lot of that is gone by 15.2 and they've at least moved into 'grey' arguments like 'abandonware' and the PE. To be fully cautious I would say Vogons don't want it linked here. Also I can't think of anything it does that you really can't do with the plethora of open source CDs these days.
July 2012. Not so bad for some things I guess but for enough others, why not just go to the site for Gparted, Memtest86+ etc and get the very latest version as required, y'know? Seems everything has its own Live-ISO version now, and broadband makes it trivial.
WinPE ships as a .wim file. You can mounting and customize a WinPE image following the same process as any other Windows image. In addition to customizations that are common to Windows and winPE images, such as drivers and packages, WinPE also has some customizations specific to it. This topic covers the common ways to customize a WinPE image.
Before you can customize WinPE, you need to have a WinPE image to work with. If you don't have a WinPE image to work with, see WinPE: Create USB bootable drive and follow the steps to create WinPE working files.
WinPE has packages that you can add with DISM to enable additional features and languages. Use DISM /add-package to add optional components to your image. When you add a WinPE optional component, make sure that you add both the optional component and its associated language packs.
For Plug and Play or networking support, make sure that you include a call to wpeinit in your customized Startnet.cmd script. For more info, see Wpeinit and Startnet.cmd: Using WinPE Startup Scripts.
To automatically launch a shell or application that runs when WinPE starts, add the path location to the Winpeshl.ini file. For more info, see Winpeshl.ini Reference: Launching an app when WinPE starts.
Some WinPE settings can be managed by using an answer file, such as firewall, network, and display settings. Create an answer file, name it unattend.xml, and add it to the root of the WinPE media to process these settings. For more information, see Wpeinit and Startnet.cmd: Using WinPE Startup Scripts.
If you've been instructed to apply an update to your WinPE image, you'll have to first download the latest update for your WinPE version from the Microsoft update catalog. Updates for WinPE are included in updates for the matching Windows version.
In some cases, you may not be able to recover the mounted image. DISM protects you from accidentally deleting the working directory, so you may have to try the following steps to get access to delete the mounted directory. Try each of the following steps:
I've used Clonezilla running off a usb stick, and also you can use a system that Macrium Reflect can boot from off a usb drive , and not when Macrium is running itself on your system. There's an option in the Restore tab of Macrium Reflect to create a bootable system, as an iso file, which you would then use a program like Rufus to write to a usb stick, then boot off that stick. I haven't encountered any errors done this way for either Clonezilla or Macrium Reflect. I haven't used Acronis True Image in a long time. I would most likely use Clonezilla, although it's not quite that user-friendly. It takes a bit of getting used to. If you use Macrium Reflect when your system is running, what you will do is copy your system, but unencrypted into an image file, and then when you restore it to your system, you would then press Esc when you get the Veracrypt password prompt, and then when you're in your system, in Veracrypt choose to decrypt the system to remove the password prompt at the beginning. This is the way I do it if I quickly want to have my system decrypted, but without going through the decryption process.
I'll try and keep this as concise as possible. Since I've finally decided to pack up courage and go ahead with OS (Windows) encryption, I would like some of you with prior experience to hopefully clear some of my lingering doubts. I do have to point out that I'm on an ancient hardware spec: Dell Inspirion N5010 laptop (No UEFI thing) with a HDD (No SSD).
Rescue Disk: Is the documentation (at the bottom of the page) for legacy MBR Disks still relevant. If so, does Verarypt Rescue ISO require a dedicated USB stick as it seems to suggest, or will it work fine from an EasyToBoot (where you can club ISOs of various applications) USB thumb drive.
Image Backup: The documentation says about backing up the image to a regular file-hosted encrypted container from a live environment (WinPE) but there's no mention of how to run veracrypt application/Backup tool (Macrium Reflect) in WinPE. Is it safe to assume this needs the use of Veracrypt portable version or are there other tricks unknown to newbies.
c80f0f1006