中国DOS联盟

Backing up with Ghost under an NTFS partition. Both the source partition and the partition where the image is stored are NTFS. After completion, the GHO file cannot be found, but the used space on the target disk has increased. Does anyone know the reason? Using Ghost 8.3, and also tried 8.2, the same problem occurs!

What tool disks are used to make ghost backups?

It can be basically determined that the gho file is hidden, but it is not excluded that some tool disks use deformed directories for hiding.

The former can be done through the command line prompt command under xp
attrib -s -r -h "The partition where the image is stored:\*.gho"
or
attrib -s -r -h "The partition where the image is stored:\folder\*.gho"
For the latter, see here
http://www.cn-dos.net/forum/viewthread.php?tid=20654&fpage=1&highlight=%E7%95%B8%E5%BD%A2

No, I used a DOS boot disk to boot, then manually used Ghost to back up, without adding any parameters. The backup file is also directly placed in the root directory.

In Windows, I can't find the gho file even after showing hidden files and system files. I also can't find it when using Ghost under DOS.

Do you use Ghost parameters for backup or select in the Ghost interface? Do you perform Ghost from the CD by booting from the CD? Or boot from USB? Or boot with GRUB DOS?
1: Check if there is a problem with your Ghost usage method.

Ghost interface, boot from CD and execute CD - based Ghost. After entering the Ghost interface, choose Pation to Image, select the source partition, the destination partition, and fill in the file name. It is estimated that there should be no problem!

Then as mentioned above, please check if DOS has loaded UDMA, XDMA, or QDMA (one of them). If so, it is estimated that the reason for not correctly loading Ultra DMA is to use chkdsk under Windows to check the disk.

What are UDMA, XDMA, QDMA? How to check? And how to change them?

Check if the config.sys content contains one of these 3 strings indicating that the Ultra DMA driver has been loaded, or use the command mem /c /p under DOS. If there is no mem command, download it from here:
http://www.cn-dos.net/forum/attachment.php?aid=1892&checkid=0a482&download=1

The person upstairs is really amazing. The files came out after using chkdsk, haha. I'll first see if it's loaded in DOS.

Oh....It can basically be concluded that it is caused by using an incorrect Ultra DMA driver. Edit the content of config.sys. Delete the entire line of content similar to DEVICE?=UDMA.SYS?? or DEVICE?=XDMA.SYS?? or DEVICE?=QDMA.SYS??. You can also use the latest Ultra DMA driver QDMA.SYS. Download address http://johnson.tmfc.net/dos

DOS=HIGH,UMB
DEVICE=HIMEM.SYS
REM DEVICE=EMM386.EXE NOEMS
DEVICEHIGH=VIDE-CDD.SYS /D:IDE-CD
COUNTRY=001,437,COUNTRY.SYS
SHELL=COMMAND.COM /P /E:640
FILES=30
FCBSHIGH=4,0
BUFFERSHIGH=20
LASTDRIVEHIGH=26
STACKSHIGH=9,256
SET TEMP=.
SET TMP=.
REM MS-DOS 7.10 Boot Disk
Brother, here is all the content, but there seems to be nothing as you mentioned

Then there might be errors on the disk before backup, so the.gho file can be seen after disk check. It is necessary to check the disk regularly

But I have tried this on many machines, including new machines that I just bought, installed the system and made backups, and it's the same!

A bit strange...
Remove COUNTRY=001,437,COUNTRY.SYS from config.sys
Then post the content of autoexec.bat