VOGONS

Common searches


First post, by Hamby

User metadata
Rank Member
Rank
Member

This https://winworldpc.com/product/services-for-unix/20 has me wondering.
Would it make it possible to compile old Linux/Unix source code to run under Windows NT/2000/XP?
I have to admit, it would be kind of amusing to play some of the old freeware Linux games natively under Windows...

Reply 1 of 4, by Jo22

User metadata
Rank l33t++
Rank
l33t++

Sounds interesting! 😀 Reminds me a bit of CoLinux/AndLinux for Windows XP x86.
http://www.colinux.org/

It worked so well, that I could install WINE and run some Windows programs with it.

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//

Reply 2 of 4, by doshea

User metadata
Rank Member
Rank
Member
Hamby wrote on 2021-02-11, 21:32:

Would it make it possible to compile old Linux/Unix source code to run under Windows NT/2000/XP?
I have to admit, it would be kind of amusing to play some of the old freeware Linux games natively under Windows...

Yeah, that's a big part of what it's for! Games might be a problem though. If they run on the console, they probably use SVGALib, which I'm pretty sure SFU doesn't provide an implementation of - SVGALib is more of a Linux and FreeBSD thing than a standard "Unix" thing. If the games are X11 ones, they might build but note that you'll need to get an X server because there isn't one included. I don't know if SFU would provide support for X extensions like OpenGL though.

And Jo22 is right, coLinux was really nice! It was so much faster than running a VM. It filled a different role though, I think: it was for actually running Linux directly under Windows, whereas SFU provides a few Unix-style tools and the ability to more easily rebuild Unix source code on Windows. With coLinux you didn't need to rebuild anything, but it wasn't really integrated into Windows, whereas with SFU you need to rebuild things but you end up with tools running natively in Windows.

Reply 3 of 4, by BloodyCactus

User metadata
Rank Oldbie
Rank
Oldbie

Well, 1.0/2.0 SFU was a buggy mess. I think later 3.5 was ok. If you wanted to build stuff you were better off using djgpp and all its installed packages for api's.

--/\-[ Stu : Bloody Cactus :: [ https://bloodycactus.com :: http://kråketær.com ]-/\--

Reply 4 of 4, by doshea

User metadata
Rank Member
Rank
Member
BloodyCactus wrote on 2021-03-01, 13:04:

Well, 1.0/2.0 SFU was a buggy mess. I think later 3.5 was ok. If you wanted to build stuff you were better off using djgpp and all its installed packages for api's.

Isn't there benefit to having a native Win32 application instead of a DOS application in quite a few cases though? I suppose you don't need a native Win32 application to use long file names, but networking for example I would expect to just work with Win32, whereas for a DOS application under Windows you need a packet driver shim or something, and you need to pick a networking library to use, etc.?