User talk:CVS - Revision history

TArntsen: (missing indent)

2021-07-09T07:23:24Z

(missing indent)

← Older revision		Revision as of 07:23, 9 July 2021
Line 30:		Line 30:
	I tested the version uploaded 02-07-2021, and it works great. I'm curious about mon204/205 which are needed for the symbolic debugger, these are undocumented everywhere as far as I can tell - was it tricky to figure out what they do? [[User:TArntsen\|TArntsen]] ([[User talk:TArntsen\|talk]])		I tested the version uploaded 02-07-2021, and it works great. I'm curious about mon204/205 which are needed for the symbolic debugger, these are undocumented everywhere as far as I can tell - was it tricky to figure out what they do? [[User:TArntsen\|TArntsen]] ([[User talk:TArntsen\|talk]])
	:You will find the SINTRAN code for MON 204/205 in SINTRAN III VSX part 2 listing which I believe I got from you (PDF). Search for 3DEBUG. Without this listing it would be very difficult for me to fugure out how the NSD is implemented. I can make a detailed description later. SINTRAN is using segment switching to run the user program/debugger at the same terminal. My emulator works somewhat different; it starts the symbolic debugger in one terminal window and the program to debug in another terminal window. The two emulator instances communicate using SIGUSR1 and SIGUSR2 and a shared memory area. When starting NSD it runs as a 1-bank program using a background segment as any other program. When doing the place command MON 205 is called. The monitor call then reads (RFILE) the PROG-file to a debug segment. The number of debug segments is a SINTRAN configuration parameter. LOOK-AT is calling MON 205 which then use the alternative page table bit to read data from the debug segment. Writing data is using the same functionality. When setting a break point in the program the debugger first reads the instruction which is found at the BP address and then writes MON 204 into this address. When issuing the RUN command MON 205 is called and SINTRAN switches segment to run the user program. When the BP is reached SINTRAN will start NSD (switching segments) at a call-back address given as far as I remember when doing run/MON 205. If you type debug 205 before you start NSD and do the same in the same in the window that appears after doing PLACE the emulator will output information that may give you some more clues about the funtions in MON 205-		:You will find the SINTRAN code for MON 204/205 in SINTRAN III VSX part 2 listing which I believe I got from you (PDF). Search for 3DEBUG. Without this listing it would be very difficult for me to fugure out how the NSD is implemented. I can make a detailed description later. SINTRAN is using segment switching to run the user program/debugger at the same terminal. My emulator works somewhat different; it starts the symbolic debugger in one terminal window and the program to debug in another terminal window. The two emulator instances communicate using SIGUSR1 and SIGUSR2 and a shared memory area. When starting NSD it runs as a 1-bank program using a background segment as any other program. When doing the place command MON 205 is called. The monitor call then reads (RFILE) the PROG-file to a debug segment. The number of debug segments is a SINTRAN configuration parameter. LOOK-AT is calling MON 205 which then use the alternative page table bit to read data from the debug segment. Writing data is using the same functionality. When setting a break point in the program the debugger first reads the instruction which is found at the BP address and then writes MON 204 into this address. When issuing the RUN command MON 205 is called and SINTRAN switches segment to run the user program. When the BP is reached SINTRAN will start NSD (switching segments) at a call-back address given as far as I remember when doing run/MON 205. If you type debug 205 before you start NSD and do the same in the same in the window that appears after doing PLACE the emulator will output information that may give you some more clues about the funtions in MON 205-
	:Thanks! That may have been the OCR'ed listing from Gandalf, from the J version. My L version listing is a bit different and reduced in that area, but I found some info there still. [[User:TArntsen\|TArntsen]] ([[User talk:TArntsen\|talk]]) 13:00, 8 July 2021 (UTC)		::Thanks! That may have been the OCR'ed listing from Gandalf, from the J version. My L version listing is a bit different and reduced in that area, but I found some info there still. [[User:TArntsen\|TArntsen]] ([[User talk:TArntsen\|talk]]) 13:00, 8 July 2021 (UTC)

TArntsen: Listing mon 204/205

2021-07-08T13:00:38Z

Listing mon 204/205

← Older revision		Revision as of 13:00, 8 July 2021
Line 30:		Line 30:
	I tested the version uploaded 02-07-2021, and it works great. I'm curious about mon204/205 which are needed for the symbolic debugger, these are undocumented everywhere as far as I can tell - was it tricky to figure out what they do? [[User:TArntsen\|TArntsen]] ([[User talk:TArntsen\|talk]])		I tested the version uploaded 02-07-2021, and it works great. I'm curious about mon204/205 which are needed for the symbolic debugger, these are undocumented everywhere as far as I can tell - was it tricky to figure out what they do? [[User:TArntsen\|TArntsen]] ([[User talk:TArntsen\|talk]])
	:You will find the SINTRAN code for MON 204/205 in SINTRAN III VSX part 2 listing which I believe I got from you (PDF). Search for 3DEBUG. Without this listing it would be very difficult for me to fugure out how the NSD is implemented. I can make a detailed description later. SINTRAN is using segment switching to run the user program/debugger at the same terminal. My emulator works somewhat different; it starts the symbolic debugger in one terminal window and the program to debug in another terminal window. The two emulator instances communicate using SIGUSR1 and SIGUSR2 and a shared memory area. When starting NSD it runs as a 1-bank program using a background segment as any other program. When doing the place command MON 205 is called. The monitor call then reads (RFILE) the PROG-file to a debug segment. The number of debug segments is a SINTRAN configuration parameter. LOOK-AT is calling MON 205 which then use the alternative page table bit to read data from the debug segment. Writing data is using the same functionality. When setting a break point in the program the debugger first reads the instruction which is found at the BP address and then writes MON 204 into this address. When issuing the RUN command MON 205 is called and SINTRAN switches segment to run the user program. When the BP is reached SINTRAN will start NSD (switching segments) at a call-back address given as far as I remember when doing run/MON 205. If you type debug 205 before you start NSD and do the same in the same in the window that appears after doing PLACE the emulator will output information that may give you some more clues about the funtions in MON 205-		:You will find the SINTRAN code for MON 204/205 in SINTRAN III VSX part 2 listing which I believe I got from you (PDF). Search for 3DEBUG. Without this listing it would be very difficult for me to fugure out how the NSD is implemented. I can make a detailed description later. SINTRAN is using segment switching to run the user program/debugger at the same terminal. My emulator works somewhat different; it starts the symbolic debugger in one terminal window and the program to debug in another terminal window. The two emulator instances communicate using SIGUSR1 and SIGUSR2 and a shared memory area. When starting NSD it runs as a 1-bank program using a background segment as any other program. When doing the place command MON 205 is called. The monitor call then reads (RFILE) the PROG-file to a debug segment. The number of debug segments is a SINTRAN configuration parameter. LOOK-AT is calling MON 205 which then use the alternative page table bit to read data from the debug segment. Writing data is using the same functionality. When setting a break point in the program the debugger first reads the instruction which is found at the BP address and then writes MON 204 into this address. When issuing the RUN command MON 205 is called and SINTRAN switches segment to run the user program. When the BP is reached SINTRAN will start NSD (switching segments) at a call-back address given as far as I remember when doing run/MON 205. If you type debug 205 before you start NSD and do the same in the same in the window that appears after doing PLACE the emulator will output information that may give you some more clues about the funtions in MON 205-
			:Thanks! That may have been the OCR'ed listing from Gandalf, from the J version. My L version listing is a bit different and reduced in that area, but I found some info there still. [[User:TArntsen\|TArntsen]] ([[User talk:TArntsen\|talk]]) 13:00, 8 July 2021 (UTC)

CVS at 21:00, 7 July 2021

2021-07-07T21:00:19Z

← Older revision		Revision as of 21:00, 7 July 2021
Line 29:		Line 29:

	I tested the version uploaded 02-07-2021, and it works great. I'm curious about mon204/205 which are needed for the symbolic debugger, these are undocumented everywhere as far as I can tell - was it tricky to figure out what they do? [[User:TArntsen\|TArntsen]] ([[User talk:TArntsen\|talk]])		I tested the version uploaded 02-07-2021, and it works great. I'm curious about mon204/205 which are needed for the symbolic debugger, these are undocumented everywhere as far as I can tell - was it tricky to figure out what they do? [[User:TArntsen\|TArntsen]] ([[User talk:TArntsen\|talk]])
	:You will find the SINTRAN code for MON 204/205 in SINTRAN III VSX part 2 listing which I believe I got from you (PDF). Search for 3DEBUG. Without this listing it would be very difficult for me to fugure out how the NSD is implemented. I can make a detailed description later. SINTRAN is using segment switching to run the user program/debugger at the same terminal. My emulator works somewhat different; it starts the symbolic debugger in one terminal window and the program to debug in another terminal window. The two emulator instances communicate using SIGUSR1 and SIGUSR2 and a shared memory area. When starting NSD it runs as a 1-bank program using a background segment as any other program. When doing the place command MON 205 is called. The monitor call then reads (RFILE) the PROG-file to a debug segment. The number of debug segments is a SINTRAN configuration parameter. LOOK-AT is calling MON 205 which then use the alternative page table bit to read data from the debug segment. Writing data is using the same functionality. When setting a break point in the program the debugger first reads the instruction which is found at the BP address and then writes MON 204 into this address. When issuing the RUN command MON 205 is called and SINTRAN switches segment to run the user program. When the BP is reached SINTRAN will start NSD (switching segments) at a call-back address given as far as I remember when doing run/MON 205.		:You will find the SINTRAN code for MON 204/205 in SINTRAN III VSX part 2 listing which I believe I got from you (PDF). Search for 3DEBUG. Without this listing it would be very difficult for me to fugure out how the NSD is implemented. I can make a detailed description later. SINTRAN is using segment switching to run the user program/debugger at the same terminal. My emulator works somewhat different; it starts the symbolic debugger in one terminal window and the program to debug in another terminal window. The two emulator instances communicate using SIGUSR1 and SIGUSR2 and a shared memory area. When starting NSD it runs as a 1-bank program using a background segment as any other program. When doing the place command MON 205 is called. The monitor call then reads (RFILE) the PROG-file to a debug segment. The number of debug segments is a SINTRAN configuration parameter. LOOK-AT is calling MON 205 which then use the alternative page table bit to read data from the debug segment. Writing data is using the same functionality. When setting a break point in the program the debugger first reads the instruction which is found at the BP address and then writes MON 204 into this address. When issuing the RUN command MON 205 is called and SINTRAN switches segment to run the user program. When the BP is reached SINTRAN will start NSD (switching segments) at a call-back address given as far as I remember when doing run/MON 205. If you type debug 205 before you start NSD and do the same in the same in the window that appears after doing PLACE the emulator will output information that may give you some more clues about the funtions in MON 205-

CVS at 19:16, 7 July 2021

2021-07-07T19:16:21Z

← Older revision		Revision as of 19:16, 7 July 2021
Line 29:		Line 29:

	I tested the version uploaded 02-07-2021, and it works great. I'm curious about mon204/205 which are needed for the symbolic debugger, these are undocumented everywhere as far as I can tell - was it tricky to figure out what they do? [[User:TArntsen\|TArntsen]] ([[User talk:TArntsen\|talk]])		I tested the version uploaded 02-07-2021, and it works great. I'm curious about mon204/205 which are needed for the symbolic debugger, these are undocumented everywhere as far as I can tell - was it tricky to figure out what they do? [[User:TArntsen\|TArntsen]] ([[User talk:TArntsen\|talk]])
			:You will find the SINTRAN code for MON 204/205 in SINTRAN III VSX part 2 listing which I believe I got from you (PDF). Search for 3DEBUG. Without this listing it would be very difficult for me to fugure out how the NSD is implemented. I can make a detailed description later. SINTRAN is using segment switching to run the user program/debugger at the same terminal. My emulator works somewhat different; it starts the symbolic debugger in one terminal window and the program to debug in another terminal window. The two emulator instances communicate using SIGUSR1 and SIGUSR2 and a shared memory area. When starting NSD it runs as a 1-bank program using a background segment as any other program. When doing the place command MON 205 is called. The monitor call then reads (RFILE) the PROG-file to a debug segment. The number of debug segments is a SINTRAN configuration parameter. LOOK-AT is calling MON 205 which then use the alternative page table bit to read data from the debug segment. Writing data is using the same functionality. When setting a break point in the program the debugger first reads the instruction which is found at the BP address and then writes MON 204 into this address. When issuing the RUN command MON 205 is called and SINTRAN switches segment to run the user program. When the BP is reached SINTRAN will start NSD (switching segments) at a call-back address given as far as I remember when doing run/MON 205.

TArntsen: (typo)

2021-07-05T09:23:11Z

(typo)

← Older revision		Revision as of 09:23, 5 July 2021
Line 28:		Line 28:
	::I am now CAVISU at GitHub (https://github.com/CAVISU and you should be able to report bugs.		::I am now CAVISU at GitHub (https://github.com/CAVISU and you should be able to report bugs.

	I tested the version uploaded 02-07-2021, and it works great. I'm ~~curios~~ about mon204/205 which are needed for the symbolic debugger, these are undocumented everywhere as far as I can tell - was it tricky to figure out what they do? [[User:TArntsen\|TArntsen]] ([[User talk:TArntsen\|talk]])		I tested the version uploaded 02-07-2021, and it works great. I'm curious about mon204/205 which are needed for the symbolic debugger, these are undocumented everywhere as far as I can tell - was it tricky to figure out what they do? [[User:TArntsen\|TArntsen]] ([[User talk:TArntsen\|talk]])

TArntsen: Tested new version V-7.7

2021-07-05T09:22:34Z

Tested new version V-7.7

← Older revision		Revision as of 09:22, 5 July 2021
Line 27:		Line 27:
	:I did a quick test of the emulator today, using Wine (4.0) in Debian 9.9 and xterm. As Tor, I can report that it works, and with DDTABLES support for terminal type 6, PED runs as well. Nice. Do you have a code repository (github / gitlab or something) where we can report bugs? [[User:Tingo\|Torfinn]] ([[User talk:Tingo\|talk]]) 13:24, 27 May 2019 (UTC)		:I did a quick test of the emulator today, using Wine (4.0) in Debian 9.9 and xterm. As Tor, I can report that it works, and with DDTABLES support for terminal type 6, PED runs as well. Nice. Do you have a code repository (github / gitlab or something) where we can report bugs? [[User:Tingo\|Torfinn]] ([[User talk:Tingo\|talk]]) 13:24, 27 May 2019 (UTC)
	::I am now CAVISU at GitHub (https://github.com/CAVISU and you should be able to report bugs.		::I am now CAVISU at GitHub (https://github.com/CAVISU and you should be able to report bugs.

			I tested the version uploaded 02-07-2021, and it works great. I'm curios about mon204/205 which are needed for the symbolic debugger, these are undocumented everywhere as far as I can tell - was it tricky to figure out what they do? [[User:TArntsen\|TArntsen]] ([[User talk:TArntsen\|talk]])

Tingo: /* Welcome */ tested the Linux version of the ND emulator

2019-06-21T13:07:51Z

Welcome: tested the Linux version of the ND emulator

← Older revision		Revision as of 13:07, 21 June 2019
Line 4:		Line 4:
	:I have generated a Linux version (beta) http://www.ndwiki.org/images/6/68/NDsim.tar.gz		:I have generated a Linux version (beta) http://www.ndwiki.org/images/6/68/NDsim.tar.gz
	::Thanks! I did a quick test. PED updates the screen quite a bit faster than when running the Windows version through Wine. Looks good! [[User:TArntsen\|TArntsen]] ([[User talk:TArntsen\|talk]]) 08:20, 9 June 2019 (UTC)		::Thanks! I did a quick test. PED updates the screen quite a bit faster than when running the Windows version through Wine. Looks good! [[User:TArntsen\|TArntsen]] ([[User talk:TArntsen\|talk]]) 08:20, 9 June 2019 (UTC)
			::I even managed to compile a small FORTRAN program with the FTN compiler with the Linux version (it would probably work in the other version too, I haven't tried it), now I just need to remember / re-learn all the other steps. [[User:Tingo\|Torfinn]] ([[User talk:Tingo\|talk]]) 13:07, 21 June 2019 (UTC)

	Yeah, welcome to the wiki. Great to have more people join us. [[User:Roger\|Roger]] ([[User talk:Roger\|talk]]) 18:09, 13 May 2019 (UTC)		Yeah, welcome to the wiki. Great to have more people join us. [[User:Roger\|Roger]] ([[User talk:Roger\|talk]]) 18:09, 13 May 2019 (UTC)

TArntsen: Quick test of Linux version

2019-06-09T08:20:44Z

Quick test of Linux version

← Older revision		Revision as of 08:20, 9 June 2019
Line 3:		Line 3:
	Welcome, from another user. It is great to have another contributor here. And personally, I'm very interested to see a working ND emulator, especially if it works under Linux and unix like operating systems. [[User:Tingo\|Torfinn]] ([[User talk:Tingo\|talk]]) 09:26, 13 May 2019 (UTC)		Welcome, from another user. It is great to have another contributor here. And personally, I'm very interested to see a working ND emulator, especially if it works under Linux and unix like operating systems. [[User:Tingo\|Torfinn]] ([[User talk:Tingo\|talk]]) 09:26, 13 May 2019 (UTC)
	:I have generated a Linux version (beta) http://www.ndwiki.org/images/6/68/NDsim.tar.gz		:I have generated a Linux version (beta) http://www.ndwiki.org/images/6/68/NDsim.tar.gz
			::Thanks! I did a quick test. PED updates the screen quite a bit faster than when running the Windows version through Wine. Looks good! [[User:TArntsen\|TArntsen]] ([[User talk:TArntsen\|talk]]) 08:20, 9 June 2019 (UTC)

	Yeah, welcome to the wiki. Great to have more people join us. [[User:Roger\|Roger]] ([[User talk:Roger\|talk]]) 18:09, 13 May 2019 (UTC)		Yeah, welcome to the wiki. Great to have more people join us. [[User:Roger\|Roger]] ([[User talk:Roger\|talk]]) 18:09, 13 May 2019 (UTC)

CVS at 17:23, 8 June 2019

2019-06-08T17:23:51Z

← Older revision		Revision as of 17:23, 8 June 2019
Line 2:		Line 2:

	Welcome, from another user. It is great to have another contributor here. And personally, I'm very interested to see a working ND emulator, especially if it works under Linux and unix like operating systems. [[User:Tingo\|Torfinn]] ([[User talk:Tingo\|talk]]) 09:26, 13 May 2019 (UTC)		Welcome, from another user. It is great to have another contributor here. And personally, I'm very interested to see a working ND emulator, especially if it works under Linux and unix like operating systems. [[User:Tingo\|Torfinn]] ([[User talk:Tingo\|talk]]) 09:26, 13 May 2019 (UTC)
			:I have generated a Linux version (beta) http://www.ndwiki.org/images/6/68/NDsim.tar.gz

	Yeah, welcome to the wiki. Great to have more people join us. [[User:Roger\|Roger]] ([[User talk:Roger\|talk]]) 18:09, 13 May 2019 (UTC)		Yeah, welcome to the wiki. Great to have more people join us. [[User:Roger\|Roger]] ([[User talk:Roger\|talk]]) 18:09, 13 May 2019 (UTC)

CVS at 16:47, 27 May 2019

2019-05-27T16:47:53Z

← Older revision		Revision as of 16:47, 27 May 2019
Line 23:		Line 23:

	:I did a quick test of the emulator today, using Wine (4.0) in Debian 9.9 and xterm. As Tor, I can report that it works, and with DDTABLES support for terminal type 6, PED runs as well. Nice. Do you have a code repository (github / gitlab or something) where we can report bugs? [[User:Tingo\|Torfinn]] ([[User talk:Tingo\|talk]]) 13:24, 27 May 2019 (UTC)		:I did a quick test of the emulator today, using Wine (4.0) in Debian 9.9 and xterm. As Tor, I can report that it works, and with DDTABLES support for terminal type 6, PED runs as well. Nice. Do you have a code repository (github / gitlab or something) where we can report bugs? [[User:Tingo\|Torfinn]] ([[User talk:Tingo\|talk]]) 13:24, 27 May 2019 (UTC)
			::I am now CAVISU at GitHub (https://github.com/CAVISU and you should be able to report bugs.