TIPI Usage and Support

[+RXB]

On 10/5/2023 at 5:34 AM, mizapf said:

As you see, it's somewhere above 12000 bytes where Extended Basic switches to this alternative save format. You may keep the PROGRAM format for another while when you use CALL FILES(1). In that case, the number of simultaneously open files is limited to 1 (instead of the default 3), which frees some more space, but which also means you have to do this CALL FILES each time you try to load the program again.

Hnmm RXB 2023 can save any program as IV254 as long as it would  take up 3 sectors on disk. i.e. SAVE DSK3.TESTFILE,IV254 or OLD DSK3.TESTFILE,IV254

The test for size of file is still done automatically but the IV254 can override the default and should even work on CASSETTE like SAVE CS1,IV254 or OLD CS1,IV254

[+arcadeshopper]

5 hours ago, hloberg said:

what are some of the URI settings you TIPI users have set.

I want to add some to my TIPI and a new section  (someday) of TI99resources for TIPI and related items.

https://myti99.com/

https://ftp.whtech.com/TIPI/

https://ti99.irata.online/

 

[+jedimatt42]

On 11/11/2023 at 10:40 AM, hloberg said:

discovered that alchemy yesterday and used it a lot so far. oddly PILOT still doesn't work but doesn't lock up. instead gives error 'can't find directory' which be easier figure out later then just a lockup.

If you can point me at the PILOT materials (disks and docs) I might be able to fix something, or at least document required configuration. Sounds a bit like PILOT is using sector access which may also be assuming crubase 1100.

[+hloberg]

here's what I got. pilot works with classic99, mame & cf7. as I posted recently it mostly works now. haven't tested recent so might work right now?

 

 

Pilot.zip pilot99.pdf

[+hloberg]

unclear on this point. tipi just added drives 5-9, I can't seem to get any of my directory programs to see those drives. is there a DSR update (if possible) or am I doing something wrong.

 

[+jedimatt42]

10 hours ago, hloberg said:

unclear on this point. tipi just added drives 5-9, I can't seem to get any of my directory programs to see those drives. is there a DSR update (if possible) or am I doing something wrong.

 

There was a DSR ROM update required to enable them, released on August 4th 2023.

 

If you go into TIPICFG ( CALL TIPI ) it shows the date of the DSR ROM.

[+hloberg]

16 hours ago, jedimatt42 said:

There was a DSR ROM update required to enable them, released on August 4th 2023.

 

If you go into TIPICFG ( CALL TIPI ) it shows the date of the DSR ROM.

how do u apply the new DSR? do I need some hardware?

[GDMike]

I believe from the tipi menu and hitting ctrl V or U, I can't remember which...but that updates and installs everything for you to the latest version. (You must have internet connection).

Edited November 16 by GDMike

[+jedimatt42]

17 hours ago, hloberg said:

how do u apply the new DSR? do I need some hardware?

You need an EPROM eraser and burner. The binary is on my website downloads page. (Same place as the SD card image, just a little further down)

 

arcadeshopper.com has a store item for that. You can look at the history of DSR changes on my downloads page and decide if investing in EPROM equipment is for you. At the time of design a lot of us were using EPROM for multicarts, so eprom seemed like a fine decision. I don't have any future plans for eprom updates. 

[+jedimatt42]

4 minutes ago, GDMike said:

I believe from the tipi menu and hitting ctrl V or U, I can't remember which...but that updates and installs everything for you to the latest version. (You must have internet connection).

Nope. That doesn't update the DSR which lives in an EPROM.

[+hloberg]

57 minutes ago, jedimatt42 said:

You need an EPROM eraser and burner. The binary is on my website downloads page. (Same place as the SD card image, just a little further down)

 

arcadeshopper.com has a store item for that. You can look at the history of DSR changes on my downloads page and decide if investing in EPROM equipment is for you. At the time of design a lot of us were using EPROM for multicarts, so eprom seemed like a fine decision. I don't have any future plans for eprom updates. 

I don't see where @arcadeshopper has eprom burner for sale an more. I had an eprom burner and made a few for, something?, a while back till it stopped working (cheap China make). I would like to make a few carts BUT can you use the eprom burner with GROM? I got a few carts in mind I like to create but some have GROM.

alternative, @arcadeshopper what charge for upgrading this on or a swap DSR?

[+arcadeshopper]

https://www.arcadeshopper.com/wp/store/#!/TIPI-DSR-Rom-upgrade-service/p/104220340

 

I don't sell burners but I can upgrade your dsr for you or send you a replacement chip whichever you prefer

[+jedimatt42]

On 11/13/2023 at 7:06 AM, jedimatt42 said:

If you can point me at the PILOT materials (disks and docs) I might be able to fix something, or at least document required configuration. Sounds a bit like PILOT is using sector access which may also be assuming crubase 1100.

 

So, PILOT seems to use DSK.<volume>.<file>:<suffix> syntax for the files.   For TIPI to find your <volume> it must be the name of the directory that you map to one of the drives. 

 

So, I uploaded the PILOT_1N.dsk to tipi via the WEB-UI, it extracted to a directory named 'PILOT'   ... I selected that directory and mapped it to DSK1.  After that using XB, the LOAD program loads up the pilot compiler, and prompts to input files... I created a file on the TIPI named 'GAME:PLT' and it is read by the compiler... 

 

You can also arrow up to the DSK part and change it to DSK1 or other DSK1-4 values. And you can use a single directory name in the path part. TIPI does support directories within mapped floppy devices. 

 

It reads, starts to compile, writes a partial GAME:ASM and does write a GAME:LST file... You have to read the GAME:LST file to see what the actual errors in the compilation are. 

 

As for a functioning programming language, I get the same errors with js99er ( non-tipi emulation mode, just plain old disk images ) - The PILOT compiler doesn't like the syntax of the examples in the PDF. Even the program consisting of 1 line with:   IT:  

 

Does it work any better on a real floppy drive? I don't think the issues have anything to do with TIPI. 

 

[+jedimatt42]

2 hours ago, jedimatt42 said:

 

So, PILOT seems to use DSK.<volume>.<file>:<suffix> syntax for the files.   For TIPI to find your <volume> it must be the name of the directory that you map to one of the drives. 

 

So, I uploaded the PILOT_1N.dsk to tipi via the WEB-UI, it extracted to a directory named 'PILOT'   ... I selected that directory and mapped it to DSK1.  After that using XB, the LOAD program loads up the pilot compiler, and prompts to input files... I created a file on the TIPI named 'GAME:PLT' and it is read by the compiler... 

 

You can also arrow up to the DSK part and change it to DSK1 or other DSK1-4 values. And you can use a single directory name in the path part. TIPI does support directories within mapped floppy devices. 

 

It reads, starts to compile, writes a partial GAME:ASM and does write a GAME:LST file... You have to read the GAME:LST file to see what the actual errors in the compilation are. 

 

As for a functioning programming language, I get the same errors with js99er ( non-tipi emulation mode, just plain old disk images ) - The PILOT compiler doesn't like the syntax of the examples in the PDF. Even the program consisting of 1 line with:   IT:  

 

Does it work any better on a real floppy drive? I don't think the issues have anything to do with TIPI. 

 

 

Ok, it works in js99er... so there must be a TIPI bug...