Ump25
01-30-2003, 03:46 AM
Well, this is kind of weird. I've got mvch135 installed and running, and in my rc.sysinit so it runs after a reboot. I mapped my own locals, and 3 other cities w/in my own spot beam, to the 02-99 range. Everything else (like LV, BF, HT, etc.) I mapped to the 900's. Richmond, the newest ones (and on the CONUS feed) I mapped to their proper 873-879. Within the last 48 hours, however, mvch suddenly went haywire. First of all, Richmond (RC) and Jacksonville (JV) completely disappeared. Hartford (HT), Knoxville (KX), Grand Rapids (GR) and Buffalo (BF) are still in their proper slots in the 900's. However, the other ones which I mapped there, like Las Vegas, New Orleans, Oklahoma City, etc., all plopped into the 02-69 range.
Normally I wouldn't complain about the resulting duplicates in the 02-69 range, but the end result is not what I desire. Plus, I can't explain how or why two cities' locals entirely--Richmond and Jacksonville--disappeared.
Rubik and I had worked on a few things (thanks, Rubik!), and we verified mvchannels IS running and is in the proper place. Heck the slowness of the guide should be enough to prove this. What we are concluding is that, for some reason, my T60 has reestablished new internal channel ID numbers and caused this new, weird realignment.
I'm about to a dumpall to check and compare to my current channels.dat file, but my question is: Has this happened to others here? Is this something that occurs often, and if so, can it be prevented or worked around automatically?
Normally I wouldn't complain about the resulting duplicates in the 02-69 range, but the end result is not what I desire. Plus, I can't explain how or why two cities' locals entirely--Richmond and Jacksonville--disappeared.
Rubik and I had worked on a few things (thanks, Rubik!), and we verified mvchannels IS running and is in the proper place. Heck the slowness of the guide should be enough to prove this. What we are concluding is that, for some reason, my T60 has reestablished new internal channel ID numbers and caused this new, weird realignment.
I'm about to a dumpall to check and compare to my current channels.dat file, but my question is: Has this happened to others here? Is this something that occurs often, and if so, can it be prevented or worked around automatically?