Shared!!! Thank you for testing! @wiktorek140

😁

does windows viruses affects react os?

Ones that attack very specific bugs in Windows, no Ones that are normal and valid Windows programs, potentially yes.

Domain is reaktos)

how upgrade ReactOS up to domain Windows =)

It can't join an Active Directory domain, if that's your meaning.

It can't join an Active Directory domain, if that's your meaning.

Ones that attack very specific bugs in Windows, no Ones that are normal and valid Windows programs, potentially yes.

what virusee way to put it.

what

First time ever tried to make a screen saver

I just mimicked the powered-off charging animation of my phone.

nicely done

Though it did take some time for me to know how to use gdi apis and such

Desktop files aren't typically directly executable.

Are you doubling clicking that file itself? Try putting it in ~/.local/share/applications

I figured it'd be good to share it? But felt too lazy to create a repo on GitHub

does windows viruses affects react os?

Depends on which apps user will download.

UPVOTE ReactOS sees major update – MM and CC, PnP, I/O, KMDF, NTFS, compiler upgrades https://news.ycombinator.com/item?id=26075670

Any ETA for x64 port? I saw 2 issues before it's done.

Any ETA for x64 port? I saw 2 issues before it's done.

We do not give estimates for completion for anything.

We do not give estimates for completion for anything.

I see, but the amd64 manifests is already done, right?

Any ETA for x64 port? I saw 2 issues before it's done.

Only one and a half of devs are working on it directly

Only one and a half of devs are working on it directly

I think this branch is outdated, see the milestones.

I think master can do this, but with debug symbols.

the MSVC build.

See the nightlies.

When?

Every day ReactOS push changes, then in 4 months is a great leap.

I will test, sadly it has bugs with VirtualBox.

but I can run on Limbo x86.

I don't like VMWare because it's proprietary (less the KVM)

Yeah, but d3d9 is a great one.

Maybe 3D games are far better now.

I don't know the actual state of virtgpu.

Maybe OpenGL 3.0 is complete.

I know, 3 major releases apart.

I think the sync is easy but still a lot of code.

Code that need kernel abstraction, needs refactoring to the ReactOS KPI. This ones aren't easy.

Yeah, this ones are pretty easy.

But you need to remove obsolete code too.

and ReactOS has 9 million lines, then it's pretty bad to maintain with a good quality.

You need menpower.

Many of the code in ReactOS is pretty obsolete I think. They have a few Vista/7 APIs, and a big portion of software dropped XP support.

I think master can do this, but with debug symbols.

nope, current master x64 doesn't boot to desktop

nope, current master x64 doesn't boot to desktop

I think the kernel and MM is universal.

Then just port some API/ABI to make plus software works.

I'm pretty certain that they run Chromium.

This part is easy I think, Vista brought MAC and some exploit mitigations.

@x86corez Why Windows NT hybrid kernel is great when you have more work to secure the interfaces? Why not a NT microkernel?

@x86corez Why Windows NT hybrid kernel is great when you have more work to secure the interfaces? Why not a NT microkernel?

Explain 🇹🇷

Explain 🇹🇷

🇹🇷 is Turkey

Why NT kernel is great 🧐

Ones that attack very specific bugs in Windows, no Ones that are normal and valid Windows programs, potentially yes.

But, there's still very much code shared between Windows Server 2016 and NT4 (that version ReactOs uses), I guess. And malware exploits those probable bugs. Are they fixed or did you have rewritten a lot of core system to avoid future bugs inherited from MS development?

With the main exceptions of CDFS and FASTFAT (that Microsoft have open sourced), ReactOS doesn't use code from Windows. It's a reimplementation, not a fork. Exploiting Windows bugs generally won't work on ReactOS.

ReactOS aims to implement the public (and some of the private) API of Windows with wholly new code. Well-behaved programs would hypothetically run identically on the two systems if ReactOS recreates all of the APIs in use perfectly.

Ok, understood. Thanks

I kind of wished this program would be incorporated, but the devs haven't been interested. I guess that just means the other option is to run the EXE on top of it anyway :P https://github.com/microsoft/winfile

the build system has an optional components thing. This could be one of those...

I totally forget how to enable them.

well I got things half-way working... though it turns out that the QXL driver being installed/enabled made it so I don't have a mouse anymore :D

As for winfile... no luck.

There's usually more to compatibility than a version flag, but if you just want the program to believe it's on Vista, set a compatibility mode.

I don't know what you're trying to run, but it's likely that ReactOS just doesn't have the DLL functions to run it.

You can try to use compatibility mode to make it think it's on Vista (or a newer version), but if the DLL functions are missing, it still won't work.

But, there's still very much code shared between Windows Server 2016 and NT4 (that version ReactOs uses), I guess. And malware exploits those probable bugs. Are they fixed or did you have rewritten a lot of core system to avoid future bugs inherited from MS development?

The malwares are written for PE executables/NT architecture, then I think a entire version will be vulnerable. Chocolatey helps bringing secure signed packages.

I think malwares for Windows 10 can affect NT5+ and beyond.

With the main exceptions of CDFS and FASTFAT (that Microsoft have open sourced), ReactOS doesn't use code from Windows. It's a reimplementation, not a fork. Exploiting Windows bugs generally won't work on ReactOS.

Wrong, ReactOS implement the abstractions, you implement the syscalls and APIs, but the API/syscalls innerworking is made from scratch. It mimic a Windows environment: example: software x use API y and syscall test(). Both exist on ReactOS/Windows, but on ReactOS it uses clean-room to mimic the Windows behaviour. Then the malwares can work due to the binary compatibility.

I think it exposes automatically.

ReactOS is pretty similar to Linux mimicking Unix.

But Linux uses old methods.

And Linux is not binary compatible with Unix.

its not? i never realized that.....

I'm not sure what "old methods" it uses either. GNU and Linux were both clean-room reimplementations, though it's been a long time since they had a target to emulate. They've become the de facto standard in the Unix world instead.

For the most part Unices never were binary compatible with each other. Partly because the OSes had vastly different sets of APIs to target... they weren't even source-compatible if an application didn't make explicit effort to support multiple Unix OSes.