Jump to content
jedimatt42

TIPI - TI-99/4A to Raspberry PI interface development

Recommended Posts

The question makes sense, but I have no idea what the answer is.

 

There is buffering on the server send side. The output buffer is handed to OS TCP stack and I don't know if it is necessarily sent if the server initiates disconnect. I imagine it is, given how common that case is with http servers.

 

Then there is buffering in the receiving computers TCP stack.

 

Often higher level programming languages end up adding another layer of buffering.

 

[email protected]

Share this post


Link to post
Share on other sites

 

k.

 

The update is available now. v1.40 - just changes this contract as now described on the TCP extension page of the wiki... read now returns a 0 length array if the socket is not connected. -- tested Irata.Online, Telnet, FTP...

 

Chatti, snek, and chess do not use the TCP extension, so shouldn't be impacted.

 

[email protected]

 

Hello jedimatt42,
Today I have the update on version 1.40 activated and my TI99 worked about 15 minutes on the update. I thought there is something wrong.
The TIPI card LED flashes and nothing happens.
After 15 minutes I reset my TI and as I assumed, the PI / TIPI was faulty.
The TI could not start anymore. After selecting XB in the FG99 the screen stays blue and the TIPI card is constantly lit.
Now I have restarted the PI and then turned on the TI99.
After selecting XB or TI BASIC everything seems to be OK.
But a CALL TIPI leads to blockage and the TIPI LED lights up permanently.
I think I have to create a new SD card.
Can I download the version 1.39 or 1.40 somewhere?
On your website I found only the version b29.
Greetings from Germany
Wolfgang

Share this post


Link to post
Share on other sites

I will work on an updated base-image for the SD card tonight.

 

The software change was tiny, but the update process deletes and rebuilds python environments in case an update included any new dependencies. This puts demands on the SD card.

 

I may spend some cycles making updates more context aware.

 

[email protected]

  • Like 1

Share this post


Link to post
Share on other sites

 

 

Hello jedimatt42,
Today I have the update on version 1.40 activated and my TI99 worked about 15 minutes on the update. I thought there is something wrong.
The TIPI card LED flashes and nothing happens.
After 15 minutes I reset my TI and as I assumed, the PI / TIPI was faulty.
The TI could not start anymore. After selecting XB in the FG99 the screen stays blue and the TIPI card is constantly lit.
Now I have restarted the PI and then turned on the TI99.
After selecting XB or TI BASIC everything seems to be OK.
But a CALL TIPI leads to blockage and the TIPI LED lights up permanently.
I think I have to create a new SD card.
Can I download the version 1.39 or 1.40 somewhere?
On your website I found only the version b29.
Greetings from Germany
Wolfgang

 

 

just curious, did you try the manual update process in the faq?

 

https://github.com/jedimatt42/tipi/wiki/FAQ#q-if-tipicfg-upgrade-fails-what-should-i-do

  • Like 1

Share this post


Link to post
Share on other sites

 

just curious, did you try the manual update process in the faq?

 

https://github.com/jedimatt42/tipi/wiki/FAQ#q-if-tipicfg-upgrade-fails-what-should-i-do

No, I only accepted the autoupdate displayed on the TIPICFG screen.
Maybe it had something to do with the fact that I used DM2K before the update. Sometimes, when I use the DM2K tool, I get access to the DSK1, DSK2 and DSK3 shown.
Yesterday I had DSKx drives mapped to TIPICFG, but only DSK1 displays the TIPI directory. DSK2 and DSK3 both showed the directory of physical drives in the PEB.
Then I made a new SD card with vB0.29 and update to vB0.36. Now everything works again with Beta0.36. But I will do the auto update today at 1.40.
Now I have created some images of the different TIPI versions with my configurations. So I can try the update with and without DM2K.

Share this post


Link to post
Share on other sites

No, I only accepted the autoupdate displayed on the TIPICFG screen.

 

Maybe it had something to do with the fact that I used DM2K before the update. Sometimes, when I use the DM2K tool, I get access to the DSK1, DSK2 and DSK3 shown.

Yesterday I had DSKx drives mapped to TIPICFG, but only DSK1 displays the TIPI directory. DSK2 and DSK3 both showed the directory of physical drives in the PEB.

 

Then I made a new SD card with vB0.29 and update to vB0.36. Now everything works again with Beta0.36. But I will do the auto update today at 1.40.

Now I have created some images of the different TIPI versions with my configurations. So I can try the update with and without DM2K.

Shouldn't make any difference.. If an update fails do that procedure.

 

Sent from my LM-G820 using Tapatalk

Share this post


Link to post
Share on other sites

 

Maybe it had something to do with the fact that I used DM2K before the update. Sometimes, when I use the DM2K tool, I get access to the DSK1, DSK2 and DSK3 shown.

 

Have you tried Force Command's disk copy function yet?

Share this post


Link to post
Share on other sites

Force Command doesn't have a Disk copy feature. Just files. I'm sure that is what you meant. DM2K doesn't disk copy either. (I just don't want anyone to get the wrong idea.)

 

And I expect many people use DM2K as a browse and launch tool. It excels at that.

 

[email protected]

Share this post


Link to post
Share on other sites

 

Have you tried Force Command's disk copy function yet?

Yes, copy function works very well between TIPI folders and physical disc drive.

 

But DELETE works only from the path you are currently.

 

[1000.TIPI.MM.]

$ COPY MM-X 1100.DSK2.MM-X <-- This works very well!

 

[1000.TIPI.MM.]

$ DELETE 1100.DSK2.MM-X <-- This isn't working

file not found TIPI.MM.1100.DSK2.MM-X

 

[1000.TIPI.MM.]

$ CD 1100.DSK2.

 

[1100.DSK2.]

$ DELETE MM-X <-- This is working!

 

Wolfgang

Share this post


Link to post
Share on other sites

Force Command doesn't have a Disk copy feature. Just files. I'm sure that is what you meant. DM2K doesn't disk copy either. (I just don't want anyone to get the wrong idea.)

 

And I expect many people use DM2K as a browse and launch tool. It excels at that.

 

[email protected]

 

Yes, I use DM2K to list files in my TIPI folder, and then select multiple files to copy to a physical disk.
DM2K works mostly between TIPI folders and physical drives, but sometimes I get a drive or file error,
then DM2K shows me only the physical DSK2 and DSK3 and not the mapped folder in the TIPICFG.
I think that was my problem yesterday when I tried to update tipi to 1.40 and it went awry.
Today I used some programs like REMIND ME and DM2K and everything works fine. Then I made the update to 1.40 and it works as expected. Everything is OK.

Share this post


Link to post
Share on other sites

I can't reiterate enough that your use of dm2k has absolutely nothing to do with the update

 

Sent from my LM-G820 using Tapatalk

You are right, it was not the DM2K. Maybe it was the disk error I got before. Maybe sometimes I have a problem in my PEB.

 

Today I tried the same thing and I had no problems.

  • Like 1

Share this post


Link to post
Share on other sites

The update runs entirely in the pi. Likely it had an issue with the internet and failed mid update leaving you borked until the script was rerun and succeeded. Always try this first before reimaging.

 

Sent from my LM-G820 using Tapatalk

  • Like 3

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...