reactos/boot/bootdata
Joachim Henze 63c4d66d6f [0.4.9][BOOTDATA] hivesys.inf Play safe with ServiceGroupOrder
Restores *inferior* code for older branches.

I recently ported back the *proper* 0.4.15-dev-4352-g cfe387a9b0
as part of:
0.4.10-release-186-g e5d8019d24
0.4.9-release-197-g 557db9a1ac
0.4.8-release-203-g 78daf4169a
0.4.7-release-229-g e0a3b0c8f5

That backport worked very well in releases/0.4.11 to releases/0.4.14

and it also caused no severe issues for releases/0.4.7 to releases/0.4.10
e.g. the mouse and keyboard works well, tested with VBox4.3.12 & MS VirtualPC 2007 SP1 6.0.192.0
but I noticed some logspam that happens for releases/0.4.7 to releases/0.4.10 and only during 2nd stage:

bad-path (with the commas):
(../ntoskrnl/mm/ARM3/sysldr.c:3025) ZwOpenFile failed for '\SystemRoot\system32\drivers\kbdclass.sys' with status 0xc000003a
(../ntoskrnl/io/iomgr/driver.c:696) Failed to load class upper filters: C000003A
(../ntoskrnl/io/iomgr/device.c:434) No DriverUnload function on PnP driver! '\Driver\I8042PRT' will not be unloaded!
(../ntoskrnl/mm/ARM3/sysldr.c:3025) ZwOpenFile failed for '\SystemRoot\system32\drivers\mouclass.sys' with status 0xc000003a
(../ntoskrnl/io/iomgr/driver.c:696) Failed to load class upper filters: C000003A
(../ntoskrnl/io/iomgr/device.c:434) No DriverUnload function on PnP driver! '\Driver\I8042PRT' will not be unloaded!
(../ntoskrnl/mm/ARM3/sysldr.c:3025) ZwOpenFile failed for '\SystemRoot\system32\drivers\vbemp.sys' with status 0xc000003a
(../ntoskrnl/mm/ARM3/sysldr.c:3025) ZwOpenFile failed for '\SystemRoot\system32\drivers\kbdclass.sys' with status 0xc000003a
(../ntoskrnl/io/iomgr/driver.c:696) Failed to load class upper filters: C000003A
(../ntoskrnl/io/iomgr/device.c:434) No DriverUnload function on PnP driver! '\Driver\I8042PRT' will not be unloaded!
(../ntoskrnl/mm/ARM3/sysldr.c:3025) ZwOpenFile failed for '\SystemRoot\system32\drivers\mouclass.sys' with status 0xc000003a
(../ntoskrnl/io/iomgr/driver.c:696) Failed to load class upper filters: C000003A
(../ntoskrnl/io/iomgr/device.c:434) No DriverUnload function on PnP driver! '\Driver\I8042PRT' will not be unloaded!
...
(../base/services/umpnpmgr/umpnpmgr.c:3653) Removal pending: ACPI\PNP0303\2&ccb86d17&0000
(../base/services/umpnpmgr/umpnpmgr.c:3623) Safe removal: ACPI\PNP0303\2&ccb86d17&0000
(../base/services/umpnpmgr/umpnpmgr.c:3653) Removal pending: ACPI\PNP0F03\2&ccb86d17&0000
(../base/services/umpnpmgr/umpnpmgr.c:3623) Safe removal: ACPI\PNP0F03\2&ccb86d17&0000
(../base/services/umpnpmgr/umpnpmgr.c:3653) Removal pending: ACPI\PNP0303\2&ccb86d17&0000
(../base/services/umpnpmgr/umpnpmgr.c:3623) Safe removal: ACPI\PNP0303\2&ccb86d17&0000
(../base/services/umpnpmgr/umpnpmgr.c:3653) Removal pending: ACPI\PNP0F03\2&ccb86d17&0000
(../base/services/umpnpmgr/umpnpmgr.c:3623) Safe removal: ACPI\PNP0F03\2&ccb86d17&0000

good-path (without the commas):
(../ntoskrnl/mm/ARM3/sysldr.c:3025) ZwOpenFile failed for '\SystemRoot\System32\DRIVERS\i8042prt.sys' with status 0xc000003a
(../ntoskrnl/mm/ARM3/sysldr.c:3025) ZwOpenFile failed for '\SystemRoot\System32\DRIVERS\i8042prt.sys' with status 0xc000003a
(../ntoskrnl/mm/ARM3/sysldr.c:3025) ZwOpenFile failed for '\SystemRoot\system32\drivers\vbemp.sys' with status 0xc000003a
(../ntoskrnl/mm/ARM3/sysldr.c:3025) ZwOpenFile failed for '\SystemRoot\System32\DRIVERS\i8042prt.sys' with status 0xc000003a
(../ntoskrnl/mm/ARM3/sysldr.c:3025) ZwOpenFile failed for '\SystemRoot\System32\DRIVERS\i8042prt.sys' with status 0xc000003a
...
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\System32\DRIVERS\i8042prt.sys at F771B000 with 1b pages
...
and no such 'Removal pending'

So we do still miss some unknown commit from 0.4.11-dev'ing that will avoid that additional logspam with the corrected hivesys.inf.
I have not identified that commit yet, and until I will, I do play safe by restoring the wrong List-multi-string in hivesys.inf.
2023-06-05 23:45:32 +02:00
..
bootcd
bootcdregtest Fix remaining text file line endings in the tree. (#18) 2017-10-06 15:00:36 +02:00
livecd
livecdregtest
packages Add virtio drivers to reactos.dff.in 2018-05-13 22:24:41 +02:00
welcome_config
.gitattributes Add a small descriptive comment for the reason why the chosen files are specified in a .gitattributes file. 2017-10-08 15:48:07 +02:00
autorun-bootcd.inf Fix remaining text file line endings in the tree. (#18) 2017-10-06 15:00:36 +02:00
autorun-hybridcd.inf Fix remaining text file line endings in the tree. (#18) 2017-10-06 15:00:36 +02:00
autorun-livecd.inf Fix remaining text file line endings in the tree. (#18) 2017-10-06 15:00:36 +02:00
bootcd.ini Fix remaining text file line endings in the tree. (#18) 2017-10-06 15:00:36 +02:00
caroots.inf [CAROOTS] Update certificates to Mozilla Certdata 28.01.18 (#338) 2018-01-29 23:43:34 +01:00
CMakeLists.txt [0.4.9][CMAKE][BOOTDATA] Fix LiveCD does not import caroots.inf into registry CORE-17739 CORE-17735 (#3930) 2022-01-21 23:11:43 +01:00
hivebcd.inf
hivecls.inf [BOOTDATA][SHELL32] Add some recognized file extensions (.db, .efi, .nls, .ocx, .tlb, .nt), and update some reported MIME types. 2018-05-05 22:20:21 +02:00
hivedef.inf [BOOTDATA] Fix path to temp folder for the Swedish locale (#381) 2018-02-24 23:08:55 +01:00
hiveinst.inf
hivesft.inf Polish translation update (#29) 2017-10-10 12:14:38 +02:00
hivesys.inf [0.4.9][BOOTDATA] hivesys.inf Play safe with ServiceGroupOrder 2023-06-05 23:45:32 +02:00
hybridcd.ini
icon.ico
livecd.inf [0.4.9][SETUP][BOOTDATA][FONTS][INF][MEDIA][ROSTESTS] Monospaced fonts and substitution 2023-01-06 09:50:44 +01:00
livecd.ini [BOOT] Add VBox debug to livecd.ini 2017-12-20 06:56:09 +01:00
livecd_start.cmd
readme.txt [0.4.9][REACTOS] Backport "http://www.reactos" -> "https://reactos" and readme.txt 2023-03-19 12:41:27 +01:00
txtsetup.sif [BOOTDATA] Do not include caroots.inf in registry.inf. CORE-12020 2018-02-25 10:07:28 +01:00

========================
ReactOS™ Version 0.4.x
Updated October 9, 2021
========================

1. What is ReactOS?
-------------------

ReactOS™ is an Open Source effort to develop a quality operating system that is
compatible with applications and drivers written for the Microsoft® Windows™ NT
family of operating systems (NT4, 2000, XP, 2003, Vista, 7).

More information is available at: https://reactos.org


2. Relationship with the WINE project
-------------------------------------

ReactOS has always intended to work with the WINE project to share as much
programming effort as possible. This mainly concerns User Mode DLLs and
still happens to a degree today. Other areas of cooperation lie in
applications and testing suites.


3. Future compatibility
-----------------------

The ReactOS project, although currently focused on Windows Server 2003
compatibility, is always keeping an eye toward compatibility with
Windows Vista and future Windows NT releases.


4. Supporting other System Applications
---------------------------------------

The Windows NT architecture allows for subsystems, as does the ReactOS
architecture. A subsystem is an implementation of the APIs of another
operating system, allowing ReactOS to run applications from other systems.
We are already looking at subsystems for: Java, OS/2, and DOS and possibly
others in the future.


5. Is ReactOS legal?
--------------------

Yes we are.
All the code of ReactOS has been written from scratch by our developers.
We go to great lengths to ensure that the code our developers create is clean,
same applies to the variety of methods we use to understand Windows internals,
including clean room reverse engineering, using existing documentation freely
available both in books and on the web, using extensive tests (tens of millions)
which apply black box engineering methods against both public and private APIs
exposed by the operating system.


6. Tutorials
------------

Developer and User Tutorials: https://reactos.org/wiki

The tutorials contain more information on the project, compiling and testing
ReactOS - amongst other topics. Contributors to the project are always welcome.


7. Frequently Asked Questions
-----------------------------

Some of your questions may be answered in: https://reactos.org/faq
In addition, the ReactOS forum: https://reactos.org/forum
may contain complementary, yet non-official, information.


8. Authors
----------

This document was originally written by Jason Filby (jasonfilby@yahoo.com)
and is now occasionally updated by various contributors.