News for hackers. Stuff that matters.
Re:If there's no 16-bit layer in 64-bit Windows, how come 16... by VLM on Sunday November 03, 2013 @10:40AM (#6663502)
This is a good example of the straightjacked of backwards compatibility. Not too long, not too short, a fun display both of people who know what they're talking about vs just complaining.

Also a good example of inside the box thinking. The reason you need to run a 16 bit installer is the software isn't free or open source therefore a simple recompile with a newer version of debhelper or whatever isn't going to bring it up to modern packaging standards.

Re:If there's no 16-bit layer in 64-bit Windows, how come 16... by justin66 on Sunday November 03, 2013 @12:14PM (#6663993)
> The reason you need to run a 16 bit installer is the software isn't free or open source therefore a simple recompile with a newer version of debhelper or whatever isn't going to bring it up to modern packaging standards.

On the other hand, the old windows software in question will most likely actually run. Debhelper is irrelevant: confronted with a package of comparable age on Linux, you'll be digging up the source code and trying to make it build, not merely tweaking the package, with all its ancient dependencies.

Re:If there's no 16-bit layer in 64-bit Windows, how come 16... by thwarted on Sunday November 03, 2013 @08:30PM (#6666156)
You make your linux binary executables future-proof by statically linking them. It's a rare event that it happens, but I've no problems with 15 year old a.out binaries on 64-bit systems.
Re:If there's no 16-bit layer in 64-bit Windows, how come 16... by anyfoo on Monday November 04, 2013 @11:59AM (#6669641)
As soon as they use for example, say, utmp, they will break. Worse, they might trash your utmp. The utmp format was changed with the transition from libc5 to glibc 2, to support IPv6. You might not care too much about utmp nowaways, but it's an example for something which changed.

Also, your 15 year old statically compiled binary will contain every little bug any of the linked in libraries had those 15 years ago.

Re:If there's no 16-bit layer in 64-bit Windows, how come 16... by thwarted on Monday November 04, 2013 @07:50PM (#6672329)
And this is the trade off you make for not having the source, but it doesn't negate it as a method to keep things running for longer. If you should keep things running, without having the source, for that long, is another issue.
Re:If there's no 16-bit layer in 64-bit Windows, how come 16... by anyfoo on Thursday November 07, 2013 @07:03AM (#6688890)
Okay, I can agree, it certainly beats "not running at all" 8)
Re:If there's no 16-bit layer in 64-bit Windows, how come 16... by ateeqs on Sunday November 03, 2013 @08:47PM (#6666238)
Yeah, I am having the same issue trying to compile gcc on an emulated old MIPS. :-/
Re:If there's no 16-bit layer in 64-bit Windows, how come 16... by derleth on Sunday November 03, 2013 @04:49PM (#6665263)
Actually, no: I've had a lot more luck getting old Linux software working than old Windows software, as the Windows software inevitably has DLL Hell written all over it.
Re:If there's no 16-bit layer in 64-bit Windows, how come 16... by justin66 on Sunday November 03, 2013 @05:35PM (#6665450)
> DLL Hell

An issue that was relevant on the Windows 3.x operating systems and, on an unusually bad day, Windows 95/98. It's irrelevant to what we are talking about here and also kind of a red flag for Linux fanboyism.

Re:If there's no 16-bit layer in 64-bit Windows, how come 16... by derleth on Monday November 04, 2013 @02:59AM (#6667466)
Not in my experience: The lack of versioned libraries is still a problem and trying to dismiss it by calling me a fanboy is not logically sound.
Re:If there's no 16-bit layer in 64-bit Windows, how come 16... by gourlaysama on Sunday November 03, 2013 @10:53AM (#6663552)
"The reason you need to run a 16 bit installer" is to display a nice "Tough luck, you need a 32-bit computer to install this" message to the user, instead of an ugly Windows error message.

This was important at the time. And the whole point of backward compatibility is to allowed old applications (written, compiled and packaged at that time) to work.

Even if the software is open-source and has been repackaged in the meantime, the old version you found on a long-forgotten CD rotting away in your basement doesn't have that. The Windows philosophy is to make sure that this one still works (which is a crazy goal IMO, but an interesting one).

Re:If there's no 16-bit layer in 64-bit Windows, how come 16... by city41 on Sunday November 03, 2013 @11:48AM (#6663830)
MS has gone to great lengths to reach that goal. There is even special code in Windows to ensure the DOS version of SimCity works: http://ianmurdock.com/platforms/on-the-importance-of-backwar...
Re:If there's no 16-bit layer in 64-bit Windows, how come 16... by johnchristopher on Sunday November 03, 2013 @11:34AM (#6663758)
Crazy ? Well, that was one of the most important selling point of MS.

I wish I could run any old software under current Ubuntu. IE: gwibber.

Re:If there's no 16-bit layer in 64-bit Windows, how come 16... by alecdbrooks on Sunday November 03, 2013 @11:37AM (#6663771)
The reason for this hack is that 32-bit software used 16-bit installers long after the switch to 32-bit. [0] This isn't a matter of supporting Windows 3.11-era software, more like Windows 9x or even XP.

[0]: Like this guy: http://www.tomshardware.com/forum/107534-13-trying-install-g....

Re:If there's no 16-bit layer in 64-bit Windows, how come 16... by bluedino on Sunday November 03, 2013 @12:01PM (#6663911)
>> The Windows philosophy is to make sure that this one still works (which is a crazy goal IMO, but an interesting one)

It's a requirement. Imagine how many people would have never upgraded to Windows 95 if their Windows 3.x programs didn't work.

Each program Microsoft 'fixes' is additional sales.

Re:If there's no 16-bit layer in 64-bit Windows, how come 16... by mikeash on Sunday November 03, 2013 @11:22AM (#6663686)
There's no point in thinking outside the box when the box was built twenty years ago and your entire job is to make the stuff inside it keep working for another OS release.