Ros-dev

ros-dev@reactos.org

1 participants
5793 discussions

Via Vt6102 Net card
by James Tabor 14 Jun '06

14 Jun '06

Hi all! This is the hivesys.inf PCNet section. I copied fetnd5a.sys to pcnet.sys. I can query network properties w/o a crash! All I get is IPHLPAPI.dll need more work and GetAdapterInfo did not return the expected data. Bus 0, device 18, function 0, Ven 1106/Dev 3065/class 0200. Start->Settings->Settings Menu->Network Properties Select VT6102->Properties, get the VIA PCNet Status Menu, select Properties, get the VIA PCNet Pro~ Menu, select Internet Protocol (TCP/IP), select Properties, get the Error menu. Wow! Did not crash! Need to check if I'm on the right track here! Thanks, James ; ReactOS PCNet NIC driver ; To use the AMD supplied driver change the driver name to pcntn5m.sys ; HKLM,"SYSTEM\CurrentControlSet\Services\PCNet","ErrorControl",0x00010001,0x00000000 HKLM,"SYSTEM\CurrentControlSet\Services\PCNet","Group",0x00000000,"NDIS" HKLM,"SYSTEM\CurrentControlSet\Services\PCNet","ImagePath",0x00020000,"system32\drivers\pcnet.sys" HKLM,"SYSTEM\CurrentControlSet\Services\PCNet","Start",0x00010001,0x00000003 HKLM,"SYSTEM\CurrentControlSet\Services\PCNet","Type",0x00010001,0x00000001 HKLM,"SYSTEM\CurrentControlSet\Services\PCNet\Enum","0",0x00000000,"PCI\VEN_1106&DEV_3065\0000" HKLM,"SYSTEM\CurrentControlSet\Services\PCNet\Enum","Count",0x00010001,0x00000001 HKLM,"SYSTEM\CurrentControlSet\Services\PCNet\Enum","NextInstance",0x00010001,0x00000001 HKLM,"SYSTEM\CurrentControlSet\Enum\PCI\VEN_1106&DEV_3065&SUBSYS_01021106&REV_10\0000","Service",0x00000000,"PCNet" HKLM,"SYSTEM\CurrentControlSet\Enum\PCI\VEN_1106&DEV_3065&SUBSYS_01021106&REV_10\0000","Class",0x00000000,"Net" HKLM,"SYSTEM\CurrentControlSet\Enum\PCI\VEN_1106&DEV_3065&SUBSYS_01021106&REV_10\0000","ClassGUID",0x00000000,"{4D36E972-E325-11CE-BFC1-08002BE10318}" HKLM,"SYSTEM\CurrentControlSet\Enum\PCI\VEN_1106&DEV_3065&SUBSYS_01021106&REV_10\0000","Driver",0x00000000,"{4D36E972-E325-11CE-BFC1-08002BE10318}\0000" ; Configuration Entries for the PCNet Adapter HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","Characteristics",0x00010001,0x00000000 HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","DriverDesc",0x00000000,"VT6102" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","ProviderName",0x00000000,"VIA Tech" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","NetCfgInstanceId",0x00000000,"{RANDOMCFGGUIDFOR_PCNET1}" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000\Linkage","Export",0x00000000,"\Device\PCNet1" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000\Linkage","RootDevice",0x00000000,"PCNet1" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000\Linkage","UpperBind",0x00000000,"Tcpip" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","BUS_TO_SCAN",0x00000000,"ALL" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","BUSTIMER",0x00000000,"0" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","BUSTYPE",0x00000000,"5" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","EXTPHY",0x00000000,"0" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","FDUP",0x00000000,"0" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","LED0",0x00000000,"10000" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","LED1",0x00000000,"10000" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","LED2",0x00000000,"10000" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","LED3",0x00000000,"10000" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","MPMODE",0x00000000,"0" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","TP",0x00000000,"1" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","AdapterCFID",0x00000000,"811929862" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","AdapterType",0x00000000,"5" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","SlotNumber",0x00000000,"8" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","BusNumber",0x00000000,"0" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","FunctionNumber",0x00000000,"0" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","EarlyReceive",0x00000000,"0" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","EarlyTransmit",0x00000000,"0" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","BurstLength",0x00000000,"1" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","ReceiveBurstIndicate",0x00000000,"64" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","ReceiveBuffers",0x00000000,"64" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","TransmitBuffers",0x00000000,"32" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","ReceiveThreshold",0x00000000,"0" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","TransmitThreshold",0x00000000,"0" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","MapRegisters",0x00000000,"32" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","ConnectionType",0x00000000,"0" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","ValidatePacketLen",0x00000000,"1" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000","IPXSPXAutoFrame",0x00000000,"0" HKLM,"SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\{RANDOMCFGGUIDFOR_PCNET1}",,0x00000000,"Network Adapters" HKLM,"SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\{RANDOMCFGGUIDFOR_PCNET1}\Connection","Name",0x00000000,"VIA PCNet" HKLM,"SYSTEM\CurrentControlSet\Services\PCNet1\Parameters\Tcpip","DefaultGateway",0x00010000,"10.65.145.1" HKLM,"SYSTEM\CurrentControlSet\Services\PCNet1\Parameters\Tcpip","IPAddress",0x00010000,"10.65.145.79" HKLM,"SYSTEM\CurrentControlSet\Services\PCNet1\Parameters\Tcpip","SubnetMask",0x00010000,"255.255.255.0"

2 3

Hang During Installation
by James Tabor 14 Jun '06

14 Jun '06

Hi all! New full system copied to the RosBox via net using Linux. For me SSDD. (ntoskrnl/ldr/loader.c:334) Driver Load Success: \SystemRoot\System32\kbdus.dll (base/system/winlogon/winlogon.c:173) WL: Failed to create lsass notification event (base/system/winlogon/winlogon.c:563) WL: Failed to start LSASS (0xA1) (base/system/winlogon/winlogon.c:764) WL-Status: ReactOS is starting up... (dll/win32/iphlpapi/ifenum_reactos.c:99) openTcpFile for <\Device\Tcp> failed: 0xc0000034 (dll/win32/iphlpapi/ifenum_reactos.c:99) openTcpFile for <\Device\Tcp> failed: 0xc0000034 (dll/win32/iphlpapi/ifenum_reactos.c:99) openTcpFile for <\Device\Tcp> failed: 0xc0000034 Hangs! after 10 min forced reboot (ntoskrnl/ldr/loader.c:334) Driver Load Success: \SystemRoot\System32\kbdus.dll (base/system/winlogon/winlogon.c:173) WL: Failed to create lsass notification event (base/system/winlogon/winlogon.c:563) WL: Failed to start LSASS (0xA1) (base/system/winlogon/winlogon.c:764) WL-Status: ReactOS is starting up... (dll/win32/iphlpapi/ifenum_reactos.c:99) openTcpFile for <\Device\Tcp> failed: 0xc0000034 (dll/win32/iphlpapi/ifenum_reactos.c:99) openTcpFile for <\Device\Tcp> failed: 0xc0000034 (dll/win32/iphlpapi/ifenum_reactos.c:99) openTcpFile for <\Device\Tcp> failed: 0xc0000034 (ntoskrnl/ldr/loader.c:334) Driver Load Success: \SystemRoot\System32\framebuf.DLL Second boot passed, first boot wiz worked Wiz reboot (ntoskrnl/ldr/loader.c:334) Driver Load Success: \SystemRoot\System32\kbdus.dll (base/system/winlogon/winlogon.c:173) WL: Failed to create lsass notification event (base/system/winlogon/winlogon.c:563) WL: Failed to start LSASS (0xA1) (base/system/winlogon/winlogon.c:764) WL-Status: ReactOS is starting up... (dll/win32/iphlpapi/ifenum_reactos.c:99) openTcpFile for <\Device\Tcp> failed: 0xc0000034 (dll/win32/iphlpapi/ifenum_reactos.c:99) openTcpFile for <\Device\Tcp> failed: 0xc0000034 (dll/win32/iphlpapi/ifenum_reactos.c:99) openTcpFile for <\Device\Tcp> failed: 0xc0000034 (dll/ntdll/ldr/utils.c:2076) Relocating (10000000 -> 00411000) C:\ReactOS\system32\dhcpcsvc.dll Hangs after 5 min forced reboot Hang again,,, forced reboot to Linux, sync than reboot Linux... (ntoskrnl/ldr/loader.c:334) Driver Load Success: \SystemRoot\System32\kbdus.dll (base/system/winlogon/winlogon.c:173) WL: Failed to create lsass notification event (base/system/winlogon/winlogon.c:563) WL: Failed to start LSASS (0xA1) (base/system/winlogon/winlogon.c:764) WL-Status: ReactOS is starting up... (dll/win32/iphlpapi/ifenum_reactos.c:99) openTcpFile for <\Device\Tcp> failed: 0xc0000034 (dll/win32/iphlpapi/ifenum_reactos.c:99) openTcpFile for <\Device\Tcp> failed: 0xc0000034 (dll/win32/iphlpapi/ifenum_reactos.c:99) openTcpFile for <\Device\Tcp> failed: 0xc0000034 (dll/ntdll/ldr/utils.c:2076) Relocating (10000000 -> 00411000) C:\ReactOS\system32\dhcpcsvc.dll (ntoskrnl/ldr/loader.c:334) Driver Load Success: \SystemRoot\System32\framebuf.DLL (dll/win32/shell32/shellpath.c:1688) Failed to create directory 'L".\\Local Settings\\Temporary Internet Files"'. (dll/win32/shell32/shellpath.c:1688) Failed to create directory 'L".\\Local Settings\\History"'. (dll/win32/shell32/shellpath.c:1688) Failed to create directory 'L".\\Cookies"'. Now I have the Gui and passed all install Wiz's Reboot so I can have networking. Yeah! Past! I have networking! I opened a cmd console to look at ipconfig, worked! I hit the "X" at the upper right hand corner. Assertion 'HandleTable' failed at ntoskrnl/ex/handle.c line 791 Entered debugger on embedded INT3 at 0x0008:0x800762d0. kdb:> bt Eip: <ntoskrnl.exe:762d1 (lib/rtl/i386/debug_asm.S:23 (DbgBreakPoint))> Frames: <ntoskrnl.exe:163b9 (ntoskrnl/ex/handle.c:791 (ExCreateHandle))> <ntoskrnl.exe:50d6a (ntoskrnl/ob/obhandle.c:595 (ObpCreateUnnamedHandle))> <ntoskrnl.exe:51aa3 (ntoskrnl/ob/obhandle.c:1713 (ObInsertObject))> <ntoskrnl.exe:14504 (ntoskrnl/ex/event.c:156 (NtCreateEvent))> <ntoskrnl.exe:665f7 (ntoskrnl/ke/i386/trap.s:306 (KiFastCallEntry))> <ntdll.dll:13eb3 (lib/rtl/critical.c:54 (RtlpCreateCriticalSectionSem))> <ntdll.dll:13f5a (lib/rtl/critical.c:113 (RtlpWaitForCriticalSection))> <ntdll.dll:1413d (lib/rtl/critical.c:459 (RtlEnterCriticalSection))> <KERNEL32.dll:e226 (dll/win32/kernel32/misc/console.c:116 (ConsoleControlDispatcher))> <KERNEL32.dll:1dfc3 (dll/win32/kernel32/thread/thread.c:55 (BaseThreadStartup))><00000000> kdb:> cont Entered debugger on last-chance exception (Exception Code: 0xc0000005) (Page Fault) Memory at 0x0000001A could not be read: Page not present. kdb:> cont KeBugCheckWithTf at ntoskrnl/ke/i386/exp.c:1241 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe Technical information: *** STOP: 0x0000001E (0xC0000005,0x800191ED,0x00000000,0x0000001A) *** ntoskrnl.exe - Address 0x800191ED base at 0x80000000, DateStamp 0x0 Page Fault Exception: 14(0) Processor: 0 CS:EIP 8:800191ed <ntoskrnl.exe:191ed (ntoskrnl/ex/resource.c:778 (ExAcquireResourceExclusiveLite))> cr2 1a cr3 3a35b000 Proc: 81fa3620 Pid: 164 <ipconfig.EXE> Thrd: 81fc3ce0 Tid: 170 DS 23 ES 23 FS 30 GS 0 EAX: 00000001 EBX: 0000000c ECX: 00000037 EDX: 81fc3ce0 EBP: a03ddb34 ESI: 00000001 ESP: a03ddab4 EDI: 81fc3f78 EFLAGS: 00010206 kESP a03ddab4 kernel stack base a03db000 Frames: <ntoskrnl.exe:16247 (ntoskrnl/ex/handle.c:472 (ExCreateHandle))> <ntoskrnl.exe:50d6a (ntoskrnl/ob/obhandle.c:595 (ObpCreateUnnamedHandle))> <ntoskrnl.exe:51aa3 (ntoskrnl/ob/obhandle.c:1713 (ObInsertObject))> <ntoskrnl.exe:14504 (ntoskrnl/ex/event.c:156 (NtCreateEvent))> <ntoskrnl.exe:665f7 (ntoskrnl/ke/i386/trap.s:306 (KiFastCallEntry))> <ntdll.dll:13eb3 (lib/rtl/critical.c:54 (RtlpCreateCriticalSectionSem))> forced reboot (ntoskrnl/ldr/loader.c:334) Driver Load Success: \SystemRoot\System32\kbdus.dll (base/system/winlogon/winlogon.c:173) WL: Failed to create lsass notification event (base/system/winlogon/winlogon.c:563) WL: Failed to start LSASS (0xA1) (base/system/winlogon/winlogon.c:764) WL-Status: ReactOS is starting up... NDIS completed the same send packet twice (Adapter 81355f38 Packet 81354058)!! (dll/ntdll/ldr/utils.c:2076) Relocating (10000000 -> 00411000) C:\ReactOS\system32\dhcpcsvc.dll (ntoskrnl/ke/queue.c:420) Unwaiting Thread: 5 Hang again! 20 min no bug check. same thing hang 4 times, forced boot to Linux. Well it booted okay and run mozilla, I get the reactos web page and it asks me if I want it to be my default browser, I select *Yes*, than~~~ (dll/win32/gdi32/objects/font.c:647) GetGlyphOutlineW uChar 78 (./subsystems/win32/win32k/objects/text.c:2326) 03010120, 120, 00000000, 0053D9E 8, 00000000, 00000000, 613407F0 (./subsystems/win32/win32k/objects/text.c:2433) Advance = 8, lsb = 0, bbx = 8 (./subsystems/win32/win32k/objects/text.c:2483) MAT2 Matrix Trans! (./subsystems/win32/win32k/objects/text.c:2515) Vec 0,448 (./subsystems/win32/win32k/objects/text.c:2515) Vec 0,0 (./subsystems/win32/win32k/objects/text.c:2515) Vec 512,448 (./subsystems/win32/win32k/objects/text.c:2515) Vec 512,0 (./subsystems/win32/win32k/objects/text.c:2536) transformed box: (0,448 - 512,0) (./subsystems/win32/win32k/objects/text.c:2548) CX 8 CY 0 BBX 8 BBY 7 GOX 0 GOY 7 (./subsystems/win32/win32k/objects/text.c:2563) Copied GLYPHMETRICS to User! (./subsystems/win32/win32k/objects/text.c:2568) GGO_METRICS Exit! (ntoskrnl/ke/queue.c:420) Unwaiting Thread: 5 (ntoskrnl/ke/queue.c:420) Unwaiting Thread: 5 (ntoskrnl/ke/queue.c:420) Unwaiting Thread: 5 (ntoskrnl/ke/queue.c:420) Unwaiting Thread: 5 (ntoskrnl/ke/queue.c:420) Unwaiting Thread: 5 Assertion '(Thread == NULL) || (FastMutex->Owner != Thread)' failed at ntoskrnl/ex/fmutex.c line 42 Entered debugger on embedded INT3 at 0x0008:0x800762d0. kdb:> bt Eip: <ntoskrnl.exe:762d1 (lib/rtl/i386/debug_asm.S:23 (DbgBreakPoint))> Frames: <ntoskrnl.exe:153a0 (ntoskrnl/ex/fmutex.c:45 (ExEnterCriticalRegionAndAcquireFastMutexUnsafe))> <ntoskrnl.exe:3d416 (ntoskrnl/mm/aspace.c:48 (MmLockAddressSpace))> <ntoskrnl.exe:4108b (ntoskrnl/mm/mm.c:312 (MmNotPresentFault))> <ntoskrnl.exe:75738 (ntoskrnl/mm/i386/pfault.c:75 (KiPageFaultHandler))> <ntoskrnl.exe:671e3 (ntoskrnl/ke/i386/trap.s:943 (KiTrap8))> <ntoskrnl.exe:3f797 (ntoskrnl/mm/marea.c:90 (MmIterateNextNode))> <ntoskrnl.exe:3fd31 (ntoskrnl/mm/marea.c:961 (MmCreateMemoryArea))> <ntoskrnl.exe:8a8d (ntoskrnl/cc/view.c:694 (CcRosCreateCacheSegment))> <ntoskrnl.exe:8c57 (ntoskrnl/cc/view.c:772 (CcRosGetCacheSegmentChain))> <ntoskrnl.exe:6960 (ntoskrnl/cc/copy.c:79 (ReadCacheSegmentChain))> <ntoskrnl.exe:7024 (ntoskrnl/cc/copy.c:385 (CcCopyRead))> <vfatfs.sys:a7c0 (drivers/filesystems/vfat/rw.c:688 (VfatRead))> <vfatfs.sys:9769 (drivers/filesystems/vfat/misc.c:109 (VfatDispatchRequest))> <vfatfs.sys:9ade (drivers/filesystems/vfat/misc.c:167 (VfatBuildRequest))> <ntoskrnl.exe:2aef0 (ntoskrnl/io/irp.c:1076 (IofCallDriver))> <ntoskrnl.exe:35d06 (ntoskrnl/io/file.c:3080 (NtReadFile))> <ntoskrnl.exe:665f7 (ntoskrnl/ke/i386/trap.s:306 (KiFastCallEntry))> <ntdll.dll:3559 (dll/ntdll/ldr/utils.c:661 (LdrpLoadModule))> <ntdll.dll:38ba (dll/ntdll/ldr/utils.c:751 (LdrLoadDll))> <KERNEL32.dll:1429f (dll/win32/kernel32/misc/ldr.c:206 (LoadLibraryExW))> <KERNEL32.dll:14333 (dll/win32/kernel32/misc/ldr.c:121 (LoadLibraryA))> --- Press q to abort, any other key to continue --- <nspr4.dll:5e6a> kdb:> cont (KERNEL32:dll/win32/kernel32/mem/global.c:417) Memory Load: 10% (KERNEL32:dll/win32/kernel32/mem/global.c:417) Memory Load: 10% (KERNEL32:dll/win32/kernel32/mem/global.c:417) Memory Load: 10% (KERNEL32:dll/win32/kernel32/mem/global.c:417) Memory Load: 10% (KERNEL32:dll/win32/kernel32/mem/global.c:417) Memory Load: 10% (KERNEL32:dll/win32/kernel32/mem/global.c:417) Memory Load: 10% (KERNEL32:dll/win32/kernel32/mem/global.c:417) Memory Load: 10% (KERNEL32:dll/win32/kernel32/mem/global.c:417) Memory Load: 10% (KERNEL32:dll/win32/kernel32/mem/global.c:417) Memory Load: 10% (KERNEL32:dll/win32/kernel32/mem/global.c:417) Memory Load: 10% Funny I can still ping the RosBox from my Linux desktop. Also notice the memory load. The system is locked up but mozilla is still running! Oh Well! Here is the one time I did get a bug check with the hang. (ntoskrnl/ldr/loader.c:334) Driver Load Success: \??\C:\ReactOS\system32\win32k.sys (ntoskrnl/ldr/loader.c:334) Driver Load Success: \SystemRoot\System32\kbdus.dll (base/system/winlogon/winlogon.c:173) WL: Failed to create lsass notification event (base/system/winlogon/winlogon.c:563) WL: Failed to start LSASS (0xA1) (base/system/winlogon/winlogon.c:764) WL-Status: ReactOS is starting up... NDIS completed the same send packet twice (Adapter 81357f38 Packet 81356010)!! (dll/ntdll/ldr/utils.c:2076) Relocating (10000000 -> 00411000) C:\ReactOS\system32\dhcpcsvc.dll (ntoskrnl/ke/queue.c:420) Unwaiting Thread: 5 right here it would hang! For over 3 min! (ntoskrnl/mm/mm.c:275) Page fault at high IRQL was 2, address c00000b2 Entered debugger on last-chance exception (Exception Code: 0xc0000005) (Page Fault) Memory at 0xC00000B2 could not be read: Page not present. kdb:> bt Eip: <ntoskrnl.exe:544e (ntoskrnl/ke/queue.c:391 (KiWakeQueue))> Frames: <ntoskrnl.exe:679e (ntoskrnl/ke/wait.c:168 (KeDelayExecutionThread))> <usbport.sys:4153 (drivers/usb/usbport/hub.c:1255 (hub_thread))> <ntoskrnl.exe:5b78a (ntoskrnl/ps/thread.c:94 (PspSystemThreadStartup))> <ntoskrnl.exe:62fa5 (ntoskrnl/ke/i386/ctxswitch.S:82 (KiThreadStartup))> kdb:>

1 0

Search author for ReactOS Weekly Newsletter
by Klemens Friedl 14 Jun '06

14 Jun '06

We search an author for our "ReactOS Weekly Newsletter". History: Jason Filby had established the ReactOS Weekly Newsletter (called "ReactOS Weekly") in 1999 as a useful weekly news summary located on www.reactos.com. In 2000 the newsletter had been discontinued. With the website redesign in summer 2005, the newsletter came back with Stuart "TwoTailedFox" Robbins as author. Requirements: Here are requirements for an author: 1. Have enough time once a week to write the newsletter text (e.g. every sunday) 2. Be good in english language 3. Understand our technlogy (svn, reactos, windows nt, win32, kernel, drivers, apps, etc.) 4. Be in frequent contact with the ReactOS developer, and come in our IRC channels too (because mailing list traffic may be sometimes slow) 5. HTML knowledge is not required but an advantage Goal: The "ReactOS Weekly Newsletter" should be weekly (as the name implies) and sum up the ongoing mailing list discussions as well as irc conversations. Additionally it should contain ReactOS news, like new releases. >From time to time interviews, reviews (of apps compatibility and reactos functions and releases) and maybe audio-podcasts, etc. would be great too. The layout of the newsletter issue page can be the same as the latest one (e.g. http://www.reactos.org/xhtml/en/newsletter_11.html), similar as WineHQ's one, or different. Previous newsletters - links: 10/2005 - 02/2005: http://www.reactos.org/?page=newsletters 1999 - 2000: http://web.archive.org/web/20000522174140/reactos.com/public/weekly.html WineHQ'S newsletters: http://www.winehq.com/?issue=back Mailing List Information: http://www.reactos.org/?page=community_mailinglists IRC Channel Information: http://www.reactos.org/?page=community_irc So... if this sounds like something you would like to do, please reply to this mailing list email explaining why you you think you would be a good newsletter author. Klemens Friedl

7 8

Re: [ros-dev] SUSPICIOUS: SESSION_5 BSOD
by Murphy, Ged (Bolton) 14 Jun '06

14 Jun '06

Alex Ionescu wrote: > In defense to Hervé, you actually need to clean *TWICE*. That's right, > you must write: > make intrlck_clean && make intrlck_clean & make ntdll_clean & make > ntdll_install. What does running 'make intrlck_clean' do the second time which it doesn't do the first time round? ************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster(a)exideuk.co.uk <mailto:postmaster@exideuk.co.uk> and then delete this message. Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com

1 0

Disk Controller Install Failure
by James Tabor 14 Jun '06

14 Jun '06

Hi all! When the install popup for the disk controller is displayed. I can install from and select everything but NEXT! Select *Next* this will happen, (tested this 4 times now, same thing) (dll/win32/newdev/newdev.c:745) Installing Other ACPI device (ACPI\PNP0C04\1&7313ac9&0000) (dll/win32/newdev/newdev.c:466) Include removable devices: no (dll/win32/newdev/newdev.c:467) Include custom path : no (dll/win32/newdev/newdev.c:534) Installing driver (Generic system devices): Math coprocessor (dll/win32/newdev/newdev.c:745) Installing Disk controller (ACPI\PNP0700\1&7313ac9&0000) (dll/win32/newdev/newdev.c:466) Include removable devices: no (dll/win32/newdev/newdev.c:467) Include custom path : no (dll/win32/shell32/classes.c:381) HCR_GetFolderAttributes should be called for simple PIDL's only! (dll/win32/shell32/shellpath.c:1688) Failed to create directory 'L".\\Desktop"'. (dll/win32/newdev/newdev.c:466) Include removable devices: yes (dll/win32/newdev/newdev.c:467) Include custom path : no KeBugCheckWithTf at ntoskrnl/ke/i386/exp.c:1241 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe Technical information: *** STOP: 0x0000001E (0xC0000005,0x80033CF6,0x00000000,0x00000030) *** ntoskrnl.exe - Address 0x80033CF6 base at 0x80000000, DateStamp 0x0 Page Fault Exception: 14(0) Processor: 0 CS:EIP 8:80033cf6 <ntoskrnl.exe:33cf6 (ntoskrnl/io/file.c:970 (IoCreateFile))> cr2 30 cr3 3be68000 Proc: 8178f328 Pid: d8 <umpnpmgr.exe> Thrd: 817a4558 Tid: e8 DS 23 ES 23 FS 30 GS 0 EAX: 00000000 EBX: 9fa43c34 ECX: 000023be EDX: 81f5d6e4 EBP: 9fa43cf0 ESI: 00000000 ESP: 9fa43b50 EDI: 00000000 EFLAGS: 00010296 kESP 9fa43b50 kernel stack base 9fa3e000 Frames: <ntoskrnl.exe:3459a (ntoskrnl/io/file.c:1527 (NtCreateFile))> <ntoskrnl.exe:66657 (ntoskrnl/ke/i386/trap.s:306 (KiFastCallEntry))> <KERNEL32.dll:9c6f (dll/win32/kernel32/file/volume.c:57 (InternalOpenDirW))> I think my hardware is not ReactOS compatible. Thanks, James

1 1

SESSION_5 BSOD
by Alex Ionescu 14 Jun '06

14 Jun '06

Hi, Annoyed by the ever-growing blame on my patches as well as the continuing lack of attention regarding the SESSION_5 BSOD, I've taken the liberty to momentarily put on hold my current paid work and take a look at the issue (which thankfully only took 30 minutes). As I suspected, it has absolutely nothing to do with any Ob stuff and is the result of ntdll being messed up after the recent changes to lib\intrlck. Revert them, clean interlck/ntdll, rebuild, and voila, you're back to a working ROS. In defense to Hervé, you actually need to clean *TWICE*. That's right, you must write: make intrlck_clean && make intrlck_clean & make ntdll_clean & make ntdll_install. It is *NOT* enough to merely write ntdll_clean, either. I'm going to assume that Hervé only cleaned interlck once (as anyone would normally do) and kept using the "correct" library. As soon as he (and others) built a new copy of the tree (probably around one of my patches), the interlck lib now got cleaned twice and the broken one started coming into use. Score one for my complaints against rbuild. If I could give some advice, next time, spend less time assigning blame on me, and actually try to find the bug (yes, this sounds arrogant, but it DOES get annoying to be the poster boy for boot BSODs. The last one I caused was over 12 months ago). Best regards, Alex Ionescu

2 2

ROS A memory hog? Rubbish!
by Alex Ionescu 13 Jun '06

13 Jun '06

Hi, With ROS_LEAN_AND_MEAN and DBG = 1, with all drivers and the bells and whistles, a boot to NCLI with 8MB gave me a working system with still 2MB to spare (perhaps for a native FTP server or other application). If I remove the network layer, I can boot with 6MB, and I still have 1MB free. I'm trying with DBG = 0 now. Maybe I can boot with 4MB :D. Best regards, Alex Ionescu

4 4

Re: [ros-dev] Wine libs vendor import
by Murphy, Ged (Bolton) 13 Jun '06

13 Jun '06

> > I spoke with Gé and he explained me the vendor import process in > > short. As soon as I find some time I will try out it myself and update > > the Wine libs in our SVN tree, if you don't mind. I have just updated comctl32 to 0.9.15, and will continue to keep this lib updated at every Wine release. Although r22329 was not mailed out via svn-diff (any ideas Aleksey??) I may also look after one or two other libs along with this. ************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster(a)exideuk.co.uk <mailto:postmaster@exideuk.co.uk> and then delete this message. Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com

1 0

Wine libs vendor import
by Aleksey Bragin 13 Jun '06

13 Jun '06

I'm answering to ros-dev so all developers could share their point of view (Klemens' original email is attached below). As I basically outlined in an irc conversation, there are 3 possible ways for us to sync with the Wine project: 1) Do manual syncs (the current way), keeping their code in our tree, building with our build system 2) Do auto-import of their source code into our tree, plus automatically detect changes in their build files and propogate them to our .rbuild files 3) Do binary-syncing of the dlls which are free from reactos and wine hacks, and do manual syncs for dlls which are forked (like setupapi which is better implemented, directx dlls which are partly shared and partly implemented differently, etc). However, it was not possible to easily come to a solution what to do. I will give a small overview of all ways: 1) We lag behind, providing outdated, featureless and buggy version of dlls. And even more, we depend on dlls bugs, reactos hacks in them. Syncing them requires time and constant efforts. From the good side we have absolute control over the libraries - we can enable/disable debug messages, build them for different architectures, optimize for different CPUs etc 2) This could sound like an ideal way, because it keeps advantages of 1. plus removing disadvantages of having to waste time doing syncs. However conversion from Wine's build system makefiles to ReactOS's build system .rbuild isn't trivial. Plus developing an auto-syncer between Cvs/Git and our SVN doesn't look like an easy task too. 3) Reduces compilation time, however wine dlls are built on another server, and just downloaded during build process (or kept in SVN server in binary form). It'd be needed to adjust building mechanism to be able to produce other platform binaries. Updates will be "heavy" (but initial download smaller). I'm listening to your (all ReactOS and Wine devs) comments, and probably I will write answers to Klemens' email later. WBR, Aleksey Bragin. On Jun 12, 2006, at 2:35 PM, Klemens Friedl wrote: > Hi Aleksey, > > I spoke with Gé and he explained me the vendor import process in > short. As soon as I find some time I will try out it myself and update > the Wine libs in our SVN tree, if you don't mind. > > Or do you want to switch to a binary wine files in trunk anyway? > > I will try to update Wine files about every months after the first > time, if that is okay. The changes of wine 0.9.x of every two week are > minor things so, every months should be fine. sdwards mentioned that > timeframe too, as we discussed about that topic about one week ago on > #winehackers and #reactos (the first time). > > btw. Gé mentioned there ARE reasons why our Wine libs DO differ from > WineHQ's one. Well Gé is not a ros dev anymore but he had not done the > vendor import work and maintain all the changes for fun, it's > important to have our adjustments in there. > Imagine for example all icons would got lost. > > Wine does use Unix specific functions like "unixfs" in several libs, > the sound libs will get a lot different in near future too > (silverblade is working in this area) and several directx libs. So a > quick auto vendor import won't work anyway. > > > In my opinion, the binary idea is not worth any efford: > > In my opinion, binary files on in a svn dir is a very bad solution. > You cannot view the source and commit the changes, you have to > download all binary files every time (every 2 weeks), binary files are > not portable, etc. > The advantages of source code is in addition to the oposite of the > facts above that you have to download only the diffs of the file > changes (svn client does that for you) and that have everything > (source) on your local hdd. > Sure the build-time would decrease about 10-15% if we use binary > files, but i don't bother about 15% time. > > And please shift the wine lib conversation to ros-dev(a)reactos.org. > The irc chat is not suitable for such a discussion where more than 3-4 > devs are involved. It is not possible to answer to more then one msg > the same time. And while you write, several other persons post other > msg's. > Mailing lists does have a purpose and does make sense here! > E-Mail's are written in a better english, no short abbreviations, etc. > and the devs does think a bit longer about what the write (no offence > here!). > > > Best regards, > Klemens

3 2

Kernel-mode COM: PORTCLS.SYS and sound
by Andrew "Silver Blade" Greenwood 09 Jun '06

09 Jun '06

Someone on this mailing list gave me a crash-course on using COM (possibly KJK, but it was a while ago so I'm not sure.) Anyway, I'm fairly comfortable with the various macros and sort of understand how it works now. == SOUND ARCHITECTURE == I've been told that Windows Vista has a new user-mode set of audio/multimedia APIs, which replace kernel-mode streaming. Evidently most of the kernel-mode components for this no longer exist in Vista. Instead, communication goes via user-mode components until PORTCLS.SYS, the only remaining kernel-streaming related component. PORTCLS.SYS interacts with WDM audio drivers. WDMAUD.DRV interacts with the MME API (winmm.dll). So the path from the MME API to the WDM driver may be different, but older applications and drivers should see no difference there. I think implementing the audio system used in Vista would be a good thing to do - since the kernel streaming components have been completely removed from Vista, there is no point in implementing them in ReactOS. There should be no reason why an NT4 audio driver wouldn't work even on Vista, and XP drivers should work too. Obviously this won't be the case, though, as all drivers will probably need to be designed specifically for Vista. My point however, is that the MME API has changed slightly, but will still work with older drivers. (As a side-note, I recall that our implementation of WINMM.DLL - as copied over from WINE - doesn't appear to deal with Plug and Play at all. This is something that will need to be remedied.) == PORTCLS.SYS : COM IN THE KERNEL == This took a while for me to get my head around, and I'm at the stage now where I can happily declare a COM interface or class. But I'm having difficulty figuring out how I should actually create an instance of one in the kernel. Apparently, there exists some kernel equivalent of CoCreateInstance. In any case, I'd prefer to work with classes using C++, which I believe can be done with COM. So I just need to know how to implement a COM class using C++. Up until now I've guessed it as being: class IBlahBlah_Impl : public IBlahBlah Is this right? I'm working on the IPort code at the moment, and am wondering how to implement this: PORTCLASSAPI NTSTATUS NTAPI PcNewPort( OUT PPORT *OutPort, IN REFCLSID ClassId) { /* ClassId must be one of: CLSID_PortDMus (IPortDMus) defined in dmusicks.h CLSID_PortMidi (IPortMidi) CLSID_PortTopology (IPortTopology) CLSID_PortWaveCyclic (IPortWaveCyclic) CLSID_PortWavePci (IPortWavePci) */ } Yes, it's just a commented function. From the documentation, the caller passes one of the CLSID's from the above list, and receives a pointer to an IPort. Question is, how do I compare the parameter with one of the CLSIDs? And again, how do I create an instance of the class in kernel-mode? If anyone can shed a little light on this, I'd appreciate it. -Andrew

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev