中国DOS联盟

5.0 (Elevation) The bootable disk has been prepared, but I always feel that the difference from version 4.0 is not too big. Although new technologies have been introduced and portability has been improved, after all, just optimizing the code is not enough. And even if it is to be released, it will go through a long testing period, so the decision is made to terminate the disk pressing work, and the code is handed over to a few of my friends for sharing and research. Please understand.

6.0 (Coalfish) The development code for the bootable disk named Black Snowfish is being designed. The initial considerations include the following functions: categorically boot MS-DOS mode, install/uninstall boot menu for Windows 9x series (CIH safe date function is no longer included), Windows Me can directly enter the command prompt without tedious modifications, the expert mode includes network support (supports nearly 30 types of network cards, automatically detects and loads drivers and can select network protocols. Includes http/ftp/telnet server and client programs, other hosts can directly access the resources of this host or log in to this host through the local area network, and the main directory of the http server function needs to be specified by the user), and a graphical file manager. Due to the various inconveniences brought by Chinese support, this version will only be developed in English, Russian, and German versions.

I tried it (I made the boot disk using DSKWRITE under DOS), and I found that some concepts are indeed very novel. Especially the USB boot function, but I can't test it (I don't have USB settings, everyone can give it a try), and it's well done by combining the functions of GRUB and MEMDISK! But may I ask, why is it formatted as an Ext2 partition? In Windows, it really can't be viewed, and in DOS, although it can be viewed with LTOOLS, it's not very convenient.

Also, may I ask, are you proficient in Russian and German?

Regarding USB booting, I've taken a close look. Actually, this "Bootable USB Loader" was modified by changing a few bytes from the "Bootable CD Loader". But why is this BCDL.BIN using DUSE 4.3 (!) to drive USB devices instead of the latest DUSE 4.4 version? I've noticed that this DUSE.EXE isn't loaded by BCDL.BIN during startup, so it's currently not possible to achieve USB booting with it. Also, DUSE is not very compatible with many systems, so the success rate...

The following is a quote from Wengier on 2003-6-24 4:23:08:
Why is it made into the Ext2 partition format? It is indeed not viewable under WIN, and although it can be viewed with LTOOLS under DOS, it is not very convenient either.

Actually, you can use Explore2fs to view it.

In fact, I don't really want to use the BCDL020 method to boot the CD-ROM and USB. The best way is to find the method of BIOS controlling the boot. I tried to extract the BIOS BIN file and am currently extracting the part that controls the boot process. It's very difficult. I hope everyone can help me.

Trying to extract the bootloader from the BIOS is really a master. But the boot part in the BIOS is often only corresponding to that computer, and it's not necessarily universal.

So I'm currently reading the model of the industrial specifications for El Torito and BIOS boot:
http://www.phoenix.com/resources/specs-cdrom.pdf
http://www.phoenix.com/resources/specs-bbs101.pdf

Let's focus again~~~

The following is a quote from kevinet on 2003-6-24 22:08:16:
So I am now reading the model of the El Torito and BIOS boot industry specifications:
http://www.phoenix.com/resources/specs-cdrom.pdf
http://www.phoenix.com/resources/specs-bbs101.pdf

High, hope to have a great work soon.

Really a master, admiration!

Admired, learning from you!!

oooooooooooh,old bird~

Oh, you're a real expert! I'm completely in awe.