I have the midi files you mention, I think I got them from a windows 95 when I was using it, mine don't have any channel greater than 10
Thanks for the information! I also found these pages on the Internet Archive that contain the MIDI files included with Windows 3.0 and Windows 95, if anyone else wants to compare them.
Windows 3.0 MIDI
Windows 95 audio media
While reviewing information about the Passport Designs MIDI files, I found a wiki site devoted to documenting various old MIDI files like these. (Warning: This wiki site has lots of ads, I suggest you use an ad-blocker or disable JavaScript to view these pages.)
htt
ps://midis.fandom.c
om/wiki/Category:Passport_Designs_Midis
htt
ps://midis.fandom.c
om/wiki/Canyon
htt
ps://midis.fandom.c
om/wiki/Passport
htt
ps://midis.fandom.c
om/wiki/Midi_Related_Glitches#Out_of_Tune_Piano_Tracks_on_Older_Midis
The pages describe CANYON.MID and PASSPORT.MID had new versions in Windows 95 with less channels. I didn't bring it up in my post above because I thought that information might be wrong, perhaps because someone had edited their copy of the file. But now you've reported your Windows 95 MIDIs only have channels up to 10 that helps confirm that information is correct. It makes sense they no longer wanted the MPC Base arrangements anymore.
(The pages actually describe this the other way around, they describe the version that originated with Windows 3.0 is an "alternate version" with more channels and an "out of tune piano" on channel 16 that is a "prototype of the drum track". The wiki authors there don't seem to be fully aware of the MPC standard. The channel 16 notes weren't a "prototype" and were there on purpose. They are percussion for the MPC Base arrangement, meant to work with something that would play either the Extended or the Base arrangement in the MIDI file as appropriate.)
they do start with a sysex FF 7F 00 00 40
In the original versions, the meta-event is the following bytes in the MIDI file:
FF 7F 03 00 00 41
This is the Sequencer-Specific meta event that contains the Microsoft Manufacturer ID that I mentioned.
In a MIDI file, a "status" byte of FF is used for a meta event.
The next byte, 7F, means it's a Sequencer-Specific meta event.
The next byte, 03, is a variable length quantity for the value 3, which means the contents of the meta event continues for the next 3 bytes.
The next bytes, 00 00 41, are the
Manufacturer ID for Microsoft.
According to the
Standard MIDI Files specification, a Sequencer-Specific meta event must begin with a Manufacturer ID. Any bytes in the meta-event after the Manufacturer ID can be anything the manufacturer wants. In this case, the only thing the Sequencer-Specific meta event contains is the Manufacturer ID for Microsoft and nothing else. This meta event is used by Windows Media Player to recognize that a MIDI file contains (or might contain) a Base arrangement on channels 13 to 16, and Windows Media Player will just ignore those channels and only play the Extended arrangement.
However, in the Windows 95 versions (at least the versions on that Internet Archive page) the meta-event does contain the bytes 00 00 40 ! That's the Manufacturer ID for some other company called Richmond Sound Design. I don't understand why this event was changed, I think it could have just been removed? I find this detail interesting and I didn't know about until you mentioned it. Thanks for the information.
(Note: Be aware that a Sequencer-Specific meta event is a different thing from a System Exclusive message, but has a similar kind of purpose. They're both manufacturer-specific messages whose contents begin with a Manufacturer ID. But a System Exclusive message will get sent out on a MIDI port for a MIDI device to see. A Sequencer-Specific meta event, like all meta events in a MIDI file, only exists in the MIDI file and can only be seen by the MIDI file software, it doesn't get sent out to the MIDI port for a MIDI device to see.)