+arcadeshopper Posted October 9 Share Posted October 9 5 hours ago, PeBo said: 1st, sorry for originally posting this in the development thread...hadn't noticed I had clicked through... I have a a PI3B+ connected to the TIPI PEB CALL TIPI recognizes the TIPI and allowed me to input and save my SSID and PSK. but when I CALL TIPI ("TIPI.NET.TELNET"), I get a "error connecting... press any key" which returns me to the column count selection screen. I've tried searching the forums but not sure how to word it to get meaningful assistance. I've left the CRU at the default. Other PEB installed items are Shiftt838's Speech-Synth adapted card, a SidMaster card, TI RS232, TI Flex-Cable card (duh), 1MB SAMS card, TI disc controller card and 2 internal drives. My network requires no special settings, and I've double and triple checked the SSID and PSK input. It should be noted that the TIPI has been assigned an IP and it appears in the DHCP leases in my router, assigning it a MAC address, so I really don't understand why there is a connection issues to telnet. If anyone can assist with ideas of where/what the issue may be, or point me to where to look in these forums or the Wiki for a solution, I will be forever grateful. What's it say in the TIPI log? Quote Link to comment Share on other sites More sharing options...
+dhe Posted October 10 Share Posted October 10 Both of my TIPI's went off last night do to power issues. I've tried a power reset. There wireless less from the router end seem to be the same. Yet, they won't ping, ssh or telnet. What's my easiest approach to getting these online? Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted October 10 Author Share Posted October 10 Reflash the SD card, restore your backup. 1 Quote Link to comment Share on other sites More sharing options...
PeBo Posted October 10 Share Posted October 10 18 hours ago, arcadeshopper said: What's it say in the TIPI log? Sorry, I am still in the initial installation and set-up phase, and have not explored further. TIPI log? No idea how to access that. I'm a newb still trying to expand the Root-partition of the SD card. Quote Link to comment Share on other sites More sharing options...
Gary from OPA Posted October 10 Share Posted October 10 (edited) 48 minutes ago, PeBo said: Sorry, I am still in the initial installation and set-up phase, and have not explored further. TIPI log? No idea how to access that. I'm a newb still trying to expand the Root-partition of the SD card. Expanding the root partition not really needed anymore, that was only for those on older smaller images. Edited October 10 by Gary from OPA Quote Link to comment Share on other sites More sharing options...
+dhe Posted October 10 Share Posted October 10 Feature Request: on http my tipi - show size of SD Card. 2 Quote Link to comment Share on other sites More sharing options...
+arcadeshopper Posted October 12 Share Posted October 12 On 10/10/2024 at 11:23 AM, PeBo said: Sorry, I am still in the initial installation and set-up phase, and have not explored further. TIPI log? No idea how to access that. I'm a newb still trying to expand the Root-partition of the SD card. telnet to localhost 23 on your ti with TIPI.NET.TELNET login with tipi tipi cat /var/log/tipi/tipi.log or web browser to tipi:9900 and view log in the menu 2 Quote Link to comment Share on other sites More sharing options...
Diesel419 Posted October 13 Share Posted October 13 Is it possible to rename directories on the tipi? I have noticed that any tipi directory or program name that contains a period or other special character causes an I/O error code zero Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted October 14 Author Share Posted October 14 You should be able to rename directories from the 4A with a TIPI compatible file manager, such as Force Command. But there seems to be a bug in the rename directory implementation when trying to rename SLASH/ES to SLASHES. It appears that the '/' to '.' handling is leaving garbage in a string buffer. At least on the latest versions. --- Actually I'm getting a bad filename sent to the PI. At least from Force Command. Maybe this is just a bug in my unreleased updates to Force Command... (rename operations are supposed to pad the 10 character file or dirname with spaces, as no length is submitted. Trailing spaces are then truncated for the actual filename - my unreleased Force Command that supports cpu-buffers for such operations wasn't padding on the cpu-buffer codepath) --- Special characters should be allowed in the 4A filenames. The file name on the host OS, if it has a periods, should have a '/' on the 4A side. This is the only translation done. Well, technically the byte array passed in from the 4A is converted to python string using 'latin-1' decoding. Then, any '/' in the name are replaced with '.', and then the python code tries to operate on it. Generally the linux OS will tolerate any character in a file name. Quote Link to comment Share on other sites More sharing options...
Diesel419 Posted October 14 Share Posted October 14 (edited) That's interesting, I've never used Force Command before so maybe I'll give that a try. The main reason I asked was because I noticed that when I tried to use Emuwriter 0.3 it wouldn't work but 0.2 worked fine, and the only noticable difference was that when uploaded on the web ui v0.2 came up with the directory name EMUWRITER where as v0.3 was EMUWRITER. that period seemed to be the only difference and I couldn't figure out how to get rid of it. Then I remembered that there were other programs that didn't work, all having special characters in the directory name or program name. Edited October 14 by Diesel419 Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted October 14 Author Share Posted October 14 @PeBo If you can get to the TIPI's WEB UI (http://tipi.local:9900) then the log can be seen here (when the menu isn't on the screen there is a "Go to bottom" button as newest entries are at the bottom of the log. If you cannot get to the WEB UI, you should go into TI BASIC, and run CALL TIPI with no arguments. This should load the config tool, and that should display the PI's IP address. I think the original problem/goal was that the TELNET client isn't connecting to some BBS or other host you are trying to go to... The connection attempts should be evidenced in the tipi.log. Quote Link to comment Share on other sites More sharing options...
Nightengale Posted October 14 Share Posted October 14 Here's the log when i try to telnet localhost 23 2024-10-13 23:54:22,085 TipiService : INFO TIPI Ready 2024-10-13 23:54:52,393 TipiDisk : INFO Opcode 5 LOAD - TIPI.NET.TELNET 2024-10-13 23:54:52,394 Pab : INFO opcode: Load, fileType: Sequential, mode: Update, dataType: Display, recordType: Fixed, recordLength: 0, recordNumber: 8198 2024-10-13 23:54:52,396 TipiDisk : INFO LOAD image size 8192 2024-10-13 23:54:54,006 TipiService : INFO Request completed. 2024-10-13 23:54:54,220 TipiDisk : INFO Opcode 5 LOAD - TIPI.NET.TELNEU 2024-10-13 23:54:54,221 Pab : INFO opcode: Load, fileType: Sequential, mode: Update, dataType: Display, recordType: Fixed, recordLength: 0, recordNumber: 8198 2024-10-13 23:54:54,223 TipiDisk : INFO LOAD image size 5120 2024-10-13 23:54:55,210 TipiService : INFO Request completed. 2024-10-13 23:55:03,643 TiSocket : INFO open socket(0) localhost:23 2024-10-13 23:55:03,647 TiSocket : INFO failed to connect socket: 0 2024-10-13 23:55:03,647 TiSocket : INFO closing socket 1 Quote Link to comment Share on other sites More sharing options...
+arcadeshopper Posted October 14 Share Posted October 14 7 hours ago, Nightengale said: Here's the log when i try to telnet localhost 23 2024-10-13 23:54:22,085 TipiService : INFO TIPI Ready 2024-10-13 23:54:52,393 TipiDisk : INFO Opcode 5 LOAD - TIPI.NET.TELNET 2024-10-13 23:54:52,394 Pab : INFO opcode: Load, fileType: Sequential, mode: Update, dataType: Display, recordType: Fixed, recordLength: 0, recordNumber: 8198 2024-10-13 23:54:52,396 TipiDisk : INFO LOAD image size 8192 2024-10-13 23:54:54,006 TipiService : INFO Request completed. 2024-10-13 23:54:54,220 TipiDisk : INFO Opcode 5 LOAD - TIPI.NET.TELNEU 2024-10-13 23:54:54,221 Pab : INFO opcode: Load, fileType: Sequential, mode: Update, dataType: Display, recordType: Fixed, recordLength: 0, recordNumber: 8198 2024-10-13 23:54:54,223 TipiDisk : INFO LOAD image size 5120 2024-10-13 23:54:55,210 TipiService : INFO Request completed. 2024-10-13 23:55:03,643 TiSocket : INFO open socket(0) localhost:23 2024-10-13 23:55:03,647 TiSocket : INFO failed to connect socket: 0 2024-10-13 23:55:03,647 TiSocket : INFO closing socket what versions are you running? maybe post a pic of tipicfg screen? have you made any changes to the pi linux config? Quote Link to comment Share on other sites More sharing options...
Nightengale Posted October 14 Share Posted October 14 Ok, when get a sec, yardwork and wife calls. I did get smb working correctly so now mapped to T drive in windows. Just rtm worked Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted October 16 Author Share Posted October 16 The log looks healthy. I wonder if an upstream package broke telnet. What about other telnet hosts? Quote Link to comment Share on other sites More sharing options...
PeBo Posted October 17 Share Posted October 17 On 10/13/2024 at 9:37 PM, jedimatt42 said: @PeBo If you can get to the TIPI's WEB UI (http://tipi.local:9900) then the log can be seen here (when the menu isn't on the screen there is a "Go to bottom" button as newest entries are at the bottom of the log. If you cannot get to the WEB UI, you should go into TI BASIC, and run CALL TIPI with no arguments. This should load the config tool, and that should display the PI's IP address. I think the original problem/goal was that the TELNET client isn't connecting to some BBS or other host you are trying to go to... The connection attempts should be evidenced in the tipi.log. Got into the Web UI a couple days ago, and felt most of my concerns were addressed. At least I understood things better than sequential reading of the instructions was allowing in my geriatric brain. THEN... Decided to install the PI in a case, and somehow messed things up (story of my life). Now the PI powers up, but doesn't post (no green light) so I have created a problem where there wasn't one...I'll have to figure this new problem out before I can proceed further, but thank you for the assist. It is appreciated far more than you know. If anyone can think of a reason why a case (and heatsinks) installation could affect the PI posting, please let me know. (doesn't post anymore if I now remove it from the case, so I messed up something fierce). I really should take up drinking as a new hobby. I am less likely to screw it up. (I'm thinking maybe I should re-burn the image to the SD, although I'm not sure how I might have corrupted it with a case installation.) But for now, I'm thinking about ANYTHING else. Quote Link to comment Share on other sites More sharing options...
tuf Posted October 17 Share Posted October 17 Time to update? Version: 2.17 Release Date: 2021-01-09 Quote Link to comment Share on other sites More sharing options...
PeBo Posted October 17 Share Posted October 17 2 hours ago, PeBo said: Got into the Web UI a couple days ago, and felt most of my concerns were addressed. At least I understood things better than sequential reading of the instructions was allowing in my geriatric brain. THEN... Decided to install the PI in a case, and somehow messed things up (story of my life). Now the PI powers up, but doesn't post (no green light) so I have created a problem where there wasn't one...I'll have to figure this new problem out before I can proceed further, but thank you for the assist. It is appreciated far more than you know. If anyone can think of a reason why a case (and heatsinks) installation could affect the PI posting, please let me know. (doesn't post anymore if I now remove it from the case, so I messed up something fierce). I really should take up drinking as a new hobby. I am less likely to screw it up. (I'm thinking maybe I should re-burn the image to the SD, although I'm not sure how I might have corrupted it with a case installation.) But for now, I'm thinking about ANYTHING else. looks like I corrupted the SD card... reads as 121MB under the Linux "Disks" app (a 32GB card). Partition seems unrepairable by the app I'll try terminal. if everything fails, I'll pick up a new sd card this aft. Hopefully the problem is the SD & I didn't fry-the-PI. (Winter-heating static is a bitch..even with a copper grounding bracelet.) If I didn't have hassles with simple tasks, it wouldn't be as much fun (or so I keep telling myself). Quote Link to comment Share on other sites More sharing options...
Nightengale Posted October 17 Share Posted October 17 On 10/15/2024 at 9:09 PM, jedimatt42 said: The log looks healthy. I wonder if an upstream package broke telnet. What about other telnet hosts? TGIF!!! 024-10-17 15:47:39,806 TipiService : INFO physical mode enabled 2024-10-17 15:47:39,820 TipiService : INFO TIPI Ready 2024-10-17 15:48:01,775 TipiDisk : INFO Opcode 5 LOAD - TIPI.NET.TELNET 2024-10-17 15:48:01,776 Pab : INFO opcode: Load, fileType: Sequential, mode: Update, dataType: Display, recordType: Fixed, recordLength: 0, recordNumber: 8198 2024-10-17 15:48:01,778 TipiDisk : INFO LOAD image size 8192 2024-10-17 15:48:03,368 TipiService : INFO Request completed. 2024-10-17 15:48:03,582 TipiDisk : INFO Opcode 5 LOAD - TIPI.NET.TELNEU 2024-10-17 15:48:03,582 Pab : INFO opcode: Load, fileType: Sequential, mode: Update, dataType: Display, recordType: Fixed, recordLength: 0, recordNumber: 8198 2024-10-17 15:48:03,584 TipiDisk : INFO LOAD image size 5120 2024-10-17 15:48:04,564 TipiService : INFO Request completed. 2024-10-17 15:48:29,192 TiSocket : INFO open socket(0) localhost:23 2024-10-17 15:48:29,197 TiSocket : INFO failed to connect socket: 0 2024-10-17 15:48:29,198 TiSocket : INFO closing socket 2024-10-17 15:48:34,858 TipiService : INFO physical mode enabled 2024-10-17 15:48:34,871 TipiService : INFO TIPI Ready 2024-10-17 15:48:39,791 TipiService : INFO physical mode enabled 2024-10-17 15:48:39,803 TipiService : INFO TIPI Ready 2024-10-17 15:48:53,850 TipiDisk : INFO Opcode 5 LOAD - TIPI.NET.TELNET 2024-10-17 15:48:53,850 Pab : INFO opcode: Load, fileType: Sequential, mode: Update, dataType: Display, recordType: Fixed, recordLength: 0, recordNumber: 8198 2024-10-17 15:48:53,853 TipiDisk : INFO LOAD image size 8192 2024-10-17 15:48:55,439 TipiService : INFO Request completed. 2024-10-17 15:48:55,654 TipiDisk : INFO Opcode 5 LOAD - TIPI.NET.TELNEU 2024-10-17 15:48:55,654 Pab : INFO opcode: Load, fileType: Sequential, mode: Update, dataType: Display, recordType: Fixed, recordLength: 0, recordNumber: 8198 2024-10-17 15:48:55,656 TipiDisk : INFO LOAD image size 5120 2024-10-17 15:48:56,636 TipiService : INFO Request completed. 2024-10-17 15:49:04,474 TiSocket : INFO open socket(0) THEKEEP.NET:9918 2024-10-17 15:49:04,636 TiSocket : INFO connected 2024-10-17 15:49:07,935 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:08,030 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:08,106 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:08,211 TiSocket : INFO read 5 bytes from 0 2024-10-17 15:49:08,327 TiSocket : INFO read 11 bytes from 0 2024-10-17 15:49:08,390 TiSocket : INFO read 23 bytes from 0 2024-10-17 15:49:08,469 TiSocket : INFO read 2 bytes from 0 2024-10-17 15:49:08,738 TiSocket : INFO read 24 bytes from 0 2024-10-17 15:49:08,796 TiSocket : INFO read 8 bytes from 0 2024-10-17 15:49:08,865 TiSocket : INFO read 2 bytes from 0 2024-10-17 15:49:08,932 TiSocket : INFO read 14 bytes from 0 2024-10-17 15:49:09,024 TiSocket : INFO read 2 bytes from 0 2024-10-17 15:49:09,415 TiSocket : INFO read 10 bytes from 0 2024-10-17 15:49:11,004 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:11,239 TiSocket : INFO read 47 bytes from 0 2024-10-17 15:49:11,391 TiSocket : INFO read 8 bytes from 0 2024-10-17 15:49:11,920 TiSocket : INFO read 14 bytes from 0 2024-10-17 15:49:12,884 TiSocket : INFO read 36 bytes from 0 2024-10-17 15:49:13,025 TiSocket : INFO read 30 bytes from 0 2024-10-17 15:49:13,054 TiSocket : INFO read 16 bytes from 0 2024-10-17 15:49:13,109 TiSocket : INFO read 10 bytes from 0 2024-10-17 15:49:13,160 TiSocket : INFO read 5 bytes from 0 2024-10-17 15:49:13,210 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:13,262 TiSocket : INFO read 13 bytes from 0 2024-10-17 15:49:13,321 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:13,376 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:13,438 TiSocket : INFO read 13 bytes from 0 2024-10-17 15:49:13,494 TiSocket : INFO read 15 bytes from 0 2024-10-17 15:49:13,550 TiSocket : INFO read 17 bytes from 0 2024-10-17 15:49:13,609 TiSocket : INFO read 17 bytes from 0 2024-10-17 15:49:13,663 TiSocket : INFO read 9 bytes from 0 2024-10-17 15:49:13,729 TiSocket : INFO read 16 bytes from 0 2024-10-17 15:49:13,862 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:13,938 TiSocket : INFO read 31 bytes from 0 2024-10-17 15:49:13,993 TiSocket : INFO read 6 bytes from 0 2024-10-17 15:49:14,052 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:14,110 TiSocket : INFO read 10 bytes from 0 2024-10-17 15:49:14,164 TiSocket : INFO read 16 bytes from 0 2024-10-17 15:49:14,214 TiSocket : INFO read 16 bytes from 0 2024-10-17 15:49:14,270 TiSocket : INFO read 15 bytes from 0 2024-10-17 15:49:14,323 TiSocket : INFO read 7 bytes from 0 2024-10-17 15:49:14,383 TiSocket : INFO read 15 bytes from 0 2024-10-17 15:49:14,439 TiSocket : INFO read 11 bytes from 0 2024-10-17 15:49:14,515 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:14,578 TiSocket : INFO read 18 bytes from 0 2024-10-17 15:49:14,646 TiSocket : INFO read 18 bytes from 0 2024-10-17 15:49:14,703 TiSocket : INFO read 12 bytes from 0 2024-10-17 15:49:14,761 TiSocket : INFO read 16 bytes from 0 2024-10-17 15:49:14,822 TiSocket : INFO read 11 bytes from 0 2024-10-17 15:49:14,883 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:14,945 TiSocket : INFO read 4 bytes from 0 2024-10-17 15:49:15,003 TiSocket : INFO read 18 bytes from 0 2024-10-17 15:49:15,054 TiSocket : INFO read 16 bytes from 0 2024-10-17 15:49:15,109 TiSocket : INFO read 15 bytes from 0 2024-10-17 15:49:15,169 TiSocket : INFO read 17 bytes from 0 2024-10-17 15:49:15,223 TiSocket : INFO read 9 bytes from 0 2024-10-17 15:49:15,275 TiSocket : INFO read 12 bytes from 0 2024-10-17 15:49:15,357 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:15,409 TiSocket : INFO read 13 bytes from 0 2024-10-17 15:49:15,472 TiSocket : INFO read 16 bytes from 0 2024-10-17 15:49:15,530 TiSocket : INFO read 2 bytes from 0 2024-10-17 15:49:15,590 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:15,652 TiSocket : INFO read 13 bytes from 0 2024-10-17 15:49:15,704 TiSocket : INFO read 18 bytes from 0 2024-10-17 15:49:15,761 TiSocket : INFO read 16 bytes from 0 2024-10-17 15:49:15,823 TiSocket : INFO read 18 bytes from 0 2024-10-17 15:49:15,878 TiSocket : INFO read 7 bytes from 0 2024-10-17 15:49:15,934 TiSocket : INFO read 15 bytes from 0 2024-10-17 15:49:16,002 TiSocket : INFO read 5 bytes from 0 2024-10-17 15:49:16,056 TiSocket : INFO read 4 bytes from 0 2024-10-17 15:49:16,123 TiSocket : INFO read 17 bytes from 0 2024-10-17 15:49:16,177 TiSocket : INFO read 18 bytes from 0 2024-10-17 15:49:16,231 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:16,290 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:16,345 TiSocket : INFO read 9 bytes from 0 2024-10-17 15:49:16,405 TiSocket : INFO read 18 bytes from 0 2024-10-17 15:49:16,463 TiSocket : INFO read 15 bytes from 0 2024-10-17 15:49:16,530 TiSocket : INFO read 22 bytes from 0 2024-10-17 15:49:16,585 TiSocket : INFO read 12 bytes from 0 2024-10-17 15:49:16,635 TiSocket : INFO read 9 bytes from 0 2024-10-17 15:49:16,690 TiSocket : INFO read 4 bytes from 0 2024-10-17 15:49:16,750 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:16,804 TiSocket : INFO read 10 bytes from 0 2024-10-17 15:49:16,871 TiSocket : INFO read 15 bytes from 0 2024-10-17 15:49:16,935 TiSocket : INFO read 19 bytes from 0 2024-10-17 15:49:17,006 TiSocket : INFO read 8 bytes from 0 2024-10-17 15:49:17,075 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:17,137 TiSocket : INFO read 16 bytes from 0 2024-10-17 15:49:17,213 TiSocket : INFO read 19 bytes from 0 2024-10-17 15:49:17,269 TiSocket : INFO read 18 bytes from 0 2024-10-17 15:49:17,327 TiSocket : INFO read 16 bytes from 0 2024-10-17 15:49:17,378 TiSocket : INFO read 9 bytes from 0 2024-10-17 15:49:17,443 TiSocket : INFO read 13 bytes from 0 2024-10-17 15:49:17,529 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:17,584 TiSocket : INFO read 16 bytes from 0 2024-10-17 15:49:17,650 TiSocket : INFO read 16 bytes from 0 2024-10-17 15:49:17,711 TiSocket : INFO read 19 bytes from 0 2024-10-17 15:49:17,868 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:17,934 TiSocket : INFO read 25 bytes from 0 2024-10-17 15:49:17,995 TiSocket : INFO read 19 bytes from 0 2024-10-17 15:49:18,055 TiSocket : INFO read 17 bytes from 0 2024-10-17 15:49:18,113 TiSocket : INFO read 14 bytes from 0 2024-10-17 15:49:18,169 TiSocket : INFO read 13 bytes from 0 2024-10-17 15:49:18,234 TiSocket : INFO read 1 bytes from 0 2024-10-17 15:49:18,293 TiSocket : INFO read 7 bytes from 0 2024-10-17 15:49:19,866 TipiService : INFO physical mode enabled 2024-10-17 15:49:19,878 TipiService : INFO TIPI Ready @arcadeshopper About TIPI TIPI software version info: Version: 4.3 Release Date: 2024-06-30 Source Branch: bookworm_release Changes to linux - not that I am aware of Not too terribly worried about it, it's just an oddity. don't care if I need to re-image etc, but I probably won't Quote Link to comment Share on other sites More sharing options...
+arcadeshopper Posted October 18 Share Posted October 18 if you can ssh in to the pi Edit /etc/inetd.conf and verify line 23 (line number is just a co-incidence) is uncommented Code: Select all #:STANDARD: These are standard services. telnet stream tcp nowait root /usr/sbin/tcpd /usr/sbin/telnetd Quote Link to comment Share on other sites More sharing options...
Nightengale Posted October 19 Share Posted October 19 On 10/17/2024 at 5:37 PM, arcadeshopper said: if you can ssh in to the pi Edit /etc/inetd.conf and verify line 23 (line number is just a co-incidence) is uncommented Code: Select all #:STANDARD: These are standard services. telnet stream tcp nowait root /usr/sbin/tcpd /usr/sbin/telnetd Thanks Greg, localhost port 23 replies connected, but hangs. Others work. 2024-10-18 21:57:43,964 TipiService : INFO physical mode enabled 2024-10-18 21:57:43,978 TipiService : INFO TIPI Ready 2024-10-18 21:59:12,167 TipiService : INFO physical mode enabled 2024-10-18 21:59:12,181 TipiService : INFO TIPI Ready 2024-10-18 21:59:25,186 TipiDisk : INFO Opcode 5 LOAD - TIPI.NET.TELNET 2024-10-18 21:59:25,187 Pab : INFO opcode: Load, fileType: Sequential, mode: Update, dataType: Display, recordType: Fixed, recordLength: 0, recordNumber: 8198 2024-10-18 21:59:25,189 TipiDisk : INFO LOAD image size 8192 2024-10-18 21:59:26,801 TipiService : INFO Request completed. 2024-10-18 21:59:27,016 TipiDisk : INFO Opcode 5 LOAD - TIPI.NET.TELNEU 2024-10-18 21:59:27,016 Pab : INFO opcode: Load, fileType: Sequential, mode: Update, dataType: Display, recordType: Fixed, recordLength: 0, recordNumber: 8198 2024-10-18 21:59:27,018 TipiDisk : INFO LOAD image size 5120 2024-10-18 21:59:28,009 TipiService : INFO Request completed. 2024-10-18 21:59:33,249 TiSocket : INFO open socket(0) localhost:23 2024-10-18 21:59:33,254 TiSocket : INFO connected 2024-10-18 21:59:33,583 TiSocket : INFO read 21 bytes from 0 2024-10-18 22:00:41,304 TipiService : INFO physical mode enabled 2024-10-18 22:00:41,316 TipiService : INFO TIPI Ready 2024-10-18 22:00:53,648 TipiDisk : INFO Opcode 5 LOAD - TIPI.NET.TELNET 2024-10-18 22:00:53,649 Pab : INFO opcode: Load, fileType: Sequential, mode: Update, dataType: Display, recordType: Fixed, recordLength: 0, recordNumber: 8198 2024-10-18 22:00:53,651 TipiDisk : INFO LOAD image size 8192 2024-10-18 22:00:55,239 TipiService : INFO Request completed. 2024-10-18 22:00:55,453 TipiDisk : INFO Opcode 5 LOAD - TIPI.NET.TELNEU 2024-10-18 22:00:55,454 Pab : INFO opcode: Load, fileType: Sequential, mode: Update, dataType: Display, recordType: Fixed, recordLength: 0, recordNumber: 8198 2024-10-18 22:00:55,456 TipiDisk : INFO LOAD image size 5120 2024-10-18 22:00:56,444 TipiService : INFO Request completed. 2024-10-18 22:01:03,215 TiSocket : INFO open socket(0) thekeep.net:9918 2024-10-18 22:01:03,414 TiSocket : INFO connected 2024-10-18 22:01:05,060 TiSocket : INFO read 1 bytes from 0 2024-10-18 22:01:05,321 TiSocket : INFO read 7 bytes from 0 2024-10-18 22:01:05,674 TiSocket : INFO read 36 bytes from 0 2024-10-18 22:01:05,965 TiSocket : INFO read 32 bytes from 0 Quote Link to comment Share on other sites More sharing options...
+dhe Posted October 19 Share Posted October 19 Does the size of your SD Card effect the TI "Drive" side of TIPI? Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted October 20 Author Share Posted October 20 6 hours ago, dhe said: Does the size of your SD Card effect the TI "Drive" side of TIPI? Nope. There is a config item somewhere in the PI.CONFIG that lets you control what is reported as free sectors. Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted October 20 Author Share Posted October 20 The instructions I use to install the local telnetd on the PI are here: https://github.com/jedimatt42/tipi/blob/main/INSTALL.md#other-items-to-setup That may help repairing the telnet server. 1 Quote Link to comment Share on other sites More sharing options...
+dhe Posted October 20 Share Posted October 20 https://github.com/jedimatt42/tipi/wiki/BASIC-CALLs Any chance of a TCAT("DEVICE_NAME") ?? There are certain times, when you have something in the GROM port, and it's helpful to be able to list a directory. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.