- Ros-dev - ReactOS.org

Re: [ros-svn] [hpoussin] 18636: Revert r18628, as we don't have any RTL8139 driver in ReactOS repository
by Gge 21 Oct '05

21 Oct '05

hpoussin(a)svn.reactos.com wrote: > Revert r18628, as we don't have any RTL8139 driver in ReactOS repository > > > Added files: > trunk/reactos/media/inf/netamd.inf > > Updated files: > trunk/reactos/media/inf/inf.xml > > Deleted files: > trunk/reactos/media/inf/netrtsnt.inf > I was able to install successfully the realtek 8138 nic using the customized "netrtsnt.inf" file provided by hpoussin and to ping www.reactos.org The wiki driver page has to be updated accordingly as this is the new/required method to install this nic with head Note : Still issue around ipconfig which does not display properly ( Registry setting ? ) Regards Gge

1 0

Re: [ros-svn] [hpoussin] 18448: Big Plug-and-Play patch for ReactOS:
by Gge 21 Oct '05

21 Oct '05

hpoussin(a)svn.reactos.com wrote: > Big Plug-and-Play patch for ReactOS: > - Install drivers for devices at first boot > - Remove now useless entries in hivesys.inf > At the moment, driver installation only uses .inf files in ReactOS\Inf directory, and the needed files have to be in ReactOS\Inf or their final location (ReactOS\system32 or ReactOS\system32\drivers) + the user can't provide a custom driver > Plug-and-Plays devices are only USB controllers (OHCI and UHCI) and serial ports now. > > > Updated files: > trunk/reactos/bootdata/hivesys.inf > trunk/reactos/ntoskrnl/io/driver.c > trunk/reactos/services/umpnpmgr/umpnpmgr.c > How the nic driver ( realtek 8139 for example ) can be installed now ? Upto now , it was installed manually by adding "rtl8139 entries" in the registry ( hiveinst.inf file) as per wiki driver page. Regards Gge

3 2

RE: [ros-dev] Break, PC, Constituion and other misc issues
by Murphy, Ged (Bolton) 20 Oct '05

20 Oct '05

Aleksey Bragin wrote: > I regret really that Steven don't have time > right now, since he's best suited to this position (at least by a number of > expos he's taken part in :-)) I also wish Steven could find the time to take on this role. It's unfortunate as this role seemed to be almost written for him. ************************************************************************ 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

3 2

Re: [ros-svn] [navaraf] 18601: Fix DbgPrint calls.
by Hartmut Birr 20 Oct '05

20 Oct '05

navaraf(a)svn.reactos.com wrote: > Fix DbgPrint calls. > > > Updated files: > trunk/reactos/boot/freeldr/freeldr/arch/i386/i386disk.c > Oops, forgot to remove some of my privat debug prints. - Hartmut

2 1

Looking for a place to chekin
by Robert Köpferl 20 Oct '05

20 Oct '05

I'm currently preparing the doc on how to publish ROS. Since I did this a several times I made a QnD script which I want to reference in my description. It's quite not a real solution, but better than nothing on the way until rbuild gets that feature/target. Where do you think I should check that in? I think of a subdirectory at reactos/tools thanks

3 3

Visual Studio
by Jurgen Van Gael 20 Oct '05

20 Oct '05

Hi, I was just fiddling around with reactos and am interested in getting some stuff to compile with msvc. (I tried 2003 and 2005 express beta 2) However, the sln workspace files don't seem to open properly on neither visual studio. The vcproj do; just wondering whether you guys use other versions of visual studio? Jurgen

3 2

top-level source header
by Ged 20 Oct '05

20 Oct '05

Although a standard header was drafted out for the ReactOS source code, few people seem to use it and it doesn't seem to be in the wiki. I would like to get something in the wiki agreed on by everyone which should be included in our source files. I think we firstly need have a vote to see if everyone actually wants a standard header, but I put together some info anyway to explain my thoughts As much of the ReactOS code is licensed under the GPL, it can be reused by anyone under the license agreements. As the BSD code does, I think a ReactOS copyright notice should be placed in the header to ensure people know where the original code came from. Our current header has no provision for this meaning anyone reading ReactOS code away from the project won't have a return point. I was talking this over with Alex, who suggested everyone might not want to give copyright to the foundation. Any suggestions? Using the existing header, I have drafted a slightly modified version /* 1 * ReactOS <place holder> 2 * Copyright (C) 2005 ReactOS Foundation 3 * 4 * LICENCE: <place holder> 5 * PROJECT: <place holder> 6 * FILE: <place holder> 7 * PURPOSE: <place holder> 8 * PROGRAMMERS: <place holder> 9 * REVISIONS: 10 * <place holder> 11 * */ 1. This is a quick line to state the area which the code was written for. Examples could include: ReactOS Executive ReactOS Win32 Subsystem ReactOS Win32 Applications 2. The copyright should detail a date when the copyright was initiated along with the date when it was last modified. For example: 1999 - 2004 The proceeding date should be updated each time a revision is made. 4. This line should state the licence used and where to find the COPYING file 5. This line should state what project / binary the code is for. Examples could include: ReactOS ntdll library ReactOS ws2_32 library ReactOS arp utility ReactOS cache manager ReactOS thread scheduler 6. This line should state the location of the file within the repository 7. This line should state the purpose of the project / binary the code is intended for 8. This line should state any programmers whom have worked on the code. The programmer can also choose to add an email address along with their name as a point of contact 9. This line should list any revisions made to the code. The revisions should include programmers initials, which can be linked to the PROGRAMMERS section, the date the revision was made and a short comment describing the revision. This is not meant for bug fixes and small modifications, but for feature additions or substantial patches I think we should put something in the wiki in relation to this. Does anyone have any other suggestions, or modifications to my header. Please see the examples below. Examples: /* * ReactOS Win32 Applications * Copyright (C) 2005 ReactOS Foundation * * LICENCE: GPL - See COPYING in the top level directory * PROJECT: ReactOS arp utility * FILE: apps/utils/net/arp/arp.c * PURPOSE: view and manipulate the ARP cache * PROGRAMMERS: Ged Murphy (gedmurphy(a)gmail.com) * REVISIONS: * GM 04/10/05 Created * */ /* * ReactOS Executive * Copyright (C) 2005 ReactOS Foundation * * LICENCE: GPL - See COPYING in the top level directory * PROJECT: ReactOS kernel * FILE: ntoskrnl/ex/mutant.c * PURPOSE: section of the kernel * PROGRAMMERS: Alex Ionescu (alex(a)reactos.org) * David Welch (welch(a)cwcom.net) * REVISIONS: * AI 04/10/05 Fix tab/space mismatching, tiny fixes to query function and * add more debug output. * */ /* * ReactOS Network Stack * Copyright (C) 2000 - 2005 ReactOS Foundation * * LICENCE: GPL - See COPYING in the top level directory * PROJECT: ReactOS TCP/IP protocol driver * FILE: transport/tcp/tcp.c * PURPOSE: Transmission Control Protocol * PROGRAMMERS: Casper S. Hornstrup (chorns(a)users.sourceforge.net) * Art Yerkes (arty(a)users.sf.net) * REVISIONS: * CSH 01/08-2000 Created * AY 12/21/2004 Added accept */

5 10

RE: [ros-dev] Voting system
by Murphy, Ged (Bolton) 19 Oct '05

19 Oct '05

Brandon Turner wrote: > I _strongly_ disagree with this. Me too. I'll just elaborate on the reasons Brandon gave > 1) No way to make sure no one is cheating and not voting a > bunch of times. Developers are put into the developer group on the board. Thus, only registered developers can vote. This will stop people from registering 50 different logins and altering the vote, which could not be controlled if everyone was allowed to vote. > 2) I don't think everyone voting is educated well enough on > the topic. This is also very true. Core design decisions cannot be made by people who do not have a deep knowledge of the subject. Opening up voting to everyone could possibly generate in bad results > In the case coding questions like the macros vote we recently had, I > didnt vote. Me either. I didn't fully understand the repercussions, therefore my vote should not effect the outcome. > In the > case of a PC, I just dont think that a user that reads the message > boards or the general mailing list will have enough info and feel for > who should and shouldnt be a PC. In both cases people with > education on > the topic will probably outnumber those who do know about it, > and might > skew things very badly. This is just one of many examples. Another one would be the recent discussions between Alex and Emmanuelle about splitting win32 the subsystem. This isn't a decision that people not working with the code should be making .... consider the users who come into the forums asking what version of Linux ReactOS is based on. Should they be allowed to sway this decision. To stop any animosity of users towards devs, the votes could be made hidden. However I don't think this is a requirement as I think the majority of users would understand the position on voting. It would also be interesting for users to see the voting results, and how ReactOS is developing. If there is a vote where the users input is needed, then it can obviously be placed in another section where the users have write access. This was demonstrated recently when Alex Ionescu started the poll on feature importance. 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

7 7

Re: [ros-diffs] [cwittich] 18611: fix compile with msvc
by Alex Ionescu 19 Oct '05

19 Oct '05

cwittich(a)svn.reactos.com wrote: >fix compile with msvc > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/lib/aclui/precomp.h* > >--- trunk/reactos/lib/aclui/precomp.h 2005-10-19 21:46:17 UTC (rev 18610) >+++ trunk/reactos/lib/aclui/precomp.h 2005-10-19 21:46:30 UTC (rev 18611) >@@ -5,7 +5,9 @@ > > #include <prsht.h> > #include <aclui.h> > #include <sddl.h> > > >+#if defined (__GNUC__) > > > #include <winternl.h> > > >+#endif > > > #include <ntsecapi.h> > #if SUPPORT_UXTHEME > #include <uxtheme.h> > > These changes are really wrong! HEADERS have nothing to do with the compiler! The HEADERS have to be fixed...you're just building with mingw headers and msvc, and assuming the errors are because of msvc, but if you'll try compiling with PSDK (or vice-versa), then these changes make no sense at all. Best regards, Alex Ionescu

2 1

Voting system
by Murphy, Ged (Bolton) 19 Oct '05

19 Oct '05

This seems to have died a death again, so I'm going to bring it back up. So far we have 2 viable options for the new voting system: 1. Have a new section in the forums where only the developer group has write access. Conduct all votes in there using the forums built-in voting system and posting mechanism for comments Vote results are stored in the database and everything is handled by the software All votes are anonymous / private and each developer has only one vote. 2. Design our own voting system and integrate it into the website. This will be controlled via the global login system and all devs will have access to initiate, vote and comment on votes. Vote results need to be stored in a database and everything should handled by the software All votes are anonymous / private and each developer has only one vote. Any comments or additions? ************************************************************************ 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

5 5

Re: [ros-svn] [cwittich] 18582: fixed compile problems with msvc 2003/2005
by Filip Navara 19 Oct '05

19 Oct '05

cwittich(a)svn.reactos.com wrote: >fixed compile problems with msvc 2003/2005 > > >Updated files: >trunk/reactos/subsys/system/msconfig/msconfig.c >trunk/reactos/subsys/system/msconfig/srvpage.c >trunk/reactos/subsys/system/msconfig/toolspage.c > > > This and r18583 breaks PCH support for GCC. - Filip

2 1

RE: [ros-dev] Voting system
by Murphy, Ged (Bolton) 19 Oct '05

19 Oct '05

Magnus Olsen wrote: > if we doing 2 we need write code for it. That's what I was thinking. By using the forums, we are adopting something which has already been implemented and has been tried and tested by millions. It seems like a good place to start. We can always move it into the website if the need ever arises, and someone ever finds the time to code 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

2 1

Release Candidate, Test coordinator, ...
by Martin Fuchs 18 Oct '05

18 Oct '05

OK, there have been a few misunderstandings, which lead to the current problems and all this partly quite angry discussions. Let's go on and see what to do now. I recommend the following steps: 1.) Fix the console bug in question, and put a new tested release candidate on the web. 2.) update the release procedure (http://www.reactos.org/wiki/index.php/Release_Management_Overview) to include the test coordinator Of course this includes a discussion about the new content on the mailing list. 3.) make an official vote for the test coordinator and new release procedure. And Alex - I hope your break period will not last too long. Regards, Martin

4 5

Break, PC, Constituion and other misc issues
by Steven Edwards 18 Oct '05

18 Oct '05

Hi, I have been away from my computer for most of the past week and will be away for another week but wanted to weigh in on some outstanding issues. 1. I like the draft constituion Casper has ripped from Debian. 2. I nominate Casper to the Project Cordinator Position (I would like the job but I have personal issues going on right now that may keep me busy for the next year or so) 3. I think the PC job should be for a 1 year term with no more than 2 consecutive terms. I don't like the idea of re-electing someone over and over again even if they are doing a good job. How do we know if someone could do a even better job? Don't bother replying directly to me unless you just want to share comments with others. I might not reply for a while. I would like to have votes for these issues as soon as possible. Thanks Steven __________________________________ Yahoo! Music Unlimited Access over 1 million songs. Try it free. http://music.yahoo.com/unlimited/

4 6

Endianness
by Bart Grantham 18 Oct '05

18 Oct '05

Sorry to barge onto the list with what may be an offtopic post, but I am very curious about how married ReactOS is to little-endianness. Is there something intrinsic about how Windows is architected that would prevent ReactOS from being ported to a big-endian platform? I noticed that the inital work on the PPC port was done with the CPU in little-endian mode. Was this for convenience or was this a technical decision? Definitely not an important topic but if someone could satisfy my curiousity, I'd be grateful. Thanks, Bart

4 3

RE: [ros-dev] Constitution
by Murphy, Ged (Bolton) 17 Oct '05

17 Oct '05

Ge van Geldorp wrote: > > > From: Murphy, Ged (Bolton) > > > > Another quick point to say that using the voting facility on > > the board would remove the issue of giving a 'project > > secretary' power in a secret vote. The software would control > > that ..... And software doesn't lie or cheat :) > > But the database administrator (i.e.: me) could... You're just moving the > power from the project secretary to the dba. > But you would have to manually edit the database and everyone would immediately notice the change as the results are updated in real-time for everyone to see. In that respect, although the DBA has the power to change it as they see fit, it would be very silly to do so. There will always be some level at which the results could be changed. If we had a secretary, some could break into their computer and alter the results, or they could be bribed. I think we have to accept this and draw a line at what we consider an acceptable, reliable and trustworthy control system. I think using the forums is the best way of removing the power of controlling the votes from everyone. I know you can be trusted not to alter the database, in the same way I can be trusted not to break into the database and alter it myself. Using the forum voting system also removes any form of human error. > > In the way the phpbb forums voting works, each voter will > > only ever be able to make 1 vote, even if they have multiple > > usernames, as only 1 of those usernames will be in the > > 'developer' group. > > > > You can even go as far as making the forum hidden from > > everyone not in the developer group ..... Although I think > > this is wrong, and should be read only to everyone else. > > But every other developer still gets to see my vote I think? Doesn't sound > like a true secret ballot. Although everyone can see the vote status, it's not possible to see who voted for a particular option. It's only evident that 'someone' has voted. You could even go as far as setting your board preferences so that your name is not shown as being online when you logon. This will give complete anonymity. 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

4 3

RE: [ros-dev] Constitution
by Murphy, Ged (Bolton) 17 Oct '05

17 Oct '05

Ge van Geldorp wrote: > > [CSH] We haven't done secret elections before. I could go > > either way. If it's secret then you put a lot of power into > > one person, the person that collects the votes (most likely > > the Project Secretary). What procedure would you suggest? > > No, we haven't done this before, and I didn't like it... > How about the Project Secretary nominates a neutral vote counter (can be > anyone, Registered or Unregistered, including the Project Secretary himself) > which all the candidates have to affirm? Can be done in private emails > between Project Secretary and candidates. That should ensure the neutrality. > Another quick point to say that using the voting facility on the board would remove the issue of giving a 'project secretary' power in a secret vote. The software would control that ..... And software doesn't lie or cheat :) In the way the phpbb forums voting works, each voter will only ever be able to make 1 vote, even if they have multiple usernames, as only 1 of those usernames will be in the 'developer' group. You can even go as far as making the forum hidden from everyone not in the developer group ..... Although I think this is wrong, and should be read only to everyone else. Ged. -----Original Message----- From: Murphy, Ged (Bolton) [mailto:MurphyG@cmpbatteries.co.uk] Sent: 17 October 2005 09:48 To: 'ReactOS Development List' Subject: RE: [ros-dev] Constitution This sounds reasonable. Phpbb can use the feature whereby only a set group can post in a certain section of the forum, in this case, the developer group in the voting section. This also gives the added bonus of being a secret ballot, as Ge requested. Comments can be made without polluting the topic, and the results can be written to the wiki. -----Original Message----- From: Freworld [mailto:michael@freeworld.net] Sent: 17 October 2005 09:19 To: ReactOS Development List Subject: Re: [ros-dev] Constitution Perhaps we should vote on the website rather than on the mailinglist? The mailinglist could be used for the discussion about what exactly the vote will be and to make the vote public with a link (most people don't look at the website but at the mailinglist). With the new login system it would be no problem to control that only committers can vote. This way we would have a clean overlook what decisions were taken and what was decided exactly. If there is an interest in this I would implement it into the website. Greetings Michael ************************************************************************ 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

3 2

UI related bugs (IMO) that need followup.
by WaxDragon 17 Oct '05

17 Oct '05

This is mostly directed at mindflayer (mf). Looking over the BZ database for 0.2.8, there are several bugs I would like the UI team to look over, followup, or investigate. 448 - Message Box Icons http://www.reactos.org/bugzilla/show_bug.cgi?id=448 449 - File Format Icons http://www.reactos.org/bugzilla/show_bug.cgi?id=449 642 - Hotkeys not supported. http://www.reactos.org/bugzilla/show_bug.cgi?id=642 691 - ReactOS Explorer needs a configurable menu delay. http://www.reactos.org/bugzilla/show_bug.cgi?id=691 692 - Taskbar buttons are not centered in taskbar. http://www.reactos.org/bugzilla/show_bug.cgi?id=692 843 - The focus rectangle is sometimes on the wrong button http://www.reactos.org/bugzilla/show_bug.cgi?id=843 855 - Cannot sort by column in Task Manager http://www.reactos.org/bugzilla/show_bug.cgi?id=855 903- Detect 640x480 and adjust the resolution automatically http://www.reactos.org/bugzilla/show_bug.cgi?id=903 904 - Start, Search, search.. does nothing visible, please add messagebox http://www.reactos.org/bugzilla/show_bug.cgi?id=904 905 - Need mouse speed adjustment in mouse control panel. http://www.reactos.org/bugzilla/show_bug.cgi?id=905 906- There is a blank control panel icon, please label. http://www.reactos.org/bugzilla/show_bug.cgi?id=906 There are others, but this is a start. I don't necessarily want the UI team to code fixes, but rather provide input and try to motivate fixes. Thanks, WD -- <arty> don't question it ... it's clearly an optimization

2 1

Release process
by Ge van Geldorp 17 Oct '05

17 Oct '05

I'm trying to keep this as non-personal and technical as possible. I did include names, most people will guess the names anyway. Yesterday, Robert announced on the IRC channel that he had put RC1 on SourceForge. Immediately, some people jumped on him, demanding to know why he did that without the approval of the Testing Coordinator. This surprised me very much. Not only do we all of a sudden have a TC (I'm not the only one surprised about that: http://www.reactos.org/pipermail/ros-dev/2005-October/005250.html), but it seems that the TC has veto powers over publishing as well. Please don't get me wrong, I think Andrew (WaxDragon) is doing a great job with the testing (much of the increased stability can be attributed to better testing), and I certainly would have voted for him if such a vote had taken place. But that's the problem: Alex put a page on the Wiki (http://www.reactos.org/wiki/index.php/ReactOS_Testing_Coordinator) and appointed Andrew as TC. In my book, that makes him Alex' testing coordinator, not the ReactOS project testing coordinator. Naming Andrew TC is only a minor problem as far as I'm concerned, after all, he's the right guy for the job, the only problem is the procedure followed. I do have a major problem with the role definition as presented on the Wiki though. I want to focus on "The TC can decide as his will which bugs to promote to Blocker status (thereby blocking a new release)" for now. This is simply unacceptable to me. End of 2003, beginning of 2004 we've had a long discussion about the release process. In the end, general concencus was reached on the text presented here: http://www.reactos.org/wiki/index.php/Release_Management_Overview. There was no formal vote, since we didn't do those at that time, but at the time it was very clear that everyone agreed to it. As far as I know, no ammendments to this document have been approved, so it still stands as a valid, agreed-upon process for the ReactOS project. (To make it absolutely clear: the TC Wiki page is just some text that someone wrote, it does not have the same status.) If you feel that the Release Management Overview is not up to date or otherwise needs to be changed, draft an amendment and put it to vote. Until that happens, we're all bound by the current version. At the time, we agreed we should do time-based releases, a new release every two months. Basically it would be a snapshot of the tree at that time, much like the Wine project does with its monthly releases. After branching a RC1 would be put out. Period. No mention of "we put out a RC1 when all blocker bugs have been fixed and the TC has approved the release". On the contrary, the reason to put out a RC1 was to find as much bugs as possible and hopefully fix them before the final release. The idea behind the time-based releases is "release early, release often" (see the famous Cathedral/Bazaar article, http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/), you release even if you know about some bugs. So, do I think we shouldn't have "blocker" bugs at all? Let me put it this way: if none of the 30 devs feel a bug is important enough to be fixed in the feature freeze period before a release, I do question the severity of the bug. The time-based releases started to go wrong at the end of last year. 0.3 seemed around the corner at that moment, so we decided to postpone the release a bit (we did that before with the 0.2 release, which worked out ok). But now, one thing lead to another, and we completely forgot about the release schedule. I was very pleased to see we were picking up the schedule again, with 0.2.8 being released 2-3 months after 0.2.7. I feel very strongly that we should continue this, go back to the original plan of making snapshot releases every two months. Of course, we should try to stabilize the releases as much as possible, but I would like to remind everyone of this quote from the Wine release announcements, which applies to us equally well: "This is still a developers only release. There are many bugs and unimplemented features. Most applications still do not work correctly.". A final word of support for Robert: He did EXACTLY what he was supposed to do by placing RC1 on SourceForge and I completely back him on his decision. Gé van Geldorp.

10 16

RE: [ros-dev] Prelude to voting for the Testing Coordinator Roles andResponsibilities.
by Murphy, Ged (Bolton) 17 Oct '05

17 Oct '05

Ge van Geldorp wrote: > > Yes, that is what RC1 is for. It is supposed to be made immediately after > branching, when entering feature freeze. It's status is basically no more > than that of a random svn version. Perhaps "RC1" is a misnomer. <snip> > Perhaps we should call > it "FF" (Feature Freeze) instead and rename RC2 to "CF" (Code Freeze)? My understanding of RC in the software world is a Release Candidate, meaning we have removed every bug we could find and we think this software is now ready for release. Therefore I think RC gives out the wrong impression and should not be used. Code Freeze or Preview Release sounds good to me. > > However, I have decided to no longer > > continue as TC, if I was even TC to start with. > > I am really sorry to hear this and hope you will reconsider. I also hope you will reconsider. IMO, the assignment of a TC has proven to be one of the most successful ideas I've seen since I started following the project. The work you have done so far has been fantastic and I would like to see it continue. 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

3 2

Coordinators
by Rick Langschultz 17 Oct '05

17 Oct '05

There has been a great deal of talk lately about coordinators. In my opinion there should be: kernel coordinator - controls the development of the kernel. device driver coordinator - makes sure device drivers are written and code managed. network coordinator - makes sure networking is complete before 0.3.0 or other release. User interface coordinator - enables the UI is stable and allows users to get a great ReactOS experience. testing coordinator - this team will test reactos on various hardware bits. They will keep a log of what hardware bits work and those that need support - for instance on Virtual PC (latest Mac OS X) enabling USB support makes ReactOS crash. A list of that hardware needs to be supported -- eventually. release coordinator - Once a release is scheduled this team makes sure releases are released on time. web coordinator - this team managers the web aspects of ReactOS. This team is pretty much complete. and IRC coordinator - this coordinator will keep logs of what has been discussed on the IRC channels. A daily list of main topics will be available on the wiki. This will keep developers up to speed on what is happening on IRC if they are away, or if someone has a quick message for other teams. These are suggested teams. Each team should have a coordinator and keep a log of information for each team. The coordinators should be able to communicate with other coordinators of other teams. Once weekly they should have a personal chat on IRC or email discussing the next release or feature addition. This is the way my company operates and it is very efficient. Rick Langschultz rlangschultz(a)cox.net (Home) rlangschultz(a)ellemaespa.com (Work) rlangschultz(a)email.uophx.edu (School)

3 3

ReactOS Development Coordinator
by Jason Filby 17 Oct '05

17 Oct '05

Hi all Before anyone else slips this through (I kid, I kid!), I would like us to move to vote on a ReactOS Development Coordinator. Before we vote, anyone that wants to run, please step up. The DC would really have the responsibility of facilitating developers. I don't know if we already have a page on this, but I would say this means helping other developers reach their potential in contributing to ReactOS through development. This also entails facilitating communication within the team and with other teams (testing, UI, translation). I'd like some discussion on this thread as to the role of the DC to prevent future confusion. Regards Jason

7 8

RE: suggestion to close (was Re: [ros-dev] Prelude to voting for the Testing Coordinator Roles andResponsibilities.)
by Murphy, Ged (Bolton) 17 Oct '05

17 Oct '05

I like and agree with all 4 of your suggestions. -----Original Message----- From: Royce Mitchell III [mailto:royce3@ev1.net] Sent: 17 October 2005 13:32 To: ReactOS Development List Subject: suggestion to close (was Re: [ros-dev] Prelude to voting for the Testing Coordinator Roles andResponsibilities.) Here's a combination of various suggestions to hopefully begin to close this matter: 1) Go with Gé's suggestion and rename our candidates to x.x.x-FF and x.x.x-CF respectively. 2) TC has no power to block FF - doesn't make sense to do so. 3) TC has power to block CF, subject to be overruled by a vote should a majority feel it is not critical enough. 4) No matter which way we enter CF, it takes an informal vote on the ML to drop back to FF for major discovered bugs - but any single developer can request and be granted a formal vote. Andrew, would you still be willing to run for TC and continue the absolutely fantastic work you've done there given these, assuming everybody would agree to them? ************************************************************************ 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

Prelude to voting for the Testing Coordinator Roles and Responsibilities.
by WaxDragon 17 Oct '05

17 Oct '05

Hello everyone. I think there is alot of time and energy being wasted regarding the Testing Coordinator role, and it's responsibilities. First the responsibilites need to be solidified. When I started acting in the TC role, this was the outline I was shown by Alex, and agreed to perform: http://www.reactos.org/wiki/index.php/ReactOS_Testing_Coordinator I am pretty pleased with the description, and have managed to balace performing these responsibilities with having a real life, wife and child included. Seems everyone agrees I am doing acceptably. I've tried to review the stability of ReactOS about once a week, since it takes about 4 to 5 solid hours to build debug and release builds, install them, load test applications and check out regressions, bugs, and newly working features. I've tried to keep the bugzilla database up to date, and filled with "Good Bugs", and I even wrote up a wiki article on how to do so. http://www.reactos.org/wiki/index.php/File_Bugs. I have tried to steer people away from reporting bugs in the IRC channel and the forums. I am usually available on IRC, and occationally surf the forums for bug reports and reminders. The last part of the obligations of the TC is the working applicaitons list, and when Alex and I discussed this, he came up with the example listed, but it was understood that the format of list was flexible. This is sort of what the "State of the Repository" emails have been about. I am collecting notes on a testing method than can be applied by our more inclined users, and a way to integrate a "testing database" that can show the status of apps using reports submitted by users or a testing team. I am also working on updating the parts of the wiki that involves testing in some manner, including building the source (and setting up the environment), using virtual machines to test, debugging, filing bugs and so on.. Please review and discuss. I would like to have the vote as soon as possible. Thanks for everyone's support, WD -- <arty> don't question it ... it's clearly an optimization

7 11

RE: [ros-dev] Constitution
by Murphy, Ged (Bolton) 17 Oct '05

17 Oct '05

Freworld wrote wrote: > If the forum is not the form you like I could include another form of > website voting. You could also peculate voting mails on the mailing > list. This project stands on a certain factor of trust. I personally think we should open up a new section in the forums entitled 'Voting' Everyone with commit access should be placed in the 'developer' group and the developer group should be given write access to this section. Polls should be made using the built in voting system. Should the 'voting' section should be made read only, or invisible to other users? Results should be posted onto the wiki > Perhaps we should make a vote which voting system is preferred? :) Although ironic, I think this is the only way. We will need a few more suggestions first of how the voting system should work. 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-dev] Constitution
by Murphy, Ged (Bolton) 17 Oct '05

17 Oct '05

This sounds reasonable. Phpbb can use the feature whereby only a set group can post in a certain section of the forum, in this case, the developer group in the voting section. This also gives the added bonus of being a secret ballot, as Ge requested. Comments can be made without polluting the topic, and the results can be written to the wiki. -----Original Message----- From: Freworld [mailto:michael@freeworld.net] Sent: 17 October 2005 09:19 To: ReactOS Development List Subject: Re: [ros-dev] Constitution Perhaps we should vote on the website rather than on the mailinglist? The mailinglist could be used for the discussion about what exactly the vote will be and to make the vote public with a link (most people don't look at the website but at the mailinglist). With the new login system it would be no problem to control that only committers can vote. This way we would have a clean overlook what decisions were taken and what was decided exactly. If there is an interest in this I would implement it into the website. Greetings Michael Casper Hornstrup wrote: > > >>-----Original Message----- >>From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Ge van Geldorp >>Sent: 16. oktober 2005 23:56 >>To: 'ReactOS Development List' >>Subject: RE: [ros-dev] Constitution >> >>Looks good. A few comments: >> >>The Registered Project Members can (by General Resolution) override any >>decision made by the Project Coordinator or the Area Coordinators. However, >>the Repository Coordinator and Project Secretary can make decisions >>"preferably consistent with the consensus of the Project Members". It seems >>to me that Registered Project Members should be able to override their >>decisions too. >> >> > >[CSH] Right. How about changing: >* Override any decision made by the Project Coordinator or Area Coordinator. >* Appoint or dismiss the Project Coordinator or Area Coordinator. > >to >* Override any decision made by the Project Secretary or any Coordinator. >* Appoint or dismiss the Project Secretary or any Coordinator. > > > >>There is a mandatory 1 week discussion period and 1 week voting period for >>each vote, with no escape clause. For some votes (whether to release or not >>comes to mind) 2 weeks seems a bit long. Can we change it so that the >>proposer can ask for shorter periods, with a safeguard that the shorter >>periods will be denied if a single Registered Project Member objects? >> >> > >[CSH] I thought of having a "quick vote" for decisions which are needed here >and now (like whether or not to release now) and not necessarily need to be >documented anywhere else than the mailing lists for future reference, but how >would you define the two? >Maybe we could allow the Registered Project Member that calls for the vote to >choose any number of days of voting period less than 7 days, but at least 2? >days and no discussion period? Any Registered Project Member already has the >right to demand a revote at any time (maybe there should be some protection >from abuse of that right? One could spam until he/she gets what he/she wants). > > > >>I really would like Coordinator Elections to be secret (or private, not sure >>what the correct English term is). I should be able to cast my vote without >>the candidates knowing on who (or even if) I voted. I believe this should be >>explicitly mentioned in the Coordinator Elections voting procedure. >> >>Ge van Geldorp. >> >> >[CSH] We haven't done secret elections before. I could go either way. If it's >secret then you put a lot of power into one person, the person that collects >the votes (most likely the Project Secretary). What procedure would you suggest? > >Casper > >_______________________________________________ >Ros-dev mailing list >Ros-dev(a)reactos.org >http://www.reactos.org/mailman/listinfo/ros-dev > > > > _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev ************************************************************************ 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

Team work
by Lucio Diaz 17 Oct '05

17 Oct '05

Jason Filby wrote: Message: 5 Date: Sun, 16 Oct 2005 09:04:49 -0600 From: Jason Filby <jason.filby(a)gmail.com> Subject: Re: [ros-dev] Break To: ReactOS Development List <ros-dev(a)reactos.org> Message-ID: <e7a1591e0510160804q74f7424fy1e8a6b53ff39d4b0(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 That doesn't seem to tie in with people leaving if they're not told that they are right. Regards Jason On 10/15/05, Royce Mitchell III <royce3(a)ev1.net> wrote: > Would you be so kind as to at least commit your work-in-progress code to > a branch, please? > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------ Message: 6 Date: Sun, 16 Oct 2005 09:06:56 -0600 From: Jason Filby <jason.filby(a)gmail.com> Subject: Re: [ros-dev] Break To: ReactOS Development List <ros-dev(a)reactos.org> Message-ID: <e7a1591e0510160806jf1ddb50le7e3154168a23a(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 On 10/15/05, James Tabor <jimtabor(a)adsl-64-217-116-74.dsl.hstntx.swbell.net> wrote: > TC was voted for and I consider it closed business. Wax has the job deal > with it! Mostly on IRC! That's not the way we've agreed to do things. > I'm not against you. Just because some of us miss the Memo does not make them right! Well excuse me. > Before anyone complains, they should open their minds and read what Alex > has to say. Right, and Alex is a great listener. Jason ----------------------------------- I am not a developer, but i am an adult man, with some experience with team working and have been reading this mailing list since the begining, and what can i say? First: I have seen Alex Ionescu apologicing, often, so yes, drop IRONY, Alex is a great listener, and NO! it is not easy to find people who would apologice nowadays. Second: I saw the loss of focus in this proyect for a long time, with the largely delayed 0.3.0, and it have being people like Alex, Filip, Ge, Waxdragon, Tabor... who took the torch and carried the proyect for a full year. Third: I have seen Alex Ionescu as the one in the center of all discusions, and he could be fast to answer, but he proved to be as fast to apologice, and that i have not seen from some other developers. Four: It IS NORMAL, to have discussions where you are working in such a big proyect, not everyone can have the same vision of a whole OS, but what have NO sense, is to harass people for doing their work well, just cause there is not a F* paper about their "election". Fith: I thought this was an open source project, so people commit if they want, if they dont they dont, period. Harassing people wont grow the developer base. I have been following this proyect before 0.2 was released, i even submited some documentation and i wonder if i have been wasting my time. Sorry if i look a bit angry, but i AM a bit angry as i see several good developers force to leave for this kind of avoidable situations even if i can not (but wish) help with code. Good luck, Lucio Diaz-Flores Varela. ______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es

3 2

Change of Project Coordinator
by Jason Filby 17 Oct '05

17 Oct '05

Hi all I've decided that now is the best time to step down as Project Coordinator. The process to vote for a new PC will be - as previously decided for this type of decision - that only registered committers can vote. Regards Jason PS - I've cc'd the developers on leave as to not exclude anyone

4 5

OK, Time for a few words..
by TwoTailedFox 16 Oct '05

16 Oct '05

I've seen quite a few users propose ideas, such as a new GUI, or new functionality, only to be told it doesn't fit in with the Core Goal of ReactOS. ReactOS is all about creating a Win32-compatible Operating System. Now, later on, when the Kernel is sufficiently developed, we can do what Linux does, and create "Distributions". I had a look at the KDE/Ros Thread, and noted that a version of that, and GNOME may well be available for Windows next year. If the UI Team chooses to Grow, you can offer, for example mind you, a Core ReactOS System, with Windows Classic, and one or more "Distributions", with a different GUI, such as KDE or GNOME. Same goes for ReactOS in different 'roles'. Offering versions aimed at Workstations, Servers, or even for Educational/Testing use, would be feasible down the line. Just my 0.02c -- "I had a handle on life, but then it broke"

1 0

New ReactOS Newsletter. Now Live on ReactOS.org
by TwoTailedFox 16 Oct '05

16 Oct '05

Hello All. Just sending out an announcement that Issue 1 of the new ReactOS Weekly Newsletter is now available for viewing on http://www.reactos.org Thanks to GvG for showing me the internals of RosCMS, Bac9 on #reactos for helping with validation checks, and dnordenberg, again on #reactos, for offering to help with the Newsletter in the form of an XML-Based back-end, to come soon. -- "I had a handle on life, but then it broke"

1 0

Alex.
by Lucio Diaz 16 Oct '05

16 Oct '05

Alex Ionescu wrote: Hi, Since it seems Emanuele has not made a post about this yet, maybe I should... I have been informed that due to time and focus reasons, Emanuele has decided to leave the project for an indeterminate time (forever?). I wish him the best of luck, and I thank him for his contributions to ReactOS. I have also talked to Filip lately, and I have understood from him that he will also be gone for the next month or two. Finally, in light of recent events, I feel that it's also best if I follow the example and take a break as well. I was undecided before, but the recent fight over the TC has convinced me that maybe this isn't the best place or time for me to apply my knowledge. I'm bit sick of being always the one in the middle of a fight. First I was blamed for always breaking the tree or causing incompatibilities, and now I'm blamed for project decisions as well. I really have too many things to worry about in life then to spend my life fighting all the time. I don't care that there are 40 people on IRC that agree with me, but when Jason and Ge, which are the two most influencial members of this project seem to be set against me, then I don't want to cause any more trouble. Best regards, Alex Ionescu ------------------------------------------ After being reading this mailing list for over a year i can really understand Alex, Period. Lucio Diaz-Flores Varela. ______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es

1 0

Break
by Alex Ionescu 16 Oct '05

16 Oct '05

Hi, Since it seems Emanuele has not made a post about this yet, maybe I should... I have been informed that due to time and focus reasons, Emanuele has decided to leave the project for an indeterminate time (forever?). I wish him the best of luck, and I thank him for his contributions to ReactOS. I have also talked to Filip lately, and I have understood from him that he will also be gone for the next month or two. Finally, in light of recent events, I feel that it's also best if I follow the example and take a break as well. I was undecided before, but the recent fight over the TC has convinced me that maybe this isn't the best place or time for me to apply my knowledge. I'm bit sick of being always the one in the middle of a fight. First I was blamed for always breaking the tree or causing incompatibilities, and now I'm blamed for project decisions as well. I really have too many things to worry about in life then to spend my life fighting all the time. I don't care that there are 40 people on IRC that agree with me, but when Jason and Ge, which are the two most influencial members of this project seem to be set against me, then I don't want to cause any more trouble. Best regards, Alex Ionescu

8 14

Ros boot failure - r 18469
by Gge 16 Oct '05

16 Oct '05

Hi, Ros installs successfuly from BootCD ( r 18469) but then at start Ros bugchecks . Any idea ? (ntoskrnl\ldr\loader.c:876) Loading Module \SystemRoot\system32\drivers\npfs.sys... (ntoskrnl\ldr\loader.c:879) Module \SystemRoot\system32\drivers\npfs.sys loaded at 0x9d120000. (ntoskrnl\ke\i386\exp.c:1306) Unhandled UserMode exception, terminating thread KeBugCheckEx at ntoskrnl\ex\init.c:716 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. Technical information: *** STOP: 0x00000071 (0x00000001,0x00000000,0x00000000,0x00000000) Frames: <ntoskrnl.exe:2615 (ntoskrnl/ke/bug.c:479 (KeBugCheckEx))> <ntoskrnl.exe:bea8a (ntoskrnl/ex/init.c:716 (ExpInitializeExecutive))> <ntoskrnl.exe:6806 (ntoskrnl/ke/main.c:100 (KiSystemStartup))> <ntoskrnl.exe:bc854 (ntoskrnl/ke/main.c:294 (_main))> <ntoskrnl.exe:104b ({standard input}:47 (_text_start__))> KeBugCheckWithTf at ntoskrnl\ke\i386\exp.c:1236 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,0x800a2d47,0x00000000,0x1f000000) *** ntoskrnl.exe - Address 0x800a2d47 base at 0x80000000, DateStamp 0x0 Regards Gge

1 0

Installing ReactOS 0.2.8 on vmware 5.5 beta
by Saravanan Jayakumar 16 Oct '05

16 Oct '05

Hi, Can anyone please let me know how to run React 0.2.8 RC1 on VMware 5.5 Beta.When i run it on vmware its asking to install certain vmwarre tools, i guess its the graphics driver.Then vmware complains that the driver is not found for this OS and i dont see anything on the screen. regards Jay

5 7

Gudie Lines for SVN Write access
by Magnus Olsen 16 Oct '05

16 Oct '05

Hi I should love to see some new gudieles how to get svn access. Today it seam anyone that provide with a patch that is coder can getting svn access. But I think we need start think how we should handle it, Here is some ideas how it can be 1. A maling list with patch or in Bugzila I love see a maling list with the patch 2. When people have submit the patch to us we start examing it see if it any godd (we are doning that already) 3. To get SVN write access u need lest provide patch in regual basic under 6 month lest, Then after 6 month the provider can write to mailing list see if can getting SVN write access before he grant SVN write access, the full name and mailing address must be provided, and we should have a vote if that provder can getting SVN write access. no accpect from all this rules. Yestday some was granted svn access his name was not on the mailing list why he got one, he did not write either on the mailing list asking for svn access that why I want see new guide lines how svn write access handles. so every one know how he is and why he was granted to be granted after few patcher are not accpect in my eys. For we are starting getting alot with people with svn write access. And new guide lines must be create. BestReagds Magnus Olsen

7 8

MM and CM architecture
by Saravanan Jayakumar 16 Oct '05

16 Oct '05

Hi, I am new to React-OS but following the project for quite sometime. I would like to know how the memory managemnet and cache manger works in React OS.Isit similar to NT?.If anyone can let me know the arcitecture of these two components in ReactOS, it would be helpful for me to follow the code.Youcould also give me a few pointers as of where to start of in the code for MM and CM so that i could dissect the flow. regards Jay

2 1

Re: [ros-diffs] [gvg] 18468: Make sure we don't hang forever when activating a window belonging to
by Gunnar Dalsnes 16 Oct '05

16 Oct '05

gvg(a)svn.reactos.com wrote: > > - co_IntSendMessage(Window->hSelf, WM_WINDOWPOSCHANGING, 0, (LPARAM) WinPos); > > + co_IntPostOrSendMessage(Window->hSelf, WM_WINDOWPOSCHANGING, 0, (LPARAM) WinPos); > I think the whole co_IntPostOrSendMessage function is wrong and crazy. Who made it? Sending and posting messages are completely different things. I think something like co_IntSendMessageTimeout should be used instead, but i dont think its implemented yet. G.

3 3

Via 8233 Sound Install
by James Tabor 16 Oct '05

16 Oct '05

Hi! From running Setup in the via8233 directory. http://www.qdigrp.com/qdisite/eng/support/d_downloadcd.htm http://www.qdigrp.com/qdisite/driver/utility/sound/Via8233.zip (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (lib/ntdll/ldr/utils.c:2072) Relocating (76160000 -> 6e0000) C:\ReactOS\system32 \comctl32.dll (lib/ntdll/ldr/utils.c:2072) Relocating (777d0000 -> 782000) C:\ReactOS\system32 \winmm.dll (lib/ntdll/ldr/utils.c:2072) Relocating (76260000 -> 7db000) C:\ReactOS\system32 \oleaut32.dll (lib/ntdll/ldr/utils.c:2072) Relocating (77a90000 -> 4b1000) C:\ReactOS\system32 \VERSION.dll (lib/comctl32/theming.c:138) Could not re-register class L"#32770": 57 FIXME: CopyImage doesn't support IMAGE_ICON correctly! (lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find mxdMessage (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'msacm.drv' (Status c0000135) (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'midimap.dr v' (Status c0000135) (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 1240000) C:\DOCUME~1\ADMINI ~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_ISTMP0.DIR\193e5.DLL (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'C:\DOCUME~ 1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_ISTMP0.DIR\_ISUSER.DLL' (Status c00001 35) (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 1263000) C:\DOCUME~1\ADMINI ~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_WUTL951.DLL (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! WARNING: ModifyMenuA at lib/user32/windows/menu.c:4327 is UNIMPLEMENTED! WARNING: ModifyMenuA at lib/user32/windows/menu.c:4327 is UNIMPLEMENTED! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 4c1000) C:\DOCUME~1\ADMINI~ 1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_ISTMP0.DIR\v32audio.dll (lib/setupapi/devinst.c:1818) : flag DIGCF_PRESENT ignored Unhandled exception ExceptionCode: c0000005 Faulting Address: 0 Address: 7c9250bc C:\ReactOS\system32\ntdll.dll CS:EIP 1b:7c9250bc DS 23 ES 23 FS 3b GS 0 EAX: 005df4a0 EBX: 7ffdf000 ECX: 7668543c EDX: 00000000 EBP: 005df4a4 ESI: 00000000 ESP: 005df498 EDI: 00696120 EFLAGS: 00010202 Frames: 76660000+5ccc C:\ReactOS\System32\SETUPAPI.DLL 76660000+6ba9 C:\ReactOS\System32\SETUPAPI.DLL 76660000+55fc C:\ReactOS\System32\SETUPAPI.DLL 76660000+540c C:\ReactOS\System32\SETUPAPI.DLL 4c1000+1452 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_ISTMP 0.DIR\v32audio.dll 400000+fff8 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 400000+10b29 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 400000+16912 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 400000+16bff C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 400000+10e60 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 400000+113ad C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 400000+76b77 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55 76._MP 7c800000+31255 C:\ReactOS\system32\KERNEL32.dll (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! (subsys/win32k/ntuser/class.c:125) Failed to lookup class atom! The linux sound system does work. Thanks, James

3 4

ReactOS build fallen over
by Wesley Parish 16 Oct '05

16 Oct '05

I started compiling ReactOS 0.2.7 on my Linux box uname -a Linux localhost 2.6.3-7mdk #1 Wed Mar 17 15:56:42 CET 2004 i686 Celeron (Coppermine) unknown GNU/Linux This was the result. I'm using i586-mingw32mscv-*. Now my question is, in which file do I find the elusive (PREFIX)? Because I can't find it in Makefile. [wparish@localhost reactos027]$ make [MKDIR] obj-i386/tools [MKDIR] obj-i386/tools/rbuild [MKDIR] obj-i386/tools/rbuild/backend [MKDIR] obj-i386/tools/rbuild/backend/mingw [CC] tools/rbuild/backend/mingw/mingw.cpp [CC] tools/rbuild/backend/mingw/modulehandler.cpp [CC] tools/rbuild/backend/mingw/proxymakefile.cpp [MKDIR] obj-i386/tools/rbuild/backend/devcpp [CC] tools/rbuild/backend/devcpp/devcpp.cpp [CC] tools/rbuild/backend/backend.cpp [CC] tools/rbuild/automaticdependency.cpp [CC] tools/rbuild/bootstrap.cpp [CC] tools/rbuild/cdfile.cpp [CC] tools/rbuild/compilerflag.cpp [CC] tools/rbuild/configuration.cpp [CC] tools/rbuild/define.cpp [CC] tools/rbuild/exception.cpp [CC] tools/rbuild/filesupportcode.cpp [CC] tools/rbuild/include.cpp [CC] tools/rbuild/installfile.cpp [CC] tools/rbuild/linkerflag.cpp [CC] tools/rbuild/module.cpp [CC] tools/rbuild/project.cpp [CC] tools/rbuild/ssprintf.cpp [CC] tools/rbuild/stubbedcomponent.cpp [CC] tools/rbuild/testsupportcode.cpp [CC] tools/rbuild/wineresource.cpp [CC] tools/rbuild/XML.cpp [CC] tools/rbuild/rbuild.cpp [MKDIR] output-i386/tools [MKDIR] output-i386/tools/rbuild [LD] output-i386/tools/rbuild/rbuild [MKDIR] obj-i386/tools/bin2res [CC] tools/bin2res/bin2res.c [CC] tools/bin2res/mkstemps.c [MKDIR] output-i386/tools/bin2res [LD] output-i386/tools/bin2res/bin2res [MKDIR] obj-i386/tools/buildno [CC] tools/buildno/buildno.cpp [CC] tools/buildno/exception.cpp [CC] tools/buildno/ssprintf.cpp [CC] tools/buildno/XML.cpp [MKDIR] output-i386/tools/buildno [LD] output-i386/tools/buildno/buildno [BUILDNO] include/reactos/buildno.h [MKDIR] obj-i386/tools/wmc [CC] tools/wmc/getopt.c [CC] tools/wmc/lang.c [CC] tools/wmc/mcl.c [CC] tools/wmc/utils.c [CC] tools/wmc/wmc.c [CC] tools/wmc/write.c [CC] tools/wmc/y_tab.c [CC] tools/wmc/misc.c [MKDIR] output-i386/tools/wmc [LD] output-i386/tools/wmc/wmc [WMC] include/reactos/bugcodes.h [WMC] include/reactos/errcodes.h [MKDIR] obj-i386/tools/nci [CC] tools/nci/ncitool.c [MKDIR] output-i386/tools/nci [LD] output-i386/tools/nci/nci [NCI] ntoskrnl/include/internal/napi.h [MKDIR] obj-i386/tools/gendib [CC] tools/gendib/gendib.c [MKDIR] output-i386/tools/gendib [LD] output-i386/tools/gendib/gendib [GENDIB] subsys/win32k/dib/dib16gen.c [RBUILD] makefile.auto Reading build files...done Detecting compiler...not detected Detecting netwide assembler...detected (nasm) Detecting compiler -pipe support...not detected Detecting compiler pre-compiled header support...not detected Processing modules...done Creating directories...done Unpacking WINE resources...done Generating test support code...done Generating proxy makefiles...done Checking automatic dependencies...done [DLLTOOL] obj-i386/lib/kernel32/libkernel32.a make: mingw32-dlltool: Command not found make: *** [obj-i386/lib/kernel32/libkernel32.a] Error 127 [wparish@localhost reactos027]$ -- Clinersterton beademung, with all of love - RIP James Blish ----- Mau e ki, he aha te mea nui? You ask, what is the most important thing? Maku e ki, he tangata, he tangata, he tangata. I reply, it is people, it is people, it is people.

2 2

Re: [ros-diffs] [hbirr] 18481: Don't use alloca in a macro, which may be used in a loop. This does fix bug #805.
by Gunnar Dalsnes 15 Oct '05

15 Oct '05

This is not the right fix... I will revert these changes when i come up with a proper fix. I also dont understand how this can fix bug 805 (eternal loop in thread windows cleanup routine). Even with your changes the eternal loop is still there, it just doesnt run out of stack? G. hbirr(a)svn.reactos.com wrote: > Don't use alloca in a macro, which may be used in a loop. This does fix bug #805. >

2 1

file copy during install
by Hartmut Birr 15 Oct '05

15 Oct '05

Hi, during install, I see the following two lines: (lib\setupapi\queue.c:1441) copy error 2 L"C:\\ReactOS\\inf\\ne2000.sys" -> L"C:\\ReactOS\\System32\\drivers\\ne2000.sys" (lib\setupapi\queue.c:1441) copy error 2 L"C:\\ReactOS\\inf\\pci.sys" -> L"C:\\ReactOS\\System32\\drivers\\pci.sys" Why does ROS try to copy drivers from the inf directory? - Hartmut

2 1

0.2.8 Branch
by Brandon Turner 15 Oct '05

15 Oct '05

After switching too DBG = 0 i get the following error: [WRC] obj-i386\apps\utils\net\tcpsvcs\quotes.coff [WRC] obj-i386\apps\utils\net\tcpsvcs\tcpsvcs.coff [LD] output-i386\apps\utils\net\tcpsvcs\tcpsvcs.exe [RSYM] output-i386\apps\utils\net\tcpsvcs\tcpsvcs.exe [CC] apps\utils\net\telnet\src\ansiprsr.cpp [CC] apps\utils\net\telnet\src\keytrans.cpp C:/RosBE/bin/../lib/gcc/mingw32/3.4.4/../../../../include/c++/3.4.4/bits/stl_uni nitialized.h: In member function `void std::vector<_Tp, _Alloc>::reserve(size_t) [with _Tp = KeyMap, _Alloc = std::allocator<KeyMap>]': C:/RosBE/bin/../lib/gcc/mingw32/3.4.4/../../../../include/c++/3.4.4/bits/stl_uni nitialized.h:82: warning: '__cur' might be used uninitialized in this function mingw32-make: *** [obj-i386\apps\utils\net\telnet\src\keytrans.o] Error 1 Do i need to update anything? Brandon

3 3

Winsock 2.2 Status
by Alex Ionescu 15 Oct '05

15 Oct '05

Hi, As many of you know, I've been working on Winsock for the last 3 weeks, then lost all my work. I have finished writing everything that I had lost and did some serious tests with MIRC. I want to update Ged, Waxdragon, Ge, Magnus and the others which were interested in a status report. MIRC uses some serious features, including asyncronous hostname lookups, which is an extremly complex part of ws2_32.dll. After fixing about 20 bugs (let me add a small note here: Microsoft has done some SERIOUSLY amazing work with MSVC 2005. The latest RC1 is now even faster, since the internal build system was updated and now supports multi-threaded compiles: ws2_32 takes me 2.5 seconds (officially timed) to compile AND link AND rc with full optimizations + pdb generated... not only did fast rebuild times help out during testing, but the integrated debugger just keeps getting better too. Finding those 20 bugs was extremly easy), I was able to connect to MIRC by using /server irc.freenode.net and join the channels, identify and talk normally. DCC transfer worked as well. Almost all of the ws2_32 APIs were being called, and both TCP and UDP (from dnsapi) communication seemed to work fine. In other words, mirc was fully usable with my ws2_32.dll My next test app is firefox. As of now, it loads fine but hangs at 100% cpu usage. I'm guessing it must be another small bug causing an inifite loop somewhere. Since it's 4AM now, I'll go sleep and check it out tomorrow. Best regards, Alex Ionescu

2 1

Re: [ros-svn] [hbirr] 18481: Don't use alloca in a macro, which may be used in a loop. This does fix bug #805.
by Royce Mitchell III 15 Oct '05

15 Oct '05

hbirr(a)svn.reactos.com wrote: >Don't use alloca in a macro, which may be used in a loop. This does fix bug #805. > > > >Updated files: >trunk/reactos/subsys/win32k/include/object.h >trunk/reactos/subsys/win32k/ntuser/accelerator.c >trunk/reactos/subsys/win32k/ntuser/caret.c >trunk/reactos/subsys/win32k/ntuser/class.c >trunk/reactos/subsys/win32k/ntuser/focus.c >trunk/reactos/subsys/win32k/ntuser/message.c >trunk/reactos/subsys/win32k/ntuser/misc.c >trunk/reactos/subsys/win32k/ntuser/msgqueue.c >trunk/reactos/subsys/win32k/ntuser/painting.c >trunk/reactos/subsys/win32k/ntuser/scrollbar.c >trunk/reactos/subsys/win32k/ntuser/vis.c >trunk/reactos/subsys/win32k/ntuser/window.c >trunk/reactos/subsys/win32k/ntuser/winpos.c >trunk/reactos/subsys/win32k/objects/color.c > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.org >http://www.reactos.org/mailman/listinfo/ros-svn > >. > > > I think this fix should be applied to 0.2.8

1 0

Re: [ros-svn] [greatlrd] 18471: Japanese translation by tsk email tsk_n@mail.goo.ne.jp
by Thomas Weidenmueller 15 Oct '05

15 Oct '05

greatlrd(a)svn.reactos.com wrote: > Added files: > trunk/reactos/lib/msi/msi_Ja.rc > trunk/reactos/lib/oleaut32/oleaut32_Ja.rc > trunk/reactos/lib/shdocvw/Ja.rc > > Updated files: > trunk/reactos/lib/comctl32/comctl_Ja.rc > trunk/reactos/lib/comdlg32/cdlg_Ja.rc > trunk/reactos/lib/mpr/mpr_Ja.rc > trunk/reactos/lib/msacm/msacm_Ja.rc > trunk/reactos/lib/msi/msi.rc > trunk/reactos/lib/oleaut32/oleaut32.rc > trunk/reactos/lib/oledlg/oledlg_Ja.rc > trunk/reactos/lib/setupapi/Ja.rc > trunk/reactos/lib/shdocvw/shdocvw.rc > trunk/reactos/lib/shell32/shell32_Ja.rc > trunk/reactos/lib/shlwapi/shlwapi_Ja.rc > trunk/reactos/lib/wininet/wininet_Ja.rc > trunk/reactos/lib/winmm/winmm_Ja.rc I hope you're also going to submit all these changes to winehq... - Thomas

1 0

Reactos 0.2.8 RC-1 is out
by Robert Köpferl 15 Oct '05

15 Oct '05

You can find a new version on SF.NET Initial network support and some more complex apps as firefox respectively seamonkey seem to work. Against to what I wrote, there's no additional app included in this RC. I try to include some in the qemu variant for the next RC. And for the intermediate time I question you to download the RC1 and try it out, PLUS report bugs into our nice bugzilla!

6 5

Re: [ros-svn] [greatlrd] 18464: Fixing directx headers from wine, by adding alot of missing struct and some struct was wrong. Complete the header dmemmgr.h it was missing and move stuff into that header.
by Alex Ionescu 15 Oct '05

15 Oct '05

greatlrd(a)svn.reactos.com wrote: >Fixing directx headers from wine, by adding alot of missing struct and some struct was wrong. Complete the header dmemmgr.h it was missing and move stuff into that header. > > >Added files: >trunk/reactos/w32api/include/ddk/dmemmgr.h > >Updated files: >trunk/reactos/w32api/include/ddk/ddrawi.h >trunk/reactos/w32api/include/ddk/ddrawint.h >trunk/reactos/w32api/include/ddk/dvp.h > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.org >http://www.reactos.org/mailman/listinfo/ros-svn > > > This breaks the build. Best regards, Alex Ionescu

2 1

RE: [ros-dev] Winsock 2.2 Status
by Murphy, Ged (Bolton) 15 Oct '05

15 Oct '05

Fantastic news Alex! Can't wait to get hold of it and read through it, and put it through some tests. It's all about the networking with me ;) -----Original Message----- From: Alex Ionescu [mailto:ionucu@videotron.ca] Sent: 15 October 2005 09:06 To: ReactOS Development List Subject: [ros-dev] Winsock 2.2 Status Hi, As many of you know, I've been working on Winsock for the last 3 weeks, then lost all my work. I have finished writing everything that I had lost and did some serious tests with MIRC. I want to update Ged, Waxdragon, Ge, Magnus and the others which were interested in a status report. MIRC uses some serious features, including asyncronous hostname lookups, which is an extremly complex part of ws2_32.dll. After fixing about 20 bugs (let me add a small note here: Microsoft has done some SERIOUSLY amazing work with MSVC 2005. The latest RC1 is now even faster, since the internal build system was updated and now supports multi-threaded compiles: ws2_32 takes me 2.5 seconds (officially timed) to compile AND link AND rc with full optimizations + pdb generated... not only did fast rebuild times help out during testing, but the integrated debugger just keeps getting better too. Finding those 20 bugs was extremly easy), I was able to connect to MIRC by using /server irc.freenode.net and join the channels, identify and talk normally. DCC transfer worked as well. Almost all of the ws2_32 APIs were being called, and both TCP and UDP (from dnsapi) communication seemed to work fine. In other words, mirc was fully usable with my ws2_32.dll My next test app is firefox. As of now, it loads fine but hangs at 100% cpu usage. I'm guessing it must be another small bug causing an inifite loop somewhere. Since it's 4AM now, I'll go sleep and check it out tomorrow. Best regards, Alex Ionescu _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev ************************************************************************ 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] [hpoussin] 18453: Remove entries that are created by netcfgx.dll
by James Tabor 15 Oct '05

15 Oct '05

hpoussin(a)svn.reactos.com wrote: > Remove entries that are created by netcfgx.dll > > > Updated files: > trunk/reactos/bootdata/hivesys.inf > Hi! Will we need to add entries in hivesys for ROS Ne2K pci (2) driver? Currently the driver loads but ROS dhclient does not work. All my other dhclient systems, Win98-2 and XP work. Thanks, James Notes: I have two net cards installed. 1) VIA VT6102 Rhine II Fast Ethernet Controller rev. 116, Irq 11, IO 0xe800 [0xe8ff], mem 0xde001000 [0xde001fff], W2k driver not tested yet. 2) RealTek RTL-8029, IO 0xd000, Irq 11 Ne2K-pci, using ROS ne2000.sys. My hivesys.inf setup. This works very well. ; NIC drivers are like any other drivers - but no card-specific info here. ; Comment the networking stuff out if you don't have the card and don't want to see errors ; NE2000 NIC driver HKLM,"SYSTEM\CurrentControlSet\Services\Ne2000","ErrorControl",0x00010001,0x00000001 HKLM,"SYSTEM\CurrentControlSet\Services\Ne2000","Group",0x00000000,"NDIS" HKLM,"SYSTEM\CurrentControlSet\Services\Ne2000","ImagePath",0x00020000,"system32\drivers\ne2000.sys" HKLM,"SYSTEM\CurrentControlSet\Services\Ne2000","Start",0x00010001,0x00000003 HKLM,"SYSTEM\CurrentControlSet\Services\Ne2000","Type",0x00010001,0x00000001 HKLM,"SYSTEM\CurrentControlSet\Services\Ne2000","Route",0x00000000,"Ne20001" ; Configuration Entries for the NE2000 Adapter HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","Characteristics",0x00010001,0x00000000 HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","DriverDesc",0x00000000,"Ne2000" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","ProviderName",0x00000000,"Provider Name(from Inffile)" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","NetCfgInstanceId",0x00000000,"{RANDOMCFGGUIDFOR_NE20001}" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001\Linkage","Export",0x00000000,"\Device\Ne20001" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001\Linkage","RootDevice",0x00000000,"Ne20001" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001\Linkage","UpperBind",0x00000000,"Tcpip" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","Port",0x00000000,"D000" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","Irq",0x00000000,"B" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","NetworkAddress",0x00000000,"001122334455" HKLM,"SYSTEM\CurrentControlSet\Services\Ne20001\Parameters\Tcpip","DefaultGateway",0x00010000,"10.65.145.1" HKLM,"SYSTEM\CurrentControlSet\Services\Ne20001\Parameters\Tcpip","IPAddress",0x00010000,"10.65.145.79" HKLM,"SYSTEM\CurrentControlSet\Services\Ne20001\Parameters\Tcpip","SubnetMask",0x00010000,"255.255.255.0" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","BusType",0x00000000,"5" ;This is from the Registry from Windows 2000 HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","SlotNumber",0x00000000,"11" HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001","BusNumber",0x00000000,"0" ;And this i get from the BIOS bootscreen.

2 1

FreeWin95
by Emanuele Aliberti 14 Oct '05

14 Oct '05

I just want to warn you are going to build FreeWin95 with WDM support. -- :Emanuele Aliberti

20 53

RE: [ros-dev] A call for 0.2.8 (Pic of Mozilla)
by Murphy, Ged (Bolton) 14 Oct '05

14 Oct '05

On Fri, 14 Oct 2005 11:50, Richard Campbell wrote: > Murphy, Ged (Bolton) wrote: > >Richard Campbell wrote: > >>But how WELL does mozilla work with it? Well enough we could include it > >>with 0.2.8? > > > >No, it's still full of bugs. > >Mozilla won't be included anyway, it's a 3rd party app. > > > >Ged. > > Normally i'd take this hardline stance on 3rd party apps, but if we say, > ship firefox with ReactOS 0.3, we'd raise a lot of eyebrows. Suddenly > this puny operating system that crashes all the time and isn't > compatible with much of anything is running several complex, everyday apps. Actually, come to this of it, you make a fair point. I'm dead against having application code in the trunk, as I'm sure everyone else is. However shipping a few 'enhancements' with the prebuilt release builds can only help with much needed publicity. (assuming they meet licensing demands). They can always be dropped as we get closer to the 1.0 build (where I think user choice should take precedence via the package manager) WaxDragon mentioned including some of our apps like Solitaire with 0.2.8. Although everyone seemed to like the idea, we don't have a definitive answer yet. Are we going ahead with this one? 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

7 6

FW: Klemens Friedl (frik 85)
by Ge van Geldorp 14 Oct '05

14 Oct '05

As requested: > From: nadja friedl <nadja.fiedl(a)gmx.at> > Sent: Friday, October 14, 2005 18:45 > > Hello! > I am the sister of Klemens! > He is since the 3rd. Oct. at the Austrian army and since the > 7th. Oct. ill. > So he is not allowed to come home and he has no possibility > to surf the net! > Are there any news about reactOS? > Please tell the others of my brothers illnes! > He hopes that he could come home next week! > > If you want to reply write to my email adresse and I' ll tell > him the things!

1 0

Re: [ros-diffs] [hpoussin] 18442: Don't always return STATUS_BUFFER_TOO_SMALL when an error occurs in ZwQueryValueKey.
by Alex Ionescu 14 Oct '05

14 Oct '05

hpoussin(a)svn.reactos.com wrote: >Don't always return STATUS_BUFFER_TOO_SMALL when an error occurs in ZwQueryValueKey. >The "if" was triggered because ValueInformation->DataLength is 0xcdcdcdcd at the return of the function > But that means that the memory was freed during the failure, so now the ExFreePool will run into a double-free! >Modified: trunk/reactos/ntoskrnl/io/pnpmgr.c > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/ntoskrnl/io/pnpmgr.c* > >--- trunk/reactos/ntoskrnl/io/pnpmgr.c 2005-10-14 13:00:18 UTC (rev 18441) >+++ trunk/reactos/ntoskrnl/io/pnpmgr.c 2005-10-14 13:04:11 UTC (rev 18442) >@@ -322,15 +322,18 @@ > > *ResultLength = ValueInformation->DataLength; > ZwClose(KeyHandle); > > > >- if (ValueInformation->DataLength > BufferLength) >- Status = STATUS_BUFFER_TOO_SMALL; >- > > > if (!NT_SUCCESS(Status)) > { > ExFreePool(ValueInformation); > return Status; > } > > > >+ if (ValueInformation->DataLength > BufferLength) >+ { >+ ExFreePool(ValueInformation); >+ return STATUS_BUFFER_TOO_SMALL; >+ } >+ > > > /* FIXME: Verify the value (NULL-terminated, correct format). */ > > RtlCopyMemory(PropertyBuffer, ValueInformation->Data, > > Please check this out in more detail... Best regards, Alex Ionescu

1 0

RE: [ros-dev] A call for 0.2.8 (Pic of Mozilla)
by Murphy, Ged (Bolton) 14 Oct '05

14 Oct '05

Richard Campbell wrote: > But how WELL does mozilla work with it? Well enough we could include it > with 0.2.8? > No, it's still full of bugs. Mozilla won't be included anyway, it's a 3rd party app. 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

3 2

Re: [ros-svn] [gdalsnes] 18427: make classes use session wide atom table. should fix bug 899
by Emanuele Aliberti 14 Oct '05

14 Oct '05

Hi Gunnar, gdalsnes(a)svn.reactos.com wrote: >make classes use session wide atom table. should fix bug 899 > > >Added files: >trunk/reactos/subsys/win32k/ntuser/session.c > > What are you plans for managing multiple instances of win32k.sys? -- :Emanuele Aliberti

3 2

termination bug
by Hartmut Birr 13 Oct '05

13 Oct '05

Hi, the termination bug is in co_DestroyThreadWindows. co_DestroyThreadWindows hangs in an endless loop which calls UserRefObjectCo. UserRefObjectCo allocates some bytes from stack with alloca. After some rounds, the kernel stack is eaten up. - Hartmut

1 0

Tenative Blocker list for 0.2.8
by WaxDragon 13 Oct '05

13 Oct '05

I've gone though bugzilla and reviewed most of the bugs, here are the ones that are blockers, might become blockers, or caveats we need to keep in mind. I'm sure we will get some real blockers when we release RC1, but this is a start. 805 - Shutdown issues http://www.reactos.org/bugzilla/show_bug.cgi?id=805 This one MUST be fixed, it affects the default install configuration. 493 - excessive repainting in tree-view controls http://www.reactos.org/bugzilla/show_bug.cgi?id=493 I would really like to see some action on this, it renders regedit near useless, and I've seen this bug in other list style controls. Pegs the CPU. 688 - AllocConsole fails on real hardware due to i8042prt http://www.reactos.org/bugzilla/show_bug.cgi?id=688 This is one of the blockers from 0.2.7 that we shipped with. Is there anything that can be done about this? Can we put some debug info into the debug builds so we can gather information? 703 - ReactOS is a fat big. Minimum mem reqs exceeded. http://www.reactos.org/bugzilla/show_bug.cgi?id=703 This one is partially fixed. 32MB installs fail on vmware due to the speed of the file copy operation. 880 - Some dlls stop display output when starting in CLI http://www.reactos.org/bugzilla/show_bug.cgi?id=880 Not a huge bug that many people see, but this is holding up hpoussin's PnP work. Discuss, WD -- <arty> don't question it ... it's clearly an optimization

1 0

Re: [ros-dev] Font problem on Japanese version of ReactOS
by tsk 13 Oct '05

13 Oct '05

Thank you for telling me that bug. I tried to use outline mplus, which doesn't include bitmap data: http://reactos-j.sourceforge.jp/up/img/083.png and tried to use Mona Font with WaxDragon's freetype.dll: http://reactos-j.sourceforge.jp/up/img/084.png Modified freetype.dll works well! But I think there still exist some bug with font rendering. One of them is a line break. ReactOS automatically insert line feeds at space. But Japanese text doesn't use space basically, so ReactOS can't insert line feeds to proper position. Many screenshots: http://reactos-j.sourceforge.jp/up/img/085.zip > mf suggested one could comment out #define > TT_CONFIG_OPTION_EMBEDDED_BITMAPS in > lib/freetype/include/freetype/config/ftoption.h to DISABLE the SBIT > support. Doing some quick testing, this allows Helmut 12pt to render > "correctly", i.e. readable. This may or may not help with the CJK > font. > > tsk, if you would like to try, I put up a modified freetype.dll at > http://waxdragon.homeip.net/~ford/freetype.dll. Give that one a try > and see if it helps with your fonts. > > WD

2 1

Firefox progress
by Ge van Geldorp 13 Oct '05

13 Oct '05

For a long time we've had problems with firefox hanging during startup. Well, I have some good news, as of r18418 it at least shows its main window, see http://www.reactos.nl/pics/ff1.png There are still lots of other problems, but I'm pretty sure we can fix those too in the next month or so. Gé van Geldorp.

4 4

A call for 0.2.8
by WaxDragon 13 Oct '05

13 Oct '05

I know how most of the devs feel about releases, but I think it's time to branch 0.2.8. After a period of instability, trunk is now showing stability. GvG and Ged reported surprising stability from the LinuxWorld demo builds, I personally had favorable results from my September State of the Repo tests. Last night I was able to build a ReactOS bootcd under r18404, and then take that bootcd and install it under qemu, under ROS! Gunnar's win32k changes have had some time to bake in and seem ok*. There have been approximately 1800 commits since 0.2.7, and I want those changes to get some general use.. I don't want to *release* now, but I want to tag the branch now, and maybe release in two weeks (which would make three months sine 0.2.7). Putting out an RC1 would give the codebase exposure to the general public, who may find problems we as devs overlook. This will also give devs and testers a change to focus on some of the big issues I see at the moment, *like this mysterious hang we see on shutdown. Also, those who wish to move forward can do so, even breaking / destabilising the tree. Giving us two or three weeks for testing release canidates will also allow for the PnP/USB and ws2_32 work to be merged in before the release. WD -- <arty> don't question it ... it's clearly an optimization

15 20

RE: [ros-dev] ReactOS UI Team - Concept, Plan, and: help wanted
by Murphy, Ged (Bolton) 13 Oct '05

13 Oct '05

Rick Langschultz wrote: > I am however writing ports for OpenLDAP, Jabber, Apache 2.0, > Tomcat, MaxDB, Postgresql, and MySQL for reactos, But there are already Win32 ports for most of, if not all of these. > but without > networking and service support my efforts are restricted to windows > 2000. That's not really a restriction. IMO, it's better to develop on Windows, get your program working perfectly and then look at testing it in ReactOS. 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

2 1

ReactOS UI Team - Concept, Plan, and: help wanted
by Aleksey Bragin 13 Oct '05

13 Oct '05

Hi, our UI Team Coordinator - mf - asked me to sent this email on his behalf, because unfortunately mails from his address doesn't reach any mailing-list. Here is the original message: From: mf <mf(a)mufunyo.net> Date: October 6, 2005 1:20:56 AM GMT+04:00 Subject: ReactOS UI Team - Concept, Plan, and: help wanted Greetings ReactOS developers and interested parties! For the unintroduced, I am your humble UI coordinator. In addition, I also made some graphics for the project. -Concept- I am here to remind you of a post that was made in the ReactOS user forum, written by crappish (Mikko Tikkanen). In it the author wrote of the need of a consistent user interface, the need of people that actually have knowledge of such things, and how these people would have to be in charge of enforcing such an interface. They should be familiar with Windows, know how to make things accessible and newbie- friendly, and have enough creativity to improve on existing concepts. In addition to that, there should be someone who represents this team and can interface it with the rest of the project, and make sure everything is the way everyone wants it to be. Now, this representative has been chosen. But there is no team to back him up! -Recruiting- So getting down to business. The UI team is recruiting two kinds of people. Primarily: Programmers who have sufficient knowledge to hack other people's code, even if said code is rooted deeply in system libraries. Skill in writing user interfaces and piecing together dialog resources. No advanced skills beyond that required. This is most important, since developers in this category can get straight to business and get started on improving ReactOS. Secondarily: Interface concept designers who have advanced knowledge of human interfacing, easy access, logical positioning, and the creativity to improve and expand on existing ideas. This is a secondary category because a) right now there is little to do in this respect, b) there are already two (counting Mikko?) of these people in ReactOS, and c) for every 1 concept designer, there can be up to 10 implementing developers. Even more appreciated, would be someone who fits both gloves and can write code AND design interfaces. Sadly, experience proves that these two traits don't usually come together in one person. And! Just as important, though not actively recruited, I welcome icon designers, graphic designers, font designers (that includes you, wierd_w!), sound effect samplers, and programmers willing to implement missing UI features (think of things such as extended cursor/icon support, alpha blitting, runtime freetype configuration, recycle bin functionality, control panel, autorun support, etc), on individual application (mail me at mf(a)mufunyo.net). -Plan- The plan(tm) to kickstart the UI team is as follows: Our first goal will be to make the surface experience of ReactOS familiar. Surface in this context means the things a user will see during and after bootup. This mainly involves modifying explorer; to display a consistent and familiar start menu, and to show a friendly explorer when My Computer or the Explore link is opened. This means making all the surface icons consistent (my task), modifying explorer's interface (the 'programmer' category), and figuring out the best layout for the start menu (the 'designer' category). There is no plan past this first task, because I cannot predict how small or big the team is going to be, what feedback we are going to get, and how fast things will move. And that's it for my first big announcement. I hope this will get some discussion going, and some balls rolling. I would also like to take this opportunity to request a mailing list for the UI team, this should have been set up right after the coordinator vote was over, but it wasn't-- so to whoever's in charge of that, I count on you. Thanks. Please reply to this mail only on the general list or to me in person (if you're not on the list and only get digests), it is only crossposted in ros-dev to get a wider range of attention. Thanks for reading, mf.

9 13

Problem with VMware Workstation 5.5
by Mike Swanson 12 Oct '05

12 Oct '05

for the most part, all is well. However, upon the installation of video drivers using the VMware Tools ISO, ReactOS fails to install the driver. I believe this is simply because of a new directory structure to accomodate both 32-bit and 64-bit Windows operating systems.. 32-bit driver: D:\program files\VMware\VMware Tools\Drivers\video\winnt2k\32Bit 64-bit driver (probably not wanted unless someone's doing a x86_64 port): D:\program files\VMware\VMware Tools\Drivers\video\winnt2k\64Bit -- Mike

1 2

RE: [ros-dev] A call for 0.2.8
by Murphy, Ged (Bolton) 12 Oct '05

12 Oct '05

Wow, there's no flies on you ;) -----Original Message----- From: WaxDragon [mailto:waxdragon@gmail.com] Sent: 12 October 2005 14:43 To: ReactOS Development List Subject: Re: [ros-dev] A call for 0.2.8 I was hoping to get it branched today, do a baseline test and have an RC1 for this weekend. If Brandon does the release, that would help me out. ************************************************************************ 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

7 6

Font problem on Japanese version of ReactOS
by tsk 12 Oct '05

12 Oct '05

I made Japanese version of ReactOS. Following is all that I have done. 1) add jpn.nls to \lib\kernel32\nls\ 2) modify \lib\kernel32\locale_rc.rc 3) add Japanese font to \media\fonts\ 4) add next line to \bootdata\hivesft.inf HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\SysFontSubstitutes","MS UI Gothic",0x0000 0000,"FontName" 5) add next line to \bootdata\packages\reactos.dff media\fonts\FontName.ttf 3 6) modify locale settings at \bootdata\hivesft.inf and hivesys.inf HKCU,"Control Panel\International","Locale",0x00000000,"0411" HKLM,"SYSTEM\CurrentControlSet\Control\NLS\Language","Default",0x00000000,"0411" HKLM,"SYSTEM\CurrentControlSet\Control\NLS\Language","InstallLanguage",0x00000000,"0411" Now please look at these screenshots. http://reactos-j.sourceforge.jp/up/img/081.png http://reactos-j.sourceforge.jp/up/img/082.png The former uses mona http://monafont.sourceforge.net/index-e.html The latter uses mplus http://www.kaoriya.net/#BDFM+ I'm very sad... Is ReactOS able to handle Japanese font properly?

3 3

Re: [ros-svn] [ekohl] 18383: First shot at CreateServiceW. It crashes due to a bug (aka missing feature) in widl. = ROS BUILD FAILED
by Gge 12 Oct '05

12 Oct '05

ekohl(a)svn.reactos.com wrote: > First shot at CreateServiceW. It crashes due to a bug (aka missing feature) in widl. I'm going to fix it as soon as possible. > > > Updated files: > trunk/reactos/include/idl/svcctl.idl > trunk/reactos/lib/advapi32/service/scm.c > trunk/reactos/subsys/system/services/database.c > trunk/reactos/subsys/system/services/rpcserver.c > trunk/reactos/subsys/system/services/services.c > trunk/reactos/subsys/system/services/services.h > Hello, This change brokes Ros - It fails to build with the following errors : [CC] lib\advapi32\service\eventlog.c [CC] lib\advapi32\service\scm.c lib\advapi32\service\scm.c: In function `CreateServiceW': lib\advapi32\service\scm.c:271: warning: implicit declaration of function `ScmrCreateServiceW' mingw32-make: *** [obj-i386\lib\advapi32\service\scm.o] Error 1 R18382 builds fine Regards Gge

4 4

RE: [ros-dev] A call for 0.2.8
by Murphy, Ged (Bolton) 12 Oct '05

12 Oct '05

Robert wrote: > This would still work out with my plans. > I'll be able to do this release. BTW I intended to document and > rbuildify (or the like) the process Can we branch for this sooner rather than later. What about this weekend? ************************************************************************ 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

2 1

Re: [ros-diffs] [gvg] 18410: Terminate the new environment with a NULL pointer
by Gunnar Dalsnes 12 Oct '05

12 Oct '05

There are probably dozens of bugs like that lurking around in crt, exposed by malloc not zeroing memory anymore... gvg(a)svn.reactos.com wrote: > Terminate the new environment with a NULL pointer > > Modified: trunk/reactos/lib/crt/misc/environ.c > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/lib/crt/misc/environ.c* > > --- trunk/reactos/lib/crt/misc/environ.c 2005-10-12 08:38:45 UTC (rev 18409) > +++ trunk/reactos/lib/crt/misc/environ.c 2005-10-12 13:00:34 UTC (rev 18410) > @@ -178,6 +178,7 @@ > > return original_environment; > } > } > > + *newenvptr = NULL; > > > return newenv; > } >

2 1

Idea for a new part in headers of .rc files
by David Hinz 12 Oct '05

12 Oct '05

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

3 3

Re: [ros-dev] ReactOS UI Team - Concept, Plan, and: help wanted
by Maritn "E.T." Misuth 12 Oct '05

12 Oct '05

To my knowledge, it is completely posible to write helper apps in JavaScript to function with XUL. At least as extension modules for apps already using the whole thing. For example I think that ChatZilla extension for mozilla is written that way, in pure JavaScript. But if XUL can be used as a core part of some system's dialog/windows rendering I think it is completely possible to create relatively simple facility to have complete standalone apps in JavaScript. It's a long time since I've played with XUL, but if you have FireFox, you can start to play with it right now, and create for example simple dialogs & windows with radio buttons etc using that language and CSS styles. PS: Yes it was an accindent, I wanted to send the mail to the list, sorry ;).

1 0

RE: [ros-dev] RE: Ros-dev Digest, Vol 14, Issue 25
by Murphy, Ged (Bolton) 12 Oct '05

12 Oct '05

I'm not quite sure what everyone is getting at here. Every file has it's entire history logged, easily accessible through your local tree under the context menu, or through Viewcvs on the web. Changes also go out through the svn mailing list. Any closer queries can me viewed via 'diff'ing to any revision you want. However, it would be easy to write a quick tool to assess local timestamps after svn updates for set file types. This would quickly tell you what has changed without the need for viewing the svn logs. Ged. -----Original Message----- From: David Hinz [mailto:post.center@gmail.com] Sent: 12 October 2005 13:12 To: ReactOS Development List Subject: Re: [ros-dev] RE: Ros-dev Digest, Vol 14, Issue 25 Well, the thing is I wanted to have something that makes it very easy to see, if something has changed since the last time I translated that file. Watching the svn all the time is not that easy than just looking at a number. There could also be a little helper app that scans all .rc files in my language and all en.rcs for revision differences and shows me, where I have to translate something. Then I can look in the svn what actually has been changed. It just makes things easier for translators. Greets, David Hinz ************************************************************************ 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

svn://svn.reactos.org/trunk/windows
by Emanuele Aliberti 11 Oct '05

11 Oct '05

Should I call for a VOTE, or is it OK having a top level module for all Win32 related pieces? Please, comment. Thank you in advance. -- :Emanuele Aliberti

6 11

Re: [ros-diffs] [gdalsnes] 18403: alloc multiple of 16 bytes
by Hartmut Birr 11 Oct '05

11 Oct '05

gdalsnes(a)svn.reactos.com wrote: > alloc multiple of 16 bytes > What was the reason for this change? - Hartmut

2 1

crash in usetup if an allocation size is given for a call to NtCreateFile
by Hartmut Birr 11 Oct '05

11 Oct '05

Hi, I've done some little changes in usetup for optimisation. One thing is the decompressing of files from a cabinet container. If the destination file exist, it is created with the create disposition FILE_OVERWRITE and without a pointer to the allocation size. If I add an allocation size pointer (cabinet.c.diff), usetup does crash after copying of all files and creating the registry. (ntoskrnl\ke\exception.c:94) KiRaiseException (ntoskrnl\ke\i386\exp.c:1306) Unhandled UserMode exception, terminating thread Exception: -1160049408(0) Processor: 0 CS:EIP 1b:12000 ????? cr2 66f924 cr3 56a000 Proc: 8094a1f0 Pid: 5c <smss.exe> Thrd: 80954088 Tid: 60 DS 23 ES 23 FS 3b GS 0 EAX: 00012000 EBX: 00000001 ECX: 0066fc18 EDX: 7c90a479 EBP: 0066ff54 ESI: 00000004 ESP: 807ebd64 EDI: 0066fc28 EFLAGS: 00000216 Frames: <smss.exe:741b> subsys/system/usetup/console.c:660 <smss.exe:19c41> subsys/system/usetup/usetup.c:3321 <smss.exe:1a65e> subsys/system/usetup/usetup.c:3781 <0> The address of the crash has nothing to do with the decompressing of the install files. If I change IoCreateFile file a little bit, that the allocation size pointer isn't read (file.c.diff), usetup didn't crash. Has someone an idea what is wrong? - Hartmut Index: subsys/system/usetup/cabinet.c =================================================================== --- subsys/system/usetup/cabinet.c (Revision 18300) +++ subsys/system/usetup/cabinet.c (Arbeitskopie) @@ -859,6 +859,7 @@ UnicodeString.Buffer = DestName + wcslen( DestName ); UnicodeString.Length = 0; RtlAnsiStringToUnicodeString( &UnicodeString, &AnsiString, FALSE ); + MaxDestFileSize.QuadPart = Search->File->FileSize; /* Create destination file, fail if it already exists */ RtlInitUnicodeString(&UnicodeString, @@ -884,7 +885,7 @@ 0); if (!NT_SUCCESS(NtStatus)) { - DPRINT("NtCreateFile() failed (%S) (%x).\n", DestName, NtStatus); + DPRINT1("NtCreateFile() failed (%S) (%x).\n", DestName, NtStatus); /* If file exists, ask to overwrite file */ if (OverwriteHandler == NULL || OverwriteHandler(Search->File, DestName)) @@ -894,7 +895,7 @@ GENERIC_READ | GENERIC_WRITE | SYNCHRONIZE, &ObjectAttributes, &IoStatusBlock, - NULL, + &MaxDestFileSize, FILE_ATTRIBUTE_NORMAL, 0, FILE_OVERWRITE, @@ -903,7 +904,7 @@ 0); if (!NT_SUCCESS(NtStatus)) { - DPRINT("NtCreateFile() failed 2 (%S) (%x).\n", DestName, NtStatus); + DPRINT1("NtCreateFile() failed 2 (%S) (%x).\n", DestName, NtStatus); return CAB_STATUS_CANNOT_CREATE; } } @@ -913,7 +914,6 @@ return CAB_STATUS_FILE_EXISTS; } } - MaxDestFileSize.QuadPart = Search->File->FileSize; NtStatus = NtCreateSection(&DestFileSection, SECTION_ALL_ACCESS, 0, @@ -964,7 +964,10 @@ } else { +// memcpy(&FileBasic.CreationTime, &FileTime, sizeof(FILETIME)); memcpy(&FileBasic.LastAccessTime, &FileTime, sizeof(FILETIME)); +// memcpy(&FileBasic.LastWriteTime, &FileTime, sizeof(FILETIME)); +// memcpy(&FileBasic.ChangeTime, &FileTime, sizeof(FILETIME)); NtStatus = NtSetInformationFile(DestFile, &IoStatusBlock, @@ -1050,6 +1053,7 @@ Status = CAB_STATUS_SUCCESS; UnmapDestFile: NtUnmapViewOfSection(NtCurrentProcess(), DestFileBuffer); +// NtFlushBuffersFile(DestFile, &IoStatusBlock); CloseDestFileSection: NtClose(DestFileSection); CloseDestFile: Index: ntoskrnl/io/file.c =================================================================== --- ntoskrnl/io/file.c (Revision 18300) +++ ntoskrnl/io/file.c (Arbeitskopie) @@ -787,7 +787,11 @@ sizeof(ULONG)); if(AllocationSize != NULL) { - SafeAllocationSize = ProbeForReadLargeInteger(AllocationSize); + ProbeForRead(AllocationSize, + sizeof(LARGE_INTEGER), + sizeof(ULONG)); + SafeAllocationSize.QuadPart = 0 /* AllocationSize->QuadPart */; +// SafeAllocationSize = ProbeForReadLargeInteger(AllocationSize); } else SafeAllocationSize.QuadPart = 0;

1 0

RE: [ros-svn] [turner] 18402: set to eol-style native ;)
by Casper Hornstrup 11 Oct '05

11 Oct '05

Open C:\Documents and Settings\...\Application Data\Subversion\config. Make sure the following is in there: [miscellany] enable-auto-props = yes [auto-props] *.c = svn:eol-style=native *.h = svn:eol-style=native *.S = svn:eol-style=native *.sh = svn:eol-style=native;svn:executable *.rc = svn:eol-style=native *.mc = svn:eol-style=native *.asm = svn:eol-style=native *.cpp = svn:eol-style=native *.cxx = svn:eol-style=native *.txt = svn:eol-style=native *.xml = svn:eol-style=native *.ini = svn:eol-style=native *.inf = svn:eol-style=native *.def = svn:eol-style=native *.dsp = svn:eol-style=CRLF *.dsw = svn:eol-style=CRLF *.gif = svn:mime-type=image/gif *.png = svn:mime-type=image/png *.jpg = svn:mime-type=image/jpeg *.bmp = svn:mime-type=application/octet-stream *.ico = svn:mime-type=application/octet-stream *.ttf = svn:mime-type=application/octet-stream *.nls = svn:mime-type=application/octet-stream *.mp3 = svn:mime-type=application/octet-stream *.wav = svn:mime-type=application/octet-stream Makefile = svn:eol-style=native DON'T add: * = svn:eol-style=native or Magic Things (TM) will happen ;-) Casper > -----Original Message----- > From: ros-svn-bounces(a)reactos.org [mailto:ros-svn-bounces@reactos.org] On Behalf Of > turner(a)svn.reactos.com > Sent: 10. oktober 2005 21:09 > To: ros-svn(a)reactos.com > Subject: [ros-svn] [turner] 18402: set to eol-style native ;) > > set to eol-style native ;) > > > Updated files: > trunk/reactos/subsys/system/cmd/readme2.txt > > _______________________________________________ > Ros-svn mailing list > Ros-svn(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-svn

4 4

Re: [ros-diffs] [gdalsnes] 18403: alloc multiple of 16 bytes
by Alex Ionescu 11 Oct '05

11 Oct '05

gdalsnes(a)svn.reactos.com wrote: > alloc multiple of 16 bytes > Modified: trunk/reactos/lib/crt/stdlib/malloc.c > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/lib/crt/stdlib/malloc.c* > --- trunk/reactos/lib/crt/stdlib/malloc.c 2005-10-10 19:08:57 UTC (rev 18402) > +++ trunk/reactos/lib/crt/stdlib/malloc.c 2005-10-10 20:18:07 UTC (rev 18403) > @@ -25,6 +25,10 @@ > #include <stdlib.h> > #include <malloc.h> > > > + > +/* fixme: should have this in common header */ > +#define ROUND_UP(a,b) ((a + (b-1)) & ~(b-1)) > helper.s > + > > extern HANDLE hHeap; > > /* > @@ -32,7 +36,7 @@ > > */ > void* malloc(size_t _size) > { > > - return HeapAlloc(hHeap, HEAP_ZERO_MEMORY, _size); > > + return HeapAlloc(hHeap, 0, ROUND_UP(_size, 16)); > > } > > /* > @@ -48,7 +52,7 @@ > > */ > void* calloc(size_t _nmemb, size_t _size) > { > > - return HeapAlloc(hHeap, HEAP_ZERO_MEMORY, _nmemb*_size); > > + return HeapAlloc(hHeap, HEAP_ZERO_MEMORY, ROUND_UP(_nmemb*_size, 16) ); > > } > > /* > @@ -57,8 +61,8 @@ > > void* realloc(void* _ptr, size_t _size) > { > if (!_ptr) > > - return HeapAlloc(hHeap, 0, _size); > - return HeapReAlloc(hHeap, 0, _ptr, _size); > > + return HeapAlloc(hHeap, 0, ROUND_UP(_size, 16)); > + return HeapReAlloc(hHeap, 0, _ptr, ROUND_UP(_size, 16)); > > } > > /* > @@ -66,7 +70,7 @@ > > */ > void* _expand(void* _ptr, size_t _size) > { > > - return HeapReAlloc(hHeap, HEAP_REALLOC_IN_PLACE_ONLY, _ptr, _size); > > + return HeapReAlloc(hHeap, HEAP_REALLOC_IN_PLACE_ONLY, _ptr, ROUND_UP(_size, 16)); > > } > > /* > Ever heard of HEAP_ALIGN_16? Best regards, Alex Ionescu

3 3

Re: [ros-svn] [gdalsnes] 18404: alloc at minimum 16 bytes (spotted by WaxDragon)
by Alex Ionescu 11 Oct '05

11 Oct '05

gdalsnes(a)svn.reactos.com wrote: > alloc at minimum 16 bytes (spotted by WaxDragon) > realloc should free passed mem if new size is 0 > > > Updated files: > trunk/reactos/lib/crt/stdlib/malloc.c > > _______________________________________________ > Ros-svn mailing list > Ros-svn(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-svn > > This fixes the bug in windres, right? Best regards, Alex Ionescu

1 0

RE: 18273: create some start menu entries for notepad, regedit and winefile
by Ge van Geldorp 09 Oct '05

09 Oct '05

> From: mf(a)svn.reactos.com > > create some start menu entries for notepad, regedit and winefile Do we really need/want the winefile link on the desktop? Especially since it is also present in the start menu now. If I recall correctly, the Command Prompt was put on the desktop 'cause at the time it was the only viable way to start programs, I think maybe even the Command Prompt link could go from the desktop now. Gé van Geldorp.

7 9

some thoughts
by D. Hazelton 09 Oct '05

09 Oct '05

I've been thinking about a chat I had with Alex Ionescu about the "userspace driver framework" that MS has put in Windows Vista for a couple of days now. Mostly I was trying to think of how they could create a secure system where the drivers could live outside the kernel and still manage to do the job of providing clean access to the hardware. I was doing this because I am just starting to take a look at the ReactOS code with an eye towards helping on the project. That being the case I decided to see if I could find a spot where I could fit my skills into the project. While I'm more geared towards fixing bugs or filling out places marked "TODO" the thought of userspace drivers - or rather, just the thought that such a system would allow for drivers that could die and not take the system with them - has caught my interest. At the current time the only way I can see this being done is by using the HAL to abstract all hardware and providing an API that, via the HAL, will allow for _AUTHENTICATED_ programs (aka drivers) to register themselves with the kernel and provide access to said devices. The access itself would best be handled by the drivers registering an interface that programs can use to call directly into the driver. This just leaves me with a simple problem to solve - should the interface be a COM/COM+ interface (or it's primitive, since I don't think anyone wants the lag having COM/COM+ in the kernel would cause) or should it be something simpler, like a UFS path ? DRH (if the PGP signature looks bad, the list probably modified the mail)

1 0

Installation Error
by Brandon Turner 08 Oct '05

08 Oct '05

After copying the files over in stage 1 installer i get the error "Failed to create regisrty hives". This is off a clean build i am doing(RosBE), same result when i download a iso from sin. any advice? Brandon

1 1

ping: maximum length value
by Emanuele Aliberti 08 Oct '05

08 Oct '05

NT 5.1/SP2: maximum length = 65500 ROS: maximum length = 65519 -- :Emanuele Aliberti

1 0

VOTE: List loop macros in ntoskrnl?
by Thomas Weidenmueller 08 Oct '05

08 Oct '05

As according to our voting rules, any permanent developer may vote on this for one week as of now. Should the flow control macros for looping double linked lists be allowed in ntoskrnl? [ ] Yes [ ] No More on voting can be found at: http://www.reactos.com/wiki/index.php/Voting

8 12

LinuxWorld report
by Ge van Geldorp 08 Oct '05

08 Oct '05

Just a quick report from LinuxWorld London. We've just finished the first day of the exhibition, lots of interest. What surprised me a bit was that the general awareness about the project was somewhat lower than last year in Frankfurt. I guess that 80-90% of the people we spoke last year had already heard about the project, that percentage was a lot lower here (more around 30%). Another pleasant surprise was the stability of the system. We ran it on an old laptop with a few applications: Quake 1, WinZip, IrfanView, AbiWord. On demand we showed some other apps like regedit, notepad, task manager. The system froze one time when a visitor played around with it, other than that no problems at all. Not a single kernel crash. We had to Tab-K to force a kernel check to show the BSOD to a visitor. I say let's bring out r18189 (I think...) as 0.2.8 (j/k). People were reacting very nicely. It was nice to see them picking up a flyer rather uninterestedly, start to read, and then suddenly turn back to watch the demo when they realized what the project was all about. Ge van Geldorp.

8 11

RE: [ros-svn] [greatlrd] 18318: Sync aginst a older version of wine, fixed GvG patch for so we do not lose poll_mouse, tested in few apps and games in ros and windows. Next sync is againstcurrent version of wine. and it does remove almost whole mypatch for
by Mike Lerwill 08 Oct '05

08 Oct '05

Why has the created file trunk/reactos/lib/dinput/makefile been added to the repo? regards Mike > -----Original Message----- > From: ros-svn-bounces(a)reactos.org [mailto:ros-svn-bounces@reactos.org]On > Behalf Of greatlrd(a)svn.reactos.com > Sent: 08 October 2005 01:22 > To: ros-svn(a)reactos.com > Subject: [ros-svn] [greatlrd] 18318: Sync aginst a older version of > wine,fixed GvG patch for so we do not lose poll_mouse,tested in few apps > and games in ros and windows. Next sync is againstcurrent version of > wine. and it does remove almost whole mypatch for wine > > > Sync aginst a older version of wine, fixed GvG patch for so we do > not lose poll_mouse, tested in few apps and games in ros and > windows. Next sync is against current version of wine. and it > does remove almost whole my patch for wine dinput thx to GvG > implemet userhook for mouse and keyboard in reactos. > > > Added files: > trunk/reactos/lib/dinput/makefile > > Updated files: > trunk/reactos/lib/dinput/Makefile.in > trunk/reactos/lib/dinput/data_formats.c > trunk/reactos/lib/dinput/device.c > trunk/reactos/lib/dinput/dinput.xml > trunk/reactos/lib/dinput/dinput_main.c > trunk/reactos/lib/dinput/dinput_private.h > trunk/reactos/lib/dinput/joystick_linux.c > trunk/reactos/lib/dinput/joystick_linuxinput.c > trunk/reactos/lib/dinput/keyboard.c > trunk/reactos/lib/dinput/mouse.c > > _______________________________________________ > Ros-svn mailing list > Ros-svn(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-svn >

2 1

SYSTEMS approaching
by Robert Köpferl 08 Oct '05

08 Oct '05

Hi, there were some rhumors of us being on SYSTEMS with a booth or part of one. Is this still current and can we present ours somehow? I for my part want to help out on presenting reactos and organize what's needed in my hometown.

2 2

RE: [ros-dev] LinuxWorld report
by Murphy, Ged (Bolton) 08 Oct '05

08 Oct '05

Robert Köpferl wrote > However I'm gogin on a big voyage at 11.11.2005 so I *can* make another > relase (maybe the mentioned 0.2.8) 0.2.8 was a joke. It really needs to be 0.3 next time, and sooner rather than later :) > Thus I would like to find a new release manager to replace > mine -- at least temproary. ( :-/ ) I think WaxDragon would fill this role perfectly, if he's willing. ************************************************************************ 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

Warning in ddk/ddrawint.h
by James Tabor 07 Oct '05

07 Oct '05

[CC] lib/ddraw/main.c In file included from lib/ddraw/rosdraw.h:10, from lib/ddraw/main.c:13: w32api/include/ddk/ddrawint.h:484: warning: parameter names (without types) in function declaration w32api/include/ddk/ddrawint.h:485: warning: parameter names (without types) in function declaration make: *** [obj-i386/lib/ddraw/main.o] Error 1 Thanks, James

2 2

State of the Repository October 6th 2005
by WaxDragon 07 Oct '05

07 Oct '05

The stats: In Sepember, there were: 578 commits 98 bugs opened 94 bugs closed I wasn't able to determine the bugs that weere touched during the last month, since something made *all* bugs appear touched. A little change of format, I will review the closed bugs first, then go over the SVN commits in less detail than last month. *First of all, the new website has been released! This resolved about 10 bugs, many of which were the oldest in Bugzilla. Thanks to everyone involved with the new site, it looks great! * The taskmgr repainting bug was fixed. (583) * ReactOS currently installs with only 32MB. (debug builds too!) (703) ** Reopened, see test results below.. * Freeldr now checks for invalid dates from the BIOS. (716) * The last page of the installer is drawn correctly now. (735) * Many notepad fixes and enhancements. * Floppy support fixed. (753) * Control combos fixed, you can now Ctrl+D in Putty to logout. (763) * Last of the vmwinst.exe bugs fixed, can change resolution now. (764) * ncftp now works. (779) * Various regedit fixes and enhancements. * WinRAR installer works. (785) * vim.exe input works again. (796) Some of the SVN highlights: *Various notepad improvements and fixes. *Various regedit improvements and fixes. *LPC work *NDK work *Sync to Wine-20050830 *More win32k work *New CSR code *More rtl cleanup *0.2.7 was tagged *USB drivers added to bootcd *Ion's 17838 WIP code !!!! *Ntoskrnl header cleanups *"Text" test added to rosperf *Some new winefile icons *The TAB+ debug combos work again *GDB stub fixes *Vaious application leak fixes *Setupapi got alot of work this month *Simple TCP/IP Services added (tcpsvcs) *Simple Device Manager added (devmgr) and the usual pile of build and bug fixes. We also gained two developers this month! Lets welcome Bletch (npwoods) and GedMurphy! Lets start October off with r18248: (Here is the rough draft of the testing list I am using, feedback apriciated) (http://waxdragon.homeip.net/~ford/reactos/ros_regression_items.html) Installation: * Installs under both vmware and qemu hangs under vmware 5 with only 32MB completes first stage installer under qemu with 32MB, crashes on first reboot (see bug 703 for more details) Drivers: * PCNet driver works VMWare * vmx_svga (and vmwinst.exe) work under VMWare * Ne2000 driver works under QEmu * CL54XX video driver works under QEmu * floppy driver appears to work under both VMWare and QEmu * USB drivers (UHCI and usbhub) both load under VMWare5 Applications: (Tested under VMWare5 only) * Abiword 2.2.9 installs; opens, edits and saves files. * Info-ZIP UNZIP 5.42 unzips the OOo 1.1.4 install * OOo 1.1.4 unpacks, and starts to install, but NONE of the text is rendered on the installer pages. I fumbled my way though the installer by memory, and it even completed the file copy, but it appears to hang setting up the registry. I can't tell, no text. ;0) This is progress though. * Firefox has multiple issues still, both install and runtime. * OffByOne installer has issues, but the binaries run and load pages, slow and some issues (win32k?). * The Mozilla ActiveX Control 1.7.12 works with ibrowser, but needs msvcp60.dll to register the dlls. This is different that the 1.6 control. Eventhough, it seems to work a runtime, making ibrowser the best browser canidate. (Still can't type in it though.. bug 876) * dillo gets a UM exception trying to start * lynx 2.8.3 runs, gets hung loading pages occationally, can break out of load. works ok. * mIRC 6.16 installs (shortcut error), and can even connect to freenode by IP. Hopefully, Alex's ws2_32 will fix that. * jbmail installs and connects to my ISP pop3 server *by IP only* * Miranda IM 0.4.0.1 and 0.3.3.1 have multiple issues, both install though. * PuTTY works, still drops chars if you type too fast (really noticeable under debug/qemu). OTOH, I can use the Control+ combos now. I can log out and detach fom screen. * RealVNC viewer suffers from the same crash tcpsvcs does. Gunnar has a patch for this in bugzilla, will followup. * 7za (the commandline stand alone 7-Zip) works well. Shipped Apps (in-tree) * regedit still has the treeview bug, but due to recent work, I can actually create new keys and string values, and I can still import from the command line. You can export subtrees now also. PROGRESSION! * taskmanager has had some bugs fixes recently, but the System Cache setting now reads 0 after fixing it in windows. * Notepad has had alot of improvements, it's looking good. * winemine still doesn't work (black box) * Solitare works, but is still missing the menubar. REGRESSION. * ps works * mc starts * format still does nothing, just hangs * calc *seems* to work. * cat works * ftp works, but still can't tell the difference between ascii and binary transfers. * ncftp has progressed and you can use it for uploads and downloads, the only issue I am aware of is you cannot backspace. * ping works * ipconfig is getting bad data from the OS, but works fine under windows. * finger works * route works, and had some cosmetic improvements * netstat fails loading snmpapi.dll * hostname returns the name you filled in second stage setup now. ;0) * arp does not work, missing some of the plumbing. * telnet works, and seems to buffer input properly. * tcpsvcs crashes upon start up, seems that AfdSelect is setting DPCs will NULL procs. There is a patch from Gunnar (Bug 857) that addresses this, still needs more testing. Hoping to regression test it after this stupid email that has taken me three days. ;0) To end this note, I will point out a few bugs. We are still seeing fatal hangs on shutdown on some configurations. Also, during this testing, I corrupted the registry three times, will need to look into that. All and all, we have made progress. Keep up the good work! WD (If I forgot anything, or you have something to add, please reply to this note) -- <arty> don't question it ... it's clearly an optimization

4 5

RE: [ros-dev] ReactOS 0.3 and magazine deals
by Murphy, Ged (Bolton) 07 Oct '05

07 Oct '05

Here is the original Linux Format article: http://homepage.ntlworld.com/gedmurphy/ReactOS.jpg <http://homepage.ntlworld.com/gedmurphy/ReactOS.jpg> I got it wrong, it was 0.2.4 they featured last time. -----Original Message----- From: Murphy, Ged (Bolton) [mailto:MurphyG@cmpbatteries.co.uk] Sent: 07 October 2005 15:31 To: 'ReactOS Development List' Subject: [ros-dev] ReactOS 0.3 and magazine deals Hi all, As a result of Linux World UK this week, I have 2 popular Linux magazines, Linux Format and Linux User, who are very interested in featuring us in the near future. Linux Format have featured us before, and would like to do a re-visited write-up detailing how far the project has progressed since the last feature, which was 0.2.5 Linux User seemed interested in doing something with one of our developers who is a competent writer, for a full feature. Both magazines would like to wait until the 0.3 release before doing their feature. I need to contact the editors with information and I'm guessing one of the first questions which will be asked is 'when will the 0.3 release be out?' GvG has said he wants to start up on networking, starting with getting Firefox running I will be doing as much as I can on the user mode side along with assisting Gé in any way I can. I know Alex has done a hell of a lot of work on the new WS2_32 and friends, and WaxDragon's relentless testing is highlighting progressions and regressions all the time. So I suppose I have 2 questions here: - Can we consider setting a date to aim for the 0.3 release, so I have something to give to the magazines? It doesn't have to be set in stone, just an incentive to work towards. - Is anyone willing to get involved in relaying / writing information to pass on to Linux User magazine? Also, I think the requirements for the 0.3 release need to be reviewed. It has some features listed that will hold back the release of 0.3 for no good reason <http://www.reactos.org/xhtml/en/about_roadmap.html> http://www.reactos.org/xhtml/en/about_roadmap.html <http://www.reactos.org/wiki/index.php/0.3.x/0.3.0> http://www.reactos.org/wiki/index.php/0.3.x/0.3.0 Lastly, can I coax anyone else into joining the ReactOS network movement ? hehe Thanks for listening :) 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 <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 ************************************************************************ 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

ReactOS 0.3 and magazine deals
by Murphy, Ged (Bolton) 07 Oct '05

07 Oct '05

Hi all, As a result of Linux World UK this week, I have 2 popular Linux magazines, Linux Format and Linux User, who are very interested in featuring us in the near future. Linux Format have featured us before, and would like to do a re-visited write-up detailing how far the project has progressed since the last feature, which was 0.2.5 Linux User seemed interested in doing something with one of our developers who is a competent writer, for a full feature. Both magazines would like to wait until the 0.3 release before doing their feature. I need to contact the editors with information and I'm guessing one of the first questions which will be asked is 'when will the 0.3 release be out?' GvG has said he wants to start up on networking, starting with getting Firefox running I will be doing as much as I can on the user mode side along with assisting Gé in any way I can. I know Alex has done a hell of a lot of work on the new WS2_32 and friends, and WaxDragon's relentless testing is highlighting progressions and regressions all the time. So I suppose I have 2 questions here: - Can we consider setting a date to aim for the 0.3 release, so I have something to give to the magazines? It doesn't have to be set in stone, just an incentive to work towards. - Is anyone willing to get involved in relaying / writing information to pass on to Linux User magazine? Also, I think the requirements for the 0.3 release need to be reviewed. It has some features listed that will hold back the release of 0.3 for no good reason http://www.reactos.org/xhtml/en/about_roadmap.html <http://www.reactos.org/xhtml/en/about_roadmap.html> http://www.reactos.org/wiki/index.php/0.3.x/0.3.0 <http://www.reactos.org/wiki/index.php/0.3.x/0.3.0> Lastly, can I coax anyone else into joining the ReactOS network movement ? hehe Thanks for listening :) 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

Fwd: A new tool to interact with Bugzilla
by Martin Fuchs 07 Oct '05

07 Oct '05

Hi, I downloaded and tried the Deskzilla tool. Quite nifty. :-) But when trying to use it with the ReactOS Bugzilla at http://www.reactos.org/bugzilla/ I have problems to login. Is there some version incompatibility? Using it with Wine's and Castor's Bugzilla works quite well. Regards, Martin ---------- Forwarded message ---------- From: Jonathan Ernst <Jonathan(a)ernstfamily.ch> Date: 06.10.2005 13:01 Subject: A new tool to interact with Bugzilla To: wine-devel(a)winehq.org Cc: wine-users(a)winehq.org Hello, This might solve people's concerns about the difficulty to use/search in bugzilla. You can save queries, make fast search in comments thanks to the local database (use top right search field), etc. Of course I discovered this application right after having triaged some hundreds bugs... http://mozillazine.org/talkback.html?article=7491 Deskzilla 1.0, a desktop client for the Bugzilla bug tracking system. Deskzilla delivers features for greater productivity and an improved working environment for the users of Bugzilla.

3 2

LinuxWorld London, 2nd day
by Ge van Geldorp 07 Oct '05

07 Oct '05

The second day of the show was very much like the first day. Not a single BSOD, my laptop hung twice after visitors played around a little bit. Basically the biggest problem I had was how to prevent loosing my voice, I'm obviously not used to talking as much as we did the these two days. There were some (Linux) magazines showing interest, Ged Murphy has their details. All in all I think it was a worthwile show and I'm looking forward to going to one of these shows again. Ge van Geldorp.

1 0

RE: [ros-dev] State of the Repository October 6th 2005
by Murphy, Ged (Bolton) 07 Oct '05

07 Oct '05

WaxDragon wrote: <snip> > * ftp works, but still can't tell the difference between ascii and > binary transfers. > * ncftp has progressed and you can use it for uploads and downloads, > the only issue I am aware of is you cannot backspace. > * ping works > * ipconfig is getting bad data from the OS, but works fine under windows. > * finger works > * route works, and had some cosmetic improvements > * netstat fails loading snmpapi.dll > * hostname returns the name you filled in second stage setup now. ;0) > * arp does not work, missing some of the plumbing. > * telnet works, and seems to buffer input properly. > * tcpsvcs crashes upon start up, seems that AfdSelect is setting DPCs > will NULL procs. </snip> Just to add a quick note on the other network tool (which isn't on the bootcd): * tracert jumps straight to the destination node as we are not yet able to set TTL values in raw packets, thus we get the default 128. This will be fixed upon implementation of setsockopt(). We also get jibberish when resolving name info. This will be fixed when WS2_32 has getnameinfo() It works as expected in Windows. 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-svn] [weiden] 18302: fixed warnings when compiled with -Wmissing-declarations
by Emanuele Aliberti 07 Oct '05

07 Oct '05

weiden(a)svn.reactos.com wrote: >fixed warnings when compiled with -Wmissing-declarations > > [CC] ntoskrnl\ke\i386\fpu.c [LD] output-i386\ntoskrnl\ntoskrnl.exe [RSYM] output-i386\ntoskrnl\ntoskrnl.exe [CC] subsys\win32k\ntddraw\ddraw.c subsys\win32k\ntddraw\ddraw.c: In function `NtGdiDdGetAvailDriverMemory': subsys\win32k\ntddraw\ddraw.c:387: error: structure has no member named `DdGetAvailDriverMemory' make: *** [obj-i386\subsys\win32k\ntddraw\ddraw.o] Error 1 -- :Emanuele Aliberti

3 2

Re: [ros-svn] [blight] 18292: Huh, what? Oops! Just some stuff which noone cares about...
by Hartmut Birr 07 Oct '05

07 Oct '05

blight(a)svn.reactos.com wrote: >Huh, what? Oops! Just some stuff which noone cares about... > > > >Updated files: >trunk/reactos/ntoskrnl/include/internal/i386/fpu.h >trunk/reactos/ntoskrnl/ke/i386/exp.c >trunk/reactos/ntoskrnl/ke/i386/fpu.c > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.org >http://www.reactos.org/mailman/listinfo/ros-svn > > > Something is wrong in this changes. If I try to install HDD-Health, I get a crash. - Hartmut Assertion (Ke386GetCr0() & X86_CR0_TS) == 0 failed at ntoskrnl\ke\i386\fpu.c:337 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:1c76 (ntoskrnl/ke/bug.c:487 (KeBugCheckEx@20))> <ntoskrnl.exe:1c8d (ntoskrnl/ke/bug.c:503 (KeBugCheck@4))> <ntoskrnl.exe:556b6 (ntoskrnl/ke/i386/fpu.c:337 (KiGetFpuState))> <ntoskrnl.exe:545c1 (ntoskrnl/ke/i386/exp.c:904 (KeTrapFrameToContext@12))> <ntoskrnl.exe:54bab (ntoskrnl/ke/i386/exp.c:1195 (KiDispatchException@20))> <ntoskrnl.exe:577ff (ntoskrnl/ke/i386/usertrap.c:133 (KiUserTrapHandler@12))> <ntoskrnl.exe:5bcc9 (ntoskrnl/mm/i386/pfault.c:132 (KiPageFaultHandler))> <ntoskrnl.exe:57251 ({standard input}:152 (KiTrapProlog2))> <shell32.dll:ad18 (lib/shell32/shell32_main.c:480 (SHGetFileInfoW@20))>

4 9

Developing on ReactOS
by Rick Langschultz 06 Oct '05

06 Oct '05

Hey everyone, I was wondering how well reactos compiles on reactos? And does the standard build tools work. I was also interested in doing some development work on ReactOS using some common GPL-based software. Rick Langschultz rlangschultz(a)cox.net (Home) rlangschultz(a)ellemaespa.com (Work) rlangschultz(a)email.uophx.edu (School)

3 3

reactos\lib\nt\entry_point.c
by Emanuele Aliberti 03 Oct '05

03 Oct '05

There should be a bug in the envp creation. ProcessParameters->Environment is a PWCHAR and envp is a char*. -- :Emanuele Aliberti

1 0

Re: [ros-diffs] [ea] 18230: More fixes to compile.
by Alex Ionescu 03 Oct '05

03 Oct '05

ea(a)svn.reactos.com wrote: >More fixes to compile. > >Modified: trunk/reactos/subsys/csr/csrsrv/api.c >Modified: trunk/reactos/subsys/csr/csrsrv/process.c > > > ------------------------------------------------------------------------ > *Mo* What compiler are you using? My gcc 3.4.4 compiled the files perfectly, so did msvc 2k5 with maximum prefast warnings on. Initializing all those variables to NULL seems an awful waste to me.. Best regards, Alex Ionescu

2 2

RE: [ros-diffs] [ekohl] 18240: - Add german resources.
by Hervé Poussineau 03 Oct '05

03 Oct '05

> Modified: trunk/reactos/lib/cpl/hdwwiz/En.rc >--- trunk/reactos/lib/cpl/hdwwiz/En.rc 2005-10-03 07:48:59 UTC (rev 18239) > +++ trunk/reactos/lib/cpl/hdwwiz/En.rc 2005-10-03 09:14:57 UTC (rev 18240) > @@ -1,4 +1,4 @@ > -LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_US > +LANGUAGE LANG_ENGLISH, SUBLANG_DEFAULT > > STRINGTABLE > BEGIN Why are you changing this? According to http://support.microsoft.com/kb/169483/en-us , English (Neutral) is not always searched by the resource loader, but English (US) is. I don't know exactly what are the rules followed by ReactOS, but English (US) allow the control panel to have correct resources on all Windows versions. > Modified: trunk/reactos/lib/cpl/hdwwiz/Fr.rc > --- trunk/reactos/lib/cpl/hdwwiz/Fr.rc 2005-10-03 07:48:59 UTC (rev 18239) > +++ trunk/reactos/lib/cpl/hdwwiz/Fr.rc 2005-10-03 09:14:57 UTC (rev 18240) > @@ -1,4 +1,4 @@ > > -LANGUAGE LANG_FRENCH, SUBLANG_NEUTRAL > +LANGUAGE LANG_FRENCH, SUBLANG_DEFAULT > > STRINGTABLE > BEGIN According to the same page, Primary Lang/Sub Lang is first searched, followed by Primary Lang/Sublang_neutral. Primany Lang/Sublang_default is not searched. With your changes, French/Canadian and other would not have French resources. Just try it on Windows, and you will see. This change is also in contradiction with changes done in Wine some months ago. (ChangeLog 0.2.7: "From Wine: changed SUBLANG_DEFAULT to SUBLANG_NEUTRAL for LANG_SPANISH in all resources, so that Spanish locales other than Spain also use Spanish resources") Please revert these changes. Hervé

1 0

Re: [ros-diffs] [ea] 18199: - add copyright notice
by Alex Ionescu 03 Oct '05

03 Oct '05

ea(a)svn.reactos.com wrote: >- add copyright noti > Hi, Please don't add these -- we already have the COPYRIGHT: Please see COPYING file at the top-level directory. It is a long overdue janitorial task to remove all the per-file copyright headers, adding more won't help ;) Best regards, Alex Ionescu

3 5

Re: [ros-svn] [ea] 18219: A do-nothing crt0 for native NT processes.
by Alex Ionescu 02 Oct '05

02 Oct '05

ea(a)svn.reactos.com wrote: >A do-nothing crt0 for native NT processes. >(see note by A.Ionescu in reactos/subsys/crt/main.c) > > >Added files: >trunk/reactos/lib/ntrt0lib/ >trunk/reactos/lib/ntrt0lib/args.c >trunk/reactos/lib/ntrt0lib/entry_point.c >trunk/reactos/lib/ntrt0lib/ntrt0.h >trunk/reactos/lib/ntrt0lib/ntrt0lib.xml > >Updated files: >trunk/reactos/lib/directory.xml > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.org >http://www.reactos.org/mailman/listinfo/ros-svn > > > Hi, Thanks, I didn't have time last night ( I went to bed at 5AM). Do you mind if I rename this to "nt" ? It's the official name of the DDK static lib, and would mean that we don't have to have 2 .XML files for anyone using the library (for the msvc build). Anyways, I'm going to commit the code now, I have it on my disk. Best regards, Alex Ionescu

2 3

Re: [ros-svn] [ion] 18183: - KeRundownThread:
by Witukind 02 Oct '05

02 Oct '05

On Sat, 1 Oct 2005 09:50:08 +0200 <ion(a)svn.reactos.com> wrote: >> which means the mutant has been already freed). omfg! we're all going to die!!! ;)

1 0

Re: [ros-svn] [ion] 18202: - Small semaphore code simplification/optimization.
by Hartmut Birr 02 Oct '05

02 Oct '05

ion(a)svn.reactos.com wrote: >- Small semaphore code simplification/optimization. > > >Updated files: >trunk/reactos/ntoskrnl/ke/kthread.c >trunk/reactos/ntoskrnl/ke/sem.c > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.org >http://www.reactos.org/mailman/listinfo/ros-svn > > > Have you tried to compile sem.c before you did commit? - Hartmut

2 1

Plug and Play status - Device installation
by Hervé Poussineau 02 Oct '05

02 Oct '05

Hello, Since some weeks/months, I've done some work in setupapi.dll. I'm now able to install devices using provided .inf files, ie copy needed files and create registry entries. Syntax: rundll32.exe newdev.dll,DevInstall [InstanceID] where InstanceID is something like ACPI\PNP0501\1 or PCI\VEN_8086&DEV_7112&SUBSYS_00000000&REV_01\3&61aaa01&0&3A However, I've still some bugs and some missing features: - OpenSCManagerW freezes ReactOS [1] - CreateServiceW is unimplemented [2] - Service image path provided to CreateServiceW looks like "C:\ReactOS\System32\drivers\driver.sys", instead of "System32\drivers\driver.sys" [3] - You have no way to use a .inf file which is not in ReactOS\Inf directory [4] - Files to be copied are always searched in ReactOS\Inf directory (so they can't be found) [5] - Files to be copied need to be already decompressed (ie not in a .cab file) [6] - A reboot is needed before being able to use the newly installed device [7] - Having multiple times a same device is not supported, if the bus driver can't provide a unique DeviceID [8] - Last, but not least, device installation is not started automatically when a new device is found/plugged [9] [1] See bug #826: http://www.reactos.org/bugzilla/show_bug.cgi?id=826 [2] In lib/advapi32/service/scm.c. It needs to call umpnpmgr.exe by RPC, as in OpenServiceW implementation [3] In lib/setupapi/dirid.c: the value returned by create_system_dirid() is always a full path [4] It's due to missing functionnality in newdev.dll (lib/newdev/*), which should ask the user when no driver is found [5] In lib/setupapi/queue.c. If a file can't be found, SetupCommitFileQueueW should ask the user where to find the file [6] We need to support the [SourceDisksNames] section in .inf files [7] Maybe calling IoInvalidateDeviceRelations() at the end of SetupDiInstallDevice (lib/setupapi/devinst.c) would be enough [8] We need to generate a ParentIdPrefix entry in registry in some(?) cases [9] I suppose it should be initiated by umpnpmgr.exe, when it sees a device for the first time Hervé PS: If someone is interested to work on one of this parts, please answer this email

2 1

Re: [ros-diffs] [weiden] 18213: minor changes (mostly formatting)
by Hartmut Birr 02 Oct '05

02 Oct '05

weiden(a)svn.reactos.com wrote: >minor changes (mostly formatting) > >Modified: trunk/reactos/lib/hid/hid.c >Modified: trunk/reactos/lib/shellext/slayer/slayer.c > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/lib/hid/hid.c* > >--- trunk/reactos/lib/hid/hid.c 2005-10-02 12:27:54 UTC (rev 18212) >+++ trunk/reactos/lib/hid/hid.c 2005-10-02 12:46:49 UTC (rev 18213) >@@ -368,8 +368,8 @@ > > HidD_Hello(OUT PCHAR Buffer, > IN ULONG BufferLength) > { > > >- const PCHAR HelloString = "Hello\n"; >- ULONG StrSize = (lstrlenA(HelloString) + 1) * sizeof(CHAR); > > >+ const CHAR HelloString[] = "Hello\n"; >+ ULONG StrSize = sizeof(HelloString) + sizeof(HelloString[0]); > > > > if(BufferLength > 0) > { > > > ------------------------------------------------------------------------ Hi, sizeof(HelloString) does already contain the terminating NULL. - Hartmut

2 1

Re: [ros-svn] [ion] 18201: - Add RtlSetProcessCritical
by Hartmut Birr 02 Oct '05

02 Oct '05

ion(a)svn.reactos.com wrote: >- Add RtlSetProcessCritical >- Some fixes. > > >Updated files: >trunk/reactos/include/ndk/ketypes.h >trunk/reactos/include/ndk/pstypes.h >trunk/reactos/include/ndk/rtlfuncs.h >trunk/reactos/include/ndk/rtltypes.h >trunk/reactos/include/ndk/umtypes.h > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.org >http://www.reactos.org/mailman/listinfo/ros-svn > > > Hi, the header changes breaks compiling for me: gcc -c boot\freeldr\freeldr\cache\blocklist.c -o .\up\obj-i386\boot\freeldr\freeldr\cache\blocklist.o -nostdlib -ffreestanding -fno-builtin -fno-inline -fno-zero-initialized-in-bss -Os -Iboot\freeldr\freeldr\include -Iboot\freeldr\freeldr\cache -Intoskrnl\include -D__USE_W32API -DDEBUG -Iinclude -Iinclude\reactos -Iinclude\libs -Iinclude\drivers -Iinclude\subsys -Iw32api\include -Iw32api\include\ddk -D_M_IX86 -DDBG -Wall -Os -Wno-strict-aliasing -ftracer -momit-leaf-frame-pointer -mpreferred-stack-boundary=2 -Wpointer-arith -g -pipe In file included from include/ndk/psfuncs.h:13, from include/ndk/ntndk.h:34, from boot/freeldr/freeldr/include/freeldr.h:24, from boot\freeldr\freeldr\cache\blocklist.c:21: include/ndk/pstypes.h:627: error: syntax error before 'PHANDLE_TABLE' include/ndk/pstypes.h:627: warning: no semicolon at end of struct or union include/ndk/pstypes.h:628: warning: type defaults to 'int' in declaration of 'Token' include/ndk/pstypes.h:628: warning: data definition has no type or storage class include/ndk/pstypes.h:655: warning: unnamed struct/union that defines no instances include/ndk/pstypes.h:668: error: syntax error before 'PrefetchTrace' include/ndk/pstypes.h:668: warning: type defaults to 'int' in declaration of 'PrefetchTrace' include/ndk/pstypes.h:668: warning: data definition has no type or storage class include/ndk/pstypes.h:718: warning: unnamed struct/union that defines no instances include/ndk/pstypes.h:730: warning: unnamed struct/union that defines no instances include/ndk/pstypes.h:745: error: syntax error before '}' token include/ndk/pstypes.h:745: warning: type defaults to 'int' in declaration of 'EPROCESS' include/ndk/pstypes.h:745: warning: data definition has no type or storage class _make: *** [.\up\obj-i386\boot\freeldr\freeldr\cache\blocklist.o] Error 1 - Hartmut

1 0

Re: [ros-svn] [ion] 18118: - Some NDK fixes when compiling with PSDK.
by Emanuele Aliberti 02 Oct '05

02 Oct '05

ion(a)svn.reactos.com wrote: >Deleted files: >trunk/reactos/include/subsys/csr/protocol.h >trunk/reactos/subsys/csr/args.c >trunk/reactos/subsys/csr/csr.h >trunk/reactos/subsys/csr/csrsrv/debug.c >trunk/reactos/subsys/csr/csrsrv/dllmain.c > > Well, a bit unfair deleting header files etc. and leaving the subtree not compilable. My working copy depends on those very files. Disabling compilation of csr also forces me to disable the vms module: not a great loss, but we had only two left: os2 and posix are broken. Keeping the whole modules compilable should be a goal, even if they are minimal subsystems (if ROS is just Win32, well, let's rename it back "FreeWin95"). -- :Emanuele Aliberti

2 2

svn: how do I restore a deleted file?
by Emanuele Aliberti 02 Oct '05

02 Oct '05

How do I restore a file deleted at revision xyz? -- :Emanuele Aliberti

2 2

another macro: OPTHDROFFSET
by vit-ros＠att.net 01 Oct '05

01 Oct '05

Hi, I found the OPTHDROFFSET not very useful. I would rather use something lighter like: (PIMAGE_NT_HEADERS)((PBYTE)a + ((PIMAGE_DOS_HEADER)a)->e_lfanew)) , same as RtlImageNtHeader() May i ask someone with write access to remove it?

2 1

Website
by Rick Langschultz 01 Oct '05

01 Oct '05

Hey everyone, The website looks great. Props to the creators and website admin... Rick Langschultz rlangschultz(a)cox.net (Home) rlangschultz(a)ellemaespa.com (Work) rlangschultz(a)email.uophx.edu (School)

8 8

Re: [ros-svn] [ea] 18180: Fix build.
by Thomas Weidenmueller 30 Sep '05

30 Sep '05

ea(a)svn.reactos.com wrote: > Fix build. Oops, sorry about that... Thanks for fixing it. -Thomas

1 0

RE: Ros-dev Digest, Vol 13, Issue 65
by Lucio Diaz 30 Sep '05

30 Sep '05

I want to make a spanish translation of the web page...once i finish, how does i submit it?. Second question: I can not LOG!, i find no sense to the code validator, what the hell imput is it waiting? The code validator is NOT human readable unless you explain how does it work!. Best regards, Lucio Diaz-Flores. ______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es

2 1

RE: [ros-dev] Site is down on release day! YAY!
by Murphy, Ged (Bolton) 30 Sep '05

30 Sep '05

Is it just my proxy cache, or does every page load except the homepage? -----Original Message----- From: Ge van Geldorp [mailto:gvg@reactos.org] Sent: 30 September 2005 09:18 To: 'ReactOS Development List' Subject: RE: [ros-dev] Site is down on release day! YAY! > From: Alex Ionescu > > The site has been slow day, some pages not loading, the > screenshots especially (confirmed by over 5 people). Now, as > I write this, it's totally dead for myself, Steven, and some > other users in the channel. It's an unfortunate coincidence. There was a problem in the configuration of the firewall between the internet and the university network to which www.reactos.org is connected. It took the network people a while to track this down and fix it. The slowness of the site was caused by the firewall problem, not by the switch to the new system. The site is quite snappy for me now. Gé van Geldorp. ************************************************************************ 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

Site is down on release day! YAY!
by Alex Ionescu 30 Sep '05

30 Sep '05

Hi, The site has been slow day, some pages not loading, the screenshots especially (confirmed by over 5 people). Now, as I write this, it's totally dead for myself, Steven, and some other users in the channel. I thought the new page was supposed to make things faster? Best regards, Alex Ionescu

2 1

RE: Ros-dev Digest, Vol 13, Issue 64
by Lucio Diaz 29 Sep '05

29 Sep '05

Sorry, i realized my old acount was transfered, that is the motive i could not recreate it. Best regards, Lucio Diaz-Flores. ______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es

1 0

installation methods?
by Bernd Blaauw 29 Sep '05

29 Sep '05

Which are current installation methods for ReactOS? so far only an ISO it seems, which for non-emulators requires to write/burn a disk, turn it into a drive that can read burned media (not all cdrom drives can do this), and also requires El-Torito support from the system BIOS. That last part might be worked around, if not supported by the system, by using Smart Boot Manager, which provides its own Eltorito stack. Questions: -why do an installed ROS, a ROS LiveCD and a ROS installCD all have a directory (root_of_drive)\REACTOS ? This makes it complex to have all 3 on 1 drive. WindowsXP/BartPE can use C:\WINDOWS (installed), C:\I386 (setup) , C:\MINIPE (LiveCD) for example -Is it possible to copy the contents of the install CD to a 2nd fat partition, and setup FreeLDR (on diskette for example) to boot that directory? some line like: multi(0)disk(0)rdisk(0)\partition(2)\ReactOS="Install ReactOS from D:\REACTOS to C:\REACTOS" if the ReactOS install CD used any other directory name than a hardcoded '\REACTOS', then 1 partition would have been enough. multi(0)disk(0)rdisk(0)\partition(1)\ROSsetup="Install ReactOS from C:\ROSSETUP to C:\REACTOS" -How do I obtain FreeLDR, other than "installing ReactOS in an emulator first and selecting to install bootloader to A:" ? Can't find the old DOS INSTALL.COM/EXE file along with both FREELDR.SYS/INI -Does installing ReactOS from harddisk actually work? At least it prevents users having to provide controller/cdrom drivers (be it DOS or Win32 drivers). -Anyone tried ROS LiveCD + QEMU (without configuring a harddisk!) ? doesn't bootup, might be a QEMU issue. Vmware + LiveCD works, though C was assigned which isn't nice in case you decide to partition in a GUI Diskmanagement subsystem. In best case, FreeLDR or a minisetup would be able to handle a (zipped) ISO by extracting the files inside it to a temporary location, and start setup from there. Is there any premade FreeLDR diskette image available somewhere? Bernd

1 0

Re: [ros-svn] [gdalsnes] 18113: -reorder InsertXscendingOrder macro argument order and update uses
by Alex Ionescu 29 Sep '05

29 Sep '05

gdalsnes(a)svn.reactos.com wrote: >-reorder InsertXscendingOrder macro argument order and update uses >-start to macrofy list enums in ntoskrnl using LIST_FOR_EACH macros >-use IsListEmpty some places instead of manual coding >-profile.c:KeStartProfile() zero correct buffer in (and not the NULL ptr;-) >-improve LIST_FOR_EACH macros so that the iterator is set to NULL at end of enum >-kthread.c:KiServiceCheck() set the shadowtable before calling the win32k proc/thread init funcs >-apc.c:KiInsertQueueApc() insert special apcs in correct fifo order >-apc.c:KeFlushQueueApc() simplify >-timer.c:KiExpireTimers() calling RemoveEntryList on a possibly empty list is not ok > > >Updated files: >trunk/reactos/include/reactos/helper.h >trunk/reactos/ntoskrnl/io/device.c >trunk/reactos/ntoskrnl/io/driver.c >trunk/reactos/ntoskrnl/io/file.c >trunk/reactos/ntoskrnl/io/fs.c >trunk/reactos/ntoskrnl/io/irp.c >trunk/reactos/ntoskrnl/io/pnpnotify.c >trunk/reactos/ntoskrnl/io/pnproot.c >trunk/reactos/ntoskrnl/ke/apc.c >trunk/reactos/ntoskrnl/ke/bug.c >trunk/reactos/ntoskrnl/ke/kqueue.c >trunk/reactos/ntoskrnl/ke/kthread.c >trunk/reactos/ntoskrnl/ke/profile.c >trunk/reactos/ntoskrnl/ke/queue.c >trunk/reactos/ntoskrnl/ke/timer.c >trunk/reactos/subsys/system/usetup/partlist.c >trunk/reactos/subsys/win32k/ntuser/class.c > >__________________________ > Hi, I'm going to have to voice my extreme outcry against this patch. It is replacing clear and easily debuggable code by non-standard macros which are impossible to debug. It is also going to create problems when people which are not used to them (such as myself): 1) Have no idea what some LIST_FOR_EACH_SAFE thing is doing vs LIST_FOR_EACH vs InsertListLifoSafeMaybeLoopOrWhoKnowsWhat 2) Will never code using these macros, and thus the source will become full of both methods, which is totally ugly. Sometimes, especially in kernel code, it's much better to have an expanded logic then to use a macro. I wrote a great majority of the code that has just been, imho, pollutted with these macros, and I don't appreciate for someone to barge in and change my code for some macro that I don't understand, nor wish to, because it only causes problems. I take great care of the code I write and "own" it (in the programming term) so that if a bug in it arises, I can quickly identify it and be held responsible for it. The addition of these macros hinders that effort. I don't mind someone using them inside his or her own code. I just mind their usage in ntoskrnl, and even more so when it overwrites the clean, clear code that I've written and am used to debugging. Best regards, Alex Ionescu

18 64

IRC Logs
by Rick Langschultz 29 Sep '05

29 Sep '05

Would it be possible to post IRC logs in html format on the website for searching and information? Rick Langschultz rlangschultz(a)cox.net (Home) rlangschultz(a)ellemaespa.com (Work) rlangschultz(a)email.uophx.edu (School)

6 7

software purchase for web forums
by Steven Edwards 29 Sep '05

29 Sep '05

Hello, The web teams has requested that we purchase a software package to handle our forum discussion on the website. The purchase cost is $160 http://www.vbulletin.com/ We have about $90 in paypal donated for misc needs and this seems like a good buy if we really need it. After our hack of the website this may be a good thing. I would like to have a vote up or down about the purchase. If the majority of the project supports this then once we reach the required amount we will purchase. Please reply to me in private, the foundation or general lists only. Do not follow this thread on ros-dev. Thanks Steven __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

1 0

RE: [ros-dev] IRC Logs
by Murphy, Ged (Bolton) 29 Sep '05

29 Sep '05

Royce Mitchell III wrote: > Rick Langschultz wrote: > > > Would it be possible to post IRC logs in html format on the website > > for searching and information? > > Rick Langschultz > > I feel very strongly this would be a bad thing. I was just thinking the same thing. Anyway, #reactos is mainly for arguing, talking garbage and rejoicing cheesecake ..... what can anyone possibly gain from logging that ;) ************************************************************************ 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

2 1

Subsystems, how to write one
by crashfourit 29 Sep '05

29 Sep '05

What are the relevent ReactOS API calls for building a dynamicly loadable subsystem? I'm asking this because I can't find the API documentation on the website. (I looks more like the documentation is not yet completed.) Other questions relevent to this: How do I register a new executible file format? I.E. coff. How do I register a new interrupt vector(s). What are the API to control v86 prosses? If y'all want to know what subsystem I want to write, it is DOS. This is because I'm more familar with programing in DOS.

2 2

New website
by Ge van Geldorp 28 Sep '05

28 Sep '05

Thursday afternoon (UTC) the website will be unavailable for some time. We're going to make the switch to the new website design then. At the same time, we're moving to www.reactos.org as the primary name for the website, with www.reactos.com being an alias (you'll be redirected automatically to www.reactos.org if you use the old name). The mailing lists are also going to be moved from reactos.com to reactos.org, so if you have filtering in place please take this into account. Many thanks to Michael Wirth and especially Klemens Friedl who put a lot of effort in the new site. Gé van Geldorp.

1 0

Re: [ros-diffs] [gdalsnes] 18113: -reorder InsertXscendingOrder macro argument order and update uses
by Hartmut Birr 27 Sep '05

27 Sep '05

gdalsnes(a)svn.reactos.com wrote: > *Modified: trunk/reactos/include/reactos/helper.h* > >--- trunk/reactos/include/reactos/helper.h 2005-09-26 22:06:31 UTC (rev 18112) >+++ trunk/reactos/include/reactos/helper.h 2005-09-26 22:57:48 UTC (rev 18113) >@@ -18,17 +18,21 @@ > > #define EXPORTED __declspec(dllexport) > #define IMPORTED __declspec(dllimport) > > > >-/* iterate through the list using a list entry */ > > >+/* iterate through the list using a list entry. >+ * elem is set to NULL if the list is run thru without breaking out or if list is empty. >+ */ > > > #define LIST_FOR_EACH(elem, list, type, field) \ > for ((elem) = CONTAINING_RECORD((list)->Flink, type, field); \ > > >- &(elem)->field != (list); \ > > >+ &(elem)->field != (list) || (elem = NULL); \ > > > (elem) = CONTAINING_RECORD((elem)->field.Flink, type, field)) > > > Hi, IMHO, this is very bad code. You use a macro to hide a 'for' loop, and later in the source you use a 'break', 'continue' or 'goto' statement to leave the loop or to bypass some code. /* Find entry with SortKey greater than or equal to the passed-in SortKey */ LIST_FOR_EACH(ReturnEntry, &DeviceQueue->DeviceListHead, KDEVICE_QUEUE_ENTRY, DeviceListEntry) { /* Check if keys match */ if (ReturnEntry->SortKey >= SortKey) { /* We found it, so just remove it */ RemoveEntryList(&ReturnEntry->DeviceListEntry); break; } } Such a source is simply unreadable. - Hartmut

3 3

Re: [ros-diffs] [navaraf] 18070: Revert r18064 and correctly set the cell size for hash cells.
by Hartmut Birr 26 Sep '05

26 Sep '05

navaraf(a)svn.reactos.com wrote: >Revert r18064 and correctly set the cell size for hash cells. > >Modified: trunk/reactos/ntoskrnl/cm/regfile.c > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/ntoskrnl/cm/regfile.c* > >--- trunk/reactos/ntoskrnl/cm/regfile.c 2005-09-25 20:46:28 UTC (rev 18069) >+++ trunk/reactos/ntoskrnl/cm/regfile.c 2005-09-25 20:54:40 UTC (rev 18070) >@@ -3033,6 +3033,7 @@ > > else > { > ASSERT(SubKeyCount <= 0xffff); /* should really be USHORT_MAX or similar */ > > >+ NewHashBlock->CellSize = -NewHashSize; > > > NewHashBlock->Id = REG_HASH_TABLE_CELL_ID; > NewHashBlock->HashTableSize = (USHORT)SubKeyCount; > *HashBlock = NewHashBlock; > > Are you sure that this change is correct? I'm not able to install reactos on real hardware. Reactos hangs within CmInitHives at the first boot after the second stage setup. The same boot cd works in qemu. - Hartmut

1 0

Re: [ros-diffs] [ion] 18082: - Fix a bug in CSR Capture APIs
by Thomas Weidenmueller 26 Sep '05

26 Sep '05

ion(a)svn.reactos.com wrote: > + CsrCaptureMessageBuffer(CaptureBuffer, > + NULL, > + Size, > + (PVOID*)&Request.Data.PeekConsoleInputRequest.InputRecord); The last parameter passed to CsrCaptureMessageBuffer in your changes looks horribly wrong. The typecast hides the bug and shouldn't be necessary, the compiler would've warned you that this is most likely wrong. - Thomas

2 2

Re: [ros-diffs] [npwoods] 18056: Lightweight sync with WINE regedit; imported obvious changes such as const correctness, TCHAR string usage etc
by Thomas Weidenmueller 26 Sep '05

26 Sep '05

npwoods(a)svn.reactos.com wrote: > + if (hRootKey == HKEY_DYN_DATA) return _T("HKEY_DYN_DATA"); This key doesn't exist on NT... ;) - Thomas

3 3

Re: [ros-svn] [ea] 18050: Required for binary compatibility with MS KERNEL32.DLL.
by KJKHyperion 25 Sep '05

25 Sep '05

ea(a)svn.reactos.com wrote: >Required for binary compatibility with MS KERNEL32.DLL. > >NOTE >Filip and I still don't understand why KERNEL32 calls twice CsrConnectToServer. >A possible explanation is because the Win32 server is a dual server: gui+console. > > yes. It connects to subsystems 1 and 2. In general, all CSR calls made by kernel32.dll are easily identifiable as calls to either subsystem from their code (the subsystem code is in the upper 16 bits). The GUI subsystem's functions, if you were wondering, are: SrvExitWindowsEx SrvEndTask SrvLogon SrvRegisterServicesProcess SrvActivateDebugger SrvGetThreadConsoleDesktop SrvDeviceEvent SrvRegisterLogonProcess SrvCreateSystemThreads SrvRecordShutdownReason

3 2

Re: [ros-svn] [ea] 18050: Required for binary compatibility with MS KERNEL32.DLL.
by Alex Ionescu 25 Sep '05

25 Sep '05

ea(a)svn.reactos.com wrote: >Required for binary compatibility with MS KERNEL32.DLL. > > > I don't understand this change; it is incorrect. MS kernel32.dll sends the name of the port. Best regards, Alex Ionescu

2 2

Re: [ros-svn] [ea] 18050: Required for binary compatibility with MS KERNEL32.DLL.
by Alex Ionescu 25 Sep '05

25 Sep '05

ea(a)svn.reactos.com wrote: >Required for binary compatibility with MS KERNEL32.DLL. > >NOTE >Filip and I still don't understand why KERNEL32 calls twice CsrConnectToServer. > Once to connect to the Base Server, and once to connect to the Console server. Best regards, Alex Ionescu

1 0

Re: [ros-diffs] [navaraf] 18043: Add TestAlert check to NtContinue.
by Hartmut Birr 25 Sep '05

25 Sep '05

navaraf(a)svn.reactos.com wrote: >Add TestAlert check to NtContinue. > >Modified: trunk/reactos/ntoskrnl/ps/i386/continue.c > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/ntoskrnl/ps/i386/continue.c* > >--- trunk/reactos/ntoskrnl/ps/i386/continue.c 2005-09-25 09:22:22 UTC (rev 18042) >+++ trunk/reactos/ntoskrnl/ps/i386/continue.c 2005-09-25 09:23:05 UTC (rev 18043) >@@ -80,6 +80,11 @@ > > KeLowerIrql(oldIrql); > } > > > >+ if (TestAlert) >+ { >+ KeTestAlertThread(TrapFrame->PreviousMode); >+ } >+ > > > /* Restore the user context */ > Thread->TrapFrame = PrevTrapFrame; > __asm__("mov %%ebx, %%esp;\n" "jmp _KiServiceExit": : "b" (TrapFrame)); > > You know, that ps\i386\continue.c is not longer used. The code was moved to ke\i386\syscall.S. - Hartmut

2 1

RE: [ros-dev] Priorities
by Murphy, Ged (Bolton) 24 Sep '05

24 Sep '05

I plan to implement these in the near future ..... unless someone else does it first. I currently have reworked code for tracert, arp, netstat, ipconfig, pathping and route I will start to commit over the next few weeks. I then plan to implement other services and apps in relation to networking, including test apps. Ged. -----Original Message----- From: WaxDragon [mailto:waxdragon@gmail.com] Sent: 24 September 2005 06:25 To: ReactOS Development List Subject: Re: [ros-dev] Priorities I'm would be very interested in a set of network "simple services" like echo, chargen, daytime, etc.. Having those on the install would help ReactOS get some wider network testing. WD On 9/23/05, Rick Langschultz <rlangschultz(a)cox.net> wrote: > I was wondering if there was a priority list for the next release. > Whether it be 0.2.8 or 0.3.0 I would either like to work on > implementing services and/or tcp/ip based networking. Primarily > though, getting services up and running would be great for me who > develops services. > Rick Langschultz > rlangschultz(a)cox.net (Home) > rlangschultz(a)ellemaespa.com (Work) > rlangschultz(a)email.uophx.edu (School) > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev > -- <arty> don't question it ... it's clearly an optimization _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev ************************************************************************ 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

Priorities
by Rick Langschultz 24 Sep '05

24 Sep '05

I was wondering if there was a priority list for the next release. Whether it be 0.2.8 or 0.3.0 I would either like to work on implementing services and/or tcp/ip based networking. Primarily though, getting services up and running would be great for me who develops services. Rick Langschultz rlangschultz(a)cox.net (Home) rlangschultz(a)ellemaespa.com (Work) rlangschultz(a)email.uophx.edu (School)

2 1

Re: [ros-diffs] [gvg] 17985: Return atom length when requested. Fixes bug 793.
by Hartmut Birr 23 Sep '05

23 Sep '05

gvg(a)svn.reactos.com wrote: >Return atom length when requested. Fixes bug 793. > >Modified: trunk/reactos/lib/rtl/atom.c >Modified: trunk/reactos/subsys/win32k/ntuser/class.c > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/lib/rtl/atom.c* > >--- trunk/reactos/lib/rtl/atom.c 2005-09-22 20:17:55 UTC (rev 17984) >+++ trunk/reactos/lib/rtl/atom.c 2005-09-22 20:24:50 UTC (rev 17985) >@@ -610,6 +610,10 @@ > > *NameLength = Length; > } > } > > >+ else if (NameLength != NULL) >+ { >+ *NameLength = (Entry->NameLength + 1) * sizeof(WCHAR); >+ } > > > > return Status; > } >@@ -651,6 +655,10 @@ > > > *NameLength = Length; > } > } > > >+ else if (NameLength != NULL) >+ { >+ *NameLength = (Entry->NameLength + 1) * sizeof(WCHAR); >+ } > > > } > else > { > > > ------------------------------------------------------------------------ Entry is uninitialized at this two points. - Hartmut

2 3

Moving onto 0.3 with networking
by Murphy, Ged (Bolton) 23 Sep '05

23 Sep '05

As one of our main features for 0.3, we can't progress out of the 0.2.* releases until it is either complete, or the goalposts are moved. With nobody working on networking at the moment, 0.2.8 seems likely and I'm starting to wonder how far into the 0.2.* releases we are going to go. Also, at what stage will the network model be enough to satisfy a 0.3 release? Does this just mean stable, basic TCP/IP with basic ws2_32 support? How many drivers need to be supported? What about service providers for ws2_32.dll (Mswsock.dll is stubbed apart from TransmitFile, and Wshtcpip.dll is non existent) What about NDIS? Change in circumstances has just released most of my evenings now, however although I'm starting to work on networking apps, and hopefully soon User Mode code, my coding skills and windows knowledge are not yet up to a level where I can tackle the more in-depth stuff, especially kernel mode (eek) Does any one plan to, or is anyone going to volunteer to take up networking? I would be more than happy to throw all my spare time into helping them in any way possible. If we glean some information from this email, I can start to document it in the wiki (we don't have much networking documentation in there at the moment) Regards, 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

3 2

Re: [ros-dev] Starcraft Setup BSODs due to KMODE_EXCEPTION_NOT_HANDLED
by eek2121＠comcast.net 23 Sep '05

23 Sep '05

Try using a crack and seeing if it works then. I know there was work done on DirectDraw, so you might have some luck. > Glad I could help you, and help get my favorite game working on ReactOS. > > BTW, the colors on the liltle setup title program (or whatever you call > it) where weird. Just skin deep, and starcraft finished installation as > usual. However, it fails the CD test as it usually does. > > Ge van Geldorp wrote: > > >>From: Reuben Perelman > >> > >> > >> > >>>Ge van Geldorp wrote: > >>>Does the patch below fix this? > >>> > >>> > >> > >>Yes it does. > >> > >> > > > >Ok, thanks for testing. The patch is an ugly hack and I don't want to commit > >it. But at least I know what's going on now and can think about a better > >patch. > > > >Ge van Geldorp. > > > >_______________________________________________ > >Ros-dev mailing list > >Ros-dev(a)reactos.com > >http://reactos.com:8080/mailman/listinfo/ros-dev > > > > > > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev

7 12

Linux Distribution installed...
by Rick Langschultz 22 Sep '05

22 Sep '05

Which linux distro is reactos.com based on? And what are the major software packages installed? Rick Langschultz rlangschultz(a)cox.net (Home) rlangschultz(a)ellemaespa.com (Work) rlangschultz(a)email.uophx.edu (School)

4 4

Re: [ros-dev] Starcraft Setup BSODs due to KMODE_EXCEPTION_NOT_HANDLED
by eek2121＠comcast.net 21 Sep '05

21 Sep '05

As a temporary solution a DirectDraw->GDI renderer could be written. Just an idea, anyways, i hope to commit a DirectDraw test app later today, and once i get my build environment set back up i will work on DirectDraw. > DirectDraw will not work yetr in ros. we are missing to much of it. if we > want directdraw working. we need implement alot more stuff in win32k, gdi32 > and ddraw.dll > > Status : noting works yet. to create a surface. > some work en reusare have been made. When I can contiune or some else on > directx devlioing I do not know when it will happen again. > > > ----- Original Message ----- > From: <eek2121(a)comcast.net> > To: "ReactOS Development List" <ros-dev(a)reactos.com> > Sent: den 21 September 2005 16:37 > Subject: Re: [ros-dev] Starcraft Setup BSODs due to > KMODE_EXCEPTION_NOT_HANDLED > > > > Try using a crack and seeing if it works then. I know there was work done > on DirectDraw, so you might have some luck. > > > > > > > Glad I could help you, and help get my favorite game working on ReactOS. > > > > > > BTW, the colors on the liltle setup title program (or whatever you call > > > it) where weird. Just skin deep, and starcraft finished installation as > > > usual. However, it fails the CD test as it usually does. > > > > > > Ge van Geldorp wrote: > > > > > > >>From: Reuben Perelman > > > >> > > > >> > > > >> > > > >>>Ge van Geldorp wrote: > > > >>>Does the patch below fix this? > > > >>> > > > >>> > > > >> > > > >>Yes it does. > > > >> > > > >> > > > > > > > >Ok, thanks for testing. The patch is an ugly hack and I don't want to > commit > > > >it. But at least I know what's going on now and can think about a > better > > > >patch. > > > > > > > >Ge van Geldorp. > > > > > > > >_______________________________________________ > > > >Ros-dev mailing list > > > >Ros-dev(a)reactos.com > > > >http://reactos.com:8080/mailman/listinfo/ros-dev > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Ros-dev mailing list > > > Ros-dev(a)reactos.com > > > http://reactos.com:8080/mailman/listinfo/ros-dev > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.com > > http://reactos.com:8080/mailman/listinfo/ros-dev > > > > > > -- > > No virus found in this incoming message. > > Checked by AVG Anti-Virus. > > Version: 7.0.344 / Virus Database: 267.11.3/107 - Release Date: 2005-09-20 > > > > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev

2 1

Re: [ros-dev] Starcraft Setup BSODs due to KMODE_EXCEPTION_NOT_HANDLED
by michael＠fritscher.net 21 Sep '05

21 Sep '05

There is already a test app in rosapps\demos\ddraw\ > As a temporary solution a DirectDraw->GDI renderer could be written. > > Just an idea, anyways, i hope to commit a DirectDraw test app later today, > and once i get my build environment set back up i will work on DirectDraw. > > >> DirectDraw will not work yetr in ros. we are missing to much of it. if >> we >> want directdraw working. we need implement alot more stuff in win32k, >> gdi32 >> and ddraw.dll >> >> Status : noting works yet. to create a surface. >> some work en reusare have been made. When I can contiune or some else on >> directx devlioing I do not know when it will happen again. >> >> >> ----- Original Message ----- >> From: <eek2121(a)comcast.net> >> To: "ReactOS Development List" <ros-dev(a)reactos.com> >> Sent: den 21 September 2005 16:37 >> Subject: Re: [ros-dev] Starcraft Setup BSODs due to >> KMODE_EXCEPTION_NOT_HANDLED >> >> >> > Try using a crack and seeing if it works then. I know there was work >> done >> on DirectDraw, so you might have some luck. >> > >> > >> > > Glad I could help you, and help get my favorite game working on >> ReactOS. >> > > >> > > BTW, the colors on the liltle setup title program (or whatever you >> call >> > > it) where weird. Just skin deep, and starcraft finished installation >> as >> > > usual. However, it fails the CD test as it usually does. >> > > >> > > Ge van Geldorp wrote: >> > > >> > > >>From: Reuben Perelman >> > > >> >> > > >> >> > > >> >> > > >>>Ge van Geldorp wrote: >> > > >>>Does the patch below fix this? >> > > >>> >> > > >>> >> > > >> >> > > >>Yes it does. >> > > >> >> > > >> >> > > > >> > > >Ok, thanks for testing. The patch is an ugly hack and I don't want >> to >> commit >> > > >it. But at least I know what's going on now and can think about a >> better >> > > >patch. >> > > > >> > > >Ge van Geldorp. >> > > > >> > > >_______________________________________________ >> > > >Ros-dev mailing list >> > > >Ros-dev(a)reactos.com >> > > >http://reactos.com:8080/mailman/listinfo/ros-dev >> > > > >> > > > >> > > > >> > > >> > > _______________________________________________ >> > > Ros-dev mailing list >> > > Ros-dev(a)reactos.com >> > > http://reactos.com:8080/mailman/listinfo/ros-dev >> > _______________________________________________ >> > Ros-dev mailing list >> > Ros-dev(a)reactos.com >> > http://reactos.com:8080/mailman/listinfo/ros-dev >> > >> > >> > -- >> > No virus found in this incoming message. >> > Checked by AVG Anti-Virus. >> > Version: 7.0.344 / Virus Database: 267.11.3/107 - Release Date: >> 2005-09-20 >> > >> > >> >> _______________________________________________ >> Ros-dev mailing list >> Ros-dev(a)reactos.com >> http://reactos.com:8080/mailman/listinfo/ros-dev > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev >

1 0

Re: [ros-svn] [hbirr] 17912: The share disposition isn't necessary for FILE_READ_ATTRIBUTES.
by Thomas Weidenmueller 21 Sep '05

21 Sep '05

hbirr(a)svn.reactos.com wrote: > The share disposition isn't necessary for FILE_READ_ATTRIBUTES. Actually this prevents opening the file during the operation. A better candidate for GetFileAttributesEx is NtQueryFullAttributesFile which accepts a OBJECT_ATTRIBUTES structure instead of a handle, so there's no need to even open the file at all. Best Regards, Thomas

2 1

Lost my password...
by eek2121＠comcast.net 21 Sep '05

21 Sep '05

Who do i contact to retrieve/reset my SVN password?

2 1

chill out
by Luke Kenneth Casson Leighton 21 Sep '05

21 Sep '05

if someone knows where richard lives could they please blow lots of ganga into the aircon ducts of his house, please. l. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

5 4

Starcraft Setup BSODs due to KMODE_EXCEPTION_NOT_HANDLED
by Reuben Perelman 21 Sep '05

21 Sep '05

Launching setup.exe on the starcraft CD immediatly causes a BSOD. Part of what it says on the BSOD is says: "The Problem Seems to be caused by the following file: win32k.sys KMODE_EXCEPTION_NOT_HANDLED" Attached is a screenshot of the BSOD. I would have put this on bugzilla if bugzilla hadn't given me the error: " The 'bug number' // is invalid. If you are trying to use QuickSearch, you need to enable JavaScript in your browser. To help us fix this limitation, add your comments to bug 70907 <http://bugzilla.mozilla.org/show_bug.cgi?id=70907>."

3 7

OT: HTA Embedding
by Rick Langschultz 21 Sep '05

21 Sep '05

Hello, I know this is a bit off topic but I was wondering if anyone knew how to embed an HTA inside a c++ application. I know that the Add / Remove Programs control panel applet uses HTAs to display registry settings. I want to do sort of the same thing with my app. Rick Langschultz rlangschultz(a)cox.net (Home) rlangschultz(a)ellemaespa.com (Work) rlangschultz(a)email.uophx.edu (School)

2 1

Re: [ros-svn] [royce] 17958: always strip '^' (unless it was preceded by an '^' itself), not just if it precedes the redirection symbols - fixes some of my test cases in seta_test.cmd
by Royce Mitchell III 21 Sep '05

21 Sep '05

royce(a)svn.reactos.com wrote: >always strip '^' (unless it was preceded by an '^' itself), not just if it precedes the redirection symbols - fixes some of my test cases in seta_test.cmd > > >Updated files: >trunk/reactos/subsys/system/cmd/set.c > > "set /a" and "if [not] ==" now work perfectly as far as I'm aware. seta_test.cmd runs successfully in our cmd.exe now.

1 0

Re: [ros-dev] compiling botched version of dcethreads exception using pthread-win32 - WORKS!
by Luke Kenneth Casson Leighton 20 Sep '05

20 Sep '05

dear hackbunny, regarding your request for information about the number of occurrences of the "FINALLY" macro, here they are. not as many. don't know why you're interested, love to know - some other time. find . -name "*.[ch]" | xargs grep FINALLY | wc 19 71 938 -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

2 1

Fresh current D/L from SVN fails to build
by Robert Dickenson 20 Sep '05

20 Sep '05

After updating my binutils to the current candidate release at mingw.org and continuing my build it fails with the following: S:\REACTOS\trunk\reactos>make [RBUILD] makefile.auto Reading build files...done Detecting compiler...detected (gcc) Detecting binutils...detected (ld) Detecting netwide assembler...detected (nasm) Detecting compiler -pipe support...detected Detecting compiler pre-compiled header support...not detected Processing modules...done Creating directories...done Unpacking WINE resources...done Generating test support code...done Generating proxy makefiles...done Checking automatic dependencies...done [DLLTOOL] obj-i386\lib\kernel32\libkernel32.a [MKDIR] obj-i386\tools\winebuild <snip> [CC] apps\utils\net\whois\whois.c [WRC] obj-i386\apps\utils\net\whois\whois.coff [LD] output-i386\apps\utils\net\whois\whois.exe [RSYM] output-i386\apps\utils\net\whois\whois.exe [DLLTOOL] obj-i386\lib\version\libversion.a [DLLTOOL] obj-i386\lib\gdi32\libgdi32.a [DLLTOOL] obj-i386\lib\ntdll\libntdll.a [CC] apps\utils\rosperf\rosperf.c [CC] apps\utils\rosperf\lines.c [CC] apps\utils\rosperf\fill.c [CC] apps\utils\rosperf\text.c [CC] apps\utils\rosperf\testlist.c [WRC] obj-i386\apps\utils\rosperf\rosperf.coff [LD] output-i386\apps\utils\rosperf\rosperf.exe [RSYM] output-i386\apps\utils\rosperf\rosperf.exe [CC] apps\utils\ps\ps.c In file included from include/ndk/ntndk.h:39, from apps/utils/ps/ps.c:27: include/ndk/extypes.h:174: warning: redefinition of `LANGID' w32api/include/winnt.h:136: warning: `LANGID' previously declared here make: *** [obj-i386\apps\utils\ps\ps.o] Error 1 S:\REACTOS\trunk\reactos>toolsver NASM version 0.98 GNU ld version 2.16.91 20050827 GNU dlltool 2.16.91 20050827 GNU windres 2.16.91 20050827 Copyright 2005 Free Software Foundation, Inc. Reading specs from C:/MinGW/bin/../lib/gcc-lib/mingw32/3.3.1/specs Configured with: ../gcc/configure --with-gcc --with-gnu-ld --with-gnu-as --host= mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls --enable -languages=c,c++,f77,objc,ada,java --disable-win32-registry --disable-shared --e nable-sjlj-exceptions --enable-libgcj --disable-java-awt --without-x --enable-ja va-gc=boehm --disable-libgcj-debug --enable-interpreter --enable-hash-synchronization Thread model: win32 gcc version 3.3.1 (mingw special 20030804-1) GNU nm 2.16.91 20050827 GNU Make 3.80 Cleaning looks a little suspect as well: S:\REACTOS\trunk\reactos>make clean make: [cabman_clean] Error 1 (ignored) [MKDIR] obj-i386\tools\cdmake [CC] tools\cdmake\cdmake.c [CC] tools\cdmake\llmosrt.c [MKDIR] output-i386\tools\cdmake [LD] output-i386\tools\cdmake\cdmake.exe [MKDIR] obj-i386\tools\mkhive [CC] tools\mkhive\binhive.c [CC] tools\mkhive\infcache.c [CC] tools\mkhive\mkhive.c [CC] tools\mkhive\reginf.c [CC] tools\mkhive\registry.c [MKDIR] output-i386\tools\mkhive [LD] output-i386\tools\mkhive\mkhive.exe [MKDIR] obj-i386\tools\rbuild\tests make: [widl_clean] Error 1 (ignored) S:\REACTOS\trunk\reactos>

1 0

moving discussion of freedce/win32 to freedce-devel
by Luke Kenneth Casson Leighton 20 Sep '05

20 Sep '05

dear reactos developers, after receiving some much appreciated advice i have made a decision: i will not be posting to the ros-dev lists (unless invited to do so). if you wish to discuss the porting of freedce to win32, or to find out about its progress, the freedce-devel mailing list is where i believe that to be most appropriate. l. p.s. banning people on freedce-devel is not even considered let alone discussed. that's mainly because not much is discussed there at all in fact, it's a pretty low-traffic list :) -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

2 1

Re: [ros-dev] found it! the "dce porting" header file
by Luke Kenneth Casson Leighton 20 Sep '05

20 Sep '05

dear hackbunny, regarding your comments about screaming in pain and having teeth pulled because of pthreads-win32, i am so so sorry: i cannot help you there. i don't have the time nor the expertise. i posted (some time afterwards) a message indicating just how many occurrences of DCE exception macros there are - it's literally hundreds. at least pthreads-win32 "gets something going". i believe strongly in "GetItWorking(tm)" and "RewriteLaterAfterProvingItWorks(tm)". i _don't_ believe in throwing everything away just because one way to get things up and running quickly happens not to be the nicest solution. it's a matter of priorities. plus, like i said in my previous reply, DCE exceptions deal with networking and memory errors in a runtime environment where application designers _know_ that there's going to be order-of-milliseconds delays. the usual speed-critical criteria which make people run away screaming about exceptions simply do not apply. l. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

1 0

Re: [ros-dev] found it! the "dce porting" header file
by Luke Kenneth Casson Leighton 20 Sep '05

20 Sep '05

dear hyperion, sorry for not getting back to this one earlier. regarding hacking up a replacement for the DCE compatible threads library: GREAT. i have made a start by removing the POSIX Draft 4 threading requirements, which has been on the cards for like ... ermmm... five years. see http://sf.net/projects/freedce, cvs requirements, see dcethreads-win32 give me a while to commit what i've done so far. there's actually very little code left, because of pthreads-win32. the only stuff left in dcethreads-win32 is actually the DCE exception handling stuff. which i understand is right in your area of expertise :) btw: one important point. it is NOT, i repeat NOT important that "speed be of the essence". the usual argument "exceptions are expensive and therefore evil" simply doesn't apply. exceptions in DCE are used to catch memory and _networking_ errors. _networking_ errors. order of milliseconds and greater. DCE/RPC applications (the Windows NT 4.0 Domains and Administrative suite are good - and relevant - examples) are _designed_ with networking errors and networking delays taken into consideration and into account. the only instance where someone didn't bother to take networking into account is the idiots who ported win16 (yes, win16, remember we're talking Windows NT 3.1 here - where do you think win32 came from? not from the idiots in the win95 team :) printing API to spoolss (taking the "blobs" as [in,out] parameters - imagine what _that_ does when you have the double-function-call thing, the first one to ask how big a "blob" to allocate). but i digress... -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

1 0

Re: [ros-dev] found it! the "dce porting" header file
by Luke Kenneth Casson Leighton 20 Sep '05

20 Sep '05

[dear ros-dev developers, i'm "on-list" but have "receive postings disabled" because i have far too much on my plate to deal with right now. i'm sorry i haven't got back to people] saveliy, hi, you asked if freedce is useable: the answer is yes [with conditions]. freedce is the _reference_ implementation from http://opengroup.org/dce. and it is autoconf'd. therefore, asking "is it fully featured" the answer is it _is_ the features :) :) now. microsoft "embraced and extended" DCE/RPC actually the 1.1 reference implementation because it's OSF 1.1 Free Software BSD-Compatible license... what am i doing, what am i doing, see this: http://en.wikipedia.org/wiki/MSRPC :) i've added certain "missing" features to freedce and it's now on-wire compatible and IDL-compatible with MSRPC. what it _doesn't_ yet do is output MSRPC-binary-compatible stuff which people are referring to on wine lists as "type libraries". hope this helps. l. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

1 0

Re: [ros-svn] [gdalsnes] 17923: -added better LIST_FOR_EACH macros (ripped from wine) and fix their usage
by Steven Edwards 19 Sep '05

19 Sep '05

Hi, --- gdalsnes(a)svn.reactos.com wrote: > -added better LIST_FOR_EACH macros (ripped from wine) and fix their usage > -make hotkeys session global (they dont belong in winsta) > Updated files: > trunk/reactos/include/reactos/helper.h These are in include/wine/list.h right? Are you duplicating the macros or are you using them from there? Sorry I don't have time to review the diff. Thanks Steven __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

1 0

scared! freedce-win32 in a cvs repository near you
by Luke Kenneth Casson Leighton 19 Sep '05

19 Sep '05

right. 48 hours later, i've got a first version of freedce-win32 to try out, which i'm actually a bit frightened of running. just in case it works :) thank goodness for pthreads-win32, otherwise i'd be up small creek. major things todo: in ipnaf.c (actually ipnaf_linux.c or even better ipnaf_win32.c) it's necessary to write an IP-interface-enumeration function. this function presumably will call GetIpAddrTable and go over all the addresses including netmasks and broadcast addresses returning information that the rpc runtime can then "listen" on - one by one. no, freedce doesn't go listening on 0.0.0.0 it binds to all "towers" whatever they're called. because i've commented this code out (stubbed) i am not expecting freedce-win32 to work straight off. once this is working, putting it in place of rpcrt4 should be relatively straightforward (and mostly very very mind numbingly boring) - a matter of "back-converting" and following the lead of dceport.h - microsoft's "wrapper" header file that allows application developers to port DCE/RPC applications to MSRPC. i say "lead" because it's woefully inadequate, representing about 10% of the functions and structs that actually need "converting", because dceport.h contains the "publicly accessible" functions. once _that's_ done, then there will be two remaining tasks: 1) check that pthreads-win32 works under wine (!) and if so, job done, otherwise it's _yet_ another emulation layer to write, but at least the source code of pthreads-win32 represents a damn good starting point 2) mash freedce's typelib output to be compatible with MSRPC binaries. this latter is no small task (but at least it could be considered). the data structures have been _totally_ mashed, by microsoft. gotta run. later. l. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

1 0

Re: [ros-bugs] [Bug 751] Putty - Ntoskrnl bugcheck when sending login/Password to FTP server
by WaxDragon 19 Sep '05

19 Sep '05

GvG and I have both seen this multiple char behaviour. I think I still need to file a bug on it. ;0/ On 9/18/05, ReactOS.Bugzilla(a)reactos.com <ReactOS.Bugzilla(a)reactos.com> wrote: > http://reactos.com/bugzilla/show_bug.cgi?id=751 > > > > > > ------- Additional Comments From gerard.gatineau(a)laposte.net 2005-18-09 19:33 ------- > With svn 17912 , There is no bugcheck when Putty is configured for protocol = > SSH and port 22 to connect to my FTP server : > > Reception of " login as " > Type login name (abcd..) > Display of login name in putty window is incorrect ( aabbccdd..) > > Debug messages are output for each character typed > so->so_state 102 > (lib\imm32\imm.c:471) (000201d0): stub > (lib\imm32\imm.c:940) (00000000, 005ac9e4): stub > (lib\imm32\imm.c:818) (000201d0, 00000000): stub > (lib\imm32\imm.c:471) (000201d0): stub > (lib\imm32\imm.c:940) (00000000, 005aca14): stub > (lib\imm32\imm.c:818) (000201d0, 00000000): stub > (lib\imm32\imm.c:471) (000201d0): stub > (lib\imm32\imm.c:940) (00000000, 005aca14): stub > (lib\imm32\imm.c:818) (000201d0, 00000000): stub > so->so_state 102 > > Note : Not sure if this test makes sense with ftp server > > -- > Configure bugmail: http://reactos.com/bugzilla/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are the assignee for the bug, or are watching the assignee. > _______________________________________________ > Ros-bugs mailing list > Ros-bugs(a)reactos.com > http://reactos.com/mailman/listinfo/ros-bugs > -- <arty> don't question it ... it's clearly an optimization

2 1

How far is the user(login) system implemented?
by Jasper Huzen 18 Sep '05

18 Sep '05

Hi, We are a group of students and we are interested in writing the user(login) system into ReactOS (we have he project with the subject 'Security' and we may choose a security project) Can anyone tell me how far the user system (userlogin and security of users) implemented????? Jasper MSN: jhuzen(a)hotmail.com

1 0

freedce-win32 - winsock joy
by Luke Kenneth Casson Leighton 18 Sep '05

18 Sep '05

progress being made. am about 10-15% the way through a compile, having previously got dcethreads to use pthread-win32 by judicious ripping out of large amounts of code. fortunately, elrond has already win32'd tng, so there is stacks of code in tng's lib/util_sock.c to rip off :) -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

1 0

Re: [ros-svn] [hbirr] 17910: Don't check the share access for directories.
by KJKHyperion 18 Sep '05

18 Sep '05

hbirr(a)svn.reactos.com wrote: >Don't check the share access for directories. > are you sure this is right? I quite remember share access being enforced on directories

2 3

Re: [ros-diffs] [hbirr] 17912: The share disposition isn't necessary for FILE_READ_ATTRIBUTES.
by Gunnar Dalsnes 18 Sep '05

18 Sep '05

Is this correct? I can't see how... Even GENERIC_READ imply FILE_READ_ATTRIBUTES and using your "share disposition isn't necessary for FILE_READ_ATTRIBUTES rule" this means file sharing isnt needed for GENERIC_READ either... hbirr(a)svn.reactos.com wrote: > The share disposition isn't necessary for FILE_READ_ATTRIBUTES. > > Modified: trunk/reactos/lib/kernel32/file/file.c > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/lib/kernel32/file/file.c* > > --- trunk/reactos/lib/kernel32/file/file.c 2005-09-18 13:36:29 UTC (rev 17911) > +++ trunk/reactos/lib/kernel32/file/file.c 2005-09-18 13:46:37 UTC (rev 17912) > @@ -873,7 +873,7 @@ > > SYNCHRONIZE | FILE_READ_ATTRIBUTES, > &ObjectAttributes, > &IoStatusBlock, > > - FILE_SHARE_READ | FILE_SHARE_WRITE | FILE_SHARE_DELETE, > > + 0, > > FILE_SYNCHRONOUS_IO_NONALERT); > RtlFreeUnicodeString (&FileName); > if (!NT_SUCCESS (Status)) >

2 2

Re: [ros-diffs] [greatlrd] 17909: give GetFileAttributesExW more NtOpenFile right to prevent reactos crash if u using CreateFile then GetFileAttributesExW. It also fix a bug for me for livecd it booting on first try now in vmware. instead second or more booting try.
by Gunnar Dalsnes 18 Sep '05

18 Sep '05

greatlrd(a)svn.reactos.com wrote: > give GetFileAttributesExW more NtOpenFile right to prevent reactos crash if u using CreateFile then GetFileAttributesExW. It also fix a bug for me for livecd it booting on first try now in vmware. instead second or more booting try. "crash if using CreateFile then GetFileAttributesExW" ??? What?? It looks like you are working around the real bug by using a _very_ dirty workaround. > > Modified: trunk/reactos/lib/kernel32/file/file.c > > - SYNCHRONIZE | FILE_READ_ATTRIBUTES, > > + SYNCHRONIZE | GENERIC_ALL, > FILE_READ_ATTRIBUTES access is surely sufficient for reading a files attributes...

1 0

found it! the "dce porting" header file
by Luke Kenneth Casson Leighton 18 Sep '05

18 Sep '05

http://examples.oreilly.de/english_examples/dce/dce_nt/dceport.h.aug95 o joy o joy. also, i found _this_!!! http://sourceware.org/pthreads-win32/ which is an implementation of pthreads on win32. _also_ i found - was reminded - by judicious searching on google, that of course entegrity.com have "PC-DCE" which is of course a _commercial_ product that has done exactly the work required: making dce (1.1? 1.2.2?) compile on Win32. including exceptions, dealing with mapping the names, blah blahhh. now. anyone got any brainy ideas on how to reverse dceport.h - in particular the thingy. wotsit. TRY/FINALLY/CATCH stuff? what i'm going to try to do is take a shot at simply compiling dcethreads - on win32. if that _works_ (the tests pass) it'll be great - it will prove two things: 1) that pthreads-win32 works 2) that the dce exception handling will fly, on win32, and _that_ means pretty much zero (urk! let's hope!) work. for now. my main goal: "GetItWorking(tm)". i couldn't care less about binary compatibility for now: i want "services" - i want srvsvcd, i want winregd, i want lsarpcd, i want samrd - all compiled, all working, using TCP/IP. i can then work on rewriting freedce's ntlmsspauth.so to be a DLL (starting off as my favourite - a stub with username and password of "test"). i can then work on writing an "ncalrpc" plugin transport (which is very straightforward: a matter of filling in about 25 functions in a vector table). and also on a ncacn_np plugin transport. "working" means that other people will then be able to focus on issues like binary compatibility. guys (wine team) i have to say this. you were utterly insane to not use freedce as your starting point - and i am still bewildered by you not even looking at its source code (which is topologically identical in almost all areas, to what you've created) or the opengroup's documentation. i say that with the greatest of respect for what you've achieved without freedce. l. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

8 11

compiling botched version of dcethreads exception using pthread-win32 - WORKS!
by Luke Kenneth Casson Leighton 18 Sep '05

18 Sep '05

okay, it's not time to get totally excited yet, but i have successfully compiled - and run, and confirmed as working on ros - some of the test programs from dcethreads (http://sf.net/projects/freedce) when cross-compiled with mingw32 and linked with pthreads-win32. this is _very_ significant because it means that there is a good chance of replicating entegrity's work - PC-DCE - with zero modifications to the freedce source code. i've cut out entirely the dcethreads "emulation" stuff, which means that dcethreads posix draft 4 compliance - including the ability to pass on thread cancellation across an RPC client/server app boundary, and including the ability to pass on signals across an RPC client/server app boundary - are completely out the window... ... but i don't care. so. the bits "remaining" in my hacked-together-version of dcethreads is _just_ the exception handling - exc_handling.c and exc_handling.h pretty much. that means that the DCE "TRY", "RAISE", "CATCH" and "EXCEPT" macros are all there. it's early days, but this is good news. now. here's what i don't want to hear from anyone: q) "why in hell's name are you doing this? why can't you just remove all references to posix threads and all references to DCE/RPC exception handling?" a) lkcl@highfield:~/sf/freedce/freedce$ find . | xargs grep pthread | wc 770 3965 64010 lkcl@highfield:~/sf/freedce/freedce$ find . -name "*.[ch]" | xargs grep ENDTRY | wc 105 248 4490 lkcl@highfield:~/sf/freedce/freedce$ find . -name "*.[ch]" | xargs grep RAISE | wc 202 731 12799 lkcl@highfield:~/sf/freedce/freedce$ find . -name "*.[ch]" | xargs grep CATCH | wc 217 685 12392 in short: modifying several thousand lines of code, by hand, is something that microsoft can happily pay some donut code-dunker to do (and did, probably back in 1990-1993) but i sure as hell ain't doing it for a proof-of-concept bit of work. q) "why are you doing this and doing it to _us_? go away!!" a) you are inflicting much pain upon yourselves, even though you probably don't know it. don't like what i'm doing, don't like what i have to say? tough - get over it: i don't have time or money to waste to stroke egos. i'll give you what time i can and what facts i can and also i will present you with an opinion: if you don't like that opinion or the way it's presented, that is your choice. live with it, deal with it or ignore it - i'll pretend i don't care which. i give you information, present you with choices: where you go from there - as neo says as the end of matrix 1.... l. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

2 1

Trunk Freeze
by WaxDragon 17 Sep '05

17 Sep '05

It's only been two weeks since I sent out the August State of the Repository, but the tree has already had 271 revisions. There have been several large commits, and trunk has had several build breakages, and instability in general. Just today we had three commits reversing and unreversing some of Alex's changes. I'm calling for a trunk freeze until several issues have been addressed. * The release build is broken. So far the string library and the usb code have been fixed. I was working with Alex on a break in the exception handling when this topic came up. * There seems to be a mysterious hang when shutting down ReactOS in qemu. I've seen it personally and heard reports of it, but since it locks up qemu so bad you can't free the mouse, no one has gotten a trace (that I am aware of). * Gunnar's win32k changes introduced several bugs, many of which were fixed, but I still feel unsure about others that may be hiding. * Hartmut fixed the MP build. See, I didn't even know that was broken. I would like to freeze the tree for 72 hours, over the weekend, allowing bugfixes only. I think we all need to grab a fresh copy and run it under every platform we have, checking all the options. According to the rules set forth, I need three developers. Who agrees to a trunk freeze?

7 11

RE: [ros-dev] Problem with compiling 17859
by Ge van Geldorp 17 Sep '05

17 Sep '05

> From: Ge van Geldorp > > Complaints to alex It turns out there was a communication problem between Alex and myself. A little background: in r17811 Alex introduced a line in an asm file which failed to compile on older binutils. I talked to him about this on IRC and proposed a workaround. The communication problem was that I thought he rejected the workaround, while Alex thought he ok'ed the workaround and thought I would make the change. Result: workaround not applied and 2 people pissed-off at each other. My apologies to Alex for the remark quoted above, which was inappropriate even if he hadn't agreed to the workaround. Ge van Geldorp.

1 0

Disassempler
by Rick Langschultz 17 Sep '05

17 Sep '05

Does anyone have any examples of a disassembler or decompiler that I could use for my ReactOS program I am writing... Does anyone know about a disassembler or decompiler for Mac OS X also? Rick Langschultz rlangschultz(a)cox.net (Home) rlangschultz(a)ellemaespa.com (Work) rlangschultz(a)email.uophx.edu (School)

2 1

set /a implementation for review
by Royce Mitchell III 17 Sep '05

17 Sep '05

recursive-descent implementation of set /a. I'm sure not all error messages are going to match MS's exactly. I didn't really try to do that. since trunk is frozen, I'm submitting this patch for anybody that wants to review. I'll commit it Monday evening (if I have time) pending any suggestions for improvements or bug-fixes, etc that ppl may have for it. Index: set.c =================================================================== --- set.c (revision 17890) +++ set.c (working copy) @@ -35,6 +35,8 @@ */ #include <precomp.h> +#include <malloc.h> +#include <stdio.h> #include "resource.h" #ifdef INCLUDE_CMD_SET @@ -43,7 +45,15 @@ /* initial size of environment variable buffer */ #define ENV_BUFFER_SIZE 1024 +static BOOL +seta_eval ( LPCTSTR expr ); +static LPCTSTR +skip_ws ( LPCTSTR p ) +{ + return p + strspn ( p, " \t" ); +} + INT cmd_set (LPTSTR cmd, LPTSTR param) { TCHAR szMsg[RC_STRING_MAX_SIZE]; @@ -83,6 +93,12 @@ return 0; } + if ( !_tcsnicmp (param, _T("/A"), 2) ) + { + // TODO FIXME - what are we supposed to return? + return seta_eval ( skip_ws(param+2) ); + } + p = _tcschr (param, _T('=')); if (p) { @@ -124,4 +140,386 @@ return 0; } +static INT +ident_len ( LPCTSTR p ) +{ + LPCTSTR p2 = p; + if ( __iscsymf(*p) ) + { + ++p2; + while ( __iscsym(*p2) ) + ++p2; + } + return p2-p; +} + +#define dup_ident(p) _tcsncpy_s(alloca((ident_len(p)+1)*sizeof(TCHAR)), p, +#define PARSE_IDENT(ident,identlen,p) \ + identlen = ident_len(p); \ + ident = (LPTSTR)alloca ( ( identlen + 1 ) * sizeof(TCHAR) ); \ + memmove ( ident, p, identlen * sizeof(TCHAR) ); \ + ident[identlen] = 0; + +static BOOL +seta_identval ( LPCTSTR ident, INT* result ) +{ + // get size of buffer for env var + LPTSTR buf; + DWORD dwBuffer = GetEnvironmentVariable ( ident, NULL, 0 ); + // if GetEnvironmentVariable() fails, it returns 0 + if ( !dwBuffer ) + { + // TODO FIXME - is it correct to report a value of 0 for non-existant variables? + *result = 0; + return FALSE; + } + buf = (LPTSTR)alloca ( dwBuffer * sizeof(TCHAR) ); + if ( !buf ) + { + // TODO FIXME - is it correct to report 0 when report resources low... should we error somehow? + *result = 0; + return FALSE; + } + GetEnvironmentVariable ( ident, buf, dwBuffer ); + *result = atoi ( buf ); + return TRUE; +} + +static BOOL +calc ( INT* lval, TCHAR op, INT rval ) +{ + switch ( op ) + { + case '*': + *lval *= rval; + break; + case '/': + *lval /= rval; + break; + case '%': + *lval %= rval; + break; + case '+': + *lval += rval; + break; + case '-': + *lval -= rval; + break; + case '&': + *lval &= rval; + break; + case '^': + *lval ^= rval; + break; + case '|': + *lval |= rval; + break; + default: + printf ( "Invalid operand.\n" ); + return FALSE; + } + return TRUE; +} + +static BOOL +seta_assignment ( LPCTSTR* p_, INT* result ); + +static BOOL +seta_unaryTerm ( LPCTSTR* p_, INT* result ) +{ + LPCTSTR p = *p_; + if ( *p == '(' ) + { + INT rval; + p = skip_ws ( p + 1 ); + if ( !seta_assignment ( &p, &rval ) ) + return FALSE; + if ( *p != ')' ) + { + _tprintf ( _T("Expected ')'\n") ); + return FALSE; + } + p = skip_ws ( p + 1 ); + *p_ = p; + return TRUE; + } + if ( isdigit(*p) ) + { + *result = atoi ( p ); + p = skip_ws ( p + strspn ( p, "1234567890" ) ); + } + else if ( __iscsymf(*p) ) + { + LPTSTR ident; + INT identlen; + PARSE_IDENT(ident,identlen,p); + if ( !seta_identval ( ident, result ) ) + return FALSE; + } + else + { + _tprintf ( _T("Expected number or variable name\n") ); + return FALSE; + } + *p_ = p; + return TRUE; +} + +static BOOL +seta_mulTerm ( LPCTSTR* p_, INT* result ) +{ + LPCTSTR p = *p_; + TCHAR op = 0; + INT rval; + if ( _tcschr(_T("!~-"),*p) ) + { + op = *p; + p = skip_ws ( p + 1 ); + } + if ( !seta_unaryTerm ( &p, &rval ) ) + return FALSE; + switch ( op ) + { + case '!': + rval = !rval; + break; + case '~': + rval = ~rval; + break; + case '-': + rval = -rval; + break; + } + + *result = rval; + *p_ = p; + return TRUE; +} + +static BOOL +seta_addTerm ( LPCTSTR* p_, INT* result ) +{ + LPCTSTR p = *p_; + INT lval; + if ( !seta_mulTerm ( &p, &lval ) ) + return FALSE; + while ( *p && _tcschr(_T("*/%"),*p) ) + { + INT rval; + TCHAR op = *p; + + p = skip_ws ( p+1 ); + + if ( !seta_mulTerm ( &p, &rval ) ) + return FALSE; + + if ( !calc ( &lval, op, rval ) ) + return FALSE; + } + + *result = lval; + *p_ = p; + return TRUE; +} + +static BOOL +seta_logShiftTerm ( LPCTSTR* p_, INT* result ) +{ + LPCTSTR p = *p_; + INT lval; + if ( !seta_addTerm ( &p, &lval ) ) + return FALSE; + while ( *p && _tcschr(_T("+-"),*p) ) + { + INT rval; + TCHAR op = *p; + + p = skip_ws ( p+1 ); + + if ( !seta_addTerm ( &p, &rval ) ) + return FALSE; + + if ( !calc ( &lval, op, rval ) ) + return FALSE; + } + + *result = lval; + *p_ = p; + return TRUE; +} + +static BOOL +seta_bitAndTerm ( LPCTSTR* p_, INT* result ) +{ + LPCTSTR p = *p_; + INT lval; + if ( !seta_logShiftTerm ( &p, &lval ) ) + return FALSE; + while ( *p && _tcschr(_T("<>"),*p) && p[0] == p[1] ) + { + INT rval; + TCHAR op = *p; + + p = skip_ws ( p+2 ); + + if ( !seta_logShiftTerm ( &p, &rval ) ) + return FALSE; + + if ( !calc ( &lval, op, rval ) ) + return FALSE; + } + + *result = lval; + *p_ = p; + return TRUE; +} + +static BOOL +seta_bitExclOrTerm ( LPCTSTR* p_, INT* result ) +{ + LPCTSTR p = *p_; + INT lval; + if ( !seta_bitAndTerm ( &p, &lval ) ) + return FALSE; + while ( *p == _T('&') ) + { + INT rval; + + p = skip_ws ( p+1 ); + + if ( !seta_bitAndTerm ( &p, &rval ) ) + return FALSE; + + lval &= rval; + } + + *result = lval; + *p_ = p; + return TRUE; +} + +static BOOL +seta_bitOrTerm ( LPCTSTR* p_, INT* result ) +{ + LPCTSTR p = *p_; + INT lval; + if ( !seta_bitExclOrTerm ( &p, &lval ) ) + return FALSE; + while ( *p == _T('^') ) + { + INT rval; + + p = skip_ws ( p+1 ); + + if ( !seta_bitExclOrTerm ( &p, &rval ) ) + return FALSE; + + lval ^= rval; + } + + *result = lval; + *p_ = p; + return TRUE; +} + +static BOOL +seta_expr ( LPCTSTR* p_, INT* result ) +{ + LPCTSTR p = *p_; + INT lval; + if ( !seta_bitOrTerm ( &p, &lval ) ) + return FALSE; + while ( *p == _T('|') ) + { + INT rval; + + p = skip_ws ( p+1 ); + + if ( !seta_bitOrTerm ( &p, &rval ) ) + return FALSE; + + lval |= rval; + } + + *result = lval; + *p_ = p; + return TRUE; +} + +static BOOL +seta_assignment ( LPCTSTR* p_, INT* result ) +{ + LPCTSTR p = *p_; + LPTSTR ident; + TCHAR op = 0; + INT identlen, exprval; + + PARSE_IDENT(ident,identlen,p); + if ( identlen ) + { + if ( *p == _T('=') ) + op = *p, p++; + else if ( _tcschr ( _T("*/%+-&^|"), *p ) && p[1] == _T('=') ) + op = *p, p += 2; + else if ( _tcschr ( _T("<>"), *p ) && *p == p[1] && p[2] == _T('=') ) + op = *p, p += 3; + else + { + _tprintf ( _T("Missing operand.\n") ); + return FALSE; + } + p += strspn ( p, " \t" ); + } + + if ( !seta_expr ( &p, &exprval ) ) + return FALSE; + + if ( identlen ) + { + INT identval; + LPTSTR buf; + + if ( !seta_identval ( ident, &identval ) ) + return FALSE; + if ( op == '=' ) + identval = *result; + else if ( !calc ( &identval, op, exprval ) ) + return FALSE; + buf = (LPTSTR)alloca ( 32 * sizeof(TCHAR) ); + _sntprintf ( buf, 32, _T("%i"), identval ); + SetEnvironmentVariable ( ident, buf ); // TODO FIXME - check return value + exprval = identval; + } + + *result = exprval; + *p_ = p; + return TRUE; +} + +static BOOL +seta_eval ( LPCTSTR p ) +{ + INT rval; + if ( !*p ) + { + _tprintf ( _T("The syntax of the command is incorrect.\n") ); + return FALSE; + } + for ( ;; ) + { + if ( !seta_assignment ( &p, &rval ) ) + return FALSE; + if ( !*p ) + break; + if ( *p != _T(',') ) + { + _tprintf ( _T("Missing operator.\n") ); + return FALSE; + } + ++p; // skip comma + } + _tprintf ( _T("%i\n"), rval ); + return TRUE; +} + #endif

2 1

Problem with compiling 17859
by Saveliy Tretiakov 17 Sep '05

17 Sep '05

What's this? [GAS] lib\rtl\i386\except.s lib\rtl\i386\except.s: Assembler messages: lib\rtl\i386\except.s:207: Error: Unrecognized token `|4)' lib\rtl\i386\except.s:207: Error: Unexpected token `' lib\rtl\i386\except.s:232: Error: Unrecognized token `|4)' lib\rtl\i386\except.s:232: Error: Unexpected token `' make: *** [obj-i386\lib\rtl\i386\except.o] Error 1

5 6

Anyone looking for a nice, uncomplicated bug to fix?
by Ge van Geldorp 16 Sep '05

16 Sep '05

Bug 775 (http://www.reactos.com/bugzilla/show_bug.cgi?id=775) seems to be a simple application bug. I expect no kernel involvement at all. So, if you were always wanting to fix something in ReactOS but were afraid it might be too complicated, this bug is for you. It should give you experience in building and debugging ReactOS so maybe next time you can attack something a little bit more complicated. Gé van Geldorp.

1 0

Re: [ros-diffs] [hbirr] 17863: Fixed the MP build.
by Alex Ionescu 16 Sep '05

16 Sep '05

hbirr(a)svn.reactos.com wrote: >Fixed the MP build. > Hi Hartmut, I'm really sorry, I forgot to test MP=1 :( We really need a way to ensure that KDBG/MP code always gets built... it would cause less problems... Best regards, Alex Ionescu

1 0

Re: [ros-diffs] [ion] 17860: Return valid status
by Hartmut Birr 15 Sep '05

15 Sep '05

ion(a)svn.reactos.com wrote: >Return valid status > >Modified: trunk/reactos/lib/rtl/exception.c > > > ------------------------------------------------------------------------ > *Modified: trunk/reactos/lib/rtl/exception.c* > >--- trunk/reactos/lib/rtl/exception.c 2005-09-15 13:25:32 UTC (rev 17859) >+++ trunk/reactos/lib/rtl/exception.c 2005-09-15 14:07:37 UTC (rev 17860) >@@ -39,10 +39,10 @@ > > Context.ContextFlags = CONTEXT_FULL; > > /* Check if we're being debugged (user-mode only) */ > > >- if (!RtlpCheckForActiveDebugger()) > > >+ if (!RtlpCheckForActiveDebugger(TRUE)) > > RtlpCheckForActiveDebugger is defined as BOOLEAN NTAPI RtlpCheckForActiveDebugger(VOID); - Hartmut

1 0

I/O subsystem question
by Ge van Geldorp 15 Sep '05

15 Sep '05

I'm working on bug 713 (http://www.reactos.com/bugzilla/show_bug.cgi?id=713 for the click-happy). What I have found is this: - Telnet opens a socket - Sending and receiving are handled by different threads, let's call them S and R - Thread R starts a recv() operation, which is translated to an ioctl on the socket - No data is available, so thread R blocks, waiting for FileObject->Event - I type something, which is handled by thread S. Thread S starts a send() operation. - Again translated to an ioctl on the socket. Since this is the same socket as used by S, the FileObject will be the same - The send can complete immediately, IoCompleteRequest is called which sets the FileObject->Event. - Thread R is unblocked, the event it was waiting for was set by thread S. However, the irp of thread R was never completed. The recv() call returns with bogus info. - Thread R starts another recv(). When some data arrives from the server, two irps are waiting for it. This eventually leads to the crash. The fundamental problem seems to be multiple overlapping I/O operations which all use FileObject->Event to signal their completion. I have no idea how to fix that... Gé van Geldorp.

5 8

Non-working uxtheme.dll
by Mike Swanson 14 Sep '05

14 Sep '05

I'm sorry if this would a wrong place to post this, but since I'm trying the ReactOS uxtheme.dll, I figured this would be fine. I've compiled today's SVN, and I noticed that ReactOS had a uxtheme.dll (didn't know that before :P). Well, as a try, I went and put it on a Windows XP Professional machine (no service pack, and the Microsoft uxtheme.dll is un-patched). When I rebooted with the ReactOS DLL, Windows XP freezes at the welcome screen, the start up sound doesn't even play. So I'm wondering if uxtheme.dll isn't complete yet or if it's already known to have problems. -- Mike

6 7

freeldr questions
by vit-ros＠att.net 14 Sep '05

14 Sep '05

Few questions about freeldr - Is there a compelling reason to have pointer members of LOADER_PARAMETER_BLOCK such as ModsAddr as ULONGs ? (include/ndk/haltypes.h) - Why the kernel module (ntoskrnl.exe) in not treated as such in the loader (there is a special case to create the corresponding module object in the kernel) ? - Why MachGetMemoryMap() is called twice: in freeldr/mm/meminit.c and in freeldr/reactos/reactos.c ? - wouldn't it be nicer to fix these ?

1 0

WaitNamedPipe bug? can anyone confirm?
by Luke Kenneth Casson Leighton 14 Sep '05

14 Sep '05

is WaitNamedPipe working, or have i got something wrong in my code? this is 0.2.7. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

1 0

msafd headers
by Mikhail Y. Zvyozdochkin 14 Sep '05

14 Sep '05

Hi All! Files on reactos/lib/msafd/misc/ uses header "msafd.h" from reactos/lib/msafd/. On my system, MinGW/linux successfully compiled these files ONLY after I manually corrected include directive: #include <../msafd.h> instead #include <msafd.h> in all 5 *.c files in reactos/lib/msafd/misc/. Maybe we must make this replacement in svn tree? Or it was my misconfiguration? ;) WBR, DarkHobbit

3 3

Testing ROS on VMWare With 32MB... Interesting Results
by TwoTailedFox 14 Sep '05

14 Sep '05

Been having a poke around, it seems neither LiveCD nor BootCD will boot into GUI (Using latest HEAD SVN), on 32MB. BootCD will complete first stage installer, but won't boot into GUI to load the second stage setup. LiveCD immediately hangs. Now, on VMWare, I use Other/Other as the OS Category, and I've been hearing some (like WaxDragon), using Windows XP Professional as the OS Category. I obtained a BootCD of 17751 rev, and tried it on the WinXP setting, using 32MB. First time I tried it, it hung at copying ole32.dll (34%). Second time, I got a STOP error during the file transfer. Third time, however, it completed the first stage fine. The only difference between the Other and WinXP Pro settings is the inclusion of a USB Controller. I added one to my "Other" setup, and ROS, again, installed fine first time around on 32MB. Now, for the interesting bit. The error is a pretty constant one, and it complains of No Memory Pages Available. It seems just common to the GUI, seeing as ROS won't boot on 32MB even once Setup is completed. This is the case for both SVN Live and BootCD's. Something in the GUI is causing a leak -- "I had a handle on life, but then it broke"

5 6

NamedPipes - cause massive reliability problems with services. what to _do_?
by Luke Kenneth Casson Leighton 14 Sep '05

14 Sep '05

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ipc/base/m… please note the comments "it is possible for a client to connect in between the CreateNamedPipe and ConnectPipe". in other words, NamedPipes don't have any equivalent of "listen()". this is a massive _massive_ problem, evidence of which i first encountered with "rpctorture --processes=100 --repeat-operation=100", back in 1998. out of 10,000 operations performed across 100 processes, about TWENTY of those operations would succeed. that's a success rate of 0.2%. (anyone who runs a lab where 400 students sit down at the beginning of a session and all log in to the same NT PDC will tell you _exactly_ what they bloody think of windows and it's the same issue) the reason why there is such an abysmal failure rate was not clear to me until today. it's due - quite simply - to this delay. if the server is particularly overloaded (due to having to deal with, oh i dunno, say, a large influx of incoming Named Pipe client requests) then the time delay between CreateNamedPipe and ConnectPipe is increased; if some idiot decides that the number of pipe connections is to be limited; if someone decides that the number of threads is to be limited, then the server quickly goes into meltdown. if there is protocol proxying or authentication going on (as is the case of SMB IPC$ providing MSRPC named pipes - ncacn_np for those people who know what that is) then you _really_ are in trouble. the question is: having access to the source code - in reactos - what can be _done_ about this? would it be reasonable to write - and use - a named pipes equivalent of "listen()"? alternatively, how in hell's name do you _deal_ with this sort of thing? l. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

1 0

Cant Install Self Compiled ISO
by Brandon Turner 13 Sep '05

13 Sep '05

I can't install any bootcd's that I compile, gives INACCESSIBLE_BOOT_DEVICE. This happens in Qemu, vmware, and virtual pc. I have done full clean builds by doing "make clean" and deleting the object/output folders. I don't know when this started happening really. But if i download the ISO off of CIA then its fine, the exact same version. I am compiling on Windows XP with ROSBe. Here is a link to a picture of the crash: www.brandonturner.org/crash.PNG Please help, its driving me crazy! Brandon

3 3

Binutils
by Casper Hornstrup 13 Sep '05

13 Sep '05

It seems that as of revision 17811, GNU ld version 2.15.90 20040222 is too old. Upgrade your binutils if you have that version. Casper

3 4

MC problem
by Hartmut Birr 13 Sep '05

13 Sep '05

Hi, if I compile MC (midnight commander ) with the option '-mpreferred-stack-boundary=2', the build-in editor doesn't work. MC hangs after pressing F4. This occurs on winXP and ROS. I've no problem without this option. - Hartmut

2 1

whoo-hooo!
by Luke Kenneth Casson Leighton 12 Sep '05

12 Sep '05

yippeee, i got NamedPipes - rpcclient.exe talking to lsarpcd.exe!! -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

1 0

New ReactOS Homepage - Status
by Klemens Friedl 12 Sep '05

12 Sep '05

New ReactOS Homepage - Status Mail-Content: * Status * Questions Homepage status: The homepage beta test started last week. Join #reactos-hp for more information. We will start reviewing and translating the content in a few days. Content List: http://www.reactos.com/wiki/index.php/New_Homepage_Content When this is done (approximatly one week) we will be able to relaunch the homepage! Homepage release date: "When it's done!" ;) Questions: 1) Should the homepage section be called ... ? a: developer b: development c: developing 2) Should the static homepage pages be ... ? a: valid HTML 4.01 b: valid XHTML 1.0 c: both variants (two versions) d: something else (e.g. xhtml 1.1) 3) What's your opinion about the following homepage content structure ... ? * Home * Community * Support * Developer / Developing / Development * myReactOS (more details: http://www.reactos.com/wiki/index.php/New_Homepage_Content ) a: okay, good structure b: ... -> then edit/add comments to the wiki page see link above !!! Klemens Friedl -- 5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail +++ GMX - die erste Adresse f�r Mail, Message, More +++

8 9

Kernel-mode COM required for Kernel Streaming (ks.sys)
by Andrew "Silver Blade" Greenwood 12 Sep '05

12 Sep '05

This is the most ugliest beast I've come across. Trying to implement parts of the Kernel Streaming (ks) stuff. I decided to start with portcls.sys. So far, it appears ks.h (the Kernel Streaming main header) isn't present in our include files (or w32api) and the official MS DDK version is 100KB + so that's a bit of a knock-out already. Anyway I had a poke around and stubbed a lot of the main portcls.sys functions. But I have no idea what I'm doing right now so it's pointless me trying. It appears to be built on COM - the MSDN documents describe "Kernel-mode COM" in the Audio and Video section. Obviously the standard COM calls can't be used in kernel-mode. And I found in kcom.h some declarations for functions such as KoCreateInstance (kernel mode version of CoCreateInstance?) yet I cannot find any references to it on Google. The sample drivers are written in C++, and appear to rely on kcom.h's C++ classes to get things done. There's just not a lot I can do as the foundation isn't even there for me to start implementing Kernel Streaming. And I have *no* idea how to use COM. So far it looks really really ugly. Can someone give me a hand? -Andrew

3 4

Re: [ros-diffs] [royce] 17819: msvc6 compatibility and small performance improvement in filename completion
by Hartmut Birr 12 Sep '05

12 Sep '05

royce(a)svn.reactos.com wrote: >msvc6 compatibility and small performance improvement in filename completion > >Modified: trunk/reactos/subsys/system/cmd/internal.c > > > *Modified: trunk/reactos/subsys/system/cmd/internal.c* > >--- trunk/reactos/subsys/system/cmd/internal.c 2005-09-12 14:55:55 UTC (rev 17818) >+++ trunk/reactos/subsys/system/cmd/internal.c 2005-09-12 16:06:53 UTC (rev 17819) >@@ -276,7 +276,7 @@ > > TCHAR * tmpPath; > TCHAR szCurrent[MAX_PATH]; > TCHAR szMsg[RC_STRING_MAX_SIZE]; > > >- INT i; > > >+ UINT i; > > > > > /* Filter out special cases first */ > > > ------------------------------------------------------------------------ If you change a variable from signed to unsigned, you have to check for comparing with zero or negativ values like this: /* Strip the paths back to the folder they are in */ for(i = (_tcslen(szFinalPath) - 1); i > -1; i--) - Hartmut

2 1

Re: [ros-svn] [royce] 17819: msvc6 compatibility and small performance improvement in filename completion
by Hartmut Birr 12 Sep '05

12 Sep '05

Hi, changing of a directory isn't possible after your changes. - Hartmut royce(a)svn.reactos.com wrote: >msvc6 compatibility and small performance improvement in filename completion > > >Updated files: >trunk/reactos/subsys/system/cmd/cmd.c >trunk/reactos/subsys/system/cmd/cmd.h >trunk/reactos/subsys/system/cmd/cmdinput.c >trunk/reactos/subsys/system/cmd/color.c >trunk/reactos/subsys/system/cmd/del.c >trunk/reactos/subsys/system/cmd/dir.c >trunk/reactos/subsys/system/cmd/echo.c >trunk/reactos/subsys/system/cmd/filecomp.c >trunk/reactos/subsys/system/cmd/history.c >trunk/reactos/subsys/system/cmd/internal.c >trunk/reactos/subsys/system/cmd/precomp.h > >_______________________________________________ >Ros-svn mailing list >Ros-svn(a)reactos.com >http://reactos.com:8080/mailman/listinfo/ros-svn > > >

1 0

Poll: Web Browsers
by Rick Langschultz 12 Sep '05

12 Sep '05

Hey everyone, I was just wondering how everyone got to reactos.com. I want to know what Browser version people use and the operating system and/or the operating system flavor you use. I know that many people are using Linux, Windows, etc. But some browsers don't support some features like some CSS tags and XMLHttprequest. But I was just wondering... Maybe the web-development team could include in the future loggin this and setting a cookie to not get 750 hits from the same computer so the developers could develop software that would benefits most users ie those that want to use firefox instead of IE and so on... Rick Langschultz rlangschultz(a)cox.net (Home) rlangschultz(a)ellemaespa.com (Work) rlangschultz(a)email.uophx.edu (School)

5 4

more HEAD crashing
by Royce Mitchell III 12 Sep '05

12 Sep '05

This time crash occured upon first movement of mouse during 2nd stage setup after "welcome" dialog had appeared ( hadn't touched mouse during bootup - if that makes a difference ) Looks like something related to the win32k refactoring maybe? Assertion 'hdr->RefCount >= 1' failed at subsys\win32k\ntuser\object.c line 282 Entered debugger on embedded INT3 at 0x0008:0x800ab2b0. kdb:> regs CS:EIP 0x0008:0x800ab2b1 SS:ESP 0x45bc:0x800b4cdc EAX 0x00000050 EBX 0x0000117d ECX 0x00000000 EDX 0x000003f8 ESI 0x0064fc60 EDI 0x9e40bd74 EBP 0x9e40bbdc EFLAGS 0x00000282 SF IF IOPL0 kdb:> bt Eip: <ntoskrnl.exe:ab2b1 ({standard input}:23 ())> Frames: <win32k.sys:abe21 (subsys/win32k/ntuser/object.c:282 (ObmDereferenceObject))> <win32k.sys:8568f (subsys/win32k/ntuser/message.c:799 (co_IntPeekMessage))> <win32k.sys:85c52 (subsys/win32k/ntuser/message.c:995 (NtUserGetMessage))> <ntoskrnl.exe:93ec2 ({standard input}:177 (KiSystemService))> <user32.dll:51a53 (lib/user32/windows/message.c:1166 (GetMessageW))> <comctl32.dll:3d024 (lib/comctl32/propsheet.c:2770 (do_loop))> <comctl32.dll:3d40d (lib/comctl32/propsheet.c:2897 (PropertySheetW))> <syssetup.dll:4185 (lib/syssetup/wizard.c:1481 (InstallWizard))> <syssetup.dll:1d39 (lib/syssetup/install.c:494 (InstallReactOS))> <setup.exe:1355 (subsys/system/setup/setup.c:86 (RunNewSetup))> <setup.exe:13c0 (subsys/system/setup/setup.c:122 (WinMain))> <setup.exe:14eb (subsys/system/setup/setup.c:123 (WinMain))> <setup.exe:120d> <setup.exe:1258> <KERNEL32.dll:307d5 (lib/kernel32/process/create.c:68 (BaseProcessStartup))> <00000000> kdb:>

2 3

Universal Kernel?
by Rick Langschultz 12 Sep '05

12 Sep '05

Hey everyone, I have a feature suggestion for version 1.0 or later... I think it would be called the universal kernel. The kernel could be compiled and made to run on various architectures: ia_32, ia_64, PPC, XBOX, PPC64, etc. The computer would translate natively compiled files from other systems into ia_32 or ia_64 code. I know that Windows XP (64 bit) uses WoW which allows 32 bit programs to access 64bit memory or something like that. This way reactos could be installed on a variety of systems with one installation disc instead of a flavor of that disc. Just a suggestion for the future... Rick Langschultz rlangschultz(a)cox.net (Home) rlangschultz(a)ellemaespa.com (Work) rlangschultz(a)email.uophx.edu (School)

7 10

RE: [ros-dev] Poll: Web Browsers
by Murphy, Ged (Bolton) 12 Sep '05

12 Sep '05

Rick Langschultz wrote: > I was just wondering how everyone got to reactos.com. I want to know > what Browser version people use and the operating system and/or the > operating system flavor you use. > I'll play along :) SuSE 9.3, Fedora Core 4 and Win XP .... All running Firefox 1.0.6 ************************************************************************ 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] [ion] 17811: Major refactoring of the exception handling code + misc fixes:
by Hartmut Birr 12 Sep '05

12 Sep '05

Hi, calling RaiseException(EXCEPTION_ACCESS_VIOLATION, EXCEPTION_NONCONTINUABLE, 0, NULL) from user mode does crash reactos. - Hartmut (lib\rtl\exception.c:29) RtlRaiseException(Status 0064fea8) (lib\rtl\exception.c:36) ExceptionAddress 7c801fcc (ntoskrnl\ke\exception.c:94) KiRaiseException (ntoskrnl\ke\i386\exp.c:933) KiDispatchException() called (lib\rtl\exception.c:75) RtlRaiseStatus(Status 0x80000002) (lib\rtl\i386\exception.c:59) RtlDispatchException(): 87032998, 870326c8 (lib\rtl\i386\exception.c:64) RegistrationFrame is 0x87032D30 (lib\rtl\i386\exception.c:90) Invalid exception frame (ntoskrnl\ke\exception.c:94) KiRaiseException (ntoskrnl\ke\i386\exp.c:933) KiDispatchException() called KeBugCheckWithTf at ntoskrnl\ke\i386\exp.c:993 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 (0x80000002,0x80072fba,0x00000001,0x870329f0) *** ntoskrnl.exe - Address 0x80072fba base at 0x80000000, DateStamp 0x0 Divide Error Exception: 0(0) Processor: 0 CS:EIP 8:80072fba <ntoskrnl.exe:72fba (ntoskrnl/mm/virtual.c:1002 (ProbeForRead))> cr2 0 cr3 178f9000 Proc: 81ad12d0 Pid: 15c <t.EXE> Thrd: 81a691d8 Tid: 160 DS 10 ES 10 FS 30 GS 0 EAX: 870326c8 EBX: 81a691d8 ECX: 00000000 EDX: 000002f8 EBP: 81a691d8 ESI: 0064fbc4 ESP: 87032644 EDI: 87032d74 EFLAGS: 00000282 kESP 87032644 kernel stack base 87030000 Frames: <0>

2 2

lib/crt/stdlib/strtoull.c
by Mark Junker 11 Sep '05

11 Sep '05

Hi, is s/o interested in a working implementation of strtoull? I submitted a patch 4 or 5 months ago but it wasn't added yet so I retry my submission. Regards, Mark Index: crt.xml =================================================================== --- crt.xml (revision 17794) +++ crt.xml (working copy) @@ -317,6 +317,7 @@ <file>senv.c</file> <file>strtod.c</file> <file>strtoul.c</file> + <file>strtoull.c</file> <file>swab.c</file> <file>wcstod.c</file> <file>wcstombs.c</file> Index: stdlib/strtoull.c =================================================================== --- stdlib/strtoull.c (revision 17794) +++ stdlib/strtoull.c (working copy) @@ -1,24 +1,38 @@ /* Copyright (C) 1996 DJ Delorie, see COPYING.DJ for details */ /* Copyright (C) 1994 DJ Delorie, see COPYING.DJ for details */ +#include <windows.h> #include <limits.h> #include <ctype.h> #include <errno.h> #include <stdlib.h> -//#include <msvcrt/unconst.h> +#include <internal/file.h> +/*#include <msvcrt/unconst.h>*/ +#if defined(LONG_LONG_MAX) +#define ULONGLONG_MAX ULONG_LONG_MAX +#elif defined(_UI64_MAX) +#define ULONGLONG_MAX _UI64_MAX +#elif defined(ULLONG_MAX) +#define ULONGLONG_MAX ULLONG_MAX +#else +/* FIXME: There must be a better way because LONGLONG might be defined as + * double. */ +#define ULONGLONG_MAX ((ULONGLONG) (LONGLONG) -1) +#endif + /* * Convert a string to an unsigned long integer. * * Ignores `locale' stuff. Assumes that the upper and lower case * alphabets and digits are each contiguous. */ -unsigned long +ULONGLONG strtoull(const char *nptr, char **endptr, int base) { const char *s = nptr; - unsigned long acc; + ULONGLONG acc; int c; - unsigned long cutoff; + ULONGLONG cutoff; int neg = 0, any, cutlim; /* @@ -43,8 +57,8 @@ } if (base == 0) base = c == '0' ? 8 : 10; - cutoff = (unsigned long)ULONG_MAX / base; - cutlim = (unsigned long)ULONG_MAX % base; + cutoff = ULONGLONG_MAX / base; + cutlim = (int) (ULONGLONG_MAX % base); for (acc = 0, any = 0;; c = *s++) { if (isdigit(c)) @@ -65,7 +79,7 @@ } if (any < 0) { - acc = ULONG_MAX; + acc = ULONGLONG_MAX; __set_errno ( ERANGE ); } else if (neg)

3 3

r17754 crash in UsbMpInitMultiSzString
by Royce Mitchell III 11 Sep '05

11 Sep '05

I rebuilt the bootcd, and installed on vmware - reformatted the hdd during setup, and got this on first boot-up. I have the virtual machine suspended if any other debug info is needed. (ntoskrnl\ke\main.c:289) --------------------------------------------------------------- (ntoskrnl\ke\main.c:290) ReactOS 0.3-SVN (Build 20050908-r17754) Used memory 65536Kb (ntoskrnl\mm\mminit.c:375) Kernel Stack Limits. InitTop = 0x8011c000, Init = 0x80119000 (ntoskrnl\mm\mm.c:283) No current process Entered debugger on embedded INT3 at 0x0008:0x800c6811. kdb:> cont (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\pcnet.sys (ntoskrnl\io\pnpmgr.c:1847) Initialization of service PCNet failed (Status c0000001) (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\System32\DRIVERS\usbuhci.sys (ntoskrnl\io\pnpmgr.c:1847) Initialization of service usbuhci failed (Status c0000001) (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\pcnet.sys (ntoskrnl\io\pnpmgr.c:1847) Initialization of service PCNet failed (Status c0000001) (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\System32\DRIVERS\usbuhci.sys (ntoskrnl\io\pnpmgr.c:1847) Initialization of service usbuhci failed (Status c0000001) (ntoskrnl\ldr\loader.c:252) Could not open module file: \SystemRoot\system32\drivers\ne2000.sys (ntoskrnl\io\pnpmgr.c:1847) Initialization of service Ne2000 failed (Status c0000001) (ntoskrnl\io\pnpmgr.c:1847) Initialization of service serial failed (Status c0000034) (ntoskrnl\io\pnpmgr.c:1847) Initialization of service serial failed (Status c0000034) (ntoskrnl\io\driver.c:1274) Driver 'buslogic.sys' load failed, status (c0000001) (ntoskrnl\io\pnpmgr.c:1847) Initialization of service serial failed (Status c0000034) (ntoskrnl\io\pnpmgr.c:1847) Initialization of service serial failed (Status c0000034) (drivers\usb\usbport\usbcore.c:15) Miniport 0x80735BF0 registered (drivers\usb\miniport\common\fdo.c:247) USBMP: unknown minor function 0x8 (drivers\usb\miniport\sys\linuxwrapper.c:479) IoGetDmaAdapter done 0x8074FC40, mapRegisterCount=2 (drivers\usb\miniport\usbuhci\uhci-hcd.c:2556) INF: drivers\usb\miniport\usbuhci\uhci-hcd.c: USB Universal Host Controller Interface driver v2.1 (drivers\usb\usbport\hcd-pci.c:74) usbcore: usb_hcd_pci_probe() called (drivers\usb\miniport\sys\linuxwrapper.c:201) driver_register 0: 9cf5f0b8 9cf56ec4(drivers\usb\usbport\usb.c:166) INF: drivers\usb\usbport\usb.c: registered new driver hub (drivers\usb\miniport\sys\li(drivers\usb\usbport\hub.c:1230) hub_thread startingnuxwrapper.c:137) usbcore: Created system thread 60 (drivers\usb\miniport\sys\linuxwrapper.c:201) driver_register 1: 9cf5f0e0 9cf56eb0(drivers\usb\usbport\hcd-pci.c:74) usbcore: usb_hcd_pci_probe() called (drivers\usb\usbport\/../miniport/linux/pci_hal.c:13) pci_enable_device() called... (drivers\usb\usbport\/../miniport/linux/pci_hal.c:44) pci_resource_flags() called, x=0x0 (drivers\usb\usbport\/../miniport/linux/pci_hal.c:21) pci_resource_start() called, x=0x0 (drivers\usb\usbport\/../miniport/linux/pci_hal.c:33) pci_resource_len() called, x=0x0 (drivers\usb\usbport\/../miniport/linux/pci_hal.c:86) request_region(): addr=0x1060, len=0x20 (drivers\usb\usbport\/../miniport/linux/pci_hal.c:58) pci_set_drvdata() called... (drivers\usb\usbport\hcd-pci.c:163) UnivHCI PCI-USB Controller (drivers\usb\usbport\hcd-pci.c:183) irq 9, io base 00001060 (drivers\usb\usbport\hcd.c:678) new USB bus registered, assigned bus number 1 (drivers\usb\miniport\usbuhci\/../linux/pci_hal.c:33) pci_resource_len() called, x=0x0 (drivers\usb\miniport\sys\linuxwrapper.c:252) schedule_timeout: 5 ms (drivers\usb\miniport\sys\linuxwrapper.c:286) schedule DONE!!!!!! (drivers\usb\miniport\sys\linuxwrapper.c:252) schedule_timeout: 1 ms (drivers\usb\miniport\sys\linuxwrapper.c:286) schedule DONE!!!!!! (drivers\usb\miniport\sys\linuxwrapper.c:793) pci_alloc_consistent() size=8196 (drivers\usb\miniport\sys\linuxwrapper.c:639) pci_pool_create(): UHCD PCI Slot/uhci_td size 48, 85/page (4096 alloc) (drivers\usb\miniport\sys\linuxwrapper.c:639) pci_pool_create(): UHCD PCI Slot/uhci_qh size 48, 85/page (4096 alloc) (drivers\usb\miniport\usbuhci\uhci-hcd.c:2264) INF: drivers\usb\miniport\usbuhci\uhci-hcd.c: detected 2 ports (drivers\usb\usbport\hcd.c:400) root hub device address 1 (drivers\usb\miniport\sys\ros_wrapper.c:8) wait_ms(10) (drivers\usb\usbport\config.c:274) DBG: drivers\usb\usbport\config.c: kmalloc IF 8cd05d48, numif 1 (drivers\usb\usbport\usb.c:1215) new device strings: Mfr=3, Product=2, SerialNumber=1 (drivers\usb\usbport\message.c:1008) DBG: drivers\usb\usbport\message.c: USB device number 1 default language ID 0x409 (drivers\usb\usbport\usb.c:1051) Product: UnivHCI PCI-USB Controller (drivers\usb\usbport\usb.c:1059) Manufacturer: XBOX ---- uhci-hcd (drivers\usb\usbport\usb.c:1086) USB connected: UnivHCI PCI-USB Controller (XBOX ---- uhci-hcd) (drivers\usb\usbport\usb-debug.c:184) SerialNumber: UHCD PCI Slot (drivers\usb\miniport\sys\linuxwrapper.c:167) drv_num 2 9cf56ec4 9cf56eb0 (drivers\usb\usbport\usb.c:1255) .........................usb_new_device: usb-UHCD PCI Slot-0 interface 0 (drivers\usb\usbport\usb.c:1257) usb_new_device - registering interface 1-0:0 (drivers\usb\miniport\sys\linuxwrapper.c:167) drv_num 2 9cf56ec4 9cf56eb0 (drivers\usb\miniport\sys\linuxwrapper.c:181) probe0 9cf56ec4 (drivers\usb\usbport\usb.c:93) usb_device_probe (drivers\usb\usbport\usb.c:103) usb_device_probe - got id (drivers\usb\usbport\hub.c:631) USB hub found (drivers\usb\usbport\hub.c:390) 2 ports detected (drivers\usb\usbport\hub.c:405) standalone hub (drivers\usb\usbport\hub.c:409) ganged power switching (drivers\usb\usbport\hub.c:422) global over-current protection (drivers\usb\usbport\hub.c:472) Port indicators are not supported (drivers\usb\usbport\hub.c:478) power on to power good time: 6ms (drivers\usb\usbport\hub.c:480) hub controller current requirement: 0mA (drivers\usb\usbport\hub.c:490) local power source is good (drivers\usb\usbport\hub.c:493) no over-current condition exists (drivers\usb\usbport\hub.c:521) hub_thread should woke up (drivers\usb\usbport\hub.c:309) enabling power on all ports (drivers\usb\miniport\sys\ros_wrapper.c:8) wait_ms(0) (drivers\usb\miniport\sys\ros_wrapper.c:8) wait_ms(0) (drivers\usb\miniport\sys\ros_wrapper.c:8) wait_ms(6) (drivers\usb\miniport\sys\linuxwrapper.c:181) probe1 9cf56eb0 (drivers\usb\miniport\sys\linuxwrapper.c:201) driver_register 2: 9cf5f268 9cf56ec4(drivers\usb\usbport\usb.c:166) INF: drivers\usb\usbport\usb.c: registered new driver keyboard (drivers\usb\miniport\sys\linuxwrapper.c:201) driver_register 3: 9cf5f2e8 9cf56ec4(drivers\usb\usbport\usb.c:166) INF: drivers\usb\usbport\usb.c: registered new driver usbmouse Entered debugger on last-chance exception number 14 (Page Fault) Memory at 0x101c0000 could not be read: Page not present. kdb:> bt [7hEip: <usbuhci.sys:9485 (drivers/usb/miniport/common/misc.c:91 (UsbMpInitMultiSzString))> Frames: <usbuhci.sys:98f0 (drivers/usb/miniport/common/pdo.c:112 (UsbMpPdoQueryId))> <usbuhci.sys:9b15 (drivers/usb/miniport/common/pdo.c:293 (UsbMpPnpPdo))> <usbuhci.sys:90d9 (drivers/usb/miniport/common/main.c:337 (DispatchPnp))> <ntoskrnl.exe:425ef (ntoskrnl/io/irp.c:1080 (IofCallDriver))> <ntoskrnl.exe:45163 (ntoskrnl/io/pnpmgr.c:752 (IopInitiatePnpIrp))> <ntoskrnl.exe:45e72 (ntoskrnl/io/pnpmgr.c:1398 (IopActionInterrogateDeviceStack))> <ntoskrnl.exe:451d8 (ntoskrnl/io/pnpmgr.c:782 (IopTraverseDeviceTreeNode))> <ntoskrnl.exe:4520b (ntoskrnl/io/pnpmgr.c:796 (IopTraverseDeviceTreeNode))> <ntoskrnl.exe:4524e (ntoskrnl/io/pnpmgr.c:822 (IopTraverseDeviceTree))> <ntoskrnl.exe:469f2 (ntoskrnl/io/pnpmgr.c:2014 (IopInvalidateDeviceRelations))> <ntoskrnl.exe:314e6 (ntoskrnl/io/device.c:162 (IopStartDevice))> <ntoskrnl.exe:46782 (ntoskrnl/io/pnpmgr.c:1831 (IopActionInitChildServices))> <ntoskrnl.exe:46815 (ntoskrnl/io/pnpmgr.c:1871 (IopActionInitAllServices))> <ntoskrnl.exe:451d8 (ntoskrnl/io/pnpmgr.c:782 (IopTraverseDeviceTreeNode))> <ntoskrnl.exe:4520b (ntoskrnl/io/pnpmgr.c:796 (IopTraverseDeviceTreeNode))> <ntoskrnl.exe:4520b (ntoskrnl/io/pnpmgr.c:796 (IopTraverseDeviceTreeNode))> <ntoskrnl.exe:4524e (ntoskrnl/io/pnpmgr.c:822 (IopTraverseDeviceTree))> <ntoskrnl.exe:4687e (ntoskrnl/io/pnpmgr.c:1931 (IopInitializePnpServices))> <ntoskrnl.exe:c8fe8 (ntoskrnl/io/iomgr.c:421 (IoInit3))> <ntoskrnl.exe:c6838 (ntoskrnl/ex/init.c:651 (ExpInitializeExecutive))> <ntoskrnl.exe:6706 (ntoskrnl/ke/main.c:100 (KiSystemStartup))>--- Press q to abort, any other key to continue --- <ntoskrnl.exe:c484e (ntoskrnl/ke/main.c:294 (_main))> <ntoskrnl.exe:104b ({standard input}:47 (_section_alignment__))> Couldn't access memory at 0x000764f8! kdb:> regs CS:EIP 0x0008:0x9cf16485 SS:ESP 0x0010:0x8011a5c0 EAX 0x101c0000 EBX 0x0007651c ECX 0x0000000c EDX 0x8011a5e8 ESI 0x0007661c EDI 0x00076514 EBP 0x8011a600 EFLAGS 0x00200296 PF AF SF IF IOPL0 ID kdb:>

1 0

How to boot using Grub
by Saravanan Jayakumar 11 Sep '05

11 Sep '05

Hi All, Can anyone please let me know the instrcutions as of how to boot reactOS using GRUB.Your help is appreciated. regards Jay

2 1

Compilation failed due to strcasecmp related problems
by Mark Junker 11 Sep '05

11 Sep '05

Hi, some compilations failed because strcasecmp is already declared in my MinGW installation. The work-around was to define HAVE_STRCASECMP in rosapps/mc/src/util.c (Midnight Commander) and in reactos/include/wine/config.h. Regards, Mark

1 0

Re: subauth.h
by Luke Kenneth Casson Leighton 11 Sep '05

11 Sep '05

On Sun, Sep 11, 2005 at 11:07:23AM +0900, Mike McCormack wrote: > > Luke Kenneth Casson Leighton wrote: > >oh maaan, that's really sad: i know what the stuff in subauth.h is all > >about, aaaaagh! > > Looking at the title of the post, I mistakenly thought that you posted a > patch for a moment... ha, sorry mike :) not yet. many windowisms to learn, which i am hoping to avoid by someone else picking up the initiative. i'm focussing on getting samba tng into reasonable shape - compiling everything under mingw32 is the first step - such that it can be plugged into an implementation of msv1_0.dll. however i am not holding out forever waiting for someone else to start msv1_0.dll. so i'm trying to track down "LsaAp"s to see if anyone - outside of microsoft - has ever written one of these. l. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

1 0

argh!!! who's implementing advapi/sec/lsa.c??
by Luke Kenneth Casson Leighton 11 Sep '05

11 Sep '05

argh! please whoever is implementing advapi32 lsa.c please look at samba tng's lsarpcd service. argh! -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

2 1

oh maaaaaan!! which mad bugger started implementing SAM!!
by Luke Kenneth Casson Leighton 10 Sep '05

10 Sep '05

okay. who's the nutcase that's been implementing libsam - i _hope_ you looked at samba tng's "samrd" source code!!!! l. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

2 1

lib/netapi32/access.c and friends
by Luke Kenneth Casson Leighton 10 Sep '05

10 Sep '05

these are standard smbclient-related and/or rpcclient-related functions. NetUserGetInfo grabs the information from a NET_USER_INFO_3 structure which is "cached" from the MSV1_0.DLL access token for example (it's a really long story). NetShareEnum() is a LANMAN function, whoopeee what fun. in nt, there are _stacks_ of functions that tie pretty much directly into samba source code. l. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

1 0

subauth.h
by Luke Kenneth Casson Leighton 10 Sep '05

10 Sep '05

oh maaan, that's really sad: i know what the stuff in subauth.h is all about, aaaaagh! it is incredibly similar to the MSRPC "NETLOGON" stuff that's implemented in cli_nt_login_interactive, cli_nt_login_network and cli_nt_login_generic in rpc_client/cli_login.c joy. l. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

1 0

SSPI stuff... not ... _entirely_ relevant to MSV1_0.DLL but hey...
by Luke Kenneth Casson Leighton 10 Sep '05

10 Sep '05

http://win32.mvps.org/security/sspi.html this is getting really obscure... -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

1 0

mooore MSV1_0.DLL
by Luke Kenneth Casson Leighton 10 Sep '05

10 Sep '05

http://computer.programming-in.net/articles/dll-api.aspx?dll=msv1_0 just some stuff about the export ordinals. l. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

1 0

MSV1_0.DLL
by Luke Kenneth Casson Leighton 10 Sep '05

10 Sep '05

... anyone speak russian? http://www.void.ru/content/720 -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

1 0

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