From priyachinc at gmail.com Thu Jan 2 08:02:51 2014 From: priyachinc at gmail.com (Priya Chincholikar) Date: Thu, 2 Jan 2014 18:32:51 +0530 Subject: [Simh] Fwd: Red Hat VM version In-Reply-To: References: Message-ID: ---------- Forwarded message ---------- From: Priya Chincholikar Date: Thu, Jan 2, 2014 at 12:31 PM Subject: Red Hat VM version To: Mark Pizzolato - Info Comm Hi Mark, I am not a paid user of Red Hat either, I have a Red Hat VM partitioned along with windows on my system. The libpcap package was downloaded and installed manually by me. My aim is to run SIMH on this host and use the .vmdk on other systems. Attached file should help. Thanks, Priya -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: VM Player.png Type: image/png Size: 95000 bytes Desc: not available URL: From captainkirk359 at gmail.com Wed Jan 8 15:10:05 2014 From: captainkirk359 at gmail.com (Christian Gauger-Cosgrove) Date: Wed, 8 Jan 2014 15:10:05 -0500 Subject: [Simh] Possible TIME and DATE Environment Variable Improvements Message-ID: I don't do much simulator scripting, but I have found one slight inconvenience with regards to the %DATE% and %TIME% variables. I'm trying to setup my simulator command file to attach a text file to the simulators LPT that is dated and timed, so I don't accidentally wipe out previous LPT listings (or make them grow to very large sizes). As they are at present, the %DATE% and %TIME% (and the %CTIME%, but that can be left alone) variable are really not suited for direct use as a part of creating a file name. Would it be possible to reformat the %DATE% variable to be ISO 8601 compliant? That is, change the forward slashes to hyphens. Secondly, would it be possible to make the %TIME% variable either return the time without the colons? (ISO 8601 "basic" format, as opposed to the current ISO 8601 "extended" format.) Alternatively, if there is some way to "massage" a the text strings reported by %DATE% and %TIME% to be something usable for a filename in the simulator command language I would not mind that either. As to what I'm trying to do: ATTACH LPT listing_%DATE%_%TIME%.txt Though, as mentioned previously, the current return strings for %DATE% and %TIME% will make -- at least Windows -- complain. Thank you, Christian -- Christian M. Gauger-Cosgrove STCKON08DS0 Contact information available upon request. From Mark at infocomm.com Wed Jan 8 15:55:49 2014 From: Mark at infocomm.com (Mark Pizzolato - Info Comm) Date: Wed, 8 Jan 2014 12:55:49 -0800 Subject: [Simh] Possible TIME and DATE Environment Variable Improvements In-Reply-To: References: Message-ID: <0CC6789C1C831B4C8CCFF49D45D7010F0127D58D3327@REDROOF2.alohasunset.com> On Wednesday, January 08, 2014 at 12:10 PM, Christian Gauger-Cosgrove wrote: > I don't do much simulator scripting, but I have found one slight > inconvenience with regards to the %DATE% and %TIME% variables. > > I'm trying to setup my simulator command file to attach a text file to the > simulators LPT that is dated and timed, so I don't accidentally wipe out > previous LPT listings (or make them grow to very large sizes). As they are at > present, the %DATE% and %TIME% (and the %CTIME%, but that can be left > alone) variable are really not suited for direct use as a part of creating a file > name. > > Would it be possible to reformat the %DATE% variable to be ISO 8601 > compliant? That is, change the forward slashes to hyphens. Done. > Secondly, would it be possible to make the %TIME% variable either return > the time without the colons? (ISO 8601 "basic" format, as opposed to the > current ISO 8601 "extended" format.) There now is a %STIME% which returns the time as hh_mm_ss. > Alternatively, if there is some way to "massage" a the text strings reported > by %DATE% and %TIME% to be something usable for a filename in the > simulator command language I would not mind that either. > > > As to what I'm trying to do: > ATTACH LPT listing_%DATE%_%TIME%.txt > Though, as mentioned previously, the current return strings for %DATE% and > %TIME% will make -- at least Windows -- complain. > > Thank you, > Christian That should work now. The Windows binaries will be updated in a couple of minutes. - Mark From captainkirk359 at gmail.com Wed Jan 8 22:47:02 2014 From: captainkirk359 at gmail.com (Christian Gauger-Cosgrove) Date: Wed, 8 Jan 2014 22:47:02 -0500 Subject: [Simh] Possible TIME and DATE Environment Variable Improvements In-Reply-To: <0CC6789C1C831B4C8CCFF49D45D7010F0127D58D3327@REDROOF2.alohasunset.com> References: <0CC6789C1C831B4C8CCFF49D45D7010F0127D58D3327@REDROOF2.alohasunset.com> Message-ID: On 8 January 2014 15:55, Mark Pizzolato - Info Comm wrote: > Done. > {snip} > > There now is a %STIME% which returns the time as hh_mm_ss. > Excellent. ISO 8601 date format makes me a happy camper; and STIME is quite useful. (Underscores look odd; but then again HHMMSS can be confused for YYMMDD or some other truncated date format). > That should work now. The Windows binaries will be updated in a couple of minutes. > > - Mark > They work excellently, though I only managed to try them just now. Thank you very much. Christian -- Christian M. Gauger-Cosgrove STCKON08DS0 Contact information available upon request. From phiber at phiber.com Thu Jan 16 02:16:20 2014 From: phiber at phiber.com (Mark Abene) Date: Wed, 15 Jan 2014 23:16:20 -0800 Subject: [Simh] PSI for TOPS-20 Message-ID: By chance, does anyone have a tape image of PSI for TOPS-20 v7? I want to get X.25 connectivity going. Probably a long shot, but doesn't hurt to ask. -Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerry77 at mail.com Thu Jan 16 08:01:00 2014 From: gerry77 at mail.com (G.) Date: Thu, 16 Jan 2014 14:01:00 +0100 Subject: [Simh] PSI for TOPS-20 In-Reply-To: References: Message-ID: <2kkfd9pjvk8k1kjp7ns4e708sd3ua6i09v@4ax.com> On Wed, 15 Jan 2014 23:16:20 -0800, Mark Abene wrote: > By chance, does anyone have a tape image of PSI for TOPS-20 v7? I want to > get X.25 connectivity going. Probably a long shot, but doesn't hurt to ask. Both Trailing Edge and Bitsavers have BB-W661A-BM (V1.0 1983) and BB-W661B-BM (V1.1 1984) tape images, but they are for TOPS-20 V5.1 so maybe they do not work with V7. On the other hand, Autopatch tape 23 (V7 indeed) has references to PSI V1.1 so you may just want to give it a try... :) HTH, G. From phiber at phiber.com Thu Jan 16 12:20:31 2014 From: phiber at phiber.com (Mark Abene) Date: Thu, 16 Jan 2014 09:20:31 -0800 Subject: [Simh] PSI for TOPS-20 In-Reply-To: <2kkfd9pjvk8k1kjp7ns4e708sd3ua6i09v@4ax.com> References: <2kkfd9pjvk8k1kjp7ns4e708sd3ua6i09v@4ax.com> Message-ID: Thanks! I'll give it a shot. -Mark On Thu, Jan 16, 2014 at 5:01 AM, G. wrote: > On Wed, 15 Jan 2014 23:16:20 -0800, Mark Abene wrote: > >> By chance, does anyone have a tape image of PSI for TOPS-20 v7? I want to >> get X.25 connectivity going. Probably a long shot, but doesn't hurt to ask. > > Both Trailing Edge and Bitsavers have BB-W661A-BM (V1.0 1983) and BB-W661B-BM > (V1.1 1984) tape images, but they are for TOPS-20 V5.1 so maybe they do not > work with V7. On the other hand, Autopatch tape 23 (V7 indeed) has references > to PSI V1.1 so you may just want to give it a try... :) > > HTH, > G. > > _______________________________________________ > Simh mailing list > Simh at trailing-edge.com > http://mailman.trailing-edge.com/mailman/listinfo/simh From simh at alderson.users.panix.com Thu Jan 16 19:38:13 2014 From: simh at alderson.users.panix.com (Rich Alderson) Date: Thu, 16 Jan 2014 19:38:13 -0500 (EST) Subject: [Simh] PSI for TOPS-20 In-Reply-To: <2kkfd9pjvk8k1kjp7ns4e708sd3ua6i09v@4ax.com> (message from G. on Thu, 16 Jan 2014 14:01:00 +0100) References: <2kkfd9pjvk8k1kjp7ns4e708sd3ua6i09v@4ax.com> Message-ID: <20140117003813.D7869242CF@panix5.panix.com> > From: G. > Date: Thu, 16 Jan 2014 14:01:00 +0100 > On Wed, 15 Jan 2014 23:16:20 -0800, Mark Abene wrote: >> By chance, does anyone have a tape image of PSI for TOPS-20 v7? I want to >> get X.25 connectivity going. Probably a long shot, but doesn't hurt to ask. > Both Trailing Edge and Bitsavers have BB-W661A-BM (V1.0 1983) and BB-W661B-BM > (V1.1 1984) tape images, but they are for TOPS-20 V5.1 so maybe they do not > work with V7. On the other hand, Autopatch tape 23 (V7 indeed) has references > to PSI V1.1 so you may just want to give it a try... :) Given that this question was raised in a SimH context, I have to point out that SimH only emulates a KS-10 processor, which is limited to TOPS-20 v4.1, and which does not support the DN20 interface (a PDP-11/40 [or /34?]) which does DMA via the DTE20 into KL-10 memory. Looking at the tape on Trailing Edge, it specifies the DN20, so I think that this is a non-starter. Someone please point out if I'm wrong about this. Rich From b4 at gewt.net Thu Jan 16 19:39:33 2014 From: b4 at gewt.net (Cory Smelosky) Date: Thu, 16 Jan 2014 19:39:33 -0500 (EST) Subject: [Simh] PSI for TOPS-20 In-Reply-To: <20140117003813.D7869242CF@panix5.panix.com> References: <2kkfd9pjvk8k1kjp7ns4e708sd3ua6i09v@4ax.com> <20140117003813.D7869242CF@panix5.panix.com> Message-ID: On Thu, 16 Jan 2014, Rich Alderson wrote: >> From: G. >> Date: Thu, 16 Jan 2014 14:01:00 +0100 > >> On Wed, 15 Jan 2014 23:16:20 -0800, Mark Abene wrote: > >>> By chance, does anyone have a tape image of PSI for TOPS-20 v7? I want to >>> get X.25 connectivity going. Probably a long shot, but doesn't hurt to ask. > >> Both Trailing Edge and Bitsavers have BB-W661A-BM (V1.0 1983) and BB-W661B-BM >> (V1.1 1984) tape images, but they are for TOPS-20 V5.1 so maybe they do not >> work with V7. On the other hand, Autopatch tape 23 (V7 indeed) has references >> to PSI V1.1 so you may just want to give it a try... :) > > Given that this question was raised in a SimH context, I have to point out that > SimH only emulates a KS-10 processor, which is limited to TOPS-20 v4.1, and > which does not support the DN20 interface (a PDP-11/40 [or /34?]) which does > DMA via the DTE20 into KL-10 memory. Looking at the tape on Trailing Edge, it > specifies the DN20, so I think that this is a non-starter. > > Someone please point out if I'm wrong about this. > Someone was implementing DMC/KMC emulation for SIMH, iirc. > Rich > _______________________________________________ > Simh mailing list > Simh at trailing-edge.com > http://mailman.trailing-edge.com/mailman/listinfo/simh > > -- Cory Smelosky http://gewt.net Personal stuff http://gimme-sympathy.org Projects From litt at ieee.org Thu Jan 16 20:27:25 2014 From: litt at ieee.org (Timothe Litt) Date: Thu, 16 Jan 2014 20:27:25 -0500 Subject: [Simh] PSI for TOPS-20 In-Reply-To: <20140117003813.D7869242CF@panix5.panix.com> References: <2kkfd9pjvk8k1kjp7ns4e708sd3ua6i09v@4ax.com> <20140117003813.D7869242CF@panix5.panix.com> Message-ID: <52D886FD.9090802@ieee.org> > Someone please point out if I'm wrong about this. It's not that simple. You are, and you aren't. TOPS-10/20 PSI (X.25) required a DN20; the X.25 gateway software lived there. The KS hardware could not connect directly to the X.25 network. The KDP could have done it, but no driver or gateway software was written. The SimH KDP emulation does not support bit-stuffing. The gateway just made the X.25 connection look like a DECnet circuit, albeit it an expensive one. In the Phase IV DNA, X.25 is a data link layer parallel to ethernet and DDCMP. The gateway in the DN20 was accessed by a standard DECnet logical link by the PSI utilities, usually from the local host. A KS could get to the gateway using DECnet, modulo the routing restrictions/hacks of the OS version. I'm not sure about the VAX implementation - I think the 10/20 PSI (the utiltiies, such as x29pad) could talk thru it. I never tried it. It should have worked. The NML has entity definitions for X.25 circuits, and any DECnet Phase IV or greater NCP can mange one (whatever node it lives on), subject to the usual privs. So yes, the KS can't physically connect to the X.25 network. But it can use a gateway elsewhere. And it can manage one. Sometimes. X.25 Circuits were introduced in Phase IV. The NCP in TOPS-20 on the KS wouldn't have had the command tables. The Phase-IV version did. This communication may not represent my employer's views, if any, on the matters discussed. On 16-Jan-14 19:38, Rich Alderson wrote: >> From: G. >> Date: Thu, 16 Jan 2014 14:01:00 +0100 >> On Wed, 15 Jan 2014 23:16:20 -0800, Mark Abene wrote: >>> By chance, does anyone have a tape image of PSI for TOPS-20 v7? I want to >>> get X.25 connectivity going. Probably a long shot, but doesn't hurt to ask. >> Both Trailing Edge and Bitsavers have BB-W661A-BM (V1.0 1983) and BB-W661B-BM >> (V1.1 1984) tape images, but they are for TOPS-20 V5.1 so maybe they do not >> work with V7. On the other hand, Autopatch tape 23 (V7 indeed) has references >> to PSI V1.1 so you may just want to give it a try... :) > Given that this question was raised in a SimH context, I have to point out that > SimH only emulates a KS-10 processor, which is limited to TOPS-20 v4.1, and > which does not support the DN20 interface (a PDP-11/40 [or /34?]) which does > DMA via the DTE20 into KL-10 memory. Looking at the tape on Trailing Edge, it > specifies the DN20, so I think that this is a non-starter. > > Someone please point out if I'm wrong about this. > > Rich > _______________________________________________ > Simh mailing list > Simh at trailing-edge.com > http://mailman.trailing-edge.com/mailman/listinfo/simh -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5159 bytes Desc: S/MIME Cryptographic Signature URL: From captainkirk359 at gmail.com Wed Jan 22 11:16:43 2014 From: captainkirk359 at gmail.com (Christian Gauger-Cosgrove) Date: Wed, 22 Jan 2014 11:16:43 -0500 Subject: [Simh] Simulator lockup when booting RSX-11/M+ V4.6 BL87 baseline system disk with insufficient memory Message-ID: Hello: I've noticed an odd issue. When booting the aforementioned baseline RSX-11/M+ disk, with 256K of memory, RSX-11 doesn't have enough RAM to work when it tries to run the startup script. This happens as the system doesn't have enough memory to allocate a checkpoint space; so RSX-11 gets stuck in an infinite loop repeating: