"My computer has EMS"
"can you help please?"
Those who remember know how true that is.
The working week is no game, which is why The Register eases readers into the weekend with a fresh instalment of On Call – our weekly reader-contribute tales recalling the lighter side of tech support. This week, meet a reader we'll Regomize as "Dan" who told us of his first gig in tech: working in the repair department of a …
This post has been deleted by its author
While I have had a few in my long working life one stands out. My role was a customer support engineer but I only earned the company money when on-site with a customer so one glorious sunny Friday lunchtime in early summer I was bimbling about in the office doing make-work and he wandered over and commented that a day like this was best spent wandering on the beach. Taking the hint I suggested I should check over my kit so I could be ready for a short-notice call and left. A month or so later I got a call from him on a Saturday morning asking me to fly out to a customer site for three weeks, the flight was the following day but I just said yes and got packed to go. He always treated us with respect and he got respect in return, amazing how that works
My bosses have generally been quite good, but the one that showed support above and beyond was actually the boss at a company that I was sub-contracted out to.
We'd been working crazy hours. and were all generally stressed out, dog tired and fed up. One afternoon the boss (a very softly spoken Irishman) said, "ah, lads...you're all looking awfully stressed by all of this. Do you want me to sort out a visit to a local <ahem> massage parlour for the lot of you? Great bunch of girls there - do you the world of good. I'm happy to let the company pick up the bill"
I think we all politely declined
I've been lucky to have worked for fantastic bosses who I've known for pretty much my entire career. This year has been a bad one for me - diagnosed with prostate cancer, then taken into hospital and put on the critical care list with bladder sepsis, then (after I recovered) having my prostate (plus uninvited guest) removed. Added together I have had over 3 months of sick leave this year. My bosses response to this is to send me a get well card, a very large and very nice bowl of fruit, and to insist that I should not return to wok until I was absolutely ready for it.
Reminds me of a visit to Japan (about 35 years ago). I went to review the third-party inspection arrangements for a large, ongoing, supply contract and the supplier had offered to give me a tour of all their sites involved (what would have been a couple days of meetings evolved into a fortnight, the first week of which was a tour of Japan's main island). At one site, the plant manager took me out for dinner in the evening - a meal I'll not forget as it was a one-table affair, with all the food cooked in front of us (three: me, the plant manager and their UK rep, who had flown over to be my escort): a starter of abalone and Kobe beef for the entree. But that wasn't the most memorable part of the evening as, from there, we went to a private karaoke bar, where I was invited to duet with a young lady in full geisha gear. Singing a duet was fine, but the invitation to go into a back room to lie down seemed a step too far. I know it wasn't seen as anything unusual in the culture there at the time, and I didn't want to insult my host or the (very attractive) young lady - so I feigned ignorance/innocence until they decided it was getting late (and we had an early start the next morning, to catch the bullet train to Tokyo).
I still occasionally kick myself - but my employer had strict rules on acceptable hospitality :)
I had a boss who really new his job. As IT manager he always took ALL the heat for network problems, and never let other bosses breathe down our necks while we fixed the issue. He never lost his cool and knew there was time for a post mortem LATER... I still keep in touch with him.
Not wanting to spoil any parties, but that's really not the answer. The fact that everyone was hesitating implies that they're not all young bucks with too much libido and not enough control. What if one of your colleagues was in a relationship, or simply had taller moral hurdles to overcome? Some of you go and leave a few behind? Some of you benefit from <n> quid's worth of non-salary benefits and the others - who have worked just as hard - don't? The boss is left in the awkward position of having to find another way to compensate those workers, or be seen to be a bit of a prat, and the workers left behind become a bit more distanced from those who went because they were "too stuffy". That sort of thing can really wreck a team.
Surely there are other things which would be more acceptable? A half day leave, to be taken when wanted, a team dinner at a convenient time (or just then-and-there), an after-hours visit to the local with the tab on the company card - acceptable even to many teetotalers these days when pubs often serve imbibe-able drinks with no alcohol involved.
Sometimes it's as simple as filling in an "extra hours" timesheet and getting the reward in the paypacket at the end of the month. Probably worth a darned sight more than a visit to the local knocking shop, and certainly both morally and physically safer. Some companies (struggling to think of any right now, but I know there are some) even have official reward schemes which aim to remove these problems.
Of course, many companies just ignore those of us who put extra hours in to get a project over the finish line. Do it too often and it begins to be taken for granted.
M.
The memories.
My experience of an Apricot was the fun of the Ram upgrade (basically strip half the internal chassis out to fit the add on board over the existing ram), and bodging it to let me hook a cheap CD-rom drive up externally.
That and the MFM or RLL drive it came with that didn't like it being too cold or too hot, so I had to place the machine in just the right place in the living room in the winter, too close to the window and it wouldn't boot, too close to the fire and it wouldn't boot, but there was a sweet spot where it was reliable. It also taught me to never trust a hard drive and make sure I always had backups on multiple media ;)
On the plus side it let me experiment and taught me not to fear working inside a computer, so much so that the auction bought 486 I picked up for a friend didn't worry me when I saw an DX4 chip for a fiver and went to install it (no manual, but the motherboard had the settings screen printed).
Apricot used Rodime hard drives. Often these would fail to spin up on a cold morning but would work OK later on. It turned out that condensation on the platters caused enough surface tension with the head to stall the motor.
The OFFICIAL work-around was to slap the right-hand side of the box. This caused the heads to bounce, and the platters to start to spin.
The Apricot's predecessor, the ACT Sirius 1, had a bad batch of hard drives. They had undergone low-level format in a California summer, and were unusable when lower temperatures shrank the platters.
some of our students want to become software testers, without realizing this does not necessarily mean playing games until they crash. They look so disappointed when we teach them software testing is usually a lot less fun.
Still, it's a good job when playing games IS part of the job.
From what I've heard, playtesting games involves doing every single weird thing you wouldn't expect players to do, so you'd spend hours running round a single level walking along the walls, jumping at odd places and generally trying to test the bounds of the play area to destruction. Very little of it involves actual "playing".
As for generic software testing, it's the whole "software tester walks into a bar and orders 1 beer, 5 beers, -1 beers, fjioewjiofewj beers, 1.2389028190 beers, etc"
"As for generic software testing, it's the whole "software tester walks into a bar and orders 1 beer, 5 beers, -1 beers, fjioewjiofewj beers, 1.2389028190 beers, etc""
I believe the next line of the joke is "and then a player walks into the bar and orders 2 beers and the bar burns down"
Trying to force edge cases is helpful but doesn't always work, sometimes you just need to play test the same part of the game 100+ times to see if you find any bugs.
I used to do game testing many, many years ago.
I'd get a floppy disk in the post for a game that had to be tested. I'd spend a week faffing around with it and then send a report back. I can't remember how much I got paid though (it wasn't a full time job, and it was very sparodic).
> play testing games [etc]
Pretty much what heard too. Speaking of which:- Old 'Penny Arcade' on game testing
Software testers do seem to get paid an inordinate amount of money - for just testing stuff!its not like they're making the software .
Well, consider that you wouldn't have to pay software testers that much if the devs would write proper software in the first place.
Looking at the latest releases from Micros~1, one can clearly see that the devs are incapable of that feat.
In the days before PC's became widespread, I was writing software for a Set top box, Internet access device.
We needed to produce a net-nanny filtering system.
A lot of intelligence went into designing what we thought could isolate most of the crud that was on the Internet at the time, but we needed to test this.
My boss employed a lad straight out of University to try to access Pron sites all day long. The thinking being that he would have a wide knowledge of suitable test sites!
He only lasted 3 months before he left to go abroad to be with someone he had met via one of the sites, and we declared the filters good enough.
During the next few months a little telemetry (only settings and not sites) told us that nearly 90% of people turned off the net nanny!
Icon as the lad always had one on his face.
I worked for a (then) major web proxy manufacturer in the early 2000s. We had to get configs from customer appliances, and logs, and the contents were eye opening. Who in their right mind would actively search for some of that stuff!
And we had to have unfiltered internet access too - "boss, I'm looking at playboy.com because the customer says the adult URL category isn't being filtered properly ..."
I use nkt.net ( or xkcd) Its blocked at my work under the "fun" category. Its quick to load and is a good test if I've bypassed the proxy successfully
Whats that? you shouldn't be able to bypass your corporate internet filtering just by adjusting your browser settings ?
IKR ? crazy times.
I believe the magazine generally recommendeds *not* actually listening to big, noisy sirens, since doing so has a tendency to entice people towards their doom.
Instead it tends to focus on their, er, massive hooters, while trying to avoid the strange reality of their bird-like feet.
Many years back, I was working with a mobile network configuration team (aka databuild) during a major network change. It was decreed that we determine the top ten (or whatever: it was a long time ago) websites that our customers use and, after the change, spend some time ensuring that they are all accessible and usable.
This was in the days before social media was much of a thing so the test list contained a sizeable number of pr0n sites. Not being one of the main team, I was not asked to help; but as testing jobs go, it sounded like one of more interesting.
I may have broken the filter in Surf Controller (about 20 years ago) when on a training course at the HQ.
They asked us to try and get through the pron filters.
Since they primarily just checked for the amount of flesh tone on show, I went for sites when the flesh was not showing.
They were surprised when it took me about 30 seconds to show them a site that you should not show to your Mother...
We quickly went for a tea break while the trainer reported to the developers.
Crafting config.sys files to make different things work was a real skill. DR-DOS made that a lot simpler by allowing you to set up a boot menu for all the different settings you need for different games and Windows.
Wing Commander 3 was the one with the video clips featuring Mark Hamill and Malcolm McDowell slumming it, right?
Ph yes, the joys of hand-editing and tweaking config.sys, re-ording the sequence of device drivers, to get the highest free RAM below 640Kb
And then runing QEMM386 against the same original config.sys, man vs machine!
The joys of a 286 PS/2 and 2mb of expanded RAM.
And (unrelated) making autoexec.bat sit up and make coffee with juficious use of ansi esc sequences, nested manus. There was an awesome book, Advanced DOS Batch File Programming, Dan Gookin. My bible at the time.
Ugh. QEMM. Not a pleasant memory.
We had 486 machines at one job for schematic capture (Viewlogic) and they would crash reliably if you opened a second page or had too much circuitry on one page. I tolerated this for a few weeks, then started thinking about alternatives. We did have ONE Unix machine with Viewlogic on it, but it was located in the lab, not the best place for deep thought.
However, at the time, I was just getting into Linux and the X windowing system, and the thought of adding a second Linux HDD to my work machine and using it to run an X terminal off the Unix machine entered my mind. This was easily done, and now I had a PC, as an X display, running Viewlogic off the Unix machine...which did NOT crash if I opened too many pages. Nor, as a bonus, did my 486 crash any more, QEMM being out of the picture, since I was running the much more stable Linux.
Since I had added a second HDD, the original Windows install was untouched and could be booted into as normal for email, etc.
The boss was not as perceptive, he seemed displeased that I had messed with the corporate hardware, but acknowledged that I was getting my work done, and left me alone.
Or be lazy and forgo the use of an MDA which then let you get base memory something above 700 kB.
Ahh the days of holding old PCBs stacked full of soldered RAM chips over the gas stove to desolder them, then popping them in iSA memory expansion boards to get I think 4 MB or maybe even 8 MB of very slow memory. Used these in a 486 when Win NT (4 I think) refused to installed as there wasn't enough memory (I guess I had 4 MB total in SIMMs), so lobbed these cards in and it passed the memory check only to take about a day to install thanks to the fine performance of this old RAM :)
NT worked fine with 4 MB after removing these...
I did something similar for [RedactedCo] after a couple years and at least one promotion, only that It was a "select what machine I'm booting on" to load the correct network drivers, log into the local site's domain controller, and pull down the appropriate windows XP image for that machine. And I managed to cram it all on a single 1.44 Mb disk, with some assistance from a network share for the "connect to the site's image server and image the machine" portion.
I've long since left that role, but that was one of the more interesting tasks I was given.
(We've long since moved on to the joys of PXE boot and leveraging SCCM and the deployment tools for bootstrapping new machines.)
Same, for me it was mostly CD or not and sound card emulation modes - the mouse stuff on my system could be reconfigured live and didn't need config.sys support. I had five or six combinations in all, one of them being for booting into Windows.
Kind of nice not to have to reboot the machine to switch from one game to another, isn't it? (Although rebooting into DOS didn't take very long.)
Yes, it is the game with Mark Hamill, Malcolm McDowell and Thomas Wilson (Biff from Back to the Future Trilogy).
I recently purchased the game from GOG.com and tortured my WinARM box using ARM64 compiled DOSBox-X. It runs like a dream, never crashes and no MemMaker needed in DOSBOX-X, with plenty of free RAM below the 640KB barrier, and presumably 8-16MB available above.
I had only a 386DX40 when it was released, so no hope of playing it then. It is almost too easy now... :o)
MS-DOS 6.0 and later introduced boot menus in config.sys. There was a way to get MS-DOS setup to run some stuff that generated two files that were pretty accurate. You could take what files had been generated and then munge them with other configs to get a multi-config setup that worked for a *lot* of ways of doing things.
Of course, most people didn't know this because they didn't get the DOS manual(s) with the PC they bought. I got the MS-DOS 5.0 box (with disks and manual) and the same for the MS-DOS 6.0 upgrade, and I spent weeks studying the manuals and intricacies, so EMM386 and HIMEM's occasional bad interactions didn't scare me. For DoubleSpace (DriveSpace) with Windows on 4MB RAM, you did have to make HIMEM and EMM386 play nice...
In the early 80s we used to play adventure games at lunchtime. One of the games was annoyingly difficult because the burning branch went out after a set number of goes, and there didn't seem to be enough goes to do what needed doing to get out of the darkness before it went out. So we did a memory dump, did a move that didn't do anything then dumped the memory again and compared them. We found the bytes that decreased by one, did a few more tests to confirm which was the branch, then set it to FF.
Can't remember the name of the game - it was a Colossal-Cave type. The aim was to collect jewels and you ended up wandering around on the face of a giant statue.
@Prst. V.Jeltz
My work W11 machine just had a BSOD and then rebooted, no games running on that just lots of dreary work related stuff (Visual Studio, IIS, SQL Server, docker, RDP, teams, outlook etc.) .. and all the corporate extra performance / resource killers such as inventory, threat / malware detection etc. software. So does get a lot of hammer. Games not required for BSOD in Win 11.
Yeah, but still not clear whether it was W11's fault unless you check the culprit with Nirsoft Bluescreenview. Albeit the minidump may contain the wrong .sys listed instead of the actual culprit, the chance it shows the real culprit is high.
Usually: Run the manufacturers auto-update tool which should get the newest tested driver, BIOS and firmwares combination, may fix your BSOD. If you have a laptop with a dock of the same manufacturer run it with the dock plugged in, quite often the docking stations get firmware updates too.
Back in the early 90s (in my first job), I convinced my boss to play games (OK, OK, Solitaire)...
This was early in Windows days (3.1?) and he came into my office with a new laptop and a copy of windows and office and told me to get it working. OK, no problem. Install..install..install..lots of floppy swaps later...
I took the machine into his office and showed him it working.
"Great, now how do I learn how to use this?"
Thinking furiously, I made up some bullshit on the spot. "There's these games <here>. I recommend playing Solitaire. It sounds silly but it will get you used to basic functions like moving the mouse accurately, clicking, drag'n'drop and so on". He looked skeptical, but agreed to try.
Two days later he came back into my office and slapped me on the back and said "That game you told me to play? It worked! Thank you"
...If my PC version of GTA was constantly crashing after I disabled memory overclock.
Windows loaded fully stable, but barely loading the single player version caused THIRTEEN different blue screens of death, until I decided to kill AMD DOCP / XMP profiles.
It then spent 18 hours straight without a single crash.
Best 18 hours I had after the memory upgrade.
I avoid Corsair due to some experience with their "Quality". RAM only when they use their own chips. Crucial (aka Micron), Samsung, Hynix, and a few others. But many, like G.Skill and Crucial, don't produce their own chips, and you have no way of knowing beforehand. So at that point I'd more likely to say that Corsair put too optimistic timings in their RAM.
I wouldn't know, I have a small pile of Vengeance LPX and the only problems I've had were installation errors (not enough force) and crashes from fooling around with timings. Zero problems when running at promised speeds (fastest DDR4-3200, faster memory isn't really worth it and there's really no guarantee memory controller, mobo and memory play well together).
This story just reminds me of the amount of time we had to spend in memmaker in DOS tweaking physical and virtual memory for different applications. Also remember manually tweaking config files when the setup utilities for DOS games never set the right sound card or you needed to play about with it until it worked properly.
Those were both simpler and much more complicated times.
Had a similar job once, back when the white unibody MacBooks were still in service and they had a nasty issue with the display panel which would cause it to fade to white and become unresponsive. Someone sent in a machine with that issue, and usually it'd fall over during the diagnostic testing, but this one didn't. So, I broke my general rule of not poking around in the customer's files (because if it were my system, I wouldn't want someone doing it to me) and found a copy of some movies like Rocky 3 and The King's Speech. So, I got to sit around and watch those legitimately claiming I was testing the machine waiting for the issue to occur. Which, it never did as I recall. That was the only customer who ever managed to call me (I worked in a repair depot) and IIRC, I had some old store stock unit that couldn't be resold for one reason or another, so got the approval to just swap the display panel with it. Fortunately, that was one of the few major components Apple didn't serialize (at least not that the repair tech had to put into GSX) so it wouldn't cause issues if the "replacement" panel was also bad.
Ah yes, trying to get the memory settings exactly right to run specific games. I remember it well...
I seem to recall that most of my memory issues were solved using QEMM (the ol' Quarterdeck product), which removed the need to use HIMEM and EMM386 altogether, and worked better with the MSDOS6 multi-config option than native MSDOS6 when optimising memory.
Morally and in some cases practically, shareware still has to be paid for... I missed, does our poorly paid hero actually have a PC at home?
Correction - he's a student with credit card debt. And a car. And the price of the game is given as the reason not to buy it - not the matter of having enough of a PC to run it.
Presumably he has access to computers in college. But not for that.
This post has been deleted by its author
"Morally and in some cases practically", as per the comment you're responding to.
Most shareware products were licensed on the basis that you would pay for them if you continued to use them after a certain amount of time - though of course most people did not. Hence the proliferation of "part 1 is free, pay to get parts 2-N" model, which provided an incentive to pay.
We are talking about shareware games here, those usually only had a few of the game levels and that's was it, once you beat those your had to buy the full game for the rest if you wanted more.
Of course some games were so hard or had so much content on the shareware levels alone you could get months worth of fun on those.
I specifically remember a level in the shareware version of War Wind (You can nowadays get the game for free on Gog) that you could keep playing for hours. Same for the shareware version of Conquest of the new world.
No - and you can read about this in Wikipedia.
I think I avoided using shareware when I couldn't afford even the reasonable registration price - and at work it was difficult to convince a boss, "Why should we pay for it if we got it free?"
An exception is touch-screen keyboard software, "FITALY", that I use for disability - and that stops working after two weeks unless paid for. And then, the boss and a BOFH type don't see an issue with un-installing and then re-installing software every two weeks to defeat the copyright. However, my employer did actually pay for my "FITALY" to use at work.
Unfortunately it seems that its main programmer died early. The software still is versatile and useful.
An old friend worked for a company and his boss let him set up a sever for Wolfenstein, then BF1942 & the Desert Combat mod, and also Wolfenstein Enemy territory... this was just outside of the fiewall so wouldn't clash with anything on the company network.
Turned out to be good for the company in the end.
We ran into an issue where the server would stutter for a second on a regular basis... after a lot of investigation both internally and externally. BT found some misconfigured equipment at the exchange, fixed it and the problem went away.
It also happened to fix an issue they'd been trying to identify with random transactions failing on checkout... the boss of that little company was happy for the game servers to remain up for our amusement.
Spent some time working graphics device drivers. Sometimes the bug was that some frame of a game in level 7 didn’t display correctly. Most of us had no chance reproducing these bugs. Lucky enough we had one guy capable of going through these levels.
Worse was a bug in the display of a software installer (the installer itself worked fine). You had _one_ chance of debugging it. After that you had to restore from some backup to run the installer again. Took hours.
I had the two pirated BASICA chips and PC DOS (IBM"S variety of MS DOS) on one of my systems. I tested dB III and IV data sets for out of range entries a lot. Once a consultant returned data where he had merged four fields into a single field "because it was really just one field." They weren't. It took an hour to undo his work in order to merge the critical fields with our database. I explained that the format was specified by a university museum, worked with _their_ cataloging system and that we were deducting my time from his bill, since nothing in the agreement included permission to futz with data formats, and worse, types. I did not buy him a beer.
this story and last weeks seem to have unleashed an epidemic of decent bosses and managers. :)
I would have loved to have been a fly on the wall when the manager offered the whole overworked team a treat at the local horizontal relaxation facilty - except I would have fallen off the wall laughing.
I suppose its the thought that counts. Working in Eire might have hidden benefits. :)
Must have been a while ago as teams now tend to be bit more diverse in that department. :)
At Uni I remember a bloke, on his 18th birthday was dropped by his classmates, with a handful of cash at such a facility. Much later he told us he waited inside for 30 minutes, split the cash with the lady and left slightly wealthier with virtue intact. Innocent yes. Naive not. ;)
Absolutely, I used to love jobs where I was going because someone was having trouble with a game. Solve problem, sit and play games with the customer for a while.
My favourite was probably an old man, in his 80's. This was back in the Windows Millennium days. He called me for a "consultation" (oooh, buzzwords) because he was convinced that he needed more memory because his Train Simulator game was freezing up (actually just hitching, freezing was his word). He already had 384M which was almost too much for a crappy Win9x OS like WinME (vcache mechanism sucked, moreover, at 512 RAM you could get blue screens if you didn't limit it).
He didn't even want me to touch his computer, but I convinced him that in 10 minutes we'd have his game working and it won't cost him a dime, if we upgrade Nvidia drivers and DirectX runtimes. So I did, and it did. I sat with him for quite a while, watching scenery go by and him tooting the whistle with a big smile on his face.
I think I just charged $30 for the visit back then, but my biggest payment was that boyish smile on his face while he was playing his Train Simulator game :-)
P.S. Of course, other fun times were fitting someone up with a new graphics card and then testing it with them.
In the early 2000's, I was tech support for SGI Visual Workstations, Diablo II was used to test the graphics performance. I had 4 or 8GB of RAM on these things with Windows NT. When the boss came around, I would say I am testing the graphics. I was waiting for calls, when a call arrived, I would switch to our app and die in the game. Fun times.
I remeber in the early 90s having to do security night shifts at SGI in theale. the day shoft used to get the noce jobs of testing equipment by playing games for the company as it was cheaper to the security staff to do it than thier engineers.
I will add it was nigh on impossible to get on the day shift ,I was stuck up the road at DEC park in Reading. Was only a fill since being made redundant thankfully
Back in the days of the Solaris 32-bit to 64-bit transition, I had horribly tight deadlines, as head of the distributed systems team at a regional oil and gas explorer, due to a very big seismic data analysis project.
I had a datacentre recently filled with Sun servers with Fujitsu SCSI RAID storage arrays with rebadged host SCSI cards that were randomly crashing, corrupting filesystems, trashing files in hard to identify ways, and all this in the days before ZFS. The vendors were of course finger pointing at each other and the clock was ticking.
We realised that the thing that sometimes, but reliably sometimes, crashed the boxes was ... doing an Oracle install. So I automated the Jumpstart for about 40 of the systems to do a clean OS install. Then do the Oracle install, and then report success, and start the process again. The boxes that failed didn't and a watchdog script emailed me as well as CCing my old Uni email account over the newly installed ISDN E1 internet link. If it was after hours, I'd run 5km to the office (I was fitter then!). I hand-noted the console errors into a journal.
About 4 weeks into this regime, I'd been working 28 days straight, and discovered the joys of working on Saturdays and Sundays - no distractions! - but getting well and truly sick of the process. Analysis of the console crash text was getting somewhere, the Sun (esp?) drivers were the probable cause, now we were into Monte Carlo testing of config options and continuing to complain to Sun and Fujitsu account managers every work day.
Building security noticed that I was in constantly, and barred me. The board negotiated a deferred beginning to my enforced home-time of another week.
Finally on the same day that Sun advised us that they'd identified a regression in the 64-bit ethernet (?maybe?) drivers, that we could fix by configuring them to run in 32-bit mode, we found a memory mapping in the bottom 2Gb of memory that gave us non-crashing boxes.
I wish I'd spent that time playing games.
For a few years in the Early 2000s till 2010 I was the hardware introduction engineer for a large MOD project and therefore every new piece of equipment except servers and network components came through me for selection and testing before being passed to Integration and Test
Screens Mice keyboards and PC's where the best as the best way to test this kit was to literally play games as well as office applications.
You'd be surprised how much equipment would fail screen refreshes and memory issues when under stress and slow refresh rates to a crawl. At this time we where also playing with full 3D graphics using screens which didn't require the silly glasses , that was fun with flight simulators in high terrain areas. on a 40 inch LCD on my desk.
Ahh those where the days