Dissecting DOS

Just as I expected, no surprises.

You can make your own operating system by studying books like this one. The source code will reveal much about how to write a kernel.

The book was pretty good with the information that it did give. Some of the programs that were discussed in the book were not on the disk like the book said they were. Alot was left out and not touched upon like they should have been. There should have been a short section on Device drivers, just to give a reader an overview that they do exist, and maybe a little on installable file systems. I bought this book because the code was written in Assembler. I probably should have bought FreeDos instead except that is was written in C. All the information that I could not find in this book I found in the Code for Free Dos.

The book provides an indepth analysis of the way DOS works, contains invaluable information that you can find nowhere else. Nevertheless especially in the beginning I 've got the impression that bypasses -I admit that I'm not the most proficient assembly user and it can be my mistake- some funtamental elements very quickly. (I still try to find a way to list my files without using DOS interupts as the book doesn' t really explain what exactly interupt 52h/21h does and I 've not yet really understood how the accompanying program printcds work - written in C)