AmigaDOS Device Input and Output - Revision history

Steven Solie at 18:47, 2 October 2015

2015-10-02T18:47:27Z

Steven Solie at 21:33, 22 April 2014

2014-04-22T21:33:04Z

← Older revision		Revision as of 21:33, 22 April 2014
Line 193:		Line 193:
	to use the packet interface directly for this instead of using the		to use the packet interface directly for this instead of using the
	function interface. For more information on packets, see [[AmigaDOS_Packets\|AmigaDOS Packets]].		function interface. For more information on packets, see [[AmigaDOS_Packets\|AmigaDOS Packets]].

			= Creating a New Device to Run Under AmigaDOS =

			This section provides information about adding devices that are NOT part
			of the DOS filing system like the console and port handlers. The next
			section provides information about adding filesystem-related devices (hard
			disks, floppy disks) - that is, devices that DOS can use to read and write
			files with their associated directories.

			You would want to use this information to add a new device such as a new
			serial port or a new parallel port. In this case you may be creating a
			device named "SER2:" which is to act just like "SER:" as far as DOS is
			concerned.

			There are two steps involved here. First, you must create a suitable
			device, a process that is not addressed here.

			Second, you must make this new device available as an AmigaDOS device.
			This process involves writing a suitable device handler and installing it
			into the AmigaDOS structures. You install a new device and its handler
			under AmigaDOS with the MOUNT command. You need to put the device in the
			DEVS: directory, the handler in the L: directory, and add an entry for the
			device in DEVS:mountlist.

			The device handler is the interface between your device and an
			application program. The AmigaDOS kernel will attempt to load the code of
			the handler and create a new process for it when it is first referenced.
			This is handled automatically when the kernel notices that the Task field
			in the DevInfo structure is zero. If the code is already loaded, the code
			segment pointer is placed in the SegList field. If this field is zero, the
			kernel loads the code from the filename given in the filename field and
			updates the SegList field.

			= Making New Disk Devices =

			To create a new disk device, you must construct a new device node as
			described in [[AmigaDOS Data Structures#Info_Substructure\|Info Substructure]] in [[AmigaDOS_Data_Structures\|AmigaDOS Data Structures]]. You must
			also write a device driver for the new disk device.

			A device driver for a new disk device must mimic the calls that are
			performed by the trackdisk.device. It must include the ability to respond
			to commands such as Read(), Write(), Seek(), and return status information
			in the same way as described for the trackdisk driver.

Steven Solie: /* NEWCON: */

2014-02-28T19:40:23Z

NEWCON:

← Older revision		Revision as of 19:40, 28 February 2014
Line 115:		Line 115:
	not automatically echoed in the RAW: window.		not automatically echoed in the RAW: window.

	== NEWCON: ==		== NEWCON: (Obsolete) ==

	(Obsolete) This handler was included only in V1.3 of the		(Obsolete) This handler was included only in V1.3 of the Amiga operating system as an alternative to the original CON: handler. The original CON: handler had no line editing functions but these have been incorporated into CON: in V2.0 and later versions of AmigaDOS.
	Amiga operating system as an alternative to the original
	CON: handler. The original CON: handler had no line editing
	functions but these have been incorporated into CON: in
	V2.0 and later versions of AmigaDOS.

	== SER: ==		== SER: ==

Steven Solie: /* CON: */

2014-02-28T19:39:33Z

CON:

@@ Line 47: / Line 47: @@
 == CON: ==
-Instead of using a new window for the output, you can send it to the
+Instead of using a new window for the output, you can send it to the currently selected window by using * instead of
 CON:x/y/width/height/title.
 {| class="wikitable"
@@ Line 87: / Line 73: @@
 |}
-The additional CON: keywords BACKDROP, NODRAG, NOBORDER, NOSIZE, SIMPLE,
+The additional CON: keywords BACKDROP, NODRAG, NOBORDER, NOSIZE, SIMPLE and SMART control the same window attributes as their similarly named Intuition window flags.
 {| class="wikitable"
@@ Line 120: / Line 97: @@
 |}
-Note that with the CON: and RAW: handlers, if the SMART flag is used in
+Note that with the CON: and RAW: handlers, if the SMART flag is used in the window specification then only text paste operations are supported. Text cut operations do not work with the SMART flag.
 == RAW: ==

Alexandre Balaban: Categorizing

2012-05-11T13:23:26Z

Categorizing

← Older revision		Revision as of 13:23, 11 May 2012
Line 1:		Line 1:
	{{WIP}}		[[Category:DOS\|Device]]{{WIP}}
	= Introduction =		= Introduction =

Steven Solie at 16:11, 2 May 2012

2012-05-02T16:11:00Z

← Older revision		Revision as of 16:11, 2 May 2012
Line 1:		Line 1:
			{{WIP}}
	= Introduction =		= Introduction =

Steven Solie at 19:06, 27 April 2012

2012-04-27T19:06:51Z

← Older revision		Revision as of 19:06, 27 April 2012
Line 233:		Line 233:
	though, is the ability to easily perform asynchronous I/O, so you may want		though, is the ability to easily perform asynchronous I/O, so you may want
	to use the packet interface directly for this instead of using the		to use the packet interface directly for this instead of using the
	function interface. For more information on packets, see ~~the~~ ~~section~~		function interface. For more information on packets, see [[AmigaDOS_Packets\|AmigaDOS Packets]].
	entitled "AmigaDOS Packets" in @{"Chapter 11" link Ele}.

Steven Solie at 16:26, 27 April 2012

2012-04-27T16:26:58Z

← Older revision		Revision as of 16:26, 27 April 2012
Line 1:		Line 1:
			= Introduction =

	AmigaDOS uses handlers and filesystems to provide a standard method of		AmigaDOS uses handlers and filesystems to provide a standard method of
	interaction with physical I/O devices. Handlers and filesystems are		interaction with physical I/O devices. Handlers and filesystems are

Steven Solie at 15:16, 27 April 2012

2012-04-27T15:16:27Z

← Older revision		Revision as of 15:16, 27 April 2012
Line 209:		Line 209:
	stream), a0 and a1 (toggled direct phoneme mode), and d0		stream), a0 and a1 (toggled direct phoneme mode), and d0
	and d1 (enables sentence pause on LF or CR).		and d1 (enables sentence pause on LF or CR).

			= Communicating with AmigaDOS Devices =

			The usual method of communicating with handlers and filesystems is through
			the AmigaDOS file I/O functions such as Open(), Read() and Write(). A
			lower level method is through the DOS packet interface, the basic
			communication method between different processes. Built on top of the Exec
			message passing system, the packet interface provides a standard means of
			interprocess communication.

			This communication may take place either synchronously or asynchronously
			(usually through a routine called DoPkt(), which does the work of finding
			the task address, sending the message via PutMsg(), and Wait()ing on the
			reserved DOS packet signal). The DOS library calls that talk to handlers -
			Read(), Write(), Open() - use the packet interface.

			The dos.library translates these calls into packets, sends them to the
			appropriate handler process, and returns the results to the calling
			routine. There is very little extra overhead associated with using the
			library calls over using the packet interface directly. What is lost,
			though, is the ability to easily perform asynchronous I/O, so you may want
			to use the packet interface directly for this instead of using the
			function interface. For more information on packets, see the section
			entitled "AmigaDOS Packets" in @{"Chapter 11" link Ele}.

Steven Solie: /* CON: */

2012-04-27T15:15:28Z

CON:

← Older revision		Revision as of 15:15, 27 April 2012
Line 116:		Line 116:
	\| Moves the cursor to the end of the line (shift cursor right also does this).		\| Moves the cursor to the end of the line (shift cursor right also does this).
	\|}		\|}

			In addition to the line editing features, some text copy and paste
			features have also been added to the console handler in V2.0. The user can
			drag-select a text block in a console window with the mouse and then copy
			the selected text to an internal buffer with Right-Amiga-C. (Extended
			drag-select is also supported with the Shift keys.) The text may then be
			pasted into another console window with Right-Amiga-V. Pasted text is
			inserted into the read stream as if the text had been typed manually.

			A special utility called ConClip (part of the standard Startup-sequence
			in V2.0) provides clipboard support for copy and paste operations. When
			ConClip is running, console text copied with Right-Amiga-C is placed in
			the clipboard.device; console paste operations with Right-Amiga-V cause a
			special code (<CSI>0 v) to be inserted into the read stream instead of the
			text. The CON: handler reads from the clipboard when this code is received
			so applications that use CON: get clipboard support automatically.
			Applications that use the RAW: handler (see blow) must provide their own
			support for clipboard reads.

			Note that with the CON: and RAW: handlers, if the SMART flag is used in
			the window specification then only text paste operations are supported.
			Text cut operations do not work with the SMART flag.

			== RAW: ==

			Provides unbuffered screen and keyboard I/O and allows
			definition of a new window for the output just like CON:.
			(In fact, RAW: and CON: are implemented as a single handler
			with two names and corresponding modes of operation.) With
			RAW:, key presses are unbuffered and can be read by an
			application immediately. The keyboard I/O is unfiltered
			allowing processing of all key combinations. Keystrokes are
			not automatically echoed in the RAW: window.

			== NEWCON: ==

			(Obsolete) This handler was included only in V1.3 of the
			Amiga operating system as an alternative to the original
			CON: handler. The original CON: handler had no line editing
			functions but these have been incorporated into CON: in
			V2.0 and later versions of AmigaDOS.

			== SER: ==

			The SER: handler provides a stream-oriented interface to
			the serial port (a stream-oriented interface allows you to
			treat the physical device as a file).

			== PAR: ==

			The PAR: handler provides a stream-oriented interface to
			the parallel port (a stream-oriented interface allows you
			to treat the physical device as a file).

			== PRT: ==

			The PRT: handler provides a stream-oriented interface to
			the printer and also accepts standard printer codes,
			translating them into the command sequence used for the
			currently selected printer driver.

			== NIL: ==

			The NIL: handler provides a convenient place to send
			command output that you are not interested in. For
			instance, MOUNT >NIL: AUX: mount[s] the AUX: device without
			printing any diagnostic messages on the screen. Note that
			the NIL: handler is really a fake handler maintained within
			AmigaDOS. It is not a separate process.

			== PIPE: ==

			The PIPE: handler is a mechanism meant to provide
			convenient buffered I/O communication between programs.
			When the PIPE: is written to, up to 4K of data are buffered
			before the writing process is blocked. After one process
			writes to PIPE: any other can read from it. This is useful,
			for instance, when you're using two application programs
			and want to transfer a large amount of data from one
			(write) to the other (read) without creating a temporary
			file in RAM: or on disk.

			== SPEAK: ==

			The SPEAK: handler provides speech output for the Amiga.
			With SPEAK: you can have the Amiga literally read the
			contents of a file out load. For instance, COPY
			DEVS:mountlist SPEAK:OPT/f/s160 will say the contents of
			the mountlist in a female voice at a moderate speed. SPEAK:
			accepts all the options of the SAY command and also o0 and
			o1 (enables or disables processing of options in the input
			stream), a0 and a1 (toggled direct phoneme mode), and d0
			and d1 (enables sentence pause on LF or CR).