111–120 of 135 posts
Correct me if I'm wrong, but this is running Wine on Linux on Windows. Not running Wine on Windows.
Technically speaking Wine is running on a emulated Linux-kernel (WSL1), just like Windows-programs under Wine is running on an emulated Windows-kernel.
So yeah. Turtles all the way down.
Earlier quoted context omitted.
Out of curiosity, since you might know: is Proton upstreaming changes or are they going their separate ways? I'm not informed enough to say whether the fork made sense or not, but my immediate reaction was that using a OS project with immense man hours and effort behind it for commercial gain without contributing back would be very ... questionable.
Yes, of course. Valve is a very good open source citizen. The fork was necessary because we have a fair number of changes that are not appropriate for upstream Wine. As a single example, we integrate closely with the Steam for Linux client for stuff like achievements and multiplayer, which obviously can't go upstream. I'm actually the guy who does the rebases, so I'm very motivated to keep the diff as small as possib…
Earlier quoted context omitted.
You can already do that with OTVDM: https://github.com/otya128/winevdm Using it not only any 16bit installer works, but also most 16bit applications. As an example you can play Exile by Spiderweb[2] on your Windows 64 PC. It even contains a .reg file that allows it to be installed system-wide so that you can run a 16bit .exe just by double clicking it in Explorer (or any other file manager). [1] https://github.com/ot…
> As an example you can play Exile by Spiderweb[2] on your Windows 64 PC. How is this of all things the go-to example? It's exactly what I want to do! Were these games more popular than I thought?
He's still making games, and they're still pretty much the same games they were--and to me that is a positive.
- Shipping a ext4 filesystem driver for Windows.
- Contributing to exfat/ntfs drivers for Linux/Mac OS.
Both would be even better.
If MS is now serious about cross-platform compatibility (and they have been moving in that direction), they should consider building a bridge over the filesystem divide as well. One or more of these would be useful: - Shipping a ext4 filesystem driver for Windows. - Contributing to exfat/ntfs drivers for Linux/Mac OS. Both would be even better.
Earlier quoted context omitted.
Looking at the install.inf file, I saw that they first remove a key from the registry with the name VDM in it. So I wondered what VDM means. > Virtual DOS machines (VDM) refer to a technology that allows running 16-bit/32-bit DOS and 16-bit Windows programs when there is already another operating system running and controlling the hardware. https://en.wikipedia.org/wiki/Virtual_DOS_machine So how come otvdm is needed…
Virtual 8086 mode isn't available when running a 64-bit OS, so the virtual DOS machine code simply won't work there. This is less of a problem with most 16-bit Windows applications since the limited 16-bit functionality they need is still possible under a 64-bit OS but making this work requires some extremely hairy kernel code.
Earlier quoted context omitted.
>I doubt anyone is missing much aside from a few nostalgic gamers. There's tons of 16-bit SCADA stuff in the world that it would be nice to not have to run on a ~20yo version of windows.
I hope those scada systems aren't running on regular Windows. If they are, they should be running on Win10 LTSB on 32-bit so they should keep working till at least 2025 if XP's level of compatibility was good enough to run them. If they can't be run on that, there's still MS-DOS licenses being sold and FreeDOS might also serve them in a pinch. If a system is not maintained for long enough that it's still running in c…
Earlier quoted context omitted.
Any CPU can only have one hypervisor running at a time. Thus the recursion stops pretty quick.
Well, yes and no. On modern enough hardware you can do nested virtualisation, so you can run kvm in esxi on hyper-v if you want. Not that it's very usefull, but it is a fun weekend project nonetheless.
Earlier quoted context omitted.
>I doubt anyone is missing much aside from a few nostalgic gamers. There's tons of 16-bit SCADA stuff in the world that it would be nice to not have to run on a ~20yo version of windows.
Aren't there still 32-bit versions of Windows 10? AFAIR only the server versions are 64-bit only by now.
Earlier quoted context omitted.
I hope those scada systems aren't running on regular Windows. If they are, they should be running on Win10 LTSB on 32-bit so they should keep working till at least 2025 if XP's level of compatibility was good enough to run them. If they can't be run on that, there's still MS-DOS licenses being sold and FreeDOS might also serve them in a pinch. If a system is not maintained for long enough that it's still running in c…
What if the manufacturer doesn't exist anymore?