jedimatt42

I thought I wrote a DISKIMAGE tool for ForceCommand... https://github.com/jedimatt42/fcmd/wiki/diskimage <- oh, I did! I would expect a lot of the legacy sector copy programs to not know how to cope with subprogram >10 in a DSR at a non->1100 crubase. Or, they'd just use crubase >1100 directly and fail to see the TIPI as a destination... This is probably why I wrote my diskimage tool...

This sub-thread of the topic was definitely meant to be humorous... But seriously, I don't have specific plans right now. But I am open to improvements and suggestions..

I think there are many life fables and tails about the dangers in assuming. In this case, it is hard to tell if you are correct or incorrect. Even I don't know if making an assumption is right for you or not. I think you just have to be okay with your assumptions being wrong and allow for the consequences if that proves to be the case. You never know when someone will message me and ask if CS1 is possible...

Things on the guest network are prevented from seeing the things on the main network, this is the point of the guest network. But consequently, the things on guest are typically invisible to the things on the main network as well. Make sure the main network is set to support the PI's wifi capabilities, which I believe is just 2.4ghz. the TIPI sd card image has the wifi set for the US region. You likey need to attach a keyboard and HDMI to the PI and manually configure the router and PI until they agree on the main network.

You can also verify that the service are running by telnetting into the PI from the 4A. The terminal is a little mismatched for Linux so you generally need to type everything perfectly the first time. From TI BASIC: CALL TIPI("TIPI.NET.TELNET") Pick the appropriate screen mode, 80 columns requires an F18A. For the hostname prompt enter: localhost For the port enter: 23 At the login prompt enter the credentials: Username: tipi Password: tipi Then run: sudo systemctl status TIPI web.service What does it show?

An example URL for the web browser looks like this: http://192.168.1.65:9900/ Note "http" and not "https" - in most web browsers if you want no 's' you have to type the 'http:' explicitly. An example CIFS/Samba path for a windows FILE browser looks like: \\192.168.1.65\TIPI\ If your router provides local DNS for your home network, then usually you can use tipi.local instead of the IP address. Otherwise run CALL TIPI from TI BASIC and use the IP address it reports on the 4A screen.

I find it isn't that bad support-wise to let people build and sell the TIPI. I generally encourage raising the price too. It has to be worthwhile for the builders out there. I keep all notifications from Atariage disabled, and don't use any other social media. So I only butt in and help here when I am curious. A lot of the support ends up being provided by the primary builder, and the community. But it is true that the eBay builders don't provide any support. I still think they are a win-win, - I'm not obligated - the device remains available - more people end up using it - and the 4A - variants were created I did build the first couple small batches which covered my R&D and tooling costs.

https://learn.microsoft.com/en-US/troubleshoot/windows-server/networking/guest-access-in-smb2-is-disabled-by-default ^--- this is what I was thinking of ..

The brief docs on getting at the web interface are here: https://github.com/jedimatt42/tipi/wiki/tipi-installation#transfering-files The port number is important if using a web browser. The windows file browser can require be picky about the Linux Samba host and lack of authentication. I think on some versions of windows I have had to Google up some windows settings to allow connecting to unsecured file servers.

password sent in PM

The TIPI DSR only uses the VDP memory that your PABs tell it to use. If at crubase 1100 it will adjust the system VDP stack on console power up/reset just like a TIFDC does. But it does not use that space. It does this for compatibility with The Missing Link.

It's every Saturday, even when no one says anything in this thread.

regarding the bitmap, yes, it is required to set the inaccessible sectors as used. The TI FDC calculates available sectors based on that bitmap. "... HFDC and Geneve for high desnity disks" <- does that mean the HFDC did not support high density on a 4A?

word alignment question... char arrays on the stack do not appear to be word aligned... makes sense. are int arrays always word aligned? what else is always word aligned?

So, I've called level 2 floppy disk format subprogram 0x11 in the disk controller and get back my formatted ( low level, no filesystem ) disk, with the total sectors returned. Then I have to construct the filesystem... which is basically echoing the format parameters, the volume name, some flags, and the available sector bitmap to sector 0. I see the docs for the Myarc HFDC that says the interleave can be varied. But their description of the sector 0 layout is unchanged from TI's. The interleave in the format request goes in the 'Density' byte when making the request. Does it also need to go in the 'Density' byte in sector 0, or does it go in the track metadata that is encapsulating sectors?