The text file you attached appears unreadble on me system Can you reply and reattach?
Andy,
When using the Partition Table Options utility function: Save Partition to File; it didn't assign any "type format" when saved. (I added the .txt file extension...which still didn't provide a legible text file.)
However, in my Reply #18, the partition information that I created in that table is what is displayed when using the View/Edit function on the Partition Table Operations Menu. (and what I am assuming is "saved" in this file...?
You could try to wipe the drive either using the drive manufacturer's utility or by using DISKPART to clean the drive from the SRD.
Here's how I would do it...
With only the SRD and laptop drive connected, boot the SRD.
Open a command prompt.
Type DISKPART [enter].
Type LIST DISK [enter].
In the list you should see your CD/DVD drive and harddisk listed. Note the number assigned to the harddisk (probably 0)
Type SELECT DISK 0 [enter]. If necessary substitute the number that was shown for the hard disk above in place of the 0.
Type CLEAN [enter]. This will wipe all partitions formatting, etc from the disk. There will be no confirmation so MAKE SURE YOU HAVE THE CORRECT DRIVE!
After the CLEAN command is complete...
Type EXIT [enter]. This will exit DISKPART.
Type EXIT [enter]. This will close the command prompt.
Shut down and plug in the USB drive.
Does it work now?
Red,
Thanks for the assistance.... That seems like a straight forward (albeit some what "concerning") approach. Due to the fact that if Ghost recovery fails me this time -- I have no valid data anywhere to work from...
As a point of clarification -- I'm assuming that the contiuation of your instructions from: Shut down and plug in the USB drive should be:
1) Shut down
2) Boot from the SRD; with the external USB attached hard-drive attached where your .v2i file resides
3) The DlMapper.exe error should not occur.... Which I think is what you mean by: Does it work now?
4) Execute Recover My Computer from the most current .v2i image.
5) Reboot and Win XP and overall system should be Back in business!
Your thoughts?
dhp10 wrote:Red,
Thanks for the assistance.... That seems like a straight forward (albeit some what "concerning") approach. Due to the fact that if Ghost recovery fails me this time -- I have no valid data anywhere to work from...
As a point of clarification -- I'm assuming that the continuation of your instructions from: Shut down and plug in the USB drive should be:
1) Shut down
2) Boot from the SRD; with the external USB attached hard-drive attached where your .v2i file resides
3) The DlMapper.exe error should not occur.... Which I think is what you mean by: Does it work now?
4) Execute Recover My Computer from the most current .v2i image.
5) Reboot and Win XP and overall system should be Back in business!
Your thoughts?
Yes. As long as you have a verified v2i file, it should restore. Is there any chance you could get a different harddrive to try to restore to?
Also, one other thing that I may have missed... Have you tried booting the SRD with the USB drive disconnected? Does it still give the DLMapper error?
just a quick question - you mentioned that when you completely removed the drive from the system, the error did not occur. Was that the internal drive or the USB drive, or both?
This issue has been resolved by following the Steps outlined in Responses 23 - 25. Even though the DlMapper.exe error message was never solved, the workaround was an acceptable means to recover the computer back to a functioning state.
Thanks Red & all others for your input towards the resolution of this problem.
So the DLMapper error disappeared when the target drive was blanked out with Diskpart?
Red,
Yes the SRD booted up clean to the Symantec Ghost 14 Menu(s) without any type of error.
So I wonder if it is a MBR error that causes the problem. I wonder if running BOOTSECT /NT52 ALL /MBR from the SRD command prompt would have fixed the problem. I'm not sure if that command is exactly correct, Type BOOTSECT /HELP to see the options and defintions.
Note: NT52 = WinXP NT60 = Vista, later.
X:\Windows\System32>bootsect /helpbootsect {/help|/nt60|/nt52} {SYS|ALL|<DriveLetter>:} [/force] [/mbr]
Boot sector restoration tool
Bootsect.exe updates the master boot code for hard disk partitions in order to
switch between BOOTMGR and NTLDR. You can use this tool to restore the boot
sector on your computer./help Displays these usage instructions.
/nt52 Applies the master boot code that is compatible with NTLDR to SYS,
ALL, or <DriveLetter>. The operating system installed on SYS, ALL, or
<DriveLetter> must be older than Windows Vista./nt60 Applies the master boot code that is compatible with BOOTMGR to SYS,
ALL, or <DriveLetter>. The operating system installed on SYS, ALL, or
<DriveLetter> must be Windows Vista, Windows Server 2008 or later.SYS Updates the master boot code on the system partition used to boot
Windows.ALL Updates the master boot code on all partitions. ALL does not
necessarily update the boot code for each volume. Instead, this
option updates the boot code on volumes that could be used as Windows
boot volumes, which excludes any dynamic volumes that are not
connected with an underlying disk partition. This restriction is
present because boot code must be located at the beginning of a disk
partition.<DriveLetter> Updates the master boot code on the volume associated with this
drive letter. Boot code will not be updated if either 1)
<DriveLetter> is not associated with a volume or 2) <DriveLetter> is
associated with a volume not connected to an underlying disk
partition./force Forcibly dismounts the volume(s) during the boot code update. You
should use this option with caution.If Bootsect.exe cannot gain exclusive volume access then the file system may overwrite the boot code before the next reboot. Bootsect.exe always attempts to lock and dismount the volume before each update. When /force is specified, a forced dismount is attempted if the initial lock attempt fails. A lock can fail, for example, if files on the target volume are currently opened by other programs. When successful, a forced dismount allows exclusive volume access and a reliable boot code update even though the initial lock failed. At the same time, a forced dismount invalidates all open handles to files on the target volume. This could result in unexpected behavior from the programs that opened these files. Therefore, you should use this option with caution./mbr Updates the Master Boot Record without changing the partition table on
sector 0 of the disk that contains the partition specified by SYS, ALL,
or drive letter. When used with /nt52 option, the master boot record
is compatible with operating systems older than Windows Vista. When
used with the /nt60 option, the master boot record is compatible with
Windows Vista, Windows Server 2008 or later.Example:
To apply the master boot code that is compatible with NTLDR to the volume
labeled E:, use the following command:bootsect /nt52 E: