中国DOS联盟

Completely don't understand oh~~~ Can you explain it in detail? I didn't see anything like copy-run either.
path?? There's nothing there either.

copy-run means you can just run it directly after downloading, no installation is needed. The specific program to run is HXLDR32 in the BIN folder. And for the path, if the BIN path is not included in the %PATH% environment variable, you need to add it first. For example, if your HXLDR32.EXE is stored in C:\HX\BIN, then you need to put the path C:\HX\BIN into the %PATH% environment variable, and then run HXLDR32. In this way, you can run the Win32 Console program directly just like running a general DOS program.

"Why the reason for 32-bit is that in the future everyone can program and run directly in the Windows graphical interface"
This I still don't understand. Can't the DOS virtual machine of the Windows system run 16-bit programs?

Does HX DOS Extender seem to support DirectX, WinSock, OLE? So powerful? Is it similar to wdosx? Of course, wdosx changes the program file, and it seems to only provide flat memory access.

Great, but there are no a few examples to let people intuitively and quickly understand it.
Tested a simple program to apply for memory, it seems that it uses Windows DLL.
Very good, but does the console program use DirectX? If it can, then similar GUI can also? But, as long as VESA can be used, then a graphical interface can also be realized, but if it is another type of display device (for example, VESA is not supported), it will not work.

Last edited by jawbin on 2006-5-16 at 10:25 ]

Originally posted by jawbin at 2006-5-16 10:05 AM:
Great, but there are no a few examples to let people intuitively and quickly understand it

HX DOS Extender has some similarities with WDOSX, but its functions are much stronger than the latter.

Since the download address above is the latest test version released yesterday, not the official full version, that's why there are no demo programs in it. The official full version (released half a month ago) comes with many demo programs, including DirectDraw, OpenGL, SDL, WinSock, DPMI test programs, etc., see the attachment:

Thanks Wengier :)
Download and take a look!
Running ddtest prompts "video mode 800x600x16 with LFB not supported"
I'm running it in DOSBox under Windows XP
Running getvmode prompts "no VESA information available for mode 3"
The thread has this in text mode, I get it, heh, I'm really silly..

Last edited by jawbin on 2006-5-17 at 08:37 ]

In real machines, this message generally doesn't appear, unless the graphics card is too old. At this time, it can be solved with Scitech Display Doctor. On new graphics cards, this problem won't occur. Don't test in DOSBox, as it doesn't simulate VESA and some other hardware very well yet.

By the way, it seems that the DOS versions of Kingsoft Antivirus or Jiangmin's KV used WDOSX. I remember that WDOSX doesn't support graphical interfaces (FORM in Delphi), right? Does it implement it directly using VESA or something? Does Wengier know?

WDOSX, like DOS4GW and others, are all DOS expanders that provide large memory support and are often used as stubs for protected-mode DOS programs. WDOSX supports some Win32 APIs but is very limited, so this aspect can be almost ignored. Those DOS antivirus software and other similar programs are truly protected-mode DOS programs that do not use Win32 APIs, and their way of accessing the graphical interface has no direct relation to WDOSX.

Thanks!;)

I just booted into DOS and tested most of the examples (since I didn't copy SDL.DLL to an easy-to-find path, so SDL wasn't tested. Also, the sound card driver wasn't loaded, so the related programs weren't tested. My sound card is AC'97, not sure if there's a DOS driver...), and found several "import not found", respectively from CreateFontIndirectW, GetObjectW, GetOutlineTextMetricsW in GDI32.DLL and WSARecvFrom and WSARecv in WS2_32.DLL.

Also, GDITEST is indeed for testing GDI. When will there be a USERTEST? It would be nice (support basic components like Button, Edit, etc., too fantasy, heh, because it said it can run console, so it can't support GUI..)

Also, it seems DDTEST (can't remember clearly) is nonsense

Last edited by jawbin on 2006-5-16 at 11:21 ]

Those example programs can't have "import not found", I've been using them all the time, and those programs have never had this phenomenon. Maybe you haven't set it up properly.

I added HXRTD\bin, c:\windows\system32, c:\widnows
Should that be enough?
When running, it doesn't seem to be able to be entered directly, so I always run the program as a parameter of dpmild32
By the way, a test program for applying for memory that I can run in DOSBox also has an error on the real machine..
Gotta eat now :P

Last edited by jawbin on 2006-5-16 at 11:30 ]

Originally posted by jawbin at 2006-5-16 11:28 AM:
...
When running, it seems that you can't input directly, so I always run the program as a parameter of dpmild32
...

That's not right. If HXLDR32 is loaded, you can input and run directly, and there's no need to run the program as a parameter of DPMILD32. It seems it's still suggested to carefully read the instructions and check the system configuration, because all the problems mentioned above have never occurred on my side (especially the built-in demo program. Obviously, only programs that can run normally will be added to the demo package by its author. If the settings are normal, "imports not found" will never occur; or it can be said that an important function of these demo programs is to help users judge whether their HX DOS Extender is correctly configured. If a problem occurs, it means the configuration is not yet complete).