中国DOS联盟

How to make a batch process to let GHOST restore after renaming .gho For example Rename .gho to .bak Directly use Ghost-clone,mode=pload,src=d:\ghost\sysbak.bak,dst=1:1 /sure /rb It seems not okay.

Last edited by kookycy on 2008-10-22 at 20:14 ]

@echo off

ren d:\ghost\sysbak.bak sysbak.gho

Ghost-clone,mode=pload,src=d:\ghost\sysbak.gho,dst=1:1 /sure /rb

@echo off

ren d:\ghost\sysbak.bak sysbak.gho

Ghost-clone,mode=pload,src=d:\ghost\sysbak.gho,dst=1:1 /sure /rb

Renaming doesn't affect usage, no problems at all.

Of course, the premise is that the command is not written incorrectly.

This should not be able to use the REN command under NTFS.

I mean when the disk is NTFS, usually it can't be seen under DOS.. Unless NTFSDOS is loaded

Last edited by kookycy on 2008-10-22 at 16:00 ]

Originally posted by HAT at 2008-10-22 14:17:

@echo off

ren d:\ghost\sysbak.bak sysbak.gho

Ghost-clone,mode=pload,src=d:\ghost\sysbak.gho,dst=1:1 /sure /rb

Just add a renaming command in the batch?

GHOST doesn't have such a parameter, right.

Thanks.

Ghost certainly supports renaming. At least renaming it to bak.gh is fine.

Ghost -clone,mode=pload,src=1:6\ghost\system1.gh:1,dst=1:1 -sure -rb
1:6 means the 6th partition of the first hard disk.
system1.gh:1 means if it is the backup data of the first partition in the full disk backup, it doesn't matter if it's a single partition.

But in the previous v8.3 v10.0.x series, there were differences in the identification of IDE dual hard disks. Forgotten. It seems that v8.3 identifies according to the BIOS hard disk boot sequence. And v10.0.x identifies according to the master-slave arrangement of the data cable. So when using dual hard disks, it is still advisable to be cautious with one-key restore tools unless you know what you are doing.

Who told you that NTFS doesn't support the ren command?

In my GGhost one-click recovery, it's renamed by default, and I haven't heard of any problems.
For example:
ghost -clone,mode=pload,src="1.4:\gghost..\sys.ggh:1",dst=1:1 -fx -sure -fro

The owner can't use it because the command is wrong, not because of the extension problem.

Originally posted by HAT at 2008-10-22 15:02:
Who told you that NTFS doesn't support the ren command?

His meaning is that NTFS is read-only under DOS and cannot be renamed.

Originally posted by yishanju at 2008-10-22 15:39:

He means that NTFS is read-only under DOS and cannot be renamed

If it can't be renamed, it's just that the NTFS driver used is incorrect. Just change to one that supports write. The problem is, there's no need to rename at all. Hehe.

Originally posted by HAT at 2008-10-22 15:02:
Who told you that NTFS doesn't support the ren command?

Dude, you got it wrong. Although I'm very green, I'm not that weak. NTFS definitely supports REN. It just can't change the name.

Last edited by kookycy on 2008-10-22 at 16:06 ]

Originally posted by lianjiang2004 at 2008-10-20 15:22:
In my GGhost one-click recovery, it is renamed by default, and I haven't heard of any problems.
For example:
ghost -clone,mode=pload,src="1.4:\gghost..\sys.ggh:1",dst=1:1 -fx -sure -fro

The landlord can't use it,...

Thanks... Your command is correct

Why is there no such statement as 1.4: in the GHOST tutorial?

Oh, dizzy... I tried 1:4 again and it works..

I also added GHO:1 before. Did I write the format wrong at that time.. - -

The new version format is 1.4, and it was 1:4 before, but both the 1.4 format and the 1:4 format are supported.