<div dir="auto">ubuntu simh please see that we have ubuntu 16.04 lts for long term support very stable.</div><div class="gmail_extra"><br><div class="gmail_quote">Em 12/12/2017 19:13, <<a href="mailto:simh-request@trailing-edge.com">simh-request@trailing-edge.com</a>> escreveu:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Simh mailing list submissions to<br>
<a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/mailman/listinfo/simh</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:simh-request@trailing-edge.com">simh-request@trailing-edge.com</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:simh-owner@trailing-edge.com">simh-owner@trailing-edge.com</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Simh digest..."<br>
<br>Today's Topics:<br>
<br>
1. Re: DECnet for Linux problems (Ubuntu 17.10) (Johnny Billquist)<br>
2. Re: Simh Digest, Vol 159, Issue 26 (Johnny Billquist)<br>
3. Re: Simh Digest, Vol 167, Issue 30 (Mark Pizzolato)<br>
<br><br>---------- Mensagem encaminhada ----------<br>From: Johnny Billquist <<a href="mailto:bqt@softjar.se">bqt@softjar.se</a>><br>To: <a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a><br>Cc: <br>Bcc: <br>Date: Tue, 12 Dec 2017 21:39:06 +0100<br>Subject: Re: [Simh] DECnet for Linux problems (Ubuntu 17.10)<br>On 2017-12-12 04:48, Tim Stark wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Ok, thanks for let me know. I now learned that DECnet for Linux is already orphaned a few years ago. CVS facility will go away soon on Sourceforge.net. I mirrored a copy of CVS repos and successfully converted to Git repo by following SF instructions for conversion. I will contact them for latest Linux kernel problems.<br>
</blockquote>
<br>
Uh? Isn't Linux already using git since many years?<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I will now remove decent from Ubuntu 17.10 because it complaint every few minutes and asked me to send report to Ubuntu maintainers.<br>
</blockquote>
<br>
Not that surprised. Linux usually have been very quick at changing internal APIs, making lots of code not work.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Instead I will use DECnet over IP method and got TCPware and MultiNet software to set up. That allows accesses to HECnet.<br>
</blockquote>
<br>
Right. It will. And probably work better. But it does require a VMS box. But I assume you have that.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I was looking for HECnet mail archives but can’t find them. I have now subscribed to HECnet list. Does anyone know where is that HECnet mail archives?<br>
</blockquote>
<br>
Nope. There are none.<br>
I do have all posts, but not in a digestable form, and they are also not separated from my private mail.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks,<br>
<br>
Tim<br>
<br>
*From:* Larry Baker [mailto:<a href="mailto:baker@usgs.gov" target="_blank">baker@usgs.gov</a>]<br>
*Sent:* Monday, December 11, 2017 5:21 PM<br>
*To:* <a href="mailto:fsword007@gmail.com" target="_blank">fsword007@gmail.com</a><br>
*Cc:* simh <<a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a>><br>
*Subject:* Re: [Simh] DECnet for Linux problems (Ubuntu 17.10)<br>
<br>
Tim,<br>
<br>
Linux-DECnet used to be maintained by Chrissie Caulfield. She gave that up three years ago. You might ask Steve Whitehouse (<a href="mailto:steve@chygwyn.com" target="_blank">steve@chygwyn.com</a> <mailto:<a href="mailto:steve@chygwyn.com" target="_blank">steve@chygwyn.com</a>>) or Eduardo Serrat (<a href="mailto:emserrat@hotmail.com" target="_blank">emserrat@hotmail.com</a> <mailto:<a href="mailto:emserrat@hotmail.com" target="_blank">emserrat@hotmail.com</a>>)<wbr>for advice. I last worked on the code several years ago for a DECnet/FAL-to-NFS gateway I built on a Marvell SheevaPlug (ARM) SBC using Arch Linux ARM linux-kirkwood-3.16. (The latest Linux longterm 3.16 kernel at that time was 3.16.6, at <a href="https://www.kernel.org" rel="noreferrer" target="_blank">https://www.kernel.org</a>. The last Arch Linux ARM Kirkwood-specific Linux 3.16 kernel was for 3.16.6 on October 16, 2014, at <a href="https://github.com/archlinuxarm/PKGBUILDs/commit/8be533de52d44d39b2b12999e979d4d377f5e2e5" rel="noreferrer" target="_blank">https://github.com/archlinuxar<wbr>m/PKGBUILDs/commit/8be533de52d<wbr>44d39b2b12999e979d4d377f5e2e5</a>.<wbr>) I had to patch the kernel driver in a couple places. There have been so may changes to the routing layer and networking in general in the Linux kernel, it could be a substantial amount of work to advance the decnet driver any further. Also, I found that submitting patches to older kernels is a bit of a problem because of the attitude of the gatekeeper of the Linux networking code.<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
Simh mailing list<br>
<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a><br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.c<wbr>om/mailman/listinfo/simh</a><br>
<br>
</blockquote>
<br>
<br>
-- <br>
Johnny Billquist || "I'm on a bus<br>
|| on a psychedelic trip<br>
email: <a href="mailto:bqt@softjar.se" target="_blank">bqt@softjar.se</a> || Reading murder books<br>
pdp is alive! || tryin' to stay hip" - B. Idol<br>
<br>
<br><br>---------- Mensagem encaminhada ----------<br>From: Johnny Billquist <<a href="mailto:bqt@softjar.se">bqt@softjar.se</a>><br>To: <a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a><br>Cc: <br>Bcc: <br>Date: Tue, 12 Dec 2017 21:42:12 +0100<br>Subject: Re: [Simh] Simh Digest, Vol 159, Issue 26<br>On 2017-12-12 14:52, Kurt Hamm wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am having a devil of a time hooking a physical VT220 into my Raspberry PI Simh VAX. Everything is setup and working beautifully. I can telnet from another computer with no trouble and get a vax login.<br>
<br>
I have a ttyusb0 connection. I can echo text to the terminal with no problem.<br>
<br>
I can configure Raspian to divert the console to the terminal with no problem. But, I can't telnet to the vax from the Raspberry PI operating system. I can telnet from another PC, but not from within the Raspberry Pi. So, that doesn't give me the Vax login on the terminal.<br>
</blockquote>
<br>
The reason for this is normally that you are sharing the network interface between the Linux box and your simh instance. So both speak on the same network interface. However, you do not hear what you send out, which means that you cannot communicate with anything else that is using the same interface. Essentially, the network interface does not loop back packets sent out.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So, I tried to create a serial connection to the ttyUSB0 using various means.<br>
Method 1) attach ttix line=0,connect=/dev/ttyUSB0;12<wbr>00-7n1 - This results in an error that says non-existent device.<br>
Method 2) attach dz line=0,connect=/dev/ttyUSB0;96<wbr>00-8n1 - This seemed to run successfully, but showed nothing on the terminal after a reboot.<br>
</blockquote>
<br>
Have you configured VMS to have the DZ serial ports as well?<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Is there a way to connect a physical serial terminal via /dev/ttyUSB0 using SIMh Microvax 3900 simulator?<br>
</blockquote>
<br>
Should be, I assume.<br>
<br>
Johnny<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks for any advice.<br>
<br>
Kurt<br>
<br>
On Wed, Apr 19, 2017 at 3:05 AM, <<a href="mailto:simh-request@trailing-edge.com" target="_blank">simh-request@trailing-edge.co<wbr>m</a> <mailto:<a href="mailto:simh-request@trailing-edge.com" target="_blank">simh-request@trailing-<wbr>edge.com</a>>> wrote:<br>
<br>
Send Simh mailing list submissions to<br>
<a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a> <mailto:<a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a><wbr>><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.c<wbr>om/mailman/listinfo/simh</a><br>
<<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/mailman/listinfo/simh</a>><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:simh-request@trailing-edge.com" target="_blank">simh-request@trailing-edge.com</a> <mailto:<a href="mailto:simh-request@trailing-edge.com" target="_blank">simh-request@trailing-<wbr>edge.com</a>><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:simh-owner@trailing-edge.com" target="_blank">simh-owner@trailing-edge.com</a> <mailto:<a href="mailto:simh-owner@trailing-edge.com" target="_blank">simh-owner@trailing-ed<wbr>ge.com</a>><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Simh digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: NetBSD 5.1 on MicoVAX 3900 boot error (Bob Supnik)<br>
2. Re: DEC VT emulators on MAME (Johnny Billquist)<br>
3. Re: NetBSD 5.1 on MicoVAX 3900 boot error (Mark Abene)<br>
4. Re: NetBSD 5.1 on MicoVAX 3900 boot error (Mark Pizzolato)<br>
5. Re: DEC VT emulators on MAME (Kevin Handy)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Tue, 18 Apr 2017 16:08:34 -0400<br>
From: Bob Supnik <<a href="mailto:bob@supnik.org" target="_blank">bob@supnik.org</a> <mailto:<a href="mailto:bob@supnik.org" target="_blank">bob@supnik.org</a>>><br>
To: <a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a> <mailto:<a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a><wbr>><br>
Subject: Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error<br>
Message-ID: <<a href="mailto:4ee0f9dc-071c-9ea9-fe74-48134c5e979b@supnik.org" target="_blank">4ee0f9dc-071c-9ea9-fe74-48134<wbr>c5e979b@supnik.org</a><br>
<mailto:<a href="mailto:4ee0f9dc-071c-9ea9-fe74-48134c5e979b@supnik.org" target="_blank">4ee0f9dc-071c-9ea9-fe7<wbr>4-48134c5e979b@supnik.org</a>>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
You can get a pre-built Windows 32b 3.9 executable without Ethernet (and<br>
therefore, without needing WinPCap) here:<br>
<a href="http://simh.trailing-edge.com/sources/simhv39-0-exe.zip" rel="noreferrer" target="_blank">http://simh.trailing-edge.com/<wbr>sources/simhv39-0-exe.zip</a><br>
<<a href="http://simh.trailing-edge.com/sources/simhv39-0-exe.zip" rel="noreferrer" target="_blank">http://simh.trailing-edge.com<wbr>/sources/simhv39-0-exe.zip</a>>. It should run<br>
fine under W10. See if it will boot NetBSD 5.1.<br>
<br>
/Bob Supnik<br>
<br>
On 4/18/2017 3:53 PM, <a href="mailto:simh-request@trailing-edge.com" target="_blank">simh-request@trailing-edge.com</a><br>
<mailto:<a href="mailto:simh-request@trailing-edge.com" target="_blank">simh-request@trailing-<wbr>edge.com</a>> wrote:<br>
> You shouldn't need WinPCAP merely to test if the CD image is<br>
bootable.<br>
> The point of the boot test exercise is to help determine if the<br>
problem is<br>
> in NetBSD or due to recent changes to simh. If changes to simh<br>
are at<br>
> fault, I'll track it down and fix the problem.<br>
><br>
>> I specifically want to run a 5.x version of NetBSD. I'm pretty<br>
sure it did<br>
>> run on SIMH 3.8-1 on Windows 7 before the upgrade. I need to<br>
downgrade a<br>
>> laptop I have to Win7 in the future and may try that. Until then<br>
I'll play<br>
>> with OpenBSD which doesn't seem to have any problems with SIMH<br>
4.0 beta.<br>
> The boot test I'm suggesting will be far less work than setting<br>
up another<br>
> system.<br>
><br>
> Let me know.<br>
><br>
> - Mark<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 18 Apr 2017 22:39:08 +0200<br>
From: Johnny Billquist <<a href="mailto:bqt@softjar.se" target="_blank">bqt@softjar.se</a> <mailto:<a href="mailto:bqt@softjar.se" target="_blank">bqt@softjar.se</a>>><br>
To: <a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a> <mailto:<a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a><wbr>><br>
Subject: Re: [Simh] DEC VT emulators on MAME<br>
Message-ID: <<a href="mailto:2e3a017d-0166-df35-3b92-11ab3a6912f4@softjar.se" target="_blank">2e3a017d-0166-df35-3b92-11ab3<wbr>a6912f4@softjar.se</a><br>
<mailto:<a href="mailto:2e3a017d-0166-df35-3b92-11ab3a6912f4@softjar.se" target="_blank">2e3a017d-0166-df35-3b9<wbr>2-11ab3a6912f4@softjar.se</a>>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
Ok, looked at the schematics now.<br>
<br>
On 2017-04-18 21:53, Timothe Litt wrote:<br>
><br>
><br>
>> Since they're windowless, they are not EPROM (remember what the E<br>
>> stands for), but plain ROMs.<br>
> Nope. I meant exactly what I wrote.<br>
<br>
[...]<br>
<br>
Good point about it being the same chip. I hadn't considered that<br>
possibility. I know that for some 27-series proms, there were certainly<br>
both mask programmable as well as EPROM versions, where the mask<br>
programmable was more persistent safe. EPROMs have a risk of loosing<br>
their content eventually, even if not exposed to UV light.<br>
<br>
> As for which signal you use for what - it doesn't matter. OE<br>
puts the<br>
> chip into a low power state just as effectively as CS - assuming that<br>
> the part isn't in programming or ID mode. Since the part is never<br>
> written (in the terminal), this effectively gives you 2 CS pins<br>
> (effectively ANDed), and thus decoding requires at most an inverter.<br>
<br>
Not entirely true.<br>
OE should timing wise be done after CS and addresses have been stable<br>
for a certain time. And power consumption of the chip is related to the<br>
control of CS, and is not related to OE.<br>
<br>
While power consumption might not be a problem, and the timing can be<br>
solve, it does mean that driving CS and OE cannot be done identically.<br>
If you use OE as a CS, you should make make sure the address is stable<br>
some time before you activate OE, and if you use CS, you need to still<br>
drive OE at a point later in time, and not just tie them together or<br>
something.<br>
<br>
> The 27C256 is a 32K x 8 part; it has no A15 (but the cartridge<br>
socket does.)<br>
<br>
Yes, that was obvious.<br>
<br>
> Keven pointed out that the odd chip is probably the character<br>
generator<br>
> ROM - thus the separate address and data bus - and it doesn't<br>
need a CS<br>
> or OE. It's always reading something.<br>
><br>
> As I've written before, rather than guessing, a few minutes with an<br>
> ohmmeter can sort all this out.<br>
><br>
> I'm leaving that - and further exploration - as an exercise to<br>
the reader.<br>
<br>
I seriously doubt it's a character generator ROM in the normal sense of<br>
the word. The VT340 do not generate character output in hardware.<br>
It's a graphic terminal, which stores the text in the the bitmap, as far<br>
as I remember (I seem to remember being able to go into graphics mode<br>
and affect text already written). Also, you have soft definable<br>
characters, so the CPU need to have access to the same memory the<br>
character generator would use anyway, and it has to contain some RAM,<br>
minimum. So it needs to be in the normal memory space of the CPU.<br>
<br>
But there is indeed two address and databuses, so I think it's fair to<br>
say the two select lines are only used for a subset of the PROMs.<br>
<br>
There might be data in one ROM that is copied into RAM at startup.<br>
Character definition tables, for example, I could imagine.<br>
<br>
Anyway, most things can be worked out my doing the measurements you<br>
suggest, yes.<br>
<br>
Johnny<br>
<br>
--<br>
Johnny Billquist || "I'm on a bus<br>
|| on a psychedelic trip<br>
email: <a href="mailto:bqt@softjar.se" target="_blank">bqt@softjar.se</a> <mailto:<a href="mailto:bqt@softjar.se" target="_blank">bqt@softjar.se</a>> || Reading murder books<br>
pdp is alive! || tryin' to stay hip" - B. Idol<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 18 Apr 2017 15:07:06 -0700<br>
From: Mark Abene <<a href="mailto:phiber@phiber.com" target="_blank">phiber@phiber.com</a> <mailto:<a href="mailto:phiber@phiber.com" target="_blank">phiber@phiber.com</a>>><br>
To: Bob Supnik <<a href="mailto:bob@supnik.org" target="_blank">bob@supnik.org</a> <mailto:<a href="mailto:bob@supnik.org" target="_blank">bob@supnik.org</a>>><br>
Cc: <a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a> <mailto:<a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a><wbr>><br>
Subject: Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error<br>
Message-ID:<br>
<<a href="mailto:CAPCE1iYZrkE19nrcTB-K-ZArhYi0USyAZY0FRFBvCsQwMRw30g@mail.gmail.com" target="_blank">CAPCE1iYZrkE19nrcTB-K-ZArhYi0<wbr>USyAZY0FRFBvCsQwMRw30g@mail.<wbr>gmail.com</a><br>
<mailto:<a href="mailto:CAPCE1iYZrkE19nrcTB-K-ZArhYi0USyAZY0FRFBvCsQwMRw30g@mail.gmail.com" target="_blank">CAPCE1iYZrkE19nrcTB-K-<wbr>ZArhYi0USyAZY0FRFBvCsQwMRw30g@<wbr>mail.gmail.com</a>>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Should one want winpcap in Windows 10, all one needs is:<br>
<a href="http://www.win10pcap.org/" rel="noreferrer" target="_blank">http://www.win10pcap.org/</a><br>
<br>
-Mark<br>
<br>
<br>
On Tue, Apr 18, 2017 at 1:08 PM, Bob Supnik <<a href="mailto:bob@supnik.org" target="_blank">bob@supnik.org</a><br>
<mailto:<a href="mailto:bob@supnik.org" target="_blank">bob@supnik.org</a>>> wrote:<br>
<br>
> You can get a pre-built Windows 32b 3.9 executable without<br>
Ethernet (and<br>
> therefore, without needing WinPCap) here:<br>
<a href="http://simh.trailing-edge.com/" rel="noreferrer" target="_blank">http://simh.trailing-edge.com/</a><br>
> sources/simhv39-0-exe.zip. It should run fine under W10. See if<br>
it will<br>
> boot NetBSD 5.1.<br>
><br>
> /Bob Supnik<br>
><br>
><br>
> On 4/18/2017 3:53 PM, <a href="mailto:simh-request@trailing-edge.com" target="_blank">simh-request@trailing-edge.com</a><br>
<mailto:<a href="mailto:simh-request@trailing-edge.com" target="_blank">simh-request@trailing-<wbr>edge.com</a>> wrote:<br>
><br>
>> You shouldn't need WinPCAP merely to test if the CD image is<br>
bootable.<br>
>> The point of the boot test exercise is to help determine if the<br>
problem is<br>
>> in NetBSD or due to recent changes to simh. If changes to simh<br>
are at<br>
>> fault, I'll track it down and fix the problem.<br>
>><br>
>> I specifically want to run a 5.x version of NetBSD. I'm pretty<br>
sure it did<br>
>>> run on SIMH 3.8-1 on Windows 7 before the upgrade. I need to<br>
downgrade a<br>
>>> laptop I have to Win7 in the future and may try that. Until<br>
then I'll<br>
>>> play<br>
>>> with OpenBSD which doesn't seem to have any problems with SIMH<br>
4.0 beta.<br>
>>><br>
>> The boot test I'm suggesting will be far less work than setting<br>
up another<br>
>> system.<br>
>><br>
>> Let me know.<br>
>><br>
>> - Mark<br>
>><br>
><br>
> ______________________________<wbr>_________________<br>
> Simh mailing list<br>
> <a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a> <mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a><wbr>><br>
> <a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.c<wbr>om/mailman/listinfo/simh</a><br>
<<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/mailman/listinfo/simh</a>><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL:<br>
<<a href="http://mailman.trailing-edge.com/pipermail/simh/attachments/20170418/7481cbde/attachment-0001.html" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/pipermail/simh/attachments<wbr>/20170418/7481cbde/attachment-<wbr>0001.html</a><br>
<<a href="http://mailman.trailing-edge.com/pipermail/simh/attachments/20170418/7481cbde/attachment-0001.html" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/pipermail/simh/attachments<wbr>/20170418/7481cbde/attachment-<wbr>0001.html</a>>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 18 Apr 2017 22:39:48 -0700<br>
From: Mark Pizzolato <<a href="mailto:Mark@infocomm.com" target="_blank">Mark@infocomm.com</a> <mailto:<a href="mailto:Mark@infocomm.com" target="_blank">Mark@infocomm.com</a>>><br>
To: Mark Abene <<a href="mailto:phiber@phiber.com" target="_blank">phiber@phiber.com</a> <mailto:<a href="mailto:phiber@phiber.com" target="_blank">phiber@phiber.com</a>>>, Bob<br>
Supnik <<a href="mailto:bob@supnik.org" target="_blank">bob@supnik.org</a> <mailto:<a href="mailto:bob@supnik.org" target="_blank">bob@supnik.org</a>>><br>
Cc: "<a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a> <mailto:<a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a><wbr>>"<br>
<<a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a> <mailto:<a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a><wbr>>><br>
Subject: Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error<br>
Message-ID:<br>
<<a href="mailto:03006E3FC39B5A48AB9DBCCC101090A82E8242E585@REDROOF2.alohasunset.com" target="_blank">03006E3FC39B5A48AB9DBCCC10109<wbr>0A82E8242E585@REDROOF2.alohasu<wbr>nset.com</a><br>
<mailto:<a href="mailto:03006E3FC39B5A48AB9DBCCC101090A82E8242E585@REDROOF2.alohasunset.com" target="_blank">03006E3FC39B5A48AB9DBC<wbr>CC101090A82E8242E585@REDROOF2.<wbr>alohasunset.com</a>>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Actually, the latest simh ‘supported’ WinPcap is npcap.<br>
<br>
Npcap is part of the nmap project and directly shares the latest<br>
libpcap code.<br>
<br>
Npcap has a BSD license like the original WinPcap did. Win10pcap is<br>
a GPL package and is untested and unsupported for use with simh<br>
Ethernet devices.<br>
<br>
Npcap is available from: <a href="https://github.com/nmap/npcap/releases" rel="noreferrer" target="_blank">https://github.com/nmap/npcap/<wbr>releases</a><br>
<<a href="https://github.com/nmap/npcap/releases" rel="noreferrer" target="_blank">https://github.com/nmap/npcap<wbr>/releases</a>><br>
<br>
From: Simh [mailto:<a href="mailto:simh-bounces@trailing-edge.com" target="_blank">simh-bounces@trailing-<wbr>edge.com</a><br>
<mailto:<a href="mailto:simh-bounces@trailing-edge.com" target="_blank">simh-bounces@trailing-<wbr>edge.com</a>>] On Behalf Of Mark Abene<br>
Sent: Tuesday, April 18, 2017 3:07 PM<br>
To: Bob Supnik <<a href="mailto:bob@supnik.org" target="_blank">bob@supnik.org</a> <mailto:<a href="mailto:bob@supnik.org" target="_blank">bob@supnik.org</a>>><br>
Cc: <a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a> <mailto:<a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a><wbr>><br>
Subject: Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error<br>
<br>
Should one want winpcap in Windows 10, all one needs is:<br>
<a href="http://www.win10pcap.org/" rel="noreferrer" target="_blank">http://www.win10pcap.org/</a><br>
<br>
-Mark<br>
<br>
<br>
On Tue, Apr 18, 2017 at 1:08 PM, Bob Supnik <<a href="mailto:bob@supnik.org" target="_blank">bob@supnik.org</a><br>
<mailto:<a href="mailto:bob@supnik.org" target="_blank">bob@supnik.org</a>><mailto<wbr>:<a href="mailto:bob@supnik.org" target="_blank">bob@supnik.org</a><br>
<mailto:<a href="mailto:bob@supnik.org" target="_blank">bob@supnik.org</a>>>> wrote:<br>
You can get a pre-built Windows 32b 3.9 executable without Ethernet<br>
(and therefore, without needing WinPCap) here:<br>
<a href="http://simh.trailing-edge.com/sources/simhv39-0-exe.zip" rel="noreferrer" target="_blank">http://simh.trailing-edge.com/<wbr>sources/simhv39-0-exe.zip</a><br>
<<a href="http://simh.trailing-edge.com/sources/simhv39-0-exe.zip" rel="noreferrer" target="_blank">http://simh.trailing-edge.com<wbr>/sources/simhv39-0-exe.zip</a>>. It should<br>
run fine under W10. See if it will boot NetBSD 5.1.<br>
<br>
/Bob Supnik<br>
<br>
<br>
On 4/18/2017 3:53 PM, <a href="mailto:simh-request@trailing-edge.com" target="_blank">simh-request@trailing-edge.com</a><br>
<mailto:<a href="mailto:simh-request@trailing-edge.com" target="_blank">simh-request@trailing-<wbr>edge.com</a>><mailto:<a href="mailto:simh-request@trailing-edge.com" target="_blank">simh-request@<wbr>trailing-edge.com</a><br>
<mailto:<a href="mailto:simh-request@trailing-edge.com" target="_blank">simh-request@trailing-<wbr>edge.com</a>>> wrote:<br>
You shouldn't need WinPCAP merely to test if the CD image is bootable.<br>
The point of the boot test exercise is to help determine if the<br>
problem is<br>
in NetBSD or due to recent changes to simh. If changes to simh are at<br>
fault, I'll track it down and fix the problem.<br>
I specifically want to run a 5.x version of NetBSD. I'm pretty sure<br>
it did<br>
run on SIMH 3.8-1 on Windows 7 before the upgrade. I need to downgrade a<br>
laptop I have to Win7 in the future and may try that. Until then<br>
I'll play<br>
with OpenBSD which doesn't seem to have any problems with SIMH 4.0 beta.<br>
The boot test I'm suggesting will be far less work than setting up<br>
another<br>
system.<br>
<br>
Let me know.<br>
<br>
- Mark<br>
<br>
______________________________<wbr>_________________<br>
Simh mailing list<br>
<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a><br>
<mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a><wbr>><mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.co<wbr>m</a><br>
<mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a><wbr>>><br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.c<wbr>om/mailman/listinfo/simh</a><br>
<<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/mailman/listinfo/simh</a>><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL:<br>
<<a href="http://mailman.trailing-edge.com/pipermail/simh/attachments/20170418/0aaa0ccb/attachment-0001.html" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/pipermail/simh/attachments<wbr>/20170418/0aaa0ccb/attachment-<wbr>0001.html</a><br>
<<a href="http://mailman.trailing-edge.com/pipermail/simh/attachments/20170418/0aaa0ccb/attachment-0001.html" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/pipermail/simh/attachments<wbr>/20170418/0aaa0ccb/attachment-<wbr>0001.html</a>>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Wed, 19 Apr 2017 01:05:20 -0600<br>
From: Kevin Handy <<a href="mailto:khandy21yo@gmail.com" target="_blank">khandy21yo@gmail.com</a> <mailto:<a href="mailto:khandy21yo@gmail.com" target="_blank">khandy21yo@gmail.com</a>>><br>
To: Johnny Billquist <<a href="mailto:bqt@softjar.se" target="_blank">bqt@softjar.se</a> <mailto:<a href="mailto:bqt@softjar.se" target="_blank">bqt@softjar.se</a>>><br>
Cc: "<a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a> <mailto:<a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a><wbr>>"<br>
<<a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a> <mailto:<a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a><wbr>>><br>
Subject: Re: [Simh] DEC VT emulators on MAME<br>
Message-ID:<br>
<CANk4W2OuRsR=<a href="mailto:uLH_856YSmrG4hJurJFUkn6tq_%2BHGWsAegh24Q@mail.gmail.com" target="_blank">uLH_856YSmrG4hJu<wbr>rJFUkn6tq_+HGWsAegh24Q@mail.<wbr>gmail.com</a><br>
<mailto:<a href="mailto:uLH_856YSmrG4hJurJFUkn6tq_%252BHGWsAegh24Q@mail.gmail.com" target="_blank">uLH_856YSmrG4hJurJFUkn<wbr>6tq_%2BHGWsAegh24Q@mail.gmail.<wbr>com</a>>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Looking at the schematic of the terminal from<br>
<a href="http://bitsavers.trailing-edge.com/pdf/dec/terminal/vt340/K-TC-VT340_Schematic_Feb87.pdf" rel="noreferrer" target="_blank">http://bitsavers.trailing-edge<wbr>.com/pdf/dec/terminal/vt340/K-<wbr>TC-VT340_Schematic_Feb87.pdf</a><br>
<<a href="http://bitsavers.trailing-edge.com/pdf/dec/terminal/vt340/K-TC-VT340_Schematic_Feb87.pdf" rel="noreferrer" target="_blank">http://bitsavers.trailing-edg<wbr>e.com/pdf/dec/terminal/vt340/<wbr>K-TC-VT340_Schematic_Feb87.pdf</a><wbr>>,<br>
it appears that there are two 8031 processors. One (E57) uses the<br>
'P1 AA'<br>
bus and has the 51x8 nvrom, the other (E24) uses the 'P2 BA' bus.<br>
<br>
64Kx8 ram seems to be shared between them.<br>
<br>
1st guess, E57 does most of the heavy work (serial, uart, keyboard,<br>
etc),<br>
and the other E24 handles the display.<br>
<br>
Also, for chip select,there is a 'P1 AA15 H' and a'P1 AA15 L' on the<br>
connector which should help with the chip selection logic. (ie. the<br>
inverter is inside the terminal, not on the card).<br>
<br>
<br>
<br>
<br>
On Tue, Apr 18, 2017 at 2:39 PM, Johnny Billquist <<a href="mailto:bqt@softjar.se" target="_blank">bqt@softjar.se</a><br>
<mailto:<a href="mailto:bqt@softjar.se" target="_blank">bqt@softjar.se</a>>> wrote:<br>
<br>
> Ok, looked at the schematics now.<br>
><br>
> On 2017-04-18 21:53, Timothe Litt wrote:<br>
><br>
>><br>
>><br>
>> Since they're windowless, they are not EPROM (remember what the E<br>
>>> stands for), but plain ROMs.<br>
>>><br>
>> Nope. I meant exactly what I wrote.<br>
>><br>
><br>
> [...]<br>
><br>
> Good point about it being the same chip. I hadn't considered that<br>
> possibility. I know that for some 27-series proms, there were<br>
certainly<br>
> both mask programmable as well as EPROM versions, where the mask<br>
> programmable was more persistent safe. EPROMs have a risk of<br>
loosing their<br>
> content eventually, even if not exposed to UV light.<br>
><br>
> As for which signal you use for what - it doesn't matter. OE<br>
puts the<br>
>> chip into a low power state just as effectively as CS - assuming<br>
that<br>
>> the part isn't in programming or ID mode. Since the part is never<br>
>> written (in the terminal), this effectively gives you 2 CS pins<br>
>> (effectively ANDed), and thus decoding requires at most an inverter.<br>
>><br>
><br>
> Not entirely true.<br>
> OE should timing wise be done after CS and addresses have been<br>
stable for<br>
> a certain time. And power consumption of the chip is related to<br>
the control<br>
> of CS, and is not related to OE.<br>
><br>
> While power consumption might not be a problem, and the timing can be<br>
> solve, it does mean that driving CS and OE cannot be done<br>
identically. If<br>
> you use OE as a CS, you should make make sure the address is<br>
stable some<br>
> time before you activate OE, and if you use CS, you need to still<br>
drive OE<br>
> at a point later in time, and not just tie them together or<br>
something.<br>
><br>
> The 27C256 is a 32K x 8 part; it has no A15 (but the cartridge socket<br>
>> does.)<br>
>><br>
><br>
> Yes, that was obvious.<br>
><br>
> Keven pointed out that the odd chip is probably the character<br>
generator<br>
>> ROM - thus the separate address and data bus - and it doesn't<br>
need a CS<br>
>> or OE. It's always reading something.<br>
>><br>
>> As I've written before, rather than guessing, a few minutes with an<br>
>> ohmmeter can sort all this out.<br>
>><br>
>> I'm leaving that - and further exploration - as an exercise to<br>
the reader.<br>
>><br>
><br>
> I seriously doubt it's a character generator ROM in the normal<br>
sense of<br>
> the word. The VT340 do not generate character output in hardware.<br>
> It's a graphic terminal, which stores the text in the the bitmap,<br>
as far<br>
> as I remember (I seem to remember being able to go into graphics<br>
mode and<br>
> affect text already written). Also, you have soft definable<br>
characters, so<br>
> the CPU need to have access to the same memory the character<br>
generator<br>
> would use anyway, and it has to contain some RAM, minimum. So it<br>
needs to<br>
> be in the normal memory space of the CPU.<br>
><br>
> But there is indeed two address and databuses, so I think it's<br>
fair to say<br>
> the two select lines are only used for a subset of the PROMs.<br>
><br>
> There might be data in one ROM that is copied into RAM at startup.<br>
> Character definition tables, for example, I could imagine.<br>
><br>
> Anyway, most things can be worked out my doing the measurements you<br>
> suggest, yes.<br>
><br>
><br>
> Johnny<br>
><br>
> --<br>
> Johnny Billquist || "I'm on a bus<br>
> || on a psychedelic trip<br>
> email: <a href="mailto:bqt@softjar.se" target="_blank">bqt@softjar.se</a> <mailto:<a href="mailto:bqt@softjar.se" target="_blank">bqt@softjar.se</a>> || Reading murder books<br>
> pdp is alive! || tryin' to stay hip" - B. Idol<br>
> ______________________________<wbr>_________________<br>
> Simh mailing list<br>
> <a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a> <mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a><wbr>><br>
> <a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.c<wbr>om/mailman/listinfo/simh</a><br>
<<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/mailman/listinfo/simh</a>><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL:<br>
<<a href="http://mailman.trailing-edge.com/pipermail/simh/attachments/20170419/b8562239/attachment.html" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/pipermail/simh/attachments<wbr>/20170419/b8562239/attachment.<wbr>html</a><br>
<<a href="http://mailman.trailing-edge.com/pipermail/simh/attachments/20170419/b8562239/attachment.html" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/pipermail/simh/attachments<wbr>/20170419/b8562239/attachment.<wbr>html</a>>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
______________________________<wbr>_________________<br>
Simh mailing list<br>
<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a> <mailto:<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a><wbr>><br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.c<wbr>om/mailman/listinfo/simh</a><br>
<<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/mailman/listinfo/simh</a>><br>
<br>
------------------------------<br>
<br>
End of Simh Digest, Vol 159, Issue 26<br>
******************************<wbr>*******<br>
<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
Simh mailing list<br>
<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a><br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.c<wbr>om/mailman/listinfo/simh</a><br>
<br>
</blockquote>
<br>
<br>
-- <br>
Johnny Billquist || "I'm on a bus<br>
|| on a psychedelic trip<br>
email: <a href="mailto:bqt@softjar.se" target="_blank">bqt@softjar.se</a> || Reading murder books<br>
pdp is alive! || tryin' to stay hip" - B. Idol<br>
<br>
<br><br>---------- Mensagem encaminhada ----------<br>From: Mark Pizzolato <<a href="mailto:Mark@infocomm.com">Mark@infocomm.com</a>><br>To: Kurt Hamm <<a href="mailto:kurt@hamm.me">kurt@hamm.me</a>>, "<a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a>" <<a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a>><br>Cc: <br>Bcc: <br>Date: Tue, 12 Dec 2017 13:12:20 -0800<br>Subject: Re: [Simh] Simh Digest, Vol 167, Issue 30<br><div lang="EN-US" link="blue" vlink="purple"><div class="m_-4087988756588622749WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Hi Kurt,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">This is a duplicate of a recently reported problem with host physical serial port connections through the DZ device on the VAX simulator. Details at: <a href="https://github.com/simh/simh/issues/504" target="_blank">https://github.com/simh/simh/<wbr>issues/504</a><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I haven’t had time to setup the environment to test this so I can track down the underlying problem.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Meanwhile, you can connect the physical terminal to the VAX simulator’s console port with:<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> sim> SET CONSOLE SERIAL=ser0;9600-8n1<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">or equivalently on your system:<u></u><u></u></span></p><p class="MsoNormal"><a name="m_-4087988756588622749__MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> sim> SET CONSOLE SERIAL=/dev/ttyUSB0;9600-8n1<u></u><u></u></span></a></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">The failure of your command:<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> sim> attach ttix line=0,connect=/dev/ttyUSB0;<wbr>1200-7n1<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> Non-existent device<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Is pilot error on your part. There is no TTIX device in the VAX simulator and the error message correctly reports that. That command might work on the PDP8 simulator which does have a TTIX device…<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="m_-4087988756588622749MsoListParagraph"><u></u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><span>-<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Mark<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"><div><div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Simh [mailto:<a href="mailto:simh-bounces@trailing-edge.com" target="_blank">simh-bounces@trailing-<wbr>edge.com</a>] <b>On Behalf Of </b>Kurt Hamm<br><b>Sent:</b> Tuesday, December 12, 2017 6:01 AM<br><b>To:</b> <a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a><br><b>Subject:</b> Re: [Simh] Simh Digest, Vol 167, Issue 30<u></u><u></u></span></p></div></div><p class="MsoNormal"><u></u> <u></u></p><div><div><div><div><p class="MsoNormal">My sincere apologies to the group for posting a complete thread with my question below.<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">I wanted to clarify. I can connect the terminal to the Raspberry Pi via Raspian with no problem. I would like to connect the terminal as a serial device within Simh.<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Kurt<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"><p class="MsoNormal" style="margin-bottom:12.0pt">Message: 6<br>Date: Tue, 12 Dec 2017 08:52:39 -0500<br>From: Kurt Hamm <<a href="mailto:kurt@hamm.me" target="_blank">kurt@hamm.me</a>><br>To: <a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a><br>Subject: Re: [Simh] Simh Digest, Vol 159, Issue 26<br>Message-ID:<br> <<a href="mailto:CAJRDvfWDKDDw5jS23BQUZqC5z89wd5U6F3i90cRNFg-ZDkkfLA@mail.gmail.com" target="_blank">CAJRDvfWDKDDw5jS23BQUZqC5z89w<wbr>d5U6F3i90cRNFg-ZDkkfLA@mail.<wbr>gmail.com</a>><br>Content-Type: text/plain; charset="utf-8"<br><br>I am having a devil of a time hooking a physical VT220 into my Raspberry PI<br>Simh VAX. Everything is setup and working beautifully. I can telnet from<br>another computer with no trouble and get a vax login.<br><br>I have a ttyusb0 connection. I can echo text to the terminal with no<br>problem.<br><br>I can configure Raspian to divert the console to the terminal with no<br>problem. But, I can't telnet to the vax from the Raspberry PI operating<br>system. I can telnet from another PC, but not from within the Raspberry<br>Pi. So, that doesn't give me the Vax login on the terminal.<br><br>So, I tried to create a serial connection to the ttyUSB0 using various<br>means.<br>Method 1) attach ttix line=0,connect=/dev/ttyUSB0;<wbr>1200-7n1 - This results<br>in an error that says non-existent device.<br>Method 2) attach dz line=0,connect=/dev/ttyUSB0;<wbr>9600-8n1 - This seemed to<br>run successfully, but showed nothing on the terminal after a reboot.<br><br>Is there a way to connect a physical serial terminal via /dev/ttyUSB0 using<br>SIMh Microvax 3900 simulator?<br><br>Thanks for any advice.<br><br>Kurt<u></u><u></u></p></blockquote></div></div></div></div></div></div><br>______________________________<wbr>_________________<br>
Simh mailing list<br>
<a href="mailto:Simh@trailing-edge.com">Simh@trailing-edge.com</a><br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/mailman/listinfo/simh</a><br></blockquote></div></div>