Ros-dev April 2005

ros-dev@reactos.org

62 participants
114 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

Ext2 Branch Tests
by James Tabor 05 Jun '05

05 Jun '05

Hi all, I tested some small files to and from root and subdirectories on the ext2 (D:) partition w/o any errors or lockups. Large file testing with 5147559 bytes. copy d:\ros.zip c:\ros.zip,,, it locked up. Only 4194304 bytes copied to drive C:. Does that number look anything familiar to anyone? How about 400000 Hex. ###### File Pointer 0xC0E184F0 [Read] IRQL = 0 [src/read.c] Line No = 12 28 *** FCB Resource Released [Read] IRQL = 0 [src/read.c] Line No = 1244 Freeing = C0E1B950 [misc] IRQL = 0 [src/misc.c] Line No = 1159 Read IRP Received... IRQL = 0 [src/read.c] Line No = 47 === Read File Name : -ros-020-bin.zip- IRQL = 0 [src/read.c] Line No = 216 ->ByteCount = 0x 4000 IRQL = 0 [src/read.c] Line No = 223 ->ByteOffset.LowPart = 0x 3fc000 IRQL = 0 [src/read.c] Line No = 224 ->Can Wait IRQL = 0 [src/read.c] Line No = 228 ->Not Paging Io IRQL = 0 [src/read.c] Line No = 241 ->SynchronousIo IRQL = 0 [src/read.c] Line No = 246 ->BufferedIo IRQL = 0 [src/read.c] Line No = 259 ###### File Pointer 0xC0E184F0 [Read] IRQL = 0 [src/read.c] Line No = 49 6 *** Attempting to acquire FCB Shared [Read] IRQL = 0 [src/read.c] Line N o = 498 State: FCBMain AC:0x0 SW:0x0 EX:0x0 [Read] IRQL = 0 *** FCB Acquired [Read] IRQL = 0 [src/read.c] Line No = 507 [File Read] BufferedIo IRQL = 0 [src/read.c] Line No = 561 State: Resource AC:0x0 SW:0x0 EX:0x0 [Read] IRQL = 0 ###### File Pointer 0xC0E184F0 [Read] IRQL = 0 [src/read.c] Line No = 12 28 *** FCB Resource Released [Read] IRQL = 0 [src/read.c] Line No = 1244 Freeing = C0E19F20 [misc] IRQL = 0 [src/misc.c] Line No = 1159 Read IRP Received... IRQL = 0 [src/read.c] Line No = 47 === Read File Name : -ros-020-bin.zip- IRQL = 0 [src/read.c] Line No = 216 ->ByteCount = 0x 4000 IRQL = 0 [src/read.c] Line No = 223 ->ByteOffset.LowPart = 0x 400000 IRQL = 0 [src/read.c] Line No = 224 ->Can Wait IRQL = 0 [src/read.c] Line No = 228 ->Not Paging Io IRQL = 0 [src/read.c] Line No = 241 ->SynchronousIo IRQL = 0 [src/read.c] Line No = 246 ->BufferedIo IRQL = 0 [src/read.c] Line No = 259 ###### File Pointer 0xC0E184F0 [Read] IRQL = 0 [src/read.c] Line No = 49 6 *** Attempting to acquire FCB Shared [Read] IRQL = 0 [src/read.c] Line N o = 498 State: FCBMain AC:0x0 SW:0x0 EX:0x0 [Read] IRQL = 0 *** FCB Acquired [Read] IRQL = 0 [src/read.c] Line No = 507 [File Read] BufferedIo IRQL = 0 [src/read.c] Line No = 561 Read IRP Received... IRQL = 0 [src/read.c] Line No = 47 === Read File Name : -ros-020-bin.zip- IRQL = 0 [src/read.c] Line No = 216 Gets lost here, ByteCount mul's up by 16: ->ByteCount = 0x 40000 IRQL = 0 [src/read.c] Line No = 223 ->ByteOffset.LowPart = 0x 400000 IRQL = 0 [src/read.c] Line No = 224 ->Can't Wait IRQL = 0 [src/read.c] Line No = 232 ->Paging Io IRQL = 0 [src/read.c] Line No = 237 ->SynchronousIo IRQL = 0 [src/read.c] Line No = 246 ->NonBufferedIo IRQL = 0 [src/read.c] Line No = 255 ###### File Pointer 0xC0E184F0 [Read] IRQL = 0 [src/read.c] Line No = 47 3 *** Attempting to acquire FCBPaging Shared [Read] IRQL = 0 [src/read.c] Line No = 475 State: FCBPaging AC:0x0 SW:0x0 EX:0x0 [Read] IRQL = 0 *** FCBPaging Acquired [Read] IRQL = 0 [src/read.c] Line No = 486 [File Read] Paging IO or NonBufferedIo IRQL = 0 [src/read.c] Line No = 634 Reading in some Single Indirect Blocks IRQL = 0 [src/read.c] Line No = 6 84 Reading in some Double Indirect Blocks IRQL = 0 [src/read.c] Line No = 7 23 State: Resource AC:0x0 SW:0x0 EX:0x0 [Read] IRQL = 0 ###### File Pointer 0xC0E184F0 [Read] IRQL = 0 [src/read.c] Line No = 12 28 *** FCB Paging Resource Released [Read] IRQL = 0 [src/read.c] Line No = 1240 === Asynchronous request. Deferring processing IRQL = 0 [src/misc.c] Li ne No = 1187 Ext2QueueHandlerThread Alerted!!! IRQL = 0 [src/ext2init.c] Line No = 36 1 === Serviceing IRP_MJ_READ request asynchronously . IRQL = 0 [src/misc. c] Line No = 1283 === Read File Name : -ros-020-bin.zip- IRQL = 0 [src/read.c] Line No = 216 ->ByteCount = 0x 40000 IRQL = 0 [src/read.c] Line No = 223 ->ByteOffset.LowPart = 0x 400000 IRQL = 0 [src/read.c] Line No = 224 ->Can Wait IRQL = 0 [src/read.c] Line No = 228 ->Paging Io IRQL = 0 [src/read.c] Line No = 237 ->SynchronousIo IRQL = 0 [src/read.c] Line No = 246 ->NonBufferedIo IRQL = 0 [src/read.c] Line No = 255 ###### File Pointer 0xC0E184F0 [Read] IRQL = 0 [src/read.c] Line No = 47 3 *** Attempting to acquire FCBPaging Shared [Read] IRQL = 0 [src/read.c] Line No = 475 State: FCBPaging AC:0x0 SW:0x0 EX:0x0 [Read] IRQL = 0 *** FCBPaging Acquired [Read] IRQL = 0 [src/read.c] Line No = 486 [File Read] Paging IO or NonBufferedIo IRQL = 0 [src/read.c] Line No = 634 Reading in some Single Indirect Blocks IRQL = 0 [src/read.c] Line No = 6 84 Reading in some Double Indirect Blocks IRQL = 0 [src/read.c] Line No = 7 23 Read IRP Received... IRQL = 0 [src/read.c] Line No = 47 === Read File Name : -null- IRQL = 0 [src/read.c] Line No = 220 ->ByteCount = 0x 40000 IRQL = 0 [src/read.c] Line No = 223 ->ByteOffset.LowPart = 0x4ab00000 IRQL = 0 [src/read.c] Line No = 224 ->Can't Wait IRQL = 0 [src/read.c] Line No = 232 ->Paging Io IRQL = 0 [src/read.c] Line No = 237 ->ASynchronousIo IRQL = 0 [src/read.c] Line No = 250 ->NonBufferedIo IRQL = 0 [src/read.c] Line No = 255 ###### File Pointer 0xC0E18900 [Read] IRQL = 0 [src/read.c] Line No = 28 9 *** Attempting to acquire VCB Shared [Read] IRQL = 0 [src/read.c] Line N o = 294 State: VCBPaging AC:0x0 SW:0x0 EX:0x0 [Read] IRQL = 0 *** VCBPaging Acquired [Read] IRQL = 0 [src/read.c] Line No = 304 [Volume Read] PagingIo or NonBufferedIo IRQL = 0 [src/read.c] Line No = 336 State: Resource AC:0x0 SW:0x0 EX:0x0 [Read] IRQL = 0 ###### File Pointer 0xC0E18900 [Read] IRQL = 0 [src/read.c] Line No = 12 28 *** VCBPaging Released [Read] IRQL = 0 [src/read.c] Line No = 1236 Freei Freeing = C0E1C440 [io] IRQL = 2 [src/io.c] Line No = 426ng = C0E25770 [misc] IRQL = 0 [src/misc.c] Line No = 1159 Lockup..........

2 2

0.2.7?
by WaxDragon 08 May '05

08 May '05

I would like to see a 0.2.7 release soon. 0.3.0 is getting closer every day, but it's not there yet IMHO. On the other hand, we have had lots of big patches from Mr. Ionescu (and others), major changes, go in and appear to be stable since we have released 0.2.6. I would like to see us have another release in this lull, instead of having a release right after committing a pile of patches *right before* the release like we did with 0.2.6. I know it's been less than a month since 0.2.6, but my the time we branch and do a couple RC's, it will have been over a month. I just have this feeling that we miss some regressions from release to release, since alot of us just use HEAD on a regular basis? Just my $0.2US WD -- "<tinus_> and also win32k should be fixed up a bit"

7 9

Re: [ros-svn] [ion] 14810: Change optimization settings for retail builds. Change to -Os for smaller executables which are not slower, and enable more advanced optimizations. funitatatime is already included by default in GCC 4.0. Strip debug info from retail builds, since we don't parse the symbols anyways. I hope these options don't break anything, they don't for me; Debugging is unaffected.
by Alex Ionescu 08 May '05

08 May '05

ion(a)svn.reactos.com wrote: >Change optimization settings for retail builds. Change to -Os for smaller executables which are not slower, and enable more advanced optimizations. funitatatime is already included by default in GCC 4.0. Strip debug info from retail builds, since we don't parse the symbols anyways. I hope these options don't break anything, they don't for me; Debugging is unaffected. > > The direct result of this is that, for non-debug builds (which don't support reading data from symbols anyways, not even during bugcheck), the following data are now true: 1) ntoskrnl is 612kb on my system, down from 1.5MB 2) win32k is 316kb on my system, down from 800kb 3) taskmgr shows 6% idle cpu time, down from 9% 4) memory usage shows 32MB, down from 40MB+ 5) total ISO size is now 12.5MB, down from 14.2MB. Booting up the system to be much faster and everything is more responsive, probably due to the smaller size and new optimizations. Nothing has changed for DBG builds. Best regards, Alex Ionescu

3 2

install problem
by Hartmut Birr 06 May '05

06 May '05

Hi, since some time, I'm not able to install ros from the bootcd over an existing ros. The first stage setup works perfect. The second boot hangs after loading most of the drivers. The last line on the debug port comes from framebuf.dll: ... DriverBase for \??\E:\ReactOS\system32\win32k.sys: 9d62b000 DriverBase for \??\E:\ReactOS\system32\freetype.dll: 9d803000 DriverBase for \SystemRoot\System32\kbdgr.dll: 9d78f000 (ntuser/desktop.c:574) IntShellHookNotify: No desktop! (ntuser/desktop.c:574) IntShellHookNotify: No desktop! (ntuser/desktop.c:574) IntShellHookNotify: No desktop! DriverBase for \SystemRoot\System32\framebuf.DLL: 9dfab000 Has anyone the same problem? The install works again, if I delete all registry files from the existing installation. Usually I use the 'make install' command to install ros over the network on my test machines. - Hartmut

2 2

Both CMD Consoles Go Puff!
by James Tabor 04 May '05

04 May '05

Hi All! Wow! Ros on ros build and I walk away come back and both consoles are gone. Thank god for taskmgr! It shows both cmds', ctm, and three make.exe, not running but still in memory. Build 14598 (KERNEL32:mem/global.c:412) Memory Load: 23 (KERNEL32:mem/global.c:412) Memory Load: 23 (MSVCRT:io/open.c:103) not valid fd 0, g_fdend 5, fdinfo 7802d2f0, bucket 7802d2 f0, fdflags 0 (MSVCRT:io/open.c:700) _setmode: inval fd (0) (NTDLL:ldr/utils.c:2097) Relocating (77ed0000 -> 780000) C:\ReactOS\System32\gdi 32.dll (NTDLL:ldr/utils.c:2097) Relocating (77ed0000 -> 850000) C:\ReactOS\system32\gdi 32.dll (NTDLL:rtl/critical.c:446) Deadlock: 8517f8 Unhandled exception Address: 7c90a05c C:\ReactOS\system32\ntdll.dll CS:EIP 1b:7c90a3d2 DS 23 ES 23 FS 3b GS 23 EAX: 00000000 EBX: 00000000 ECX: 00000000 EDX: 00000000 EBP: 019afdd8 ESI: 00000000 ESP: 019afde0 EDI: 00000000 EFLAGS: 00000212 Frames: 7c900000+a05c C:\ReactOS\system32\ntdll.dll 5ffb0000+8381 C:\ReactOS\system32\win32csr.dll 5ffb0000+8eac C:\ReactOS\system32\win32csr.dll 220000+12a8f C:\ReactOS\system32\user32.dll 220000+12ced C:\ReactOS\system32\user32.dll 5ffb0000+91c4 C:\ReactOS\system32\win32csr.dll 7c800000+26554 C:\ReactOS\system32\kernel32.dll (NTDLL:rtl/critical.c:446) Deadlock: 8517f8 (ke/catch.c:191) Unhandled UserMode exception, terminating thread Explorer is running btw, James

2 4

Multiple problems with HEAD
by Ge van Geldorp 01 May '05

01 May '05

1st problem: when booting rev 14873 (DBG := 1, KDBG := 0) it crashes with: DriverBase for \SystemRoot\system32\drivers\fs_rec.sys: 9cf7c000 (io/file.c:898) Status :0 (io/file.c:898) Status :0 (io/file.c:898) Status :0 DriverBase for \SystemRoot\system32\drivers\beep.sys: 9cf8b000 (io/file.c:898) Status :0 Assertion NewRefCount >= 0 failed at ob/object.c:1150 KeBugCheckWithTf at ke/catch.c:217 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 KMODE_EXCEPTION_NOT_HANDLED Technical information: *** STOP: 0x0000001E (0x80000003,0x800057a4,0x8005d08b,0x8071c9ec) *** ntoskrnl.exe - Address 0x800057a4 base at 0x80000000, DateStamp 0x0 Breakpoint Exception: 3(0) Processor: 0 CS:EIP 8:800057a4 <ntoskrnl.exe: 57a4> cr2 8ccfc000 cr3 27000 Proc: 8053fcf8 Pid: 4 <System> Thrd: 805407f0 Tid: 0 DS 10 ES 10 FS 30 GS 10 EAX: 00000036 EBX: 8004515d ECX: 00000000 EDX: 000003f8 EBP: 800e47a4 ESI: 800e4a84 ESP: 800e4730 EDI: 800e49f4 EFLAGS: 00200286 kESP 800e4730 kernel stack base 800e3000 Frames: <ntoskrnl.exe: 72a9f> <ntoskrnl.exe: 45f2a> <ntoskrnl.exe: 456e1> <vfatfs.sys: 2d00> <vfatfs.sys: d1de> <vfatfs.sys: d3ee> <ntoskrnl.exe: 45158> <ntoskrnl.exe: 40487> <ntoskrnl.exe: 414dd> <ntoskrnl.exe: 3602> <7D83F045> <ntoskrnl.exe: 3e6c0> <ntoskrnl.exe: 3602> <EC83FC45> <ntoskrnl.exe: 3de8e> <800A48CE> <800A21D4> <ntoskrnl.exe: 10004> <800A07AA> <ntoskrnl.exe: 104b> 2nd problem: the crash info is only written to the debug log and not shown as a BSOD. 3rd problem: the stack trace only shows addresses, not source file/line as it should for a DBG build 4th problem: booting with /DEBUGPORT=GDB results in a kernel stack fault very early in the boot process. Gé van Geldorp.

3 6

Re: [ros-dev] 0.2.7?
by reactos 30 Apr '05

30 Apr '05

>>> It's still not fully stable, card support is not great and it's only configurable through regedit at the moment. However it's all being worked on. Arty has done a fantastic job so far. Ged. <<< Actually lately no regedit is needed, as long as reactos registry supports your card only the dhcp software is needed, then everything is working... ...and soon the controlpanel app will be ready and everyone with a compatible card will be able to configure easy. The thing that we really need is support for driver installation. But on the other hand when we releas a new version we could transfer it to a usual textfile and put it on the welcome screen. /Jaix Bly ----Ursprungligt meddelande----- From: Gedi gedi(a)ntlworld.com Date: Sat, 30 Apr 2005 15:21:39 +0200 To: ReactOS Development List ros-dev(a)reactos.com Subject: Re: [ros-dev] 0.2.7? > Michael B. Trausch wrote: > > >Uh... Networking? > > > >I know at the very least *I* haven't seen ping working yet... > > > Networking has been up and running since before christmas now. > Along with the Mozilla control, you can now browse the web with ROS' > built in ibrowser, or use something like dillo. > There are many other programs running too, email, IRC too name but a few. > > >Networking support at the very least should be a staple for most overly > >popular cards before you think about trying to require a web page be > >displayed for something. Instead, put a static page on the CD that gets > >copied to the installed system. > > > > > It's still not fully stable, card support is not great and it's only > configurable through regedit at the moment. > However it's all being worked on. Arty has done a fantastic job so far. > > Ged. > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev

2 1

Re: [ros-dev] 0.2.7?
by reactos 30 Apr '05

30 Apr '05

Good idea, but ones a month is to frequent, people will get tired of testing new versions that they can't see any difference between. I think it has to be focust releases where something actually can be tested or seen, a feature not just read about in a change-log, everyone doesn't read the changelog. By the way, to be able to get people test the right thing when a new versin is released, we should have a welcome-screen packed with information about things changed since last release and so forth, this in a way that people can know how to test the new feature. This welcome screen could be a page in the WIKI so every developer easy can add what they want the testers to try out and how to do it. I know this opens for another problem, we need a browser to do that, can we add the mozilla-com plugin to the release? Or can we include another one? ----Ursprungligt meddelande----- From: WaxDragon waxdragon(a)gmail.com Date: Fri, 29 Apr 2005 19:13:29 +0200 To: ReactOS Development List ros-dev(a)reactos.com Subject: [ros-dev] 0.2.7? > I would like to see a 0.2.7 release soon. 0.3.0 is getting closer > every day, but it's not there yet IMHO. On the other hand, we have > had lots of big patches from Mr. Ionescu (and others), major changes, > go in and appear to be stable since we have released 0.2.6. I would > like to see us have another release in this lull, instead of having a > release right after committing a pile of patches *right before* the > release like we did with 0.2.6. > > I know it's been less than a month since 0.2.6, but my the time we > branch and do a couple RC's, it will have been over a month. > > I just have this feeling that we miss some regressions from release to > release, since alot of us just use HEAD on a regular basis? > > Just my $0.2US > WD > -- > "<tinus_> and also win32k should be fixed up a bit" > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev

3 3

ROS System Updater
by Rick Langschultz 28 Apr '05

28 Apr '05

I have a simple request for when ReactOS wants to add updates to system software when Service Packs and Updates become available. I think that a ReactOS computer should utilize a small system service that indexes file version numbers, indexes them on importance, size, type, and other information. This can be done on a flatfile, XML, or a SQL Database connection. Then the server sends reponses back to the computer offering service packs, files, device drivers, etc. I think that kind of system will allow easy updates to ReactOs on users computers while not having to reinstall or reformat. Something like up2date, or mac os x¹s update program. The system can maybe support rollback of files. Just an idea.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev April 2005