Sardu special configuration -extra.cfg

http://www.sarducd.it/extra.html
Sample of use for extra folder for add Acronis True Image

• Extract the folder Recovery Manager into folder extra (you can use 7zip, winiso or similar)
• Rename it in Acronis
• Add these lines to the file extra.cfg:

#-> EDIT HERE <- br="">Label Acronis True Image
Menu Label ^Acronis True Image
MENU INDENT 1
kernel /extra/Acronis/dat3.dat
append initrd=/extra/Acronis/dat2.dat vga=0x314 ramdisk_size=40000 quiet
#->; EDIT HERE <- code="">

• Make ISO or USB with SARDU.

http://www.sarducd.it/forum/german-forum/trueimage-einbinden-schlagt-fehl-t315.html
Recovery Manager unter dem Ordnernamen "Acronis" mit 7z nach "Extras" entpacken

Editiere in ISO/extra/ die Datei "extra.cfg"

CODE: SELECT ALL

    #-> EDIT HERE <- br="" style="margin: 0px; padding: 0px;">    Label Acronis True Image
    Menu Label ^Acronis True Image
    MENU INDENT 1
    kernel /extra/Acronis/dat3.dat
    append initrd=/extra/Acronis/dat2.dat vga=0x314 ramdisk_size=40000 quiet
    #-> EDIT HERE <

Important information: Don't change the SARDU screen or menu's when you want a fine working SARDU. 

-----------
In der 2.03 Version ist noch eine andere Anleitung dafür.

Label Acronis True Image
Menu Label ^Acronis True Image
MENU INDENT 1
kernel /extra/Acronis/kernel.dat
append initrd=/extra/Acronis/ramdisk.dat vga=0x314 ramdisk_size=40000 quiet

Ich habe es nach beiden probiert. Das Problem ist das nach deiner Anleitung in meinem entpackten Ordner keine dat3.dat usw. ist.
------------------
Dat is dat Problem mit die Dat Dateien.  Darum wird das hier auch nicht supportet ..... Es wäre unzumutbar jede Version von Acronis-Software (und es gibt unheimlich viele davon) hier zu supporten.
Bitte um Verständnis dass wir nur die in SARDU fest integrierten Bestandteile in den Bootmanagersupport nehmen können. 
Hier aber noch eine Anregung zum 2ten Versuch

CODE: SELECT ALL

kernel /extra/Acronis/kernel.dat
append initrd=/extra/Acronis/ramdisk.dat vga=0x314 ramdisk_size=40000 root=/dev/ram0 quiet

oder vielleicht

CODE: SELECT ALL

kernel /extra/Acronis/kernel.dat
append initrd=/extra/Acronis/ramdisk.dat vga=vga=791 root=/dev/ram0 root=/dev/ram0 quiet------------------Das steht auf der "Extra"-Seite
#-> EDIT HERE <- span="">
Label Acronis True Image 
Menu Label ^Acronis True Image
MENU INDENT 1
kernel /extra/Acronis/dat3.dat
append initrd=/extra/Acronis/dat2.dat vga=0x314 ramdisk_size=40000 quiet 
#->; EDIT HERE <- span="">
Das hier klappt bei mir:
#-> EDIT HERE <- span="">
Label Acronis True Image
Menu Label ^Acronis True Image
MENU INDENT 1
kernel /extra/Acronis/kernel.dat vga=0x314 quiet
append initrd=/extra/Acronis/ramdisk.dat /s
#-> EDIT HERE <- span="">
Hinweis: 
1. Mal ins Acronis Verzeichnis und dort die .cfg Datei ansehen (beim mir: f11.cfg).
Die Datei sieht so aus:

CODE: SELECT ALL

echo Acronis True Image wird gestartet...
initrd ramdisk.dat /s
kernel kernel.dat quiet
quiet on
mbrcrcs on
vga vesa
[continue]
sysboot /active
[bootmgr]
echo Druecken Sie F11 zum Ausfuehren des Startup Recovery Managers...
default continue
delay 30
bootmenu 389

2. Die Zeile die bei Sardu mir "kernel" beginnt (in f11.cfg heißt die Datei - kernel.dat). Außerdem nochvga=0x314 zum kernel - nicht (wie oben in einem Post zur Ramdisk).
3. Die Zeile die bei Sardu mit "append" beginnt (f11.cfg: "initrd") muss ramdisk.dat lauten

-----------------------
Ich habe die Rescue CDs von TrueImage11, 2010, 2011 und 2012 über den Punkt Extras / Add Extra ISO (Grub) hinzugefügt. 
Funktioniert einwandfrei (Zumindest wenn der PC genug RAM hat, habe bisher noch einen Test mit weniger als 1 GB machen können).
Das einzige was ich etwas nerfig finde ist, das ich diese 4 zusätzlichen ISOs nach jedem SARDU Neustart neu einbinden muss.

Disk image

http://en.wikipedia.org/wiki/Disk_image
A disk image is a single file or storage device containing the complete contents and structure representing a data storage medium or device, such as a hard drive, tape drive, floppy disk, optical disc, or USB flash drive. A disk image is usually created by creating a complete sector-by-sector copy of the source medium and thereby perfectly replicating the structure and contents of a storage device.
Some disk imaging utilities omit unused file space from source media, or compress the disk they represent to reduce storage requirements, though these are typically referred to as archive files, as they are not literally disk images.
Disk image file formats may be open standards, such as the ISO image format for optical disc images, or proprietary to particular software applications.
A tape image is an image of the contents of a computer's magnetic tape. Image files derived from magnetic tape data storage are known as tape images.

Contents

• 1 History
• 2 Uses
  • 2.1 Enhancement
  • 2.2 Software distribution
  • 2.3 Security
  • 2.4 Virtualization
  • 2.5 System backup
  • 2.6 Rapid deployment of clone systems
  • 2.7 Legacy hardware emulation
  • 2.8 Copy protection circumvention
• 3 Creation
• 4 File formats
• 5 See also
• 6 References
• 7 External links

Windows Imaging Format

Filename extension	.wim .swm
Magic number	MSWIM\0\0
Developed by	Microsoft
Type of format	Disk image

The Windows Imaging Format (WIM) is a file-based disk image format. It was developed by Microsoft to deploy Windows Vista and all later Windows operating system releases, which use it as part of their standard installation procedure. It works equally well with older versions of Windows however, and is used as part of Windows Fundamentals for Legacy PCs.

1 Design 2 ImageX 3 DISM 4 Customizing images 5 See also 6 References

Design
Like other disk image formats, a WIM file contains a set of files and associated filesystem metadata. However, unlike sector-based formats (such as .ISO, .CUE/.BIN used for CD and DVD images), WIM is file-based, which means that the smallest unit of information is a file. The primary advantages of it being file-based include hardware independence and single-instance storage of a file referenced multiple times in the filesystem tree.

Although the architecture is file-based, the files are stored inside a single WIM database, reducing the SMB overhead of opening and closing many individual files at that end of the data transfer. The cost of reading or writing many thousands of individual files on the local disk is negated by hardware and software-based disk caching as well as sequential reading and writing of the data.

WIM images need to be deployed to an existing volume or partition as the toolset does not create low-level disk structures such as partitions, nor does it format them. Microsoft provides a command-line tool called diskpart for creating and formatting new volumes.

WIM files can contain multiple disk images, which are referenced either by their numerical index or by their unique name. Due to the use of single instance storage, the more each successive disk image has in common with previous images added to the WIM file, the less new data will be added. A WIM can also be split (spanned) into multiple parts, which have the .swm extension.

[edit] ImageX

ImageX is the command-line tool used to create, edit and deploy Windows disk images in the Windows Imaging Format. It is distributed as part of the free Windows Automated Installation Kit (WAIK). Starting with Windows Vista, Windows Setup uses the WAIK API to install fresh as well as cloned installation of Windows.

The first developed prototype of ImageX was build 6.0.4007.0 (main.030212-2037). It allowed Microsoft OEM Partners to experiment with the imaging technology and was developed in parallel with Longhorn alpha prototypes. It was first introduced in Milestone 4 into the Longhorn project, and used in later builds of Longhorn. Build 6.0.5384.4 added significant advantages over previous versions, like read-only and read/write folder mounting capabilities, splitting to multiple image files (SWM), a WIM filter driver and the latest LZX compression algorithms. It has been used since pre-RC (release candidates) of Windows Vista.

DISM

The Deployment Image Service and Management Tool is used to retrieve or modify information within an image.
Example usage:

mount image
dism /mount-wim /wimfile:c:\win7\sources\boot.wim /index:1 /mountDir:c:\temp2

which drivers are included?
dism /image:c:\temp2 /get-Drivers

add drivers
dism /image:c:\temp2 /add-driver /driver:C:\dell\drivers\r191214\nvdm.inf

unmount image
dism /unmount-wim /mountdir:c:\temp2 /commit

OTHER DISM COMMANDS
/mount-wim

/set-edition

/set-productKey

/apply-unattend

/cleanup-wim

/add-driver

/remove-driver

/set-uilang

/set-setupuilang

/add-package

/remove-package

/enable-feature

/disable-feature

Customizing images 

A WIM image can also be mounted as a new volume under Windows with a drive letter associated in order to facilitate easier extraction or updating of its contents. (For example, a WIM image can be converted into an ISO image using this approach). A device driver named WimFltr.sys needs to be loaded before a WIM image can be mounted using ImageX however.

A set of public APIs for manipulating WIMs have also been released, with the required functionality contained in WIMGAPI.DLL, thereby allowing developers to write their own tools too. A number of third party applications have therefore included the capability to read or write WIM files.

WIM images can be made bootable, as is the case with Windows Vista's setup DVD. In this case, BOOT.WIM contains a bootable version of Windows PE from which the installation is performed. Other setup files are contained in the file INSTALL.WIM.

See also Windows Preinstallation Environment
System Deployment Image
Windows To Go

Inmediate System Recovery

FirstDefense-ISR is an Instant System Recovery solution that has been designed for enterprise and mid-range servers and mission critical workstations, running Windows 2000, XP, and Server 2003 operating systems. FirstDefense-ISR functions transparently and allows administrators to quickly restore their systems to any complete predefined configuration. No special hardware is required. Furthermore, you do not require special CMOS, or additional disk partitions to be created. FirstDefense-ISR works on single or multi-partitioned systems, fully supporting RAID 0, 0+1, 5, and/or in clustering environments. FirstDefense-ISR performs full-system backups for the purpose of immediate system recovery. The concept was developed as a result of years of listening to IT professionals concerned about having to deal with non-recoverable Windows blue screens, service pack installs going awry, and critical files becoming corrupted. These occurrences render the system unbootable and data is inaccessible until the problem is repaired. FirstDefense-ISR periodically (and transparently) takes snapshots of the current state of the userOCOs system and applications software. It has the capability of storing up to ten point-in-time snapshots. Following a system crash, the user can immediately fall back to the most recent and uncorrupted snapshot. This reduces the MTTR to virtually zero and enables users and IT staff to instantly repair system crashes without the loss of productivity that results from extensive downtime. Ability to create and maintain up to 10 point-in-time system snapshots. Each snapshot is bootable with no rebuild required. Differential (changed files only) copy engine for fast snapshot updates. Data Anchoring feature makes data files available to any snapshot that is booted. Ability to create a compressed snapshot using NTFS file compression for a significantly smaller snapshot. Ability to archive snapshots to another device.

Compare and Contrast: Rollback Rx Pro vs. FirstDefense ISR
horizondatasys.com/ downloads 
Forum
FD-ISR and Windows 7 ( 1 2 3 4)
XPMode
XP Mode is that it's just a Virtual Machine like VMWare Workstation. Therefore a seperate running OS.
FD ISR will install with no added tweaks needed just like a real machine with XP installed. 
Well done. You do need to download that little boot fixer file, but that should be it. 
Only works with Windows 7 Ultimate,Enterprise and Professional:
http://windows.microsoft.com/en-GB/w...indows-xp-mode
http://arstechnica.com/microsoft/rev...ws-xp-mode.ars

How are you using FirstDefense-ISR?
High Availability/Disaster Recovery		65	71.43%
Software Development		10	10.99%
Beta Testing/Sandbox		45	49.45%
Optimized Build for Gaming		15	16.48%
Optimized Build for CAD, Video Editing, etc.		7	7.69%
Multiple Builds for Multiple Users		8	8.79%
Multiple Builds for Multiple OS's		10	10.99%
Other (please post)		7	7.69%

Combine FDISR with Image for DOS/Windows and even a caveman can be trusted with your computer.
I am using it for High Availability/Recovery and in combination with Image for Windows/DOS the two make me feel invulnerable.
I hear a lot of people in this forum talking about Acronis. Personally I have no experience with their software, have not even seen a screenshot. However, I have have a bad experience with the latest Ghost product. To the best of my knowledge Ghost and Acronis have one thing in common. They both operate within windows and try to take a still shot of a moving image. I like Image for Windows/DOS because you can take an image from within DOS and this allows you to get a still shot and in my opinion a more reliable image. Is it safe a idiot proof?
With FD there is never any need to reinstall XP
just keep a freshly installed XP snapshot somewhere.
There are even instructions at the Raxco website on how to do a clean install of XP on an already "polluted" system.
----------
Which FirstDefense-ISR you are using?
FirstDefense-ISR PC RESCUE or FirstDefense-ISR ?
There is a huge difference between both.
If you are using FDISR PC RESCUE and you want to boot in the Rescue Snapshot
1. Click on "Actions"
2. Click on "Boot to Rescue Area" and you will boot in the Rescue Snapshot
OR
Press the F1-key during reboot in the Pre-boot screen.
FDISR PC RESCUE has only two snapshots Active and Rescue.
The Active is your work snapshot for daily use.
The Rescue is for saving the Active, if the Active is in trouble.
The icon in the system tray will tell you in which snapshot you are.
These are the manuals of FDISR PC RESCUE
http://www.horizondatasys.com/323511.ihtml
In FirstDefense PC Rescue you don't have archives, you only have two snapshots : Active and Rescue.
You have to keep your Rescue healthy and malware-free with your security softwares. Each time when your Active is in trouble, you can save it with your Rescue by using the F1 key (Pre-boot) and copy/update from Rescue to Active.
In a normal situation you copy/update from Active to Rescue to keep your Rescue up-to-date every day, but run your scanners first.
You can also test new softwares in Active, if you want to get rid of them, boot to Rescue and copy/update from Rescue to Active and boot back in Active and the tested softwares will be gone completely as nothing happened.
Read also about "anchoring", you can reduce the size of your Active and Rescue this way.
I hope this helps.
PS: the terminated FirstDefense-ISR was more complicated, but FDISR PC Rescue is quite simple and very practical once you understand how it works.

FirstDefense-ISR 3.20.202 Download

burning .MDF and .MDS files

How to mount and burn .MDF and .MDS Files with Alcohol 120 free



Use Astroburn for burning mds/mdf files. It comes with Daemon Tools.
Open ISO buster, browse for your MDS or MDF files and just add them, save the out come to a new location and then burn to disc! Also does bin/cue/data  file formats
Source
mdf and mds files are frequently seen on torrent networks.
To burn these files, you’ll need special software packages.

mdf and mds files are types of CD and DVD image files. Only certain software packages will read and burn these types of files. Alcohol-Soft http://www.alcohol-soft.com/ (Trialware)

Daemon Tools http://www.daemon-tools.cc/dtcc/download.php (Freeware)

Install the software and select the mds file. The mds file basically contains the information the software needs to burn the mdf image file.

Both of these software packages will either allow you to run the image file from a simulated CD/DVD drive… or it will allow you to actually burn the image to a real CD/DVD disc.

You can use iso buster to change the file from mds or mdf to bin by opening the image and then right clicking on where it says cd in the left colum and then pick extract to .tao , .bin. i did it and it made a bin file. 

1. Get 'ISO buster' from www.download.com
2. Open ISO buster and in the top left corner open 'File' then 'Image file' Now browse to the file you want.
3. Create a folder in windows.
4. Drag/Drop the files into the new file you just made.
5. Burn the outcome.
You can test your CD without burn it !! Try daemon tools, its program create a virtual cd drive in yourPC

UltraISO Is Much Better, Supports All File Types And May Other Features. A*
http://www.ezbsystems.com/ultraiso/