______________________________________
______________________________________
Kon-Boot
1) I created konboot folder ("SARDU Drive":\konboot) and added img file from
http://www.piotrbani...m/all/kon-boot/
2)Then added reference in utility.cfg ("SARDU Drive":\menu\utility.cfg)
label Boot from KonBoot Menu label Boot from ^KonBoot MENU INDENT 1 LINUX /boot/grub.exe APPEND --config-file="find --set-root /konboot/konboot.lst;configfile /konboot/konboot.lst"
3)Created konboot.lst to put in the konboot folder created in step 1 ("SARDU Drive":\konboot) Can be done with most text editors.
foreground = FFFF80 background = FF0000 timeout 0 default /default title KONBOOT map --mem /konboot/konboot.img (fd0) checkrange 0x80 read 0x8280 && map (hd0) (hd1) checkrange 0x80 read 0x8280 && map (hd1) (hd0) map --hook chainloader (fd0)+1 rootnoverify (fd0)
4) Boot and test.
~Fin
______________________________________
______________________________________
SpinRite
1) Buy License and download spinrite
http://www.grc.com/spinrite.htm
2) I Placed the img file on the root "SARDU Drive":\spinrite.img
3) I added reference in utility.cfg ("SARDU Drive":\menu\utility.cfg)
label Boot from Spinrite menu label Boot from ^SpinRite KERNEL memdisk MENU INDENT 1 append initrd=/SpinRite.img
4) Boot and test.
~Fin
______________________________________
______________________________________
Microsoft DaRT or OS recovery discs
http://www.microsoft.../mdop/dart.aspx
http://neosmart.net/...-disc-download/
**ERD Commander excluded**
1) Extract ISO's to files (I prefer winrar)
2) Rename .wim files located in "Extracted Directory":\sources to manageable names.
** examples- for windows 7 64 I used "win764.win"- for Vista x86 I used "vis32.wim" ( I left one named boot.wim due to laziness)
3) Copy all of the .wim files to "Extracted Directory of windows 7 recovery disc":\sources
**This is important because we want the bootmgr from a windows 7 disc**
4) Copy the extracted files from windows 7 recovery folder ,that the .wims were added to, into "SARDU Drive":\ The folder boot already existed for me, so I just added the "missing" files, and added the folders EFI, and sources. Also added bootmgr to the root of "SARDU Drive":\
5) Add the .wims to the bcd store (this is the tricky part) Thanks to ENT Surgeon on the MSFN Forums there is a bat file to help this process.
Rem BCD (boot configuration data) editor for multiple vista pe REM THIS IS THE ORIGINAL BCD FILE EXTRACTED FROM ANY VISTA WINDOWS 7 WINPE / WINDOWS 7 DVD set BCD-File="c:\bcd 1\BCD" REM SET THE NAME FOR THE WINPE HERE (CHANGE IT EVERY TIME FOR EVERY BOOT ENTRY) set pename="Your PE Name" REM SET THE NAME FOR THE WIM.FILE HERE WITH PATH set filena=[boot]\sources\yourwimfile.wim for /f "eol=r tokens=1-2" %%a in ('bcdedit /store %BCD-File% /ENUM all') do set rdo=%%b for /f "tokens=1-7" %%a in ('Bcdedit /store %BCD-File% /copy {default} /d %pename%') do set guid1=%%g bcdedit /store %BCD-File% /set %guid1:~0,38% DEVICE ramdisk=%filena%,%rdo% bcdedit /store %BCD-File% /set %guid1:~0,38% OSDEVICE ramdisk=%filena%,%rdo% bcdedit /store %BCD-File% /ENUM
6) Change the parameters for each .wim file, and run the script with administrative privileges.
** If like me, you left one named boot.wim you'll probably want to change the name in BCD (the default is windows setup.) This can be done with RawReg or regedit. Load the hive and search for "Windows setup" and change value to your liking.
** If you want to change timeout, or order of items in the BCD EasyBCD is a very easy way.
7) Then edit pe.cfg to add reference for BCD Store ("SARDU Drive":\menu\pe.cfg)
LABEL Boot From MS DaRT MENU LABEL Boot from ^MS DaRT Loader MENU INDENT 1 COM32 /chain.c32 APPEND boot ntldr=/BOOTMGR
8) Boot and test.
~Fin
______________________________________
______________________________________
ERD Commander is the XP Microsoft DaRT disc
1) The way I installed was to simply change the name to livexp.iso (Good replacement for it anyway,) and let Sardu build it for me.
2) Then edited pe.cfg ("SARDU Drive":\menu\pe.cfg)
label Boot from ERD Commander menu label Boot from ^ERD Commander MENU INDENT 1 COM32 /chain.c32 APPEND boot ntldr=/minixp/SETUPLDR.BIN
3) Boot and test.
~Fin
______________________________________
______________________________________
************Edit for bonus boot option*************
Trinity Rescue Disc
Thanks to Arctor at hak5 forums
hak5 link
edited quote to fit Sardu contextHow to get Trinity Rescue Kit up and running
1. Copy the TRK ISO contents to the "Root" of your USB Stick
2. Rename your USB stick to "TRK_3-3" without quotes... if you do not do this it will give you the error that it cannot find the CD etc.
3. Create trk.lst
title TRK 3.3
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1
initrd /initrd.trk
title TRK 3.3 - as bootserver to boot other TRK clients
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 trkbootnet
initrd /initrd.trk
title TRK 3.3 - running from RAM (best >= 512mb, 256mb min)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 trkinmem
initrd /initrd.trk
title TRK 3.3 - with bigger screenfont
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 normalfont
initrd /initrd.trk
title TRK 3.3 - in simple VGA mode (debugging of kernel output)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=1 pci=conf1 splash=off
initrd /initrd.trk
title TRK 3.3 - with Belgian keyboard (see docs for other)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 keyb_be
initrd /initrd.trk
title TRK 3.3 - Virusscan all drives (non interactive)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 virusscan
initrd /initrd.trk
title TRK 3.3 - Try more pcmcia and usb nics (when not detected)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 pcmcia
initrd /initrd.trk
title TRK 3.3 - Try more SCSI drivers (when disks not detected)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 scsidrv
initrd /initrd.trk
title TRK 3.3 - with a secure shell server enabled
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 sshd
initrd /initrd.trk
title TRK 3.3 - Execute local scripts on harddrive of PC
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 locscr
initrd /initrd.trk
title TRK 3.3 - Fileshare all drives, secured with user
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 smbsec
initrd /initrd.trk
title TRK 3.3 - Fileshare all drives as guest, no security
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 smbguest
initrd /initrd.trk
title TRK 3.3 - Single user mode
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 runlevel 1
initrd /initrd.trk
title TRK 3.3 - Acpi=off, noapic PCI=bios (Alternate boot 1)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose acpi=off noapic pci=bios
initrd /initrd.trk
title TRK 3.3 - Acpi=off, noapic PCI=any (Alternate boot 2)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose acpi=off noapic
initrd /initrd.trk
title TRK 3.3 - PCI=conf2 (Alternate boot 3)
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf2
initrd /initrd.trk
title TRK 3.3 - Verbose startup for debugging after initial bootfase
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 debugging
initrd /initrd.trk
timeout 100
title TRK 3.3 - SSH server and run from RAM
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 sshd trkinmem
initrd /initrd.trk
title TRK 3.3 - SSH server, run from RAM, act as a secure fileserver
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 sshd trkinmem smbsec
initrd /initrd.trk
title TRK 3.3 - with proxyserver support enabled
kernel /kernel.trk ramdisk_size=49152 root=/dev/ram0 vga=788 splash=verbose pci=conf1 proxy
initrd /initrd.trk
title Memory tester: Memtest86+ v1.65
kernel memtest.x86
4) Added trk.lst to trk3 folder, and added reference to linux.cfg ("SARDU Drive":\menu\linux.cfg)
label Boot from Trinity Rescue Kit menu label Boot from ^Trinity Rescue Kit MENU INDENT 1 kernel /boot/grub.exe APPEND --config-file=/trk3/trk.lst
5) Tested and works great. Don't like having to rename the flash drive, but it may be worth it...
~Fin
______________________________________
Any modifications or suggestions are more then welcome.
My hopes is this will help people with other skill sets that will in turn contribute what they can to keep expanding the capability of Sardu. I wish I could add more, becuase I absolutely love this tool.
Thanks for the tool davidecosta
edit to add trinity rescue kit