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.
This is great. Saw a ton of useful repos here. I'd prefer using VSBHDA driver for Sound though. If you have any fixes for those cards see if you can land them there. Great work.
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.
I would too. With lots of tuning it's possible to get Chicago95 and similar looking close, but it's never exact in appearance or behavior. Wish we could have a real Windows 2000/XP shell over top a modern Linux kernel, that'd be cool!
It's one of the reasons I still enjoy using XP and 7 with the classic theme, it's just such a crisp and usable UI. Not that Plasma etc. aren't usable of course, but there's a lot of nostalgia and comfort in those old UIs.
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.
I have yet to find an old laptop that could run the open source GPU nouveau driver properly, or the legacy EOL Nvidia dkms drivers on modern kernels above 6.1.x-6.3.x. There were some efforts to port the drivers to modern kernels, but most older i7 laptops GPU will be locked in the default recovery mode graphics.
Windows from decades ago will still accept the last official GPU driver installers, fully support floppy drives, and fit in a few hundred MB of ram.
Voodoo has full software emulation on 86box, and made old games accessible. Yet finding the official cards is fairly silly.
I'm wondering why this is implementing udf on its own and not reusing and improving videolan's libudfread[1]
[1]https://code.videolan.org/videolan/libudfread
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.
Because the author never wrote it since it's slop?
A while ago, I thought about making dos to early winnt drivers.
The information was basically nonexistent even with the SDKs and MSDN.
If Claude can pull working examples from private repositories or Hell or wherever it pulls information from, I say let him cook.
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.
This is great. Saw a ton of useful repos here. I'd prefer using VSBHDA driver for Sound though. If you have any fixes for those cards see if you can land them there. Great work.
Next time I need a blueray on Windows 1.0, now I know where to look!
The wait is over
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.
"look what I can make Claude do!"
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.
I would love to be proven wrong though.
I would too. With lots of tuning it's possible to get Chicago95 and similar looking close, but it's never exact in appearance or behavior. Wish we could have a real Windows 2000/XP shell over top a modern Linux kernel, that'd be cool!
It's one of the reasons I still enjoy using XP and 7 with the classic theme, it's just such a crisp and usable UI. Not that Plasma etc. aren't usable of course, but there's a lot of nostalgia and comfort in those old UIs.
https://github.com/mikuta0407/win4wine
Presenting: Windows XP's Explorer on WINE. The impossible has been made possible.
Oh my gosh, this is incredible. I'm going to try this out. Thanks for sharing the link!
This is cursed, I love it
>makes more sense to reskin a modern linux distro
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
T2SDE supports even MESA for VooDoo video cards. Modern Linux.
> 3rd party oddball GPU drivers now only work on Windows systems.
More like the opposite.
>More like the opposite.
I have yet to find an old laptop that could run the open source GPU nouveau driver properly, or the legacy EOL Nvidia dkms drivers on modern kernels above 6.1.x-6.3.x. There were some efforts to port the drivers to modern kernels, but most older i7 laptops GPU will be locked in the default recovery mode graphics.
Windows from decades ago will still accept the last official GPU driver installers, fully support floppy drives, and fit in a few hundred MB of ram.
Voodoo has full software emulation on 86box, and made old games accessible. Yet finding the official cards is fairly silly.
Have a great day =3
This guy backported nearly everything.
https://t2linux.com/
I guess „because we can“ and that’s perfectly fine in my opinion.
Why is this a thing in 2026 ? Passion ?