Desklink/TS-DOS Directory Access - Revision history

Jhoger: Reverted edits by 194.228.3.29 (Talk); changed back to last version by Jhoger

2011-07-09T04:11:36Z

Reverted edits by 194.228.3.29 (Talk); changed back to last version by Jhoger

Show changes

194.228.3.29: Undo revision 1873 by Jhoger (Talk)

2011-07-07T04:46:10Z

Undo revision 1873 by Jhoger (Talk)

Show changes

Jhoger: /* Change Directory requests from TS-DOS */

2009-10-21T19:05:56Z

Change Directory requests from TS-DOS

← Older revision		Revision as of 12:05, 21 October 2009
Line 177:		Line 177:
	\|}		\|}

	<br /> The server should respond to the CDRReq packet with a DRResp response packet containing the same directory name that was passed in the CDRReq. The server should save the directory name and expect to receive a subsequent Open File Request. When the Open File Request is received, the server should process it as a Change Directory operation to the directory specified in the CDRReq packet and return a standard Normal Response Packet (Id = 12H) with the appropriate error code. If the directory name matches the special name given for the parent directory ("PARENT.<>"), then the server should change to the parent of the current directory. The the server should then expect a Close File Request and respond as usual.<br />		<br /> The server should respond to the CDRReq packet with a DRResp response packet containing the same directory name that was passed in the CDRReq. The server should save the directory name and expect to receive a subsequent Open File For Reading Request. When the Open File Request is received, the server should process it as a Change Directory operation to the directory specified in the CDRReq packet and return a standard Normal Response Packet (Id = 12H) with the appropriate error code. If the directory name matches the special name given for the parent directory ("PARENT.<>"), then the server should change to the parent of the current directory. The the server should then expect a Close File Request and respond as usual.<br />

	=== Checksum Algorithm ===		== Make Directory ==

			The "Make Directory" request is similar to CDRReq. However, instead of opening the directory "file" for reading, the client will create a new file in Write mode.

			== Kill Directory ==

			TS-DOS Kill directory appears to the server as a Delete request for the picked directory "file." It is up to implementers to decide whether to permit deletion of non-empty directories.

			== Rename Directory ==

			TS-DOS "Name" (rename/move) request appears to the server as a Rename request for the picked directory "file."

			== Checksum Algorithm ==

	Total = Sum of all bytes from TypeID..Last byte of Payload<br /> Checksum = (Total & FFh) XOR FFh		Total = Sum of all bytes from TypeID..Last byte of Payload<br /> Checksum = (Total & FFh) XOR FFh

	[[Category:Model T Developer Reference]]		[[Category:Model T Developer Reference]]

Jhoger: /* Directory reporting from Server */

2009-10-21T19:00:16Z

Directory reporting from Server

← Older revision		Revision as of 12:00, 21 October 2009
Line 84:		Line 84:
	Directory Reference Requests (Request ID $00) are part of the standard TPDD-1 and TPDD-2 protocol. They are used for enumerating directory contents. During enumeration, the client can request "pick," "get-first," "get-next," and "get-previous" search forms to reference, initialize, move forward and backward (respectively) through the current directory.		Directory Reference Requests (Request ID $00) are part of the standard TPDD-1 and TPDD-2 protocol. They are used for enumerating directory contents. During enumeration, the client can request "pick," "get-first," "get-next," and "get-previous" search forms to reference, initialize, move forward and backward (respectively) through the current directory.

	~~Once the~~ TPDD server ~~device~~ (DeskLink, NADSBox, etc.) infers client support for DME by receipt of DMEReq. Directory and subdirectory names are then provided during enumeration along with filenames for the remainder of the session. If the DMEReq sequence is not received, then the server is communicating with a DOS that does not support DME (TEENY, FLOPPY, POWR-DOS, WP-2, etc.).		The TPDD server implementing DME (DeskLink, NADSBox, etc.) infers client support for DME by receipt of DMEReq. Directory and subdirectory names are then provided during enumeration along with filenames for the remainder of the session. If the DMEReq sequence is not received, then the server is communicating with a DOS that does not support DME (TEENY, FLOPPY, POWR-DOS, WP-2, etc.).

	Once enabled, directory names are reported using the same protocol as files using the Directory Reference Request except that the extension is reported as "<>".		Once enabled, directory names are reported using the same protocol as files using the Directory Reference Request except that the extension is reported as "<>".
Line 113:		Line 113:
	\|}		\|}

	<br /> When DME support has been established, the server reports directory information by responding to the DRReq sequence with a Directory Reference Response (DRResp) packet with the filename field containing the directory name in 6.2 filename format. The directory name should be 6 characters or less with space padding and the 2 character extension must be set to "<>". TS-DOS uses the "<>" extension to identify the entry as a directory. When the server is reporting file / directory entries for a directory other than the root, it should provide a mechanism for navigating to the parent directory. While DeskLink only provides navigation to the "ROOT.<>" directory, NADSBox allows navigation to the parent by reporting the first entry of a subdirectory as "PARENT.<>". The number of Free Sectors on the media should be a single byte with the value 80H or less. Sectors in the TPDD protocol are 1280 bytes in length.<br />		<br /> When DME support has been established, the server reports directory information by responding to the DRReq sequence with a Directory Reference Response (DRResp) packet with the filename field containing the directory name in 6.2 filename format. The directory name should be 6 characters or less with space padding and the 2 character extension must be set to "<>". TS-DOS uses the "<>" extension to identify the entry as a directory. When the server is reporting file and directory entries for a directory other than the root, it should provide a mechanism for navigating to the parent directory. While DeskLink only provides navigation to the "ROOT.<>" directory, NADSBox, for example, allows navigation to the parent by reporting the first entry of a subdirectory as "PARENT.<>". The number of Free Sectors on the media should be a single byte with the value 80H or less. Sectors in the TPDD protocol are 1280 bytes in length.<br />

	=== Directory Reference Response (DRResp) ===		=== Directory Reference Response (DRResp) ===

Jhoger at 18:56, 21 October 2009

2009-10-21T18:56:15Z

← Older revision		Revision as of 11:56, 21 October 2009
Line 54:		Line 54:

	<br /> For a TPDD service that supports FDC Emulation mode, the standard response for both commands is no response. If the server does not respond to either command, or responds with an error message, then TS-DOS knows the server does not support DME.<br /><br /> If the server does support DME, then after the final carriage return (0Dh), it shall reply with a standard operational mode response. The response ID must be 12h and the payload field must be 11 bytes long and contain the name of the current directory, or at least the lowest level name in the tree, as shown below. The name should be 6 characters long and should be terminated with ".<>",20h. Names shorter than 6 characters should be padded with spaces before the ".<>",20h extension.<br /><br /> TS-DOS will display the directory name reported in the DMEResp payload in the upper right corner of the display in reverse video characters. If the current directory is the root "/" directory, then the server should return "ROOT .<> " in the payload field as a standard, although any name could be provided. TS-DOS will send the DMEReq sequence multiple times including when it has requested a directory change operation. This provides a way of reporting the new subdirectory name for display in the TS-DOS title bar.		<br /> For a TPDD service that supports FDC Emulation mode, the standard response for both commands is no response. If the server does not respond to either command, or responds with an error message, then TS-DOS knows the server does not support DME.<br /><br /> If the server does support DME, then after the final carriage return (0Dh), it shall reply with a standard operational mode response. The response ID must be 12h and the payload field must be 11 bytes long and contain the name of the current directory, or at least the lowest level name in the tree, as shown below. The name should be 6 characters long and should be terminated with ".<>",20h. Names shorter than 6 characters should be padded with spaces before the ".<>",20h extension.<br /><br /> TS-DOS will display the directory name reported in the DMEResp payload in the upper right corner of the display in reverse video characters. If the current directory is the root "/" directory, then the server should return "ROOT .<> " in the payload field as a standard, although any name could be provided. TS-DOS will send the DMEReq sequence multiple times including when it has requested a directory change operation. This provides a way of reporting the new subdirectory name for display in the TS-DOS title bar.

			If you are writing a TPDD service, and you wish to implement DME but not FDC mode, you can simply ignore the FDC mode change command and newline. Instead, just respond to the ZZ$08 file-access style command as described in DMEResp.

	=== Directory Management Extensions Response (DMEResp) ===		=== Directory Management Extensions Response (DMEResp) ===

99.6.119.22: /* Directory reporting from Server */

2009-10-19T08:54:02Z

Directory reporting from Server

← Older revision		Revision as of 01:54, 19 October 2009
Line 80:		Line 80:
	== Directory reporting from Server ==		== Directory reporting from Server ==

	Directory Reference Requests (Request ID $00) are part of the standard TPDD-1 and TPDD-2 protocol. They are used for enumerating directory contents. During enumeration, the client can request "get-first," "get-next," and "get-previous" search forms to initialize, move forward and backward (respectively) through the current directory.		Directory Reference Requests (Request ID $00) are part of the standard TPDD-1 and TPDD-2 protocol. They are used for enumerating directory contents. During enumeration, the client can request "pick," "get-first," "get-next," and "get-previous" search forms to reference, initialize, move forward and backward (respectively) through the current directory.

	Once the TPDD server device (DeskLink, NADSBox, etc.) infers client support for DME by receipt of DMEReq. Directory and subdirectory names are then provided during enumeration along with filenames for the remainder of the session. If the DMEReq sequence is not received, then the server is communicating with a DOS that does not support DME (TEENY, FLOPPY, POWR-DOS, WP-2, etc.).		Once the TPDD server device (DeskLink, NADSBox, etc.) infers client support for DME by receipt of DMEReq. Directory and subdirectory names are then provided during enumeration along with filenames for the remainder of the session. If the DMEReq sequence is not received, then the server is communicating with a DOS that does not support DME (TEENY, FLOPPY, POWR-DOS, WP-2, etc.).

99.6.119.22: /* Directory reporting from Server */

2009-10-19T08:48:05Z

Directory reporting from Server

← Older revision		Revision as of 01:48, 19 October 2009
Line 82:		Line 82:
	Directory Reference Requests (Request ID $00) are part of the standard TPDD-1 and TPDD-2 protocol. They are used for enumerating directory contents. During enumeration, the client can request "get-first," "get-next," and "get-previous" search forms to initialize, move forward and backward (respectively) through the current directory.		Directory Reference Requests (Request ID $00) are part of the standard TPDD-1 and TPDD-2 protocol. They are used for enumerating directory contents. During enumeration, the client can request "get-first," "get-next," and "get-previous" search forms to initialize, move forward and backward (respectively) through the current directory.

	Once the TPDD server device (~~LaddieCon,~~ DeskLink, NADSBox, etc.) infers client support for DME by receipt of DMEReq. Directory and subdirectory names are then provided during enumeration along with filenames for the remainder of the session. If the DMEReq sequence is not received, then the server is communicating with a DOS that does not support DME (TEENY, FLOPPY, POWR-DOS, WP-2, etc.).		Once the TPDD server device (DeskLink, NADSBox, etc.) infers client support for DME by receipt of DMEReq. Directory and subdirectory names are then provided during enumeration along with filenames for the remainder of the session. If the DMEReq sequence is not received, then the server is communicating with a DOS that does not support DME (TEENY, FLOPPY, POWR-DOS, WP-2, etc.).

	Once enabled, directory names are reported using the same protocol as files using the Directory Reference Request except that the extension is reported as "<>".		Once enabled, directory names are reported using the same protocol as files using the Directory Reference Request except that the extension is reported as "<>".

99.6.119.22: /* Directory reporting from Server */

2009-10-19T08:47:48Z

Directory reporting from Server

← Older revision		Revision as of 01:47, 19 October 2009
Line 82:		Line 82:
	Directory Reference Requests (Request ID $00) are part of the standard TPDD-1 and TPDD-2 protocol. They are used for enumerating directory contents. During enumeration, the client can request "get-first," "get-next," and "get-previous" search forms to initialize, move forward and backward (respectively) through the current directory.		Directory Reference Requests (Request ID $00) are part of the standard TPDD-1 and TPDD-2 protocol. They are used for enumerating directory contents. During enumeration, the client can request "get-first," "get-next," and "get-previous" search forms to initialize, move forward and backward (respectively) through the current directory.

	Once the TPDD server device (DeskLink, NADSBox, etc.) infers client support for DME by receipt of DMEReq. Directory and subdirectory names are then provided during enumeration along with filenames for the remainder of the session. If the DMEReq sequence is not received, then the server is communicating with a DOS that does not support DME (TEENY, FLOPPY, POWR-DOS, WP-2, etc.).		Once the TPDD server device (LaddieCon, DeskLink, NADSBox, etc.) infers client support for DME by receipt of DMEReq. Directory and subdirectory names are then provided during enumeration along with filenames for the remainder of the session. If the DMEReq sequence is not received, then the server is communicating with a DOS that does not support DME (TEENY, FLOPPY, POWR-DOS, WP-2, etc.).

	Once enabled, directory names are reported using the same protocol as files using the Directory Reference Request except that the extension is reported as "<>".		Once enabled, directory names are reported using the same protocol as files using the Directory Reference Request except that the extension is reported as "<>".

99.6.119.22: /* Change Directory requests from TS-DOS */

2009-10-19T06:24:49Z

Change Directory requests from TS-DOS

← Older revision		Revision as of 23:24, 18 October 2009
Line 144:		Line 144:
	== Change Directory requests from TS-DOS ==		== Change Directory requests from TS-DOS ==

	When the user navigates the cursor to a directory entry that has the "<>" extension and pressed Enter, TS-DOS will perform a Directory Change operation to naviagte to that directory. This is accomplished by sending a Change ~~Direcotry~~ Reference Request (CDRReq) followed by a standard Open File Request and then a Close File Request. The CDRReq packet is the same as a standard DRReq packet except the filename extension is set to "<>".		When the user navigates the cursor to a directory entry that has the "<>" extension and pressed Enter, TS-DOS will perform a Directory Change operation to naviagte to that directory. This is accomplished by sending a Change Directory Reference Request (CDRReq) followed by a standard Open File Request and then a Close File Request. The CDRReq packet is the same as a standard DRReq packet except the filename extension is set to "<>".

	=== Change Directory Reference Request (CDRReq) ===		=== Change Directory Reference Request (CDRReq) ===

99.6.119.22: /* Directory reporting from Server */

2009-10-19T05:49:41Z

Directory reporting from Server

← Older revision		Revision as of 22:49, 18 October 2009
Line 80:		Line 80:
	== Directory reporting from Server ==		== Directory reporting from Server ==

	Directory Reference Requests (Request ID $00) are part of the standard TPDD-1 and TPDD-2 protocol. They are used for enumerating directory contents. During enumeration, the client can request a "get-first," "get-next," and "get-previous" search forms.		Directory Reference Requests (Request ID $00) are part of the standard TPDD-1 and TPDD-2 protocol. They are used for enumerating directory contents. During enumeration, the client can request "get-first," "get-next," and "get-previous" search forms to initialize, move forward and backward (respectively) through the current directory.

	Once the TPDD server device (DeskLink, NADSBox, etc.) infers client support for DME by receipt of DMEReq. Directory and subdirectory names are then provided during enumeration along with filenames for the remainder of the session. If the DMEReq sequence is not received, then the server is communicating with a DOS that does not support DME (TEENY, FLOPPY, POWR-DOS, WP-2, etc.).		Once the TPDD server device (DeskLink, NADSBox, etc.) infers client support for DME by receipt of DMEReq. Directory and subdirectory names are then provided during enumeration along with filenames for the remainder of the session. If the DMEReq sequence is not received, then the server is communicating with a DOS that does not support DME (TEENY, FLOPPY, POWR-DOS, WP-2, etc.).