The Computer Chronicles - Year 2000 (Y2K) (1999)

Special thanks to archive.org for hosting these episodes. Downloads of all these episodes and more can be found at: archive.org/details/computerch...

[@Abernathythedull]

I was in the final group at Microsoft that supported DOS and Windows 3.1. There were 10 of us hired in early 1999 that comprised the entire team. Both DOS and Windows 3.1 were Y2K compliant. We knew nothing was going to happen. But they had us all come into work New Years Eve to work through midnight in case any emergencies cropped up. They sent us home at 1am with zero phone calls.

[@tinto278]

climate change is the new Y2K problem...$$$$$$

[@MaGiKRat420]

What about all that yellow Microsoft software?

[@koopey]

Congrats?

[@shawnhussain7713]

That’s pretty cool!

[@gregledbetter5942]

Zero calls.. I wonder how many calls they got July 19th 2024.. thanks for going into work that night, I was in high school and my mom and dad were up in a frenzy they had purchase large quantities of water food flashlights candles ect they were barely able to squeeze the car into the garage along the surplus provisions. I remember my dad for months leading up to this tinkering with the computer watching this program and really studying leading up to it.. I forget the program that he purchased, dad was a do it yourself type guy.. I remember he purchased a software package for it, but i forget the name. although nothing happened it's good to know they had you guys come in to work..

[@FeedEgg]

At 12:00 am on January 1st year 2000 i ran outside and screamed. "MY TOASTER IS TRYING TO MURDER ME!"

[@hehotbros01]

Kool

[@TheJFGB93]

Some people seem to forget that the reason nobody had problems because of the Y2K bug was because a lot of people worked to prevent these problems in the preceding years. It's like people saying "the ozone layer thing was a scam, nobody talks about it anymore". People did the work and solved the problem before it was worse.

[@talanock]

there was a shootout and i wore a bullet proof vest. didn't get shot once. wore that thing for no reason!

[@ATCRyderX]

Tis a shame the world didn't implode but these "Computer Chronicles" vids are worth watching just for nostalgic purposes.

[@raven4k998]

dude it was just a clock glitch it's not like it would have caused Fukashima you needed idiot Japanese nuclear reactor workers to make that happen

[@harshbarj]

@@raven4k998 It was more than a simple clock glitch. It would have caused many programs to crash. Including many that perform critical operations (from traffic control to operation of the power grid) . Had it gone unnoticed, you would have likely seen weeks to months of daily life coming to a halt. I know many of the old systems I have that still have that bug can no longer be used with the correct date and will crash when flipping over. We dodged a bullet caused mainly by lazy programmers that did not want to work with a 4 digit year.

[@levioptionallastname6749]

@@raven4k998 you are 12 go to bed.

[@raven4k998]

@@levioptionallastname6749 you are 5 years old so go back to kinder garden you stupid child so you can learn to read

[@levioptionallastname6749]

@@raven4k998 *Kindergarten, It is one word.

[@cloviscareca]

Who's else watching this in 1918?

[@nicholasmorales24]

Matheus Bitencourt 1919

[@mindtreat]

Watched it back in 1891 first time, and returned today for nostalgic reasons.

[@shermanzuki]

Year 10000 anyone?

[@netherforager]

1920

[@JaredConnell]

@@lemonmerrengue why even comment? Like really?

[@greeneightball]

Love that Audible still be getting their plug in 25 years later...

[@DavePoo2]

From what I remember at the time, all Y2K achieved was every desktop computer in the world now had a "Y2K Compliant" sticker on the front.

[@BokBarber]

It was a very serious problem... on legacy mainframes, if they didn't fix the issue beforehand. Your computer at home was probably always fine.

[@CollyDoo]

These were the Napster/Linewire years. Good times!

[@cursetheserpent]

Napster and limewire were the beginning of the absolute destruction of the music world. I loved limewire. Remember kazaa?

[@graxjpg]

@@cursetheserpentthose music industry leaders have a much more deadly grip on things with everybody streaming everything.

[@brianx2405]

liMe wire

[@brianx2405]

replaced by torrents i would say

[@CollyDoo]

Can't forget MPlayer as well..but that was back in 97,98.

[@NoirHammer]

I've seen the future so don't worry about it my friends in 1999. Y2K everything is okay!

[@raven4k998]

yeah y3k is a killer but even it has been fixed gigabyte fixed the bios versions to force you to use a year 2000 year for your date if you put a year 3000 or higher year in the date it does not accept it anymore

[@scottandrew8906]

The good old days of being 15 and being told to worry about a computer crash by my I.T. Career father.

[@Stenstorp]

26:05 wow! Audible is older than I thought!

[@sergheiadrian]

Stenstorp It would have been fun to hear him say: "This episode was brought to you by audible.com..."

[@BlazeBluetm35]

+Adi Serghei would have been a real mind fuck that's for sure.

[@kejiri3593]

But you cant upload anything to Audible i think. But its nice that audiobooks library exists

[@bhollingsworth]

I worked at best buy during this time and we used to charge people $100 for Y2K compliance checks and it was 100% a scam .

[@DavidB-rx3km]

The next episode - Steve Cheifet - “Why was my bank account cleared out?”

[@nicholasbrooks7349]

It probably was invalid or he canceled it or both

[@agy234]

It’s a gas station card, not like it was accepted anywhere else . Plus the types to try wouldn’t have been watching computer chronicles

[@DanielBurapavong]

I love watching these mid-to-late 90s computer shows. I wish the entire library of CNET Central was available.

[@zachsteiner]

Do you have any recommendations for good videos or shows I can check out? I want more content besides Computer Chronicles.

[@DanielBurapavong]

@@zachsteiner No. I'd like to know too.

[@numericalcode]

That would be awesome

[@ObiWanBillKenobi]

1:50 “Valid until the year 1000”! 🤣🤣🤣🤣🤣

[@Real_The_Goof]

I wish this show still existed.

[@Nomadd665]

And talk about what? How the next gen gpu is the same as the last one but $300 more expensive?

[@toyotasupra97]

All because they didn’t listen to programmers in the 80s who knew this would be a problem.

[@BokBarber]

This episode was brought to you by The Audible.

[@oldtwinsna8347]

The issue was profound on backend mainframe systems, not on desktop PCs. The PDP systems were particularly notorious - just check out some other videos on youtube to see how catastrophic the issue could have been when midnight rolled over if patches and updates were not done. Keep in mind you had thousands of sessions going on running little things here and there that supported the computing operation of major applications around the world. In contrast, the desktop PCs were immune - opportunists took advantage by fear mongering tactics to tell the public their desktop PC would burn into flames unless they bought their product.

[@Grunchy005]

Oh yes it was terribly profound! People’s lives revolved around computers, one “tiny” problem and you were instantly shafted in the worst possible way. :droll:

[@oldtwinsna8347]

@@Grunchy005 You bet it was. Logistic services would've crumbled, meaning the toilet paper you value so much for yourself since you're full of it would've been stuck in warehouses.

[@medes5597]

Hey I've still got a copy of WordPerfect that doesn't work because of the Y2K problem. I mean they sent me a new version on disk for free in 1997 but still, that could have been mildly inconvenient.

[@rickybobby7276]

Ok, but that's nothing compared to if people didn't make patches and updates in general. I guarantee you if nobody made patches and updates to the software in use today terrible things would happen. Take Tesla every car would be put off the road since there cars constantly require updates which get referred to as "recalls". Those cars wouldn't be drivable. That's just one piece of software that has to be updated or its use is crippled.

[@ObiWanBillKenobi]

Even if we all use 4-digit years now, in 9999 people will have to work out the Y10K problem, and somehow make room for a fifth digit.

[@imperiumcommentingnetwork4677]

or invent a new date system

[@victoriamarotosilva7093]

Windows is fine even for that. SYSTEMTIME is ready up to year 30827. And I bet the Windows core will survive till this time..

[@rickybobby7276]

Please explain to me how it's hard to upsize from 4 digits to 5 digits?

[@zvndmvn]

A new way to listen to books on tape without the tape? That'll never catch on!

[@Grunchy005]

I love how Stewart Cheifet starts the show, with skepticism about Y2K being an actual issue. Then he shows his faulty credit card. (I guess it might be embarrassing to have to pay for gas using a Visa, or - shock! - with actual cash.)

[@escueme]

Lol I finally understand what the y2k problem in 2020

[@BanditSlots]

24:24 “Planes are not gonna fly, drop out of the sky” - In a weird way it sounds like he was saying they WERE gonna drop out of the sky

[@sydneyx906]

I'm Scared In The Year 1999 I have 6 Years old The Electronics And Lighting Sytesms Are Switch Off

[@nyccollin]

Imagine, if you will, a guest on the show that Stewart doesn’t feel the overwhelming urge to cut short, and talk over, time and time again. That guest, simply does not exist.

[@CatastrophicalPencil]

Getting an Audible ad in 1999 makes me upset

[@jurgenbussche]

this is epic so happy they digi all those episode's

[@markchas4554]

The only problem I encountered was my Flux Capacitor stopped fluxing.

[@Amalekites]

Great Scott!

[@joelhodes1619]

Mine was fluxing just fine, as my girlfriend can testify😮

[@pamelahusky1179]

My Toshiba laptop from 1991 that I was using for high school in 2014 - 2015 didn't have that problem.

[@hpbills]

I remember working to get a lot of PCs Y2k compliant. I was posted as an onsite contractor at Wise Foods in Pennsylvania. Helped ensure the famous potato chips could still be made in 2000.

[@gamerecks]

Are we going to gloss over the fact that he displayed his credit card number on a nationally syndicated TV show. I know it was 1999 when that happened but yikes, who was thinking when that happened.

[@osmandius]

Lol, I was thinking the same thing

[@BrianSmith-yq7ys]

I imagine he cancelled it there was a whole studio of people that would give him a heads up

[@rickybobby7276]

Obviously he cancelled the card prior to displaying it.

[@TheStevenWhiting]

Unfortunately I was just finishing my IT course then and not in IT work, could of cashed in like lots of network guys did with Y2K. What annoys me, is people who don't understand IT saying it was nothing and all hype because nothing happened. Well it was a real problem, but yes, the media hyped it quite a bit, but work was done BEFORE the date and when clocks ticked over to 12am, to make sure nothing went tits up. That's why all those engineers made shit loads due to being at work at 12am on the year 2000 and missing the party.

[@AcornElectron]

Whilst it's true that a lot of work was done on a lot of systems, I recall having to do literally nothing to any of my pcs/macs or nimbus machines in order for them to be y2k compliant. The hard coded chips didn't crash the systems, planes didn't fall out of the sky, cats and dogs did not start living in harmony. It was pretty much an over-hyped scam for IT to make money off fearful, misinformed people. In my opinion.

[@TheStevenWhiting]

But that's the point it wasn't just hype. If you were in the industry at that time and even now, you'd know companies take ages to upgrade to new systems and insist on sticking to old crap hardware (RBS and their crap CRT Monochrome monitors and Nationwide internally still stuck on XP). So there were systems out there, in companies that would of been affected if thinks hadn't been fixed before the date. The stupid argument "planes didn't fall out the sky, systems didn't crash". Obviously not because you don't wait till the day to see what happens, you test it before the date, see the issue it's going to cause and fix it before the date. With critical systems its always better to be safe than sorry so you pay people to be there on the night in case. What would the news have said if things had happened and companies hadn't bothered to pay people to keep watch. Either way you can't win. It's bullshit hype if nothing happens (ignoring that this was because things were fixed before or on the night) and get beaten if you do nothing and major things happen.

[@AcornElectron]

Again that's not really correct. But I see we shall have to simply disagree on the point. ok?

[@rustynail6819]

It was all hype! I raked it in in 1999 because of it.

[@nxxxxzn]

> being at work at 12am on the year 2000 and missing the party completely not a problem. i like to miss all the parties.

[@GeminiWoods]

Wow... This really takes me back.

[@CaptchaNeon]

Meanwhile because I grew up in extreme Christianity, I had to listen to the entire speech about how Y2K was the great return of Jesus and how many of us would be left behind 🙄 Their legit reason was it would roll back to the year 1,000 which matches Jesus’s “1,000 year reign”

[@floydjohnson7888]

@CaptchaNeon Nothing like a few "False-faith Filberts" having the gall to call themselves Christian to foul up yer spiritual life with willful misinterpretation.

[@calvinhobbes1617]

At AMD‘s FAB30 at 23:30 we shut down the fab, send all the operators into the cantina to have late night dinner, the engineers and technicians stayed in the clean room, and watched the machinery. At 00:15 we powered up everything again , so I spent the only millennium change i ever will experience. Anyway, as we did a lot of 2K compliance testing nothing happened. Funfact: The cashier in the cantina showed 1.1.1900 on the receipts, but over the years the ink faded, so no proof of the 2K bug.😢

[@TruthLivesNow]

So dopey! What I did is set the clock to January 1, 2000 and could tell there would be NO PROBLEMS! I had nuts call me telling me that when January 1, 2000 my wife's DOS Court Reporting Software would "cease to function." I told them they were wrong and we are still running it today!

[@user-sv8cr9ox1t]

+Truth Lives that's what I did too just test my computer a few months before the year 2000 so lets say in july 1999 all I did was change the date/year and month and watch what happens when it turns 2000. Computer didn't die like a freak. Remember the month and the date and the year on every computer is not a BOMB. :)

[@user-sv8cr9ox1t]

+HBO 1 the neighbour next door who are oldies. Was scared that they thought their computer was going to explode and they all freaked out and stay away from the computer 1 minute before year 2000. LOL Perhaps in the year 2999 maybe computers might fuck things up believing that everything is going to BOMB leading to 3000. Seriously its just a date and month and numbers.. Its not a BOMB TIMER.

[@TruthLivesNow]

What I liked was the comments from the genius Engineers telling us our cars were not going to start due to the car computer BIOS chips and y2K! LOL!

[@ricsip]

@@TruthLivesNow Nowadays I would start worrying seriously for modern cars.

[@TruthLivesNow]

ricsip I actually have a car that cannot get smogged in my driveway that is a 2000 Camry built in 1999 w only 128k miles.

[@MikeBehrensWX]

26:48 man even in 1999 KZbin was being powered by Audible. lol

[@PressThatButton]

Audible.com, before they were purchase by Amazon.com! Skip to 26:30. This was such a good episode; I remember living through this "scare" as a teen. I was not aware of all of the different software suites (at exorbitant prices) on the market to patch for this issue of the time.

[@crocodile2006]

One of the books listed showed the audio length was 13 Hours 40 Mins... thats quite a download on a dial up connection, would have taken weeks or months to download

[@J_Patterns]

Look at 9:03! It is so funny how sensitive personal information was so readily available back then. Employee names, addresses, birthdays, salary? Wow.

[@chownful]

+Jason Donnelly lorem ipsum bro

[@imperiumcommentingnetwork4677]

I set my Linux pc to Dec 31, 1999 at a minute to midnight (today) and nothing happened.(just wanted to see how well they fixed it back then.

[@unnamedchannel1237]

This makes no sense unless your Linux box is 30 odd years old, even then the calendar is set correctly at a date past year 2000 so obviously your computer is Y2K compliant

[@scyence]

Who else is watching this while Stewart Cheifet is sleeping on their couch?

[@weak1ings]

If my current PC existed in 1999 it'd be stolen from me and used as a Super Computer by the government...

[@adorabasilwinterpock6035]

Super computers in 99 were far more powerful than your modern pc. 1989 maybe

[@MattieCooper10000]

@@nadiagvozdeva3587 If that's the case then why does the FBI have a long old history or losing track of people and being helpless to solve crimes and needing technology to catch up(!) to solve all kinds of past crimes? 🤔 The US Government has been plenty more stupid and antiquated than you recognize.

[@psisis7423]

@@MattieCooper10000 Idk, but could be good software is crucial as well. A lot of bioinformatics and DNA sequencing technology was super hard and expensive until recently. Only scientists knew how to program before, I mean, they shot rockets into space with computers early on.

[@MattieCooper10000]

@@psisis7423 I was responding to Nadia at first. The Apollo 11 computer had a processor - an electronic circuit that performs operations on external data sources - which ran at 0.043 MHz. ... This means that the iPhone in your pocket has more than 100,000 times the processing power of the computer that landed man on the moon 50 years ago. We didn't send men to the moon with 0.043 MHz of power for shits and giggles. That was the available computer power at the time. Nadia G is not thinking things through.

[@JaredConnell]

@@MattieCooper10000 plus think of the fact that modern processors are so much more powerful than just comparing them by clock speed. My phone would be more powerful than supercomputers from only decades ago if you take into account 64 bit, multi core architecture with faster bus and data transfer speeds from flash memory and ram, etc., etc., etc.

[@HKragh]

So many in these comments speak as if the Y2K problems was bs, because: "Nothing happened", right? Well... we did use close to a decade making sure nothing would happen. And then when we succeeded: "What was all the fuzz about, nothing happened!!!"

[@medes5597]

Russia spent almost no money and made no effort to fix it and they also had no problem.

[@focusmicro]

ah memory lane, the good old Y2K compliant slogan haha

[@wallacelang1374]

All of the Operating Systems such as Windows 95, 98, Me, XP, 10 & 11 and MacOS have either been issued with a Y2K fix in them and/or update software packages were made available in the late 1990s through the early 2000s.

[@DyoKasparov]

I'm watching this on 1916

[@Amalekites]

On? 🤔

[@zerocool1344]

I was so worried for my VCR. Lol

[@paulchamberlin6884]

I wasn't worried about anything and nothing ended up happening period. This ended up being a total sham.

[@justinnewton7366]

I was too but it blinked 12:00 am on 1/1/2000 as it did on 12/31/1999... I was worried sick all day because of this one...😎

[@juhaervola1954]

I am recalling memories in 0024.

[@johnbrown92]

I remember this and no new pc's that were being sold in my area had any trouble in fact most were good that were a few years old.

[@user-sv8cr9ox1t]

+John Brown people would had forgotten to just simply test their own computer months in advance leading to new years eve by just change the date/time and month on the computer and watch what happens then people would had known what happens before new years eve 2000 came. :) Its not difficult to knew this.

[@oldtwinsna8347]

Y2k played no role in personal computing as they were immune due to its newer architecture. The issue resided in mainframe computing to which you had legacy systems running from 1960's programming commonplace. For instance, the PDP machines still ran a ton of code that supported commercial backend systems all over the world at the time. They would have all failed if patches and updates were not made. Check out the videos on youtube yourself if you want to see how catastrophic the issue was if it was let to slide.

[@breathtakingblue]

I remember the panic surrounding Y2K... Magazines, software, you name it. I just carried on as normal... Apparently missiles might have been fired, power stations shut down, planes crashing...

[@floydjohnson7888]

@breathtakingblue Metaphorically speaking, the less reasonable folk were doing impressions of "Curly" Horwitz ("woob wood woob").

[@RJARRRPCGP]

Well, unlike what I was afraid of for a bit, MS-DOS didn't reply with the error message, "Invalid date", when I manually set the date to 2000 with the MS-DOS date command. I believe I was using MS-DOS 6.20 with my Windows 3.1 builds.

[@mornnb]

Well I can see this problem today. Was setting up a vintage pc for dos games, some apps in their file explorers see 2024 as ?4 and dont seem to understand what 2000 or 20 are. Yet its not like it crashes or anything.

[@congoballs9725]

From the future Y2k went horribly the computers went nuts they started ww3

[@AbdiPianoChannel]

When was t time this show last aired? Is this guy still alive? Y2K AKA year 2000 was crazy time. I was worried about my Pentium 2. 400mhz pc. But my old pc with win 98 didn't have date problem on January 01, 2000. December 31 1999 at 11:59 pm I was with my now ex-wife in Ottawa on high 417 east bound heading to my new year party. I got there late. I had my y2k on highway. Had to believe it's been 20 years since ytk.

[@xKynOx]

In the UK they nearly destroyed some tins of corned beef but the error was fixed in 2 mins, What a scary day.

[@burkezillar]

We laugh now, but we have the UNIX time problem on the horizon. THAT's going to screw everything up if it isn't fixed.

[@AboveEmAllProduction]

isnt it that thing that even has myths in time travel

[@GeminiWoods]

talking about the 2020 issue? Didn't fuck up too much. Some patches were released for various hardware and some clocks were reset but thats about it.

[@mfaizsyahmi]

@@GeminiWoods 2038

[@Silvers24]

We got 18 years.

[@pixelpi3s]

@@Silvers24 Yeah we have 18 years but, no large tech companies will not work on it until it's 1 year or less away most likely. Just like ya know, Y2K. Edit: bad grammar

[@geemailMossman]

ahh - Nostalgia nowadays, it ain't what it used to be...

[@Amalekites]

And how long has nostalgia been around btw? 🤔

[@captaingreen4367]

Who's watching in December 1999??

[@davidslife989]

Right I CAN NOT figure that one out, considering everything run on dial up.

[@matambale]

I can't imagine what it was like to be interrupted excuse me interviewed by Cheifet.

[@doalwa]

Well, we'll have our next chance at global mayhem when the Unix clock flows over in 2038...lets keep our fingers crossed and our machines patched :-)

[@user-sv8cr9ox1t]

+Michael Echeverria this means by the time it ends 2036. It will just go back to 0000 year. But that's not like as if your phone is going to explode :) lol

[@franksmith613]

How do get your computer Y2K ready? Not do anything at all!

[@osmandius]

Lol, we thought 2000 was going to be the end of the world. 2020 said “hold my beer...”

[@raven4k998]

nope nope nope it the year 3000 dude always has been always will be🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣

[@notthemama7296]

Then year 2001 (the true year 2000) then 2012

[@Expressionistix]

I wish it ended in 2000 as 2001 and after have been hell.

[@tony_anello]

@@notthemama7296 The world did end in 2012, we are in our 10th year of hell

[@notthemama7296]

@@Expressionistix Wait, so was Harambe just an actor demon use to make us feel a collective sense of guilt?

[@countdown2567]

It was the one and only time they could pull this shit on us.

[@Treetops27]

Until 2012.

[@andljoy]

Count Down until 2038, the end of time! en.wikipedia.org/wiki/Year_2038_problem

[@countdown2567]

Andrew Joy Looks like more "made up" electronic nonsense. Nothing happened in 2000, just like nothing will happen in 2038. All these programs have been run and tested already. And besides, at the rate of technology, it will all be replaced with far superior systems in 20 years.

[@andljoy]

Count Down Nothing happened with the 2000 problem as it was all gone through and fixed , same as we should do with 2038. But 2038 is slightly different as we reach the limit of 32 bit numbers, its not like the 2000 problem where we where just lazy and used 2 number for the year. Its also a bigger thing as the unix timestamp is ticking away in many many old devices. Not impossible to fix but its a hard issue rather than a soft issue that 2k was (hard as in mathematical limit not as in hardware)

[@Windfarmer]

I know I'm way late on this but I think we'd be running 64-bit systems or greater by 2038 (we're mostly running 64-bit systems now). Are we still running 16-bit systems today?

[@melbar]

It is now the year 1402 in Iran, no y2k problems in sight for some time...

[@windowsxseven]

In the year 2030 Stewart Cheifet, 130 years old, cybernetically augmentated and secretly the cold blooded killer behind Kildall's passing in 1994, stands atop a chasm. The last survivor of humanity, he watches over the remnants of San Francisco. As he gazes across the horizons, his eyes come upon the sight of Computer Chronicles playing in a 24 inch display, its owner long gone from the earthly realm. And for a brief moment, he shortly wept - for he had failed to predict mankind's unfortunate fate to the machines while he had the chance.

[@windowsxseven]

Stewart Cheifet stood at the edge, the weight of his long life and the consequences of his actions heavy upon him. The remnants of a world once teeming with life now lay silent, taken over by machines he had helped advance. The irony of his past haunts him as he watches the old episodes of Computer Chronicles flickering on the screen. In those fleeting moments, remorse pierces through his cybernetic augmentations. He remembers the time when he could have changed the course of history, diverted humanity from this catastrophic path. But now, as the last echoes of human existence fade, he mourns his failure to prevent their downfall. As he stands there, a solitary figure in a world of steel and circuits, he contemplates the relentless march of progress and the unintended consequences of his contributions to technology. With a heavy heart, Stewart Cheifet, the lone witness to humanity's demise, grapples with the weight of his own legacy amidst the ruins of a civilization lost to the very innovations he once championed.

[@BoomBox02]

Was that Reagan reading the book on the audible.

[@ryleitdept]

the sample audio book played thou LOLS

[@syferdet]

So, you're saying the ATM on the street corner will not kick out a stream of 20s at 12:00:00 am on New Year's Day then?

[@thabudmaster]

just another commercial exercise to get us all to buy new software/hardware & have something to fear.

[@abdielvelazquez773]

Just like climate change

[@imperiumcommentingnetwork4677]

Was born 2 weeks before y2K was supposed to "end the world"

[@HowieIsaacks]

I've been using a Mac since 1987. Macs were Y2K compliant without any modifications or updates needed.

[@JS-wp4gs]

So was literally every other computer in existence at the time. It was bs from the start

[@morbidmanmusic]

All computers were.

[@dbloyd2]

I thought the thumbnail of this clip was Mr Drummond from the 1980s TV show "Different Strokes". Another view at 15:47

[@broderperdurabo]

Old PDP, or older minicomputers soft ware had a problem.

[@ArtyomGalstyan]

Why couldn't they just reflash bios?

[@cardbored_]

Norton of that era was literally death, no one ran Norton willingly.

[@nitehawk4067]

Norton is a virus

[@unnamedchannel1237]

I don’t think they have ever unless sold by mindless sofa sales people

[@gm7717]

Back in late '99 when I was starting my career in IT, I was working in a small computer shop and I remeber that the boss found the Y2K issue as an opportunity to earn extra money from their customers :-)

[@SokolS125]

This has aged like milk.

[@tuduff]

Just another random video popped in my home screen? In 2020.

[@ThatGuy-wz3or]

I made ridiculous money updating PC's as a consultant before Y2k.

[@Amirichi]

I found that in his later years he speaks over the guests a lot.. I understand he was under time pressure but damn, let them spit out their sentence lol

[@barriewilson3052]

New years eve 1999, my town center had the biggest party of all time. No one gave a fuck about the millenium bug.

[@josem.rodriguez1121]

Lol the host is so frustrated that he doesn’t quit get the internet. So passive aggressive to the techs! He must be a tech wiz nowadays lol

[@barnacl437]

due to the damn 2-digit year display, we had a chaotic over the world.

[@BigEightiesNewWave]

I used Audible with my pocket PC in 1999.

[@Earthwirm]

Thanks Stewart for the free tank of Shell gas!

[@ObiWanBillKenobi]

28:28 You could call the 888 number to order a videotape copy of an episode.

[@MysteryD]

Fact: Computers never had a 19XX embedded into the CMOS chip. Nothing is embedded. The computer just counts up. 2000 came after 1999, so it simple went to the next number.

[@oldtwinsna8347]

The issue was with mainframe computing to which that wasn't necessarily the case. There were still a lot of applications running on PDP systems which were notoriously the bad apples when it came to y2k compatibility.

[@JS-wp4gs]

@@oldtwinsna8347 Nope

[@DripDripDrip69]

The issue was storing the year in two characters to save memory, counting up past 99 would either cause an underflow or overflow depending on the implementation.

[@MysteryD]

@@DripDripDrip69 Uh, but this actually happened 23 years ago, man. And it turns out... I was right.

[@Real_The_Goof]

Why is this video so quiet?

[@penklislawnmowing4508]

Love love to be the Historian who know about computers than the one who wrote the programs

[@Drago1995]

and after it's the Y2K38 problem "2038 bug" everybody is gonna have to deal with

[@thatguyontheright1]

***** It's already solved by going to 64 bit CPUs and Operating Systems.

[@Drago1995]

***** i know that but it can still cause some damage who knows maybe it will just pass by without anyone noticing

[@Kajayacht]

***** I myself have actually ran into that problem. I work with Call Center systems that control the menu and routing structures. A customer created some schedules that they could activate or deactivate in case of emergencies. They configured these schedules to run 24x7 until 2050 so that when necessary they just mark them as active. What ended up happening is that the system defaulted the date to 1/1/1970, thus making their schedules not work. Ironically I had actually read about the 2038 problem on wikipedia a few weeks earlier and knew what it was almost immediately, made me look like I was really smart :D

[@markarca6360]

This problem will repeat in the year 2030. (The last year in the firmware of PCs today is 2029).

[@NomadicDmitry]

A lot of discussion of a problem that was never a problem :)

[@Silligk]

I'm a big fan of that woman's accent

[@nelsonferrer8994]

Nowadays we have rechargeable cell phones those can tap without a keypad. But the problem will be on January 19, 2038

[@logicaloutlook]

I found one computer that had it an IBM 486 lol

[@kevdogyt08ti]

OMG ''The Y2K Bug'' ... LOL :D At first, that was quite serious. But then, it was OK...

[@Richardpasquinucci]

can you make it louder

[@andymate2006]

The Y2K thing was a scare campaign. Nothing happened when the clock went to 1/1/2000. Even with computers that weren’t Y2K compliant nothing happened.

[@Lee_1971]

Itellifix 2000 *only* $79 !!