Slashdot Mirror


Windows 3.1 Glitch Causes Problems At French Airport -- Wait, 3.1? (vice.com)

OakDragon writes: Microsoft has tamped down the earth on XP's grave, steered Internet Explorer toward the nursing home, and is trying to convince everyone Windows 10 is a bright up-and-comer. But in the Paris airport of Orly, a system called DECOR — which helps air traffic controllers relay weather information to pilots — is running on Windows 3.1. That program suffered a glitch recently that grounded planes for some time. The airport actually runs on a variety of old systems, including Windows XP and UNIX. Maintenance is a problem. There are only three people in Paris that work on DECOR issues, and one of them is retiring soon. Hardware is also an issue. "Sometimes we have to go rummaging on eBay to replace certain parts," said Fiacre. "In any case, these machines were not designed to keep working for more than 20 years."

199 of 406 comments (clear)

  1. Virtulize? by Henriok · · Score: 4, Insightful

    Wouldn't virtualization be a viable option here?

    --

    - Henrik

    - when the Shadows descend -
    1. Re:Virtulize? by selectspec · · Score: 1

      Or emulate.

      --

      Someone you trust is one of us.

    2. Re:Virtulize? by andreas.hummelbrunne · · Score: 1

      You really think anyone has written hardware emulation-modules for hardware that was still running WIn 3.1?

    3. Re:Virtulize? by avandesande · · Score: 4, Insightful

      There might be some weird ISA interface to a radio or something that you can't virtualize-

      --
      love is just extroverted narcissism
    4. Re:Virtulize? by known_coward_69 · · Score: 4, Insightful

      this is how i first learned about computers in college in 1992. every project was a huge undertaking. you spent months or years planning it and selecting a solution. months or years deploying it and then supporting it and maintaining it. every project was supposed to last for years or decades. none of this, hey lets buy some servers this month to replace something

    5. Re:Virtulize? by Anonymous Coward · · Score: 2, Insightful

      Yes, it's called DOSBox.

    6. Re:Virtulize? by Rei · · Score: 1

      If you want to fund the migration of a (almost assuredly large and complex) ancient system that has to deal with countless rare edge cases, be my guest, I'm sure they'll greatly appreciate your generosity.

      --
      Hello from Sputnik 2. I am receiving you.
    7. Re:Virtulize? by Anonymous Coward · · Score: 2, Informative

      I was able to create Virtualbox VMs with windows 3.1, 3.11, and even DOS 3.3 (!), all with networking enabled, and I even browsed some websites with them. I mostly used this guide:

      http://www.kompx.com/en/arachn...

    8. Re:Virtulize? by Anna+Merikin · · Score: 2

      Uh, no. Unix/BSD/Linux uses the F1...F10 keys for OS functionality (virtual desktops) where DOS apps typically used them, if at all, for internal functions. WordPerfect, for example, was useless on DOSemu or DOSbox for this reason as all software actions found in GUI menus were activated with these keys, which *nix clobbers,

    9. Re:Virtulize? by prunus.avium · · Score: 2

      The problem is not likely the OS or software running on that PC. The problem is far more likely to be a specific piece of hardware on that PC that is used to communicate with some other system.

      Remember Windows 3.1 did not have any native network stack. You had to buy or download a free network stack separately (Trumpet WinSock, anyone?). So any interface that came out of the PC was likely some proprietary protocol that had some "interesting" drivers that loaded before Windows 3.1 started and hooked directly in to the BIOS interrupt tables.

    10. Re:Virtulize? by Rei · · Score: 4, Insightful

      You have no clue of the complexity of these systems. A three-man team is sufficient to hobble them along and keep them functional, not to port them. We've had an ongoing project to port one of our systems from AIX to Linux here for much of a decade and it's still only partly done, and we have a much larger team.

      ATC systems sound simple on the face of them, but they're so ridiculously full of diverse, unreliable datasources (which can conflict with each other) and edge cases that they have to deal with it's not even funny.

      --
      Hello from Sputnik 2. I am receiving you.
    11. Re: Virtulize? by Anonymous Coward · · Score: 1

      Too pussy to verify the info. It is not Windows 3.1, but Windows NT 3.1. And moron enough to believe all this clickbait titles.

    12. Re:Virtulize? by gnupun · · Score: 1

      It's management's fault to not modernize the OS and hardware. They want to save design costs not updating software/hardware, and they get away with it for 25 years or so, but then if something critical fails, this happens... the whole system is shutdown.

    13. Re:Virtulize? by bhcompy · · Score: 1

      If it ain't broke, don't fix it. There's a reason that Pick is still in use 50 years after its release.

    14. Re:Virtulize? by Coren22 · · Score: 1

      https://en.wikipedia.org/wiki/...

      Next issue?

      This thing takes weather reports and pipes them to systems on airplanes. Very likely, the airplanes are newer than this system. Heck, you could replace the system with iPads in every cockpit for the cost of a couple of repairs to a system that old.

      --
      APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
    15. Re:Virtulize? by aardvarkjoe · · Score: 4, Informative

      In 25 years, there've probably been 25 managers who have walked away with fat bonuses for keeping this department under budget. The current one will get a slap on the wrist. They're just playing the odds to get the best outcome for themselves.

      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
    16. Re:Virtulize? by known_coward_69 · · Score: 1

      SpaceX is learning to do stuff cheaper than NASA has done it for decades. NASA has been doing resupply missions long before there was a SpaceX. Call me when they do something new like design a rocket to land a man on Mars or something else that hasn't been done by Boeing or one of the other big contractors out there

    17. Re:Virtulize? by known_coward_69 · · Score: 1

      and when you port it, the solution has to work right the first time. every time. or people die. none of this testing and patching in production like the kids do today.

    18. Re:Virtulize? by cpotoso · · Score: 1

      Trumpet WinSock... AH! Those were the times!

    19. Re:Virtulize? by MachineShedFred · · Score: 1

      Now only if there was some kind of alternative OS to UNIX/BSD/Linux that doesn't act that way with F-key scan codes...

      --
      Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
    20. Re:Virtulize? by jopsen · · Score: 2

      It's management's fault to not modernize the OS and hardware. They want to save design costs not updating software/hardware, and they get away with it for 25 years or so, but then if something critical fails, this happens... the whole system is shutdown.

      If it lives for 25 years with minimal cost, is this really a bad strategy?


      When I write software now, I try to aim for it to live 10 years without any maintenance (not always realistic, just an idealistic goal).
      Then I deploy it and stick my head in the sand. Most of my systems won't live for 10 years, but if something ends up doing so, is this really a bad strategy?
      I think stick your head in the sand and wait 25 years for the system to crash and someone to call you could be a cost efficient strategy :)
      (Granted, in the airport industry, you might want to make sure "system crash" != plane falling out of the sky)

    21. Re:Virtulize? by parkinglot777 · · Score: 1

      SpaceX years ago ...

      And they are still trying to complete their project, aren't they? Also, there is NO human involve yet which would make the task way lots more critical.

      There is a rule of thumb with this type of software, if it works, don't touch it. The software had been running fine for decades. It is critical if it all of the sudden breaks (as it did just now). Doing anything with the working version would easily introduce other kind of bugs and would become a much bigger mess trying to find/fix them. It would be OK to port/update a software to match newer technologies if the software is not this critical. It is obvious that you have never dealt this critical type of software...

    22. Re:Virtulize? by MachineShedFred · · Score: 3, Insightful

      and I'm sure there are common USB-to-ATC radar adapters you can just get on Amazon.

      Many times the reason you see an antiquated OS still being used is because there was some very specific software written to talk to an incredibly unique (and expensive) piece of hardware, and that software just won't work in any other configuration. Also, they just can't shut the system down for a few hours in order to fuck around with it, so there's that.

      --
      Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
    23. Re:Virtulize? by MachineShedFred · · Score: 1

      The good thing is that we've had PCI to ISA bridge chips for at least a decade: https://www.altera.com/product...

      So unless they are doing some seriously weird low-level signal nonsense, you would be able to get past that with some hardware hackery.

      --
      Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
    24. Re:Virtulize? by gnupun · · Score: 1

      If it lives for 25 years with minimal cost, is this really a bad strategy?

      It is. Other managers follow the same strategy and that's why COBOL still exists. Then you have to hire scarce COBOL programmers at a higher price building an inferior system. Good for them it bites them in the ass 10, 15, 20 years later when the costs blow up.

      They could've contracted maintenance of their software/hardware to some company and kept costs down while controlling how often the system was updated.

    25. Re:Virtulize? by petermgreen · · Score: 1

      As I understand it "system crash" doesn't mean planes falling out of the sky but it does mean massive disruption if it can't be recovered from quickly. They need the automated systems to manage the density of takeoffs and landings at busy modern airports. If they lose that automation then flights have to be held/diverted/cancelled to keep the number of plane movements in the problem to a level they can manage manually.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    26. Re:Virtulize? by Cacadril · · Score: 1

      Everybody explaining how hard it is to replace old sw and hw... How come they managed to implement it in the first place?

      Build a new system working in parallel with the old one. Adapt the planes to communicate with both systems og switch them over to the new one.

      --
      There is no substitute for common sense. Especially, no body of rules will do.
    27. Re:Virtulize? by tnk1 · · Score: 1

      They needed to upgrade it years ago. That's from a simple parts availability/maintenance standpoint. Yes, it works. That's not the point. Eventually the people who actually know how this works will retire or die. That would be okay if they were planning on replacing it. It doesn't sound like they are. Luckily, this doesn't feel like a mission critical system, but it's still dumb that this has been allowed to go that far.

    28. Re:Virtulize? by Blaskowicz · · Score: 1

      Motherboards with ISA slots never stopped being available, you can get one with socket 1150 for instance (Haswell processors).

      I am wondering if that uses a PCI (or PCIe) to ISA bridge, or is it still using the ISA bus directly?
      The Low Pin Count bus is ISA compatible (but runs at 33.32MHz on fewer pins), gives real parallel, serial, PS/2, real time clock etc. on even the very latest hardware. Perhaps some simple added circuitry allows to derive a couple ISA slots from it, not exposing a bridge to the hardware and OS in the process.

    29. Re:Virtulize? by MachineShedFred · · Score: 1

      It's bridged. Intel's chipsets haven't directly had an ISA bus in years - Things like ISA, PS/2 ports, etc. hang off of the PCI bus on bridge chips.

      --
      Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
  2. Which version of unix? by Anonymous Coward · · Score: 1

    The airport actually runs on a variety of old systems, including Windows XP and UNIX

    Unix isn't necessarily old, grasshopper.

    1. Re: Which version of unix? by Anonymous Coward · · Score: 1

      Freebsd , opensolaris , I think unix , not linux.

    2. Re: Which version of unix? by Anonymous Coward · · Score: 1

      Unix has been replaced by Linux, fool.

    3. Re:Which version of unix? by Anonymous Coward · · Score: 1

      Yes I do, but what the grasshopper said gives away his age and experience just as well, doesn't it? Of course, you'd never realize that if your own age and experience is even less.

    4. Re: Which version of unix? by Anonymous Coward · · Score: 1

      Call your school and request a refund. Leave your nerd card on the counter, and walk out that door.

      You are a disgrace. You're an idiotic disgrace. You are a gormless knob.

      And some background: BSD, Solaris, and OS X are all Unix. Linux is a Unix-like system. It acts like a Unix but is NOT a Unix.

    5. Re:Which version of unix? by armanox · · Score: 1

      If you're going to use that, at least use it correctly...UNIX means it is a full POSIX compliant Operating System, like Solaris, IRIX, or AIX. None of that nasty GNU stuff needed.

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
    6. Re: Which version of unix? by Kiaser+Zohsay · · Score: 1

      BTW: taking into account the age of the systems I can make a bet they use HP-UX since I worked on both systems 'in parallel' in the early nineties.

      Really? You've been around that long, and still have not learned not to feed the trolls?

      --
      I am not your blowing wind, I am the lightning.
    7. Re: Which version of unix? by danmoran · · Score: 1

      Unix has been replaced by Linux, fool.

      Not even close to being true. Linux has its place, but Unix is alive and well.

    8. Re:Which version of unix? by idontgno · · Score: 1

      None of that nasty GNU stuff needed.

      Unless the sysadmin has a brain, in which case she installs the optional but ubiquitous GNU userland packages and places them first in execution paths. Because the UNIX native utils suck dead donkey balls.

      But yes, in those true UNIX systems /usr/bin and /usr/sbin is probably pure UNIX heritage, for good or ill.

      --
      Welcome to the Panopticon. Used to be a prison, now it's your home.
    9. Re:Which version of unix? by jellomizer · · Score: 1

      If it is called Unix, then chances are it is fairly darn old.
      Otherwise they would be calling it Solaris, xBSD, OS X...

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    10. Re: Which version of unix? by jellomizer · · Score: 1

      GNU = GNU Not Unix.
      GNU/Linux is not Unix

      GNU systems including Linux are very Unix like. But have none of the original Bell Labs Code. It isn't a Fork of Unix, but a new product.

      GNU was derived as a response to some legal and copyright issues in the early 1990's.

      GNU is GPL but GPL is how they chose to license the System.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    11. Re: Which version of unix? by EmeraldBot · · Score: 1

      It isn't a Fork of Unix, but a new product.

      I don't dispute that GNU doesn't base on the original Bell labs Unix code, but is instead a full rewrite in order to promote FREE SOFTWARE. But all these Forks of the Unix code base, they aren't real UNIX anymore. Because why do you fork something. Do you do it in order to create the same piece of software? No, you want to do something different, chose a different path. That's what all these operating systems did you regard to as being the "real UNIX". Them chosing a different path is completely okay, its nothing wrong. Its just that BSD isn't an Unix anymore.

      Now to the GNU operating system. Why did they chose to _rewrite_ unix, and not just create something entirely new? Because they wanted to create a free _implementation_ of unix that would work just like the original Bell labs unix worked, so that software could easily be ported, and improvement patches still could be shared freely over the internet, just like in the old days.

      The name "GNU Is not Unix" was chosen in a joking manner, just like YACC for "Yet Another Compiler Compiler". It doesn't reflect the truth.

      So, to summarize, the GNU developers did want to keep as close to unix as possible, in order to make life easier for people who want to migrate, and to provide a general-purpose base for free sharing of modifications and improvements. The forkers like the BSD team however, wanted to tailor unix for their needs, for their specific use-case. Of course the operating system becomes something different in the process.

      Except that the HURD kernel (GNU's native) is radically different from any UNIX kernel, Stallman disagrees with all the unix's licenses, the GNU project doesn't endorse or even accept the legitimacy of any UNIX, and several very important GNU tools (emacs, gcc, gdb, etc) actively violate UNIX philosophy.

      You've got it backwards. Stallman set out to make a completely free (well, by his definition, anyway) ecosystem of tools. He actually didn't (and probably still doesn't) like UNIX philosophy very much, they just happen to have done much of the work for him. In contrast, even though they don't use any of the originial code due to lawsuits, the BSDs aimed to make an opensource reimplementation of the UNIX ideas, albeit it with different focuses. All of them stay true to the originials, and if you were to use OpenBSD or FreeBSD for a bit, they're a marked contrast to Stallman's dream of a modern day lisp machine.

      --
      "Set a man a fire, he'll be warm for the rest of the night. Set a man afire, he'll be warm for the rest of his life."
    12. Re:Which version of unix? by armanox · · Score: 1

      The only GNU package I find that I really miss on other operating systems and usually build is the bash shell. POSIX tar can be a pain (it's really nice to be able to type tar xjvf or tar xzvf instead of bunzip2 -c filename | tar xf -), but otherwise there isn't too much that is required (exempting stupid packages full of GCCisms that won't compile correctly using MIPSPro or SunStudio)

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
    13. Re:Which version of unix? by armanox · · Score: 1

      Info is nice, but for many packages it just shows the man page anyway.

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
    14. Re:Which version of unix? by l0n3s0m3phr34k · · Score: 1

      in the airline industry, anything like installing anything "optional" is a quick path to the unemployment line. We follow ITIL to the letter, nothing is done without a very detailed plan that also includes "rollback". Not because we really want to, but the FAA doesn't like it when some random app crashes planes so it's just not allowed. We have run books with very specific steps for everything; it all has to be documented and signed off on.

    15. Re:Which version of unix? by quetwo · · Score: 1

      UNIX was a property of AT&T (Bell Labs), and sold to Novell in the mid-nineties. Since Novell bought it, there hasn't been an operating that was truly UNIX. The last boxed copy of UNIX was in the early 90's... There have been many OSes that have licensed Unix and many more that were derivatives of it. BSD (which was based off UNIX System V) was one variant, and Linux was based off that.

    16. Re: Which version of unix? by tnk1 · · Score: 1

      Heh. Linux uses GNU applications and GNU's Not UNIX.

      Strictly speaking, Linux is UNIX-like. UNIX is an actual trademark for a multiuser, multitasking system which currently exists as UNIX System V Revision 4. There are three OS's today that are actually True UNIX: AIX, HP-UX, and Solaris.

    17. Re:Which version of unix? by cwsumner · · Score: 1

      Do you realize how old it makes you sound when you say that?

      You have no idea! I was old before you were born.
      You are but a dayfly, destined to live out your life before the sun sets... 8-}

      No offence meant. 8-)

  3. Re:Virtualize? by Duhfus · · Score: 4, Insightful

    Possibly for the physical machines needing parts from eBay issue. I think their real problem is still needing to run on Windows 3.1, and once you address that (hopefully moving to something much more modern) you can solve the legacy machine part as well.

  4. Mainframes by Tablizer · · Score: 5, Interesting

    This is why mainframe software lives on and on. It won't go out of fashion because it never was in fashion (except in the mid 60's) and there is so much mainframe code floating around that something or someone will always support it.

    1. Re:Mainframes by gstoddart · · Score: 5, Insightful

      And, more importantly, it's also why you can't always replace those mainframe systems: because it works, and has worked for decades.

      I've been on projects to replace aging mainframe stuff, some of which went back to the mid 60s or so.

      You could start off trying to design a replacement, gather requirements, and design something which works on your assumptions and in the limited use cases you've seen.

      And the more you delve into it, and discover all of the exceptions, corner cases, "didn't we tell you that?", sheer size of the data, all of the hairy bits, the 50 other systems which tie into that system and would also need to be replaced or updated ... you can quickly reach the point where you really can't design a system which does the same things, you can't replace all of the integration points, you can't even really map out all the logic and business rules embedded in that system.

      At the end of the day I've seen at least two such projects utterly fail.

      Say what you will about legacy mainframe stuff. But they work, are so closely tied into the entire business and other systems that you can't simply swap them out as easily as people think you can, and as often as not are vastly more complex than you can possibly know until it's too late.

      They're old, clunky, convoluted, and utterly mission critical. And when every other computer system in the company ties into them to extract data, you quickly realize you can't possibly update all of them.

      That, and you might also find that you simply can't match the performance and throughput of those damned things.

      A mainframe is a big lumbering beast. But it's a big lumbering beast which has kept the company moving for decades, hasn't had much in the way of downtime, has been expanded and added onto over the years, and in many cases will cost so much damned money to replace that nobody can afford to do it.

      The guys coming in thinking they can whip up something in .NET, running SQL server, and on one machine? They often have no idea of just how big of a task they're trying to take on.

      Personally, I would run screaming in the opposite direction from any project trying to replace a mainframe that's been in service for a long period. Because the scope of those things, and extent to which they interact with everything else in the company can be mind-boggling.

      --
      Lost at C:>. Found at C.
    2. Re:Mainframes by deKernel · · Score: 1

      Hi Five there brother. I have been down that road which eventually ran right off the cliff for all the reasons you stated. We tried early on to explain, but I had a manager that confidence that we could handle everything in a timely manor. Needless to say, he is employed there anymore.

    3. Re:Mainframes by PRMan · · Score: 1

      I worked at a company where they were 8 years into a 2-year mainframe migration. And they had halted all mainframe development for over 5 years. I hear they are just about done, 3 more years later.

      --
      Peter predicted that you would "deliberately forget" creation 2000 years ago...
    4. Re:Mainframes by known_coward_69 · · Score: 1

      SQL Server can do the job. you just have to spend a crapload of money on storage to separate all your drives and files and indexes and everything to it's own RAID1 volume for performance. none of this just put it on RAID5 and logs on RAID1. by the time you make it fault tolerant with the high priced storage, you just bought yourself a mainframe

    5. Re:Mainframes by ZorinLynx · · Score: 2

      Mainframes aren't even obsolete. IBM still sells them, fully code compatible going all the way back to 1968 when the first System/360 mainframe shipped.

      Companies that use this stuff have big expensive support contracts with IBM. They don't replace it because it works. In fact it works so well that "the mainframe is down!" is seen as a HUGE DISASTER in the business process, akin to a building burning down.

      It's a whole different world than the modern idea of blades in a rack running Linux. And it still works today, which is why it sticks around.

    6. Re:Mainframes by Ryanrule · · Score: 1

      thats why you have a management consultant whos whispering what needs done into the c suites ear. replacing old systems = replacing old business processes.

    7. Re:Mainframes by l0n3s0m3phr34k · · Score: 1

      LOL, not for an airline. We have racks of machines just running a single DB, blade servers for redundancy...this isn't some small business you buy off-the-shelf systems and stick it in a closet.

    8. Re:Mainframes by Tablizer · · Score: 1

      If you pay enough, you will "find" them. At least they exist. If you pick something obscure, even money may not be enough to bring them in.

    9. Re:Mainframes by Tablizer · · Score: 1

      Microsoft plays too many games to "encourage" you to migrate. They may not outright pull the plug on legacy stuff, but they often make you jump through hoops to keep using older stuff. IBM seems to have gotten over trying that crap and realize if you run old stuff you are likely to keep buying IBM. MS sales is still caught in the upgrades=profits mode.

  5. No surprise... by __aaclcg7560 · · Score: 4, Insightful

    When I worked at the college bookstore warehouse in the early 1990's, we had an ancient IBM XT computer with dual 5.25" drives, an amber monitor and a dot matrix printer for printing shipping labels. It did that one job exceptionally well. I wouldn't be surprised if it still working there today.

    1. Re:No surprise... by Nyder · · Score: 2

      When I worked at the college bookstore warehouse in the early 1990's, we had an ancient IBM XT computer with dual 5.25" drives, an amber monitor and a dot matrix printer for printing shipping labels. It did that one job exceptionally well. I wouldn't be surprised if it still working there today.

      IBM XT computers were not ancient in the early 1990's.

      --
      Be seeing you...
    2. Re:No surprise... by armanox · · Score: 1

      I was still seeing VT102s in use at a Doctor's office in the Baltimore area about 5 years ago. Also last I saw in a large pharmacy near me (three years ago now?) they were still running DOS 6.22.

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
    3. Re:No surprise... by __aaclcg7560 · · Score: 2

      The IBM XT was nine years old when I started work in Spring 1992, running an 8088 processor. The 286, 386 and 486 processors were on the market, and the Pentium was on the horizon. By prevailing CPU standards, it was ancient.

    4. Re:No surprise... by gstoddart · · Score: 1

      Well, in 1993 I bought a 486 machine.

      A dual floppy IBM XT could be as old as 1983, ran an 8088, and ran at 4.77MHz.

      So, yes, by a lot of standards, an IBM XT was ancient in the early 90s. At the very least it was around 4-5 generations of CPU behind contemporary Intel offerings.

      --
      Lost at C:>. Found at C.
    5. Re:No surprise... by __aaclcg7560 · · Score: 1

      Although the Records & Admission office at my local community college have updated PCs, each PC had a terminal emulator and a 9600 baud serial link to the mainframe computer.

    6. Re:No surprise... by __aaclcg7560 · · Score: 1

      I think the label printer database was RBASE. The only person who knew how to tweak it was the Japanese exchange student who worked in the warehouse for a few years.

    7. Re:No surprise... by zwarte+piet · · Score: 1

      You could still buy brand new PX/XT clones at the end of the eighties. They where good enough for most of the dos software of the day and hose things where generally very well built and lasted many years.

    8. Re:No surprise... by PRMan · · Score: 1

      I bought a 286 in 1990. By 1992, 8088s were ancient.

      --
      Peter predicted that you would "deliberately forget" creation 2000 years ago...
    9. Re:No surprise... by __aaclcg7560 · · Score: 1

      Um... dude? You are aware that it's 2015 now, right? The "early" 1990s were about 25 years ago.

      You are a fsking moron.

      FTFY - Thank you for noticing my misbegotten youth.

    10. Re:No surprise... by __aaclcg7560 · · Score: 1

      Doom came out in 1993. My roommate gave me his old IBM AT (286) and bought a 386 with a whooping 4MB of RAM and an VGA video card to play the game. That started the race to upgrade to ever powerful computers to play the next-gen video game.

    11. Re:No surprise... by citylivin · · Score: 1

      Would you call a core 2 duo ancient then? About the same age now as your XT then.

      For what its worth, around the same time I was in a school that had loads of XT's and maybe one or two x86s. I believe the XTs were on a token ring network with a giant hub in the middle of the room and cables as thick as extension cords. So yes, they were quite common in 1992 and not at all ancient. This was the system that they taught school kids to type. In fact, i remember even using XT's in the school environment as late as 1997.

      I'd say 20 years minimum is needed for something to be called "ancient" in computing.

      --
      As a potential lottery winner, I totally support tax cuts for the wealthy
    12. Re:No surprise... by CharlieG · · Score: 1

      I too had an original IBM PC (Model 5051) running in 1992. I wrote the code on it in the 1985 or so timeframe. It didn't do anything fancy, but did talk to a special board (a particular IEEE-488 card from CEC). It worked. It worked EVERY day. It did what it was supposed to do. We had a 386 doing the same exact thing one desk over, but why change it? The literally 10+ lbs of paperwork to make the change (did I mention it was doing stuff for the .MIL) wasn't worth it. If/when it died, we'd replace it with current hardware, and start the paperwork. I left in 1992, and from what I heard, when the company closed in 1993 or 1994 (owners retired) it was still working at the new company. Sometimes good enough is good enough

      --
      -- 73 de KG2V For the Children - RKBA! "You are what you do when it counts" - the Masso
    13. Re:No surprise... by zwarte+piet · · Score: 1

      yep (but the xt's remained in the library till 2000 or so) I skipped the 286 and got a monster with a 80386sx@25Mhz and 2mb Ram.. what a difference..... Doom ran perfect on that thing, but then they had to make quake....

    14. Re:No surprise... by zwarte+piet · · Score: 1

      My XT clone from '87 ran @ 8Mhz. (NEC V20 cpu) .... (but switched back automatically to 4.77Mhz during access to the disks etc). I also saw 10Mhz XT clones

    15. Re:No surprise... by ancientmyth · · Score: 1

      The 286 prices dropped dramatically as the 386 and 486 models came out. People gravitated towards compatibility with the new software that tried to keep some backward compatibility then, too. That said, vocational schools were popular as they used business' hand me downs (8086's).

    16. Re:No surprise... by ancientmyth · · Score: 1

      And even that was down a couple of versions. The 80486 being released in 89.

  6. Let the guy retire by Nidi62 · · Score: 5, Funny

    Even if it is an old system, everyone knows you can easily fix things in UNIX by just clicking around the 3D interface for the right file which, when opened, will magically restore everything.

    --
    The only thing necessary for evil to triumph is for it to be pitted against a slightly greater evil
    1. Re:Let the guy retire by known_coward_69 · · Score: 1, Informative

      and lock the dinosaurs back in their cages

    2. Re:Let the guy retire by FatdogHaiku · · Score: 2

      and lock the dinosaurs back in their cages

      Well, it locks the cages...
      where the dinosaurs are at that moment is an external variable.

      --
      You have the right to remain sentient. If you give up the right to remain sentient, you will be elected to public office
    3. Re:Let the guy retire by 93+Escort+Wagon · · Score: 1

      That's because it lacks support to the dinosaur presence detector.

      It doesn't "lack support" - it's just that the vendor won't open-source a binary blob that's necessary for the dinosaur presence detector kernel extension to function.

      --
      #DeleteChrome
    4. Re:Let the guy retire by gstoddart · · Score: 1

      You jest, but you do know that 3D interface was a real thing, that SGI built, right?

      If you happened to have an SGI UNIX machine which had this interface, it was real. At one point someone had gotten us an SGI box to port our software to .. so in 1996 I suddenly found myself staring at the interface going "wait, this is real?". Real, shipping software.

      So, if you had a sensible filesystem layout, and a single script to restart the system, it's shockingly not nearly as far fetched as you think.

      It really isn't a case of Hollywood making shit up. I've personally used that interface.

      --
      Lost at C:>. Found at C.
    5. Re:Let the guy retire by UnknowingFool · · Score: 1

      You jest, but you do know that 3D interface was a real thing [wikipedia.org], that SGI built, right?

      You know that according to your own wiki, it labeled it as "experimental" right? That means most people who actually used Unix never saw it and never worked with it.

      If you happened to have an SGI UNIX machine which had this interface, it was real. At one point someone had gotten us an SGI box to port our software to .. so in 1996 I suddenly found myself staring at the interface going "wait, this is real?". Real, shipping software.

      Um your own link says: "Even though it was never developed to a fully functional file manager, . . . ". So some people may have gotten to see it if they had a SGI IRIX machine which unfortunately was eclipsed by many more IBM, Suns, HP-UX, etc. Even then I wouldn't call it "shipping" software.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    6. Re:Let the guy retire by gstoddart · · Score: 1

      Yes, I know it was experimental. Yes, I know it wasn't widespread. Yes, I know that all UNIX systems did not have this.

      By the same token, a lot of people have probably never used HP-UX, Solaris, SunOS, AIX, DEC's Open UNIX (or whatever it was), or even a VAX. That doesn't mean they didn't exist.

      But if it was on the SGI IRIX workstation we had to port our software to, and if it was installed, it was real software. We sure as heck didn't go and install it.

      Now, in fairness, we had a pretty low end IRIX workstation, and the interface was dog slow. We fiddled with it for a little while and then put it away ... I'm sure on a really beefy machine it was awesome.

      That does not change my fundamental point that people who mock it because they don't know it existed are, in fact, wrong. It isn't a special effect, it isn't something some guy in Hollywood made up. It was a real thing.

      The interface existed. Period.

      I'm not saying it was common or widespread, or even ready for production. But since it was a company who made graphic workstations, it was the kind of demo they would do.

      Hell, the monitor might have even had the SGI logo on it in the screen frame of Jurassic Park.

      --
      Lost at C:>. Found at C.
    7. Re:Let the guy retire by KGIII · · Score: 1

      That's why you use grep and awk. You find the dinosaurs and then their exact locations.

      --
      "So long and thanks for all the fish."
  7. Re:Virtualize? by alphatel · · Score: 5, Insightful

    You're both wrong. The reason why these machines weren't virtualized a while ago is that you have to make a lot of serial/parallel/ps2 conversions for ports that are truly physical. These are the types of programs that send specific voltage down the wires and expect exactly something specific in return. Lots of times you try to get those returns right and you simply can't anticipate the various bugs that amazingly show up just a few months after you convert. The real problem? Some are nearly unsolveable. You can't even figure out what the manufacturer/programmer was trying to achieve with their hardware interface so it's best to simply leave eveything as is. Half these people don't even work in computers anymore, let alone the vendor they were at in the 80's.

    This coming from a guy who espouses VMs every day on a variety of systems.

    --
    When the foot seeks the place of the head, the line is crossed. Know your place. Keep your place. Be a shoe.
  8. Orly? by Anonymous Coward · · Score: 3, Interesting

    Fucking hell, I'd much rather run a mission-critical system on Windows 3.1 than Windows 10. Complexity means more potential points of failure. Windows 10 is doing so much stuff all the time that it makes a horrendous option for a machine that's chugging along doing one thing predictably and reliably. As long as it's isolated from the wild, once something works, one leaves a system the fuck alone.

    If employment is an issue, employ more people. If hardware is an issue, virtualise on the most stable, simple possible hypervisor.

    1. Re:Orly? by godrik · · Score: 2

      Lol. Not sure you did it on purpose, but the airport that suffered the bug is "Orly" indeed! :)

    2. Re:Orly? by Tablizer · · Score: 1, Informative

      and less snoopware

    3. Re:Orly? by armanox · · Score: 1

      Hey - if they need employees who can maintain Windows 3.11 I know that I'd go for the right price. I still keep a Win 3.11 system running just for fun (along side my Windows Me laptop)

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
  9. Sacré bleu-screen! by JoeyRox · · Score: 1

    Viva la Windows

  10. Re:I would actually bet money by ledow · · Score: 5, Insightful

    I have some old VB apps from the 3.1 era.

    Although it may be technically possible to get them running, it's certainly not as easy as just copying the files across and running the program.

    The fact that it is to do with weather suggests it interfaces with hardware of some kind or some external services. That's where you'll REALLY hit problems that just running as admin or renaming files or providing substitutes isn't going to fix.

    Good luck getting a driver from the 3.1 era working on anything at all nowadays, even emulated. You would literally just be better off throwing it out, starting again and suffering the inconvenience.

  11. Re:Virtualize? by ISoldat53 · · Score: 4, Funny

    Shoulda used TRS80 and arcnet.

  12. Ha this is how my company makes all it's money by mt2mb4me · · Score: 3, Interesting

    We do third party support for out of warranty shit, The fun one over here (for us anyways) is MPE, Factories still run on this stuff, everyone who supports it is dying, it's hard to train new people to deal with the old way of doing things. But there is always a need somewhere. I don't see why Microsoft doesn't spend their resources for SAS for updates on antiquated software. They could probably hold their company indefinitely just running windows XP,7 or 8. The corporate licensing could compensate for security updates on the consumer side. In the early days upgrading all the time made sense. But how many different ways do you need to edit a document, or use Excel. These things are at a point. Windows is a stable operating system. Why should companies keep shelling out for new hardware, when for most people (not designers, or other power users) a core 2 duo is more than enough power. As to virutalizing, Not likely, and more importantly, not free. Windows 3.1 is 16 bit. If you didn't need access to any hardware (old network cards or specialty cards of any kind) there would be a shot. But this is pre HAL, it relies on BIOS for control of it's hardware. Also, even if you could virtualize, you would need to know the coders to fix all the bugs from the switch over. How do you do that in a live system that was pre-virtualization without making downtime. Downtime that isn't really available for an airport. Lastly, they have a system that "works" they would have to pay the capital investment to switch. (I know they should but hey they are French)

    1. Re:Ha this is how my company makes all it's money by Grishnakh · · Score: 1

      They could probably hold their company indefinitely just running windows XP,7 or 8

      Corporations have to constantly grow, or they're considered "dying". MS isn't going to grow if they can't get customers to keep shelling out $$$ for new versions of the old software they're already using.

    2. Re:Ha this is how my company makes all it's money by thegarbz · · Score: 1

      Downtime that isn't really available for an airport.

      Err no. That couldn't be further from the truth. Most airports around the world provide ample downtime on an almost daily basis. In the case of Paris-ORLY there's a noise abatement procedure that requires the airport to be down between 11pm and 6am every day. This is not an excuse. If major oil and gas pipelines can take an outage for upgrades at the cost of hundreds of millions of dollars then so can a crappy airport.

    3. Re:Ha this is how my company makes all it's money by l0n3s0m3phr34k · · Score: 1

      Normally, each system has it's own scheduled maintenance window. We've even waited a few minutes so an app crash could be considered in that window so we didn't have to log an outage ticket.

    4. Re:Ha this is how my company makes all it's money by Grishnakh · · Score: 2

      No company can force another company to spend money. They can try really hard, but the fact is, "I bought and own this, and I will use it till it doesn't work anymore" is a common mindset.

      The corollary to that is that no customer can force a vendor to support an old product forever. They can try really hard, but the fact is, supporting obsolete stuff just isn't worth it most of the time. And they're definitely not going to do it for free.

      They can still develop new OS's there is nothing stopping that, but there is no reason for an EOL, they should just charge for support.

      How many customers are willing to pay $10 million per year per computer for support?

      Continuing to support old OSes (which are highly complex products remember) isn't a trivial effort. At some point, the amount of money customers are willing to pay for continued support just isn't enough to pay for the extra organizational overhead needed to do that. Don't forget that there's a lot of institutional memory in stuff like this: long-time employees have all the requisite knowledge, and a lot of it doesn't get written down. You can't just hire a bunch of new employees and put them to work supporting some 25-year-old software product; they're going to be lost. And the old-timers are going to age out or go find new jobs, and where are you going to find fresh new employees who want to have on their resume, "supported Windows 3.1 for 3 years"? No one really wants that job.

  13. Re:Virtualize? by Rei · · Score: 5, Informative

    My favorite I've encountered about ATC systems is how the documentation lies. For example, how checksums are to be computed computed for a particular broad class of messages. The ARINC specs go into detail, with diagrams and everything about the computation process. But when you look at existing samples of code, they don't do this - they do this weird thing with a lookup table and uncalled-for bitshifts and the like. After spending a day or so studying the code, I finally figured out what they were trying to do - they were trying to "optimize" the algorithm in the specs. But in the process they made it deviate from what is actually supposed to be computed in about four different ways (plus, their "optimizations" don't actually save compute time, the simple math operations are faster than the lookup in the "precompute" table that they made).

    So what do we do when we need to compute and check checksums? We use the wrong code, of course! It's what's "out in the wild", so who cares what the specs say we're supposed to use, it's what we have to use if we want checksums to ever to come up valid. Hopefully they'll eventually update the specs to reflect the reality.

    --
    Hello from Sputnik 2. I am receiving you.
  14. 20 years? by fustakrakich · · Score: 5, Interesting

    That's not a long time at all. How old is our perfectly functional ordinary telephone? If computers are going to remain so maintenance intensive, the damn things will never really be any good. We have to be able to plug it in and ignore it for those 20 years, until the smoke leaks out

    --
    “He’s not deformed, he’s just drunk!”
    1. Re:20 years? by avandesande · · Score: 1

      Do you think consumer electronics that have seen a nominal amount of usage over 20 years will be still working? Probably not, and that includes your telephone example. I don't think there is anything special either way about computers.

      --
      love is just extroverted narcissism
    2. Re:20 years? by cdrudge · · Score: 2

      Do you think consumer electronics that have seen a nominal amount of usage over 20 years will be still working? Probably not, and that includes your telephone example.

      Ever seen a Model 500 telephone or one of it's successors? Chances are that they are well over 20 years old. Some that are still in use may have been 20 years old 20 years ago.

    3. Re:20 years? by avandesande · · Score: 1

      I am not talking about a completely analog phone- that is a ridiculous example. How about a 20 YO cell phone, or answering machine or cordless phone?

      --
      love is just extroverted narcissism
    4. Re:20 years? by amicusNYCL · · Score: 1

      We have to be able to plug it in and ignore it for those 20 years, until the smoke leaks out

      We did, and it is.

      --
      "Our two-party system is like a bowl of shit looking at itself in a mirror." - Lewis Black
    5. Re:20 years? by fustakrakich · · Score: 1

      We had TV sets that lasted over 20 years easy, and with user replaceable parts. It's not hard to find a working fifty year old radio. And I have a ~70 year old telephone (Western Electric Model 302) that makes a handy weapon that can be used more than once, blood stains wash right off... if you do it quickly, before it dries.

      --
      “He’s not deformed, he’s just drunk!”
    6. Re:20 years? by drinkypoo · · Score: 2

      Do you think consumer electronics that have seen a nominal amount of usage over 20 years will be still working?

      It used to be normal for electronics to last for twenty years. People used to throw away stereo systems because they got dirty volume pots and they were too cheap and/or lazy to fix them. Now they throw them away because they lose an audio channel.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    7. Re:20 years? by Impy+the+Impiuos+Imp · · Score: 1

      This kind of thing was something deliberately over-engineered because the phone company didn't wanna deal with it after putting it in your house. See, when you pay for it monthly, they can't charge a repair fee.

      > Microsoft...is trying to convince everyone Windows 10 is a bright up-and-comer.

      Well, that's better than Windows 8, where Microsoft was trying to convince everyone it was a 12 year old with unusually large breasts.

      --
      (-1: Post disagrees with my already-settled worldview) is not a valid mod option.
    8. Re:20 years? by avandesande · · Score: 1

      Lots of old electronics work, lots of them don't work. Same with computers. A very simple point.....

      --
      love is just extroverted narcissism
    9. Re:20 years? by ancientmyth · · Score: 1

      In the early 90's I worked on equipment that was manufactured in the 70's. Electronics were expected to last 20 years then because they were designed for that. But it was expensive. As cheaper metals were used for electronics, driving down their cost, so did their life expectancy.

  15. I'd take that bet. by prunus.avium · · Score: 3, Informative

    Primarily because I'm betting the interface from that Windows 3.1 machine has some very specific DOS "driver" (TSR for us old-timers) that even Windows 95 would kill.

    There were some very interesting hacks that could be done on a DOS box. I remember writing a TSR that bumped up the system timer to allow a finer grain on the timer events. It also sent out the "normal" system event to the rest of the OS so Windows would keep running.

    1. Re:I'd take that bet. by prunus.avium · · Score: 1

      Global memory allocation for the WIN!

      Who needs IPC when you can just allocate a memory block and have ALL of the processes use it?

      Sure, there's the minor issue of running out of system RAM but as long as everyone plays nice, there shouldn't be any problems. Right?

  16. Re:I would actually bet money by Anonymous Coward · · Score: 1

    The old system talks to hardware by sending specific voltage down analog connections (hot / cold pins). You would need to rebuild not only the system but all the systems it talks to (which could be a radar dish, an old school display, or anything else really).

    This is not the same as just replacing the computer OS, you are asking to rebuild the entire hardware interface.

  17. Re:Virtualize? by fustakrakich · · Score: 1

    you have to make a lot of serial/parallel/ps2 conversions for ports that are truly physical.

    I got a drawer full of adapters if you need any... Parallel, serial switches, you name it.

    --
    “He’s not deformed, he’s just drunk!”
  18. It's Warped by stereoroid · · Score: 1

    I remember trying ti buy a train ticket at the Charles de Gaulle airport station after flying in, in 2005. The queues were horrendous, and then one of ticket machines crashed, and all the people in queue swore and walked away. Except for me, since I recognised that the machine was running OS/2 Warp. By having the patience to wait a couple of minutes for it to reboot, I effectively jumped the queue. It took only three tries to get the machine to accept my credit card ... I hope their systems are a bit better today.

    --
    (this is not a .sig)
    1. Re:It's Warped by ancientmyth · · Score: 1

      I usually have 3 drinks on the flight if i see a screen and recognize the underlying OS (Windows anything).

  19. So cute by ITRambo · · Score: 4, Funny

    They're so cute when they're young. But so clumsy. Someday this little Windows 3.1 machine will grow up to be bigger stronger, just not any faster.

  20. Re:I would actually bet money by prunus.avium · · Score: 1

    Good luck getting a driver from the 3.1 era working on anything at all nowadays, even emulated.

    Exactly. What the young-uns don't know is that the 3.1 era drivers - especially for customized hardware - were often loaded before the Windows 3.1 kernel and involved changing the interrupt vectors out from underneath the kernel.

  21. Re:Virtulize? - Emulate?!! by ripvlan · · Score: 4, Funny

    > [ Or emulate ] ....In a Browser.

  22. Hardware or software? by lurker412 · · Score: 1

    TFA doesn't say. The software (including Win 3.1) may still be doing just what it always did correctly, which might explain why it hasn't been replaced.

  23. TRS-80 still in use by tekrat · · Score: 4, Insightful

    Considering I still use a TRS-80 Model 100 on a regular basis (great keyboard!), Systems using Windows 3.1 do not surprise me.

    Then again, I work for a bank, login to a mainframe and review COBOL code that dates back into 1980... So, yeah. I'm not surprised.

    --
    If telephones are outlawed, then only outlaws will have telephones.
    1. Re:TRS-80 still in use by prunus.avium · · Score: 5, Funny

      1980? Wow. You got the new stuff.

    2. Re:TRS-80 still in use by MagickalMyst · · Score: 1

      "I...review COBOL code that dates back into 1980... "

      You wouldn't happen to be the missing COBOL programmer that ExxonMobil has been trying to track down to upgrade the TANDEM system that he created in the early 80's, are you?

      If so, they've spent a FORTUNE on P.I.'s looking for you! You should call them....

      --
      Political correctness is really just herd psychology pushed by insecure people who desperately seek social conformity.
    3. Re:TRS-80 still in use by metaforest · · Score: 1

      I have two fully functional mod 100's and a NEC PC-8201A. While they are not daily drivers, I am in the process of reengineering them to be more capable, and still support the old firmware. The goal is to create a system that replaces the MOBO and the antiquated I/O with modern equivalents and still supports all the core features of the system, as well as enabling more modern interfaces.

      The Mod 100 is one of the toughest laptop designs out there... I used one for taking notes in Olympic National Park during my stint as a volunteer back country ranger in the mid-90's. It easily handled running for 10 days on one set of batteries (4 AA) and storing all of my daily field notes. It was light and happily survived getting banged around in my field kit. It also easily interfaced with the aging PC XT that the ranger station used for storing our field notes. Simple serial cable interface to DOS on the host PCXT allowed me to stream my notes into a text file and then copy them into the logging system that the park service used to record rangerly activities. The other rangers had a rough time comprehending my madness at first. It took less than a half hour to finish my tour by filing my reports in the station. It took the others hours to do it by typing in their hand-written field notes. I think some of them started to see the light.

      The keyboard alone is an amazingly beast that few modern keyboards can beat for feel or reliability even under harsh conditions... Anyone who has spent 6 months touring the back country in the Olympics for 10 days out of 14 at a time knows what I am talking about.

  24. 32 bit disk access and 32 bit file access does not by Joe_Dragon · · Score: 1

    32 bit disk access and 32 bit file access does not work that well in VM.

    also this likely needs real serial parallel ports maybe even custom PCI / ISA cards. Can you do ISA pass though in VM? Will even a PCIe to ISA Bridge work with the cards out side of a VM?

  25. Re:Virtualize? by ripvlan · · Score: 4, Insightful

    Very true I'm sure. But I also believe in "where there's a will, there's a way"

    I've been in these kinds of discussions. The Cost to figure out or build such a gap-device is too-large, or equal to "just rewrite it in modern tech." So everyone waits for another 10 years while the rewrite doesn't happen. Rather than picking it apart and refactoring a bit here and there - wait for the big bang!!

  26. Dirty Little Secret by danmoran · · Score: 1

    Every organization of any appreciable size has a room where they keep systems that were never upgraded and that hold data that has never been migrated to newer systems, but which they might need someday. Often, it's simply a matter of CYA, that no one wants to be the one who eliminated "System X".

  27. Learn from the railroads by Anonymous Coward · · Score: 5, Interesting

    Demand support nearly forever. When steam was replaced here in the mid 50s to late 60s, the average age of the replaced engines were around 50 years. The replacement engines are still in operation. The main reason is safety. When designing a new locomotive, the manufactor spend a fortune verifying the performance, which is then added to the price (naturally). On delivery of the first of its kind, it goes through a whole lot of testing and documentation to ensure that it's not too heavy for the track, works with the signal system and all that stuff. It takes time and cost millions. It's a lot cheaper once the type is certified, but they are still tested with non-free tests. This makes buying a used already certified engine quite attractive and as a result, spare parts are produced for many decades after production stopped. It's a demand from the railroads and supplying those parts makes manufactors trustworthy enough to be candidates for new engines expected to be used for at least 30 years, likely more than that.

    Computers are way too short lived. Powerplants/grid, railroad signals, air traffic control and so on are hard to replace systems and once they have something working, they want to stick to their systems as long as possible. They make horrible contracts since they are unable to get the spare parts they need. The US army invented VHDL to give a description of the work of a chip and you would not be able to sell to the army without VHDL code. The idea is that if the army needs a replacement chip 20 years later and the original company went out of business, they can send the VHDL code to another company and say "make this chip using housing XYZ". That will ensure they don't have to scrap helicopters or whatever because a single chip went out of production. Civilians should be equally demanding for critical systems.

    1. Re:Learn from the railroads by Grishnakh · · Score: 1

      The problem is that that approach you describe with VHDL doesn't actually work. The Army has all kinds of problems sourcing obsolete parts these days. If what you described actually worked, they'd just get someone to fab the chips for them.. But they don't, they source them from all kinds of weird little suppliers of NOS components, and frequently end up getting counterfeit stuff from China.

      Moreover, there's a lot more to a chip design than the HDL code. You can't just give some foundry some HDL code and have them spit out an Intel processor.

      If you want continuous support for electronics like this, you have to keep up with what's going on in the industry, and continuously upgrade your designs to use modern parts. There's no other way to do it, unless you have a really simple design that can be built with discrete circuits and doesn't need any ASICs. You could do much of your designs in Verilog and make your hardware FPGA-based, and then just upgrade to newer FPGAs over time, since porting Verilog code to newer FPGAs isn't that hard, but it's still not a simple solution requiring absolutely no redesign. There's just no such thing.

  28. Re:Virtualize? by ebh · · Score: 2

    Probably needs a 20ma current loop to drive the ASR-33 Teletype.

  29. Re:Total infrastructure failure in many Countries by Grishnakh · · Score: 1

    The problem with outdated, obsolete technology is maintenance. Nothing lasts forever, and a 25-year-old PC computer is going to fail at some point. Then you're not going to be able to find working replacement components, though you might be able to get by for a while by replacing capacitors or something. But at some point you're going to have a lot of trouble finding people willing and able to work on this stuff and keep it going. And yes, the prices end up going through the roof because you have to find specialists to do this stuff, and they charge a fortune. A highly skilled electronics tech could probably get an old PC like that working again, but his hourly cost isn't going to be cheap; you could buy an all-new server-grade PC for less that it'd cost to get him to diagnose and repair a component failure.

  30. The airport in Orly is run on Windows 3.1 by Kevin108 · · Score: 1

    O rly?
    Ya rly.

      ^ . . . ^
    / o , o \
    | ) : : : ( |
    ==w=w==

    --

    It's a perfect time for being wasted.
    A perfect time to watch the stars.
    - Burden Brothers, "Beautiful Night"
  31. Re: Virtualize? by jellomizer · · Score: 1

    They are... However you will need to make new software to interact with it.

    It is a case of Organic design, where a small app to make your job easier becomes a vital infrastructure, and was never designed for future upgrades.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  32. Re:Virtualize? by Coren22 · · Score: 2

    I'm not your guy, pal

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  33. Re:Virtualize? by Coren22 · · Score: 2

    Please don't, he will just spam this thread some more.

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  34. Re:Virtualize? by 0x15e · · Score: 1

    Is it really that common for the software to need such specific voltages and timing? How would you get to those values from software running on a PC?

    I ask because I just got done implementing some very old vending hardware (some 1200 baud, some 9600 baud serial) and although they were ancient and badly documented, none really needed anything I'd call exotic.

  35. Re:I would actually bet money by PPH · · Score: 1

    Including support for some custom 8-but ISA bus cards? Good luck.

    --
    Have gnu, will travel.
  36. Re:Virtualize? by Grishnakh · · Score: 1

    I think we need *more* APK spam. As it is, there's a lot of it and it's a big nuisance, but no one's doing anything to fix the problem.

    We need to have so much APK spam that the site becomes completely unusable. That's the only way the idiotic management around here is finally going to step up and do something about the problem.

    A lot of times, you have to completely burn something down before you can rebuild something better.

  37. Understatement of the century. by geekmux · · Score: 1

    "Maintenance is a problem."

    No shit. Really?

    I'm guessing the business justification to replace these systems has read about as benign as this understatement for decades now.

    Let's hope for the city of Paris learns a lesson here when one of the three people supporting this system agrees to fix it at the rate of $500,000/hr. (2 hour minimum of course).

    1. Re:Understatement of the century. by armanox · · Score: 1

      Hey - I'd fly from the States to fix it for that price.

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
    2. Re:Understatement of the century. by ancientmyth · · Score: 1

      There's no time to replace them. Hours are very strict when it comes to IT work; and probably residential requirements as well. You pay a huge fine when you require outside of regulated business hours.

    3. Re:Understatement of the century. by geekmux · · Score: 1

      There's no time to replace them. Hours are very strict when it comes to IT work; and probably residential requirements as well. You pay a huge fine when you require outside of regulated business hours.

      Huge fines, eh?

      I wonder what the price tag is when you put all your eggs in one basket with no backup.

      I would say good luck to them, but ignorance needs to be punished to avoid it being perpetuated through another generation of incompetence.

  38. Re:Virtualize? by Coren22 · · Score: 1

    http://slashdot.org/~Coren22/c...

    I think he is spamming quite enough. But that could be just me.

    I am doing my best to highlight the problem to Dice, we will see if they ever do anything about it. I doubt there is much that can be done to block his "Bridge" method (really a proxy...) of spamming Slashdot, but maybe if it becomes enough of a problem they will do something about it.

    I'm all for watching it all burn though.

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  39. Ehh, sorry... by Ecuador · · Score: 1

    Ehh, sorry to break it to you, but not all Unix installations come with SGI's File System Navigator. So in those installations, your best bet would be to create a GUI interface using VB and track the IP.

    --
    Violence is the last refuge of the incompetent. Polar Scope Align for iOS
  40. Re:I would actually bet money by PRMan · · Score: 1

    Good luck getting any serial port app to work correctly in Windows 7. We've never been able to.

    --
    Peter predicted that you would "deliberately forget" creation 2000 years ago...
  41. UNIX is old...? by jjn1056 · · Score: 1

    "The airport actually runs on a variety of old systems, including Windows XP and UNIX."

    Depending on what actual operating system this is, just because its UNIX doesn't mean its old.

    If it was some version of SunOS UNIX, yeah I'd say its old :)

    --
    Peace, or Not?
  42. Re:Virtualize? by unixisc · · Score: 1

    You're both wrong. The reason why these machines weren't virtualized a while ago is that you have to make a lot of serial/parallel/ps2 conversions for ports that are truly physical. These are the types of programs that send specific voltage down the wires and expect exactly something specific in return. Lots of times you try to get those returns right and you simply can't anticipate the various bugs that amazingly show up just a few months after you convert. The real problem? Some are nearly unsolveable. You can't even figure out what the manufacturer/programmer was trying to achieve with their hardware interface so it's best to simply leave eveything as is. Half these people don't even work in computers anymore, let alone the vendor they were at in the 80's. This coming from a guy who espouses VMs every day on a variety of systems.

    Is there a compelling reason that Windows of any version is needed here? Looks like the underpinnings here are DOS. So if they get computers that have just 1MB of RAM, fired up w/ FreeDOS, that should work well and run all the apps in question, right? In fact, it would be not just possible, but actually feasible, to have a single chip computer - say a 486 at 1GHz w/ 1MB of RAM and 1GB of SSD that would be a much faster computer for the same software. Since it's FreeDOS, one needn't depend on Microsoft for anything - just get an IT team to manage it.

  43. Re:Virtualize? by MagickalMyst · · Score: 2

    Electric barbed wire.

    --
    Political correctness is really just herd psychology pushed by insecure people who desperately seek social conformity.
  44. Re:Virtualize? by fustakrakich · · Score: 1

    Last time I looked most motherboards still seem to have the headers (RS232, etc) needed to make stuff work. if not, you plug in an expansion card. That's how I'm doing it on a guy's win7 machine running ancient shit made for DOS. Win7 only only there to run the drivers for the card.

    --
    “He’s not deformed, he’s just drunk!”
  45. Cheapskate power 10 by aepervius · · Score: 1

    Look I understand the desire to spare, but there are a heap of vendor which propose this exact service (I work for one !) and i doubt it is connected to anything for which tehre would not be an interface we handle already (from MATIP to other weird protocol), even going to change format for you, all on modern cheap hardware. having anything that run 3.1 when it should be easily to get for cheap such a service.... So if there is no incredibly rare hardware unknown protocol reason, then it is cheer stupidity.

    --
    C. Sagan : A demon haunted world:
    http://www.amazon.com/gp/product/0345409469/
    visit randi.org
  46. Re:Virtulize? - Emulate?!! by selectspec · · Score: 1
    --

    Someone you trust is one of us.

  47. Re:Virtulize? - Emulate?!! by selectspec · · Score: 1
    --

    Someone you trust is one of us.

  48. Re:Virtualize? by Coren22 · · Score: 1

    Does the poor baby need more attention?
    Is he crying because his diaper needs changing?

    You are pretty sad, but keep it up, it doesn't bother me one bit, buddy.

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  49. Re:Virtualize? by Drethon · · Score: 1

    One problem is when you get to the specs written by companies that use the same protocols. On the civil GPS unit I had to communicate with, the specification on the CRC protocol left out half of what you needed to know. So we just used a CRC table for another application that produced results that the GPS unit accepted. Of course the original CRC code was about a decade old but... yay?

  50. Re:GNU == GNU is not Unix by armanox · · Score: 1

    The SunOS kernel and the BSD kernel can be recompiled with various options pretty easily too, so that argument falls flat.

    --
    I'm starting to think GNU is the problem with "GNU/Linux" these days.
  51. Re:Virtualize? by drinkypoo · · Score: 4, Insightful

    You're both wrong. The reason why these machines weren't virtualized a while ago is that you have to make a lot of serial/parallel/ps2 conversions for ports that are truly physical. These are the types of programs that send specific voltage down the wires and expect exactly something specific in return.

    Ironically, you just named three ports where that's either not the case, or trivial to achieve. All PC keyboard ports are digital 5V, there are only two kinds of signaling, and nobody was using the old kind by the time Windows 3.1 came out. All PC parallel ports are digital 5V. And by definition, RS-232 is 12V, although many if not most ports will accept a 5V signal. (If you hook up any outgoing lines, though, you may well murder any 5V serial devices you hook up, if they don't have a real MAX232 in them.)

    The real problem is that a lot of these PCs have ISA-bus interface cards in them, and their drivers are often crap that is pissy about timings. Even a really high-speed PC is enough to make them not work. In order to reasonably replace these devices, you have to analyze the circuit and/or connection to figure out what the original control board was doing, throw it away, and replace it with something else. These days you might reasonably replace it with any little microcontroller board, like an Arduino. They are faster than early PCs were! But first you have to figure out how. Those boards also often included a specialty power supply to drive whatever-it-was, so you've got to replace that as well.

    Most of the time it's going to make more sense to throw it all away and start with a new thing. But it's not impossible, just expensive.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  52. Re:Virtualize? by Coren22 · · Score: 1

    That is crying in your world? You must be pretty sensitive if you think that. I was saying that you were posting quite enough to be penalized by the Slashdot editors, but you can take it as me rolling on the ground crying my eyes out if you want...it doesn't make it true though.

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  53. Re:Virtualize? by Coren22 · · Score: 1

    OMG, that is comedy gold, so now APK thinks he is a visualization and datacenter expert too. Another feather for him to claim he has in his cap.

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  54. Re:32 bit disk access and 32 bit file access does by MachineShedFred · · Score: 1

    In theory, you could use something like Intel VT-d to grant exclusive access to that PCI-to-ISA bridge to that VM. It might take a bit of work, but that's the kind of thing that VT-d is for.

    --
    Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
  55. Re: Virtualize? by Hylandr · · Score: 1

    >Your funny, guy.

    You're a funny guy.

    ftfy

    --
    ~ People that think they are better than anyone else for any reason are the cause of all the strife in the world.
  56. Re: Virtualize? by SumDog · · Score: 1

    I have a feeling they only have one set of hardware. You can't just plug in the 2nd set of sensor wires and ensure they work with protocol converters or reverse engineer them. Even if there is a 2nd system, it's probably a backup that always needs to be ready.

    I'm sure modern airports have newer equipment and there are probably specialized companies that can come in and install newer hardware and get it up and running side by side the old stuff so you can then take the old stuff down (or turn it into a backup), but that stuff doesn't come cheap. For smaller cities, they probably just don't want to spend the money on the airport.

  57. Re:Coren22 I tried to make peace w/ you 3x by Coren22 · · Score: 2

    You do realize that there are around 10 people who mention your crap in their signatures right?

    Perhaps you should read Slashdot sometime with an accoutn logged in. You already stated previously that you created an account (I think it was AlecStar) for the Carmack interview I beleive, just use it and see what we all say "behind your back" (because you not logging in is somehow our fault).

    KGIII busted your mistake on AD too!

    What crack are you smoking? Here is his comment, in full, including his (current) signature. Where does he say a DAMN thing about AD?

    An interesting note... In an earlier thread, I saw that APK quoted your signature. I do believe that signatures are not visible unless the user is logged in. APK has stated, numerous times, that they have no account. I'm unsure of what to make of it but I did find it amusing though I probably should have commented in that thread. Alas, I'm too lazy... Well, technically, it didn't cross my mind.

    As stated, I have no idea what to make of it. I just noticed the comment that quoted your signature. Personally, I don't mind 'em but that's just me. I'm pretty easy to get along with, most of the time. ;-)

    --
    "So long and thanks for all the fish."

    Yeah, I said I would change the sig, but it is apparent you can't read them, because you are proving my signature correct!

    --
    Making APK lose his mind one post at a time, it looks like I have succeeded.

    You have lost your mind now, you just keep posting all this crap while people bitch about how annoying you are. No one but you actually reads these, and no one cares what you put there.

    How about this, no matter what you do, post, say, scream, cry, whimper, or shout; I WILL NOT CHANGE MY SIGNATURE AT YOUR DEMAND. I am an independent person, and no matter what you do, you cannot force me to do your bidding, and for spite, I will do what I want just to piss you off. That is how the world works. I am sorry you think you have some kind of control, and that you think that acting like a petulant little child because you didn't get your way will work, but it will never work with me.

    Have a good day sir, and Thanks for all the Fish.

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  58. Re:Virtualize? by AmiMoJo · · Score: 1

    Someone could probably fix it, but the certification would be painful. Massive amounts of testing required for safety critical systems. The same problem affects things like fire alarm/smoke extraction systems. It's cheaper to pay silly money for parts to keep the old one going.

    --
    const int one = 65536; (Silvermoon, Texture.cs)
    SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
  59. Re: Virtualize? by Wintermute__ · · Score: 2

    Smaller cities... like Paris, apparently?

  60. Re: Virtualize? by jeremyp · · Score: 1

    This is Orly which is no longer Paris's main airport. If you ever travel through it, it'll be obvious that they have no money.

    --
    All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe
  61. Re:GNU == GNU is not Unix by armanox · · Score: 1

    I wasn't saying that recompiling it didn't void the cert, I was just saying the kernel can be recompiled. And yes, you are right. You would have to certify say RHEL 6.5 on x86, RHEL 6.6 on x86, and RHEL 6.5 on x64 all separately, and definately a re-certification for each distribution (fun fact, only OS X 10.4 and up on Intel hardware has been certified UNIX, the PPC versions never were)

    --
    I'm starting to think GNU is the problem with "GNU/Linux" these days.
  62. Re:Total infrastructure failure in many Countries by Joe_Dragon · · Score: 1

    At least you can do board work on the older systems the new ones have to many layers for that to work.

  63. Re:Really? by vrt3 · · Score: 1

    Secondly, it's usually something like ALT+F keys that are trapped, not the F keys by themselves.

    WordPerfect made heavy use of ALT+Fn, CTRL+Fn, SHIFT+Fn.

    --
    This sig under construction. Please check back later.
  64. Toronto Pearson... by matbury · · Score: 1

    ...runs on Windows XP throughout, as far as I can tell.

  65. Re:32 bit disk access and 32 bit file access does by Joe_Dragon · · Score: 1

    But will VT-d work with a 16 BIT os / the older 32 BIT's nt's or the mixed 16/32 dos + win9x?

    also there are quite a few ram pool / address space limits with the old software / hardware. Also they may freak out with trying to pass a non 486 / 386 / 586 / Pentium cpu.

    Runtime error 200 type errors as well.

  66. Re: Virtualize? by budgenator · · Score: 1

    Damn I just threw out my 486SLC that had dos 6.1 and windows 3.1 installed on it just last month!

    --
    Apocalypse Cancelled, Sorry, No Ticket Refunds
  67. Re: Virtualize? by LocalH · · Score: 1

    I'm not your bub, guy.

    --
    FC Closer
  68. Re:Total infrastructure failure in many Countries by Grishnakh · · Score: 1

    The components are all on the outside of the boards, so that doesn't really matter unless something happens to actually damage the PCB. And if that happens, it's generally not worth it to try to salvage the PCB anyway.

  69. Re:ME still runnig on a 486.... by toddestan · · Score: 1

    Really? Because Windows ME supposedly required a Pentium processor. Not sure whether or not that was a hard requirement or if it could still technically boot on a 486. If it really is a 486, it must be dreadfully slow, especially since most 486's aren't going to accept enough ram to run ME comfortably.

  70. From one extreme to the other... by pinzvidz · · Score: 1

    ... the most hilarious and saddest news out of France at the same time.

    1. Re:From one extreme to the other... by ancientmyth · · Score: 1

      I wish i had mod points.

  71. Re:Virtualize? by Z00L00K · · Score: 1

    One word: Dosbox.

    --
    If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
  72. Win16 support in Wine by staalmannen · · Score: 1

    I have found and reported a few bugs blocking some Win16 applications to run under Wine. It is ofcourse more difficult for developers to adress those issues nowadays, but on the other hand is the OS much smaller than the current versions so a 100% re-implementation should be possible. I think it would be great if some more effort would be put into the Win16 compatibility of Wine. At work, we had some fully working machines where the controlling software was built for Win16, and when the machines had to be replaced by Win95/98/XP machines it all became completely unreliable (crashes claiming "not enough memory"). It is sad when very expensive and fully functional machinery (in this case a CytoFluor 4000) gets unusable because of something stupid like that.

  73. Re:Virtualize? by arglebargle_xiv · · Score: 1

    Same thing with checksums on various mag stripe cards, which I wrote software for in the 1980s. There was the Luhn algorithm, and then the other Luhn algorithm, and then the other other Luhn algorithm, and the alternate Luhn algorithm, and the not-quite-right Luhn algorithm, and the Luhn variant, and the other Luhn variant, and holy fsck how many ways can you screw up one checksum?

  74. Re:ME still runnig on a 486.... by Blaskowicz · · Score: 1

    Windows ME requires 32MB, 64MB recommended. So it sounds possible.

  75. Re:Virtualize? by Bearhouse · · Score: 1

    ARCNET (note caps) is actually pretty good, and still used in applications that require deterministic network response, (like industrial control applications).
    It was far superior to Ethernet back in the day, but was "closed" so was slowly hammered into oblivion.

    https://en.wikipedia.org/wiki/...

  76. Re: Virtualize? by Desty · · Score: 1

    Depending on when that code was written, it's possible that the machine's ALU was slower than doing a fetch from cache or even memory, so the ganky lookup table may have been faster then. Maybe.

  77. Re:Virtualize? by lowen · · Score: 1

    But the TRS-80 Model II ARCnet board was indeed a piece of work. Grep the comp.sys.tandy archives on google groups for ARCnet one day.

  78. Re:I would actually bet money by pekka5766 · · Score: 1

    I'll App to that!

  79. Re:So much for the Y2K bug. by cwsumner · · Score: 1

    This is just yet more proof that the Y2K bug was overblown (as if we needed more evidence).

    Ha! Y2K was not overblown, even though the media had fun with it.
    Thousands of people worked very long hours to make sure it -seemed- overblown. And were mostly successful!

    I worked on a lot of PC programs that malfunctioned after 2000. Luckily none of those were critical... but others were.

  80. Re: Lumber Mill by rakslice · · Score: 1

    Is there open source software to use an x86 machine as a 61131 PLC, I wonder? Companies that are going to decide to solve the problem with a computer they can pick up for 400€ at the local FNAC could at least be pointed in the direction of a more maintainable solution.

  81. Re:So much for the Y2K bug. by ancientmyth · · Score: 1

    I'm curious what programs that were 'critical' other than payroll. Most of the hype surrounding the y2k bug was whether mechanics would just stop. Other than reports, nothing happened. Elevators, shipyards, medical equipment, and toasters were all safe.

  82. Re:Coren22 I tried to make peace w/ you 3x by lucien86 · · Score: 1

    Some trolls are amusing, some trolls are annoying, but APK is one of the worst I have seen in a long time.. Definite psychosis in the writing style and demeanour. Repetition and denial of logic, plus bizarre absolute beliefs. False belief systems driven by paranoia. Sad to say it but APK seriously needs the help of mental health professionals.

    --
    Below the speed of light Special Relativity is one of the most accurate theories in physics - above the speed of light..
  83. OS/2 for temp solution? by Zeekort · · Score: 1

    What about OS/2 for a temporary solution? It can run many of the apps that Windows 3.1 could and thanks to derivatives that are still actively developed like eComStation it can run on more hardware than in the past which would help give them time to port it over to something else.

    I'm not saying to just abandon their old system right away since they can't just drop it and move away from it overnight they have to eventually do something about hardware support because eventually supported hardware for old systems goes away and they're already using eBay. Given OS/2's reputation for running Windows programs from back then, it may at least open up some options while they work on replacing the old system and if they had to make some updates to it, it may be a little more cost effective to jump to a platform that's known to run those apps that still has a company backing it up.

    Ultimately they are going to need to abandon their old system, however in the meantime they have to do something about the hardware and this looks like something that can't be virtualized.

  84. Re: Virtualize? by cthulhu11 · · Score: 1

    Let's leave Family Ties out of this.

  85. Re:Virtualize? by drinkypoo · · Score: 1

    No, RS-232 is +/- 3-15V

    In actual fact, you can't use -3/+3 signaling on RS-232, either, and in practice all PCs implemented +/-12V serial ports.

    and requires a withstand voltage on both transmitters and receivers of a short in the range of +/- 25V though it wouldn't surprise me that many a modern "RS-232" ports or adaptors fry at below 25V.

    I mean that there's a lot of TTL serial stuff (or even 3.3v) and if you pretend it's RS-232 you'll kill it when you hook it up to a PC, which has a +/-12V serial port.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  86. Re:So much for the Y2K bug. by cwsumner · · Score: 1

    There must have been some things, an aweful lot of people were explicitly working on it!

    I worked on a number of PCs that refused to boot during that January. In those day many PCs had to have the ROM chip replaced, no flashing. Luckily many were in sockets back then. Some people that couldn't get updates, or didn't want to bother, just set the date back 4 years, so the days of the month would be the same.

    Many applications could not find data in their databases. Some had unchecked error conditions that caused GPFs. In those day a lot less machinery had computer controls. But, many did and some of it was very old, just like today.

    Much effort was spent on dangerous machines and I am not aware of any that were still giving problems in the date tests, on January first.
    After all, the computers and networks could have the date changed for testing, before it actually happened. Some companies built extensive isolated systems just to simulate what would happen. By the time year 2000 came everyone (well most) had been fixing for a while.

    And then when we were successful, the news media said that it had all been a fraud! 8-(
    But then this was often the same news people that had been encouraging people to spit on the returning soldiers from Vietnam, a few years before! So we sort of expected it...

  87. Re:Virtualize? by Drethon · · Score: 1

    Because improvement in processing capability and storage capability in the past decade mean that using coding tricks to conserve both is no longer necessary.

  88. Re: Coren22's "greatest hits" fails #5/5... apk by Coren22 · · Score: 1

    You complain that that person posts AC? Isn't that a bit abnormal, an AC bitching about someone posting AC? Make an account, log in and post, or don't bitch about others posting AC as well.

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  89. Re:Perhaps you should go fuck yourself pussy by Coren22 · · Score: 1

    Oooo, now who is getting all wound up?

    I don't need to fuck myself thank you, I am still young enough to attract the ladies.

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  90. Re:Coren22 I tried to make peace w/ you 3x by Coren22 · · Score: 1

    Agreed.

    Here is an AC detailing the mental issues with links to the information about them:

    http://slashdot.org/comments.p...

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  91. Re:Coren22's "greatest hits" fails #5/5... apk by dave420 · · Score: 1

    Translation: I have nothing else in my life, so I will moan and gripe about people on Slashdot, and try to hawk my old, tired, outclasses software in the most obnoxious manner, attracting notoriety and scorn in the process.

  92. Re:Virtualize? by RockDoctor · · Score: 1

    "where there's a will, there's a way"

    The implication of still running on win 3.1 and not being updated is that there isn't the will.

    --
    Birds are not dinosaur descendants;birds are dinosaurs, for all useful meanings of "birds", "are" and "dinosaurs"
  93. Re:Coren22 I tried to make peace w/ you 3x by lucien86 · · Score: 1

    The Ars Technica one - terrifying..

    LOL from that I just got his full name and address from 2000, I don't really want it. :(

    --
    Below the speed of light Special Relativity is one of the most accurate theories in physics - above the speed of light..
  94. Re:Coren22 I tried to make peace w/ you 3x by Coren22 · · Score: 1

    I imagine that if you grabbed a copy of his current software it would have his current address. It is funny to read him trying to defend trademark infringement, and making his software out to be so hard to make when it is a file copy/rename/delete program...LOL!

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  95. Re:Virtulize? - Emulate?!! by ripvlan · · Score: 1

    The monkeys on the internet have been active !!!

    Thanks for the link. It is amazing how far technology has progressed. To think that it took a WHOLE PC to run Windows/DOS and now it can run (pretty well) in a scripted language hosted by another app. I took a look at the source of one of these JS emulation projects and it is amazing the level at which it works - pretty darned cool. I played DOOM in a browser a few years ago - worked better than my 486 of yesteryear.

    I'll bet if I looked I'd find one as a VBA macro in Excel.