NSC800 Conversion - Revision history

Sadolph: /* TPDD Utilities for CP/M mode */

2024-12-26T14:15:59Z

TPDD Utilities for CP/M mode

← Older revision		Revision as of 07:15, 26 December 2024
Line 202:		Line 202:

	Transfer these programs using IMP80 (and change .COM to .CO for transfer) into CP/M.		Transfer these programs using IMP80 (and change .COM to .CO for transfer) into CP/M.

			Note:
			-----
			TPDD servers usually only support 6.2 filenames.
			John has a version of LaddieAlpha that supports 8.3 filenames, which is ideal for CP/M use.
			The end result is that by using this version of LaddieAlpha, and my TD/TS/TL/TK utilities,
			you can work directly with 8.3 files.
			Contact John directly for a LaddieAlpha that works with 8.3 filenames.

	=== How do I get M100 CP/M loaded up? ===		=== How do I get M100 CP/M loaded up? ===

Sadolph: /* Notes on use with M100 CP/M */

2024-12-26T14:10:58Z

Notes on use with M100 CP/M

← Older revision		Revision as of 07:10, 26 December 2024
Line 147:		Line 147:
	5. IMPORT and EXPORT are not written using 8080 opcodes, so you will need replacements. See below.		5. IMPORT and EXPORT are not written using 8080 opcodes, so you will need replacements. See below.
	6. If you want to use the BCR Hack for external video over MVT100, you need to (1) change the hack slightly and (2) patch CP/M. See below.		6. If you want to use the BCR Hack for external video over MVT100, you need to (1) change the hack slightly and (2) patch CP/M. See below.
	7. Also note - the utilities for backup/restore of REXCPM also do not work on NSC800.		7. Also note - the utilities for backup/restore of REXCPM also do not work on NSC800... now resolved! RXCUTN below.

Sadolph: /* Is there a quick way to bootstrap my CP/M system from scratch? */

2024-12-26T14:04:00Z

Is there a quick way to bootstrap my CP/M system from scratch?

← Older revision		Revision as of 07:04, 26 December 2024
Line 425:		Line 425:
	\|'''Software'''\|\|'''Version'''\|\|'''Note'''\|\|'''File'''		\|'''Software'''\|\|'''Version'''\|\|'''Note'''\|\|'''File'''
	\|-		\|-
	\|NSC800 disk image\|\| ~~N/A~~ \|\| as of December 2024 \|\|[[Media:NSC800_disk.ZIP\|NSC800_disk.ZIP]]		\|NSC800 disk image\|\| 2MB image \|\| as of December 2024 \|\|[[Media:NSC800_disk.ZIP\|NSC800_disk.ZIP]]
	\|-		\|-
	\|}		\|}

Sadolph: /* Setting up your system for 76800 baud */

2024-12-26T14:03:26Z

Setting up your system for 76800 baud

← Older revision		Revision as of 07:03, 26 December 2024
Line 387:		Line 387:
	https://sourceforge.net/p/bacnet/discussion/402140/thread/f2eeb911/		https://sourceforge.net/p/bacnet/discussion/402140/thread/f2eeb911/

	For Windows, you edit the registry to provide an alternative dividsor value, to enable 76800.		For Windows, you edit the registry to provide an alternative dividsor value, to enable 76800.

	Here's the good part for Windows:		Here's the good part for Windows:

Sadolph: /* Setting up your system for 76800 baud */

2024-12-26T14:03:05Z

Setting up your system for 76800 baud

Sadolph at 14:02, 26 December 2024

2024-12-26T14:02:41Z

← Older revision		Revision as of 07:02, 26 December 2024
Line 366:		Line 366:
	If you see an error message - "CAN'T RUN", this means that REXCPM is not in the default state.		If you see an error message - "CAN'T RUN", this means that REXCPM is not in the default state.
	See instruction #1 above!		See instruction #1 above!



			=== Setting up your system for 76800 baud ===

			To run backup/restore at 76800 baud, you need a couple of things.

			1) a serial port capable of 76800 baud
			2) a TPDD server that is able to run at 76800 baud


			Regarding serial port, what I use is a USB serial port based on the FTDI chip.

			An example of an FTDI based USB serial port is here:
			https://www.startech.com/en-ca/cards-adapters/icusb2321f

			However, 76800 is not a standard baud. So, you generally have to make some changes to your host machine and the change is different depending on the operating system.

			This article provides a good summary:
			https://sourceforge.net/p/bacnet/discussion/402140/thread/f2eeb911/

			For Windows, you edit the registry to provide an alternative dividsor value, to enable 76800.

			Here's the good part for Windows:
			Windows XP
			1) Plug in and locate your USB/RSS85 in Device Manager under ports. Right
			click on it and select Properties. Click Details tab and from the drop down
			select Device Instance Id.

			2) Click Start, Run and then type regedit.

			Follow this path in the registry

			HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\FTDIBUS

			Locate the folder that has the same name as what you found earlier Device
			Instance Id in step 1. Click on 0000 folder and then Device Parameters. On the
			right side you will see ConfigData. Right click and select Modify Binary Data.

			Locate the 10 27 which in my case were in 5th and 6th position and replace
			with 27 C0.

			This will make the RS485 go to 76800 baud (76923 baud) baud when you ask it to
			be 300 baud.

			So to capture at 76800 baud type: mstpcap.exe COM2 300


			With regards to a TPDD server, I use a version of LaddieAlpha which John has modified to allow serial port parameters to be set.

			I suggest contacting John with regards to getting an up-to-date LaddieAlpha that supports baud rate settings.

Sadolph: /* Is there a quick way to bootstrap my CP/M system from scratch? */

2024-12-25T22:01:36Z

Is there a quick way to bootstrap my CP/M system from scratch?

← Older revision		Revision as of 15:01, 25 December 2024
Line 376:		Line 376:


	~~just~~ for kicks, here is my current NSC800 CP/M disk image.		Just for kicks, here is my current NSC800 CP/M disk image.
			Contains Turbo Pascal, MBASIC, maybe BDS-C, my TPDD utilities, etc.

Sadolph: /* Is there a quick way to bootstrap my CP/M system from scratch? */

2024-12-25T21:58:29Z

Is there a quick way to bootstrap my CP/M system from scratch?

← Older revision		Revision as of 14:58, 25 December 2024
Line 372:		Line 372:

	Why yes there is.		Why yes there is.
	Use ~~RXCTUN~~ to "restore" a working CP/M image directly into your REXCPM.		Use RXCUTN to "restore" a working CP/M image directly into your REXCPM.
	Then, load and run CPM.DO to allow you to start CP/M.		Then, load and run CPM.DO to allow you to start CP/M.

Sadolph: /* How do I back up my CP/M Disk? */

2024-12-25T21:58:09Z

How do I back up my CP/M Disk?

← Older revision		Revision as of 14:58, 25 December 2024
Line 366:		Line 366:
	If you see an error message - "CAN'T RUN", this means that REXCPM is not in the default state.		If you see an error message - "CAN'T RUN", this means that REXCPM is not in the default state.
	See instruction #1 above!		See instruction #1 above!



			=== Is there a quick way to bootstrap my CP/M system from scratch? ===

			Why yes there is.
			Use RXCTUN to "restore" a working CP/M image directly into your REXCPM.
			Then, load and run CPM.DO to allow you to start CP/M.


			just for kicks, here is my current NSC800 CP/M disk image.


			{\| class="wikitable"
			\|'''Software'''\|\|'''Version'''\|\|'''Note'''\|\|'''File'''
			\|-
			\|NSC800 disk image\|\| N/A \|\| as of December 2024 \|\|[[Media:NSC800_disk.ZIP\|NSC800_disk.ZIP]]
			\|-
			\|}

Sadolph: /* How do I back up my CP/M Disk? */

2024-12-25T19:27:10Z

How do I back up my CP/M Disk?

← Older revision		Revision as of 12:27, 25 December 2024
Line 299:		Line 299:
	\|'''Software'''\|\|'''Version'''\|\|'''Note'''\|\|'''File'''		\|'''Software'''\|\|'''Version'''\|\|'''Note'''\|\|'''File'''
	\|-		\|-
	\|RXCUTN\|\| 3 \|\| initial release December 2024 \|\|[[Media:RXCUTN.ZIP\|RXCUTN.ZIP]] \|\|		\|RXCUTN\|\| 3 \|\| initial release December 2024 \|\|[[Media:RXCUTN.ZIP\|RXCUTN.ZIP]]
	\|-		\|-
	\|}		\|}

← Older revision		Revision as of 07:03, 26 December 2024
Line 394:		Line 394:
	click on it and select Properties. Click Details tab and from the drop down		click on it and select Properties. Click Details tab and from the drop down
	select Device Instance Id.		select Device Instance Id.

	2) Click Start, Run and then type regedit.		2) Click Start, Run and then type regedit.

	Follow this path in the registry		Follow this path in the registry

	HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\FTDIBUS		HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\FTDIBUS

	Locate the folder that has the same name as what you found earlier Device		Locate the folder that has the same name as what you found earlier Device
	Instance Id in step 1. Click on 0000 folder and then Device Parameters. On the		Instance Id in step 1. Click on 0000 folder and then Device Parameters. On the
	right side you will see ConfigData. Right click and select Modify Binary Data.		right side you will see ConfigData. Right click and select Modify Binary Data.

	Locate the 10 27 which in my case were in 5th and 6th position and replace		Locate the 10 27 which in my case were in 5th and 6th position and replace
	with 27 C0.		with 27 C0.

	This will make the RS485 go to 76800 baud (76923 baud) baud when you ask it to		This will make the RS485 go to 76800 baud (76923 baud) baud when you ask it to
	be 300 baud.		be 300 baud.

	So to capture at 76800 baud type: mstpcap.exe COM2 300		So to capture at 76800 baud type: mstpcap.exe COM2 300

Line 417:		Line 410:

	I suggest contacting John with regards to getting an up-to-date LaddieAlpha that supports baud rate settings.		I suggest contacting John with regards to getting an up-to-date LaddieAlpha that supports baud rate settings.



	=== Is there a quick way to bootstrap my CP/M system from scratch? ===		=== Is there a quick way to bootstrap my CP/M system from scratch? ===