Ros-dev April 2006

ros-dev@reactos.org

28 participants
45 discussions

by James Tabor

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"

18 years, 8 months

Re: [ros-svn] [jimtabor] 20958: Port Wine GetCharWidth32A.

by Magnus Olsen

This implention is wrong please revert it it shall and must be implement in win32k not direcly to gdi32 NtGdiGetCharWidth ----- Original Message ----- From: <jimtabor(a)svn.reactos.org> To: <ros-svn(a)reactos.org> Sent: den 21 January 2006 01:52 Subject: [ros-svn] [jimtabor] 20958: Port Wine GetCharWidth32A. > Port Wine GetCharWidth32A. > > > Updated files: > trunk/reactos/lib/gdi32/objects/font.c > > _______________________________________________ > Ros-svn mailing list > Ros-svn(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-svn

18 years, 9 months

RE: Ros-dev Digest, Vol 14, Issue 25

by Lucio Diaz

David Hinz wrote: Hey guys, when I just translated format, I stunbled over one thing: What if somebody changed the content of a string after I translated it? After some minutes, I had a easy solution for that problem: The En.rc gets a little line in it's head-comment with a revision number. Each time somebody changes or adds a string in the En.rc, he sets the revision number +1 and so all translators have an easy to control indicator, if they need to translate something or not. But I think one thing should be clear, if there just has been corrected a spelling mistake and not something important, the revision number won't be touched. Now some example headers: in the EN.rc: /* * Moved all hardcoded strings to En.rc. * By Magnus Olsen 2005 * * Revision: 1 */ in my De.rc: /* * Moved all hardcoded strings to En.rc. * By Magnus Olsen 2005 * First German Translation by David Hinz 20051010 * * Translated Revision 1 of En.rc */ This is just an idea, but I think this could save a lot of work on bigger applications than format... Greets, David Hinz --------------------------------------- I agree, in fact i am working in a program to manage translation in reactos, i am using Delphi 2.0 but as i am not much skilled (long time since i used pascal) and my time is on the limit it is going slowly but it should work as follow: Part 1: - You select your language - You select the working directory of reactos source. - The program scans all files for en.rc files and list their directories (as their names are all the same). - With each file the program check a text file with a list of en.rc files, and if it is not there it adds it, and it is shown in the GUI as highlighted (pending translation). - If the file is found in the list, it check if translating language file is current--> if it is not current then the file is highlighted (pending translation). - If the file is found in the list, and found a translation file current--> the file is listed but not highlighted. - It does with all rc files till no more rc files in the directory. Part 2: - On clicking in a file in the listbox (highlighted or not) it will be shown in an Richtext edit panel and besides another panel with the material already translated (if there is any language related file already done), if not, the english text will be shown with the "probable translatable" areas highligthed (those between ""). -A save button, that will save the changes in the second panel automatically into the right directory in a language working copy. What do you think? ______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es

18 years, 9 months

Re: [Freedce-devel] pthread_clear_exit_np()

by Luke Kenneth Casson Leighton

okay, so these are the options: 1) forget redhat and forget them ever being helpful and supporting strategically important free software projects, and go back to using dcethreads posix draft 4 "emulation". 2) forget redhat and forget them ever being helpful and supporting strategically important free software projects, and put the cancellation "wrapper" side back into the dcethreads library - just keep the same posix "final draft" API. lord only knows what would happen on pthreads-win32 when compiling freedce with mingw32, with the "wrapper" stuff back in, but i'd be fascinated to find out. 3) think of ways to persuade the developers of glibc to enter into reasonable conversations and dialog to help support a strategically important free software project. how does any other project manage this (and what in hell's name prompted ulrich to be so dismissive?) On Fri, Apr 21, 2006 at 05:26:44PM +0200, thomas.schuetzkowski(a)web.de wrote: > Hi Luke, > > > > To make this work with libc we need to "un-cancel" a thread. > > ... > > Of course, using this in a third-party application is problematic as it > > depends on internal glibc structures. > > > > I know the chances of such an API being added to glibc are about nil, but > > I thought I'd mention this anyway! :-) > > We thought about adding a detection of the glibc version to autoconf stuff and choose the right version of the function. (see Loic's patch) > Then of course someone has to maintain this for every new version of glibc. :-( > > This idea was skipped, because no one had the time to do this. > > regards, > Thomas > _______________________________________________________________ > SMS schreiben mit WEB.DE FreeMail - einfach, schnell und > kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 > -- -- lkcl.net - mad free software computer person, visionary and poet. --

18 years, 10 months

[lukeh@padl.com: NPTL and FreeDCE]

by Luke Kenneth Casson Leighton

guys, hi, am on the mailing list (subscribed) but am not receiving posts: please cc me if this would be an issue. for win32, i am using pthreads-win32: will reactos be able to support the trick that luke howard is referring to? l. ----- Forwarded message from Luke Howard <lukeh(a)padl.com> ----- Envelope-to: lkcl@localhost Delivery-date: Mon, 24 Apr 2006 12:51:50 +0100 X-Original-To: lkcl(a)lkcl.net Resent-Date: 24 Apr 2006 10:22:43 -0000 From: Luke Howard <lukeh(a)padl.com> Organization: PADL Software Pty Ltd To: freedce-devel(a)lists.sourceforge.net Subject: NPTL and FreeDCE Cc: opendce(a)opengroup.org Reply-To: lukeh(a)padl.com Versions: dmail (bsd44) 2.6d/makemail 2.10 X-Spam-Status: NO, hits=-5.60 required=5.00 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on au.padl.com X-Spam-Flag: NO X-Spam-Level: Resent-Message-ID: <UQB5HC.A.7PG.ubKTEB@mailman> Resent-To: opendce(a)opengroup.org Resent-From: opendce(a)opengroup.org X-Mailing-List: opendce:archive/latest/626 Resent-Sender: opendce-request(a)opengroup.org X-hands-com-MailScanner: Found to be clean X-MailScanner-From: opendce-request(a)opengroup.org Resent-Date: Mon, 24 Apr 2006 12:51:50 +0100 It may be possible to integrate DCE exception handling and NPTL so that longjmp() is never explicitly called from a cancellation cleanup handler. In fact, cleanup handlers need not be used at all. This approach requires the NPTL r ather than the LinuxThreads, API and is orthogonal to the previous issue about removing thread cancellation (that was a runtime issue present with NPTL regardless of which header one compiles against). Instead of calling _pthread_cleanup_push_defer(), we can store a __pthread_unwind_buf_t in the exception context and call __sigsetjmp() and __pthread_register_cancel_defer(). If __sigsetjmp() returns from a longjmp(), then we call dce_pthread_test_exit_np() to test whether the thread was cancelled, and set the current exception to pthread_cancel_e if necessary. No cleanup handler is necessary. The trick is that the code that raises an exception needs to call the internal API __pthread_unwind(), rather than longjmp(). Of course this ends up calling longjmp() anyway but hopefully does the right thing with respect to any other cleanup handlers that are registered. Another idea is to use the _Unwind_XXX API, but this strikes me as a little ambitious for now and I don't have any desire to interleave C++ and DCE exceptions. /* * For the NPTL API we share a setjmp/longjmp buffer between the * pthreads cancellation and DCE exception handling APIs. * * Note that we never actually call the cancellation function, we * just change the current exception context directly; this is the * same as calling dce_ptdexc_raise(&pthread_cancel_e) except that * __pthread_unwind() is not called. */ #define dce_exc_cleanup_push(cu, routine, arg) do \ { \ __exc_occured = __sigsetjmp((struct __jmp_buf_tag *)(cu)->__cancel_buf.__cancel_jmp_buf, 0); \ if (__exc_occured) \ { \ void *__status; \ \ if (dce_pthread_test_exit_np(&__status) == PTHREAD_STATUS_EXIT_NP \ && __status == PTHREAD_CANCELED) \ __exc_ctxt.exc = &pthread_cancel_e; \ } \ else \ { \ __pthread_register_cancel_defer(&(cu)->__cancel_buf); \ } \ } while (0) #define dce_exc_cleanup_pop(cu, execute) do \ { \ __pthread_unregister_cancel_restore(&(cu)->__cancel_buf); \ } while (0) /* make this a NOOP because we called it above */ #define dce_exc_setjmp(jmpbuf, val) /* we call __pthread_unwind() directly from dce_ptdexc_raise() */ #undef dce_exc_longjmp -- Luke -- ----- End forwarded message ----- -- -- lkcl.net - mad free software computer person, visionary and poet. --

18 years, 10 months

Summer of Code

by Nate DeSimone

Hello Everyone, I've been lurking on this list for a few years and I'm considering applying for the Google Summer of Code 2006. I am a Computer Systems Engineer at Rensselaer Polytechnic Institute, just finishing up my junior year. My GPA is 3.06, and I have taken a good amount of computer science courses including Data Structures and Algorithms and Database Systems. I have programmed in C, C++, C#, VB, Perl, PHP, Java and Javascript before. I'm also familiar with Sybase and MySQL and HTML design. I have also done some Win32 programming on my spare time, you can look at some of my projects at: http://www.rpi.edu/~desimn <http://www.rpi.edu/%7Edesimn> I have never done kernel mode programming before and I'm not certain if I'm quite ready for it yet, so if possible I would like to stay in the user mode space. The enhance explorer and add "wow factor" sounds interesting to me. Is there anything else that would involve at least almost all user mode work? Also I was wondering, approximately how many hours would you expect me to put forth every week should I be accepted? Thank You, Nate DeSimone

18 years, 10 months

need help debugging

by Peter Quiring

Hi all, I'm new to ROS but I've had a few patches accepted to Wine. I'm having difficulty with the website and I can't seem to login (even after enabling multisession) so I can't use bugzilla or the forums. So anyways, I've got ROS to compile (RosBE is great!)/build/install on two systems but I'm getting the following problems on one system (Dell Inspiron 5150 Laptop): During install it shows a 17592185991168 MB unused space partition after my 60 GB FAT32 partition. But install still works okay. During 1st boot I get a bsod, I don't have a COM port (USB only) so I tried to use the SCREEN output option but it's too fast to read. I've try to use the FILE option but only 600+ bytes are written to the debug.log file. I know the cache_manager isn't being flushed because everytime it crashes the contents of the folders in "Documents & settings" folder are corrupt (ie: "All Users.Reactos", etc.) So my question is : How can I disable the cache_manager? Or can I place sync() commands somewhere in the source for testing. (is there such a function available?). The bsod seems to be related to gdi issues during creating the primary surface. Somewhere the DeviceObject for the screen is NULL and is not caught till it causes a GPE much later. I'll give a little info that I've written down. /ntoskrnl/io/irp.c:570 - GPE /ntoskrnl/io/irp.c:911 /subsystems/win32/win32k/objects/dc.c:693 /subsystems/win32/win32k/ntuser/winsta.c:348 /subsystems/win32/win32k/ntuser/guicheck.c:57 /subsystems/win32/win32k/objects/dc.c:853 /subsystems/win32/win32k/ntuser/windc.c:121 /subsystems/win32/win32k/ntuser/windc.c:441 /subsystems/win32/win32k/ntuser/windc.c:529 /subsystems/win32/win32k/ntuser/windc.c:101 /ntoskrnl/ke/traps.c:306 /dll/win32/user32/windows/dialog.c:696 Hope this helps. I was using the lastest SVN at the time (21738 I think). Thanks. Peter Quiring

18 years, 10 months

two new bugs in newer ROS

by theUser BL

Hi! There existing two bugs from which I know, which existing not in older SVN/CVS-Snapshot ROS versions. Windows Tetris don't show the Highscore correct. With build 21549 there was still all ok. But with 21639 and all above the Highscore shows only curios symbols as text. AbiWord no longer runs. On build 21323 still all runs correct. But with 21549 the complete ROS hangs up. It ends with "A problem has been detected and ReactOS has been shut down to prevent damage to your computer APC_INDEX_MISMATCH" And so on. Don't know if in the current CVS/SVN-Version the bugs are already fixed. But they existing for some days/weeks. Greatings theuserbl

18 years, 10 months

RE: [ros-dev] RE: ncpa

by Murphy, Ged (Bolton)

Ge van Geldorp wrote: > > The status of the applet when I worked on it was that the UI > was complete > and I was starting to work on transfering the data from the > dialog to the > TCP/IP driver (via the DHCP client). That part simply isn't > implemented yet. Is there a particular reason you were doing this via the DHCP client and not just using functions provided by iphlpapi? 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

18 years, 10 months

Oh, and then the ROS-Explorer bug with the Folder-Icons

by theUser BL

Oh, I have fogotten to mention, that there is also a bug in the ROS-Explorer, that the icon for folders is the same like that for files.

18 years, 10 months

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 2006