jedimatt42

Today at 3pm Pacific. I will likely not make it. But I hope you all have fun!

There is no audio emulation in the TIPI CS1 support, TIPI catches LVL3 IO requests to device name "CS1", and directs them to the TIFILES file that you specify in the CS1_FILE entry in PI.CONFIG. See: https://github.com/jedimatt42/tipi/wiki/PI.CONFIG#cassette-file-mapping

No. I have dropped that website/domain. jedimatt42.com is my relevant website now along with GitHub.

Awesome! Yes, all physical varieties of the TIPI that I am aware of are compatible with the updated PI software. And the error makes sense given the old 2.x PI software was based on a very outdated Raspberry PI OS version.

@Rafael1138 are you a brand new install of TIPI, or a very old one? It'll make a difference in how I try to reproduce the issue...

My employer has done this motto nonsense in the past, and now we are busy at the last minute removing the motto from marketing images inside installers and login pages and login error pages, and... As an engineer, feels real productive (sarcasm)

That was clearly a missed opportunity to build real future alumni pride. Which is probably worth more money over the long term than the marketing stunt.

So, the error messages show that the http site is redirecting to an https site with an invalid certificate. @tschak909 probably needs to refresh a certificate.

Update 3.22 3.23 - 2023-09-03 - Experimental 16 sector per track, track dump to sector dump conversion. TIPI supports converting DSK images to an extracted directory on your TIPI share. It delegates sector dump extraction to xdm99.py. However PC99 DSK images are in one of 3 track dump formats. Previously I have supported the 9 and 18 sector per track formats, for 40 track disks. Now I have extended this to support the 16 sector per track format, and to allow for 80 track (per side) disks images. I have implemented this from the spec at https://www.ninerpedia.org/wiki/Track_Dump_Format. I've already gotten tired of looking for disk images to test. If you find specific examples of incompatible disks, I am happy to receive them here, so that I may examine and keep this feature as 'magic' as possible. -M@

The list is pretty limited. The EA manual details how to perform the lookup in the speech PHROMs. So you don't need to build your own table. The libti99 code hopefully provides hints about how to wait for results from the synthesizer. Like VDP RAM, the speech PHROMs are only accessible through the synthesizer. However, I figured since the vocabulary is so limited, it is pretty useless for user input. So for C, a set of defines seemed the most useful approach. A nice addition to the lib might be a routine that takes an array of the addresses and loops through the say, and wait functions. I didn't do that because I figured for game dev, you wouldn't want to block your game loop on an entire phrase set. But that is a compile time solution, and not what you asked for.

It only creates an incompatibility with other people or yourself if you switch to an 80 track controller. So you have to ask yourself if that is an actual use case you have...

Idioms evolve. Shotgun wedding is commonly used to describe haste in a business arrangement. I think usually a criticism, expressing doubt in the merits of the arrangement. That is closer to the use of shotgun to describe therapeutic diagnostics as a repair technique. Hastily swap the chips in sockets, and if the problem goes away, one of the replaced chips must have been the problem. They are both about a hasty decision. Medical professionals exercise therapeutic diagnostics to, but suggesting they are "shotgunning it" would typically be insulting. But traditional use did mean forcing a man to marry a woman, usually to avoid family embarrassment of premarital pregnancy.

Much more enjoyable with the continuous music, and simultaneous effects. Thanks! @Tursi and @OLD CS1

Ok, that announcer expression popped into my head and so I pretended I was 20 years younger and found a meme generator. Sorry... But OMG - https://www.monsterjam.com/en-US <- they still do this ??? Imagine the maintenance cost of these things when they become retro... LOL...

https://github.com/jedimatt42/tipi/wiki/File-name-rules#case-sensitive

There are those programmers that enjoy porting a game from another platform to the 4A, or Geneve. I might imagine there is overlap in the reward to the programmer for this proposal.

Update 3.21 - 2023-08-20 - Fix TipiWatchdog.service - restore functionality that tipi.service restarts when PI detects reset signal from TIPI hardware. I think this has been broken since the Le Potato alternative PI function went in. This is also a good example of why whitespace should not be a substitute for { } in a programming language. As you can see here, the change is just deleting 6 space characters: https://github.com/jedimatt42/tipi/commit/6d7de225b1c67f252aaa1e02d1608838295ed9c3

I've dropped an update to ForceCommand that supports the CS1 and DSK5-9 mapping with the builtin TIPIMAP command.

I've dropped an update in post #1 of this thread, that allows TIPIMAP command to support CS1 and DSK5-9 mapping... @JasonACT this does not have the beta 2.6 change I sent you to support cataloging 'DSK.' and treating it like a full drive. I think we only want to do that if your device is the lone provider of 'DSK.' So I'm curious if there a designated way to identify your device. Such as a device name unique to it, or some other consistently discoverable attribute in the ROM?

More precisely, p-code is a different operating system. The feature that allows TIPI to skip requests for an unmapped drive is a part of the third, high level, file access APIs of the console DSRLNK, and most clones. P-code uses the lowest level API, sector read/write. And when it was created, nothing had DSRs that 'skipped' a request and so the implementation of p-code didn't consistently allow for the feature. Worse yet, some pieces of p-code assume the floppy controller is at CRU base 1100 and optimize out the legacy DSRLNK altogether. Supporting p-code stopped being my intention. Even under 1st party control, TI didn't protect the hardware abstraction layer correctly. The sector access support I implemented is good enough for Plato, and a few poorly written 4A utilities. But even for those, generally only if TIPI is the sole disk provider.

Yes, p-code with TIPI only really works if there is no other disk controller and TIPI is at CRU base 1100. There is nothing we can do to fix it short of fixing the p-code system.

Seems like the word "text" should show up in the Kickstarter description. Sure, young folk can Google Infocom, but I would expect to see the phrase "text adventure" instead of simply the term "adventure" Question I would ask in the FAQ if I were willing to login to Kickstarter: - Is the game already written? ---- If I were interested in text adventures, I still wouldn't want to back the authoring up front, but could understand up front backing of the physical deliverables with compensation for the authoring included.

It was true a month ago, and it is true today, that there is no intention to update the ROM in the future.

I've been a little distracted. I kinda want to restructure TIPICFG completely. In the mean time, you can edit PI.CONFIG in your favorite DV80 editor to set the new properties.

I think you are right. Crazy how that happens.