AMSDOS - Revision history

Phi2x at 09:39, 13 October 2024

2024-10-13T09:39:40Z

@@ Line 9: / Line 9: @@
 * [[AMSDOS Hidden RSX Functions]]
 * [[AMSDOS Memory Map]]
 == AMSDOS command reference ==
@@ Line 48: / Line 50: @@
 You can choose another user with a POKE into AMSDOS variables. For example, '''poke &a701,&e5''' provides access to the deleted files or USER 229 (recycle bin). |Ren,"0:filename.typ","filename.typ" moves the deleted file filename.typ from USER 229 to USER 0. Another example, '''poke &a701,&a2''' provides access to USER 162.
 == CAS TEST EOF ==
@@ Line 53: / Line 78: @@
 * If the opened file doesn't have a header then hard EOF is signaled at the end of the current record (Each record is 128 bytes). e.g. if reading a file without a header which is meant to be 2 bytes long, hard eof will not be signalled until byte 128.
 * If the opened file does have a header then hard EOF is signaled at the end of the data defined by the header. (i.e. if there is a header and the file has length 2, hard EOF is signalled when reading the third byte).
 == BASDOS ==

Phi2x: /* AMSDOS command reference */

2024-10-13T09:33:59Z

AMSDOS command reference

← Older revision		Revision as of 09:33, 13 October 2024
Line 45:		Line 45:
	\|}		\|}

	Note: In fact, more user areas exist. Deleted files for example are in reality only moved to USER 229 (hexadecimal &E5)~~. You can choose another user with a POKE into AMSDOS variables~~.		Note: In fact, more user areas exist. Deleted files for example are in reality only moved to USER 229 (hexadecimal &E5).

	For example, '''poke &a701,&e5''' provides access to the deleted files or USER 229 (recycle bin). \|Ren,"0:filename.typ","filename.typ" moves the deleted file filename.typ from USER 229 to USER 0. Another example, poke &a701,&a2 provides access to USER 162.		You can choose another user with a POKE into AMSDOS variables. For example, '''poke &a701,&e5''' provides access to the deleted files or USER 229 (recycle bin). \|Ren,"0:filename.typ","filename.typ" moves the deleted file filename.typ from USER 229 to USER 0. Another example, '''poke &a701,&a2''' provides access to USER 162.

	== CAS TEST EOF ==		== CAS TEST EOF ==

Phi2x: /* AMSDOS command reference */

2024-09-30T10:40:44Z

AMSDOS command reference

← Older revision		Revision as of 10:40, 30 September 2024
Line 45:		Line 45:
	\|}		\|}

	Note: In fact, more user areas exist. Deleted files for example are in reality only moved to USER 229 (hexadecimal &E5). You can choose another user with a POKE into AMSDOS variables. For example '''poke &a701,&e5''' provides access to the deleted files or USER 229 (recycle bin). \|Ren,"0:filename.typ","filename.typ" moves the deleted file filename.typ from USER 229 to USER 0. Another example, poke &a701,&a2 provides access to USER 162.		Note: In fact, more user areas exist. Deleted files for example are in reality only moved to USER 229 (hexadecimal &E5). You can choose another user with a POKE into AMSDOS variables.

			For example, '''poke &a701,&e5''' provides access to the deleted files or USER 229 (recycle bin). \|Ren,"0:filename.typ","filename.typ" moves the deleted file filename.typ from USER 229 to USER 0. Another example, poke &a701,&a2 provides access to USER 162.

	== CAS TEST EOF ==		== CAS TEST EOF ==

Phi2x: /* AMSDOS command reference */

2024-09-30T10:36:44Z

AMSDOS command reference

@@ Line 12: / Line 12: @@
 == AMSDOS command reference ==
-=== |A ===
+{| class="wikitable"
-Makes drive A: the default disk drive. The result equals that of |DRIVE with parameter A. On a CPC664, CPC6128 or 6128plus, normally the built-in disk drive is A:.
+Note: In fact, more user areas exist. Deleted files for example are in reality only moved to USER 229 (hexadecimal &amp;E5). You can choose another user with a POKE into AMSDOS variables. For example '''poke &a701,&e5''' provides access to the deleted files or USER 229 (recycle bin). |Ren,"0:filename.typ","filename.typ" moves the deleted file filename.typ from USER 229 to USER 0. Another example, poke &a701,&a2 provides access to USER 162.
 == CAS TEST EOF ==

KSL at 13:54, 21 August 2024

2024-08-21T13:54:38Z

← Older revision		Revision as of 13:54, 21 August 2024
Line 96:		Line 96:
	moves the file EXAMPLE.BAS from USER 0 to USER 15 without changing its name.		moves the file EXAMPLE.BAS from USER 0 to USER 15 without changing its name.

	¹: In fact, more user areas exist. Deleted files for example are in reality only moved to USER 229 (hexadecimal &E5). You can choose another user with a POKE into AMSDOS variables. For example '''poke &a701,&e5''' provides access to the deleted files or ~~user~~ 229 (recycle bin). \|Ren,"0:filename.typ","filename.typ" moves the deleted file from ~~user~~ 229 to ~~user~~ 0.		¹: In fact, more user areas exist. Deleted files for example are in reality only moved to USER 229 (hexadecimal &E5). You can choose another user with a POKE into AMSDOS variables. For example '''poke &a701,&e5''' provides access to the deleted files or USER 229 (recycle bin). \|Ren,"0:filename.typ","filename.typ" moves the deleted file filename.typ from USER 229 to USER 0. Another example, poke &a701,&a2 provides access to USER 162.

	== CAS TEST EOF ==		== CAS TEST EOF ==

KSL at 13:51, 21 August 2024

2024-08-21T13:51:12Z

← Older revision		Revision as of 13:51, 21 August 2024
Line 96:		Line 96:
	moves the file EXAMPLE.BAS from USER 0 to USER 15 without changing its name.		moves the file EXAMPLE.BAS from USER 0 to USER 15 without changing its name.

	¹: In fact, more user areas exist. Deleted files for example are in reality only moved to USER 229 (hexadecimal &E5). You can choose another user with a POKE into AMSDOS variables.		¹: In fact, more user areas exist. Deleted files for example are in reality only moved to USER 229 (hexadecimal &E5). You can choose another user with a POKE into AMSDOS variables. For example '''poke &a701,&e5''' provides access to the deleted files or user 229 (recycle bin). \|Ren,"0:filename.typ","filename.typ" moves the deleted file from user 229 to user 0.

	== CAS TEST EOF ==		== CAS TEST EOF ==

Arnoldemu at 07:52, 1 May 2018

2018-05-01T07:52:25Z

← Older revision		Revision as of 07:52, 1 May 2018
Line 111:		Line 111:
	Differences compared to AMSDOS:		Differences compared to AMSDOS:
	* There is a new block of code at &dc00-&df00 in the ROM which starts with a small jumpblock. This code implements the patches. Other parts of the ROM have been patched to call into this.		* There is a new block of code at &dc00-&df00 in the ROM which starts with a small jumpblock. This code implements the patches. Other parts of the ROM have been patched to call into this.
	* Disc motor handler is patched to support a Ramdisk if ~~detected~~.		* Disc motor handler is patched to support a Ramdisk if selected.
	* Ramdisk is chosen with drive 'C' or 'D'. The XDPB is fixed and ~~can~~'t be auto detected. In addition data within the XDPB is used to identify Ramdisk 'formats'. 'Auto select' parameter is 1 for a ramdisk based format, which has a dual purpose of identifying it and preventing auto-detection and the filler byte has been repurposed to define the base ram page of the ramdisk. The ramdisk uses KC Compact RAM Expansion/Amstrad compatible RAM Expansions.		* Ramdisk is chosen with drive 'C' or 'D' using \|DRIVE only. The XDPB for the ramdisk is fixed and isn't auto detected. In addition data within the XDPB is used to identify Ramdisk 'formats'. 'Auto select' parameter is 1 for a ramdisk based format, which has a dual purpose of identifying it and preventing auto-detection and the filler byte has been repurposed to define the base ram page of the ramdisk. The ramdisk uses KC Compact RAM Expansion/Amstrad compatible RAM Expansions.
	* Read/write is patched to allow double sided discs so that BASDOS can be used.		* Read/write is patched to allow double sided discs so that BASDOS format can be used.
	* Drive 'A' or 'B' can be DATA, BASDOS format (704KB) or SYSTEM/VENDOR. IBM is replaced by BASDOS.		* Drive 'A' or 'B' can be DATA, BASDOS format (704KB) or SYSTEM/VENDOR. IBM format is replaced by BASDOS format.
	* Drive 'C' accesses a 64KB RAM DISK. (1KB blocks, 64 blocks, 32 directory entries). Uses second bank with ram selections from c4.		* Drive 'C' accesses a 64KB RAM DISK. (1KB blocks, 64 blocks, 32 directory entries). Uses second bank with ram selections from c4.
	* Drive 'D' accesses a 192KB RAM DISK. (2KB blocks, 96 blocks, 128 directory entries). Uses second bank with ram selections from e8. Useful if you have a 256KB/512KB ram expansion.		* Drive 'D' accesses a 192KB RAM DISK. (2KB blocks, 96 blocks, 128 directory entries). Uses second bank with ram selections from e8. Useful if you have a 256KB/512KB ram expansion.
	* the double sided [[MicroDOS]] disc format is only supported in Microdos and not in AMSDOS mode. There are no XDPB ~~which have sector size N=3~~ defined in the ROM.		* the double sided [[MicroDOS]] disc format is only supported in Microdos and not in AMSDOS mode. There are no XDPB defined for it within the BASDOS ROM.
	* can boot both [[MicroDOS]] and Amstrad CP/M ~~based~~ on the detected disc format. Read id is used to detect which is used. Both the sector ID and sector size are used. A ram expansion is required for MicroDOS.		* BASDOS can boot both [[MicroDOS]] and Amstrad CP/M using \|CPM depending on the detected disc format. Read id is used to detect which is used. Both the sector ID (R) and sector size (N) from the read id results are used. A ram expansion is required for MicroDOS.

			Both BASDOS and MicroDOS should be useable on a CPC.

	[[Category:Stub]] [[Category:Disc Operating_System]]		[[Category:Stub]] [[Category:Disc Operating_System]]

Arnoldemu: /* BASDOS */

2018-04-30T20:05:32Z

BASDOS

Arnoldemu: /* BASDOS */

2018-04-30T20:01:22Z

BASDOS

← Older revision		Revision as of 20:01, 30 April 2018
Line 109:		Line 109:
	Differences compared to AMSDOS:		Differences compared to AMSDOS:
	* There is a new block of code at &dc00-&df00 in the ROM which starts with a small jumpblock. This code implements the patches. Other parts of the ROM have been patched to call into this.		* There is a new block of code at &dc00-&df00 in the ROM which starts with a small jumpblock. This code implements the patches. Other parts of the ROM have been patched to call into this.
	* the double sided ~~[[MicroDOS]] disc~~ format is ~~supported in AMSDOS mode~~		* Disc motor handler is patched to support a Ramdisk. It uses data within the XDPB to determine if it's a disc based or ram based CPM based disc format. (auto select parameter is 1 for a ramdisk based format with the filler byte parameter defining the base ram page of the ramdisk).
	* the double sided ~~BASDOS~~ disc format is supported in AMSDOS mode.		* Read/write is patched to allow double sided discs.
	* ~~BASDOS~~ can boot both [[MicroDOS]] and Amstrad CP/M based on the detected disc format. Read id is used. Both the sector ID and sector size are used.		* Drive 'A' or 'B' can be DATA, BASDOS format (704KB) or SYSTEM/VENDOR. IBM is replaced by BASDOS.
			* Drive 'C' accesses a 64KB RAM DISK. (1KB blocks, 64 blocks, 32 directory entries). Uses second bank with ram selections from c4.
			* Drive 'D' accesses a 192KB RAM DISK. (2KB blocks, 96 blocks, 128 directory entries). Uses second bank with ram selections from e8. Useful if you have a 256KB/512KB ram expansion.
			* the double sided [[MicroDOS]] disc format is only supported in Microdos and not in AMSDOS mode.
			* can boot both [[MicroDOS]] and Amstrad CP/M based on the detected disc format. Read id is used to detect which is used. Both the sector ID and sector size are used.

	[[Category:Stub]] [[Category:Disc Operating_System]]		[[Category:Stub]] [[Category:Disc Operating_System]]

Arnoldemu: /* BASDOS */

2018-04-29T10:13:24Z

BASDOS

← Older revision		Revision as of 10:13, 29 April 2018
Line 109:		Line 109:
	Differences compared to AMSDOS:		Differences compared to AMSDOS:
	* There is a new block of code at &dc00-&df00 in the ROM which starts with a small jumpblock. This code implements the patches. Other parts of the ROM have been patched to call into this.		* There is a new block of code at &dc00-&df00 in the ROM which starts with a small jumpblock. This code implements the patches. Other parts of the ROM have been patched to call into this.
	* the double sided ~~Microdos~~ disc format is supported in AMSDOS mode		* the double sided [[MicroDOS]] disc format is supported in AMSDOS mode
	* BASDOS can boot both ~~Microdos~~ and Amstrad CP/M based on the detected disc format. Read id is used. Both the sector ID and sector size are used.		* the double sided BASDOS disc format is supported in AMSDOS mode.
			* BASDOS can boot both [[MicroDOS]] and Amstrad CP/M based on the detected disc format. Read id is used. Both the sector ID and sector size are used.

	[[Category:Stub]] [[Category:Disc Operating_System]]		[[Category:Stub]] [[Category:Disc Operating_System]]

← Older revision		Revision as of 20:05, 30 April 2018
Line 106:		Line 106:

	'''BASDOS''' (BASIC Disc Operating System) is a patched AMSDOS made in East Germany (GDR) for the [[KC Compact]].		'''BASDOS''' (BASIC Disc Operating System) is a patched AMSDOS made in East Germany (GDR) for the [[KC Compact]].

			The disc interface for the KC Compact contains the BASDOS rom, a NEC765 disc controller and 64KB RAM.

	Differences compared to AMSDOS:		Differences compared to AMSDOS:
	* There is a new block of code at &dc00-&df00 in the ROM which starts with a small jumpblock. This code implements the patches. Other parts of the ROM have been patched to call into this.		* There is a new block of code at &dc00-&df00 in the ROM which starts with a small jumpblock. This code implements the patches. Other parts of the ROM have been patched to call into this.
	* Disc motor handler is patched to support a Ramdisk. ~~It uses~~ data within the XDPB to ~~determine if it~~'~~s a disc based or ram based CPM based disc format~~. ~~(auto~~ select parameter is 1 for a ramdisk based format ~~with~~ the filler byte ~~parameter defining~~ the base ram page of the ramdisk).		* Disc motor handler is patched to support a Ramdisk if detected.
	* Read/write is patched to allow double sided discs.		* Ramdisk is chosen with drive 'C' or 'D'. The XDPB is fixed and can't be auto detected. In addition data within the XDPB is used to identify Ramdisk 'formats'. 'Auto select' parameter is 1 for a ramdisk based format, which has a dual purpose of identifying it and preventing auto-detection and the filler byte has been repurposed to define the base ram page of the ramdisk. The ramdisk uses KC Compact RAM Expansion/Amstrad compatible RAM Expansions.
			* Read/write is patched to allow double sided discs so that BASDOS can be used.
	* Drive 'A' or 'B' can be DATA, BASDOS format (704KB) or SYSTEM/VENDOR. IBM is replaced by BASDOS.		* Drive 'A' or 'B' can be DATA, BASDOS format (704KB) or SYSTEM/VENDOR. IBM is replaced by BASDOS.
	* Drive 'C' accesses a 64KB RAM DISK. (1KB blocks, 64 blocks, 32 directory entries). Uses second bank with ram selections from c4.		* Drive 'C' accesses a 64KB RAM DISK. (1KB blocks, 64 blocks, 32 directory entries). Uses second bank with ram selections from c4.
	* Drive 'D' accesses a 192KB RAM DISK. (2KB blocks, 96 blocks, 128 directory entries). Uses second bank with ram selections from e8. Useful if you have a 256KB/512KB ram expansion.		* Drive 'D' accesses a 192KB RAM DISK. (2KB blocks, 96 blocks, 128 directory entries). Uses second bank with ram selections from e8. Useful if you have a 256KB/512KB ram expansion.
	* the double sided [[MicroDOS]] disc format is only supported in Microdos and not in AMSDOS mode.		* the double sided [[MicroDOS]] disc format is only supported in Microdos and not in AMSDOS mode. There are no XDPB which have sector size N=3 defined in the ROM.
	* can boot both [[MicroDOS]] and Amstrad CP/M based on the detected disc format. Read id is used to detect which is used. Both the sector ID and sector size are used.		* can boot both [[MicroDOS]] and Amstrad CP/M based on the detected disc format. Read id is used to detect which is used. Both the sector ID and sector size are used. A ram expansion is required for MicroDOS.

	[[Category:Stub]] [[Category:Disc Operating_System]]		[[Category:Stub]] [[Category:Disc Operating_System]]