| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | 16 32 |
Udo van den Heuvel wrote in a message to All: UvdH> Why 'must' (?) devicedrivers be written in 16-bit and not in UvdH> 32-bit code? Some OS/2 device drivers are 16-bit, while others are 32-bit. It depends upon the type of driver. Most of the reason is historical, since OS/2 1.x was a 16-bit system. However, there are some advantages to having 16-bit physical device drivers, since most physical devices have 16-bit interfaces and you end up with smaller drivers. You can also use 32-bit 386 instructions inside your 16-bit driver if your compiler supports this; certainly your assembler does. -- Mike ---* Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) SEEN-BY: 50/99 78/0 270/101 620/243 711/401 409 410 413 430 808 809 934 955 SEEN-BY: 712/407 515 517 628 713/888 800/1 7877/2809 @PATH: 323/107 396/1 270/101 712/515 711/808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.