Ask yourself the following question: If your hypothesis was correct, then how is it possible that our kernel is still much incomplete and buggy, after all those years?

All ReactOS releases so far (available on sourceforge) are debug builds.

When the ISO is analysed by these scanners, usually you will get the list of the files (in the ISO) that the scanners think they contain a virus.
So you can then look at their source code in our repo, to see whether they contain weird-looking code.

Then maybe wait until ReactOS becomes more user-friendly.

And what would be the difference compared to the current state of ReactOS?

It seems they are using ReactOS' command line interpreter (cmd.exe), which is itself based on the one from FreeDOS (hence "Tim Norman" appearing in the copyright license). Do you say this based only on the Tim Norman reference, or is there something else you found? All I can see from FLIR themselve...

It seems they are using ReactOS' command line interpreter (cmd.exe), which is itself based on the one from FreeDOS (hence "Tim Norman" appearing in the copyright license).

1. Optional RamDisk loaded. 2. SYSTEM hive loaded: a. Boot file system enumerated, a. Boot drivers enumerated, b. NLS data loaded. 2b. Firmware Errata INF file loaded. 3. ntoskrnl.exe and hal.dll (exact files depending on whether you use standard vs. ACPI vs multiCPU....) loaded. 3b. KD transport DL...

The bootloader code will tell you exactly all what you need:
Starting from this function
https://git.reactos.org/?p=reactos.git; ... =HEAD#l819
just follow the ones it calls.

erkinalp wrote: ↑

Sun Apr 19, 2020 7:35 am

github.microsoft.com is now used for GitHub's US west coast administration.

Or not...

If it was just "der-die-das-die" and co! It's also all about the ending of the words themselves!!!!

Just so you know that the change to the underlying method of hosting images does have an overhead on the poor user who has to do the uploading. What about an automatic conversion with user warning when the user uploads an image that is larger than the limit? (like: "Warning! Your image is too large...

For "academic purposes" would be an answer.

Updated list for NTDLL.DLL: LdrAlternateResourceEnabled LdrFindResourceEx_U LdrHotPatchRoutine LdrInitShimEngineDynamic LdrQueryImageFileExecutionOptionsEx RtlAddCompoundAce RtlAddressInSectionTable RtlAppendPathElement RtlCaptureStackContext RtlCheckProcessParameters RtlDebugPrintTimes RtlEnableEar...

Certainly because developers want to quickly run ReactOS and do the tests with the system allowing full access.