gleened a little bit from the inf setup file
it says these are the drivers and what they do:
Code:
atinyuxx.sys ; ati ntsc ; TV Tuner
atinysxx.sys ; ati ntsc ; Sound Crossbar
atinyvxx.sys ; ati ntsc ; Video Crossbar
atinypxx.sys ; ati ntsc ; Parental Decoder
atinymxx.sys ; ati ntsc ; Macrovision Decoder
atinyttx.sys ; ati ntsc ; Teletext Decoder
atinymvx.ax ; ati ntsc ; MVDetection activex filter
atinytmx.dll ; ati ntsc ; MVDetection function driver
atinyc20.cod ; ati ntsc ; DSPminicode (VideoSOAP maybe)
Only the first three are really related to AV capture, the others enable more features in the ATI MMC software.
Each has its own little stanza that builds up an interface that DirectX or another program could use.
As far as I can tell the inf file was used as a scratch pad for ideas and certain parts are commented out or look like they were "beta".
But since it was based on the use of DirectX and WDM its fairly similar to the inf for the empia 2860 capture device. I can definitely see where a little text formatting problem could be tripping it up from working well under Win7 or Win10.
This could be a dead end.. along with a modified inf file is a security .CAT (catalog) file which is suppose to be signed and act as a token to validate a driver package as valid and verified by a developer.. that's what costs a lot of money to sign and keep up to date. I am not sure how to get around that yet.
But it is interesting to read the plain text file and compare and contrast to the same plain text file from a different but similar driver.. its very educational, if academic.
p.s. One other thing
The USB device driver is in a separate driver inf and driver file completely. That driver gets loaded upon detecting a Cypress USB controller that identifies itself as an ATI TV Wonder USB2.0 with a VEN and DEV id, when that loads it enumerates the other logical devices attached to it.. which appear as the "three" hardware devices above, tuner, video xbar, sound xbar which then automatically build their interfaces and plug into the DirectX plugin gallery ready for use.
I presume the protocol then is to send USB packets of data labeled or "addressed" to one of the three devices with instructions or commands to perform. The rest of the device drivers are "virtual" devices which carry out their orders in virtual logical devices that examine the data stream coming into the operating system from the other USB devices.
amazingly
uxx is 63 kbytes
sxx is 78 kbytes
vxx is 171 kbytes
total 311 kbytes
that's the difference between a 32 bit or 64 bit driver to keep this hardware going