中国DOS联盟

The building owner is very enthusiastic, support, may the building owner overcome the speed problem!

Originally posted by zts59 at 2007-4-11 10:11 AM:
The landlord is very enthusiastic, support, may the landlord overcome the speed problem!

The speed problem, I have tried many methods, but there is currently no breakthrough.
However, if the partition is smaller, there is no big difference..

Just now, I have successfully added the function of writing the content of the specified sector position of the file (including the compressed file generated by this program) to the disk in the main program. (That is, the file at the source position also supports the "-" minus sign!)
Preliminarily passed the test....

And corrected the following BUG:

(Very inconspicuous, but caused a crash!!)

fseek(f,0-strlen(zlibKeyTRUE),SEEK_CUR)
causes an error
Later found that this 0 is problematic, changed to 0L, and it is okay!





So far, all the functions planned to be added have been successfully added to TOdisk!

(Some of these problems are very difficult! Even to the point of almost making me give up! Finally, they were all taken down by me one by one! Writing this system took me more than half a year of precious time, and the dark circles under my eyes have not disappeared until now, I feel really scary, but finally it's done!
Also, thank the friends who supported and encouraged TOdisk!)

Except for the speed aspect, there will be no major updates in the future..
Have re-uploaded: (The help in the program is still old, not updated yet... But it will be soon)
All basically passed the test
Welcome to play..(If there is a problem, please report the BUG... I will improve it when I have time)

Last edited by GOTOmsdos on 2007-4-17 at 07:01 AM ]

Identify and correct the following bugs:
1. When the floppy disk was originally running a program in the floppy drive, the floppy disk was not recognized. Only after running the program when the floppy drive was empty and then inserting the floppy disk could the floppy disk be recognized.
2. Problem with display when writing volume segments.
3. The number of sectors of the file's task amount was not changed according to the specified starting sector.

The format of the inquiry has been improved.

Re - uploaded.

Last edited by GOTOmsdos on 2007 - 4 - 17 at 07:02 AM ]

Top, support the boss GOTOmsdos

Download the latest version of the file, which can be used; but after loading IFS, it cannot run. Restarting and changing to load NTFS4DOS still cannot run TODISK. I wonder if TODISK can recognize the NTFS drive letter after loading IFS or NTFS4DOS?

Originally posted by terse at 2007-4-15 06:35:
To download the latest version of the file, it can be used; but after loading IFS, it cannot run. Restarting and changing to load NTFS4DOS still cannot run TODISK. I wonder if TODISK can recognize the NTFS drive letter after loading IFS or NTFS4DOS?

I can run todisk under IFS or NTFS4DOS

One

It is best not to completely rely on NTFSPro or IFS and other NT support tools under DOS. The reliability is not guaranteed, and the speed may be slower. It is best to use FAT - series partitions for system backup. If you must use NTFS, it is recommended to use the new version of GHOST.

Two

TODISK searches for drive letters according to the DOS logic. After loading NTFSPro, NTFSPro adds drive letters to NTFS partitions. These drive letters can be used together with files in TODISK, but cannot be used as partitions.

However, to operate these NTFS partitions, you can use numbers like 1:1, 2:2, etc., which is more accurate (but you need to check in advance with TODISK - P. But the partition numbering of TODISK is the same as that of GHOST, using a direct sequential extension method, which is very intuitive, unlike Linux which has special regulations).

Three

The update of TODISK is as follows:
Add the function of replacing the first FAT with the second FAT for FAT partitions.
The parameters are as follows:
TODISK - FAT2 D:
Replace the first FAT of drive D: with the second FAT.

Re - uploaded

Last edited by GOTOmsdos on 2007 - 4 - 17 at 07:03 AM ]

Just entered DOS and tried loading IFS and NTFS4dos respectively but couldn't run TODISK. Is there something wrong with my CONFIG.SYS?

I know if there are conflicts between programs? Help take a look at the CONFIG.SYS file as follows!

device=QHIMEM.sys /N32 /W
device=UMBPCI.SYS
DEVICEHIGH=QCACHE.SYS /L /S5
device=XDMA.SYS
FILES=20
BUFFERS=30
SHELL=COMMAND.COM /P /F /E:4096
FCBS=4,0
STACKS=9,256
DOS=HIGH,UMB,AUTO
lastdrive=z

Been looking for a software that can recognize NTFS drives after loading IFS or NTFS4dos, not sure if it's possible?

Last edited by terse on 2007-4-15 at 10:56 AM ]

Maybe XDMA.SYS is loaded, causing TODISK not to run..
I don't know the reason? TODISK doesn't have any special requirements, just uses ordinary interrupts 13, 25/26, and has very small memory requirements. Generally, 70 - 370KB is enough.
It also doesn't work with UDMA.SYS...
I don't know what the DMA.SYS series does in DOS?

Last edited by GOTOmsdos on 2007-4-15 at 11:28 AM ]

......

Last edited by GOTOmsdos on 2007-4-15 at 11:33 AM ]

Thanks for the reply. I'll go try it again and report back.

CONFIG.SYS is changed as follows:

device=himem.sys /testmem:off
FILESHIGH=20
BUFFERSHIGH=10,0
SHELL=COMMAND.COM /P /F /E:4096
FCBSHIGH=4,0
STACKSHIGH=9,256
LASTDRIVEHIGH=Z
DOS=HIGH,UMB,AUTO

After entering DOS for the first time, NTFS4DOS is loaded successfully and TODISK runs. As you said, the drive letter cannot be seen!

After entering DOS for the second time, IFS is loaded and TODISK does not run successfully. I will look for other versions of IFS to see how it goes!

By the way, is it quite difficult for TODISK to recognize NTFS drive letters after loading NTFS4DOS or IFS in the current situation?

Methods are not without:
1
From inside the drive letter of the DOS system, I don't know if TC/BC has functions
2
From the principle of NTFSPRO allocating drive letters for NTFS partitions, this might be more complicated
3
From the order in which NTFSPRO allocates drive letters for NTFS partitions, this is still probably easy to implement. Wait a minute, I'll take a look at its allocation order and pattern...

Last edited by GOTOmsdos on 2007-4-15 at 09:28 PM ]

改为换位比较好，不舒服再运行一次再换回来。免得替换后情况更糟糕。

The original text in Chinese here is: "改为换位比较好，不舒服再运行一次再换回来。免得替换后情况更糟糕。" Since it's already in Chinese, we just present it as is. But according to the requirements, if it's not translatable, return the original text. Wait, no, wait. Wait, the user provided a quote in Chinese, and the subsequent Chinese text is part of the user's input. So the entire relevant part here is:

Originally posted by GOTOmsdos at 2007-4-15 10:03 AM:
三

TODISK更新如下:
对FAT分区增加用第二个FAT替换第一FAT的功能.
参数如下:
TODISK -FAT2 D:
用D:盘的第二FAT替换掉第一FAT
...

改为换位比较好，不舒服再运行一次再换回来。免得替换后情况更糟糕。

So the part "改为换位比较好，不舒服再运行一次再换回来。免得替换后情况更糟糕。" is in Chinese. So the translated output for that part is:

It's better to swap positions. If you're not comfortable, run it again and swap back. To avoid the situation getting worse after replacement.

Wait, no. Wait, I need to translate the Chinese text "改为换位比较好，不舒服再运行一次再换回来。免得替换后情况更糟糕。"

"改为换位比较好" can be translated as "It's better to swap positions".

"不舒服再运行一次再换回来" can be translated as "If you're not comfortable, run it again and swap back".

"免得替换后情况更糟糕" can be translated as "To avoid the situation getting worse after replacement".

So combining them:

It's better to swap positions. If you're not comfortable, run it again and swap back. To avoid the situation getting worse after replacement.

But let's do it more smoothly:

It's better to swap positions. If you're not satisfied, run it again and swap back to avoid the situation from getting worse after replacement.

Wait, but let's be precise.

"改为换位比较好" -> "It's better to change to swapping positions"

"不舒服再运行一次再换回来" -> "If you are not comfortable, run it again and swap back"

"免得替换后情况更糟糕" -> "To avoid the situation from getting worse after replacement"

So putting it all together:

It's better to change to swapping positions. If you are not comfortable, run it again and swap back to avoid the situation from getting worse after replacement.

But maybe a more natural way:

It's better to swap positions. If you're not comfortable, run it again and swap back to prevent the situation from worsening after replacement.

Yes, that works.

So the full translated content including the quote and the subsequent Chinese text:

Originally posted by GOTOmsdos at 2007-4-15 10:03 AM:
Three

TODISK update is as follows:
For FAT partitions, add the function to replace the first FAT with the second FAT.
Parameters are as follows:
TODISK -FAT2 D:
Replace the first FAT of drive D: with the second FAT
...

It's better to swap positions. If you're not comfortable, run it again and swap back to prevent the situation from worsening after replacement.

Originally posted by wang6610 at 2007-4-16 12:09 AM:


It's better to swap positions. If it's still uncomfortable, run it again and swap back. To avoid the situation being worse after replacement.

Do you mean, add swapping the first FAT to the second FAT?

In this way, it's unnecessary, because DOS will automatically write the updates of the first FAT to the second FAT at any time..