News:

Masm32 SDK description, downloads and other helpful links
Message to All Guests
NB: Posting URL's See here: Posted URL Change

Main Menu

MS-DOS int 21 functions should work under XP!!

Started by laskar01, July 10, 2012, 05:48:13 AM

Previous topic - Next topic

jj2007

If you want to use Kip's book, check this post about using his library in parallel to the Masm32 SDK.

laskar01

Thank you all.
I am finishing the BIOS chapter now, but neither BIOS is availible running MASM under XP, correct? All I have is a managed "BIOS"?

Lasse

Gunther

Lasse,

you should read Hutchs posts very careful. He is absolutely right, but don't forget the excellent AMD manuals. On the other hand, there is a lot of good information and documentation inside the MASM32 package. We have that due to the honest and diligent work of Hutch and the other volunteers - special thanks to all.

QuoteIf you want to use Kip's book, check this post about using his library in parallel to the Masm32 SDK.

Good hint, Jochen.

Gunther
You have to know the facts before you can distort them.

MichaelW

Quote from: laskar01 on July 11, 2012, 06:35:22 AM
I am finishing the BIOS chapter now, but neither BIOS is availible running MASM under XP, correct? All I have is a managed "BIOS"?

Under XP you have access to the BIOS functions through NTVDM. As to whether or not any of the function calls end up being handled by real-mode BIOS code I don't know, but at many/most of functions will behave as they would under DOS. A small number of the functions will always fail and return an error (for example the BIOS wait functions, Interrupt 15h, functions 83h and 86h), and any attempt by a DOS app to use the BIOS disk functions to access a hard disk will cause the system to terminate the app. And the BIOS will recognize devices that may not exist in hardware. For example, my Windows XP system has one serial port and one parallel port, as reported in the System Information app, but if use the DOS DEBUG program to dump the first 16 bytes of the BIOS data area I get:

-d 40:0
0040:0000  F8 03 F8 02 E8 03 E8 02-BC 03 78 03 78 02 C0 9F   ..........x.x...


Which shows that the BIOS POST found the full complement of 4 serial ports and 3 parallel ports. And IIRC I could access these "virtual" ports from a DOS app running under Windows, although obviously I could not attach anything to an external connector to do a function test.

Well Microsoft, here's another nice mess you've gotten us into.

Gunther

Hi Michael,

QuoteAnd IIRC I could access these "virtual" ports from a DOS app running under Windows, although obviously I could not attach anything to an external connector to do a function test.

That's interesting. It could be that this is a remainder for old hardware. For example: some old scanners are using the TWAIN interface. Should be tested.

Gunther
You have to know the facts before you can distort them.