i was thinking about Valve's Linux support (Steam play) and i was wondering
about asking them to support ReactOS via development...
Since Windows XP/2k3 are being abandoned, maybe ReactOS could still run
Steam games... if they support it.
what do you think?
I believe from the testbot log, that my commit made some DLLs grow out of
their assigned memory allocation, but I don't know how to update the dll
address mappings. Help appreciated.
Hi all!
Let me invite you to the August 2018 meeting, taking place this
Thursday, August 30, 2018 at 19:00 UTC.
Invited members will again receive their credentials shortly before the
meeting.
The current agenda is:
1. Status Reports (extended)
Note that this is the first meeting after both GSoC and the
Hackfest.
Participants in either effort are encouraged to also report
their related work, what they liked and didn't like about GSoC/
Hackfest, and what we could do better next time.
As always, I'm open for additional proposals.
I also have to announce that I will definitely be unavailable during the
entire September, so someone else has to invite for and lead the
September meeting.
Best regards,
Colin
Hi all,
I took some time during Hackfest to upgrade our Test_VBox Testbot to
Ubuntu 18.04, which finally brings us VirtualBox 5.2.x support for
sysreg2. Pierre also worked on the relevant BuildBot scripts to improve
their reliability.
This has resulted in
https://github.com/reactos/buildbot_config/commit/388a831eb5ccf67535d8cbd6d…
and since using that script, the infamous "IVirtualBox object is null"
bug hasn't occurred again :)
The upgrade from VirtualBox 4.3.40 to 5.2.10 also resulted in unbearably
slow serial port output at first, but this could be fixed by
https://github.com/reactos/sysreg2/commit/a4eb4a4551618b4af4dc1985ad8c55fe0….
Have a look at this commit if you encounter a slow serial port output in
one of the latest VirtualBox versions with either operating system.
This only leaves a funnily flawed WINE test left, which currently causes
the entire regression testing process to come to a standstill:
https://jira.reactos.org/browse/CORE-14975
Cheers,
Colin
|My proposed architecture diagram for ENIW: Linux app systemd <>
systemd2svchost Windows userland ------ User-mode Linux kernel -------
SVCHOST Windows services ENIW.SYS Windows personalities Kernel-mode
drivers for everything -------------------------- NTOSKRNL.EXE
----------------------------------- ENIW is a component to implement
WSL-like functionality named after WINE and its bacronym is ENIW never
imitated WSL. systemd2svchost is a service translator to run systemd
units as svchost services. Forum thread:
<https://www.reactos.org/forum/viewtopic.php?f=9&t=17434> JIRA ticket:
<https://jira.reactos.org/browse/CORE-13613> Yours, faihfully Erkin Alp |
Hi Timo et al.,
To make the issue wider known than just me comment on GitHub. That
commit introduced a regression.
Le 20/08/2018 à 18:07, Timo Kreuzer a écrit :
> https://git.reactos.org/?p=reactos.git;a=commitdiff;h=c219be9409af429909b14…
>
> commit c219be9409af429909b1433da536516b3c3ab823
> Author: Timo Kreuzer <timo.kreuzer(a)reactos.org>
> AuthorDate: Sun Feb 4 19:20:56 2018 +0100
> Commit: Timo Kreuzer <timo.kreuzer(a)reactos.org>
> CommitDate: Mon Aug 20 18:07:35 2018 +0200
>
> [NTOS:MM] Fix paged pool expansion
> ---
> ntoskrnl/mm/ARM3/pool.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/ntoskrnl/mm/ARM3/pool.c b/ntoskrnl/mm/ARM3/pool.c
> index 7cebabe818..113a7aa981 100644
> --- a/ntoskrnl/mm/ARM3/pool.c
> +++ b/ntoskrnl/mm/ARM3/pool.c
> @@ -561,10 +565,11 @@ MiAllocatePoolPages(IN POOL_TYPE PoolType,
> MiInitializePfnForOtherProcess(PageFrameNumber,
> (PMMPTE)PointerPde,
> MmSystemPageDirectory[(PointerPde - MiAddressToPde(NULL)) / PDE_COUNT]);
> +#endif
>
> /* Write the actual PDE now */
> -// MI_WRITE_VALID_PDE(PointerPde, TempPde);
> -#endif
> + MI_WRITE_VALID_PDE(PointerPde, TempPde);
> +
That little change for x86 actually breaks VBox support. It hits an
ASSERT during 3rd stage:
*** Assertion failed: PointerPde->u.Hard.Valid == 0
*** Source File:
/srv/buildbot/Build_GCCLin_x86/build/ntoskrnl/mm/ARM3/miarm.h, line 975
See testbots for instance:
https://build.reactos.org/builders/Test%20VBox/builds/8625/steps/test/logs/…
Cheers,
Pierre
--
Pierre Schweitzer <pierre at reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.
Why are these misleading? These are checks that Windows does that we are
missing.
Guys, open PRs for changes like these ffs.
Best regards,
Alex Ionescu
On Wed, Aug 8, 2018 at 7:14 PM Thomas Faber <thomas.faber(a)reactos.org>
wrote:
>
> https://git.reactos.org/?p=reactos.git;a=commitdiff;h=1ed0f9ab576f094b27e11…
>
> commit 1ed0f9ab576f094b27e11ba374738ecabc00e2e6
> Author: Thomas Faber <thomas.faber(a)reactos.org>
> AuthorDate: Wed Aug 8 19:58:56 2018 +0200
> Commit: Thomas Faber <thomas.faber(a)reactos.org>
> CommitDate: Wed Aug 8 20:08:38 2018 +0200
>
> [HAL] Remove misleading debug prints about USB controllers.
> ---
> hal/halx86/legacy/bussupp.c | 26 --------------------------
> 1 file changed, 26 deletions(-)
>
> diff --git a/hal/halx86/legacy/bussupp.c b/hal/halx86/legacy/bussupp.c
> index a37d875ede..4d20396560 100644
> --- a/hal/halx86/legacy/bussupp.c
> +++ b/hal/halx86/legacy/bussupp.c
> @@ -1128,32 +1128,6 @@ HalpInitializePciBus(VOID)
> }
> }
>
> - /* Check if this is a USB controller */
> - if ((PciData->BaseClass == PCI_CLASS_SERIAL_BUS_CTLR) &&
> - (PciData->SubClass == PCI_SUBCLASS_SB_USB))
> - {
> - /* Check if this is an OHCI controller */
> - if (PciData->ProgIf == 0x10)
> - {
> - DbgPrint("\tDevice is an OHCI (USB) PCI Expansion
> Card. Turn off Legacy USB in your BIOS!\n\n");
> - continue;
> - }
> -
> - /* Check for Intel UHCI controller */
> - if (PciData->VendorID == 0x8086)
> - {
> - DbgPrint("\tDevice is an Intel UHCI (USB)
> Controller. Turn off Legacy USB in your BIOS!\n\n");
> - continue;
> - }
> -
> - /* Check for VIA UHCI controller */
> - if (PciData->VendorID == 0x1106)
> - {
> - DbgPrint("\tDevice is a VIA UHCI (USB)
> Controller. Turn off Legacy USB in your BIOS!\n\n");
> - continue;
> - }
> - }
> -
> /* Now check the registry for chipset hacks */
> Status = HalpGetChipHacks(PciData->VendorID,
> PciData->DeviceID,
>
>