Usage of mmio* function set of MMOS/2

From EDM2
Jump to: navigation, search

by Prokushev

I/O Procedures

I/O Procedures (IOProc in short) are set of DLLs which provides MMOS/2 access to format/file data. IOProc handles all I/O tasks:

  1. Storage access (Storage IOProc)
  2. Format handling (Format IOProc)

Storage IOProc is lowest level of IOProc hierarhy.

Format IOProc actually transforms corresponding file format to common MMOS/2 format and vice versa.

Actually, IOProcs can call each other. For example, PNG IOProc uses CF IOProc to read PNG data from compound file. CF IOProc uses HTTP IO Proc to read compound file from HTTP stream. And HTTP IOProc uses TCP IOProc to read HTTP stream via TCP protocol. So, to read PNG data byte-stream comes via four I/O procedures.



Exist special type of IO Procedures named "codec". Codec procedure can COde (compress/encrypt/etc.) and/or DECode (uncompress/decrypt/etc.) byte-stream. To continue above example lets add codec to chain:

              Z Codec

In this example PNG IO Procedure reads PNG data and moves corresponding data array to Z codec which decompress data and returns to PNG IOProc.

Logic of above solutions is easy: reuse code. Different IOProcs can use common codecs and read byte-stream from different places.


From user (application level) point of view no difference which file you loading. Is it GIF, PNG, JPEG, BMP or something other. It is work of IOProc subsystem of MMPM/2 to handle corresponding format. So, user has two tasks:

  1. Read image
  2. Store image

Reading image

Image reading is easy thing. Let's try to read image, create bitmap and display it.

Storing image

Now let's try reverse method: storing. Lets create image from resource, get data from bitmap and store data.

Creating new procedure

I/O Procedure templates