royce(a)svn.reactos.com wrote:
>initialize StringBuffer to NULL, as some code paths lead to it being tested without ever being set.
>
>
I forgot to give credit to WaxDragon for the find, I humbly beg your
forgiveness...
Updated and built latest version. It installs ok, but when I try to
boot, I get this ( I enabled some debug messages after the first failure ):
(ntoskrnl\ke\main.c:289)
---------------------------------------------------------------
(ntoskrnl\ke\main.c:290) ReactOS 0.3-SVN (Build 20050809-r17251)
Used memory 65536Kb
(ntoskrnl\mm\mminit.c:375) Kernel Stack Limits. InitTop = 0x800f7000,
Init = 0x800f4000
(ntoskrnl\mm\mm.c:283) No current process
(ntoskrnl\io\driver.c:442) IopLoadServiceModule(Pci, 0x800f6a80)
(ntoskrnl\io\driver.c:518) Initializing boot module
(ntoskrnl\io\driver.c:562) Module loading (Status 0)
Peripheral Component Interconnect Bus Driver
(ntoskrnl\io\driver.c:442) IopLoadServiceModule(PCNet, 0x800f6850)
(ntoskrnl\io\driver.c:541) Loading module
(ntoskrnl\ldr\loader.c:252) Could not open module file:
\SystemRoot\system32\drivers\pcnet.sys
(ntoskrnl\io\driver.c:559) Module loading failed (Status c0000001)
(ntoskrnl\io\driver.c:562) Module loading (Status c0000001)
(ntoskrnl\io\pnpmgr.c:1750) Initialization of service PCNet failed
(Status c0000001)
(ntoskrnl\io\driver.c:442) IopLoadServiceModule(usbuhci, 0x800f6850)
(ntoskrnl\io\driver.c:541) Loading module
(ntoskrnl\ldr\loader.c:252) Could not open module file:
\SystemRoot\System32\DRIVERS\usbuhci.sys
(ntoskrnl\io\driver.c:559) Module loading failed (Status c0000001)
(ntoskrnl\io\driver.c:562) Module loading (Status c0000001)
(ntoskrnl\io\pnpmgr.c:1750) Initialization of service usbuhci failed
(Status c0000001)
(ntoskrnl\io\driver.c:442) IopLoadServiceModule(PCNet, 0x800f6a60)
(ntoskrnl\io\driver.c:541) Loading module
(ntoskrnl\ldr\loader.c:252) Could not open module file:
\SystemRoot\system32\drivers\pcnet.sys
(ntoskrnl\io\driver.c:559) Module loading failed (Status c0000001)
(ntoskrnl\io\driver.c:562) Module loading (Status c0000001)
(ntoskrnl\io\pnpmgr.c:1750) Initialization of service PCNet failed
(Status c0000001)
(ntoskrnl\io\driver.c:442) IopLoadServiceModule(usbuhci, 0x800f6a60)
(ntoskrnl\io\driver.c:541) Loading module
(ntoskrnl\ldr\loader.c:252) Could not open module file:
\SystemRoot\System32\DRIVERS\usbuhci.sys
(ntoskrnl\io\driver.c:559) Module loading failed (Status c0000001)
(ntoskrnl\io\driver.c:562) Module loading (Status c0000001)
(ntoskrnl\io\pnpmgr.c:1750) Initialization of service usbuhci failed
(Status c0000001)
(ntoskrnl\io\driver.c:442) IopLoadServiceModule(Ne2000, 0x800f6a80)
(ntoskrnl\io\driver.c:541) Loading module
(ntoskrnl\ldr\loader.c:252) Could not open module file:
\SystemRoot\system32\drivers\ne2000.sys
(ntoskrnl\io\driver.c:559) Module loading failed (Status c0000001)
(ntoskrnl\io\driver.c:562) Module loading (Status c0000001)
(ntoskrnl\io\pnpmgr.c:1750) Initialization of service Ne2000 failed
(Status c0000001)
Advanced Configuration and Power Interface Bus Driver
ACPI: System firmware supports:
+------------------------------------------------------------
| Sx states: +S0 -S1 -S2 -S3 -S4 +S5
+------------------------------------------------------------
Power Button: found
Sleep Button: found
(ntoskrnl\io\driver.c:442) IopLoadServiceModule(serial, 0x800f6980)
(ntoskrnl\io\driver.c:465) RtlQueryRegistryValues() failed (Status c0000034)
(ntoskrnl\io\pnpmgr.c:1750) Initialization of service serial failed
(Status c0000034)
(ntoskrnl\io\driver.c:442) IopLoadServiceModule(serial, 0x800f6980)
(ntoskrnl\io\driver.c:465) RtlQueryRegistryValues() failed (Status c0000034)
(ntoskrnl\io\pnpmgr.c:1750) Initialization of service serial failed
(Status c0000034)
(ntoskrnl\io\driver.c:442) IopLoadServiceModule(serial, 0x800f6bc0)
(ntoskrnl\io\driver.c:465) RtlQueryRegistryValues() failed (Status c0000034)
(ntoskrnl\io\pnpmgr.c:1750) Initialization of service serial failed
(Status c0000034)
(ntoskrnl\io\driver.c:442) IopLoadServiceModule(serial, 0x800f6bc0)
(ntoskrnl\io\driver.c:465) RtlQueryRegistryValues() failed (Status c0000034)
(ntoskrnl\io\pnpmgr.c:1750) Initialization of service serial failed
(Status c0000034)
(ntoskrnl\io\driver.c:442) IopLoadServiceModule(PCNet, 0x800f6bc0)
(ntoskrnl\io\driver.c:541) Loading module
(ntoskrnl\io\driver.c:562) Module loading (Status 0)
(ntoskrnl\io\driver.c:442) IopLoadServiceModule(usbuhci, 0x800f6bc0)
(ntoskrnl\io\driver.c:541) Loading module
(ntoskrnl\ldr\loader.c:252) Could not open module file:
\SystemRoot\System32\DRIVERS\usbuhci.sys
(ntoskrnl\io\driver.c:559) Module loading failed (Status c0000034)
(ntoskrnl\io\driver.c:562) Module loading (Status c0000034)
(ntoskrnl\io\pnpmgr.c:1750) Initialization of service usbuhci failed
(Status c0000034)
(ntoskrnl\io\driver.c:442) IopLoadServiceModule(Ne2000, 0x800f6be0)
(ntoskrnl\io\driver.c:541) Loading module
(ntoskrnl\io\driver.c:562) Module loading (Status 0)
(ne2000/8390.c:86)(NICCheck) Adapter NOT found!
(ndis/miniport.c:1425)(NdisIPnPStartDevice) MiniportInitialize() failed
for an adapter.
(drivers\input\i8042prt\registry.c:215) Can't read registry: c0000034
(drivers\input\i8042prt\registry.c:226) Manually set defaults
(ntoskrnl\ldr\loader.c:252) Could not open module file:
\SystemRoot\system32\drivers\sndblst.sys
(ntoskrnl\ldr\loader.c:252) Could not open module file:
\SystemRoot\system32\drivers\mpu401.sys
(ntoskrnl\ldr\loader.c:252) Could not open module file:
\SystemRoot\system32\drivers\xboxvmp.sys
NtSetEaFile at ntoskrnl\io\file.c:2873 is unimplemented, have a nice day
greatlrd(a)svn.reactos.com wrote:
>fixing bug 690 by Brandon Turner. note ms only allown start "notepad" or "note"pad not notep"ad or notepad" but we do that, for we think it is a bug in ms cmd that only allowing " at start of a file name to start the apps.
>
>
>Updated files:
>trunk/reactos/subsys/system/cmd/cmd.c
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
>
>
This change is broken, because the input strings may be longer than
MAX_PATH. This is always true for compilung ros on ros.
- Hartmut
navaraf(a)svn.reactos.com wrote:
>Fix mutex unlocking in NpfsWaiterThread and add ASSERT.
>
>
>Updated files:
>trunk/reactos/drivers/fs/np/rw.c
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
>
>
Something is wrong with this change or r17157. Compiling ros on ros
reports hundreds of errors if pipes are enabled. Reverting npfs to
r17153 does fix this problem.
- Hartmut
hbirr(a)svn.reactos.com wrote:
>- DPRINT("%wZ\n", ObjectAttributes->ObjectName);
>
>
>
>
>
>+ DPRINT1("%wZ\n", ObjectAttributes->ObjectName);
>+
>
>
Do we really need to be verbose? ;-)
- Filip
ion(a)svn.reactos.com wrote:
>- Last patch was incomplete, apologies. SVN @ 5AM = bad idea.
>- Do not report that ROS is running on 0 active processors, that's a bad idea.
>- Actually check the affinity mask set by NtSetInformationThread
>- Fix the check in KeSetAffinityThread
>- Give a valid affinity to the system thread (corresponding to the active cpu affinity set).
>
>This removes all bugchecks from the kernel32 thread winetest.
>
>Modified: trunk/reactos/ntoskrnl/include/internal/ke.h
>Modified: trunk/reactos/ntoskrnl/ke/kthread.c
>Modified: trunk/reactos/ntoskrnl/ke/main.c
>Modified: trunk/reactos/ntoskrnl/ps/psmgr.c
>Modified: trunk/reactos/ntoskrnl/ps/query.c
>
>
> ------------------------------------------------------------------------
>
> *Modified: trunk/reactos/ntoskrnl/ps/psmgr.c*
>
>--- trunk/reactos/ntoskrnl/ps/psmgr.c 2005-08-09 08:02:05 UTC (rev 17234)
>+++ trunk/reactos/ntoskrnl/ps/psmgr.c 2005-08-09 08:50:57 UTC (rev 17235)
>@@ -213,7 +213,7 @@
>
>
> /* System threads may run on any processor. */
> RtlZeroMemory(PsInitialSystemProcess, sizeof(EPROCESS));
>
>
>- PsInitialSystemProcess->Pcb.Affinity = 0xFFFFFFFF;
>
>
>+ PsInitialSystemProcess->Pcb.Affinity = KeActiveProcessors;
>
>
> PsInitialSystemProcess->Pcb.IopmOffset = 0xffff;
> PsInitialSystemProcess->Pcb.BasePriority = PROCESS_PRIO_NORMAL;
> PsInitialSystemProcess->Pcb.QuantumReset = 6;
>
>
> ------------------------------------------------------------------------
*
*This is change is possible incorrect. PsInitProcessManagment is called
after the boot processor is started and before the application
processors are started (on a smp machine). All system threads will only
run on the boot processor.
- Hartmut