OS2DD303 - OS/2 Adapter Device Driver (ADD)

From OS2World.Com Wiki
Revision as of 00:07, 21 February 2016 by Tomh (talk | contribs) (Created page with "Course OS2DD303 -Adapter Device Drivers (ADD) OS/2 Device Drivers for SCSI or Proprietary Interfaces '''Objective''' This five day workshop will enable programmers to wri...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Course OS2DD303 -Adapter Device Drivers (ADD) OS/2 Device Drivers for SCSI or Proprietary Interfaces

Objective

This five day workshop will enable programmers to write OS/2 Adapter device drivers (ADD). An ADD communicates with SCSI or proprietary I/O interfaces which usually connect to DASD, CD-ROM, etc.

This class will identify the protocol on how the ADD communicates with the Device Manager (DMD) using the IORB interface. Installation and debug techniques will also be covered. The Developer Connection Device Driver Kit (Devcon-DDK) will be used extensively in order to build and test the ADD.

Target audience

IBM or OEM programmers who code device drivers for PC I/O interfaces such as SCSI or proprietary.

Attendee prerequisites

o Programming expertise: C (MASM useful)

o Have written device drivers for DASD I/O hardware (DOS device drivers, ROM BIOS, test utilities)

o Attendee must be a licensee of the following software:

 - OS/2 2.x, OS/2 Warp 
 - Developer Connection Device Driver Kit (Devcon-DDK), MSC 6.0 
 - Knowledge of OS/2 Physical Device Driver (recommend attendance at OS2DD101 workshop) 

Outline

o OS/2 Structure o Device Driver types o Driver Stack under OS/2

 - Adapter Device Driver (ADD) 
 - Filter ADD (FLT), Device Manager (DMD) 

o CONFIG.SYS

 - Installation (BASEDEV= ) 
 - Boot sequence 

o ADD Development considerations

 - Command line parameters 
 - Error handling 

o IORB - Format, Control o Device Table Structure o TESTCFG.SYS

 - IOctl functions, parameters 

o CDROM filter ADD example

 - Sample Code layout 

o Device Driver Profiles o Impact: SCSI versus proprietary interfaces o Lab: Adapter device driver development