And commit / contribution restriction

Why do you ask in the first place?

copy-paste isn't even the point. If some miracle hacker starts submitting code with the similar algorithms, they'll be found out pretty fast.

This has always been a hard rule of ReactOS. If you look at leaked Windows source code, you are banned from the project/community.

I'd say yes

Discussing this might lead to someone looking at leaks

If you want to look at some Windows source code without getting in trouble... some where it's even legal to copy-paste... here you go https://github.com/microsoft/winfile

This is not official chat — official is https://chat.reactos.org but it doesn't matter in this case

totally not an excuse

i don't know what there is to be curious about.

Just a shitty source code as usual I guess

You shouldn't even look at leaked source code

The fact that ReactOS lost years of development and good will due to a stolen-source-code allegation makes it a sensitive topic. They must always be taken very seriously, and prodding around in an attempt to look at a code leak and still contribute to ReactOS does a lot of harm on its own. You've very likely just put yourself as extremely suspicious and might not be allowed to contribute to the OS anymore.

It's this simple.

Just read the Wikipedia especially part about internal code audit

Or basically you're already will not be able to contribute

wii's iOS system's source code leaked

Well, there's nothing new inside this. Yes with the N64 internals.

But... The XBOX one... Wow.

The issue is simple: if you look at a leaked code, you will see how it handle specific things, you want it or not

So when you write ReactOS code you do this by knowing how the original one was written

The risk of emulation is really high, even if not intentional

I think this is the point

So when you write ReactOS code you do this by knowing how the original one was written

Moreover, if Big M could somehow prove that a ROS developer downloaded the leak, even if he didn't use it to copy, there would be no excuses at all

This extends to leaked documentation too

And if you have been working for Microsoft

Yep

<hbelusca> What about if you have worked on Office ? 🤔

Probably

i swear there s build glitch. I have freeldr in fixed linux btrfs root directory, so i supposed as ninja option give prebuilt iso, i extracted the "reactos" folder to home directory, used cfg file for hd0, and boot...

first boot was successful (text console boot though). reboot and... something from below APC level (i guess its due to audio DPC drivers that failed to implement above some API) and stucked there.

the topic is.. as for normal bootcd setup to btrfs neither has NDIS Lan nor network configuration interface. that is awkward. so, audio and ndis DPC or like that are connected in API, so modern low power CPU hasn't same ISA as older ones. that way xqemu wraps old opcodes from DPC API.

i would say it is fault of such buggy version of gcc or make config, or macros that target old assembly then where ros-arm-bringup corrupted the build environment with code exclusive for armv4. i wonder what parts we need to reimplement.

even worse, why not ask for eltech and 4corn so that eltech make an $objdump ntoskrnl.exe --arch=armv6 -o ntoskrnl.s meanwhile 4corn does reverse engineer to static decompile manually. so the fusion between Risc and React

even worse, why not ask for eltech and 4corn so that eltech make an $objdump ntoskrnl.exe --arch=armv6 -o ntoskrnl.s meanwhile 4corn does reverse engineer to static decompile manually. so the fusion between Risc and React

It's not so hard to obtain ntoskrnl for armv7 (thumb-2) or armv8-a (aarch64) from public, but why armv6? 😅

Windows 7 on ARM ran on armv6

But one does not simply obtain it 👌😅

i plan to get involved in some specific area to show people anyone can develop for his zero pi and may be from scratch to something greater than BBC BASIC on risc os

i plan to get involved in some specific area to show people anyone can develop for his zero pi and may be from scratch to something greater than BBC BASIC on risc os

oh that's nice

https://reactos.org/wiki/ARM_Port article might contain some useful information

however I don't know if UEFI / ACPI is applicable to ARMv6 — probably yes, since it's universal, but I never seen it "in the wild"

@AppleCyclone might know how it was done

i plan to get involved in some specific area to show people anyone can develop for his zero pi and may be from scratch to something greater than BBC BASIC on risc os

also, you might want to join our official chat development channel: https://chat.reactos.org/reactos/channels/development be welcome 🙂

mhm, seems to be very specific on drivers and conditions. that's the problem. we need encaurage pc sticked people to make a lift from the low land. even would be trivial dig the code (i've been there) and fork it with traditional GNU tools. "ninja, get out of our way"

what the problem with ninja? it's a part of build system, not much relevant to the compiler and architecture stuff

though I don't know how well our toolchain is adapted for cross-compiling

ping @extravert34

It should be trivial to tell CMake to use generate Makefiles instead

nothing is really wrong with ninja

<hbelusca> ninja is just a more efficient make, but that's it.

speaking of build tools though, the new version of RosBE doesn't require me to put in -DPCH=0 anymore and it's great

This has always been a hard rule of ReactOS. If you look at leaked Windows source code, you are banned from the project/community.

Excommunicate Traitoris

speaking of build tools though, the new version of RosBE doesn't require me to put in -DPCH=0 anymore and it's great

It's turned off by default atm. What's the problem with PCH build for you?

on RosBE 2.1.2, it failed to build by default and I needed to pass that to configure.sh for it to work

last I knew it was a known problem

now if I use -DPCH=1... $ ninja bootcd ninja: error: 'base/applications/calc/calc_pch.h.gch', needed by 'base/applications/calc/CMakeFiles/calc.dir/convert.c.obj', missing and no known rule to make it

that's a pretty big issue :P

at least it works by default so not that big

$ time ninja bootcd [...] real 5m18.641s user 47m38.620s sys 5m6.528s can't complain about these times anyway :P

peak ReactOS. I just tried installing it in PCem :P

thanks, not helpful :P

I usually run it in qemu where it works fine

man...changed graphics adapter to plain VGA, "Please wait while the ReactOS setup initializes itself and discovers your devices..." it stays here for a good few minutes xD

now if I use -DPCH=1... $ ninja bootcd ninja: error: 'base/applications/calc/calc_pch.h.gch', needed by 'base/applications/calc/CMakeFiles/calc.dir/convert.c.obj', missing and no known rule to make it

yeah, atm it doesn't work that's why it was turned off)

we have a PR for that, but it has one problem... https://github.com/reactos/reactos/pull/2764

and now it just crashes PCem for some reason.... haha

that should never actually happen. Unless it's creating a triple fault in the CPU, but I doubt it

<hbelusca> Is there a serial port in PCem?

<hbelusca> At worst, try booting selecting "Debug (Screen)"

<hbelusca> Maybe you'll be able to obtain some more information.

It technically does but I don't think it's usable for anything but the built-in mouse emulation. It definitely is not a debugging platform

honestly I could give a whole rant about PCem and that's not appropriate in this group. It has almost zero documentation and has some major points of suckage

however I don't know if UEFI / ACPI is applicable to ARMv6 — probably yes, since it's universal, but I never seen it "in the wild"

pretty much nothing too special

it can play 3D Space Cadet Pinball, so it has that going for it