General Category > LisaList2
LisaEm 1.2.7-RC4 support bug reports
rayarachelian:
Didn't manage to fix serial port A, so disabled it instead. Added host serial port support (i.e. USB to serial adapters: /dev/ttyUSB0, or wired serial ports /dev/ttyS0 - names on macos and FreeBSD will vary.).
On Linux you might not have permissions to your USB serial port, so you either have to add yourself to the right group (dialout) and then logout and log back in, or use sudo chmod o+rw on /dev/ttyUSB0 (or whatever) as the device will be owned by root and you won't be able to open it.
The Serial code in LisaEm only connects at "power on" - if for example you choose Shell (PTY) and then type in exit, you won't be able to use that connection until you tell Lisa Office System to power off and then power back on. Perhaps in future releases I'll add a way to reconnect or even switch the backend device. But for now this will suffice as a lame, but somewhat acceptably usable thing.
I've not tested this on macos yet. I've mostly used POSIX methods of opening the pty and serial port, so in theory it should work, testing may reveal it will not. Will find out soon enough. ;D
This will be part of 1.2.7-RC4 release.
As you might have noticed, I've renamed some of the options, so PTY is now "Shell" as that's more human friendly, and the parameter would be either nothing, or something like /bin/bash or /bin/zsh.
For Serial, meaning host physial serial port, you'll need to figure out the device name. If it's a USB serial port, it will create a new character device in /dev with the time/date of the insertion, so you can use ls -Flatr /dev/tty* to find it, or perhaps the output of dmesg:
--- Code: ---
$ dmesg -T
...[Wed Dec 9 12:26:22 2020] keyspan_pda 1-1:1.0: Xircom / Entrega PGS - (prerenumeration) converter detected
[Wed Dec 9 12:26:22 2020] usb 1-1: USB disconnect, device number 6
[Wed Dec 9 12:26:22 2020] keyspan_pda 1-1:1.0: device disconnected
[Wed Dec 9 12:26:24 2020] usb 1-1: new full-speed USB device number 7 using xhci_hcd
[Wed Dec 9 12:26:24 2020] usb 1-1: New USB device found, idVendor=06cd, idProduct=0104, bcdDevice=ab.89
[Wed Dec 9 12:26:24 2020] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Wed Dec 9 12:26:24 2020] usb 1-1: Product: ACME USB serial widget
[Wed Dec 9 12:26:24 2020] usb 1-1: Manufacturer: ACME usb widgets
[Wed Dec 9 12:26:24 2020] usb 1-1: SerialNumber: 47
[Wed Dec 9 12:26:24 2020] keyspan_pda 1-1:1.0: Keyspan PDA converter detected
[Wed Dec 9 12:26:24 2020] usb 1-1: Keyspan PDA converter now attached to ttyUSB0 <<<--- here it is
$ ls -Flatr /dev/tty*
....
crw-rw-rw- 1 root dialout 188, 0 Dec 9 11:37 /dev/ttyUSB0 <<-- and here.
....
--- End code ---
As you can see, the device is owned by root:dialout, so adding your user to the dialout group, followed by logging out and logging back in should get you access to the port, if not, or you don't feel like logging out, you can sudo chown it or sudo chmod it as needed.
The preferences string for the port I used is "/dev/ttyUSB0|9600,N,8,1" - the first part is the device name. This is absolutely required or you won't be able to use the port.
The | character is a separator to the parameters. If you omit it, LisaTerminal will be able to set the baud rate, number of bits, parity, and stop bits.
If you provide it, you can lock the port to the settings you've provided, and no matter what's set in Lisa Terminal the port will remain at that speed/settings.
You can also add ",hw" to enable hardware handshaking, or ",-hw" to disable it. ",xon" (as well as checking the Xon/Off checkbox will enable software handshaking on the Linux side of the port. ",-xon" will force disable software handshaking on the Linux side. Note that Lisa Terminal will still send ^S/^Q characters to signal xoff/xon through the port.
For LOS and LisaTerminal it's pretty much required to use Xon/Xoff software handshaking to prevent data loss, even though I've built in some code to detect LOS and slow down the serial port pacing, but since LisaTerminal lacks file transfers, there's not much disadvantage to enabling software handshaking.
Since Serial A is broken, it's now set to Nothing, and all the options are disabled. Sadly this will remain until I can get it to work such as LOS doesn't hang when Serial A is accessed. There's some bug in the z8530 code somewhere that prevents it from working properly.
Neither the PTY(Shell), nor the Serial port code will work on Windows. I'll eventually write Windows specific equivalent code to allow it to work there, but likely this won't be in 1.2.7.
Most likely I'll release 1.2.7 final before the end of this year, and then start on 2.0. I'll back fill some of the features into a 1.2.8 and possibly 1.2.9 - i.e. the widget emulation, and debugger features.
D.Finni:
--- Quote from: rayarachelian on December 09, 2020, 12:20:11 pm ---Since Serial A is broken, it's now set to Nothing, and all the options are disabled. Sadly this will remain until I can get it to work such as LOS doesn't hang when Serial A is accessed. There's some bug in the z8530 code somewhere that prevents it from working properly.
--- End quote ---
Isn't this the port whose baud rate is limited to 9600? Does that have something to do with the problem? Earlier this summer we discovered that one port can go up to 57600, but the other is limited to only 9600.
Also, have you committed to Github recently? I'm trying to checkout the latest source, but I don't see anything new.
blusnowkitty:
There any way you could change the Double X/Triple Y display scaler to pull up a bypassable warning instead of a hard stop? Just a minor thing really that's kinda bothered me since one of my monitors is only 100 pixels short; let me play with it anyway darn it :P
rayarachelian:
--- Quote from: D.Finni on December 09, 2020, 04:25:43 pm ---Isn't this the port whose baud rate is limited to 9600? Does that have something to do with the problem? Earlier this summer we discovered that one port can go up to 57600, but the other is limited to only 9600.
--- End quote ---
That's unrelated and has to do with the design of the I/O board and which clock is presented to which z8530 timing pin. That said, it is possible for Serial A on actual Lisas to go higher than 9600 with MacWorks (without the PFG), and it's possible to user Serial B for LocalTalk (230KBPs).
The weird thing is that early on, LisaEm passed the LisaTest of the serial ports where a cable that takes data from port A and sends it to port B and vice versa is used. So it's something in the way LOS uses it that the z8530 emulation isn't quite providing. I've tried older LisaEm's all the way down to 1.0 on macos x and they all lock up when LOS accesses Serial port A.
I'll have to retry LisaTest again to see if it still works or if it throws an error and see if I can get a clue of what's going wrong with port A.
--- Quote from: D.Finni on December 09, 2020, 04:25:43 pm ---Also, have you committed to Github recently? I'm trying to checkout the latest source, but I don't see anything new.
--- End quote ---
Nope. I only push to github when there's a release and things are stable. I'm working on adding yet another feature, so depending on how that goes the next one may be as early as next weekend, or much later.
rayarachelian:
--- Quote from: blusnowkitty on December 09, 2020, 11:54:41 pm ---There any way you could change the Double X/Triple Y display scaler to pull up a bypassable warning instead of a hard stop? Just a minor thing really that's kinda bothered me since one of my monitors is only 100 pixels short; let me play with it anyway darn it :P
--- End quote ---
Eh, I suppose I could, but then you might get stuck in that mode without a way to function properly. 100 pixels would be enough to cut off the bottom of the screen where the icons get minimized to, or the top of the screen where the menu bar is, so do you think you'd enjoy scrolling up and down of almost every operation like that? It might be fun for about 5 minutes and then will be annoying.
edit: if a window shows up too high (or too large in Lisa), you could install https://www.spectacleapp.com/ on OS if you get stuck, but sadly this isn't being supported anymore. That said it seems to work all the way up to big sur.
Ubuntu seems to implement windows key + left|right to resize the window. I'd rather not disable these, but if you're hell bent on it you could disable those dialogs yourself.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version