Ros-dev August 2005

ros-dev@reactos.org

62 participants
118 discussions

wiki
by Hartmut Birr 05 Aug '05

05 Aug '05

Hi, I've described the procedure to install ReactOS on a scsi disk. It would be nice, if someone can correct the spelling mistakes of my poor english. http://www.reactos.com/wiki/index.php/Disk_and_SCSI_miniport_drivers - Hartmut

4 3

RE: [ros-svn] [navaraf] 17064: Fix shell32 build.
by Ge van Geldorp 05 Aug '05

05 Aug '05

> From: navaraf(a)svn.reactos.com > > Fix shell32 build. Sorry, forgot to commit the changes to include files.

1 0

install problem
by Hartmut Birr 05 Aug '05

05 Aug '05

Hi, since some time, I'm not able to change the screen resolution after a fresh installation. It isn't possible to move the display dialog in a position, where it is possible to hit the 'OK' button. This has worked in the past. - Hartmut

2 1

RE: [ros-dev] RE: [ros-bugs] [Bug 695] New: Tracert - Wrong outpo ut
by Murphy, Ged (Bolton) 05 Aug '05

05 Aug '05

> -----Original Message----- > From: Murphy, Ged (Bolton) [mailto:MurphyG@cmpbatteries.co.uk] > Sent: 05 August 2005 08:18 > To: 'ros-dev(a)reactos.com' > Subject: [ros-dev] RE: [ros-bugs] [Bug 695] New: Tracert - > Wrong outpout > > This is because GetNameInfo is not implememted in ROS. I > originally used > GetHostByAddr, but if the IP does not have a hostname, it > takes a long time > for the function to return, blocking the flow of the program. > This is the > reason tracert hasn't been added to the bootcd yet. > > Alex's ws2_32 rewrite should solve this. I'm hoping he's used > GetNameInfo, > as GetHostByAddr is depricieted anyway now in favour of this. > > I also need to do testing with tracert in ROS, as it is > currently untested > and will more that likely contain a few bugs. (such > confidence I have in my > code :) ) > > I'm also wondering why node 11 and 12 are the same in the > above windows > output. I haven't seen that happen before. Again, I'll look into it. > > Ged. Sorry, I also forgot to mention that TTL support is not yet acessable via the SetSockOpt routine. TTL will therefore default to 128 IIRC, which will break out of the loop imidietly as it would if it had hit the default maximum of 30 hops in tracert. All this info is available in the usage screen which can be viewed by entering 'tracert' with no args. Ged. ************************************************************************ 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

RE: [ros-bugs] [Bug 695] New: Tracert - Wrong outpout
by Murphy, Ged (Bolton) 05 Aug '05

05 Aug '05

> -----Original Message----- > From: ReactOS.Bugzilla(a)reactos.com > [mailto:ReactOS.Bugzilla@reactos.com] > Sent: 05 August 2005 06:52 > To: ros-bugs(a)reactos.com > Subject: [ros-bugs] [Bug 695] New: Tracert - Wrong outpout > > > http://reactos.com/bugzilla/show_bug.cgi?id=695 > > Summary: Tracert - Wrong outpout > Product: ReactOS > Version: 0.3.0-SVN > Platform: x86 Hardware > OS/Version: ReactOS > Status: NEW > Severity: normal > Priority: P3 > Component: Networking > AssignedTo: ros-bugs(a)reactos.com > ReportedBy: gerard.gatineau(a)laposte.net > > > Test done with svn 17040 > > The "tracert command" does not display correct result as below > > Ros Tracert in Ros > ------------------ > > Tracing route to www.laposte.net [81.255.54.10] > over a maximum of 30 hops: > > 1 164 ms 80 ms 81 ms > aaaAAaaaaaaAaaaa-LIBGCCW32-EH-2-SJLJ-GTHR-MINGW32 [81.255.54.10] > > Trace complete. > > The tracert command ( from Ros ) ran in windows displays correctly . > It means that the tracert program in Reactos is correct but > the Ros networking > support is the problem > > Ros Tracert in Windows > ---------------------- > > Tracing route to www.laposte.net [81.255.54.10] > > over a maximum of 30 hops: > > 1 1 ms <1 ms <1 ms 192.168.0.254 > 2 83 ms 84 ms 84 ms 192.168.254.254 > 3 61 ms 59 ms 59 ms > vlq-6k-2-a11.routers.proxad.net [212.27.37.190] > 4 62 ms 61 ms 62 ms > p19-6k-2-v800.intf.routers.proxad.net [212.27.50.6] > 5 62 ms 62 ms 62 ms > aub-6k-1-v806.routers.proxad.net [212.27.50.162] > 6 60 ms 62 ms 61 ms > GE0-3-0-0.noaub101.Aubervilliers.francetelecom.net [193.252.161.97] > 7 60 ms 59 ms 62 ms > pos5-0.ntaub301.Aubervilliers.francetelecom.net > [193.252.103.86] > 8 69 ms 69 ms 70 ms pos9-0.nrlyo201.Lyon.francetelecom.net > [193.252.103.77] > 9 73 ms 72 ms 75 ms pos6-0.ncnic201.Nice.francetelecom.net > [193.252.101.157] > 10 74 ms 73 ms 74 ms 81.255.54.252 > 11 76 ms 75 ms 74 ms www.laposte.net [81.255.54.10] > 12 74 ms 76 ms 77 ms www.laposte.net [81.255.54.10] > > Trace complete. > This is because GetNameInfo is not implememted in ROS. I originally used GetHostByAddr, but if the IP does not have a hostname, it takes a long time for the function to return, blocking the flow of the program. This is the reason tracert hasn't been added to the bootcd yet. Alex's ws2_32 rewrite should solve this. I'm hoping he's used GetNameInfo, as GetHostByAddr is depricieted anyway now in favour of this. I also need to do testing with tracert in ROS, as it is currently untested and will more that likely contain a few bugs. (such confidence I have in my code :) ) I'm also wondering why node 11 and 12 are the same in the above windows output. I haven't seen that happen before. Again, I'll look into it. Ged. ************************************************************************ 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

Website Design Voting
by Murphy, Ged (Bolton) 05 Aug '05

05 Aug '05

Would it not be easier to wait until the website is back up and use the poll feature. This could get confusing. ************************************************************************ 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

Re: [ros-svn] [weiden] 17031: implemented OffsetClipRgn()
by James Tabor 04 Aug '05

04 Aug '05

Hi! weiden(a)svn.reactos.com wrote: > implemented OffsetClipRgn() > > > Updated files: > trunk/reactos/subsys/win32k/objects/cliprgn.c > Yeah!!! 8^D Thanks, James

1 0

Installed X-Chat 2.4.4 and Gdi32_crosstest
by James Tabor 04 Aug '05

04 Aug '05

Hi! I can install Xchat 2.4.4 from http://www.silverex.org/news/. It look horrible but it does run with some exceptions. One, you may have to start the app from it's lib directory, "..\xchat". I do not have a screen- shot 8^P. But here is a debug print, this does not happen often, only when exiting the app from the X button. It looks like something I posted before. GTK+ apps are starting to work under ROS, this alone should speak volumes! Btw! We need to implement NtGdiOffsetClipRgn, I dont care if it is a haxed wine port, atleast something. Bitmap seems broken too. X-Chat, WARNING: NtGdiOffsetClipRgn at subsys/win32k/objects/cliprgn.c:330 is UNIMPLEME NTED! WARNING: NtGdiOffsetClipRgn at subsys/win32k/objects/cliprgn.c:330 is UNIMPLEME NTED! (subsys/win32k/misc/object.c:463) Object type mismatch 0x2 0x5 (subsys/win32k/misc/object.c:463) Object type mismatch 0x2 0x5 (lib/comctl32/toolbar.c:416) bitmap for ID 0, index 1 is not valid, number of bi tmaps in imagelist: 0 (subsys/win32k/misc/object.c:463) Object type mismatch 0x2 0x5 (subsys/win32k/objects/gdiobj.c:545) GdiHdr->Locks: 1 Assertion 'FALSE' failed at subsys/win32k/objects/gdiobj.c line 549 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,0x8009fdf1,0x9dcf622e,0x00000009) *** ntoskrnl.exe - Address 0x8009fdf1 base at 0x80000000, DateStamp 0x0 Breakpoint Exception: 3(0) Processor: 0 CS:EIP 8:8009fdf1 <ntoskrnl.exe:9fdf1 ({standard input}:23 ())> cr2 77ee23f6 cr3 20c91000 Proc: 817108e0 Pid: 128 <gtk2_prefs.exe> Thrd: 81c744b 8 Tid: 120 DS 10 ES 10 FS 30 GS 0 EAX: 00000044 EBX: 000000d5 ECX: 00000000 EDX: 000003f8 EBP: 9db53c14 ESI: 0068fec0 ESP: 9db53b84 EDI: 9db53d74 EFLAGS: 00000292 kESP 9db53b84 kernel stack base 9db51000 Frames: <win32k.sys:802b8 (subsys/win32k/objects/gdiobj.c:549 (GDIOBJ_FreeObj))> <win32k.sys:805d2 (subsys/win32k/objects/gdiobj.c:670 (GDI_CleanupForProcess))> <win32k.sys:3aea3 (subsys/win32k/main/dllmain.c:102 (Win32kProcessCallback))> <ntoskrnl.exe:82c0e (ntoskrnl/ps/win32.c:99 (PsTerminateWin32Process))> <ntoskrnl.exe:7a5f2 (ntoskrnl/ps/kill.c:295 (PspExitThread))> <ntoskrnl.exe:7ad74 (ntoskrnl/ps/kill.c:593 (NtTerminateProcess))> <ntoskrnl.exe:958f2 ({standard input}:177 (KiSystemService))> <kernel32.dll:32142 (lib/kernel32/process/proc.c:592 (ExitProcess))> gdi32_crosstest bitmap, (subsys/win32k/objects/gdiobj.c:802) Attempted to lock object 0x0 that is delete d! (subsys/win32k/objects/gdiobj.c:802) Attempted to lock object 0x0 that is delete d! (subsys/win32k/objects/gdiobj.c:939) Attempted to lock object 0x0 that is delete d! Assertion 'Dest != NULL && Source != NULL && DestRect != NULL && SourcePoint != NULL' failed at subsys/win32k/eng/copybits.c line 53 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,0x8009fdf1,0x00000296,0x0a32ec37) *** ntoskrnl.exe - Address 0x8009fdf1 base at 0x80000000, DateStamp 0x0 Breakpoint Exception: 3(0) Processor: 0 CS:EIP 8:8009fdf1 <ntoskrnl.exe:9fdf1 ({standard input}:23 ())> cr2 930000 cr3 3aeda000 Proc: 816eb508 Pid: 120 <gdi32_crosstest> Thrd: 816f63c0 Tid: 124 DS 10 ES 10 FS 30 GS 0 EAX: 00000085 EBX: 0000106a ECX: 00000000 EDX: 000003f8 EBP: 9f32e8c0 ESI: 006cee54 ESP: 9f32e830 EDI: 9f32ed74 EFLAGS: 00000282 kESP 9f32e830 kernel stack base 9f32c000 Frames: <win32k.sys:30ce0 (subsys/win32k/eng/copybits.c:53 (EngCopyBits))> <win32k.sys:7a1e3 (subsys/win32k/objects/dib.c:508 (NtGdiGetDIBits))> <ntoskrnl.exe:958f2 ({standard input}:177 (KiSystemService))> <gdi32_crosstest.EXE:565c>

2 2

0.2.7 needs help!
by WaxDragon 03 Aug '05

03 Aug '05

This is a call to all devs! The 0.2.7 branch has a input bug that is currently listed as a blocker for the release. We have been unable to get ahold of tinus (the i8042prt author) to take a look at this particular bug. If anyone is capable and interested in fixing this, please contact myself or simply join #reactos and offer help. Bug info: http://www.reactos.com/bugzilla/show_bug.cgi?id=657 WD -- #irc.freenode.net #reactos 01:03PM <filip2307> i don't know about any bug 01:04PM <filip2307> none exist 01:04PM <filip2307> ReactOS is prefect

1 0

svn.reactos.com unavailable
by Casper Hornstrup 03 Aug '05

03 Aug '05

Hi. Svn.reactos.com will be unavailable in the next 15 min. to ½ hour. Casper

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