What is the best way to create recovery CD

  • Thread starter Thread starter Justin_Fang
  • Start date Start date
J

Justin_Fang

Hi all,

I have an image around 300MB. My purpose is to create a recovery CD to
ship with our product. And then user will be able to recovery it
himself.
I find there are two way to create recovery CD disscussed here.
1. Use windows PE
I find one topic
http://groups.google.com.tw/group/m...recovery+CD&rnum=10&hl=zh-TW#b46f6d6abb7ffd1e
The conclusion in this topic is it is impossible to create it with
Windows PE. Can anyone prove it?
Another issue is I can not find "Windows PE toolkit or OEM
Preinstallation Kit (OPK)". Can anyone give me some information about
it? I can not find it in MSDN or Microsoft website. Do I need to buy
it somewhere?

2. Use Ghost
People here said that it takes $20 for each license. Is it ture?
If I create recovery CD with windows PE, is there any extra charge?

Please share your experience about recovery CD. Thanks a lot.

Justin
 
Justin,

I don't really know how expensive Ghost licenses are today.

You can definitely use WinPE. Full WinPE 1.x version comes in on 1st CD with XPe Toolkit. If you were to customize PE to fit your
needs (basically to create a custom WinRE) you'd need to get the OPK. It is available from various distributors including some XPe
distributors. Not sure if OPK for WinPE 1.x is publicly available for download these days but PE 2.0 is. You could use PE 2.0
(much... *much* easier to work with then with PE 1.1) but then you should consult with MS or XPe distributor on whether it is
legally allowed to use the newer PE version in XPe recovery scenario's.

Another approach with some great benefits even to PE way is to create your own, small, XPe image for recovery purposes only. If used
only in recovery scenario, the same PID can be used for the small XPe image as you used for your "big" XPe image. With XPe toolkit
you obviously would be able to customize that recovery OS as much as you want to, from minimizing its footprint and adding only
features you need to embedding required custom apps/drivers/scripts you may need for image restoration, media preparation and etc.
 
Hi KM,

Thanks for your information.

I follow the instruction on msdn of topic "Creating an Embedded
Recovery CD by Using Windows PE and SDI". I can not find oscdimg.exe
and etfsboot.com. That's why I said I need to get OPK. Finally, I get
Windows AIK from MS web site which include these two files and PE2.0.
After boot up from CD, I can not run sdimgr.wsf, it ask me for the
program to open it. I saw you talk about cscript in other discussion.
But it is failed, too. :(

Then, I try to your another suggestion to create XPe image on CD. I
follow "Tutorial: Creating a Bootable CD-ROM" in help file. After the
CD created and I try to boot from it. The result is windows logo show
up, and then system crash (blue background). It's really a nightmire.
I don't know how to debug it. And once the CD boot up successfully,
how to recover system? Use sdimgr or write a program to do it?

Is there any eaiser way to create Recovery CD? I saw Windows AIK has a
tool Windows System Image Manager, are you familiar with it?

Thanks,
Justin
 
Hi KM,

Could you please point out how to create a bootable CD?

I create a working folder which contains I386 folder, recovery.sdi,
sdiaut.dll, SDIMgr.wsf, win51, win51ip, win51ip.SP2, winfom.ini. And
use the oscdimg.exe and etfsboot.com from windows AIK to run following
command.
oscdimg -n -bc:\winpe_x86\etfsboot.com MyWokingFolder c:
\winpe_x86\winpe_x86.iso. Such image can not create a bootable CD.
(Can not find bootmgr)

I use the instrunction in Windows AIK to create a CD which contain 4
folders: boot, EFI, Servicing, sources, and 5 files: bootmgr,
imagex.exe, rcd.sdi, sdiaut.dll, SDIMgr.wsf. This image can create a
bootable CD correctly, but can not run either sdimgr.wsf or cscript.

Thank you in advance.

Justin
 
Justin,

Bootable CD-ROM feature of XPe FP2007:
http://msdn2.microsoft.com/en-us/library/ms912902.aspx
This feature is now tested by many devs and should work as long as you follow the instructions. Otherwise, please let us know what
the BSOD you saw, what you see in the FBALog.txt, how and when you enabled EWF, what EWF mode is set and etc..

I hope you don't mix PE 1.x and PE2.0 tools and binaries. It is not going to work.
From the files below it does seem though you are missing things. Please don't.

AIK (2.0 stuff) works with WIM files, not SDI.
How to Create a Bootable Windows PE RAM Disk on CD-ROM:
http://technet2.microsoft.com/Windo...ca59-4586-b688-3a3c098d34241033.mspx?mfr=true (I used this and
this feature works great! as well as the boot off UFD, HDD, etc.)
This is probably what you have used (the last paragraph of your message below). However, please keep in mind this is new kernel (the
one Vista's using), not XP's kernel. You may definitely be experiencing problems of application compatibility and etc.

To get SDIMgr script working you have to make sure the WSH engine is included in your image. Also, use cscript or wscript to run the
script command line. The sdiaut must be registered as COM object.
If you do the above and still see an error, please post the error info here.
 
Dear KM,

Thanks for your response.

In link http://msdn2.microsoft.com/en-us/library/aa460091.aspx, it
said it needs oscdimg tool and ETFSboot.com
Do you know where to get these two files for PE1.0? Once I had these
two files, I can just use oscdimg to create a bootable CD, am I right?
This document doesn't have this information but I think it is a easier
way to create recovery CD.

To avoid the risk, I don't plan to try PE 2.0 now.

I am trying to build XPE image boot from CD again. I will post the log
here later.

Thanks,
Justin
 
In linkhttp://msdn2.microsoft.com/en-us/library/aa460091.aspx, it
Click to expand...

Oh yeah, I like this article. Since it will never work from write
protected media. It may work form LAN, but not from CD/DVD. I tried
many times and I always failed.
said it needs oscdimg tool and ETFSboot.com
Do you know where to get these two files for PE1.0? Once I had these
two files, I can just use oscdimg to create a bootable CD, am I right?
Click to expand...

Yep. I got that WinPE OPK from distributor, and the two files are
located on that cds. You should get it for free from your distributor
from wich you buy the runtime keys.
This document doesn't have this information but I think it is a easier
way to create recovery CD.
Click to expand...

I'm facing a similar problem. Look at the topics "compressed ntldr" in
this ng.

Well, here is the way I did, and it workes so far without problems.
And is very simple.

- configuring Image
- run fbreseal on it with shutdown
- after shutdown just copy all files and folders as they are
(including system files and hidden ones).
- creating "Working"-Folder as stated in that article above
- including the files from your xpe-image
- creating a diskpart script wich first delets all content of compact
flash and then creates the partitions as you need it, name it and set
first partition as active.
- change the Working\I386\System32\startnet.cmd - batch file this way:

- show eula addendum for WinPE with question of acceptance (Set /P
command) ... ;-)
- run diskpart script
- format the volumes created
- just copy the files of xpe-Image to active partiton/volume (C:)

if you are using compressed images, run compact, to uncompress ntldr /
regfdata (if you are using regfilter).

than create the image with oscdimg.

Here is the command line I use with oscdimg:

oscdimg -lXPE -h -n -bE:\Etfsboot.com -x -o E:\Working E:\XPE_REC.ISO -
m

I can give you complete sample for diskpart script / batch file, I use
to do this. Just let me know.

Not a nice solution, but a rarely one and easy to handle - even for
none software engineers like me... ;-)

There is just the need of another copy-tool, since xcopy will always
end in shifted characters on the target system - working, but not
nice.

Steffi
 
Dear Steffi,

Thanks. I already create a bootable CD successfully with a small XPE
image.
Now, I am looking for a restore solution.
I find SDI will modify partition table which is not what I need.
Could you explain more about your copy tool?

I'd like to know anyone use the way in msdn link to create recovery CD
with WinPE and SDI?
It really takes me a lot of time and without success.
Just a little upset.

Justin
 
Now, I am looking for a restore solution.
I find SDI will modify partition table which is not what I need.
Could you explain more about your copy tool?
Click to expand...

Hmm, just copy it. First time, i used xcopy (with all that switches
for hidden files etc), but this will result in SHIFTED characters.
So then I cab'ed all files form my xpe-image (cabarc-tool from xp
support tools), and then I extracted them back to the original volume,
wich has to be formated before. That's it.
I'd like to know anyone use the way in msdn link to create recovery CD
with WinPE and SDI?
Click to expand...

Yes, me too. But maybe KM has a solution for deploying an sdi-image
from a CD, but I cannot follow all the steps right now.
It really takes me a lot of time and without success.
Just a little upset.
Click to expand...

Well, my problem is none unicode characters. My solution is ok for
unicode language. But it cannot handle cyrillic/russian characters.
Therefore I need a disk imaging tool like sdimgr.

Steffi
 
I posted the info about that possible solution [you will have to test it on your target first to make sure it's working] to the
thread above ("compressed ntldr"). Obviously, it is not going to work for Stefanie due to the limited size of the flash used. Maybe
Justin is more lucky and has enough storage space on his target to create and hold a temporary partition if the SDI approach is
taken :-)

Stefanie,
Since we are running out of ideas how to fix your issue. How about just sticking to the [x]copy thing?
I actually think robocopy, which is way better and truly unicode app, would be a better choice. I also recall there is a unicode
related issue with robocopy on XP when it writes the log of all file operations performed. I've heard it has been fixed in the
robocopy version shipped within Vista. You may want to check it out, although I am not sure that version will run on XP.
Another possible approach is to have certain files in localized images preserved with slightly modified names to only use ASCII
characters. You can always go back to original file names at run time with a self-cleaning script that is launched very first time
the image boots as runonce (or startup folder) item.
 
Hi KM,

Since we are running out of ideas how to fix your issue. How about just sticking to the [x]copy thing?
Click to expand...

Well, that xcopy-thing is not that issue it self. Since xcopy actually
can copy filenames with such characters. I think xcopy just takes them
as they are and is writing them in exactly the same case - it will be
logged as "writing C:\????????????????????.???... I don't know if that
characters are also shiftet then, but I don't think so.

The problem is OSCDIMG, wich will imediatly cancel iso-image creation,
as it reaches such a file. Maybe it is possible, to use NERO instead
of oscdimg. But I don't know exactly, wich settings to use, to get a
booting winpe CD/DVD. I will try with ETFSBOOT.COM as Image-File, and
then pick up all contet of my working-folder. Maybe it will do the
job.
I actually think robocopy, which is way better and truly unicode app, would be a better choice. I also recall there is a unicode
related issue with robocopy on XP when it writes the log of all file operations performed. I've heard it has been fixed in the
robocopy version shipped within Vista. You may want to check it out, although I am not sure that version will run on XP.
Another possible approach is to have certain files in localized images preserved with slightly modified names to only use ASCII
characters. You can always go back to original file names at run time with a self-cleaning script that is launched very first time
the image boots as runonce (or startup folder) item.
Click to expand...

This could be a solution. I also will try that robocopy thing.

Anyway KM, thank you very much for your help and suggestions! I'm
sure, I will find a way, to do that. If there is nothing working, than
I need to go that runonce-way. It will be a kind of pain but if it's
working, than it has to be done.

Thank you!

Steffi
 
Stefanie,

A dump question - have you tried using OSCDIMG from a localized (Russian) version of WinPE OPK? Just sustitue the version you've got
in your english OPK.
Obviously, you can't have the version of OSCDIMG to support all the languages at once but I recall you mentioned you only had
troubles with russian characters so far.

Yo can definitely use Nero. Here is a guide for you: http://www.tacktech.com/display.cfm?ttid=297
You will only have to tweak the disk signature manually to make it El-torito.

Perphas better to use the following steps posted by Slobodan long time ago:

NERO usage for El-torito CD creation.
1. Select Make Bootable Disk option.
2. Select Bootable logical drive option, and select volume with XPe that you want to record on El-torito part of CD.
3. Go to next step. (Press New.)
4. Add files that you want to have on your CD.
5. Select recorder->Choose Recorder
6. Select Device "Image Recorder" and press OK.
7. Choose Burn option and then name file that will receive CD image.
8. Use HEX editor and find MBR sector placed by Nero. Go to 1B8 location (relative offset from MBR) and type 'ELTO' DiskID on that
position of hex representation depending on hex editor. You can make a simple app that will change this number if you need to
frequently burn new images.
9. From NERO. Choose option Burn image to Disk.
10. Choose image file.

11. Change back to real recording device driver so you can burn image on CD instead to image again.
12. Burn image.

Reason for this long procedure is because Nero creates MBR block that use DiskID 0 and El-torito or other win drivers can't use
DiskId 0.


IIRC, he also posted ElSigFix utility on www.xpefiles.com that will help you open and trace El-torito information's to find MBR
sector and then patch it.

--
=========
Regards,
KM

Hi KM,

Since we are running out of ideas how to fix your issue. How about just sticking to the [x]copy thing?
Click to expand...

Well, that xcopy-thing is not that issue it self. Since xcopy actually
can copy filenames with such characters. I think xcopy just takes them
as they are and is writing them in exactly the same case - it will be
logged as "writing C:\????????????????????.???... I don't know if that
characters are also shiftet then, but I don't think so.

The problem is OSCDIMG, wich will imediatly cancel iso-image creation,
as it reaches such a file. Maybe it is possible, to use NERO instead
of oscdimg. But I don't know exactly, wich settings to use, to get a
booting winpe CD/DVD. I will try with ETFSBOOT.COM as Image-File, and
then pick up all contet of my working-folder. Maybe it will do the
job.
I actually think robocopy, which is way better and truly unicode app, would be a better choice. I also recall there is a unicode
related issue with robocopy on XP when it writes the log of all file operations performed. I've heard it has been fixed in the
robocopy version shipped within Vista. You may want to check it out, although I am not sure that version will run on XP.
Another possible approach is to have certain files in localized images preserved with slightly modified names to only use ASCII
characters. You can always go back to original file names at run time with a self-cleaning script that is launched very first
time
the image boots as runonce (or startup folder) item.
Click to expand...

This could be a solution. I also will try that robocopy thing.

Anyway KM, thank you very much for your help and suggestions! I'm
sure, I will find a way, to do that. If there is nothing working, than
I need to go that runonce-way. It will be a kind of pain but if it's
working, than it has to be done.

Thank you!

Steffi
Click to expand...
 
Dear both,

Sorry that I am not very clear about your discussion about restore
function.
I am trying to use zip for restore. It seems work fine for
restoration.
Do you think it's a good idea for restration by zip?

Could you please also share your restore procedure with me?
Do you put fdisk, diskpart, format tool in your recovery CD?
How do you design your script?

Thanks,
Justin
 
Justin,

I don't see any problems with zip archiving your image files beside just licensing issues. Using the right licensed tool or freeware
or an utility from XPe/PE repository would probably be a way to go here.

My image restore procedures were too custom and it wouldn't help you much if I described them here in details. I have posted some
stuff in this NG a while back so you may want to search a bit for more info.

Below are some common points shared across restore scenarios.

In general the idea is simple - you have to go offline to be able to copy over/restore/replace the current XP(e) based OS. This
means you want to boot another image of yours [off a XPe or PE bootable CD for instance, or bootable UFD, or from another, better
hidden, partition on the same hard drive or from another hidden hard drive, or do a remote boot for a DOS/XPe/PE image, etc.] and be
able to copy the *main* XPe image over to the target storage.
Obviously, for wiping out disk you can use delete [CMD's *del*] or format or diskpart or whatever tool you like and/or required
by your system security spec (maybe you need to clean every single cluster on the hard disk before the restore).
As I already pointed out earlier it is better to use robocopy for copying files than xcopy. There are other great and reliable
3rd party tools but not free (e.g., xxcopy). Or you can pull the image down from a network if acceptable and exists.
If the restoration image needed to be compressed and/or encrypted (for saving some space or to use an unvulnerable encryption)
you could always use either one of Resource Kit or PE tools or some other 3rd party tools (freeware is preferable, of course). The
cabarc is an example here. Or you can use built-in NTFS compression if the underlying restoration media allows that (e.g., UFD or
HDD approach).
Another point should be made about the restore-bootable image itself. If PE used, you may want to remove all the unnecessary extra
packages from the image before sysprep. If XPe based, just create a small footprint image with a very limited number of components
to support basic operations such as file system operations and/or network [MS or base TCP/IP] and/or whatever custom component
dependencies you are adding there. Likely the image should be Minlogon based with either a custom shell or CMD shell. No need to
resolve all the platform drivers in that image since you can always disable the hardware wizard and PnP popups.
 
Back
Top