by
Jinx » Thu May 13, 2021 2:20 pm
Thanks, but like I said, that was 2006--7.
Cancer #2 was either 2011 or 2012. Cancer #3, which never happened, was detected before it became cancer #3 about 6--8 months ago, when a cyst was checked in the lab and determined to be (according to gi doc, pre-cancerous; according to my doc---fantastic doc, btw, and my oncologists, cancer precursor ... either way, if we hadn't caught it, it would have been cancer within about a year from then). And that's the last time I'll ever resist getting a colonoscopy. GI specialist doc said next in five years. I said how about next in one year.....
But this is drifting way off-topic again...not that I really see much left on this topic, unless someone has a major breakthrough with new information. I'm past being ready to be unhappy when I download VSTs that turn out not to be VSTs, but MSEs instead. M$ may be getting confused about which type of .mse file it is---here are three that I found in one search result:
* 3ds Max Encrypted MAXScript files
* XML-like format used to describe ... file format used to store audio data.
* Perfect Keyboard ... a macro file that enables ....
* Magic Set Editor
But then, the file extension, with rare exceptions, is only for human consumption, and the file header is what actually tells the OS what kind of file it is, so that may not have anything to do with it. For example, I could have vet records for my Norwegian Forest Cat (Wegie), Jinx and call the file "Jinx.vetRecords (or simply JinxVetRecords with no extension, or even, if I want to hide his vet records, .JinxVetRecords) and it'd work just fine. I have shell scripts that both have a .sh extension, and don't. It's the "#!/bin/sh" in the first line that identifies it as a shell script (in this case, under Cygwin). So again, that might not have anything to do with it.
Who knows.........