Jump to content
jedimatt42

TIPI Usage and Support

Recommended Posts

On 9/18/2021 at 6:32 PM, J-Data said:

This may be a dumb question, but what’s the downside of setting the TIPI CRUBASE to >1000?  I had assumed this was the better choice so it wouldn’t conflict with a real disk controller.

There are programs that expect the CALL FILES VDP buffer management routine to work. TIPI doesn't need VDP sector buffers so it only manages that if the crubase is >1100. This provides compatibility with the most programs.

 

The number is small, typically hybrid XB bitmap graphics apps, "The Missing Link" to name one.

 

It also prevents the TIPI generation from creating large, run of the mill XB programs that are too big to fit if a real disk controller is present.

 

 

  • Like 3

Share this post


Link to post
Share on other sites
On 9/19/2021 at 11:51 PM, jedimatt42 said:

There are programs that expect the CALL FILES VDP buffer management routine to work. TIPI doesn't need VDP sector buffers so it only manages that if the crubase is >1100. This provides compatibility with the most programs.

Understood, I'll update the TIPI/32K combo Wiki and start making mine with the first jumper populated. 

  • Like 2

Share this post


Link to post
Share on other sites

Can I access any of the TIpi troubleshooting logs from the TIpi (TI basic) menu? 

And is their any way to look at TIpi logs without removing the raspberry SD card? 

I have not seen how to get to logs on the forum.

 

Edited by GDMike

Share this post


Link to post
Share on other sites
Can I access any of the TIpi troubleshooting logs from the TIpi (TI basic) menu? 
And is their any way to look at TIpi logs without removing the raspberry SD card? 
I have not seen how to get to logs on the forum.
 
Easiest way is the web browser
Tipi:9900

Sent from my LM-V600 using Tapatalk

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites
8 minutes ago, arcadeshopper said:

Easiest way is the web browser
Tipi:9900

Sent from my LM-V600 using Tapatalk
 

Thank you

Share this post


Link to post
Share on other sites

I telnet into my PI and navigate to the logs file from my Windows PC.  Then, with either the tipi.log file or the daemon.log file (I think those names are correct), I can click on the file and open it in notepad.  There are some other log files as well, but I think those are the only two you might really need to review in most cases.

 

The tipi.log file contains a lot of useful information on the blocks/records and file formats  as things are opened, read/written, and closed.  Matt did exceptionally well with his reporting in the log file.

 

On the TI for file saving, if the file open/read/write/close works on regular devices, highly unlikely you will encounter a problem with file i/o.  I do know during the Geneve development cycle with the tipi, @InsaneMultitasker and myself caught a couple of very unique cases of issues in the file i/o Matt resolved as we pushed the TIPI further than what previous developers had done with the 4A.

 

Now, when you start doing socket access testing for characters/strings, now, you will get some very long log files as each time you scan for a character/string, you get a line entry in the log file.  Those files grow very large very quickly if your code is testing the socket multiple times per second.

 

Beery

 

  • Like 1

Share this post


Link to post
Share on other sites
41 minutes ago, 9640News said:

I telnet into my PI and navigate to the logs file from my Windows PC.  Then, with either the tipi.log file or the daemon.log file (I think those names are correct), I can click on the file and open it in notepad.  There are some other log files as well, but I think those are the only two you might really need to review in most cases.

 

The tipi.log file contains a lot of useful information on the blocks/records and file formats  as things are opened, read/written, and closed.  Matt did exceptionally well with his reporting in the log file.

 

On the TI for file saving, if the file open/read/write/close works on regular devices, highly unlikely you will encounter a problem with file i/o.  I do know during the Geneve development cycle with the tipi, @InsaneMultitasker and myself caught a couple of very unique cases of issues in the file i/o Matt resolved as we pushed the TIPI further than what previous developers had done with the 4A.

 

Now, when you start doing socket access testing for characters/strings, now, you will get some very long log files as each time you scan for a character/string, you get a line entry in the log file.  Those files grow very large very quickly if your code is testing the socket multiple times per second.

 

Beery

 

I'm just trying to determine where I'm failing in my Foxit program at which time I'm creating a file and I error,hang in DSRLNK on TIpi write to DSK4.TESTDB on real hardware with no disk controller card. BUT DOES work in my SNP program.

Foxit has no error  using classic 99 using and a FIAD setting.

My log from TIpi is over on Foxit post 

Edited by GDMike

Share this post


Link to post
Share on other sites
4 hours ago, GDMike said:

Can I access any of the TIpi troubleshooting logs from the TIpi (TI basic) menu? 

And is their any way to look at TIpi logs without removing the raspberry SD card? 

I have not seen how to get to logs on the forum.

 

That is because the documentation for TIPI is not on the forum, it is here on Github, as described in POST #1: https://github.com/jedimatt42/tipi/wiki

 

If you remove the SD card, you will not find the logs on it... the logs are setup to use a ramdisk so that your SDcard doesn't wear out. 

 

specifically regarding logs: https://github.com/jedimatt42/tipi/wiki/Troubleshooting

  • Like 3

Share this post


Link to post
Share on other sites

A couple of observations on file functions with TIPI and XB.

  • The defaults do not seem to be implemented. For example, OPEN #1:"TIPI.TEST", INPUT does not default to DV80,SEQUENTIAL. These have to be specified.
  • When opening an existing TIPI file for OUTPUT, it is not overwritten by the new data, again not the expected behavior. EDIT: This actually happens, but only after the file is explicitly closed (normally XB will automatically close all open files when an abnormal termination is encountered, but this is not happening with TIPI files for some reason).

 

  • Like 2

Share this post


Link to post
Share on other sites

Just a common sense note for the time.

 

For the first time, the price of a Raspberry Pi single-board computer is increasing and we have the global supply chain shortages to thank for it.

 

Eben Upton, chief executive of Raspberry Pi Trading, made the announcement today, but also made it clear the price increase is only temporary and only impacts one model of the Raspberry Pi 

 

In February last year, the price of the Raspberry Pi 4 2GB dropped from $45 to $35 "permanently" and the 1GB model was discontinued. The 2GB model is reverting back to $45 and the 1GB model is making a comeback for industrial customers at its previous $35 price. The reason for this is one of supply chain challenges, with Upton confirming they will only manage to match 2020's shipments of around seven million units this year. The main shortages have been for the Raspberry Pi Zero and Raspberry Pi 4 2GB.4. time.

Edited by GDMike

Share this post


Link to post
Share on other sites
8 hours ago, Vorticon said:

A couple of observations on file functions with TIPI and XB.

  • The defaults do not seem to be implemented. For example, OPEN #1:"TIPI.TEST", INPUT does not default to DV80,SEQUENTIAL. These have to be specified.
  • When opening an existing TIPI file for OUTPUT, it is not overwritten by the new data, again not the expected behavior. EDIT: This actually happens, but only after the file is explicitly closed (normally XB will automatically close all open files when an abnormal termination is encountered, but this is not happening with TIPI files for some reason).

 

TIPI only writes on close or delete for record based access... This is on purpose. I am not inclined to change that unless it is a real problem...

 

As for the defaults.. I am surprised. I would have thought BASIC was responsible for creating a fully intentional PAB.  I'll take a look at this.

 

Ah, "Functional Specification for the 99/4 Disk Peripheral" section 4.1.4 backs you up.

  • Like 2

Share this post


Link to post
Share on other sites
33 minutes ago, jedimatt42 said:

TIPI only writes on close or delete for record based access... This is on purpose. I am not inclined to change that unless it is a real problem...

It's not a problem as long as the user ensures a CLOSE statement made prior to exiting the program. Common sense but I have forgotten to do that on many occasions but XB took care of that for me anyway...

  • Like 3
  • Thanks 1

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.
Note: Your post will require moderator approval before it will be visible.

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...