Ros-dev August 2005

ros-dev@reactos.org

62 participants
118 discussions

some ROS 0.27RC1 LiveCD feedback
by Bernd Blaauw 07 Aug '05

07 Aug '05

Hi ReactOS project, I've tried your 0.27RC1 LiveCD in VMware Workstation 4.5.2 for Windows, and it's great to have a win32 compatible LiveCD. things I noticed. *CTRL-ALT-DEL (eh..INS for VMware) doesn't bring up Taskmgr, but rightclicking on start menu, then selecting taskmgr, does, as well as running START/RUN/TASKMGR.EXE does. *In VMware, the third tab (with graphs) looks strange *bootCD doesn't start LiveCD automatically when no bootable harddisk is present. It still prompts for 'press a key to start CD'. MS Win2000/XP cdrom behave different depending on if an active bootable primary partition is present (press a key to boot cdrom), or not (automatically boot into cdrom) *LiveCD gets assigned drive C:. I hope you're able to change this into 'start with D: or higher' Reason: partition from a ROS LiveCD, at least a primary partition with driveletter C: should be able to be created. *Rightclick on Start, then Settings. The window show up too low (tab page Desktop shows top 8 items, not all 11). Also the checkbox doesn't have any noticeable effect, I expected some version number to be displayed on the desktop, like in beta Windows builds. *Shutdown EXPLORER causes reboot (why not just fallback into TASKMGR which can start programs, or in CMD.EXE ?) *Logoff causes reboot *Shutdown option is followed by a dialogue, in which answering YES doesn't shut duwn the computer *Where is the cdrom bootsector as a file? Copying all files from cdrom to a directory on harddisk followed by running MKISOFS should be possible, but to create a bootable cdrom you'd also need the bootsector as a 2KB file. I'd really dislike needing some 'extract bootsector from (Live)CD' program, or needing to download additional files just to compile/extract a bootsector. Can the target file which the bootsector should load be configured at boottime? Enough space for '\12345678.ABC\12345678.ABC' ? The Windows bootsector usually is limited (in binary form ofcourse) to 'i386\somefile.ext' (4 characters for directory). Would be cool if a modified ROS cdrom bootsector could boot Win2000/XP setup as the cdrom bootsector for these operating systems might be copyrighted officially (and no public license for distribution of it). Despite these comments, I'm VERY impressed by the current progress since 0.24/0.25 ! 0.35 or so might have a moderately usable system working (OpenOffice, FireFox, Thunderbird, Winrar/7Zip, WinAMP perhaps) Bernd PS: normal ROS cd: ICON.ICO still in root of cdrom, which is not necessary and pollutes your DVD if you add ROS to a multi-OS compilation ( WinPE + Win2000 setup + FreeDOS + ReactOS setup + Knoppix + ... ) Bernd

2 1

bugcheck: kernel32_winetest thread
by Steven Edwards 07 Aug '05

07 Aug '05

Hi, Nice work on nailing down the bugchecks. I think this is one of the last ones. KeBugCheck at ntoskrnl/ps/thread.c:678 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. Technical information: *** STOP: 0x00000000 (0x00000000,0x00000000,0x00000000,0x00000000) Frames: <ntoskrnl.exe:2516 (ntoskrnl/ke/bug.c:498 (KeBugCheckEx))> <ntoskrnl.exe:254e (ntoskrnl/ke/bug.c:519 (KeBugCheck))> <ntoskrnl.exe:82df6 (ntoskrnl/ps/thread.c:678 (NtOpenThread))> <ntoskrnl.exe:96362 ({standard input}:177 (KiSystemService))> <kernel32.dll:34f82 (lib/kernel32/thread/thread.c:279 (OpenThread))> KeBugCheckWithTf at ntoskrnl/ke/catch.c:228 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 (0x80000003,0x800a0847,0x80fa44c0,0x1f000000) *** ntoskrnl.exe - Address 0x800a0847 base at 0x80000000, DateStamp 0x0 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Publish - new sub project
by Robert Köpferl 07 Aug '05

07 Aug '05

Hi, since it is not the only time I do a 'publish-build', I have already some kind of publish program/script. I intend to create a new sub project i.e. 'ros-publish' to more or less automate the process of building reactos, installing ros plus upping it to a ftp. Currently, this is a horrible mixture of bash script and win32-programs plus batch files. However I intend to rewrite it in a general purpose script language like ruby, perl or python. Comments welcome

2 1

Re: [ros-dev] Website Design Voting
by Vegard Edvardsen 07 Aug '05

07 Aug '05

If I'm allowed to vote, my vote is for 4) Mindflyer.

1 0

Re: [ros-svn] [ion] 17150: Fix NtSignalAndwaitForSingleObject: Use SEH when appropriate, use direct Mutant release call, query handle info and write fixmes when permission checking needed, optimize failure cases, fix horrid tab/space formatting mismatches
by Royce Mitchell III 07 Aug '05

07 Aug '05

ion(a)svn.reactos.com wrote: >Fix NtSignalAndwaitForSingleObject: Use SEH when appropriate, use direct Mutant release call, query handle info and write fixmes when permission checking needed, optimize failure cases, fix horrid tab/space formatting mismatches > > >Updated files: >trunk/reactos/include/ndk/extypes.h >trunk/reactos/ntoskrnl/ob/wait.c > > > Alex, May I please request that we not mix reformatting with real changes. It makes it hard to see what was really changed. Thanks, Royce3

1 0

Re: [ros-svn] [hpoussin] 17162: Implement SetupGetInfFileListW and SetupGetInfInformationW
by Thomas Weidenmueller 07 Aug '05

07 Aug '05

hpoussin(a)svn.reactos.com wrote: > Implement SetupGetInfFileListW and SetupGetInfInformationW > Inf file parser now accept UNICODE files with FF FE header > Return required buffer size when buffer is too small in SetupGetLineTextA/W, SetupGetStringFieldA/W I think you forgot to commit changes to a header file: lib\setupapi\parser.c: In function 'SetupGetInfInformationW': lib\setupapi\parser.c:1874: error: 'INFINFO_INF_SPEC_IS_HINF' undeclared (first use in this function) lib\setupapi\parser.c:1874: error: (Each undeclared identifier is reported only once lib\setupapi\parser.c:1874: error: for each function it appears in.) lib\setupapi\parser.c:1875: error: 'INFINFO_INF_NAME_IS_ABSOLUTE' undeclared (fi rst use in this function) lib\setupapi\parser.c:1876: error: 'INFINFO_DEFAULT_SEARCH' undeclared (first us e in this function) lib\setupapi\parser.c:1877: error: 'INFINFO_REVERSE_DEFAULT_SEARCH' undeclared ( first use in this function) lib\setupapi\parser.c:1877: error: 'INFINFO_INF_PATH_LIST_SEARCH' undeclared (fi rst use in this function) lib\setupapi\parser.c: In function 'SetupGetInfFileListW': lib\setupapi\parser.c:2019: error: 'INFINFO_INF_SPEC_IS_HINF' undeclared (first use in this function)

2 1

Re: [ros-svn] [ion] 17139: Add failure cases for more things then a WINE test could shake a stick at (hopefully)
by Steven Edwards 07 Aug '05

07 Aug '05

Hi Alex, --- ion(a)svn.reactos.com wrote: > Add failure cases for more things then a WINE test could shake a stick at (hopefully) Great! The virtual test no longer causes a bugcheck. Want to try this one? =) kernel32_test sync sync.c:93: Test failed: should succeed KeBugCheckWithTf at ntoskrnl/ke/catch.c:228 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 (0xc0000047,0x80007cfb,0x000ef350,0x9e89bc5c) *** ntoskrnl.exe - Address 0x8002ad39 base at 0x80000000, DateStamp 0x0 Exception: -2131009312(0) Processor: 0 CS:EIP 8:8002ad39 <ntoskrnl.exe:2ad39 ({standard input}:1521 (ZwRaiseException))> cr2 8069be40 cr3 5522000 Proc: 80fa3cb0 Pid: 128 <kernel32_test.e> Thrd: 80f98718 Tid: 12c DS 10 ES 10 FS 30 GS 0 EAX: 00000096 EBX: 000000ce ECX: 00000000 EDX: 9e89bd74 EBP: 9e89bc0c ESI: 006afdf0 ESP: 9e89b89c EDI: 9e89bd74 EFLAGS: 00000292 kESP 9e89b89c kernel stack base 9e899000 Frames: <ntoskrnl.exe:1bc3a (ntoskrnl/ex/error.c:64 (ExRaiseStatus))> <ntoskrnl.exe:7cfb (ntoskrnl/ke/sem.c:104 (KeReleaseSemaphore))> <ntoskrnl.exe:77df0 (ntoskrnl/ob/wait.c:276 (NtSignalAndWaitForSingleObject))> <ntoskrnl.exe:95ca2 ({standard input}:177 (KiSystemService))> <kernel32.dll:341c4 (lib/kernel32/synch/wait.c:283 (SignalObjectAndWait))> KeBugCheckWithTf at ntoskrnl/ke/catch.c:228 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 (0x80000003,0x800a0187,0x00000000,0x9e89b0e0) *** ntoskrnl.exe - Address 0x800a0187 base at 0x80000000, DateStamp 0x0 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

VirtualAlloc Bugcheck
by Steven Edwards 07 Aug '05

07 Aug '05

With the trunk. kernel32_test.exe virtual virtual.c:36: Test failed: VirtualAlloc should fail on zero-sized allocation virtual.c:37: Test failed: got -559038737, expected ERROR_INVALID_PARAMETER Assertion 'marea->StartingAddress != Node->StartingAddress' failed at ntoskrnl/mm/marea.c line 437 KeBugCheckWithTf at ntoskrnl/ke/catch.c:228 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 (0x80000003,0x8009fe71,0x80fc6364,0x9e89bb70) *** ntoskrnl.exe - Address 0x8009fe71 base at 0x80000000, DateStamp 0x0 Breakpoint Exception: 3(0) Processor: 0 CS:EIP 8:8009fe71 <ntoskrnl.exe:9fe71 ({standard input}:23 ())> cr2 6ad9a8 cr3 589f000 Proc: 80fc48d8 Pid: 12c <kernel32_test.e> Thrd: 80f984d8 Tid: 124 DS 10 ES 10 FS 30 GS 0 EAX: 00000063 EBX: 0000000b ECX: 00000000 EDX: 000003f8 EBP: 9e89bc54 ESI: 006afdf8 ESP: 9e89bbc4 EDI: 9e89bd74 EFLAGS: 00000296 kESP 9e89bbc4 kernel stack base 9e899000 Frames: <ntoskrnl.exe:5a309 (ntoskrnl/mm/marea.c:437 (MmInsertMemoryArea))> <ntoskrnl.exe:5ad47 (ntoskrnl/mm/marea.c:1015 (MmCreateMemoryArea))> <ntoskrnl.exe:53f65 (ntoskrnl/mm/anonmem.c:640 (NtAllocateVirtualMemory))> <ntoskrnl.exe:95992 ({standard input}:177 (KiSystemService))> <kernel32.dll:100e5 (lib/kernel32/mem/virtual.c:31 (VirtualAllocEx))> KeBugCheckWithTf at ntoskrnl/ke/catch.c:228 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 (0x80000003,0x8009fe77,0x00000000,0x9e89b388) *** ntoskrnl.exe - Address 0x8009fe77 base at 0x80000000, DateStamp 0x0 ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs

2 1

Re: [ros-dev] mouse and keyboaed
by Filip Navara 05 Aug '05

05 Aug '05

4 4

mouse and keyboaed
by Hartmut Birr 05 Aug '05

05 Aug '05

Hi, something is wrong with the keyboard and mouse. I get the following message on real hardware and keyboard and mouse are not usable: (drivers\input\i8042prt\registry.c:215) Can't read registry: c0000034 (drivers\input\i8042prt\registry.c:226) Manually set defaults (drivers\input\i8042prt\i8042prt.c:538) Got fe instead of 55 (drivers\input\i8042prt\i8042prt.c:565) Basic keyboard detection failed: c0000185 - Hartmut

2 1

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 August 2005