Jump to content

New pages

New pages
Hide registered users | Hide bots | Hide redirects
(newest | oldest) View ( | ) (20 | 50 | 100 | 250 | 500)

4 May 2026

3 May 2026

  • 22:2922:29, 3 May 2026 DosSetKBDSigFocus (hist | edit) [519 bytes] Martini (talk | contribs) (Created page with "The DosSetKBDSigFocus() function is used to allow 32-bit programs to inform the operating system that they are "primed for signals", although the signals are dispatched as exceptions. Note the following: * 16-bit DosSetVec() exceptions are supported under OS/2 Version 2.0. * The 32-bit OS/2 Version 2.0 exception manager allows per-thread exception handling. * OS/2 Version 2.0 does not allow an exception handler to be registered for the numeric processor exception (NPX)....")
  • 19:0219:02, 3 May 2026 STATUS (hist | edit) [1,231 bytes] Martini (talk | contribs) (Created page with "The STATUS command obtains status information for the device. ==Syntax== <pre> STATUS ─── object ───┬─ MODE ─┬───┬──────────┬───┤ └─ READY ─┘ ├─ WAIT ─┤ └─ NOTIFY ─┘ </pre> ==Keywords== ;object :Object associated with this media control interface command. The object can be one of the following: :*Device type :*Device name :*...")
  • 19:0119:01, 3 May 2026 OPEN (hist | edit) [2,718 bytes] Martini (talk | contribs) (Created page with "The OPEN command is used to open or create a new device instance. OPEN returns a device ID that is used for subsequent calls for the procedure interface, if desired. ==Syntax== <pre> ┌──────────────────────────┐ │ │ OPEN ──── object ─┴──┬────────────────────┬──┴──┬─────...")
  • 19:0019:00, 3 May 2026 INFO (hist | edit) [1,078 bytes] Martini (talk | contribs) (Created page with "The INFO command fills a user-supplied buffer with information. ==Syntax== <pre> INFO ──── object ───── PRODUCT ────┬──────────┬────┤ ├─ WAIT ─┤ └─ NOTIFY ─┘ </pre> ==Keywords== ;object :Object associated with this media control interface command. The object can be one of the following: :*Device type :*Device name :*Filen...")
  • 19:0019:00, 3 May 2026 CLOSE (hist | edit) [890 bytes] Martini (talk | contribs) (Created page with "The CLOSE command closes the device context and frees resources. ==Syntax== <pre> CLOSE ──── object ────┬──────────┬────┤ ├─ WAIT ─┤ └─ NOTIFY ─┘ </pre> ==Keywords== ;object :Object associated with this media control interface command. The object can be one of the following: :*Device type :*Device name :*Filename :*Alias ;WAIT :The command is executed syn...")
  • 18:5918:59, 3 May 2026 CAPABILITY (hist | edit) [3,599 bytes] Martini (talk | contribs) (Created page with "== CAPABILITY == The CAPABILITY command requests information about a particular capability of a device. ==Syntax== <pre> CAPABILITY ─── object ───┬─ CAN EJECT ────────┬───┬──────────┬───┤ ├─ CAN PLAY ─────────┤ ├─ WAIT ─┤ ├─ CAN RECORD ───────┤ └─ NOTIFY ─┘...")
  • 18:2318:23, 3 May 2026 MMProgRef - Return Codes (hist | edit) [25,575 bytes] Martini (talk | contribs) (Created page with "This section lists the following categories of OS/2 multimedia return codes including number, message, and a brief description: * Media Device Manager Return Codes * Sync Stream Manager Return Codes * MMIO Manager Return Codes * DIVE Return Codes == Media Device Manager Return Codes == 5000 - MCIERR_SUCCESS MMPM/2 command completed success...")
  • 18:1918:19, 3 May 2026 MMProgRef - RIFF Compound Files and Elements - Sharing and Access (hist | edit) [5,151 bytes] Martini (talk | contribs) (Created page with "{{MMProgRef}} The following tables show the relationship between sharing and accessing RIFF compound files (CF) and elements within those files, both within the current process and between processes. === Access and Sharing Modes === An '''A''' indicates that the function is allowed. Both the access and sharing values must be '''A''' for the open to work. For example, in the CF Open - CF Open of the same process, if the first CF Open is RO - DW, then the next CF Open m...")
  • 06:2306:23, 3 May 2026 MMAPG - Installing a Program Using MINSTALL (hist | edit) [27,831 bytes] Martini (talk | contribs) (Created page with "This section describes the procedures for preparing control files for installing a multimedia application using the multimedia installation program (MINSTALL). The MINSTALL program utilizes features provided by the OS/2 multimedia installation engine, such as creating workplace shell objects and changing the CONFIG.SYS file, providing a consistent installation process. '''Note:''' For installation requirements when writing a subsystem, refer to the ''OS/2 Multimedia...")
  • 05:5605:56, 3 May 2026 MMAPG - Sample Application Programs (hist | edit) [64,910 bytes] Martini (talk | contribs) (Created page with "{{MMAPG}} {{IBM-Reprint}} This section gives a brief overview of the sample application programs provided with the Toolkit, including programming concepts and program flow diagrams for each of the sample programs. The purpose of the OS/2 multimedia sample programs is to illustrate multimedia programming concepts and establish a basis for creating your own multimedia applications. The programs provide you with practical examples that span a range of multimedia concepts...")
  • 05:4805:48, 3 May 2026 MMAPG - Resource Interchange File Format (RIFF) Services (hist | edit) [26,094 bytes] Martini (talk | contribs) (Created page with "{{MMAPG}} {{IBM-Reprint}} The Resource Interchange File Format (RIFF) is the standard file format used for storing multimedia files. RIFF enables audio, image, animation, and other multimedia elements to be stored in a common format. RIFF is also used as the basis for defining new file formats for OS/2 multimedia software. RIFF file I/O provides simple functions to locate, create, enter, exit, and access the ''chunk''—the basic building block of a RIFF file. You can...")
  • 05:2705:27, 3 May 2026 MMAPG - Multimedia I/O File Services (hist | edit) [50,997 bytes] Martini (talk | contribs) (Created page with "{{MMAPG}} {{IBM-Reprint}} The multimedia input/output (MMIO) file services are an extension of the base OS/2 file services. Designed to be simple, fast, and flexible, MMIO functions enable an application to access and manipulate multimedia data files in a transparent manner. Multimedia files contain a variety of media elements such as images, graphics, digital audio and video. These elements can be in different file formats: for example, RIFF, M-Motion, and AVI. Multim...")
(newest | oldest) View ( | ) (20 | 50 | 100 | 250 | 500)
Retrieved from "https://www.edm2.com/index.php/Special:NewPages"