China DOS Union

Originally posted by xugaohui at 2008-11-29 17:32:
It was originally:
Some people also use the same technology as the vt system software to display Chinese characters.
http://bbs.wuyou.com/viewthread.php?tid=131706&extra=page%3D1&page=1
This thing is very good.
Currently...

RE:xugaohui:
I read the post on Wuyou. I also studied the.PSF font file format, and it's very simple to make. However, I don't want to steal someone's thunder, so let him have his moment! ——But that hzpsf.exe is actually over 500K, which is too exaggerated. I can do it in about 250 bytes. The biggest problem with window programming may be its large size, which is why I haven't wanted to learn window programming so far.

VT technology should be applicable to any high-level or low-level language. If using BIOS programming, that is, interrupt calls, programming in Qbasic will require some extra effort. It's simpler with QB, Turbo Basic, First Basic, or other compiled languages.

The attachment is an example I made with FirstBasic (source code and.EXE). Other BASICs should be similar.

Thanks, it can display Chinese after running. I'll study it.
I don't understand First basic, so I'll search it on Google.
Found here:
http://www.cn-dos.net/forum/viewthread.php?tid=944&page=6&fpage=1&sid=dSaGju
Ben Shi is really an expert.
Isn't the window interface of Norton Utilities 8.0 Chinese version for DOS generated by power basic? It's exactly the same, probably written by power basic+.RTLink.

[ Last edited by xugaohui on 2008-12-1 at 01:24 ]

I use the qboot tool to boot, and it should have loaded vtm. Why can't Chinese be displayed normally when using the English edit to edit a Chinese file? The Chinese-English bilingual software also can't display Chinese normally. Thanks!

Single-byte encoding and double-byte encoding. If you know the difference between the two, it's easier to understand the so-called new and old Chinese character internal codes of VtMagiK. You can also understand the source of the intelligent recognition of Chinese character system tab characters. You can also understand why the software tab characters are messy after using VT technology.

Originally posted by xugaohui at 2008-11-29 17:32:
Yulu:
After localizing the command.com of FreeDOS, it can only run under FreeDOS. Directly replacing the command.com of MSDOS 7.1 makes it unusable.

It shouldn't be like that. I directly replaced the command.com of the localized FreeDOS 1.0 with the command.com of Xiaoyun's localized MSDOS 7.1, and it still runs normally! It's not exclusive!

The COMMAND.COM of FreeDOS is in delayed processing of variables when executing the for command, unlike MS which executes all at once after reading the entire for command. The boot disk of 98SE doesn't recognize FreeDOS's COMMAND.COM at all. After replacement, pressing the F5 key in the config.sys menu always prompts you to enter the path of COMMAND.COM. Even if you enter the correct one, it still prompts you. Entering the path of MS's COMMAND.COM is fine.

The COMMAND.COM of FreeDOS can't recognize the command "set path=D:\", this doesn't search the D:\ directory, it can only be written as "set path=D:".

The COMMAND.COM of MS can recognize these two kinds of search paths.

The COMSPEC variable of MS is C:\COMMAND.COM.

The COMSPEC variable of FreeDOS is c:\command.com.

Conversely, MS's COMMAND.COM can't be used to replace FreeDOS's COMMAND.COM.

There are many other details that are different.

[ Last edited by xugaohui on 2008-12-1 at 11:33 ]

There must be differences, but it has nothing to do with whether it's localized or not, right!?

Reply to the example program on floor 16.

I was using vbdos 1.0, and just modified the bas of firstbas a bit, and it works. But the first time the generated program runs, it's okay. The second time it runs, it always shows "Display Chinese characters" and there's no garbled code anymore. And your program has garbled code at the start of each run, then shows Chinese characters later, but you used the screen statement to clear the screen.

That is to say, the modified basvtfnt program might affect other programs with extended ASCII display, and garbled code might appear.

This is how I modified it:

' $INCLUDE: 'VBDOS.BI'
..................Omitted, removed screen 0 and cls to clear screen
DEFINT A-Z
a$ = ""
FOR i = 0 TO (8 * 16 - 1)
READ b
a$ = a$ + CHR$(b)
NEXT
PRINT "Before replacing font: ";
PRINT CHR$(&H80); CHR$(&H81); CHR$(&H82); CHR$(&H83); CHR$(&H84); CHR$(&H85); CHR$(&H86); CHR$(&H87)

PRINT "Press any key to see font changed..."
b$ = INPUT$(1)

DIM regs AS regtypex
regs.AX = &H1100
regs.BX = &H1000
regs.CX = 8
regs.DX = &H80
regs.BP = SADD(a$) 'The following three lines are changed to vbdos commands.
regs.ES = SSEG(a$)
CALL INTERRUPTX(&H10, regs, regs)

PRINT "After replacing font: ";
PRINT CHR$(&H80); CHR$(&H81); CHR$(&H82); CHR$(&H83); CHR$(&H84); CHR$(&H85); CHR$(&H86); CHR$(&H87)

PRINT "Press any key to see font restored..."
b$ = INPUT$(1)
'Removed and changed to display mode 0
END

If the vbdos program has a window interface, it can only use screen 0. The default is originally 0.
If you add the statement screen 12 : screen 0 when exiting the window program, this will clear the DOS prompt interface.
May I ask how to modify the program to achieve that each run starts with garbled code, shows Chinese characters after pressing any key, doesn't clear the previously displayed content on the screen, and doesn't affect other programs with extended ASCII characters?

[ Last edited by xugaohui on 2009-1-2 at 16:07 ]

The following program resets the character set using the system - default 8x16 ASCII dot matrix without clearing the screen characters. You can test it.

mov ax,1130h
mov bh,6
int 10h ; get font type bh info into; cx=points,dl=rows, es:bp=ptr
xor dx,dx;mov dx,0
mov cx,100h
mov bx,1000h
mov ax,1110h
int 10h ; font load bh=points, bl=block; cx=qty, dx=1st char code; es:bp=ptr to font table
ret

[ Last edited by 本是 on 2009-1-2 at 23:34 ]

Can't understand assembly, so I'll bookmark it. Thanks, Ben Shi.

"Excuse me, to achieve that every time it runs, it starts with garbled text, and after pressing any key, it displays Chinese, without clearing the previously displayed content on the screen, and without affecting other programs with extended ASCII characters, how to modify the program?"
Just call the following code segment whenever you want to display normal English glyphs.

DIM regs AS regtypex
regs.AX = &H1130
regs.BX = &H0600
CALL INTERRUPTX(&H10, regs, regs)

regs.AX = &H1110
regs.BX = &H1000
regs.CX = &H100
regs.DX = 0
'regs.BP, regs.ES obtained from the previous interrupt call
CALL INTERRUPTX(&H10, regs, regs)

RETURN

[ Last edited by 本是 on 2009-1-3 at 00:35 ]

Tested in VBDOS, very good and practical. Thanks again, Ben Shi.

Downloaded, only to find that I couldn't download. Probably because I don't have enough points.