For one this winudf is compiled with https://openwatcom.org/ which targets older C89/C99 and legacy C++ standards alongside legacy platforms (DOS, OS/2, Win16/Win32). So unlikely direct reuse would help
Plus 16-bit segmented code. The code contains explicit "FAR" declaration for pointers, etc... when taking "outside" code to such an environment, extensive changes might be required.
Which is kind of the pointless since A) By being >100KB of _conventional_ memory this is practically useless for all DOS platforms, B) You have gcc-ia16 for those anyway if you wanted to for bragging rights or whatever , C) for 9x and above you can already use normal gcc.
Watcom also has terrible licensing up to the point it is up for debate whether you can really publish anything with it that's not also using Watcom license.
We all know the real reason is that this is just AI slop.
Quick glance at readme seems to indicate this is layered between block device and filesystem.
So does this offer both disk access INT 13h and filesystem INT 21h as separate TSR?
In the old day you also had a CD-ROM driver depending on it being ATAPI or SCSI and MSCDEX for the filesystem part. I never actually noticed that DVDs didn't work in DOS. There could have been a use case for loading a buttload of shareware on a single disk but I guess DOS was truly dead by then.
I feel like it makes more sense to reskin a modern linux distro than to add blue ray support to these operating systems?
I really wish the use-case was included, are they trying to show movies while doing cat scans on a machine that can only run windows 98? Just the love of the game?
So many questions about this answer to a very specific problem.
For fun and experimentation. There's a large group of retro OS and computer enthusiasts that now have the opportunity to add new hardware support for old OSs that would never have been feasible at the hobbiest level. For example, support for some GeForce 10xx GPUs was recently created for vanilla Windows 2000. Using a skinned Linux would defeat the purpose, it's about using the specific OS they're interested in on whatever hardware they want.
I like both. I would actually really dig pixel-perfect recreations of retro OS styles on top of modern, secure OSes. Unfortunately the number of such creations is currently zero.
Whatever it is you think exists that is already pixel-perfect... I would bet money it really isn't.
Modern Linux has deprecated a lot of legacy hardware support, Desktops now eat a lot more ram, and many 3rd party oddball GPU drivers now only work on Windows systems.
[1]https://code.videolan.org/videolan/libudfread
Watcom also has terrible licensing up to the point it is up for debate whether you can really publish anything with it that's not also using Watcom license.
We all know the real reason is that this is just AI slop.
So does this offer both disk access INT 13h and filesystem INT 21h as separate TSR?
In the old day you also had a CD-ROM driver depending on it being ATAPI or SCSI and MSCDEX for the filesystem part. I never actually noticed that DVDs didn't work in DOS. There could have been a use case for loading a buttload of shareware on a single disk but I guess DOS was truly dead by then.
I really wish the use-case was included, are they trying to show movies while doing cat scans on a machine that can only run windows 98? Just the love of the game?
So many questions about this answer to a very specific problem.
Whatever it is you think exists that is already pixel-perfect... I would bet money it really isn't.
I would love to be proven wrong though.
Modern Linux has deprecated a lot of legacy hardware support, Desktops now eat a lot more ram, and many 3rd party oddball GPU drivers now only work on Windows systems.
Many people still dual boot for good reasons. =3
> 3rd party oddball GPU drivers now only work on Windows systems.
More like the opposite.