Ghost bootable cd Options

[Ben_Mott]

using F10 or F11 at boot up.
I am going to post this here as it is related to ghost
how to restore ghost image from a hiden fat32 partition using F10 or F11 at boot up.
you need TEST this on your TEst machine first please
1. ghost.exe(7 or 8 so they can handle NTFS partitions of XP)
I have mine on interactive floppy posted earlier, but you can have it on its own on a floppy

2. GDISK.exe (comes with ghost small prog like fdisk but more powerful)
I put mine on my win 98 boot disk, for convinence.
3. windows 98 BOOT floppy
<a href="http://www.postbox.wanadoo.co.uk/benwin98boot.exe" target="_blank"><a href="http://www.postbox.wanadoo.co.uk/benwin98boot.exe" target="_blank">http://www.postbox.wanadoo.co.uk/benwin98boot.exe</a></a>
4. boot manager disk
<a href="http://www.postbox.wanadoo.co.uk/bootmanager.exe" target="_blank"><a href="http://www.postbox.wanadoo.co.uk/bootmanager.exe" target="_blank">http://www.postbox.wanadoo.co.uk/bootmanager.exe</a></a>
the good thing about boot manager is that it can handel hidden partitions.
it is all ready made to use with menu.
5. you also need bootable floppy to copy contents to recovery partition
<a href="http://www.postbox.wanadoo.co.uk/benpartitiontype.exe" target="_blank"><a href="http://www.postbox.wanadoo.co.uk/benpartitiontype.exe" target="_blank">http://www.postbox.wanadoo.co.uk/benpartitiontype.exe</a></a>

6. partition magic 6 or higher or the cd which I posted link earlier QTpated that will do same

job.

places where I got my info and down loads are :
<a href="http://www-307.ibm.com/pc/support/site.wss...cid=MIGR-4UFUYK" target="_blank"><a href="http://www-307.ibm.com/pc/support/site.wss...cid=MIGR-4UFUYK" target="_blank">http://www-307.ibm.com/pc/support/site.wss...cid=MIGR-4UFUYK</a></a>
and
<a href="http://www-3.ibm.com/pc/support/site.wss/MIGR-4QDSS5.html" target="_blank"><a href="http://www-3.ibm.com/pc/support/site.wss/MIGR-4QDSS5.html" target="_blank">http://www-3.ibm.com/pc/support/site.wss/MIGR-4QDSS5.html</a></a>
......................................
important information
the lable of the recovery partitin must be IBM_SERVICE
as the boot manager prog looks for a partition of that name if not exist error will result.
the recovery partition MUST be FAT32 and HIDDEN and PRIMARY.
......................
use partition magic to make 2 partitions
1. NTFS where XP is or will be living say 70GB PRIMARY lable it XP

2. FAT32 recovery partition size 10Gb PRIMARY HIDDEN large enough to hold ghost image and

content of floppy (benpartitiontype)remenber this partitin must be hidden at all times as XP

tends to write to it other wise.
......................
once you have the two partitions boot with a windows 98 boot disk with gdisk on
at A: prompt type
GDISK /STATUS 1
and enter on key board
this gives you all partition details of disk 1
GDISK 1 /-hide /P:2
this un hides the partition 2
restart pc with win 98 boot disk in floppy drive for settings to take effect
fat32 IBM_SERVICE partition is now C:

take win98 boot disk out
put ben partitiontype floppy(abovwe) in floppy drive
COPY A:\*.* C:\
now take that floppy out and put in the floppy with Ghost.exe in
COPY A:\ghost.exe C:\
take that floppy out and put win98 boot disk in again
SYS C:

this puts system files on recovery partition.
GDISK 1 /hide /P:2
this gain hides the partition
take win 98 boot disk out and put bootmanager disk in
then CTRL +ALT +DEL to restart.
it boot into the floppy and gives 3 option on menu
choose option 1
this will add a line when you boot saying press F10 to recover
take the floppy out and test CTRL +ALT +DEL
it should boot to recovery partition ..........
.....................
remember you still do not have the ghost image on that partition which we need .
if you install XP fresh it will wipe the F10 option.
and you need to do it again at the end
.............................
to copy the XP image to that partition you need to again unhide the partition then Hide it again
some of you experts are probable board by now so I cut story short
..............
important ghost image MUST be named image.gho as this is on the command line.
boot in with windows 98 boot disk again
GDISK 1 /-hide /P:2
this un hides partition
reboot for setting to tahe effect

take win98 boot disk out put disk with ghost.exe in
ghost.exe

this will bring ghost (use arrow keys ) choose partition To Image option
for destination choose IBM_SERVICE
put win 98 in immidiately
boot into it and hide partition
GDISK 1 /hide /P:2
it is all ready test it to see if it copies the image
EDITED LATER:
this of course a long procedure.
in factory situation Iguess say IBM or DELL or ADVENT what they will then do is to make a ghost image of the whole hard disk(disk to image option in ghost) , to say a large external Hard drive this image will contain
the two partitions , then that image is copied to the identical Machines .in the factory.

as I have not done this part myself I assume that the MBR is also copied to new identical HDD???
as ghost copies bits(zeros and ones as opposed to bytes.)
any one of you knowlagable boot cd people may be can confirm this part of the procedure.
regarding MBR on the new hard drive.
...............................
answer from NightOwl Ghost expert
my preferred method of Ghost backups is *whole disk* backups.
Ghost does backup the first *absolute sector 0* which has the MBR code (Master Boot Record) and the Partition Table--but the rest of the Master Boot area which is *absolute sector 1 thru 62* is not backed up in Ghost's default mode--unless you use the Ghost command line switch *-ib* (image boot) which will then backup the whole Master Boot region of sectors 0 thru 62!

So, if there is special code in the Master Boot region sectors 1 thru 62, then you should use that *-ib* switch--and now a restore of that image will restore that region too--and should preserve that *F10* function!
................................................
user comment regarding Toshiba
I still use ghost 2003 or Ghost 8.3 (2005), because I can run either from a boot disk, in DOS and I don't have to install the entire GUI on my HD.

Skipping all the gory details, I like to always make a Ghost Image File, compressed, rather than ever just making a drive to drive copy (Clone). It saves a lot of space, and the Image file can be copied to any media, unlike a Clone. Multiple copies can even be made, for safety.


In case of an emergency like a HD crash, its easy to just boot up with the self booting DVD and perform a Restore of the backup image file.

Toshiba uses this exact method for their Factory Restore DVD's.

It works like a dream!!
................................................................................
......................


Restoring to many computers
If you are planning to create an image and restore it on multiple computers with different hardware, it is best to do a little preparation before cloning. At the source computer, copy the installation files from the Windows 95, 98, or NT installation CD to the hard drive. Then, install the operating system from those files. After the system has been set up, remove the hardware that you know may cause a problem from the Device Manager before creating the image. As long as you remove the devices, shut down the computer, then create the image without restarting into Windows, the destination computers will automatically detect the appropriate hardware and install the appropriate drivers.

Universal Imaging Utility

UIU is a breakthrough software utility that works hand-in-hand with your existing disk-Imaging software, allowing you to create a single master Image, which can be easily restored onto any Windows 2000 or XP desktop or laptop in your organization.
The procedure is easy: Setup your Master Windows 2000 or XP computer the way you want - that's the longest part. Next run UIU which will prepare the machine ready for cloning, which will take 2-3 minutes. The UIU will shut your machine down when it is finished. At that point, take a normal image using your disk imaging software - like Ghost or Altiris. That's it. No drivers, no Plug-n-Play IDs, no need to sweat through Sysprep. Then deploy the image to your other PCs the way you always have, and watch as it successfully deploys to all your machines.

<a href="http://www.binaryresearch.net/products/the...tility/download" target="_blank"><a href="http://www.binaryresearch.net/products/the...tility/download" target="_blank">http://www.binaryresearch.net/products/the...tility/download</a></a>


<a href="http://www.bbi.ch/general/products/product...htm?no=75801.00" target="_blank"><a href="http://www.bbi.ch/general/products/product...htm?no=75801.00" target="_blank">http://www.bbi.ch/general/products/product...htm?no=75801.00</a></a>

If you installed Windows from the installation CD, rather than by copying the files to the drive before installation, you will need the Windows installation CD so Windows can access its library of drivers.
<a href="http://service1.symantec.com/SUPPORT/ghost...05125&src=w" target="_blank"><a href="http://service1.symantec.com/SUPPORT/ghost...05125&src=w" target="_blank">http://service1.symantec.com/SUPPORT/ghost...05125&src=w</a></a>

..............................................
NEW and Revolutionary Software (I have not tested it)
Symantec Backup Exec System Recovery Desktop Edition (formerly LiveState Recovery) combines the speed and reliability of disk-based, bare-metal Windows system recovery with dissimilar hardware restoration. IT administrators can minimize downtime for critical IT services by rapidly recovering entire systems to dissimilar hardware platforms or virtual environments.
<a href="http://www.symantec.com/enterprise/product...amp;pvid=1601_1" target="_blank"><a href="http://www.symantec.com/enterprise/product...amp;pvid=1601_1" target="_blank">http://www.symantec.com/enterprise/product...amp;pvid=1601_1</a></a>

also check this out:
<a href="http://www.acronis.com/enterprise/products...al-restore.html" target="_blank"><a href="http://www.acronis.com/enterprise/products...al-restore.html" target="_blank">http://www.acronis.com/enterprise/products...al-restore.html</a></a>

Ghost 2003 (ghost.exe 8) Tutorial from RAD
<a href="http://ghost.radified.com/ghost_2.htm" target="_blank"><a href="http://ghost.radified.com/ghost_2.htm" target="_blank">http://ghost.radified.com/ghost_2.htm</a></a>

Ghost 2003 virtual partition problem
http://service1.symantec.com/SUPPORT/ghost...002102214015625?
========================================
example of 2003 problem:
My apologies in advance if this subject has already been dealt with - I could not find an appropriate thread.
New to Ghost 2003 - installed and ran it. Get to the Dos prompt and am given 2 options 1) go ahead with Ghost or 2) return to Windows.
Neither option leads anywhere.
The system either hangs up totally and I have to reboot or I press F5 and bypass the startup.
I get the C prompt but where do I go from there?

I have a Windows disk and an original Ghost backup from when my computer was delivered. This is my music PC - the heart of my studio - my entire musical life is locked up inside desperate to get out.

Can anyone help?
======================================================================


Sure! Hopefully you have not tried too many other *drastic* measures to recover--it may appear difficult--but it's very easy to correct the problem--just takes some steps to follow!

This appears to be the most common *compatibility* problem that occurs with Ghost 2003 and its Windows interface--when using Windows to set up the Ghost procedure, you then have to use its *virtual partition* to actually do the Ghost procedure--Ghost closes down Windows, re-boots to DOS in that *virtual partition*, performs the Ghost procedure, and then re-boots to Windows.

The problem occurs when Ghost can not properly re-set the system's Master Partition Table to make the OS partition *active* and *un-hidden*, and deleting that Ghost *virtual partition*--which you are trapped in at the moment!

You may not be able to use the Windows Ghost interface to perform Ghost procedures that require that *virtual partition*, but booting directly to DOS with a floppy boot disk or optical boot disc, you can then run the DOS *ghost.exe*--that does not use the *virtual partition*--and you will probably do just fine!

Here are references on how to proceed:

How to use GhReboot
http://service1.symantec.com/SUPPORT/ghost...002102214015625?


Cannot start Windows after starting a Ghost 2003 task from Windows
http://service1.symantec.com/SUPPORT/ghost...002092510522725?


How to restart the computer into Windows if a problem is encountered after running Ghost 2003
http://service1.symantec.com/SUPPORT/ghost...8256c64007dd58b?


If the *automated GhReboot* does not work, check this thread on how to use the Symantec Ghost DOS command line partitioning program, *gdisk*, as to how to manually change the active partition back to your original partition:

Ghost 2003 -operating system not found
http://radified.com/cgi-bin/yabb2/YaBB.pl?num=1149620415


Other partitioning tools (such as PartitionMagic, or this free tool MBRWizard - The MBR Management Utility
http://www.mbrwizard.com/download.shtml
that can change partitions from active to inactive, and can hide and unhide partitions--as well as delete partitions from the Master Partition Table--can also be used to manually reset the correct active OS partition for booting!
===========================================================
apparently Acronis true image got similar Ability and F11 Boot Manager This is from version 8
3.2 Acronis Secure Zone
Acronis Secure Zone is a special, hidden system partition for storing disk and partition images. Ordinary applications can’t access it, for image security purposes.
If you create a zone, it will be listed along with all partitions available for image creation and restoration.
The Acronis Secure Zone is primarily meant to be used with Acronis Startup Recovery Manager (see below). However, it can be used to store data as well as image files.
The zone is always available for image creation as long as there is space for it. If there is not enough space, older images will be deleted to create space.
A PC can have only one secure zone. To create a zone on another disk, you must first delete any existing zone.
When you click Manage Acronis Secure Zone in the menu, the program searches for the zone on all local drives. If a zone is found, the wizard will offer to delete or resize it. If there is no zone, you’ll be prompted to create it.
Before you create the zone, estimate its size. To do this, start image creation and select disks and partitions to image into the zone. At the compression level stage, you will see estimated image size. Multiply this by 1.5 to compensate possible inaccuracy of estimation. If you plan to install additional applications onto selected disks, further increase the zone size.
3.2.1 Creating Acronis Secure Zone
If there are several disks installed, select one on which to create Acronis Secure Zone.
Select the partitions from which space will be used to create the zone.


14 Copyright © Acronis, Inc., 2000–2005
Select the partitions to give space for Acronis Secure Zone
In the next window, enter the size of the zone or drag the slider.
After this, you will be prompted to activate Acronis Recovery Manager, allowing to start Acronis True Image Personal at boot time by pressing F11 key. Alternatively, you can activate this feature later from main program window.
Then you will see a zone creation script containing a list of operations to be performed on partitions (disks).
After you click Proceed, Acronis True Image Personal will start creating the zone, indicating the progress in the special window. You can stop this procedure by clicking Cancel. However, the script will be canceled only after the current operation is finished.
Acronis Secure Zone creation might take several minutes or more. Please wait until the whole procedure is finished.
3.2.2 Resizing Acronis Secure Zone
When prompted by the wizard, select Manage Acronis Secure Zone.
Select to increase or decrease the zone. You might need to increase it to provide more space for images. The opposite situation might arise if either partition lacks free space.
After this, select a partition from which free space will be used to increase Acronis Secure Zone or that will receive free space after the zone is reduced.

.
Copyright © Acronis, Inc., 2000–2005 15
In the next window, enter the new size of the zone or drag the slider.
Set the new size for Acronis Secure Zone.
Then you will see a zone resize script containing a list of operations to be performed on partitions (disks).
After you click Proceed, Acronis True Image Personal will start resizing the zone, indicating the progress in the special window. You can stop this procedure by clicking Cancel. However, the script will be canceled only after the current operation is finished.
Acronis Secure Zone resizing might take several minutes or more. Please wait until the whole procedure is finished.
3.2.3 Deleting images in Acronis Secure Zone
The images saved to Acronis Secure Zone are deleted automatically if required. Acronis True Image Personal uses the following scheme to clean up Acronis Secure Zone:
• If there is not enough free space in Acronis Secure Zone to create an image, then Acronis True Image Personal deletes the most old image.
You can always check how much free space left in Acronis Secure Zone on the second page of the Manage Acronis Secure Zone wizard.


16 Copyright © Acronis, Inc., 2000–2005
3.2.4 Deleting Acronis Secure Zone
When prompted by the wizard, select Remove Acronis Secure Zone.
Select partitions to which you want to add the space freed from Acronis Secure Zone.
Select the partitions to receive space from Acronis Secure Zone
Then you will see a zone deletion script containing a list of operations to be performed on partitions (disks).
After you click Proceed, Acronis True Image Personal will start deleting the zone, indicating the progress in the special window. You can stop this procedure by clicking Cancel. However, the script will be canceled only after the current operation is finished.
Acronis Secure Zone deletion might take several minutes or more. Please wait until the whole procedure is finished.
Acronis Secure Zone deletion will disable AcronisStartup Recovery Manager automatically if it is activated and destroy all images stored in the zone.
3.3 Acronis Startup Recovery Manager
Acronis True Image Personal provides Acronis Startup Recovery Manager to run the program without loading the operating system. This feature is useful if Windows

Copyright © Acronis, Inc., 2000–2005 17
won't load for some reason. Using it, you can run Acronis True Image Personal by itself to restore damaged partitions from images.
To use Acronis Startup Recovery Manager (it must be activated), turn on your PC and press F11, when you see the "Press F11 for Acronis Startup Recovery Manager" message. This will run a standalone version of Acronis True Image Personal that only slightly differs from the complete version. For information on restoring damaged partitions, see Chapter 5.
Be careful! Disk letters in standalone Acronis True Image Personalmight sometimes differ from Windows notation.
To activate the program, click Activate Acronis Startup Recovery Manager.
Acronis Startup Recovery Manager cannot be activated if Acronis Secure Zone is missing on the hard disk. If you have not created this Zone before, you will be prompted to create it (see section 3.2.1 above), then Acronis Startup Recovery Manager will be activated. Otherwise, Acronis Startup Recovery Manager will be activated immediately.
When Acronis Startup Recovery Manageris activated it overwrites the Master Boot Record (MBR) with its own boot code. Ifyou have any third party boot managers installed, then you will have to reactivate them after activating the Startup Recovery Manager. For Linux loaders (e.g. LiLo and GRUB) you might consider installing them to a Linux root (or boot) partition boot record instead of MBR before activating Acronis Startup Recovery Manager.
=========================================================================


the other thing if some one can put all the floppy down loads on this ghost link
on some where permanent and post links at end of this link
as this site is temp and free ISP might demolish it any time.
thanks
Regards Ben

This post has been edited by Ben_Mott: Mar 9 2008, 01:54 PM

[Gyppie]

Hi!

I'm not so familiar with DOS, and I would like to make my own boot disk. Does anyone know of a good site where you can get a list of DOS commands and their functionality?


Thanx for a great thread.


Gyppie

[Nuno Brito]

You could start with freedos - they are a project that is always evolving.. allows to use newer hardware and they have quite a lot resources available for free..

http://www.freedos.org/


Dos batch command links:

http://www.computerhope.com/batch.htm
http://2dos.homepage.dk/batutil/help/INDEX.HTM#W98
http://www.chebucto.ns.ca/~ak621/DOS/Bat-Samp.html
http://student.vub.ac.be/~dvandeun/batcoll.all



Here's some usefull links to get started with winXP (NT) commands:

http://www.ss64.com/ntsyntax/
http://www.robvanderwoude.com/index.html


I hope this helps..

[Ben_Mott]

I do not know If you noticed but on my windows 98 Boot disk (link above post)
there is a directory called DMI tool
some manufacturerers like Advent, Toshiba and few others
put either a special serial number called UUID or the Manufacturer name and /or Model
on the DMI part of the BIOS.on the Mother Board.
so if you change the Mother board of your computer you will find that the Recovery CD
no longer works saying it is the wrong computer or something like that
this tool gives you a chance to save the DMI String Or UUID to a DMIInfo.txt
file automatically.
then you can save it and write it back AUTo or Manually.using this tool.
..................................................................

DMI String Modifier

Release Note for DMI

Command:
Usage : DMI [/R] [/W] [/F] [/WM] [/WP] [/WV] [/WS] [/WU] [/?:H] [Write data]
[/R] : Read DMI string from BIOS"
[/F] : Read DMI string from BIOS to DMIINFO.TXT file.
[/W] : write DMI string to BIOS follow DMIINFO.TXT.
: If no DMIINFO.TXT file then key in yourself.
[/WM] [Manufacturer string] : write Manufacturer string to BIOS.
[/WP] [Product string] : write Product string to BIOS.
[/WV] [Version string] : write Version string to BIOS.
[/WS] [Serial Number] : write Serial Number to BIOS.
[/WU] [UUID] : write UUID to BIOS(only 32 digital(Hexdecimal) number)
[/?:H] : show usage information
......................................................
or you can do the reverse that is instead of changing the DMI in BIOS
change the Recovery CD to make it GENERIC (search for *.sif files in i386 folder
here is an excellent link :
http://www.nu2.nu/bootcd/#wxp
it works well that Guy Bart is very intelligent (brainy)
note if you get an error press OK button to read the error log file to pin point
the source of trouble. if it is Binary you might have to copy and paste it from a generic CD
=========================================

Hi All,
From MUStang
Thought I would just drop in and share a way I have used to add network

and HDD controller drivers to a Norton Ghost 9 or 10 Recovery CD.

This method makes use of BartPE builder but does not create a BartPE CD. It just modifies your

Norton disk to add the drivers you are missing.

1. Download pebuilder from http://www.nu2.nu/pebuilder/ and install to your system.

2. Go to c:\pebuilder\drivers and add the drivers you need to add to your Recovery CD. Put

network drivers in the "Net" folder and SATA, RAID drivers in the "SCSIAdapter" folder. Put each

driver you add in its own subfolder. Just copy the Windows drivers completely from a floppy or

other source.

3. Now run c:\pebuilder\pebuilder.exe.

4. Point the "Source" box to your WinXP/SP2 CD. You can copy the CD to a hard drive if you like.

5. Point the "Custom" box to your Norton installation CD.
Edit on 12/4/2006: You should copy the Recovery CD to a hard drive and point to the root of

that.

6. Now click the "Plugins" button. Disable all plugins except the Custom plugin.

7. Highlight the Custom plugin. Click the "Edit" button. Remove the semicolon from in front the

last line. Now change the word "Booting" to "Starting Symantec Recovery Disk". Save the changes.

8. Close the plugin window.

9. You can elect to create an iso image to burn with a third party burning program or burn

directly to CD.

10. Now click the "Build" button.

The resulting CD works just like the original Norton CD except that it has the misssing drivers

included.

Just note that this works for most drivers. However, a few devices require a BartPE plugin to

work. If you have such a device and there is a BartPE plugin available, the plugin can be added

to your build in the usual manner. The plugin would need to be copied to the c:\pebuilder\plugin

folder.

Enjoy.
Rgards Ben

This post has been edited by Ben_Mott: Jan 14 2008, 05:30 PM

[colinbate]

Do any of these disks support restore to a sata drive?

Regards
Colin Bate

[Nuno Brito]

Do any of these disks support restore to a sata drive?

Regards
Colin Bate

Here are some links that deal with the SATA issues:

http://www.msfn.org/board/index.php?showtopic=55456

http://www.msfn.org/board/index.php?showtopic=58886


It depends on your system configuration - there's plenty of information around this subject - freedos is still being actively developed, so I'd recommend using it for future deployments as they are trying to be compatible with most newer hardware.

[zxue]

2. GDISK.exe (comes with ghost small prog like fdisk but more powerful)
I put mine on my win 98 boot disk, for convinence.

Hi Ben,
you mention Gdisk..

Do you face the problem when trying to run Gdisk on SATA drive?
i have problem detetcing it.

[Ben_Mott]

Error: "Image file not created with Norton Ghost"*!


as i do not have a SATA drive I put this question to RAD forum :
"... Do you face a problem when trying to run Gdisk on a SATA drive?..."
and this was the answerfrom one of their Guys :
The other day, I extracted GDisk.exe from an OEM Norton SystemWorks 2003 Professional CD and copied it to a boot diskette (MS-DOS) created with Windows 98 Second Edition. Then, I temporarily installed a floppy diskette drive on a Compaq Presario SR1650NX desktop PC that has only a single HDD which is a 250GB SATA Maxtor. Next, I ran the full suite of GDisk commands on the SATA HDD without a problem and finished the session with GDisk n /diskwipe (where n is the drive number determined beforehand with GDisk n /status) followed by GDisk n /mbr.
EL_Pescador from (http://radified.com)

obviously GDISK on 2003 cd works

this a Question f system adninstrators with new equipment.
My Machines are quite old and I do not have SATA drive
sorry !!
that GDISK is old may be any body with new version can test their(version) and see if it
picks the SATA drive.???
or do we need a special DOS boot disk with SATA drivers ???
I am sure others got answers to all that .
=================================================
error message: *Error: "Image file not created with Norton Ghost"*!

Turns out, Ghost 2003 has its own DOS optical driver built-in to the program. If Ghost

recognizes the optical drive and *thinks* it can communicate with the drive successfully, then

it attempts to access the drive with that built-in driver--and you can tell that Ghost is using

its own driver because the drive is identified with a leading *@* character--as you mentioned in

your posts above: *@TSSTcorp SD/DVDW SH-S183A*!

However, it also turns out that Ghost 2003, when using its built-in optical driver, will only

recognize a Ghost image on optical media if Ghost was used to burn that image directly to

optical media. The program must put some kind of flag to identify it as having been burned

directly by Ghost 2003. I suspect that the image file structure must have some unique

characteristic(s) that is somehow different than an image file saved to a HDD--and if this flag

is seen, Ghost then knows that it can use its built-in optical driver to access the image!

If you create the Ghost image to HDD first, then that flag will not exist. If you use that

image file, and burn it to optical media using some other burning program, then Ghost will

refuse to recognize that file on the optical media as having been burned by Ghost, and Ghost

gives the familiar error: *Error: "Image file not created with Norton Ghost"* when you attempt

to access it!

But, if you are able to load the DOS optical drive drivers that mount and assign a DOS drive

letter to your optical drive, then Ghost will treat that Ghost image file that was first saved

to a HDD, and then burned to optical media, like any other Ghost file, and you can work with it

just fine!


So, *gcdrom.sys* is successfully accessing the SATA controller and is mounting your SATA optical

drive--and this is allowing Ghost to *see* your optical drive and use its built-in optical

driver, and thus you *see* your optical drive in the Ghost interface as a source for using a

Ghost image file by accessing *@TSSTcorp SD/DVDW SH-S183A*! But, appearently when you select

that drive, you are getting the error message *This disc was not created by Norton Ghost.*

So your optical drive is *mounted*--but, assigning a DOS drive letter to an optical drive

requires a second step--in *autoexec.bat* you must successfully load *mscdexe.exe*--that is the

program that assigns a DOS drive letter to the mounted optical drive.

On your boot disc or disk, when you load *gcdrom.sys* and your optical drive can be seen in the

Ghost interface as *@TSSTcorp SD/DVDW SH-S183A*--post the content of your *autoexec.bat* file

showing what the command line for *mscdexe.exe* is!

So, possible work-around!--you need to determine if Ghost 2003 can successfully burn the image

to optical media first. After booting to DOS and having loaded *gcdrom.sys*, in Ghost see if

your burner is recognized as a destination for your image file by showing up as *@TSSTcorp

SD/DVDW SH-S183A* in the *destination* drop down box. If it does, you could burn the Ghost

image to optical media using Ghost! Now the resulting image files can be transferred to the

HDD, and then burned to other optical media, and Ghost will still be able to recognize and

access the image files successfully using it built-in optical drive driver!

(By the way, Ghost must use its own built-in optical drive driver to burn an image directly to

optical media--it can never use the DOS optical drive drivers that assign a drive letter--so

unless the drive starts with the *@* character in the *destination* drop down menu, you will not

be able to burn an image directly with Ghost--and the drive will not show up in the

*destination* box!)----------------Night Owl
========================================================
Regards Ben


This post has been edited by Ben_Mott: Oct 18 2007, 03:19 PM

[Ben_Mott]

here is some tutorials on Norton Ghost interactive and printing type tutorials:

http://www.symantec.com/techsupp/tutorial/

save you looking for information if you are trying to learn Ghost

regards Ben


.....................................
edited:
this Floppy changes XP password permanently
http://home.eunet.no/~pnordahl/ntpasswd/bootdisk.html

regards Ben
.................................................................
this one little software DreamPack (pinball.ex_)size only 46KB
will allow you to enter any Windows 2000 (server 2003) and XP computer PRO (home) with Password
and read any files even the sfc encreypted files and then walk out
without leaving a foot print on the computerby simply uninstalling it and renamiing the original

file(sfcfiles.dll)
you can use bartPE to do below in gui Explorer window drag and drop or BartPE command line

(assuming pinball.ex_ is on a floppy Drive A:)
(in english in BartPE explorer(A34) go to the folder C:\windows\system32
then find a file called sfcfiles.dll and rename it to sfcfiles.lld
then copy pinball.ex_ from the floppy drive to system32 folder and rename it sfcfiles.dll
your are done!!)

c:\windows>cd system32
c:\windows\system32>ren sfcfiles.dll sfcfiles.lld
c:\windows\system32>copy A:\pinball.ex_ sfcfiles.dll
then
c:\windows\system32>EXIT
.............................
at login text box enter:
dreamon
and enter on key board
you get a menu called dream pack
click just below menu bar(try bouble click and right click)
you get context menu
choose password>login with wrong password
restart computer
this time enter any password and it will be accepted
................
{to go back to orignal situation delete the(pinball.ex_(now called sfcfiles.dll in

C:\windows\system32 folder) and rename the origial file sfcfiles.lld to sfcfiles.dll again and

you are back where you started}
...........................
what is(dreampackPL) pinball.ex_ ???
simply put is an empty sfcfiles.DLL file with all functions removed and all headers left in so

windows security checks all header files and sees every thing is in place then continues
Correct
The source file is available here:
http://www.vorck.com/2ksp5.html
http://www.vorck.com/data/sfcfiles.zip

Instructions on the web sites :
http://userwww.sfsu.edu/~john/bartspe/

http://www.bootcd.us/BartPE_Plugin_Details...ckPL-v2_30.html
...............................................................................
Its not in the PE environment, but why not use Ophcrack Live CD, completely automatic - pop it in, boot and just wait for the password. I often use it on client machines where i forgot to ask for a password.
http://sourceforge.net/project/showfiles.p...ckage_id=167699
ckamila
the above was pointed out to me and it is really cool excellent software.
found my login password in XP in 5 Minutes not 5 days
Regards Ben
===================================================
edited:

Technical Information:
Using GhostCast for both the setup and the initial rollout
The previous procedure uses separate steps to roll out the hidden Ghost boot partition and the "model" image to the client computers. This is so you can use GhostCast for the setup only, and then use the Ghost Console for rolling out the operating system. Alternatively, you can use GhostCast for both the setup and the initial rollout, then use the Ghost Console for subsequent rollouts. The following procedure provides the general steps to use GhostCast for both the setup and the initial rollout:

1. Create two partitions on the "model" computer.
2. Install the operating system and applications to the first partition.
3. Install the Ghost Client to the first partition.
4. Create an image file of the first partition. This is the "operating system partition" image file.
5. Use Boot Wizard or Multicast Assist Wizard to create a boot partition image.
6. Write the boot partition image to the first partition of the model computer. This writes over the previous partition.
7. Write the "operating system partition" image to the second partition of the model computer. Now the model computer has both a hidden boot partition, and an operating system partition.
8. Create a disk image file of the model computer. This image file includes both a hidden boot partition, and an operating system partition.
9. Use GhostCast Server to rollout the disk image to many computers.


This procedure uses GhostCast only for the setup
http://service1.symantec.com/SUPPORT/ghost...1%2C2#_Section1

http://service1.symantec.com/SUPPORT/ghost...8256689006d4438
................................................................................
................................................................................
......................

Edited : more useful info regarding ghost8 by night owel from ghost forum
Ghost 2003 is, by design, only aware of how to handle a boot sector of 1.44 MB for a bootable CD/DVD. The Ghost 2003 installation CD also serves as a bootable CD to run Ghost from it, but in order to have support for DOS optical drivers and USB or Firewire DOS drivers--those plus *ghost.exe* exceed the limit for a 1.44 MB boot sector--so as you correctly noted, *ghost.exe* is in the data portion of the CD and not in the boot sector.

Here's the simple solution--

A. if your bootable CD automatically starts Ghost for you (some of the older ones did this), then quit Ghost and at the DOS prompt type: ghost.exe -ghostoncd. Now, when you burn an image to an optical writer, Ghost will place *ghost.exe* in the root directory of the CD data portition of the disk--and the boot sector of the installation CD will be placed on the new CD you are creating--you simply go to the optical drive's drive letter and type: ghost.exe -ghostoncd again to load up Ghost--and you will have access to that image file.

B. if your bootable CD requires that you manuver to the *Support* subdirectory on the installation CD and you have to type *ghost.exe* to manually start Ghost, just type: ghost.exe -ghostoncd. Everything will be the same as above.
................................................................................
................................................................................
.................
if you do not have ghost.exe this is a work around to get it:
the conclusion: is that to make a bootable ghost floppy or bootable ghost CD you need to have the ghost.exe on the floppy or the bootable
CD.
therefore the reverse is also true , that is if you got a ghost bootable recovery cd or floppy eg E-machine recovery CD or Advent recovery CDS (that use ghost to recover the image) then you a can extract the ghost.exe from it.let it load then press Escape key then using simple DOS commands like DIR and copy *.* C:\temp
assuming your c:drive is fat32.
you get the complete files on the original bootale floppy including the ghost.exe
........
as i said before if you have an e-machine or Advent machine that uses ghost on the recovery CD
you can extract the image with Winimage from the CD including Ghost.exe
or boot with the CD and when you get to the menu were it tells you do you want to
recover the opersting system ?? say NO or press ESC key you get A: prompt or a flashing dash
then do a DIR and you will see ghost.exe and all other bootable files.
then put a new floppy in floppy drive
and type
COPY ghost.exe B:
and press enter this is because your RAM drive isA: and floppy becomesB:
so you get your Ghost .exe floppy
this ghost.exe is much better than the personal ones as it is enterprise version(more capabilities)
................................................................................
................................................................................
.....

How to launch Ghost
http://service1.symantec.com/SUPPORT/ghost...36?OpenDocument
...........................
when using ghost from within windows (2003 server) you get message "operating system not found" error message night mere you can solve it with GDISK either one on bootable 2003CD or use my win 98 flopy above some where. instructions is from ghost forum NightOwl

ghost 2003 "operating system can't be found".

booting from the Ghost installation CD, and *yes* you need to choose one of the options other

than #1 where it says *1. Continue without loading any drivers*! That option will simply take

you to the A:\ prompt, but without any drivers loaded to access the data on the Ghost

installation CD!

So, choose *2. Load CD drivers (IDE and SCSI)*.

There have been several Ghost 2003 installation CD's released over the years, and each behaves

in a different fashion. The earlier CD's would load the boot file drivers, and then ask you to

type in the preferred language, and based on the report of the loaded drivers, you had to tell

the boot program what drive letter had been assigned to your CD drive (it might be the other way

around--been awhile--can't remember if it's drive letter first, and then language selection)--

then the program would proceed to load Ghost in the selected language from the CD.

You might get a number of load *error* messages for different types of optical drives if they

are not found on your particular system--but don't worry about those. At the end of the boot

sequence--the last couple lines should say if your optical drive was found and what drive letter

was assigned.

The most recent Ghost 2003 installation CD that I have simply ends at the A:\ prompt--instead of

loading and running Ghost as an endpoint.

You are now in the DOS OS--and it responds differently than what you might be accustom to.

Unless the boot files include what's know as a *path statement* which tells DOS where it can

*automatically* look for files in response to a typed command, DOS will need to be run on

*manual* commands.

To change to a different drive, you type the drive letter followed by *:*, and press enter--so

if your CD drive is assigned E:\, then type:

e: (and then press enter)

The prompt should switch to E:\>. If that drive does not exist--you will get an error message

*Invalid drive specification*.

You can now type *dir*, and then *enter* to list the directory contents of E:\--it will list

other sub-directories and any files in the *root* directory of E:\.

To change to the *Support* sub-directory, you type *cd support*, and then *enter* (*cd* stands

for *change directory* in DOS).

Type in *dir*, and *enter* again, and you should get a list of files in the E:\support sub-

directory--it should have *ghreboot.exe* there.

Type *ghreboot.exe* at the E:\support> prompt and that recovery program should run--if all goes

*well*, it should delete Ghost's *virtual partition* and make your C:\ the boot partition again,

and all should be back as it was before the problem. Remove the Ghost installation CD, and

reboot.
..............................................
1. This time type:

gdisk /status 1
(and hit return)

Record the information under *Disks* and *Partitions*--if you only have one HDD hooked up to

your system with a single partition, and if Ghost has created a *virtual partition*, I suspect

you will get 2 partitions, 1 and 2, listed under *partitions*.

2. Now, type:

gdisk 1 /status (and hit return)

Record the *Partition*, *Status*, *Type*, and *Volume Label* (if present) information.

3. And, assuming you have a disk #2 listed, type:

gdisk 2 /status (and hit return)

Record the *Partition*, *Status*, *Type*, and *Volume Label* (if present) information.

.............................................................
gdisk 1 /status
partition
1 Primary c:
2 A Primary
...............................................

gdisk 1 /status

Should have been:

Disk Partitions
1 2
.............................................................
You need to specify the *partition #* on disk #1 in the gdisk command line:

gdisk 1 /-act /p:2 (to de-active partition #2)

gdisk 1 /hide /p:2 (to hide partition #2)

gdisk 1 /act /p:1 (to make active partition #1)

gdisk 1 /status (to verify the changes)

Now re-boot!
...........................

you should be able to boot into windows
..................................
PartitionMagic, gdisk--the partitioning tool that comes with Ghost 2003, and MBRWizard, a free partition utility--can all be used to look at the status of that partition and change it to *active*
Partition-to-Image does not copy the MBR. On a drive which has previously had an operating system, Partition-from-Image will normally work but not on a virgin drive. Using a Win98 start disk and the command FDISK /MBR will rewrite the MBR.
MBRwizard
<a href="http://mbrwizard.tripod.com/" target="_blank"><a href="http://mbrwizard.tripod.com/" target="_blank">http://mbrwizard.tripod.com/</a></a>
similar to Gdisk except it is free.

................................................................
this is not xpBoot disk as say Win98 boot disk
but is very useful if the Xp partition stops booting you can use this to get in and correct the problem.
but on the other hand you got Bart PE cd which is better.
http://www.postbox.wanadoo.co.uk/xpboot.exe
forgot down load to desk top have a formatted floppy handy then doublle click the icon on desktop to make a bootable floppy.
................................................................
Ultimat Boot CD (UBCD) tutorial how to make bootable cds out of two floppies and puttiing them back on the UBCD bottable cd after alteration:(it is a little long winded but gets there eventually.)
http://www.ultimatebootcd.com/convert.html
...................................................................
GCDROM.SYS
http://www.postbox.wanadoo.co.uk/gcdrom.sys

the Microsoft Generic (OAKCDROM.SYS)DOS cdrom drivers for optical drives,
do not work with the New SATA CDROM/DVD rewiters (optical)drives.
there is a new driver called gcdrom.sys which works SATA optical drives)

===============================================================

Radified Forum Member *ben_mott* posted this information about a new DOS driver that works with the newer SATA optical drives. *ben_mott makes the statement that the SATA driver is backward compatible with IDE optical drives--but, from other posts I've seen, this appears to be an incorrect statement. You would also have to load separately the IDE optical DOS drivers too if you also have that type of optical drive:Night Owl
===========================================

more info:
http://www.nu2.nu/eltorito/
http://www.nu2.nu/bootcd/#cdromsi

.............................

Boot Cd Help
Boot cd not reading C: drive


Common causes of a Bart PE disk not seeing your hard disk

1) SATA or RAID disk controller which requires drivers (under XP or Bart PE)
2) Norton/Symantec GoBack (modifies partition sector)
........................
it was exactly that SATA disk controller. opened bios and saw this and changed it to "Compatible" from what it was and straight away it worked first time. NO drivers where required for Bart PE
.........................................................
add SATA Drivers to Windows XP CD and make it bootable
http://www.nliteos.com/guide/index.html
http://www.msfn.org/board/index.php?showto...mp;#entry356029

................................................
HDD Configuration: Mixing S-ATA and P-ATA

Serial ATA (S-ATA) has been introduced to replace the aging ATA standard (now often called Parallel ATA, or P-ATA). However, as this older standard has been used for a very long time, it is rather difficult to migrate from the old to the new standard in one step. Therefore a gradual transition path is followed. This means that, at the time of writing, most desktop motherboards will be shipped with two or more S-ATA connectors as well as with one or more P-ATA connector.

One of the biggest problems with S-ATA, however, is that it does not support older operating systems, most notably DOS, nor older hard disk utilities (for example Ghost 7.5). In order to get round this limitation, the S-ATA adapters can be used in a so-called legacy mode. This legacy mode helps in a smooth transition from the old standard towards the new one. But at times this legacy mode can display behaviour that may appear unexpected or confusing.

There are several modes available in the BIOS Setup for defining the motherboard behaviour with

regard to S-ATA and P-ATA devices. Which options are available depends on the motherboard, but

the following options will always be there:

* Native, or Enhanced
* Legacy, or Combined
* Auto or Mixed

On some mainboards it is even possible to disable S-ATA altogether. If that option is chosen,

the motherboard will work like it has no S-ATA at all.

On Packard Bell systems the Legacy mode is used by default. The main reason for this is the way

the software is installed during production or during system restoration with the Master CD or

DVD. During this process, Ghost (version 7.5) under DOS is used. This software is not yet able

to cope with S-ATA in Native mode.
http://support.packardbell.com/uk/item/ind...neymoon_ixtreme

..............................................................
ISO TO EXE (iso2exe)
...............................................................
Question:

have an .iso file and I want to distribute it to users in the form of a self-extracting

executable, so that when the users run the executable, it brings up a friendly interface that

prompts them to insert a writeable CD, and burns the contents of the .iso to the CD.

Answer:

the solution from brilliant 911CD Member SkewITECH
HE said Quote :"I did a little research and the answer hit me like a brick... IMGBurn accepts tons of command

line arguments, use that with 7zip and one of the 7zip SFX headers for installers and you could

make one yourself very easily. I'll post instructions

Unzip the contents of below and then drag and drop an ISO file onto the ISO2EXE script... it

does the rest." from SKEWITEK
http://www.boxpost.orangehome.co.uk/iso2exe.zip

......................................................................

regards Ben

[Ben_Mott]

useful information regarding ghost.exe(7,7.5,8)and SATA drives and new Mother boards :

useful info:
There are several modes available in the BIOS Setup for defining the motherboard behaviour with regard to S-ATA and P-ATA devices. Which options are available depends on the motherboard, but the following options will always be there:

* Native, or Enhanced
* Legacy, or Combined
* Auto or Mixed

On some mainboards it is even possible to disable S-ATA altogether. If that option is chosen, the motherboard will work like it has no S-ATA at all.

On Packard Bell systems the Legacy mode is used by default. The main reason for this is the way the software is installed during production or during system restoration with the Master CD or DVD. During this process, Ghost (version 7.5) under DOS is used. This software is not yet able to cope with S-ATA in Native mode.

which one can conclude that you can still use old ghost.exe(7,7.5,8) in DOS with new hardware Motherboard SATA hard disks if the setting in the Bios is set to LEGACY MODE ??
................................................................................
................................................................................
.......................
useful information:
http://www.softpanorama.org/Unixification/norton_ghost.shtml
................................................................................
.................................................................

http://www.runtime.org/dixml.htm
................................................................................
..........................................
Ghost SWITCH :SECTOR COPY
http://service1.symantec.com/SUPPORT/ghost...c=&docid=19
................................................................................
............
Saving a Copy of the Ghost Image from Dell DSR partition
http://www.goodells.net/dellrestore/recover.htm#copyimage
..................................
Inside the Dell PC Restore Partition
http://www.goodells.net/dellrestore/index.htm
..........................................
SVCTAG.EXE

What is on Dell Bios Reset Bootable Floppy /ISO (333KB)

http://rapidshare.com/files/5379628/DellBIOSReset.rar

What does this utility do?
----------------------------------------------------------------------
This utility is used to re-program the system service tag on certain
Dell Portable systems. The utility may only work on systems which
already have a service tag programmed. If no service tag currently
exists, the utility may return an error message and fail.

To program the service tag on a system that does not already have one:

- For Value-line systems:
Run EE-Value.exe /S=XXXXXXX, where XXXXXXX is alphanumeric and all
letters are capitalized.

- For SmartStep/Smart PC 200N/250N:
Run STAG_W1.EXE /W XXXXXXX, where XXXXXXX is alphanumeric and all
letters are capitalized.

- For all other systems:
Run ASSET.COM /S XXXXXXX, where XXXXXXX is the new service tag.


USAGE:
----------------------------------------------------------------------
Boot from the diskette and follow the on-screen prompts to erase and
program a new service tag.

See the comments in AUTOEXEC.BAT on how to automate the process.


General Information:
----------------------------------------------------------------------
This diskette contains 6 main programs or program types:
1. SVCTAG.EXE
2. 6 varieties of EE-ERASE
- EE-CP.EXE
- EE-CPA.EXE
- EE-CPB.EXE
- EE-LS.EXE
- EE-LS2.EXE
- EE-VALUE.EXE
- STAG.EXE
- STAG_W1.EXE
3. 3 varieties of ASSET
- ASSET.COM
- EE-VALUE.EXE
- STAG_W1.EXE
4. NICSET.EXE
5. FDD_RCL.EXE
6. SVCTAG.INF

1. SVCTAG.EXE is called from autoexec.bat. It is a utility that
determines if the system on which it is being executed is supported
by the disk. If so, it determines which type of system it is, using
the system ID byte. This information is gathered from either SMBOIS
calls or XBIOS calls, if SMBIOS fails. The utility also uses these
calls to determine if a service tag is currently programmed on the
system. If one isn't programmed, there is no need to run EE-ERASE
so the utility goes directly to the ASSET program.

2. Based on the information gathered, SVCTAG.EXE launches the
appropriate version of EE-Erase.

Each of these utilities can be run stand-alone. For EE-CPA.EXE, the
-forcetype command line switch may be required.

3. The appropriate version of ASSET program is then launched.
SVCTAG.EXE first asks the user the enter the new service tag (twice
for verification) then passes that value to ASSET when it is
launched.

The ASSET programs can be run as a stand-alone utilities as noted
above.

4. NICSET.EXE is launched by SVCTAG.EXE after EE_ERASE if the system
is a Latitude C610 or Inspiron 4100. NICSET is needed in order to
unhide and enable the onboard NIC, which is disabled by EE-ERASE.

5. FDD_RCL.EXE is the launched from AUTOEXEC.BAT after SVCTAG.EXE. It
performs a Recalibrate operation on the floppy diskette drive.
The purpose of this utility is to ensure the FDD head is moved to
track 0 in preperation for transport.
It is important to power off the system immediately after this
utility is run in order to guarantee the head remains at track 0.

6. SVCTAG.INF is the text file contains vendor name, system id, ee-erase,
erase options, asset and asset options. This file is processed
by svctag.exe. The program goes through this file line by line
and searches for system id and BIOS vendor string which match the
system ID and BIOS vendor string read from the system on which
the utility is being run. If a match is found, the corresponding
line will be parsed and the executables and command line options
from that line will be used to erase and program the service tag.


======================================================================


Supported Systems

All Dell Portable Systems

======================================================================

updated 07/10/03
.............................................................
Autoexec.bat
@echo off
cls
rem
rem To automate this process, modify the call the svctag.exe in the following
rem manner:
rem svctag -nopause new_service_tag < y.txt
rem
rem For example, to program the service tag with 'FLDSRV' use the following
rem command line:
rem svctag -nopause FLDSRV < y.txt
rem
rem NOTE: There is no error checking performed in the program with respect to
rem tag length!

REM svctag -nopause FLDSRV < y.txt

svctag

rem
rem FDD_RCL.EXE is used to recalibrate the floppy controller. This has the
rem effect of moving the head to track 0 in preperation for transport.

fdd_rcl

.............................................................................


regards Ben

This post has been edited by Ben_Mott: Jul 2 2007, 02:26 PM

[Ben_Mott]

useful information:from NightOwl"
to use older versions of Ghost with Vista you either need to use -fdsp (which from memory means

the volume has to stay the same size)


From the User Guide of Ghost 2003:

Quote:
-fdsp

Preserves the signature bytes on the destination disk when performing a disk-to-disk or
image-to-disk cloning operation

I don't know what the *f* stands for, but I think the *dsp* stands for *disk signature

preserve*--my testing has shown that this switch preserves the four hex data points (often

referred to as the *NT Disk Signature*) in the Master Boot Record (MBR) of a disk-to-disk clone

or restored image . Whatever else it may do, I've not seen any other effect.

The companion switch, *-fdsz* (*dsz*=disk signature zeroed?) places zeros in the *NT Disk

Signature* hex data points of the MBR of a disk-to-disk clone restored image (which appears to

be the default mode of operation for Ghost 2003):

Quote:
-fdsz

Clears the signature bytes on the destination disk when performing a disk-to-disk or
image-to-disk cloning operation.


So, by forcing Ghost to preserve the *NT Disk Signature*, the new Vista boot data is preserved

and the cloning will be successful? "

<a href="http://www.runtime.org/dixml.htm" target="_blank"><a href="http://www.runtime.org/dixml.htm" target="_blank">http://www.runtime.org/dixml.htm</a></a>
................................................................................
driveImageXML Tutorial
http://www.darkchip.com/DriveImageXML/index.html
................................................................................
.
...........

PTEDIT32.ZIP(Partition Table and Boot Record Editor by PowerQuest FREE!!)

Caution: Ptedit is a DOS program with a user-friendly graphical interface, but is not made to be used without a mouse. To use ptedit, boot to DOS, load a DOS mouse driver, and then launch ptedit.)


<a href="ftp://ftp.symantec.com/public/english_us_...s/pq/utilities/" target="_blank"><a href="ftp://ftp.symantec.com/public/english_us_...s/pq/utilities/" target="_blank">ftp://ftp.symantec.com/public/english_us_...s/pq/utilities/</a></a>

<a href="http://www.geocities.com/thestarman3/tool/FreeTools.html" target="_blank"><a href="http://www.geocities.com/thestarman3/tool/FreeTools.html" target="_blank">http://www.geocities.com/thestarman3/tool/FreeTools.html</a></a>
How to use it:

<a href="http://www.goodells.net/multiboot/ptedit.htm" target="_blank"><a href="http://www.goodells.net/multiboot/ptedit.htm" target="_blank">http://www.goodells.net/multiboot/ptedit.htm</a></a>
................................................................................
................................................................................
.
................
Fixing Windows 2000/XP Drive Letters

<a href="http://www.goodells.net/multiboot/partsigs.htm#method3" target="_blank"><a href="http://www.goodells.net/multiboot/partsigs.htm#method3" target="_blank">http://www.goodells.net/multiboot/partsigs.htm#method3</a></a>

This post has been edited by Ben_Mott: Nov 23 2007, 04:51 PM

[Ed_P]

It's not necessary to cut & paste a product's whole webpage here. A simple link to it's webpage is sufficient.

[Ben_Mott]

thanks ED for that , in future I will keep it short and simple.
http://www.runtime.org/dixml.htm

I noticed that is included in UBCD4WIN PE Bootable CD
http://www.ubcd4win.com/


check this out:
http://selfimage.excelcia.org/
it is only 1.31MB
and it works in VistaPE 2

and it is FREE

SelfImage is a disk imaging program for Windows. It allows you to create an image of any partition on your computer's hard drives. It can even create images from partitions that Windows can't access and don't have drive letters assigned to. Linux partitions, for example. This makes it easy to make backups of a second operating system's partitions. (when run on Windows 2000 or later

Also we got Imagex.exe now very powerful tool a credit to Microsoft
http://www.boxpost.orangehome.co.uk/vistaimaging.htm

cheers Ben


This post has been edited by Ben_Mott: Mar 3 2007, 02:11 AM

[jaclaz]

...and here is a thread where that tool and other alternatives are discussed:
http://www.911cd.net/forums//index.php?showtopic=16534

jaclaz

[Ben_Mott]

Ghost.exe 2003 (Ghost 8 in DOS) Ghosting Vista

If your ghosting a vista image to a disk that has already had vista running on it, then you can use Ghost 2003 DOS version as normal.

If your moving ghost image to another hard drive, do the following from the command line (make sure you right click the command prompt icon and choose 'run as administrator')

and run these commands one after the other:
To run BCDEDIT.EXE, indeed you need to have your full Administrators rights in effect. You can do this with any Administrators-member account (not specifically "Administrator"), but you will need to right-click the Command Prompt shorcut and select "Run as Administrator" in order to subsequently run BCDEDIT.EXE successfully within that Command Prompt session.

(Or, as alluded to, if UAC is simply disabled altogether that would give you full Administrators right in any Command Prompt session too. But simply right-clicking the Command Prompt and selecting "Run as Administrator" will suffice for the default UAC-enabled mode of Vista.)

bcdedit /set {bootmgr} device boot
bcdedit /set {default} device boot
bcdedit /set {default} osdevice boot

How to obtain the programs updates that are archived on Symantec LiveUpdate server

<a href="http://service1.symantec.com/Support/share...007010219171513" target="_blank"><a href="http://service1.symantec.com/Support/share...007010219171513" target="_blank">http://service1.symantec.com/Support/share...007010219171513</a></a>

ghost 11 compatible with vista
<a href="http://www.symantec.com/enterprise/product...&pvid=865_1" target="_blank"><a href="http://www.symantec.com/enterprise/product...&pvid=865_1" target="_blank">http://www.symantec.com/enterprise/product...&pvid=865_1</a></a>

Multi Booting /Cloning Vista
<a href="http://www.multibooters.co.uk/cloning.html" target="_blank"><a href="http://www.multibooters.co.uk/cloning.html" target="_blank">http://www.multibooters.co.uk/cloning.html</a></a>

Switches
<a href="http://service1.symantec.com/SUPPORT/ghost...998082612540625" target="_blank"><a href="http://service1.symantec.com/SUPPORT/ghost...998082612540625" target="_blank">http://service1.symantec.com/SUPPORT/ghost...998082612540625</a></a>

useful info:
important information using ghost2003 ghost.exe version 8:
The key was having the HDD on one partition and everything matching up.
...............................................
I had the same issue on the first reboot after the Ghost clonning.

Here it is how I fixed it

Boot with a Windows PE CD or any SW that allow you to run from the command prompt the followign

command located on c:\windows\system32\.

bcdedit /set {bootmgr} device boot

bcdedit /set {default} device boot

bcdedit /set {default} osdevice boot

Note you can "fix" a previously restored (and currently failing to boot) installation using a PE

boot disc and executing these same actions against the restored partition's BCD entries.


That should fix your boot whatever sector/partition ...


bcdedit /set {bootmgr} device boot
bcdedit /set {default} device boot
bcdedit /set {default} osdevice boot
.............................................
or simply run DVD repair to repair WinLoad
problem start if you are using a new HDD
vista will refuse to Boot.
...........................................
Once the BCD entries are no longer referring to specific disk signatures and partition numbers,

there is no need to use -FDSP with Ghost anymore, either. The disk signature can be reset as it

is by default with a Ghost disk restore, and "nothing special" is required during image creation

or restore (from a Ghost perspective)

There's a switch with Ghost (well, ghost 8.2 anyway) that fixes the issue of the boot manager

Use the -fdsp switch( [b]Force Disk Signature Preserve) switch, (or -fdsz on older versions). It works for me and its much easier than

playing around with bcdedit[/b]
................................................................................
..........

in ghost 2003 this can be accomplished through the options menu as well. Forcing

ghost to clone the boot sector. The command line is something like -ImageBoot or -ImageAll. ????

................................................................................
........
some one on another forum reported :
Forget Ghost Solution Suite 2 guys, because this worked.

If your ghosting a vista image to a disk that has already had vista running on it, then you can use Ghost 2003 DOS version as normal.

If however your moving ghost image to another hard drive, do the following from the command line (make sure you right click the command prompt icon and choose 'run as administrator')

and run these commands one after the other:

bcdedit /set {bootmgr} device boot
bcdedit /set {default} device boot
bcdedit /set {default} osdevice boot

some one on another forum reported that he has just successfully copied his Vista image from one hard drive to a completly blank drive without partitions etc and then successfully booted from it.
...................................................
To run BCDEDIT.EXE, indeed you need to have your full Administrators rights in effect. You can do this with any Administrators-member account (not specifically "Administrator"), but you will need to right-click the Command Prompt shorcut and select "Run as Administrator" in order to subsequently run BCDEDIT.EXE successfully within that Command Prompt session.

(Or, as alluded to, if UAC is simply disabled altogether that would give you full Administrators right in any Command Prompt session too. But simply right-clicking the Command Prompt and selecting "Run as Administrator" will suffice for the default UAC-enabled mode of Vista.)
====================================
I'd like to have Ghost Explorer installed (on Vista)to be able to do selective file restores.
...........................
Do you have Ghost Explorer installed on another system? Just find the *Ghostexp.exe* program from the *Norton Ghost* sub-directory, and copy it over to the Vista system. Execute it and see if it works
...............................
Copied *Ghostexp.exe* over to this Vista Ultimate install and it works no probs in opening the image I created with the Ghost floppy.
--------------------------------------------------------------------------------------------
============================================================
................................................................................
.........................
useful infomation regarding Dual Boot
I downloaded Grub4DOS from
<a href="http://linux.softpedia.com/get/System/Boot...-DOS-3507.shtml" target="_blank"><a href="http://linux.softpedia.com/get/System/Boot...-DOS-3507.shtml" target="_blank">http://linux.softpedia.com/get/System/Boot...-DOS-3507.shtml</a></a>
then unziped it
it had fat12grldr.img so using winimage i made a bootable floppy.
and booted from that ok. cool !!
then as ED sugested I copied the GRldr and MENU.lst from th floppy to the root of my
IDE HDD C: drive
and then opened the Boot.ini which lives in the root of C:
and added (appended)this line to it
C:\GRLDR="start GRUB"
then saved it.
and rebooted it .
it went straight to XP menu and had the line "start Grub" on the menu
so using the down arrow key I navigated quickly to it and pressed enter on key board .
the GRUB4DOS menu came up.
Cool REAL cool!!! laugh.gif laugh.gif

<a href="http://www.gnu.org/software/grub/manual/grub.html#Top" target="_blank"><a href="http://www.gnu.org/software/grub/manual/grub.html#Top" target="_blank">http://www.gnu.org/software/grub/manual/grub.html#Top</a></a>

alternative method and useful info:

<a href="http://www.littlewhitedog.com/content-52.html" target="_blank"><a href="http://www.littlewhitedog.com/content-52.html" target="_blank">http://www.littlewhitedog.com/content-52.html</a></a>

<a href="http://tinyurl.com/yqynr6" target="_blank"><a href="http://tinyurl.com/yqynr6" target="_blank">http://tinyurl.com/yqynr6</a></a>
<a href="http://tinyurl.com/mrhjd" target="_blank"><a href="http://tinyurl.com/mrhjd" target="_blank">http://tinyurl.com/mrhjd</a></a>

Regards Ben

regards Ben


This post has been edited by Ben_Mott: Jan 5 2008, 03:09 PM

[Ben_Mott]

Ghost 7.5 and Ghost 8 have proven track record and nobody likes to buy new version of Ghost if it works with Vista.
Many forums confirm this work around which is detailed in previous post and summerized here:
.......................................................
Please note that making this change to the BCD file is of course only desirable if you are not using the Windows bootmanager. If you don’t know for sure that you are not, then don’t mess with the BCD file.
--------------------------------------------------------------------------------------------------------------

You can still create a Ghost image of a Vista machine using Ghost 7 or 8

Its just a little more involved.

When you have your vista machine ready

Run the CMD as administrator (Right click CMD, RUN AS ADMIN)

Then type the following (Copy line for line)

bcdedit /set {bootmgr} device boot
bcdedit /set {default} device boot
bcdedit /set {default} osdevice boot

Restart the machine and then GHOST as usual

The image will be able to ghost back and work.
................................................................................
lright, I got it fixed now.

Here is what I did:
1) Booted on my Bart PE CD
2) Start ghost32.exe -ib and local --> disk --> to image
3) Exchange drives
4) Boot on Bart PE again
5) Start ghost32.exe -ib and local --> disk --> from image
6) Reboot - Computer will not boot, keeps restarting after a few seconds
7) Boot on Vista install CD - select Repair

After reboot, things are working.

Thanks for your suggestions and help - much appreciated.
As you can see, you were right about the version of Ghost being used. It is indeed ghost32.exe

that is being used.
============================
Probably should load Ghost with this command switch (-ib) = *image boot* to make sure any

special programing in the *boot tract*, and not just the first absolute sector 0 boot

information, is included in the file: ghost.exe -ib or ghost32.exe -ib

And, use *Whole Disk* and not just a *Partition* back up procedure--like you mentioned above!

=================================================================
You might avoid having to do the *Repair* by using the Ghost switch *-FDSP*:
ghost32.exe -ib -fdsp
=====================================================================

Should I use it both for creating AND restoring the image, or just when I create the image?
Don't know for sure, but I think if the image is created using the *-ib* switch, Ghost will

probably only allow a *whole disk* restore and will default to restoring the whole boot tract.

I think you get an error message if you try any other *partition only* procedure. But using the

*-ib* switch for restore, as well, will cause no harm--and avoid any possible issue.
-----------------------------------------------------------------------

Reference:MSDN
<a href="http://forums.microsoft.com/MSDN/ShowPost....p;PostID=181082" target="_blank"><a href="http://forums.microsoft.com/MSDN/ShowPost....p;PostID=181082" target="_blank">http://forums.microsoft.com/MSDN/ShowPost....p;PostID=181082</a></a>
---------------------------------------------------------------------
<a href="http://www.symantec.com/vista/" target="_blank"><a href="http://www.symantec.com/vista/" target="_blank">http://www.symantec.com/vista/</a></a>
This previously mentioned reference:
<a href="http://radified.com/cgi-bin/yabb2/YaBB.pl?...170184062/60#70" target="_blank"><a href="http://radified.com/cgi-bin/yabb2/YaBB.pl?...170184062/60#70" target="_blank">http://radified.com/cgi-bin/yabb2/YaBB.pl?...170184062/60#70</a></a>
has *three* different solutions as to how to deal with DOS Ghost and Vista:

1. Edit the BCD data before using Ghost to create images--so restores work without further issues,

2. If you did not edit the BCD data before creating Ghost images, then restore the image--then boot from a PE boot disc (Windows Vista installation CD)--and now, apply those BCD data edits to the restored Vista OS boot partition.

3. Use Ghost's *-FDSP* switch to force Ghost to preserve the disk signature when doing a restore
==================================================
some comments from vista owners:

Failure to boot after the first Vista restore is fairly typical. You just need to boot to your Vista DVD and run a BCD repair. A few minutes at most. Subsequent restores will work without a repair.

Here are some links as a reference.

http://radified.com/cgi-bin/yabb2/YaBB.pl?num=1170184062/0

http://radified.com/cgi-bin/yabb2/YaBB.pl?num=1190587619/0

http://www.wilderssecurity.com/showthread.php?t=185731

http://www.wilderssecurity.com/showthread.php?t=173214
===========================================================
I did manage to fix the problem with the help of easybcd.
http://neosmart.net/dl.php?id=1
I found out the setting my device to BOOT as below
---------------------------
bcdedit /set {bootmgr} device boot
bcdedit /set {default} device boot
bcdedit /set {default} osdevice boot
-----------------------------------
in the BCD was only correct if you were only restoring the vista partition but in a dual boot system like what I had I needed to use the drive letter itself (which in my case was E:\) for the device setting and everything worked just fine.
------------------------------------------------
daul boot system
---------------------------------------------------------------------------------------
c:\Windows\System32>bcdedit
----------------------------------------------------------------------------------------
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=D:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
displayorder {ntldr}
{current}
toolsdisplayorder {memdiag}
timeout 10

Windows Legacy OS Loader
------------------------
identifier {ntldr}
device partition=D:
path \ntldr
description Earlier Version of Windows

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows Vista
locale en-US
inherit {bootloadersettings}
osdevice partition=C:
systemroot \Windows
resumeobject {2461cbd7-bba7-11dc-a461-8e290a68bec5}
nx OptIn
---------------------------------------------------------------------------
--------------------------------------------------------------------------


I have not got Vista myself so if this works around works for you confirm the result here and others will benefit from your
experience Thank you
====================================================
DiscWizard (Free) Acronis Cloning software

Seagate have aquired Maxator (maxblast5 is now same as seagate tool) they updated DiscWizard to better fit the needs of today’s technology (improved USB support, improved support for diagnostic partitions, and Windows Vista support). The newer tools are below.
===============================================================
<a href="http://www.seagate.com/ww/v/index.jsp?loca...000f5ee0a0aRCRD" target="_blank"><a href="http://www.seagate.com/ww/v/index.jsp?loca...000f5ee0a0aRCRD" target="_blank">http://www.seagate.com/ww/v/index.jsp?loca...000f5ee0a0aRCRD</a></a>
=================================
<a href="http://www.seagate.com/www/en-us/support/d...oads/discwizard" target="_blank"><a href="http://www.seagate.com/www/en-us/support/d...oads/discwizard" target="_blank">http://www.seagate.com/www/en-us/support/d...oads/discwizard</a></a>
=============================================
it is by Acronis and is a Free as long as you got a Maxtor or seagate Harddrive.
it is basically a cloning tool plus partioning and Hard disk preparation.
===============================================
also down load the instruction from the sam site
when you install it to windows it gives you a chance to make an emergency Acronis
Bootable CD.
=================================================
read the help files Contents .
=======================================================
RecoveryConsole Bootable XPhome(XP PRO) ISO CD Real Cool !!!
<a href="http://www.boot-land.net/forums/Recovery-Console-t2254.html" target="_blank"><a href="http://www.boot-land.net/forums/Recovery-Console-t2254.html" target="_blank">http://www.boot-land.net/forums/Recovery-Console-t2254.html</a></a>
=====================================================


Regards Ben


This post has been edited by Ben_Mott: Mar 21 2008, 04:16 PM

[Ben_Mott]

PC Angle and Ghost HP Compaq use PC Angle recovery

Hello Again,

here is a link to PC Angle:

http://www.softthinks.com/us/
http://www.pcangelle.com/s

Symantec and ghost & Norton 360
===============================

the new Norton 360 internet protection software insist on removing
norton Works along with Norton utilities,ghost,and goback.

PC Angle
========
Pc Angle comes from a German/french company called Soft Thinks
Some PC manufacturerers ,including HP and Compaq ,are now factory installing
an emergency rescue program called PC Angle instead of Ghost.

Dell use Ghost for recovery but they do not install norton 360.
======================================

I just noticed that 50,000 people have read this Link topic

Is this a record ???

Regards Ben

====================================================================
Windows bootable installation CD using Bart's instruction:
http://www.nu2.nu/bootcd/#wxp
http://www.frogaspi.org/index.html
=====================================================================
DiscWizard (Free) Acronis Cloning software
http://www.911cd.net/forums//index.php?showtopic=20220

=====================================================================
How To Make Bootable Cd Winpe 2.0, down load link to WAIK (Vista PE)
http://www.911cd.net/forums//index.php?showtopic=18995
======================================================================
Failure to boot after the first Vista restore is fairly typical. You just need to boot to your Vista DVD and run a BCD repair. A few minutes at most. Subsequent restores will work without a repair.

Here are some links as a reference.

http://radified.com/cgi-bin/yabb2/YaBB.pl?num=1170184062/0

http://radified.com/cgi-bin/yabb2/YaBB.pl?num=1190587619/0

http://www.wilderssecurity.com/showthread.php?t=185731

http://www.wilderssecurity.com/showthread.php?t=173214
===========================================================
I did manage to fix the problem with the help of easybcd. I found out the setting my device to BOOT as below
---------------------------
bcdedit /set {bootmgr} device boot
bcdedit /set {default} device boot
bcdedit /set {default} osdevice boot
-----------------------------------
in the BCD was only correct if you were only restoring the vista partition but in a dual boot system like what I had I needed to use the drive letter itself (which in my case was E:\) for the device setting and everything worked just fine.
------------------------------------------------
daul boot system
---------------------------------------------------------------------------------------
c:\Windows\System32>bcdedit
----------------------------------------------------------------------------------------
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=D:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
displayorder {ntldr}
{current}
toolsdisplayorder {memdiag}
timeout 10

Windows Legacy OS Loader
------------------------
identifier {ntldr}
device partition=D:
path \ntldr
description Earlier Version of Windows

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows Vista
locale en-US
inherit {bootloadersettings}
osdevice partition=C:
systemroot \Windows
resumeobject {2461cbd7-bba7-11dc-a461-8e290a68bec5}
nx OptIn
----------------------------------------------------------------------------

------------------------------------------------------------------------------------------
see previous notes on Ghost parameters for SATA HDD but here is another Tip
-----------------------------------------------------------------------------

Ghost and SATA go into BIOS and change the driver setting from
RAID Auto detect /AHCI
to
RAID Auto detect/ATA
save and exit
=============================================================
so many people using Vista 's OWEN back up and restore have reported problems.
a cheap alternative back up Prog for vista is:
---------------
AISBackup: A PC Backup Solution.

AISBackup provides a managed backup of data and the Operating System of Windows PC's and Server's to CD, DVD, Internal and External Disk drives, Networked drives, FTP Servers and all other media that looks like a disk to Windows.
http://www.aiscl.co.uk/index.php

--------------------------------
Here is a very nice TIP from MUSTANG regarding adding drivers to ghost 9 and 10 CDs:

Hi All,
From MUStang

Thought I would just drop in and share a way I have used to add network

and HDD controller drivers to a Norton Ghost 9 or 10 Recovery CD.

This method makes use of BartPE builder but does not create a BartPE CD. It just modifies your

Norton disk to add the drivers you are missing.

1. Download pebuilder from http://www.nu2.nu/pebuilder/ and install to your system.

2. Go to c:\pebuilder\drivers and add the drivers you need to add to your Recovery CD. Put

network drivers in the "Net" folder and SATA, RAID drivers in the "SCSIAdapter" folder. Put each

driver you add in its own subfolder. Just copy the Windows drivers completely from a floppy or

other source.

3. Now run c:\pebuilder\pebuilder.exe.

4. Point the "Source" box to your WinXP/SP2 CD. You can copy the CD to a hard drive if you like.

5. Point the "Custom" box to your Norton installation CD.
Edit on 12/4/2006: You should copy the Recovery CD to a hard drive and point to the root of

that.

6. Now click the "Plugins" button. Disable all plugins except the Custom plugin.

7. Highlight the Custom plugin. Click the "Edit" button. Remove the semicolon from in front the

last line. Now change the word "Booting" to "Starting Symantec Recovery Disk". Save the changes.

8. Close the plugin window.

9. You can elect to create an iso image to burn with a third party burning program or burn

directly to CD.

10. Now click the "Build" button.

The resulting CD works just like the original Norton CD except that it has the misssing drivers

included.

Just note that this works for most drivers. However, a few devices require a BartPE plugin to

work. If you have such a device and there is a BartPE plugin available, the plugin can be added

to your build in the usual manner. The plugin would need to be copied to the c:\pebuilder\plugin

folder.

Enjoy.
===========================================================
now for something completely different
this is a link to MBR AUTO
http://www.acronis.com/files/support/mbrautowrite_en.iso
it is a Cd so is good for people without floppy disk
==========================================================
Trapped in Ghost 2003 Virtual partition !!!!
http://radified.com/cgi-bin/yabb2/YaBB.pl?num=1188045499/1#1

Many folks can avoid the problem of the *virtual partition* by booting to DOS *manually* rather than using the Windows Ghost interface--by booting to DOS directly.
=====================================================================


I have half a dozen or more USB Flash drives that I've made bootable with the little HP program.
http://h18000.www1.hp.com/support/files/se...load/23839.html
http://h18007.www1.hp.com/support/files/hp...load/20306.html
http://www.weethet.nl/english/hardware_bootfromusbstick.php


I've even done it with a SD flash card.
All of my older FD's boot into an A: prompt.

But, I just formatted a 1 gig FD from "Mediamate" in the normal manner and it boots up to a C:

prompt. That won't work!!! I need the A: prompt to run Ghost 2003 or 2005 from the FD and make

a bootable Ghost backup DVD.


when I run Ghost to make a bootable DVD, Ghost can't find the boot files on A: where it's

programmed to look for them. It won't accept them from any other drive letter. It's A: or

nothing.

Edit: I've looked at all my flash drives that boot to A: and they are all 512mb or less. The 1

gig drives all boot to a C: prompt when made exactly the same way as the smaller drives.

So my solution is to just NOT use and Flash Drive over 512 when making a bootable FD.
I did a little shopping yesterday and found that in all the local stores, FD's below 1 gig have

disappeared from the store shelves.
I really don't need any more small FD's, but if I did, I guess I'd have to do some internet

shopping. I'm sure someone out there has a quantity of the small FD's that they'd like to get

rid of.
SD Flash cards of less than 512mb work just as well as the Flash Drives (also called thumb

drives).
................................................................................
How to obtain the programs updates that are archived on Symantec LiveUpdate server
http://service1.symantec.com/Support/share...007010219171513
After browsing boards and google on how to use Ghost 2003 with SATA drives I realized you have to have the .793 build. If you have the .775 or .778 etc builds you HAVE to upgrade in order to be able to use SATA drives with the -FNI switch.

Most everyone was under the impression that this patch was 'discontinued' by symantec or no longer available as running liveupdate tells you you are all up to date if you have the .775 or .778 build.

After doing some digging I realized that the patch WAS available if you followed symantec's instructions to access their ARCHIVED Liveupdate server!

Here's Symantec's instructions on how to do this, follow them exactly and you should get the update. Just make sure all of your ghost services are killed in task manager before the update or it won't take hold and you'll have to run it again.

http://service1.symantec.com/Support/share...007010219171513

............................

This post has been edited by Ben_Mott: Mar 31 2008, 03:42 PM

[Ed_P]

Not even close.

The CD Forum > Bart's PE Builder > Plugins - Windows Password Renew Tool - 112,272

[Ben_Mott]

Hello,

here is another temp Link

http://tinyurl.com/bootmanagerdisk

down load to desk top and put a formatted floppy in floppy drive and double click
the icon on desk top.
=============================
here is content of the other floppy benpartitiontype

Benpartitiontype:

Volume in drive A has no label.
Volume Serial Number is B896-FD88

Directory of A:\

11/05/1998 20:01 93,880 COMMAND.COM
17/09/1994 08:50 1,608 DEVICE.COM
27/04/2006 20:52 2,636 CDINST.BAT
06/05/1998 20:01 25,473 MSCDEX.EXE
24/03/2002 21:15 39 autoexec.bat
04/06/1998 09:22 41,302 OAKCDROM.SYS
30/01/1997 11:11 1,754 CHOICE.COM
18/01/2009 20:02 0 list.txt
8 File(s) 166,692 bytes
0 Dir(s) 979,968 bytes free

===================================================
CDinst.bat

CODE

@echo off
echo.
echo CDINST Version 3.00
echo.

rem cdletter is the CDROM letter
SET CDLETTER=%1

If not Exist DEVICE.COM goto ERROR
If not Exist MSCDEX.EXE goto ERROR

echo Checking for ATAPI Drive...
DEVICE.COM OAKCDROM.SYS /D:CD001
IF ERRORLEVEL 1 Goto NOCDROM
GOTO JUMP

rem -------------------------------------------------------------------------------------------

:NOCDROM
ECHO .
ECHO No CD-ROM drive has been detected.
ECHO .
ECHO If your system includes a CD-ROM drive,
ECHO please check cable connection and try again.
ECHO .
if not $%1==$CREATETAG GOTO END
if $%1==$CREATETAG ECHO NO CDROM PRESENT>C:\CABS\TAGS\CDROM0.TAG
GOTO END

:ERROR
CLS
ECHO Unable to detect CD-ROM drive. Missing DET-CD.EXE, DEVICE.COM,
ECHO DRIVERS.EXE or MSCDEX.EXE.
GOTO END

rem -------------------------------------------------------------------------------------------

:JUMP
echo.

If $%CDLETTER%==$ Goto NOCDL
LH MSCDEX.EXE /D:CD001 /M:30 /L:%CDLETTER%
If ERRORLEVEL 1 MSCDEX.EXE /D:CD001 /M:30 /L:%CDLETTER%
If ERRORLEVEL 1 GOTO NOCDROM

Goto END

:NOCDL
LH MSCDEX.EXE /D:CD001 /M:30
If ERRORLEVEL 1 MSCDEX.EXE /D:CD001 /M:30
If ERRORLEVEL 1 GOTO NOCDROM
Goto END

:END
echo Benny Recovery Disk
echo .
echo WARNING! If you continue you will erase everything from your hard drive
echo .
echo .

echo.
echo The recovery CD will restore the system to its
echo original factory state. Any other programs or files
echo will be deleted, it is strongly recommended that
echo you backup any important data before continuing.
echo .
choice Would you like to continue with the recovery?
if errorlevel 2 goto endend

echo .
cls

echo Recovery Disk
echo .
echo WARNING! if you continue you will erase everything from your hard drive
echo .
echo You are about to start the recovery procedure
echo this will erase everything that is currently on
echo your hard drive.
echo .
echo Are you sure you want to restore system?
choice data will be lost!
if errorlevel 2 goto endend

cls

echo Recovery CD
echo .
echo WARNING! Starting Recovery Procedure
echo .
echo .
echo .

echo.
choice Continue With Recovery?

if errorlevel 2 goto end

ghost.exe -clone,mode=pload,src=c:image.gho:1,dst=1:1 -sure -rb

:endend

===================================================
AUTOexec.bat
========================
@echo off

cdinst.bat

exit
=====================================================

also seethis Tip By jaclaz:

Newish option, Terabyte MBR Utility can istall MBR's that allow for pressing a Fn key to select a "recovery" partition. :
http://www.msfn.org/board/Create-My-Own-Re....html&st=26



jaclaz

Ben
================================================================================
==
MBR
~~~

MBR.EXE is a utility intended to complement other TeraByte Unlimited products.

http://www.terabyteunlimited.com/downloads/mbr.zip


MBR.EXE allows you to manipulate a drive's master boot record (MBR). For
example, MBR.EXE is capable of deleting all the partitions in a MBR, zeroing
out a MBR, installing a standard MBR, and more.


Installation:
~~~~~~~~~~~~~

Simply copy the program file to a directory on your hard drive, or to a
bootable floppy diskette. MBR.EXE can be run from a command prompt, or from
a batch file.


Usage (mode 1 of 2):
~~~~~~~~~~~~~~~~~~~~

mbr hdnum [/RESET] [/ZERO] [/DEL] [/INSTALL] [/REBOOT]

hdnum Hard drive number whose MBR will be acted on (0-15).

/RESET Used in combination with MBR code installed with SELM below.

/ZERO Set the entire MBR to zero (deletes all MBR partitions).

/DEL Delete all partitions in MBR.

/INSTALL Install MBR code using the follow addtional parameters:

[STD] [SEL to fkey "msg"] [SELM to fkey "msg" fsid fsidhid]

STD Install standard MBR code.
SEL Install MBR code that will display 'msg' and boot a hidden
FAT/FAT32 partition if 'fkey' is pressed within 'to' seconds.
The ondisk MBR is not modified.
SELM Install MBR code that will display 'msg' and boot a partition
with a file system id of 'fsidhid' if 'fkey' is pressed within
'to' seconds. The MBR is modifed so that the partition is marked
active and the file system is changed to 'fsid'. To reset the
MBR back to the prior settings, use the /RESET switch before
modifying the MBR again.

/REBOOT Reboot the computer after the selected action is carried out.


Additional usage notes:
~~~~~~~~~~~~~~~~~~~~~~~

* If the /INSTALL SEL or /INSTALL SELM command parameters are to be used,
there must be one and only one partition available that matches. For example,
the /INSTALL SEL command parameters cause a hidden FAT/FAT32 partition to be
booted from, if the defined F-key is pressed. If there is more than one
hidden FAT/FAT32 partition, however, the F-key defined by the /INSTALL SEL
command parameters will not work.

* If the /INSTALL SELM command parameters are used, the /RESET command should
be run when the alternate partition is booted from. This will reset the MBR
to its previous configuration.


Examples of use:
~~~~~~~~~~~~~~~~

mbr 1 /zero

MBR.EXE will write zeros to the MBR of hard drive 1. Note: Hard drive
1 is the SECOND hard drive, since these numbers start at 0.

mbr 2 /del

MBR.EXE will delete each partition in the MBR of hard drive 2.

mbr 2 /del /reboot

Same as above, except that the system will reboot immediately after
MBR.EXE performs the requested action.

mbr 0 /install std

MBR.EXE will install a standard MBR to hard drive 0.

mbr 0 /install sel 5 12 "Press F12 to boot the recovery partition"

MBR.EXE will install a MBR to hard drive 0. The MBR will display the
message "Press F12 to boot the recovery partition" for 5 seconds, and
the F12 key will cause a hidden FAT/FAT32 to be selected for booting.

mbr 0 /install selm 10 9 "Press F9 for recovery" 0xC 0xDB

MBR.EXE will install a MBR to hard drive 0. The MBR will display the
message "Press F9 to boot the recovery partition" for 10 seconds.

If the F9 key is pressed within 10 seconds, it will cause a partition
with the file system ID 0xDB to be booted from. The MBR will then be
modified to mark the new boot partition active, and the file system ID
of it will be changed to 0xC.

Once booted in the partition whose file system ID was originally 0xDB,
the command line "mbr 0 /reset" should be run, in order to set the MBR
back to the state it was in before the file system ID and active
partition values were changed.


Usage (mode 2 of 2):
~~~~~~~~~~~~~~~~~~~~

mbr hdnum entry [/ISACT] [/DEL] [/[U]H] [/A] [/SET id] [/ISFSID id] [/REBOOT]

hdnum Hard drive number whose MBR will be acted on (0-15).

entry MBR entry number (0-3).

/ISACT Returns ERRORLEVEL 1 if the entry (zero based) is marked active.

/DEL Delete the entry.

/[U]H Unhide or Hide the FAT/FAT32/NTFS/HPFS entry.

/A Set the entry active.

/SET Set the file system id of the entry.

/ISFSID Returns ERRORLEVEL 1 if the entry file system id matches id

/REBOOT Reboot the computer after the selected action is carried out.


Examples of use:
~~~~~~~~~~~~~~~~

mbr 0 2 /isact

MBR.EXE will set ErrorLevel to 1 if MBR entry 2 on hard drive 0 is
marked active:

@echo off
mbr 0 2 /isact
if errorlevel 1 goto label

mbr 0 2 /isfsid 0xC

MBR.EXE will set ErrorLevel to 1 if MBR entry 2 on hard drive 0 has a
file system ID of 0xC:

@echo off
mbr 0 2 /isfsid 0xC
if errorlevel 1 goto label

mbr 2 1 /del

MBR.EXE will delete MBR entry 1 on hard drive 2.

mbr 1 0 /h
mbr 1 0 /u

The command lines above will, respectively:

- Instruct MBR.EXE to hide MBR entry 0 on hard drive 1.
- Instruct MBR.EXE to unhide MBR entry 0 on hard drive 1.

mbr 0 1 /a

MBR.EXE will set MBR entry 1 on hard drive 0 active.

mbr 0 1 /a /reboot

Same as above, except that the system will reboot immediately after
MBR.EXE performs the requested action.

mbr 1 1 /set 0xD

MBR.EXE will set the file system ID of MBR entry 1 on hard drive 1
to 0xD.



============================================================================



Ben

This post has been edited by Ben_Mott: Jan 19 2009, 02:34 PM

Reason for edit: Added codebox tags around the code.

[Ed_P]

tinyurl=http://www.pcclinic.orangehome.co.uk/bootmanager.exe