![]() ![]() I thought of things like robots, a homemade wheater station, or a talking toaster. So I think ReactOS can really be useful for smaller projects, if paired with well written software.īasically as a free runtime for self-written programs.Īnyone who needs something like that would probably be much better off with WinPE or Linux, I think. It seems to me that smaller programs written by individuals do run better on ReactOS than commercial bloatware. ![]() MixW2 (radio stuff), FlashPlayer 9, ShockWave 10.1, 7zip 9.25, Zemu (z80 emulator), wglgears (OpenGL gearwheels demo) Wait, here's a little -albeit outdated- list : EasyISO, FoxitReader 2, IrfanView 4.23, VLC 2.0.1, ICProg, Firefox 2.0, I wanted to use that machine right beside my soldering station for electronics stuff and for programming.īut sadly VB6 didn't properly run on it, so it was of little use for me (VB5 kinda did, just like old Delphi).īut on the positive side, there were a few programs that worked quite nicely, almost bug-free. In fact, I prefered to use the command line instead, because I was afraid of data corruption.Ī few years ago I even installed ReactOS on a dedicated PC. It is still very buggy! □ In previous versions it wasn't much of a help. I haven't tested it yet, but I will as soon as possible.Īnd yeah, that explorer. Thanks for the testing and your feedback! ![]() I have all sorts of crazy, outlandish ideas I'd like to see the ReactOS team implement, but as of right now they should focus on just making it a solid, Windows-compatible OS. I've been dreaming for years of having a Windows-compatible operating system that I could take around with me on a USB and run on different computers, and since ReactOS is open source without Micro$oft's bullshit licensing model, I think this may actually be possible.Īnyway, enough rambling. Or, maybe you could even run applications in a self-contained bubble with all their own libraries and whatnot, kind of like a chroot jail on Linux.Īs far as memory management goes, I'm not sure how possible this is, but I'd like to see them adopt a more Linux-like model where the swapfile only gets touched whenever it is needed, and physical RAM is used as much as possible.įinally, I'd like to see support for LiveUSB persistence, possibly with a UEFI key lifted from Ubuntu so that you can run it on systems that have SecureBoot enabled. I'm thinking you could do it in such a way that each program you installed could have its own registry, and you'd be able restrict or allow access to certain things on a program by program basis. Inbuilt sandboxing would be another great thing to have in ReactOS, from both a security and stability standpoint. Heck, maybe a clever hacker could port WINE (aww, I made a lame pun □) and use it for running particularly troublesome apps. ![]() Now, I know the idea is to make it a Windows clone, and as such it will never be entirely *nix-ey, but a working *nix subsystem would kick ass and make it easier to port other open source programs to the OS. I think it would also be cool if they made it POSIX compliant as well, with support for things like the X Windows system. It would be cool if they could set it up so that things that merely use Win32 API functions can be handled natively, while the x86 emulation is used only for things that absolutely require it. It makes me wonder if maybe a full x86 emulator is in the works for things like the ARM version of the OS. I like the fact that it doesn't rely on V86 mode, and as such can be ported to platforms other than 32-bit x86. The one thing that REALLY impresses me about ReactOS however, is its NTVDM implementation. I honestly can't wait for the day where ReactOS can replace Windows for most users altogether, especially since M$ have been driving Windows into the ground with all the telemetry and forced updates and other stupid bullshit. It just goes to show how hard the ReactOS team have been working to make this a viable OS. In all seriousness though, that's quite a significant list of features. Though for the current desktop systems this is not a problem. Here is a recent article about their NTVDM, though it does not say about using DosBox code.Īlso not a word about the downside of full software emulation: slower. I should go and look at the sourcecode for that component to see what they've done. If memory serves, they modified DOSBox to serve as their OS's NTVDM replacement not too long ago. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |