Re: [M100] M100 as Terminal to Raspberry Pi
I started over with a new install of Raspian and that made errors go away at home. It will be curious how it works at the office. On Tue, Jul 13, 2021 at 7:12 PM Bill Miranda wrote: > The errors I am getting are as follows: > > -bash: cannot set terminal process group (868): Inappropriate ioctl for > device > -bash: no job control in this shell > Then it is not registering all my keystrokes on the Pi connected by the > USB serial cable that I got from Retrofloppy.com > > > > On Tue, Jul 13, 2021 at 3:48 AM Brian Brindle wrote: > >> Hey Bill, >> >> Weird, what sort of error is it giving you? That absolutely should work >> without any issues.. Dumb quesiton, do you have flow control enabled? (Last >> character on your STAT should be an E to accomplish this.) Sometimes that >> can cause this. Editing the wpa_supplicant file can be a bit of a challenge >> from the M100 with a traditional editor.. I do find it easier to >> either have my wpa_supplicant file pre-loaded, but there are options.. >> >> When sitting at your local coffee shop, scan for wireless networks. Run: >> *sudo >> iwlist wlan0 scan *to list the nearby networks. Do some fancy grep work >> or make sure you have your dot-matrix printer at the ready to capture it >> all. It's gonna scroll across the screen for the next 10 minutes, so sit >> back and enjoy your coffee, enjoy all the new friends you will make with >> your dot matrix printer screaming away - or alternatively just look for the >> wifi network on your phone. >> >> To add the config from the M100 and not use an editor: >> >> sudo wpa_passphrase *SSID-of-WiFi-Here* >> >> /etc/wpa_supplicant/wpa_supplicant.conf(Always make backups of the >> original files when on the M100! Easier to copy back than to try and edit >> with a tiny screen.) >> >> It should prompt you for the network password. Enter that and it will >> append the network to your existing wpa_suplicant.conf file. >> >> Then issue: >> sudo wpa_cli -i wlan0 reconfigure >> >> This will activate the changes. >> >> Hope this helps, >> Brian >> >> >> >> >> >> >> >> >> >> >> On Tue, Jul 13, 2021 at 12:38 AM Bill Miranda >> wrote: >> >>> Brian your response was much appreciated. I am still having a problem >>> with my Pi. I got it working at home but then I took it to the office and >>> plugged it in but I thought I would be able to change the wifi from the >>> terminal connection. No joy. I guess I need to change the wpa supplicant >>> file at home. When I got to the office, the M100 can log into the Pi but I >>> get a bash error with every command, even something simple like "ls". >>> >>> On Mon, Jul 12, 2021 at 9:43 AM Brian Brindle >>> wrote: >>> Hi Bill, I totally missed that you actually had your console working, sorry the systemd changes make me blind with rage. If you are primarily using BBSes X-modem works pretty well, if you have an X-Modem capable term on your M100. You can also send files to/from the M100 via the Linux command line with the sx (send x-modem) command. Brian On Mon, Jul 12, 2021 at 8:15 AM Bill Miranda wrote: > Thank you so much! Embarrassingly I discovered my problem was that > that I had to go into raspi-config and designate my country so the WiFi > would work. The packages I was trying to install on my raspberry pi > weren’t installing because no internet. Once I got that sorted and made a > couple changes to configure I was good to go and successfully contacted a > BBS with the setup. Now I need to sort out out to exchange files. Thanks > again for your response. > > Regards, > Bill Miranda > bill.mira...@gmail.com > > On Jul 12, 2021, at 6:18 AM, Brian Brindle wrote: > > > HI Bill, > > The divergence from systemd is frustrating but at last current > versions of Raspian still have ifconfig... > > I'm using Raspian 10 here are my quick and dirty hints: > > Get your termcap sorted: > https://zork.net/~octal/mod100.xhtml > > You will note that termcap doesn't exist like it should though, so > save the cap to a file and install it like so: > > tic > > I assume you are going to to the easy route and use a USB to serial > adapter. You can use the onboard UART with some level conversion as I have > done, but you have to get creative with the hardware. Check out the photos > of my M100 hooked to my pi zero here: > http://niedobry.com/mod100/tanpi/ > > Copy the template file */lib/systemd/system/**serial-getty@.service* > to* /etc/systemd/system/serial-getty@ttyUSB0.service*(Provided > you are using ttyUSB0) > > In [Service] modify the ExecStart line to say the following: (Adjust > your baud as you like.) > ExecStart=-/sbin/agetty -o '-p -- \\u' 19200 %I trs100 > > Issue *systemctl enable serial-getty@ttyUSB0.service* > > Do a
[M100] NEC 32kb BANK2 upgrade card and M100 24kB Upgrade card
Regarding my new memory upgrade cards, information posted at the wiki- https://bitchin100.com/wiki/index.php?title=PC-8201_BANK2_32kB_SRAM_card https://bitchin100.com/wiki/index.php?title=M100_26-3801_24kB_SRAM_card Nothing too novel here, but I made it for my purposes and thought I would share. If anyone is interested, ordering info is posted here. https://bitchin100.com/wiki/index.php?title=Ordering_Information cheers Steve
Re: [M100] M100 as Terminal to Raspberry Pi
The errors I am getting are as follows: -bash: cannot set terminal process group (868): Inappropriate ioctl for device -bash: no job control in this shell Then it is not registering all my keystrokes on the Pi connected by the USB serial cable that I got from Retrofloppy.com On Tue, Jul 13, 2021 at 3:48 AM Brian Brindle wrote: > Hey Bill, > > Weird, what sort of error is it giving you? That absolutely should work > without any issues.. Dumb quesiton, do you have flow control enabled? (Last > character on your STAT should be an E to accomplish this.) Sometimes that > can cause this. Editing the wpa_supplicant file can be a bit of a challenge > from the M100 with a traditional editor.. I do find it easier to > either have my wpa_supplicant file pre-loaded, but there are options.. > > When sitting at your local coffee shop, scan for wireless networks. Run: *sudo > iwlist wlan0 scan *to list the nearby networks. Do some fancy grep work > or make sure you have your dot-matrix printer at the ready to capture it > all. It's gonna scroll across the screen for the next 10 minutes, so sit > back and enjoy your coffee, enjoy all the new friends you will make with > your dot matrix printer screaming away - or alternatively just look for the > wifi network on your phone. > > To add the config from the M100 and not use an editor: > > sudo wpa_passphrase *SSID-of-WiFi-Here* >> > /etc/wpa_supplicant/wpa_supplicant.conf(Always make backups of the > original files when on the M100! Easier to copy back than to try and edit > with a tiny screen.) > > It should prompt you for the network password. Enter that and it will > append the network to your existing wpa_suplicant.conf file. > > Then issue: > sudo wpa_cli -i wlan0 reconfigure > > This will activate the changes. > > Hope this helps, > Brian > > > > > > > > > > > On Tue, Jul 13, 2021 at 12:38 AM Bill Miranda > wrote: > >> Brian your response was much appreciated. I am still having a problem >> with my Pi. I got it working at home but then I took it to the office and >> plugged it in but I thought I would be able to change the wifi from the >> terminal connection. No joy. I guess I need to change the wpa supplicant >> file at home. When I got to the office, the M100 can log into the Pi but I >> get a bash error with every command, even something simple like "ls". >> >> On Mon, Jul 12, 2021 at 9:43 AM Brian Brindle wrote: >> >>> Hi Bill, >>> >>> I totally missed that you actually had your console working, sorry the >>> systemd changes make me blind with rage. >>> >>> If you are primarily using BBSes X-modem works pretty well, if you have >>> an X-Modem capable term on your M100. You can also send files to/from the >>> M100 via the Linux command line with the sx (send x-modem) command. >>> >>> Brian >>> >>> >>> On Mon, Jul 12, 2021 at 8:15 AM Bill Miranda >>> wrote: >>> Thank you so much! Embarrassingly I discovered my problem was that that I had to go into raspi-config and designate my country so the WiFi would work. The packages I was trying to install on my raspberry pi weren’t installing because no internet. Once I got that sorted and made a couple changes to configure I was good to go and successfully contacted a BBS with the setup. Now I need to sort out out to exchange files. Thanks again for your response. Regards, Bill Miranda bill.mira...@gmail.com On Jul 12, 2021, at 6:18 AM, Brian Brindle wrote: HI Bill, The divergence from systemd is frustrating but at last current versions of Raspian still have ifconfig... I'm using Raspian 10 here are my quick and dirty hints: Get your termcap sorted: https://zork.net/~octal/mod100.xhtml You will note that termcap doesn't exist like it should though, so save the cap to a file and install it like so: tic I assume you are going to to the easy route and use a USB to serial adapter. You can use the onboard UART with some level conversion as I have done, but you have to get creative with the hardware. Check out the photos of my M100 hooked to my pi zero here: http://niedobry.com/mod100/tanpi/ Copy the template file */lib/systemd/system/**serial-getty@.service* to* /etc/systemd/system/serial-getty@ttyUSB0.service*(Provided you are using ttyUSB0) In [Service] modify the ExecStart line to say the following: (Adjust your baud as you like.) ExecStart=-/sbin/agetty -o '-p -- \\u' 19200 %I trs100 Issue *systemctl enable serial-getty@ttyUSB0.service* Do a ps -ax | grep getty and you should now see a getty process running on the USB port. Connect your Model-T with a null modem cable to the serial port, set your TERM to STAT 98N1E and you should be good to go. Lots and lots of customization needed for it to be useful, I'm working on getting my notes
Re: [M100] A decent replacement for M100 "Feet"
On Tue, Jul 13, 2021 at 6:18 PM Brian White wrote: > Dang, TS-DOS is specifically requesting the name "ROOT", which means I > have to make PDDuino use that, and you can't have a real directory named > ROOT. > > There is a macro or const you can edit in the main .ino to change that > from "SD: " to "ROOT ". > > Probably won't affect UR2 but if it's baked into something like TS-DOS > since 35 years ago, then I just have to go along. > > Then again... TS-DOS is the one thing that actually works pretty well as > it is. So then, no I don't ??? > > Anyway thanks for the captures. > I don't think that's the issue, in this case the capture was taken from the perspective of the TPDD so RX is what the TPDD is receiving and TX is what it is sending, so it sent ROOT - didn't ask for it and in this case it was actually correct.. That was the name of the dir. (Sorry,that was probably confusing.) Capture was done with a NADs box since it would be successful. What I was seeing during testing was loading DOS100.CO from the UR2 didn't an FDC Emulation mode command (M1) and the PDDuino didn't seem to know how to proceed without having the dmeLabel set. If you run through one cycle with TS-DOS where it does check for FDC, everything works after that point. So I think there is something broken in the routine to allow for a non FDC Emulation request, although I haven't been able to nail it down yet and I did majorly screw everything up trying to "improve" debugging before.. Lashing together a modular test setup now with the serial port broken out for capture. Should make it easier to get a full capture of the issue. Brian
Re: [M100] M100 as Terminal to Raspberry Pi
Huh. The timing on this is interesting. I just started writing a line based text editor; my long term plan is to run it in Linux, CP/M, and Commodore computers (including the upcoming Commander X16.) If you're interested in trying it on your Pi/Model M setup, I can ping the list here when it's ready for an initial test (probably a couple of weeks.) Tom Wilson wilso...@gmail.com (619)940-6311 On Tue, Jul 13, 2021 at 2:18 AM Brian Brindle wrote: > Hey Bill, > > Weird, what sort of error is it giving you? That absolutely should work > without any issues.. Dumb quesiton, do you have flow control enabled? (Last > character on your STAT should be an E to accomplish this.) Sometimes that > can cause this. Editing the wpa_supplicant file can be a bit of a challenge > from the M100 with a traditional editor.. I do find it easier to > either have my wpa_supplicant file pre-loaded, but there are options.. > > When sitting at your local coffee shop, scan for wireless networks. Run: *sudo > iwlist wlan0 scan *to list the nearby networks. Do some fancy grep work > or make sure you have your dot-matrix printer at the ready to capture it > all. It's gonna scroll across the screen for the next 10 minutes, so sit > back and enjoy your coffee, enjoy all the new friends you will make with > your dot matrix printer screaming away - or alternatively just look for the > wifi network on your phone. > > To add the config from the M100 and not use an editor: > > sudo wpa_passphrase *SSID-of-WiFi-Here* >> > /etc/wpa_supplicant/wpa_supplicant.conf(Always make backups of the > original files when on the M100! Easier to copy back than to try and edit > with a tiny screen.) > > It should prompt you for the network password. Enter that and it will > append the network to your existing wpa_suplicant.conf file. > > Then issue: > sudo wpa_cli -i wlan0 reconfigure > > This will activate the changes. > > Hope this helps, > Brian > > > > > > > > > > > On Tue, Jul 13, 2021 at 12:38 AM Bill Miranda > wrote: > >> Brian your response was much appreciated. I am still having a problem >> with my Pi. I got it working at home but then I took it to the office and >> plugged it in but I thought I would be able to change the wifi from the >> terminal connection. No joy. I guess I need to change the wpa supplicant >> file at home. When I got to the office, the M100 can log into the Pi but I >> get a bash error with every command, even something simple like "ls". >> >> On Mon, Jul 12, 2021 at 9:43 AM Brian Brindle wrote: >> >>> Hi Bill, >>> >>> I totally missed that you actually had your console working, sorry the >>> systemd changes make me blind with rage. >>> >>> If you are primarily using BBSes X-modem works pretty well, if you have >>> an X-Modem capable term on your M100. You can also send files to/from the >>> M100 via the Linux command line with the sx (send x-modem) command. >>> >>> Brian >>> >>> >>> On Mon, Jul 12, 2021 at 8:15 AM Bill Miranda >>> wrote: >>> Thank you so much! Embarrassingly I discovered my problem was that that I had to go into raspi-config and designate my country so the WiFi would work. The packages I was trying to install on my raspberry pi weren’t installing because no internet. Once I got that sorted and made a couple changes to configure I was good to go and successfully contacted a BBS with the setup. Now I need to sort out out to exchange files. Thanks again for your response. Regards, Bill Miranda bill.mira...@gmail.com On Jul 12, 2021, at 6:18 AM, Brian Brindle wrote: HI Bill, The divergence from systemd is frustrating but at last current versions of Raspian still have ifconfig... I'm using Raspian 10 here are my quick and dirty hints: Get your termcap sorted: https://zork.net/~octal/mod100.xhtml You will note that termcap doesn't exist like it should though, so save the cap to a file and install it like so: tic I assume you are going to to the easy route and use a USB to serial adapter. You can use the onboard UART with some level conversion as I have done, but you have to get creative with the hardware. Check out the photos of my M100 hooked to my pi zero here: http://niedobry.com/mod100/tanpi/ Copy the template file */lib/systemd/system/**serial-getty@.service* to* /etc/systemd/system/serial-getty@ttyUSB0.service*(Provided you are using ttyUSB0) In [Service] modify the ExecStart line to say the following: (Adjust your baud as you like.) ExecStart=-/sbin/agetty -o '-p -- \\u' 19200 %I trs100 Issue *systemctl enable serial-getty@ttyUSB0.service* Do a ps -ax | grep getty and you should now see a getty process running on the USB port. Connect your Model-T with a null modem cable to the serial port, set your TERM to STAT 98N1E and you
Re: [M100] A decent replacement for M100 "Feet"
Dang, TS-DOS is specifically requesting the name "ROOT", which means I have to make PDDuino use that, and you can't have a real directory named ROOT. There is a macro or const you can edit in the main .ino to change that from "SD: " to "ROOT ". Probably won't affect UR2 but if it's baked into something like TS-DOS since 35 years ago, then I just have to go along. Then again... TS-DOS is the one thing that actually works pretty well as it is. So then, no I don't ??? Anyway thanks for the captures. -- bkw On Tue, Jul 13, 2021, 4:21 AM Brian Brindle wrote: > >> That is strange. Remember, UR2 works with a real tpdd which has no such > thing as a current directory label, and as well, the whole point of the UR2 > stub on-demand loader is that you don't have TS-DOS installed, either ram > or rom. > > I'm probably not articulating what I'm trying to say right, it's > sometimes impossible for me to talk without a whiteboard. I'd explain why, > but we'd need a whiteboard. > > Here is the behavior I have observed: > > TS-DOS seems to always use M1, or at least does when loading a directory > anyway. UR2 does not when asking for DOS100.CO. > > (Working Dev) > UR2: > RX: 5A 5A 07 00 F8 0D - ZZ > TX: 12 01 00 EC 0D 0A 3E 20 - > > > RX: 5A 5A 00 1A 44 4F 53 31 30 30 2E 43 4F 20 20 20 20 20 20 20 20 20 20 > 20 20 20 20 20 46 00 - ZZ..DOS100.CO F > TX: 11 1C 44 4F 53 31 30 30 2E 43 4F 20 20 20 20 20 20 20 20 20 20 20 20 > 20 20 20 46 FF FF 9D - DOS100.CO F > RX: 5A 5A 01 01 03 FA - ZZ > TX: 12 01 00 EC > RX: 5A 5A 03 00 FC - > > TS-DOS: > RX: 4D 31 0D 5A 5A 08 00 F7 0D - M1 ZZ > TX: 12 0B 00 52 4F 4F 54 20 20 2E 3C 3E 20 96 - ROOT <> > RX: 0D 4D 31 0D 5A 5A 07 00 F8 - M1 ZZ > TX: 12 01 00 EC > RX: 4D 31 0D 5A 5A 08 00 F7 0D - M1 ZZ > TX: 12 0B 00 52 4F 4F 54 20 20 2E 3C 3E 20 96 - ROOT <> > RX: 0D 4D 31 0D 5A 5A 07 00 F8 - M1 ZZ > TX: 12 01 00 EC > RX: 5A 5A 08 00 F7 - ZZ > TX: 12 0B 00 52 4F 4F 54 20 20 2E 3C 3E 20 96 - ROOT <> > RX: 5A 5A 00 1A 44 4F 53 31 30 30 2E 43 4F 20 20 20 20 20 20 20 20 20 20 > 20 20 20 20 20 46 00 - ZZ DOS100.CO F > TX: 11 1C 44 4F 53 31 30 30 2E 43 4F 20 20 20 20 20 20 20 20 20 20 20 20 > 20 20 20 46 FF FF 9D - DOS100.C0 F > > So, in my playing it looks like when you swap back to TS-DOS, load a > directory it runs the PDDuino through the M1 routine, sets the dmeLabel then > when you flip to the UR2, do the load DOS it takes the ZZ DOS100.CO F > without any issue. Do just the ZZ DOS100.CO F without dmeLabel set it > just looks at you. > > - Brian > > > > On Mon, Jul 12, 2021 at 11:26 PM Brian White wrote: > >> >> >> bkw >> >> On Mon, Jul 12, 2021, 9:48 PM Brian Brindle wrote: >> >>> >>> >>> On Mon, Jul 12, 2021 at 5:34 PM Brian K. White >>> wrote: >>> master actually? or latest default branch which is not master but 0.4.1? I didn't have master marked as default currently because I thought I had made it worse, you know like the partly-broken point mid-way in a refactor, so I made the last-known at least basically-minimally-working version default. But if you're actually using the master branch that's great and I'll switch that to default. That is where I started porting Jim's main loop. >>> >>> I'm using the Master. I had a lot of issues with the current default. >>> Granted I didn't improve my situation by mucking with it, but I stumbled on >>> the Master, saw the changes you made and liked them so went with it. It's >>> been working pretty well since. >>> >>> Biggest thing I saw was the PDDuino would wander off looking for >>> > label information and not respond to drive commands. Like when trying to > load TS-DOS from the UR2 it would fail unless you could force the > PDDuino to get a disk label, IE: swap to TS-DOS rom, list a directory, > then it would happily go on to the load step. It is somewhat working now > so I took a break from it, although my M0 still doesn't work and I'm not > 100% sure why but I think it's the guy from SdFats fault.. I'd love to know the fix for that. I wrote a whole paragraph in the front page readme about it just as a bug description to be figured out sometime. >>> >>> I did a lot of debugging on this, both with a serial monitor and with >>> the debug options on the pdduino. I came to the conclusion that it had >>> something to do with dmeLabel not getting set. When watching the >>> interactions it looked like the UR2 just does a ZZ - ZZ DOS100.CO and >>> that's it. TS-DOS did a little dance that gave it the root dir first and >>> set dmeLabel. >>> >> >> >> That is strange. Remember, UR2 works with a real tpdd which has no such >> thing as a current directory label, and as well, the whole point of the UR2 >> stub on-demand loader is that you don't have TS-DOS installed, either ram >> or rom. >> >> Ken Pettit has a TS-DOS disassembly in his directory on club100 that we >> can consult too when it comes
Re: [M100] A decent replacement for M100 "Feet"
> > I always had the idea that there could be a whole raft of virtual files > that don't actually exist but that could be used to issue commands or > return data like RTC time etc, like /proc /sys etc. They could even be in > their own virtual sub dir. The dir could even be invisible where it isn't > listed in the root directory listing, but never the less works if you > request the right dir and filenames. > I like the idea that, at least for some things, you might be able go use > them by just opening the "file" in TEXT. Or sched or addr for that matter. > You could have a 2 MB address book for real, but a virtual addr.do that > only sees a 5k window of it at any given time. > I don't actually know what all the useful uses might be but it just seems > obvious to provide the facility simply because you can, and maybe someone > else comes up with functions that are made possible by using the facility. The virtual files would be very useful, if not found in current dir - look to the magic directory and serve up the file. Would be great for SARDINE and DOS and I don't think would cost too much memory/program wise. I could just never get past the whole, do I search the "magic" directory for specific files defined somewhere or if it doesn't exist I just check for predefined files? I thought about a config file that would be read on boot/insertion that would set these hints but with the limited memory I didn't want that to get too big. Maybe read the file each time? Maybe just one directory where you put things and they always show, but then how do you treat duplicates? Fun stuff to play with. I really like the /proc file system idea, that's pretty smart to use the file system to transmit the data. One thing I would also like to see though is serial communication that does something similar. IE: a serial command that can pull real time clock info as well as the /proc/. That would give me the best of both worlds for doing things. I really do miss the CLI interface the NADs has when using this device. -Brian
Re: [M100] M100 as Terminal to Raspberry Pi
Hey Bill, Weird, what sort of error is it giving you? That absolutely should work without any issues.. Dumb quesiton, do you have flow control enabled? (Last character on your STAT should be an E to accomplish this.) Sometimes that can cause this. Editing the wpa_supplicant file can be a bit of a challenge from the M100 with a traditional editor.. I do find it easier to either have my wpa_supplicant file pre-loaded, but there are options.. When sitting at your local coffee shop, scan for wireless networks. Run: *sudo iwlist wlan0 scan *to list the nearby networks. Do some fancy grep work or make sure you have your dot-matrix printer at the ready to capture it all. It's gonna scroll across the screen for the next 10 minutes, so sit back and enjoy your coffee, enjoy all the new friends you will make with your dot matrix printer screaming away - or alternatively just look for the wifi network on your phone. To add the config from the M100 and not use an editor: sudo wpa_passphrase *SSID-of-WiFi-Here* >> /etc/wpa_supplicant/wpa_supplicant.conf(Always make backups of the original files when on the M100! Easier to copy back than to try and edit with a tiny screen.) It should prompt you for the network password. Enter that and it will append the network to your existing wpa_suplicant.conf file. Then issue: sudo wpa_cli -i wlan0 reconfigure This will activate the changes. Hope this helps, Brian On Tue, Jul 13, 2021 at 12:38 AM Bill Miranda wrote: > Brian your response was much appreciated. I am still having a problem > with my Pi. I got it working at home but then I took it to the office and > plugged it in but I thought I would be able to change the wifi from the > terminal connection. No joy. I guess I need to change the wpa supplicant > file at home. When I got to the office, the M100 can log into the Pi but I > get a bash error with every command, even something simple like "ls". > > On Mon, Jul 12, 2021 at 9:43 AM Brian Brindle wrote: > >> Hi Bill, >> >> I totally missed that you actually had your console working, sorry the >> systemd changes make me blind with rage. >> >> If you are primarily using BBSes X-modem works pretty well, if you have >> an X-Modem capable term on your M100. You can also send files to/from the >> M100 via the Linux command line with the sx (send x-modem) command. >> >> Brian >> >> >> On Mon, Jul 12, 2021 at 8:15 AM Bill Miranda >> wrote: >> >>> Thank you so much! Embarrassingly I discovered my problem was that that >>> I had to go into raspi-config and designate my country so the WiFi would >>> work. The packages I was trying to install on my raspberry pi weren’t >>> installing because no internet. Once I got that sorted and made a couple >>> changes to configure I was good to go and successfully contacted a BBS with >>> the setup. Now I need to sort out out to exchange files. Thanks again for >>> your response. >>> >>> Regards, >>> Bill Miranda >>> bill.mira...@gmail.com >>> >>> On Jul 12, 2021, at 6:18 AM, Brian Brindle wrote: >>> >>> >>> HI Bill, >>> >>> The divergence from systemd is frustrating but at last current versions >>> of Raspian still have ifconfig... >>> >>> I'm using Raspian 10 here are my quick and dirty hints: >>> >>> Get your termcap sorted: >>> https://zork.net/~octal/mod100.xhtml >>> >>> You will note that termcap doesn't exist like it should though, so save >>> the cap to a file and install it like so: >>> >>> tic >>> >>> I assume you are going to to the easy route and use a USB to serial >>> adapter. You can use the onboard UART with some level conversion as I have >>> done, but you have to get creative with the hardware. Check out the photos >>> of my M100 hooked to my pi zero here: http://niedobry.com/mod100/tanpi/ >>> >>> Copy the template file */lib/systemd/system/**serial-getty@.service* to* >>> /etc/systemd/system/serial-getty@ttyUSB0.service*(Provided you are >>> using ttyUSB0) >>> >>> In [Service] modify the ExecStart line to say the following: (Adjust >>> your baud as you like.) >>> ExecStart=-/sbin/agetty -o '-p -- \\u' 19200 %I trs100 >>> >>> Issue *systemctl enable serial-getty@ttyUSB0.service* >>> >>> Do a ps -ax | grep getty and you should now see a getty process running >>> on the USB port. >>> >>> Connect your Model-T with a null modem cable to the serial port, set >>> your TERM to STAT 98N1E and you should be good to go. Lots and lots of >>> customization needed for it to be useful, I'm working on getting my notes >>> together on this and hope to have it somewhere for reference soon. >>> >>> Hope this helps, >>> Brian >>> >>> >>> On Sun, Jul 11, 2021 at 11:09 PM Bill Miranda >>> wrote: >>> Can anyone point me to current instructions on how to configure a Raspberry Pi so that I can connect my M100 as a serial console? I found numerous websites with instructions for older versions of Raspian which were pre-systemd. I was able to get the M100 to connect to the Pi after a lot
Re: [M100] A decent replacement for M100 "Feet"
>> That is strange. Remember, UR2 works with a real tpdd which has no such thing as a current directory label, and as well, the whole point of the UR2 stub on-demand loader is that you don't have TS-DOS installed, either ram or rom. I'm probably not articulating what I'm trying to say right, it's sometimes impossible for me to talk without a whiteboard. I'd explain why, but we'd need a whiteboard. Here is the behavior I have observed: TS-DOS seems to always use M1, or at least does when loading a directory anyway. UR2 does not when asking for DOS100.CO. (Working Dev) UR2: RX: 5A 5A 07 00 F8 0D - ZZ TX: 12 01 00 EC 0D 0A 3E 20 - > RX: 5A 5A 00 1A 44 4F 53 31 30 30 2E 43 4F 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 46 00 - ZZ..DOS100.CO F TX: 11 1C 44 4F 53 31 30 30 2E 43 4F 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 46 FF FF 9D - DOS100.CO F RX: 5A 5A 01 01 03 FA - ZZ TX: 12 01 00 EC RX: 5A 5A 03 00 FC - TS-DOS: RX: 4D 31 0D 5A 5A 08 00 F7 0D - M1 ZZ TX: 12 0B 00 52 4F 4F 54 20 20 2E 3C 3E 20 96 - ROOT <> RX: 0D 4D 31 0D 5A 5A 07 00 F8 - M1 ZZ TX: 12 01 00 EC RX: 4D 31 0D 5A 5A 08 00 F7 0D - M1 ZZ TX: 12 0B 00 52 4F 4F 54 20 20 2E 3C 3E 20 96 - ROOT <> RX: 0D 4D 31 0D 5A 5A 07 00 F8 - M1 ZZ TX: 12 01 00 EC RX: 5A 5A 08 00 F7 - ZZ TX: 12 0B 00 52 4F 4F 54 20 20 2E 3C 3E 20 96 - ROOT <> RX: 5A 5A 00 1A 44 4F 53 31 30 30 2E 43 4F 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 46 00 - ZZ DOS100.CO F TX: 11 1C 44 4F 53 31 30 30 2E 43 4F 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 46 FF FF 9D - DOS100.C0 F So, in my playing it looks like when you swap back to TS-DOS, load a directory it runs the PDDuino through the M1 routine, sets the dmeLabel then when you flip to the UR2, do the load DOS it takes the ZZ DOS100.CO F without any issue. Do just the ZZ DOS100.CO F without dmeLabel set it just looks at you. - Brian On Mon, Jul 12, 2021 at 11:26 PM Brian White wrote: > > > bkw > > On Mon, Jul 12, 2021, 9:48 PM Brian Brindle wrote: > >> >> >> On Mon, Jul 12, 2021 at 5:34 PM Brian K. White >> wrote: >> >>> >>> >>> master actually? or latest default branch which is not master but 0.4.1? >>> I didn't have master marked as default currently because I thought I had >>> made it worse, you know like the partly-broken point mid-way in a >>> refactor, so I made the last-known at least basically-minimally-working >>> version default. >>> >>> But if you're actually using the master branch that's great and I'll >>> switch that to default. That is where I started porting Jim's main loop. >>> >> >> I'm using the Master. I had a lot of issues with the current default. >> Granted I didn't improve my situation by mucking with it, but I stumbled on >> the Master, saw the changes you made and liked them so went with it. It's >> been working pretty well since. >> >> Biggest thing I saw was the PDDuino would wander off looking for >> >>> > label information and not respond to drive commands. Like when trying >>> to >>> > load TS-DOS from the UR2 it would fail unless you could force the >>> > PDDuino to get a disk label, IE: swap to TS-DOS rom, list a directory, >>> > then it would happily go on to the load step. It is somewhat working >>> now >>> > so I took a break from it, although my M0 still doesn't work and I'm >>> not >>> > 100% sure why but I think it's the guy from SdFats fault.. >>> >>> I'd love to know the fix for that. I wrote a whole paragraph in the >>> front page readme about it just as a bug description to be figured out >>> sometime. >>> >> >> I did a lot of debugging on this, both with a serial monitor and with the >> debug options on the pdduino. I came to the conclusion that it had >> something to do with dmeLabel not getting set. When watching the >> interactions it looked like the UR2 just does a ZZ - ZZ DOS100.CO and >> that's it. TS-DOS did a little dance that gave it the root dir first and >> set dmeLabel. >> > > > That is strange. Remember, UR2 works with a real tpdd which has no such > thing as a current directory label, and as well, the whole point of the UR2 > stub on-demand loader is that you don't have TS-DOS installed, either ram > or rom. > > Ken Pettit has a TS-DOS disassembly in his directory on club100 that we > can consult too when it comes to nailing down a real mystery. > > Maybe it's something where IF the server says it supports directory > extensions (by acknowledging one of the commands that should be unknown to > a real tpdd), THEN the label must actually be supplied at various times, > and I'm missing some. > > We had discussed here not too long ago the idea of having a tpdd server at > least have an option to treat some filenames specially, like having > DOS100.CO always work regardless of current directory. It sounds pretty > sensible to me, but if the UR2 loader always cds to root first, then that > means there is no point. > > That would also mean the root label is not free to be whatever I think it > should be, but has to be whatever UR2 cds to or looks
