Remote: Windows 3.11 Administrator (m/f/d)
gulp.de
gulp.de
I worked for a rail operator and the driver interface systems of our locos (from other suppliers) were running on WinXP. We wanted some changes and feature upgrades, but the supplier said it was obsolete and they would not do any code changes to the WinXP software. Instead, they were telling us to move to a QNX-based version of it (which came with all of the fun joys of ensuring feature and interface equivalence for both the system and the human-computer interfaces). This was even for old locos, where moving to the QNX-based system wasn't just about running the same front-end software on a different OS, but in some cases was a fundamental hardware design upgrade (i.e. moving from a dumb terminal with a rack of hardware in a cupboard to fully integrated computers in the dash), which then meant making it interface with other hardware systems that may not be designed to talk to it. In some cases, those additional systems had to be upgraded. It was well in to 8 figures of work to do.
I am surprised that Siemens have, in some degree, allowed ongoing support for this. Whichever operator uses it must be fairly big in order to bend them to still actively manage it.
The ICE 1 and ICE 2 trains use this for their internal system. Deutsche Bahn will keep them running until at least 2029 (ICE 1) and 2030 (ICE 2).
A co-worker showed me a video of a display of the passenger information system that boots in MS-DOS and then restarts after it fails to load network drivers. BIOS from 1996 (166 MHz, 8 MB RAM). I guess they also need some people to maintain network drivers (and serial/parallel port drivers and the applications using it).
SIBAS is also used in Japanese and Swiss trains.
(GE Canada tried to headhunt me for that but I don't want a job where a typo turns Toronto into a parking lot. Thanks but no thanks. I will stick to web pages.)
Much older than that are the IRS Master files: the US tax system runs on IBM 7074 assembler although I think the actual 7074 hardware is long gone.
If that were cheaper, or considered more reliable or less hackable, than upgrading the systems to run on more modern technology then why not, as long as they look ahead far enough to make sure they fund the required tutoring to get the knowledge being passed down a generation or two, and do it before getting to the point where not having enough young experts actually has become a problem.
Also the PDP-11 was designed at the time boundary of core vs semiconductor memory with the clear intent to be able switch to semiconductor which led to an unusually flexible design around memory (and also affected I/O design). Check this 1975 paper https://dl.acm.org/doi/pdf/10.1145/800110.803541
> One of the plan’s priorities is the retirement of the Business Master File by FY2027 and the Individual Master File by FY2028
But it's not at all clear whether there's funding available to execute this plan.
I mean, yes, it's been 15 years and now only about five remains (because these projects never meet deadlines, let's face it) so they are nearer the finish line ... but it's very far still.
There HAS to be a project to feed the Master file(s) thru a modern AI to analyse and document the file(s).
Your Honor, my client could not have committed tax evasion because these were the most likely numbers based on millions of tax reports analyzed.
Please, please do that in front of a judge, I will bring the popcorn.
But I refer to the IRS's core executable code. Isn't the current state of affairs that it is code that is not well-documented, or not even documented at all ?
That's the impression I have gotten. Correct me if I am OTL.
In 80s, people said "it is good, that we don't have western infrastructure, because when become democracy and need it, will build all new from zero".
What really happened then, few waves of upgrades at West, when obsolete systems exported to developing countries very cheap.
But this is not whole picture. As First World is just about Billion humans (from more than 6 Billion at about Y2K) and have very limited land, number of obsolete systems exported to developing countries is just not enough for their size, so developing countries could not build whole infrastructure from just obsolete systems from West, but have to do (or to buy) something other.
So now, developing countries usually have mixed infrastructure, partially already obsoleted when imported systems, partially modern systems (many made in China), and partially some custom, even literally hand-made or garage-production.
Assuming that you’re male, would you be inclined to apply for a job if the description referred only to the “female employee who will hold this position” and what “her” responsibilities will be?
That’s essentially analogous to the situation that women have when applying for jobs in German-speaking countries.
The burden of proof still lies on the people arguing that word X does not include women.
There is no sense to accept risks of business continuity and prolong such outdated software with heap of security vulnerabilities together with significant hard-'n'software limitations.
I propose: - SWAP ALL unsupported system software (Win 3.11) and start using modern opensource OS distributives. - migrate all GUI's to to web interfaces with flexible markup. I believe you will require different resolutions and displays also! - to expect regular system software update process in critical infrastructure.
Now i know the reason why trains always coming not in time. We all wait until Win3.11 is loaded))
I am already surprised that a company still support this target knowing that most dev tools for this platform are more found over enthusiast website rather than Microsoft itself. And having hardware for making these tools running too!
As an example, starting DOSBox-X with an empty scratch directory mounted as drive C, the Visual C++ 1.52c CD-ROM mounted as drive D, and no additional configuration,
C:\>copy con hello.c
#include <stdlib.h>
void main(int argc, char **argv) {
puts("Hello, MS-DOS.");
}
^Z
1 File(s) copied.
C:\>set tmp=c:\
C:\>set path=d:\msvc15\bin;%path%
C:\>set include=d:\msvc15\include
C:\>set lib=d:\msvc15\lib
C:\>cl hello.c
Microsoft (R) C/C++ Optimizing Compiler Version 8.00c
Copyright (c) Microsoft Corp 1984-1993. All rights reserved.
hello.c
Microsoft (R) Segmented Executable Linker Version 5.60.339 Dec 5 1994
Copyright (C) Microsoft Corp 1984-1993. All rights reserved.
Object Modules [.obj]: hello.obj
Run File [hello.exe]: "hello.exe" /noi
List File [nul.map]: NUL
Libraries [.lib]:
Definitions File [nul.def]: ;
C:\>hello
Hello, MS-DOS.
C:\>
Alternatively, the full Visual C++ 1.52c GUI environment should run on any 32-bit x86 version of Windows 10.[1] https://en.wikipedia.org/wiki/DOS_Protected_Mode_Interface
If only it was NT 3.51 instead of Windows 3.11, I might be tempted…
I think they can't update the internal system responsible for the engine and brakes that easily, as well as the cockpit control systems.
But the system that displays the time and the next stations. With some investment you can communicate via serial or parallel port with the internal system. I guess using the WIFI for this instead would be a problem with security and reliablity, so they have to use the internal system.
So this is probably spot on.
(Having said that, I detest the usage of win3.11 here anyway ;)
Talking Win 3.1, it means using Quick C / MFC 1.0 and co. that I image no today AI would learn as deprecated.