yeah.I know

RPi 3 ARM64 developers are here: https://t.me/raspberrypiwoa (but don't ask them to make ReactOS port, you can ask their help with testings if you're gonna work on ROS ARM port)

OK.Thanks.

The window title is pretty cryptic.

how to fix?, help

how to fix?, help

Search for virtualbox-dkms in your distro

how to fix?, help

Oh, wait Install too headers of your kernel

what

what

Hello sorry for the inconvenience :-) the three profiles are mine I'm proving the multi telegram accounts is a pleasure to be here :-)

what

...b-but ReactOS is not Linux 🙄

but it could be tbh like wine+ros-as-a-kernel-module= overthrow windows :p

What is the point of being 3 times in here?

https://www.youtube.com/watch?v=oEr_t5N8P1U

I want to know how to enable ReactOS to support USB keyboard and mouse on new computers (with XHCI).

My PC with Z97 motherboard can enter the ReactOS desktop, but I can't use a keyboard or mouse.

<Illen> A Z97 board still should include the EHCI controller, it should work fine in ReactOS, at least with VGal patches.

There is EHCI related content in the firmware settings, but there is no effect after the setting.

which options are in "XHCI Mode" at the top?

But setting it to Auto and Disabled didn't solve the problem.

C:\users\chungy\reactos>configure.cmd Your source path contains at least one space. This will cause problems with building. Please rename your folders so there are no spaces in the source path, or move your source to a different folder.

well then :V

https://discourse.pi64.win/t/mcci-usb-driver-status-2019-01-31/14/3

LOL! My message with GIF is now in the history of ARM64 driver development for Windows 😆 (see 3rd post in this thread)

That was totally unexpected 😅

lmao

😂😉

@dreimer are you here? Please lock this forum thread: https://reactos.org/forum/viewtopic.php?f=11&t=18260 — they're discussing patching Microsoft binaries... 😮

As you wish

In such a case... A PM is a good way too ^^

In such a case... A PM is a good way too ^^

Ah ok, good to know 🙂

Mattermost does not help because somehow I don't get the mentions on my phone as message. But in telegram does work fine.

Btw, what's that translated?

каулхацкер дытехтед

каулхацкер дытехтед

that's tower's russian dialect 😆 ("coolhacker detected")

Translator was... Shocked about that ^^

😁

I think tower breaks his words on purpose so only russians can read him

Well in that case... It was not good. That was a reported post reasoning ^^

Hehe xD

<BieHDC> what were these people really doing there? "patching ms binaries" is not really descriptive

Wat? We are mattermost linked too?

No, that's Discord bot

I see

<BieHDC> 😄

It would be interesting to see what will happen if bridge that chat to mattermost as well (as separate channel ofc) 😏

Hell freezing over?

B33r getting warm?

<BieHDC> we have limited write access to staff to not cause havoc

¯\_(ツ)_/¯

<BieHDC> anyway, are you going to tell me now? 😛

Not warm yet

even if you did link the same channel you'd get broken convo's between mattermost and discord in here :p

right, two different Telegram bots could not read each other messages

yep :p

in discord you'd get broken convo's between telegram and mattermost i'd suppose xP

But if implement mattermost bridge in the same bot, it would work

eeh? but then how would it pass messages from mattermost to discord?

eeh? but then how would it pass messages from mattermost to discord?

in three ways

eh? hmm

Hello

Hello

Hello

Sup

I want to make more verbose the debugging of ndis driver

Ndis has a debug.h file

But there is no enough info abou it

I want to make more verbose the debugging of ndis driver

https://github.com/reactos/reactos/blob/master/drivers/network/ndis/ndis/main.c#L18

maybe set this to MAX_TRACE ?

drivers/network/ndis/ndis/main.c

yeah, that file

and besides MAX_TRACE there are some more constants

like DEBUG_PROTOCOL or DEBUG_PACKET

Eeee!!!! Chromium 69!!!!!