Origin of the name Ty Files

Tivo Ty Files were an exported version of the database oriented FSID files from an early version of the Tivo operating system. This is purely speculation.. but

T could stand for Tivo

Y could stand for 'Yellow Dog Linux'

Early versions of the Tivo recording box were based on the IBM PowerPC PPC cpu.

A version of Linux compiled for the PowerPC cpu was called 'Yellow Dog Linux' which is where the fancier YUM command later used in RedHat Linux came from. Its was more the Package manager to the package format, as APT was to the debian dpkg file relationships.

Anyhoo.. that the original Tivo operating system probably had some similarities or origins to the Yellow Dog Linux, might explain the inclusion of the letter 'y' in the name.

And since the FSID objects in the storage system were a type of non-file, file which held an entire recording, calling them Ty files .. might make a nice play on words or 'pun' attractive to program writers at the time.


Setting up Airpods Pro on Windows 7 - eliminating Yellow Exclaimation Cones Error 28

Airpods Pro are nice, and will pair with a Bluetooth Adapter on Windows 7, however there will be one Unidentified Bluetooth Device


Checking the device manager under Other devices will have an unmatched device for which there is no driver and Error 28

I do not know if this is proper, its based on 

Airpods windows 7 conection error "Bluetooth Peripheral Device Driver Not Found"

Basically (this does work).

You have to find a source for the install package, for 32 bit or 64 bit Windows 7 for;

"Windows Mobile-based device support"

1. Install that

2. Then find that device and right click to update its device driver

3. Choose to navigate the Local system device drivers and wait for a complete list to compile

4. Scroll down to "Microsoft Corporation" and ignore the other surrounding "Microsoft" collections

5. Find "Windows Mobile-based device support" and choose that one to install for this device. Click on dismiss to continue to install it no matter what the warnings.

It will install a new service under the Device Manager : Bluetooth Radios, with no error or warning cones.

And it will decorate the "Devices and printers" object (for me); "John's AirPods Pro Properties" in the Hardware tab

With a new Device Function - Windows Mobile-based device support

And the Airpods Icon in "Devices and printers" will no longer have a Yellow Cone, and "Device Manager" will no longer have an un-associated device with no device driver.

The Key thing is the "Windows Mobile-based device support 6.1" which has been de-supported and Microsoft has removed the download install packages from its home websites. This was the replacement in Windows Vista for ActiveSync for Mobile devices like iPods, iPads, iPhones, Windows Mobile devices and Android devices. (2007)

The final install packages are archived all over the Internet.


EDIUS - AJA, Blackmagic, Matrox, Canopus/Grass Valley. DV, HDV

Getting a copy of EDIUS is expensive and rather hard for the older versions. Being as its basically from Japan and I understand it I can understand there would be some challenges.

But I kind of like it.

I have EDIUS Pro 6.5, following the "Pro" model - this includes a software waveform and vectorscope feature. The non-Pro version effectively leaves that feature out among other things.

Its got a fast, snappy response and a proxy system for pre-render that speeds up the editing process on lower powered machines.

But what really makes it interesting for me, is that EDIUS seems to work well with AJA Kona, Blackmagic Intensity Shuttles, Express USB3.0 and Thunderbolt devices, and the entire line of Canopus capture devices.

There are some quirks depending on the device, some only play sound in preview, while capturing, some don't at all.. but by the time of this type of software, it was more common to also output the incoming signals through a second set of jacks to an analog monitor setup like an LCD monitor or TV and speakers or headsets.

EDIUS 7 was the last version to support Matrox mini and MXO2 hardware, but I think that may be because either Matrox desupported them, or because of the lack of 64 bit device drivers for some older gear. Its seems Adobe Premiere Pro went through something similar between CS 4 and CS5.5 where CS5.5 was 64 bit only and offered a gratius copy of CS4 for 32 bit operating systems.

EDIUS 10 (X) is available for Windows 10 and Windows 11, but I am not sure if it retains the ability to support older capture gear.


TiVO sharing between TiVOs in a Household - Making that work in 2022


The old TiVO ToGo feature is no longer officially supported and the ability to turn on sharing seems to have been removed from the My Account page on the TiVO Account management site.

But at least for TiVO Series 2 and Series 3 HD, it still does work.

One curious bit of information, it seems if a TiVO is Reset using Guided Setup the sharing TiVOs "must" be in the same ZipCode. 

If they are not, it appears this is one measure for them not being in the same household and sharing will not work. TiVOs reset with the guided setup and in the same Zip Code can "share and see one another" but TiVOs setup in different Zip Codes cannot see one another even if on the same local LAN in the same household.

TiVO Desktop for transferring recording to a desktop, also works between PC and Mac with the proper software installed, and licensed for the PC or Mac.

Presumably this also means the same thing for PyTivo.

UPDATE: different day, different Tivo HD

The New TivoHD had to get added to my account, then it had to update its MAC Key to mine by contacting Tivo.. but the other Tivos on my subnet could see but not share videos, and the New Tivo could see them but not see videos on them. Turned out the other Tivos had to contact Tivo and then they could see each others videos. I initiated a Tivo network update, and only after it went though all but the last step of loading guide data.. di they start to see each others recordings.

So its not just that the New Tivo needs to contact Tivo and update its MAC key.. and that it have Tivo sharing turned on.. but also needs for the other Tivos.. even if they have the exact same MAC key.. both sides need to contact Tivo and then sharing starts working.

I wonder if the MAC key is more a pointer to a table or permission list held at Tivo.. that downloads a list of Tivos for the end user Tivos that says its okay to share recordings between them. So basically.. when they contact Tivo Central.. they download the updated recording share lists for your subnet.

It also seems to be mac address based, since I had a burned out ethernet port on one Tivo that never shares.. but it seems the Tivo share list won't update to include it.

Ironic is the "MAC" key refers to a user table like a hosts or DNS list of Tivos on the local subnet that are allowed to share. They can "see" each other by MDNS or some type of Bonjour.. but don't have permissions until the updated MAC list is downloaded into each Tivo.


Using Snell Wilcox CVR400D and CVR600AD with Windows GUI Software

Snell & Wilcox had a bespoken TCP/IP and COM/USB networking tool for managing the CVR400/CVR600 series of Kudos+Plus Timebase Corrector and Frame Synchronizers

I finally got a copy of the RollCall Lite software to install and work with the USB ports on the CVR400D and CVR600AD

The trick lay in the versions and history.

RollCall Lite was a slightly stripped down of the full suite of network management tools minus things like their Logging server. It was free for download, but since it came from either 1998/1999 or 2003/2004 there aren't a lot of copies left on the internet.

The PDF documentation manuals also suffered from being written probably by people overly familiar with the software and less with communicating information to other people. Many terms are left poorly or completely undefined and its assumed the reader knows the context.. mostly it comes up as gibberish and ends abruptly.

The key was reading a small portion of a subnote that referred to difficulty Upgrading from Version 3.x to Version 4.x

Version 3.x seemed to be written for an older Windows platform, perhaps as old as 98SE or ME

Version 4.x seemed to be written for a newer Windows platform using Java

Version 3.x relied upon a separate service that monitored and managed the USB port and surfaced it in Device Drivers as a virtual COMM port, but also as a TCP/IP service on port 2059 - this separate service was called - RollTop and was a separate install and start up.

Version 4.x was a Java applet and program called RollCall Control Panel, this started up and searched for services on TCP/IP port, including the local workstation, and if told to search port 2059 it would find any device connected over the USB port.

It could then be configured to source the device templates (control panels) from the device and build a control panel within the Java application RollCall Control Panel.

The caveat of this however is that although the RollCall install warns you need Java JRE 1.6 or later, only Java JRE 1.7 actually works - the behavior with 1.6 is a blank window that never populates or builds with controls and through an obscure SWING AWT error message in the error.log file


Using a Matrox MXO2 Dock with Windows 7 32 bit Thunderbolt 3 laptop

I was quite surprised to find this was even possible.

I believe the Matrox MXO2 Thunderbolt 2 Dock came out in 2010 and was directly targeted for the Apple Mac OSX 10.6 market.

But after installing and activating Windows 7 x32 on an HP Folio G1 laptop with a USB3/Thunderbolt 3 port, and using an Apple Thunderbolt 3 to Thunderbolt 2 adapter.

At first the MXO2 Dock powered up green, but the OS could not see it.

So I had to install the HP sp85610.exe package - Intel Thunderbolt 3 Secure Connect Utility

It detected the Matrox MXO2 "knocking" on the PCI buses door, and I changed the answer from Block to Allow.. and suddenly PCI bridges and device drivers started installing.

When it was done the only device it couldn't find a driver for was the Broadcom Extreme Gigabit Ethernet port of the Dock.

I hunted around by PCI VEN and DEV to find the HP Broadcom 17 sp82011.exe package had that driver and installed it.. it was a universal installer so it brought along a lot of peripheral management software and installed a 32 device driver for the Ethernet port.. and it detected the network and setup the adapter.

So now its fully functional.

I tested both the USB 2 high speed ports.

I tested the USB3 super speed port.

I tested the HDMI port and could extend or replicate the Intel 515 display on an external monitor.

I tested the Ethernet port.

 All work as expected.

I'm really curious to see if the Matrox MXO2 capture devices like the mini, mini-max and LE can also be used through the proprietary PCI "host" port on this dock to avoid using the ugly little black host to Thunderbolt 2 boxes, or the PCIexpress card or the PCIe PC card.

It just seems a more future proof way of using the old capture devices on newer hardware.. even if it has to be with Windows 7 - Flashboot provides a way of installing Windows 7 even on newer hardware without a CSM compatibility bios extension with a UEFI shim to support ancient bios legacy calls for the startup screen and bsod windows.

I assume this will work for Windows 7 x64 but its a guess.. a 32 bit install was a little older and closer to what was more common at the dawn of the Vista and Win7 age.


GPD P2Max Firefox right Click Crashes Browser

When running Windows 7 x64 on a GPD P2Max handbook computer. Right clicking on anything in a Firefox browser page of YouTube videos and sidebar links.

Resulted in a Blank White or Hollow Blank Black box about the size of a Context menu. It cannot be cancelled or removed and eventually the entire Browser crashes. Any currently playifeatureng videos continue to play but all other browser controls are unresponsive. A popup dialog box appears after crashing asking what to do close browser?

Solution: Disable the Firefox Hardware Acceleration feature.

Tools menu > Settings 

Use the Find Search box .. type Hardware

Under Performance "expand" and uncheck