Subj : Y2K again..? was: Note f To : Nancy Backus From : Barry Martin Date : Fri Jan 24 2020 11:40:00 Hi Nancy! Ooo! Your message was #11111 here! BM>> January 4th: I'm back! Appears there some sort of problem with the BM>> mailruns when rolled to 2020 -- two decade delay on Y2K?! NB>> Richard just mentioned tonight that apparently some of the Y2K fixes NB>> merely tossed the problem down the road 20 years.... maybe that caught NB>> you...? He said that nothing that I use would be affected by that, NB>> though.... :) BM> I may have read the same article. Prior I hadn't heard anything; it BM> would have seemed there would have been some 'leak' there could be a BM> problem. NB> Perhaps the authors of those kick-it-down-the-road fixes aren't NB> around any more or forgot it would eventually loom again... it NB> was, after all, 20 years ago.... BM> I would guess a combination of all options. I didn't read anything; BM> admittedly I'm not "in the loop" but usually read in the techier stuff BM> of potential problems. NB> I don't think that Richard had heard anything ahead of time, NB> either... OK -- not that I'm concerned with being out of the loop, but nice to know I was sort of caught unawares also. BM>> (For the Y2K one I didn't do much other than screen print a BM>> copy of my financial statements from on-line, have a little extra BM>> cash, and make sure the cars were reasonably filled. I didn't think BM>> things would grind to a halt and if they did would be isolated cases BM>> and fixed so running within a few days.) NB>> There was a lot of hubbub before Y2K... and lots of people scrambling NB>> to patch important stuff.... Richard didn't expect much of a problem, NB>> either, but we did take the precaution to shut down all the computers NB>> entirely before midnight, and wait a few minutes after before turning NB>> things back on.... And then nothing happened... BM> I think I shut down overnight also -- don't recall: it was twenty BM> years ago. AFAICT all went smoothly here at the house, at the BM> store, elsewhere in the area. NB> Yup, it was pretty much a non-event... Not that anybody I knew NB> was upset by that... it was more a relief... :) I don't know of anyone who was in a panic either. Thinking back seemed most did about the same as I did: get some verification paperwork together, have some money, make sure the gas tank wasn't empty.... As you said, ended up pretty much being a non-event, probbaly because of all the behind-the-scenes work going on to make sure it didn't occur. NB>>>> ... Workarounds are lifesavers... until they get waterlogged... ;) BM>>> And it's really bad when the patch has to be patched! NB>>> That's for sure.... BM>> Years and years and years ago I used WordPerfect. Not cheap but BM>> worked the way I wanted it to and had the functions I wanted and BM>> whatever Microsoft offered didn't. Recall reading WordPerfect did a BM>> complete overhaul of their product about 2/3rds of the way into my BM>> using them because there were so many patches and sub-sub-sub-routines, BM>> etc., it was causing a significant slowdown. So they started from BM>> scratch, rewrote the code, and came out with a much faster and BM>> better-running product. NB>> Makes sense... :) Did they offer the new product at a discount to NB>> their faithful customers that were still using the old version...? BM> I don't recall: that was probably more like forty years ago. NB> Must have seemed equitable to you at the time... otherwise, I'd NB> expect that you'd remember it more vividly... ;) Especially as NB> you kept using it for quite a while longer... ;) Right: probably more along an upgrade price as opposed to a brand new version price. BM> ...Had to do a rescan of the TVs because of the "Repack" ==> BM> television stations moving their transmitting frequencies. Locally BM> "Channel 6" had done it (finally) a month or so ago, with lots of BM> notifications on-air and their website, including delays because of BM> weather. BM> That left Chs. 8, 18, and 26. (Other stations not moving.) Ch 8 had BM> a handful of announcements it would be updating today (January 17th) BM> but seemed like their total announcments would have added up to what BM> Ch. 6 notified in one day. Never did see announcments for the other BM> two stations. BM> So Ch. 8 was "off the air" this morning, did my rescanning which BM> brought them back. Also found out later Chs. 18 and 26 had changed so BM> locally the TV stations should be up-to-date. NB> Ours happened a couple of months ago, I think.... I remember NB> Richard needing to rescan at one point, and lots of announcements NB> ahead of time on my radio station for the (PBS) TV's changing NB> transmitting frequency. And I think it affected all the stations NB> in our area.... For whatever reason about half the local stations moved. I'm not sure why the move other than to use the band more effectively. Did notice one thing different: my MythTV scan only went to Channel 52; UHF band used to go to 68 or 69. Maybe the "repack" name is to oveall condense the band; I half-remember the FCC wanting to use some new channels for things like cell phones, maybe WiFi and conumer devices. LIS, half- remembering bits and pieces. Back to the local repacking, Ch. 6 was the first one, but delayed because of weather, and some of the weather delay was at whatever station the tower crews were working one before coming here, some weather delays due to the bad weather locally. As for the other stations, just didn't say much. ¯ ® ¯ Barry_Martin_3@ ® ¯ @Q.COM ® ¯ ® .... Repair 101: He said the doodlehickey isn't contacting the thingammiejig. --- MultiMail/Win32 v0.47 þ wcECHO 4.2 ÷ ILink: The Safe BBS þ Bettendorf, IA --- QScan/PCB v1.20a / 01-0462 * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1) .