中国DOS联盟

My Ultimate Countermeasures:
　　1. When there is no problem, record important data. Note that it is to be recorded in writing first, and then electronic records. For example, the values you have modified in CMOS (especially hard disk parameters and reading/writing modes), the cylinder-head-sector values of the hard disk partition, the MBR of each hard disk, the partition BOOT of each partition (back up to floppy disk, USB flash drive with SRCMBR/SRCBOOT/SRXBOOT). The system should be.GHO to other partitions outside the first partition. It is better to have another reliable hard disk specially for backup (especially personal data).
　　2. After a problem occurs, the first thing is not to be in a hurry to try to restore software. Some software has side effects, such as DISKFIX.COM. I have used it many times and was invincible before, but this time it wasn't. There were bad sectors in the beginning part of my disk, so I reserved 200 MB of blank space and then carried out the partitioning work. But when a problem occurred recently, I tried DISKFIX, and as a result, nearly half of the first partition was damaged. Fortunately, I had made a.GHO not long ago and it was only the system partition, so the loss was not too big -- personal data is never placed in the first partition!
　　After a problem occurs, you can use SPFDISK.EXE to "re" partition the hard disk, which is based on the old data recorded in writing -- this is also a recovery method, and I have succeeded.
　　If your first partition is partitioned in order from the beginning part of the hard disk, you can also try DISKFIX. However, it is better to run PQMAGIC once later to correct some data errors, but do not do any other operations, and restart immediately.

But maybe I'm showing off my ignorance -- although the above are all my experiences and lessons.

Alas, just give a complete and usable one, hehe

The next version VTHZMK v2.0D will
Add the /? command to write error messages and help information to a file;
Add the /+ command to allow merging different.EXE files into a complete file.

In addition, I used TS2.EXE to generate several HZK16 Chinese character libraries of other styles. Please see the merged.EXE and.NEW files and screenshots in the attachment, as well as the new version information file.

The new version of VTHZMK is being tested intensively. ;)

I've debugged it several times these past two days, :mad: Why does the VTHZMK.COM during debugging always fail to pass?
　　The VTHZMK in the attachment is version 2.0D, being debugged; 1, 2, 3, 4, 5, 6, 7, 8 are.EXE files renamed from eight EXE files generated with different style font libraries (for convenience); 12345678.BAT is intended to generate a VTHZ~!~.EXE with multi-style glyphs displayed on the same screen through the merging function. It can be generated, but every time I have to close the XP command prompt window, saying an invalid instruction is encountered. In TR debugging it doesn't "crash", but in BXD it "crashes", crashing at the final EXIT segment:
mov ax,4C00h
int 21h

　　In the past Sheng Ying could be born smoothly, I wonder when my new version VTHZMK will be delivered smoothly???
　　Please help the webmaster, moderators, and experts!!!

Can we directly generate a COM file and use the INT 20H instruction to return to the DOS prompt?

It's not the problem with the generated .EXE, but with VTHZMK.COM itself. MOV AX,4C00H and INT 21H are the standard conventional ways to return to DOS with ERRORLEVEL.

If it's just VTHZMK.COM, can we not try INT20 again? It's just that there's no EXIT parameter. (Sorry, I just think we can try this way.)

Can DOS graphical interface software be localized into Chinese?

Re LiveOnLove:
　　I tried mov ax,4c00h//int 21h and int 20h and ret, but none worked.
It should be a problem with other parts, because there were no such problems before adding the merging function.
　　Thank you for the discussion!

Originally posted by gzx8 at 2005-12-25 10:37:
Can DOS graphical interface software be localized into Chinese?

The reply has been made on your post.

In the DOS console of XP, debugging VTHZ～！～.EXE with DEBUG doesn't cause a crash (but there are no echo characters, I think it should be okay in pure DOS). 7 strange? And in XP, the error is shown at CS:0416, but it seems there's no problem? Could it be that in the non-debug environment, some registers of the system are damaged?

Last edited by LiveOnLove on 2005-12-25 at 11:46 ]

No, that's not right... You directly run the just-generated VTHZ～！～.EXE and there are no problems at all!!! (Can't test echo under XP) To see the program segment of VTHZMK.COM. Well... Without the source code for this part, it's not easy to analyze by disassembling. Originally, LZ, you look for it again.

Last edited by LiveOnLove on 2005-12-25 at 11:48 ]

Re LiveOnLove:

　　Thank you for your effort! After the weekend (too busy), I will carefully debug VTHZMK.COM again.
　　In addition:
　　VTHZ~!~.EXE only performs the task of loading Chinese character glyphs. To see the effect, please TYPE VTHZ~!~.NEW (this file should have been provided in the compressed package). The effect should be like the screenshot on floor 108!

Originally posted by Benshi at 2005-12-25 02:52 PM:
Re LiveOnLove:

　　Thank you for your efforts! After the weekend (too busy) I will carefully debug VTHZMK.COM again.
　　In addition:
　　VTHZ~!~.EXE only performs the task of loading Chinese character glyphs. To see the effect, please T ...

Benshi, you are too polite. Let's study together. I need to learn more from you. I don't have the TYPE that NEW file, I made a mistake. HOHO. I'm sorry.

Just tried the new version, and it's much more powerful!
Assembly, I've forgotten it all. I had a one-semester course in college before, but I didn't study hard, ashamed! Watching everyone discuss, I really can't chime in, but I'll always support everyone. (It's a good thing, I have it too, heh heh)