China DOS Union

Google and forums, in addition to greatly facilitating our lives, it seems that they have also made everyone lazier.

I remember I mentioned it in a post, but it seems no one followed my clues,

Where do standards like BIOS large memory address space, BIOS32, DMI, enhanced hard disk access extensions come from? Of course, from phoenix-award. Then, when you guys search on Google, should you search for phoenix or INT13?

Here's an official link: http://www.phoenix.com/en/Customer+Services/White+Papers-Specs/pc+industry+specifications.htm

Bus standards such as USB, 1394, CPCI, etc., all have their own communities, and the above phoenix page also provides links to download these standard documents.

Needless to say, other things? SATA is Intel's standard, and AMD's programming manuals for CPU and north-south bridge optimization are more detailed than Intel's...

I hope all brothers think more about the origin when searching for a certain standard, heh heh

Publicize the clues given before:

In the clock interrupt analysis post by兄台 zyl910 last month, I talked about the Intel and AMD x86 architecture programmer guides. And I urged everyone to find and share other technical documents, but the result was completely ignored....

The other day, in a post by兄台 qb45 about INT13 extensions explanation, several brothers mentioned suffering from incorrect documents, and I replied again saying that we must read the official standards, which seemed to be ignored again....

There should be some others, but I can't remember them~

INT13 extensions, the disassembled DBR of WIN95OSR2 that I looked at
rapid prototyping:)

Well, even if you only use high-level languages such as C/C++, it's a good habit to often look at assembly code. You can continuously review the time and space efficiency of each operation and each feature in the high-level language; understand some details of compiler optimization and the operating system.

But I think this doesn't prevent you from having a relevant standard document at hand for reference while coding