Yes. You are not, sorry for the outburst.
It occurs that my problem was due to GMail scripts targetting Opera
specifically. Got an addon for it to pose as Firefox and guess what?
Problem's gone.
Thank you gmail, i`m moving away.
Regards
2011/6/5 Riccardo Bestetti <riccardo.kyogre(a)live.it>
> Yes, I probably missed his previous email, but this isn’t a good reason
> to say that I am deficient.
> Now please, let’s stop to discuss [image: Sorriso]
>
> *From:* Ameen Ross <a.ross(a)amdev.eu>
> *Sent:* Sunday, June 05, 2011 4:04 PM
> *To:* ros-dev(a)reactos.org
> *Subject:* Re: [ros-dev] 1294 [dreimer] Fix clean for cmake trees. ...
>
> You missed his previous mail ;)
> He said that he emails with lots of replies were almost unreadable and
> requested to remove what's not needed.
>
> On 06/05/2011 03:58 PM, Riccardo Bestetti wrote:
>
> I wasn’t talking to you, we was talking about browsers and I told what IE
> does on my PC.
> Here the deficient is you.
>
> *From:* Olaf Siejka <caemyr(a)gmail.com>
> *Sent:* Sunday, June 05, 2011 3:07 PM
> *To:* ReactOS Development List <ros-dev(a)reactos.org>
> *Subject:* Re: [ros-dev] 1294 [dreimer] Fix clean for cmake trees. ...
>
> Are you being a person intellectually deficient? Or just provoking me on
> any purpose?
>
> 2011/6/5 Riccardo Bestetti <riccardo.kyogre(a)live.it>
>
>> I can’t start IE on a Turion X2 @2GHz, 4GB ram (win 7), because it
>> literally eats my CPU.
>> It crashes my PC. It is terrible.
>> Firefox works fine.
>>
> [whole bunch of trash deleted]
> ------------------------------
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
> _______________________________________________
> Ros-dev mailing listRos-dev@reactos.orghttp://www.reactos.org/mailman/listinfo/ros-dev
>
> ------------------------------
> _______________________________________________
> 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
>
Hi,
I know that for some open source projects React OS sign's windows drivers.
Could you please sign the driver for virtual floppy drive?
Motivation:
Virtual Floppy drive is very helpfull, for example take freedos floppy image,
include Samsung SpinPoint F4 EcoGreen HD204UI firmware update into the image
and put it with unetbootin on usb stick.
Problem: virtual floppy drive didn't run on windows 7 x64 because the need of
driver signing.
Homepage:
http://vfd.sourceforge.net/
Description:
>This is a virtual floppy drive for Windows NT / 2000 / XP developed by Ken Kato
>(Reported to work also on 2003 Server and Vista). <-- and windows 7 x86, too.
>
>You can mount a floppy image file as a virtual floppy drive and directly access the contents --
>view, edit, rename, delete or create files on a virtual floppy, format a virtual floppy,
>launch a program on a virtual floppy... almost anything you can do with a real floppy.
vfdwin x64 driver build (unsigned) from "critical0"
http://sourceforge.net/projects/vfd/files/2.1%20(February%2006%2C%202008)/v…
vfdwin x64 driver build (unsigned) from "Igor Levicki"
http://levicki.net/downloads/sendfile.php?path=vfd_x64/vfd_x64.zip
Discussion about the different versions:
http://levicki.net/articles/stories/2007/08/17/The_story_of_the_vfdwin_21_6…
greetings
Carsten
dreimer(a)svn.reactos.org wrote:
> if not exist "CMakeLists.txt" (
Can we decide on dropping support for rbuild stuff in RosBE 2.0?
Reasons:
- RosBE 2.0 will certainly come with an updated set of build tools.
(GCC 4.6 with mingw-w64 target is planned, maybe even a multilib
version)
The target change already makes older builds uncompilable with RosBE
2.0. Even if this would be fixed, nobody would guarantee you that a
revision built with RosBE 2.0 behaves the same as one compiled with
1.5.x.
- Several versions of RosBE can be installed parallely, especially if
you're also moving to a Windows Installer for RosBE 2.0, which doesn't
care about Uninstall entries of NSIS. So everybody has the option
to build older rbuild-powered revisions at any time.
- It could make all scripts cleaner again :-)
Regards,
Colin
dreimer(a)svn.reactos.org wrote:
> Get the cmake path from a system variable called _ROSBE_CMAKEPATH.
I hope we're not thinking about requiring the user to install RosBE and
CMake separately.
This would pretty much kill the point of RosBE if people are forced to
get random versions of their build tools from multiple sources again..
- Colin
Same comment as before, resources MUST be acquired within a critical region (as the old code did).
--
Best regards,
Alex Ionescu
On 2011-06-02, at 1:43 PM, pschweitzer(a)svn.reactos.org wrote:
> /* Acquire the FS lock */
> - KeEnterCriticalRegion();
> - ExAcquireResourceExclusiveLite(&FileSystemListLock, TRUE);
> + ExAcquireResourceExclusiveLite(&IopDatabaseResource, TRUE);
jgardou(a)svn.reactos.org wrote:
> - set(_gch_filename "${_target_name}_${_FILE}.gch")
> + set(_gch_filename "${_FILE}.gch")
Looks like we're going through the same mess of GNU precompiled headers,
which we already had in rbuild:
1) Giving the GCH file a custom name.
Problem: It is simply ignored in the build process.
2) Just renaming it to the name of the header file.
Problem: If two modules use the same header file with different
build options (like #defines), the compiler can only choose one
precompiled header and we have a corrupted build.
The solution now is to give every GCH file an individual directory whose
name contains the module name (like ".gch_smlib", this is what we
currently have in rbuild).
Concluding from what I see in rbuild, please also note that the GCH file
needs to be named "header.h.gch", not "header.gch". Your ${basename}
variable sounds like this is not done either in the CMake branch.
- Colin
You are rebrowsing the *whole* list, yet the caller gave you an argument (DriverObjectListSize) that indicated to you how large his array is.
You should browse the minimum of the whole list while making sure that "Index" does not grow larger than DriverObjectListSize / sizeof(pointer).
Right now the function is overwriting memory possibly.
This is because + /* Then, check if given buffer is big enough to contain list */
+ if (ListSize > DriverObjectListSize / sizeof(PDRIVER_OBJECT))
+ {
+ Status = STATUS_BUFFER_TOO_SMALL;
+ }
+ else
is incorrect. The function attempts to write as many entries as possible instead of failing.
As per the docs:
" Note that if the array at DriverObjectList is too small, the number of driver object pointers that are copied into the array will be less than ActualNumberDriverObjects."
--
Best regards,
Alex Ionescu
On 2011-06-02, at 1:43 PM, pschweitzer(a)svn.reactos.org wrote:
> + /* Rebrowse the whole list */
> + ListEntry = IopFsNotifyChangeQueueHead.Flink;
> + while (ListEntry != &IopFsNotifyChangeQueueHead)
> + {
As per elementary Windows Driver Development basics, resources should ALWAYS be acquired within a critical or guarded region.
--
Best regards,
Alex Ionescu
On 2011-06-02, at 1:43 PM, pschweitzer(a)svn.reactos.org wrote:
> + /* Acquire the FS lock */
> + ExAcquireResourceExclusiveLite(&IopDatabaseResource, TRUE);
You misunderstand the meaning of the parameter. The last entry is the RAW file system. This parameter influences if RAWFS should be notified or not.
--
Best regards,
Alex Ionescu
On 2011-06-02, at 1:43 PM, pschweitzer(a)svn.reactos.org wrote:
> + /* Check if we reached end and if we have to skip it */
> + if (ListEntry->Flink == ListHead && SkipLast)
> + {
You need to cast to volatile.
(Same for Increment).
There's also no need to return the old value.
--
Best regards,
Alex Ionescu
On 2011-06-02, at 1:43 PM, pschweitzer(a)svn.reactos.org wrote:
> + OldValue = (*Ulong)--;
With all my respect to the hard work put into this, I want to express
my concerns:
Why is there a need to develop a half-done fdc, if there is a full,
working, tested by millions driver available even in old DDKs, which
we can use without violating its license?
Why waste time writing that driver from scratch now when we could
just import DDK's one and spend time fixing our PnP manager instead,
and other involved components so that DDK's driver actually works?
Again, with all my respect to Cameron, he does a great job, but when
he disappears next time for a year or two, who is going to finish
FDC? Or any other of his half-finished branches? (each being really a
pearl if it's done).
I would really suggest using all available resources first and only
then spend time developing our own stuff instead of already existing.
Thanks for understanding,
Aleksey.
On Jun 2, 2011, at 10:24 AM, cgutman(a)svn.reactos.org wrote:
> Author: cgutman
> Date: Thu Jun 2 06:24:25 2011
> New Revision: 52055
>
> URL: http://svn.reactos.org/svn/reactos?rev=52055&view=rev
> Log:
> [FDC]
> - Implement fdc.sys (still needs work but fairly complete)
> [TXTSETUP.SIF]
> - Load fdc.sys for floppy controllers
> [FDC.INF]
> - Install fdc.sys for floppy controllers
>
> Added:
> trunk/reactos/drivers/storage/fdc/CMakeLists.txt (with props)
> trunk/reactos/drivers/storage/fdc/directory.rbuild (with props)
> trunk/reactos/drivers/storage/fdc/fdc/CMakeLists.txt (with
> props)
> trunk/reactos/drivers/storage/fdc/fdc/SOURCES (with props)
> trunk/reactos/drivers/storage/fdc/fdc/fdc.c (with props)
> trunk/reactos/drivers/storage/fdc/fdc/fdc.h (with props)
> trunk/reactos/drivers/storage/fdc/fdc/fdc.rbuild (with props)
> trunk/reactos/drivers/storage/fdc/fdc/fdc.rc (with props)
> trunk/reactos/drivers/storage/fdc/fdc/fdo.c (with props)
> trunk/reactos/drivers/storage/fdc/fdc/pdo.c (with props)
> Modified:
> trunk/reactos/boot/bootdata/txtsetup.sif
> trunk/reactos/drivers/storage/CMakeLists.txt
> trunk/reactos/drivers/storage/directory.rbuild
> trunk/reactos/media/inf/fdc.inf
>
Hi, I'm one of the authors of hivex, a program for reading Windows
registry hive files:
http://libguestfs.org/hivex.3.html
The library can't currently read ReactOS hive files. I'm *very*
hestitant to say anyone is "wrong" here since the documentation for
hive files is obviously non-existent, but it appears that ReactOS
doesn't fill in the end_pages field in the header, and instead relies
on the size of the file itself.
For example, a hive downloaded from a fresh ReactOS install:
hivex_open: header fields:
file version 1.3
sequence nos 3 3
(sequences nos should match if hive was synched at shutdown)
original file name
(only 32 chars are stored, name is probably truncated)
root offset 0x70 + 0x1000
** end of last page 0x1000 + 0x1000 (total file size 0x22000)
checksum 0x8dc38fdf (calculated 0x8dc38fdf)
Notice that "end of last page" field is 0x1000, versus a completely
different file size.
hivex currently refuses to read past the end_pages limit, and we are
able to read every Windows hive that has ever been thrown at us.
If I hack hivex so that it ignores end_pages and simply uses the size
of the file as a guide, then hivex can successfully read the whole of
the file.
However I'm a bit unwilling to make this change to hivex just for
ReactOS, since it works fine with real Windows already.
So I wonder if this could just be a mistake in ReactOS or if there's
some deeper reason that I'm missing.
TIA,
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://et.redhat.com/~rjones/virt-df/
May Meeting Minutes
2011-05-26
20:05 UTC
Freenode, #reactos-meeting
Participants
=============
- Aleksey Bragin
- Art Yerkes
- Cameron Gutman
- Claudiu Mihail
- Colin Finck
- Gabriel Ilardi
- Ged Murphy
- Giannis Adamopoulos
- James Tabor
- Jan Blomqvist Kinander
- Javier Agustìn Fernàndez Arroyo
- Johannes Anderwald
- Kamil Hornicek
- Maciej Bialas
- Matthias Kupfer
- Neeraj Yadav
- Olaf Siejka
- Pierre Schweitzer
- Rafal Harabien
- Samuel Serapion
- Sylvain Petreolle
- Thomas Faber
- Timo Kreuzer
- Victor Martinez
- Ziliang Guo
Proceedings
============
○ Meeting called to order at 20:05 UTC by Aleksey Bragin.
○ Point 1: Status of our GSoC participation
--------------------------------------------
■ ReactOS' GSoC administrator Ged Murphy gave a quick update about
individual participants:
- Timo Kreuzer is way ahead of the timeline and already has his
font driver working under Windows. He later showed these
screenshots:
* http://imageshack.us/photo/my-images/156/ftfd.png/
* http://imageshack.us/photo/my-images/5/roxxc.png/
* http://imageshack.us/photo/my-images/220/wtfishappening.png/
* http://imageshack.us/photo/my-images/199/ie1d.png/
The major remaining work is implementing the appropriate interface
to make the font driver usable under ReactOS.
- Giannis Adamopoulos is also progressing well and has already
committed a lot of code regarding theming. He later showed these
screenshots:
* http://img846.imageshack.us/img846/8500/theme2.png
* http://img88.imageshack.us/img88/9660/theme3v.png
* http://img691.imageshack.us/img691/7425/theme1c.jpg
- Thomas Faber, who works on the kernel-mode test suite, has been
pretty quiet so far, but is considered a trustworthy person who
knows what he is doing and does not need much help from the
community.
- Claudiu Mihail is considered a great student who is always
available on IRC and often asking questions. His lwIP driver is
progressing well, although he agrees that there is still much
work left.
- Andrew Green has taken the task to complete our new Explorer, but
there were a few issues with what he thought he was doing and what
we wanted from him. He assumed he had to work on the explorer_new
application itself while we actually need work done on related
components like shell32 and browseui. Ged thinks he might have
underestimated the workload a little, so some help from the
community might be required. This is also why Ged has begun to
work on shell32 himself and merge the latest changes with the C++
code by Andrew Hill.
Ged explicitly asks for more developers to join these efforts.
It would be great if these people had experiences with COM,
although this could also be a nice task for developers who want
to learn a bit about COM.
○ Point 2 (added): Neeraj Yadav's participation in GSoC
--------------------------------------------------------
■ Ged Murphy gave a quick background on what happened regarding Neeraj
Yadav, who was meant to work on the Audio Mixer project:
- After Google announced the project, Neeraj Yadav disappeared for
4 weeks and was not reachable by E-Mail or IRC.
- Ged has spoken to Carol Smith from Google afterwards, who
mentioned that some students waited for the first payment and then
fled.
- After a lot of discussion, it was necessary to inform Google that
we had lost a student.
- Ged has written some very apologetic mails to Google afterwards,
and they were pretty understanding.
- He has especially emphasized that this was a very bad time for us
and made the project looking incompetent. Apart from him, Amine
Khaldi and Johannes Anderwald (his mentor) were very angry about
this as well.
- Two days after these mails, Neeraj Yadav reappeared on IRC.
■ Neeraj Yadav said he was really sorry about his mistake, but also
explained his actions:
- He mentioned that his case was actually the opposite of what
Google might assume: While some students keep in contact with the
organisation until they get their first payment, he actually
disappeared during the community bonding period, but was available
again on the first day when coding started.
- His sudden absence occurred, because he needed to move to his
brother who lives in a remote place with no internet connectivity.
■ Ged again emphasized that a wrong decision on this can affect our
further participation in Google's Summer of Code project.
■ After a long discussion, it was decided that this matter requires a
private conversation between Johannes Anderwald and Ged Murphy and a
final decision needs to be taken by them.
Please note that this is a very shortened version of the discussion and
you should not build an opinion about the issue just from this information.
○ Point 3 (added): Changes in the meeting organisation
-------------------------------------------------------
■ Victor Martinez proposed to create a list of E-Mail addresses of
ReactOS Members, who are then informed one week before the meeting takes
place.
- This idea was immediately rejected by Aleksey Bragin and Samuel
Serapion, because we have the ros-dev mailing list for this.
- Victor Martinez then proposed that someone at least sends a mail
to ros-dev one week in advance. Colin Finck, Gabriel Ilardi, Jan
Blomqvist Kinander and Pierre Schweitzer agreed to this.
- Colin Finck proposed that Aleksey Bragin could take this job.
Aleksey Bragin agreed.
■ Jan Blomqvist Kinander asked whether we could already begin at 19:00
UTC. This required a voting between all participants (excluding the
people who only came to us through GSoC). As Colin Finck has not fixed
the IRC server with voting capabilities yet, the voters were publicly
asked about their opinion. Result:
- 17 positive votes
- 1 abstention
- 0 negative votes
The remaining participants were not available and did not vote. Even
without them, this result shows that we have a clear simple majority, so
further meetings will begin at 19:00 UTC.
○ Point 4: Current ReactOS work, Developers reporting their status
-------------------------------------------------------------------
■ Aleksey Bragin had a busy month, which began by giving a technical
lecture about ReactOS at Prague's technical university in the faculty of
informatics. It was received quite well with enough of interesting
questions. Afterwards, he moved to Berlin to join Matthias at our
LinuxTag booth. He describes the event as a very crowded and well
advertised one. On top of this, the ReactOS booth was located quite
close to the entrance, so we received a lot of visitors. Despite
LinuxTag being Europe's biggest Open-Source event, 99% of the incoming
people were German, so Matthias had to handle most of them.
Regarding ReactOS development, Aleksey is still working on his LDR
rewrite and fixed a few of the blocker bugs. There is still one serious
problem left until he can commit the rewrite to Trunk and gradually
improve it there, which should be done much faster. When this is done
and there are no new regressions left, he wants to perform a full Wine sync.
■ Art Yerkes has spent most time working on DWARF symbols. He made slow
progress towards reading the arguments off the stack as described by the
DWARF debug information. After Colin Finck asked, he also reported about
NewCC being in the same state as before, namely still requiring
performance improvements and regression testing until it can be merged
back to Trunk.
■ Cameron Gutman has been doing work on the PnP manager involving hot
swapping devices (like implementing device ejection, surprise removal,
etc.). He is almost done with his implementation of
IoRequestDeviceEject. The code is currently unused, but the USB work
might be a good testcase for it.
■ Colin Finck has returned to Germany two weeks ago and has been busy
with (mostly routine) foundation and server work. He is also relocating
in August, so he might be missing time for ReactOS work afterwards. For
now, his list basically inclues three ReactOS-related points:
- Fixing the bug in the IRC server we used for the March meeting
- Starting work on "RosBE 2.0" (certainly together with dreimer),
which also includes establishing fixed build tool versions for the
big CMake rollout
- Helping with the big website revamp
■ Gabriel Ilardi is quite busy lately, so he is mainly following the
forum and contributed some bitmaps for logonui.
■ Giannis Adamopoulos is exclusively working on the Theming task for GSoC.
■ Ged Murphy as our GSoC administrator has been pretty busy with related
work. However, he has recently started to work on the conversion of
shell32 to C++ and just finished merging back all changes from the C
version. He especially wants to thank Andrew Hill for his first work on
the C++ version and in particular his ATL headers, which give us a true
OO COM implementation. Additionally, he has started work on a logonui
module, but this is just a fun project for now. Finally, he has a
partially working NTFS driver, but this project is currently put on hold.
■ James Tabor is researching bug reports and building a list of related
issues and problems in the server-side window procedures. As we
currently do not have a functional screensaver, he is also trying to fix
this.
■ Jan Blomqvist Kinander is planning a new burglar-proof server bunker
fire cell at his workplace and will move our Fezile server (currently
hosting Doxygen and ISO Storage) there. He is also planning to make room
for a LAN behind the Fezile server, which we could use for automatic
tests on real hardware.
■ Johannes Anderwald is teaming with Michael Martin to develop the USB
stack. The current goal is to bring a working USB mass storage stack to
ReactOS. From this perspective, the goal is already reached for USB 2.0.
Today, he also got OHCI 1.1 mass storage support working and added some
fixes for keyboard/mice support in the USBOHCI driver. This still
requires proper HID support in a higher class driver though. The next
goals probably include UHCI support and synchronizing the work with
Cameron's PnP fixes and Pierre's Mount Manager work.
■ Kamil Hornicek has been arranging Aleksey's speech in Prague, but did
not have time for other ReactOS-related work. If anybody has an
interesting side project, he is willing to find some spare time for it
though.
■ Maciej Bialas hopes to get back to working on our new website in the
next one or two weeks. He has lately been setting up a local Bugzilla
and evaluated its authentication capabilities when combined with Drupal CMS.
■ Matthias Kupfer has been attending our LinuxTag booth for all three
days and is now working on a lot of "end-user-visible" parts in his
spare time. Since LinuxTag, he has started with the internationalization
of registry entries and small changes like adding the progress bar back
to FreeLdr. Besides, he also does routine work for the German ReactOS
foundation.
■ Olaf Siejka has been working on testing and pushing patches (as
reported by Gabriel Ilardi). He also reported that the CMake/MSVC builds
are now compiled from Trunk, but he needs to reinstall his Buildslave
with Windows 7 SP1 and thinks about buying a fast SSD for it. Finally,
he is in the middle of converting Polish resources to UTF-8 and perform
some cleanup and style corrections in the process.
■ Rafal Harabien has been busy with real life issues lately, but plans
to fix our cursors implementation in Win32k soon and clipboards afterwards.
■ Samuel Serapion is writing code for NTLM authentication stuff and will
move to the MSV1_0 and LSA modules afterwards. He referred to
http://msdn.microsoft.com/en-us/library/aa378753%28v=vs.85%29.aspx for
explanations about what these modules are used for.
■ Timo Kreuzer is exclusively working on the FreeType font driver for GSoC.
■ Victor Martinez has been presenting ReactOS at small Spanish
conferences about Open-Source in Seville and Huelva (again) before he
joined Aleksey and Matthias at LinuxTag in Berlin. Lately, he has been
modifying the Testing Central Wiki page, where the GoldenApps now point
to the Compatibility Database. Finally, he plans to establish a real
Testing Team (mainly from Forum users) together with Olaf.
■ Ziliang Guo has been working on several things like building and
verifying the drivers which are going to be signed with the ReactOS
Foundation certificate. He is also testing out a new MSI installer for
RosBE-Windows. His work towards the website overhaul is currently on
hold, because he first needs to install some more modules.
○ Meeting closed at 22:36 UTC by Colin Finck on behalf of Aleksey Bragin.
○ Minutes written by Colin Finck.
Hi,
I am a GSoC student working on Audio Mixer Project.Unfortunately, I was not
able to contact my mentor/administrator during community bonding period.I
have disappointed whole of the community and you have every right to be
angry and I am really sorry for my act.But I request you all to reconsider
the following points :
1. Firstly, Why would one disappear during community bonding period without
any reason ? It is the easiest part of the whole program for a student in
which they have to just talk to the community, which I think they have
already been doing for not less than a month, then what is the problem in
being in contact for another month.
In my opinion a smart student who just wanted his initial payment would have
disappeared after the community bonding period.Instead of coming back at the
time of actual work.
2. Some of you think that I was waiting for initial payment and then
reappeared when i did not get it, I would like to say that I appeared
without even knowing that my project has been discontinued, neither had
anyone got his welcome package upto that time.Nothing regarding my project
discontinuation had been reported in Melange.How could i get even a
slightest idea about my project's termination.
3. Some of you think that it is going to hurt the reputation of organisation
for next year's selection at GSoC, I would like to admit that terminating my
project will straightaway decrease project completion rate of ReactOS
organisation to 80% and it may further reduce if some students actually do
not complete the project which is considered too bad for an organisation.And
believe me next year's sole criterion for organisation selection will be
this success rate.
4.Problems occur to every organisation and Google understands it very well
and it doesn't affect the organisation's reputation that much.All that
matters is the success rate.
5. I talked to Google and they just want an email of consent from my mentor
and its not too late.I have filled all my forms in due time.
6. My project would have automatically been discontinued if I failed for
Mid-term Evaluation.But no one gets benefit if my project is discontinued
earlier.Take a chance guys, If I complete my project it will be good for
both me and community if not terminating my project at both
7. In case above explanations do not satisfy you and if you think this is
only money I am after, I am ready to deposit $500 as security which is equal
to the initial payment.[or whatever amount you say]
This issue can be discussed in today's meeting.I am ready to answer all of
your questions.I hope you will think about it with a cool mind keeping the
anger/ego apart.
--
Regards
Neeraj Yadav
Undergraduate Student
Indian Institute of Technology, Delhi
HI folks,
the German company Thomas Krenn AG (Server Hardware) announced on LinuxTag an
open source support programme for open source projectes, that register during
LinuxTag. So I've use this chance and made the first step and registered
ReactOS. Now we need some arguments what kind of hardware do we need and why
resp. for what purpose. Devs please take a look at thomas-krenn.com and
select a usefull set of hardware and describe what is usefull for. I think we
should define specific tasks, not "upgrade exisiting hardware", but e.g. "New
continuous integration server". Please send the description and the ID of the
basket to me. The prices are:
1st: hardware for 2500 € (excluding VAT)
2nd: hardware for 1500 € (excluding VAT)
3rd: hardware for 1000 € (excluding VAT)
4th: hardware for 800 € (excluding VAT)
5th: hardware for 700 € (excluding VAT)
They told me at the booth the chances increase with the detailed description
of the intended use of the selected hardware (maybe combined with neediness).
Best regards
Matthias
--
Matthias Kupfer phone +49 371 236 46 52
Wilhelm-Firl-Straße 21 mobile +49 160 859 43 54
09122 Chemnitz, Germany
Hi, I will have to take down the Fezile server for a short period of time in about 2 weeks due to a move of the server room to a fireproof, fairly burglarproof security room (brickswork with steeldoor, no windows). However, it is beeing remodelled right now, and then the aircondition, ethernet lines and power is going to be installed, so I guess two weeks.
I have some computers to move so the power down may take some time, but I will try to make the move as fast as possible.
During this time I will try to prepare for a ReactOS LAN behind the Fezile server on the second and third LAN adapter, for example for build testing on real hardware or another build bot.
Yours sincerely,
Jaix Bly (Jan Blomqvist Kinander)
Hello,
I want to remind you of the monthly status meeting taking place today, Thursday the 26th of May at 20:00 UTC at freenode #reactos-meeting.
The suggested (subject to change and addition before meeting starts) meeting agenda is:
- Status of our GSoC participation
- Current ReactOS work. Developers reporting their status.
Those who don’t attend will be able to read up the meeting minutes later.
See you at the meeting today!
WBR,
Aleksey Bragin.
Hiya
Our nightly builds repository is not working and people cannot download
anything from it. Is it a known issue? Any idea when it might be fixed?
Best regards
Commit messages should include the component name that your commit changes.
Messages like the following:
[nyadav] 51882: Fix a Deadlock (nyadav(a)svn.reactos.org)
will result in me coming after you when I need to do the changelog for the
next release. Messages should be formatted like this:
[tkreuzer] 51885: [WIN32K] - Fix the bitmap alignment issue that caused
broken scrollbar pattern (tkreuzer(a)svn.reactos.org)
Z98
Hi,
it appears that Linux buildbot is running a bad issue and is looping on building. If anyone can have a look?
To prevent flood on IRC, I silent bot and removed voice.
Thanks in advance
That was very confusing :)
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of osiejka(a)svn.reactos.org
Sent: 23 May 2011 22:49
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [osiejka] 51874: [RPCSS] Addenum. This change slipped past in commit 51873. Fix name of irot header include, which should be irot.h and not irot_s.h. Fixes rpcss build in MSVC.
Author: osiejka
Date: Mon May 23 21:49:12 2011
New Revision: 51874
URL: http://svn.reactos.org/svn/reactos?rev=51874&view=rev
Log:
[RPCSS]
Addenum. This change slipped past in commit 51873. Fix name of irot header include, which should be irot.h and not irot_s.h. Fixes rpcss build in MSVC.
Modified:
trunk/reactos/base/services/rpcss/irotp.c
Modified: trunk/reactos/base/services/rpcss/irotp.c
URL: http://svn.reactos.org/svn/reactos/trunk/reactos/base/services/rpcss/irotp.…
==============================================================================
--- trunk/reactos/base/services/rpcss/irotp.c [iso-8859-1] (original)
+++ trunk/reactos/base/services/rpcss/irotp.c [iso-8859-1] Mon May 23 21:49:12 2011
@@ -1,5 +1,5 @@
/*
- * Running Object Table
+ * Running Object Table
*
* Copyright 2007 Robert Shearman
*
It was spotted by MSVC build:
P:\Trunk_slave\MSVC-trunk\build\base\services\rpcss\irotp.c(28) : fatal
error C1083: Cannot open include file: 'irot_s.h': No such file or directory
LINK : fatal error LNK1104: cannot open file
'CMakeFiles/rpcss.dir/irotp.c.obj'
In base\services\rpcss\irotp.c:28 we see: #include "irot_s.h"
This file is not present in ReactOS trunk. In WINE's RPCSS
http://source.winehq.org/git/wine.git/blob/HEAD:/programs/rpcss/irotp.c :28
we have: #include "irot.h" which is also missing, and listed in .gitignore:
http://source.winehq.org/git/wine.git/blob?f=.gitignore
260 programs/rpcss/irot.h
261 programs/rpcss/irot_s.c
I think we can safely clean it up, perhaps adding proper line to ros-diff,
but i would like to ask you guys for confirmation.
Regards
Hi ros-dev,
I've seen shell32_new being added into trunk by r51768, but haven't heard of
anything else about it. From what I can see it changes shell32 from C to
C++, which looks like a good move.
Problematic seems to me that it is completely out of sync with trunk's
shell32 (judging from the translations alone).
It might also be annoying for merging future patches, since the C to C++
move changes the code substantially.
So are there any plans concering shell32_new? Do I have to merge all code
changes in C and C++ or is shell32(_old) going to be dumped anytime soon?
Best regards,
Gregor
When I was trying to build trunk (using Cmake) the configure.cmd did not
complete. Host tools were OK but reactos directory was not.
I tracked the issue to /dll/win32/msports/CMakeLists.txt which contained
references to two nonexistent files (serial.c and parallel.c) and
commenting them out allowed the build to continue (albeit with an error at
the very end) there.
Hiya
Attached, you will find a rough draft of current patch assignment proposals.
I`m trying to keep it in realtime, so several of those are already in place.
As usual, please comment if you find you shouldn't be reviewing assigned
patch.
Best regards
Speaking about bug reports drama, im still watching how there are several
people that are still sending totally useless compatibility test results to
ROS database...
I want to ask for a moderation system for that, and i would want to offer
myself to moderate new incoming results, such as Wine system....
Hi Eric,
Sounds like you got it licked, the right way.
Good job !
Best Regards
L.
2011/5/6 <ros-dev-request(a)reactos.org>
> From: Eric Kohl <eric.kohl(a)t-online.de>
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Date: Thu, 05 May 2011 22:41:24 +0200
> Subject: Re: [ros-dev] [EVENTVWR/EVENTLOG] Fix a double off-by-one bug
> Hi Love,
>
> I just committed a fix for the calculation of the available number of event
> records. It addresses the issues you mentioned.
>
> And this is how it works:
> When a new log file is created, the first (or oldest) record gets the
> record number 1. With each new event record the record number is incremented
> by 1. To get the number of records in the log file we need to subtract the
> OldestRecordNumber from the CurrentRecordNumber. If the log file is empty
> the OldestRecordNumber will be 0. In this case we will return 0 for the
> number of event records.
>
> Now we call clear a filled log file and fill it with new records. The
> oldest record will not be record number 1 but we can still return the true
> number of records in the log file.
>
>
> Regards
> Eric
>
Hi Aleksey,
I'm sorry if my opinion came across as critique of the work as such.
It was definitely not intended that way.
I have great respect for all your efforts.
Just a point about unfortunate choice of AT&T syntax.
I would gladly volunteer to translate all old AT&T code to Intel.
After all, I do have 25 years of expertise in assembly coding.
It's just that I'm completely bogged down by R.L and have no time.
But if it can wait, just leave it be, and I'll do it later.
I'm sure Timo has enough to do with other issues already.
I abbreviated the pro's and con's to just two points,
of which the 2nd applies just to gcc's inline asm syntax.
Translating non-inline AT&T to Intel is fairly straight forward.
InvalidateHarshMode(TRUE);
No offence taken.
Best Regards
L.
On 2011-05-05 14.58, "Aleksey Bragin" <aleksey(a)reactos.org> wrote:
> SetHarshMode(TRUE);
>
> Your opinion would be interesting if it was motivated by your
knowledge and experience in writing assembly
> in both AT&T and Intel syntax, so that you could provide us pros and
cons of each approach by your judgement.
>
> Or, if you would be author of that code part in ReactOS.
>
> Otherwise, I’m afraid, it’s just criticizing a very good work, didn’t
even noticing the great PXE milestone,
> but nitpicking to a syntax. Don’t join complaints if you can’t fix
it. (Timo’s point is valid because that’s him who actually > converts
this stuff!)
>
> SetHarshMode(FALSE);
>
> WBR,
> Aleksey.
I noticed this YouTube channel here - http://www.youtube.com/reactosorg -
and apparently it seems to have 3 videos about ReactOS on it.
Nothing seems to be uploaded to it for a little over 1 year and I was
wondering perhaps it wouldn't be a bad idea to upload some videos about
various events to it.
I suspect a major issue with the lack of developers is lack of publicity
and I think this seems like a good opportunity.
(note I am not sure if it is the official ReactOS channel or not - if not
time to make one - apparently it seems the person who made the channel is
displaying the Age as 16 years old)
I am sorry to Vicmarcal for outbursting on ros-dev. The reason for that was
yet another pointless bugreport, after my requestes, passed several times,
regarding bug reports quality.
Sorry, Vicmarcal, as well as those who had to witness it.
Regards
Bugzilla is crowded with untouched bugs for so long, and you HAVE to add
more crud to it? Bugs like no.6214, very usefull as we can see below:
"1)Download ClickToDesktop
2)Run in ReactOS
3)Click on the desktop to hide. It doesn't work. Apps just lost the focus.
Nothing appears in the DebugLog."
Now that is informative... Why dont you get back doing something useful for
a change?
Hi Ged,
Yes of course I read Hervé's mail.
I did not suggest that he should go about porting existing code, I just
expressed my opinion that we shouldn't use AT&T for new code.
As for porting the existing freeldr AT&T code, I guess I could, eventually,
when I get time,
if I can just get a firm enough grip on the AT&T directive voodoo, which is
obscure.
But in the short run, no, sorry, I'm really bogged down by RL :(
(It's even hard to try and keep up with the mailing list)
You wouldn't happen to have a good pointer for that obscure AT&T string
voodoo?
Best Regards
L.
On Tue, May 3, 2011 at 11:12 PM, <ros-dev-request(a)reactos.org> wrote:
> Send Ros-dev mailing list submissions to
> ros-dev(a)reactos.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.reactos.org/mailman/listinfo/ros-dev
> or, via email, send a message with subject or body 'help' to
> ros-dev-request(a)reactos.org
>
> You can reach the person managing the list at
> ros-dev-owner(a)reactos.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ros-dev digest..."
>
> Today's Topics:
>
> 1. Re: [EVENTVWR/EVENTLOG] Fix a double off-by-one bug (Love Nystrom)
> 2. Re: [freeldr] Add PXE "filesystem" (Love Nystrom)
> 3. Re: [freeldr] Add PXE "filesystem" (Ged Murphy)
>
>
> ---------- Forwarded message ----------
> From: Love Nystrom <love.nystrom(a)gmail.com>
> To: ros-dev(a)reactos.org
> Date: Tue, 3 May 2011 21:52:40 +0700
> Subject: Re: [ros-dev] [EVENTVWR/EVENTLOG] Fix a double off-by-one bug
>
> Hi Gabriel, Eric,
>
> Isn't the real issue why LogFile->Header.CurrentRecordNumber is off by one
> ?
> If that is found and fixed, this patch will make the error re-emerge as an
> off by -1.
> And if CurrentRecordNumber is actually used as the next *pending* record
> number,
> the identifier is somewhat mis-leading .. ?
>
> Just my penny to the pot
> Best Regards
> L.
>
> ---------- Forwarded message ----------
>> From: Gabriel ilardi <gabrielilardi(a)hotmail.it>
>> To: ros-dev <ros-dev(a)reactos.org>
>> Date: Mon, 2 May 2011 21:50:03 +0200
>> Subject: Re: [ros-dev] [ros-diffs] [ekohl] 51558: [EVENTVWR/EVENTLOG] Fix
>> a double off-by-one bug: - The eventlog service was reporting one event more
>> than was available (+1). - The event viewer did not display the latest event
>> from...
>> Great work on event service and event viewer... keep it up Eric :)
>>
>>
>> > Date: Mon, 2 May 2011 19:38:24 +0000
>> > To: ros-diffs(a)reactos.org
>> > From: ekohl(a)svn.reactos.org
>> > Subject: [ros-diffs] [ekohl] 51558: [EVENTVWR/EVENTLOG] Fix a double
>> off-by-one bug: - The eventlog service was reporting one event more than was
>> available (+1). - The event viewer did not display the latest event from...
>> >
>> > Author: ekohl
>> > Date: Mon May 2 19:38:23 2011
>> > New Revision: 51558
>> >
>> > URL: http://svn.reactos.org/svn/reactos?rev=51558&view=rev
>> > Log:
>> > [EVENTVWR/EVENTLOG]
>> > Fix a double off-by-one bug:
>> > - The eventlog service was reporting one event more than was available
>> (+1).
>> > - The event viewer did not display the latest event from the eventlog
>> service (-1).
>> >
>> > See issue #6182 for more details.
>> >
>> > Modified:
>> > trunk/reactos/base/applications/mscutils/eventvwr/eventvwr.c
>> > trunk/reactos/base/services/eventlog/rpc.c
>> >
>> > Modified: trunk/reactos/base/applications/mscutils/eventvwr/eventvwr.c
>> > URL:
>> http://svn.reactos.org/svn/reactos/trunk/reactos/base/applications/mscutils…
>> >
>> ==============================================================================
>> > --- trunk/reactos/base/applications/mscutils/eventvwr/eventvwr.c
>> [iso-8859-1] (original)
>> > +++ trunk/reactos/base/applications/mscutils/eventvwr/eventvwr.c
>> [iso-8859-1] Mon May 2 19:38:23 2011
>> > @@ -503,7 +503,7 @@
>> > HWND hwndDlg;
>> > HANDLE hEventLog;
>> > EVENTLOGRECORD *pevlr;
>> > - DWORD dwRead, dwNeeded, dwThisRecord, dwTotalRecords = 0,
>> dwCurrentRecord = 1, dwRecordsToRead = 0, dwFlags, dwMaxLength;
>> > + DWORD dwRead, dwNeeded, dwThisRecord, dwTotalRecords = 0,
>> dwCurrentRecord = 0, dwRecordsToRead = 0, dwFlags, dwMaxLength;
>> > LPWSTR lpSourceName;
>> > LPWSTR lpComputerName;
>> > LPSTR lpData;
>> >
>> > Modified: trunk/reactos/base/services/eventlog/rpc.c
>> > URL:
>> http://svn.reactos.org/svn/reactos/trunk/reactos/base/services/eventlog/rpc…
>> >
>> ==============================================================================
>> > --- trunk/reactos/base/services/eventlog/rpc.c [iso-8859-1] (original)
>> > +++ trunk/reactos/base/services/eventlog/rpc.c [iso-8859-1] Mon May 2
>> 19:38:23 2011
>> > @@ -199,6 +199,7 @@
>> > DWORD *NumberOfRecords)
>> > {
>> > PLOGHANDLE lpLogHandle;
>> > + DWORD dwRecords;
>> >
>> > lpLogHandle = ElfGetLogHandleEntryByHandle(LogHandle);
>> > if (!lpLogHandle)
>> > @@ -206,7 +207,9 @@
>> > return STATUS_INVALID_HANDLE;
>> > }
>> >
>> > - *NumberOfRecords = lpLogHandle->LogFile->Header.CurrentRecordNumber;
>> > + dwRecords = lpLogHandle->LogFile->Header.CurrentRecordNumber;
>> > +
>> > + *NumberOfRecords = (dwRecords > 0) ? (dwRecords - 1) : 0;
>> >
>> > return STATUS_SUCCESS;
>> > }
>> >
>> >
>>
>
>
>
> ---------- Forwarded message ----------
> From: Love Nystrom <love.nystrom(a)gmail.com>
> To: ros-dev(a)reactos.org
> Date: Tue, 3 May 2011 22:35:30 +0700
> Subject: Re: [ros-dev] [freeldr] Add PXE "filesystem"
>
> Hi Hervé,
>
> No disrespect for your work, but I'm inclined to concur with Timo regrading
> AT&T vs. Intel.
>
> Even though I usually preach "don't fix it if it isn't broken', I really
> think that AT&T syntax
> is broken by design, and we should use only Intel assembly, which is *much*
> clearer.
> After all, we're programming Intel CPU's, not AT&T telephone switchboards
> ;)
>
> 1) AT&T does not conform with Intel instruction reference.
> Intel syntax conforms with the instruction reference.
>
> 2) AT&T has a lot of quaint obscure directive voodoo.
> What little directives exist in Intel is clear and concise.
>
> Eventually, I hope we'll get rid of all backwards & muddy AT&T assembly,
> but until then I think we should at least not use it for new code.
>
> Best Regards
> L.
>
>
> ---------- Forwarded message ----------
>> From: "Hervé Poussineau" <hpoussin(a)reactos.org>
>> To: ReactOS Development List <ros-dev(a)reactos.org>
>> Date: Mon, 02 May 2011 19:33:19 +0200
>> Subject: Re: [ros-dev] [ros-diffs] [hpoussin] 51517: [freeldr] Add PXE
>> "filesystem"
>> Hi,
>>
>> The file is in AT&T syntax, as all asm files in
>> reactos/boot/freeldr/freeldr/arch/i386/ , except fathelp.asm
>> Sorry, I won't "fix" it, so you'll have to find someone to do it.
>>
>> Regards,
>>
>> Hervé
>>
>> Timo Kreuzer a écrit :
>>
>>>
>>> Why did you write the asm code in AT&T syntax? Its both ugly and breaks
>>> compilation with MSVC.
>>> I've spent quite some time converting all asm code to MSVC friendly intel
>>> syntax.
>>> Could you please fix that?
>>>
>>> Regards,
>>> Timo
>>>
>>> Am 01.05.2011 10:11, schrieb hpoussin(a)svn.reactos.org:
>>>
>>>> Author: hpoussin
>>>> Date: Sun May 1 08:11:43 2011
>>>> New Revision: 51517
>>>>
>>>> URL: http://svn.reactos.org/svn/reactos?rev=51517&view=rev
>>>> Log:
>>>> [freeldr] Add PXE "filesystem"
>>>>
>>>> Added:
>>>> trunk/reactos/boot/freeldr/freeldr/arch/i386/i386pxe.S (with
>>>> props)
>>>> trunk/reactos/boot/freeldr/freeldr/fs/pxe.c (with props)
>>>> trunk/reactos/boot/freeldr/freeldr/include/arch/i386/pxe.h (with
>>>> props)
>>>> trunk/reactos/boot/freeldr/freeldr/include/fs/pxe.h (with props)
>>>> Modified:
>>>> trunk/reactos/boot/freeldr/freeldr/arch/i386/machpc.c
>>>> trunk/reactos/boot/freeldr/freeldr/arch/i386/pcdisk.c
>>>> trunk/reactos/boot/freeldr/freeldr/freeldr_base.rbuild
>>>> trunk/reactos/boot/freeldr/freeldr/freeldr_base64k.rbuild
>>>> trunk/reactos/boot/freeldr/freeldr/fs/fs.c
>>>> trunk/reactos/boot/freeldr/freeldr/include/arch/i386/hardware.h
>>>> trunk/reactos/boot/freeldr/freeldr/include/arch/i386/machpc.h
>>>> trunk/reactos/boot/freeldr/freeldr/include/freeldr.h
>>>>
>>>> Added: trunk/reactos/boot/freeldr/freeldr/arch/i386/i386pxe.S
>>>> URL:
>>>> http://svn.reactos.org/svn/reactos/trunk/reactos/boot/freeldr/freeldr/arch/…
>>>> ==============================================================================
>>>>
>>>> --- trunk/reactos/boot/freeldr/freeldr/arch/i386/i386pxe.S (added)
>>>> +++ trunk/reactos/boot/freeldr/freeldr/arch/i386/i386pxe.S [iso-8859-1]
>>>> Sun May 1 08:11:43 2011
>>>> @@ -1,0 +1,97 @@
>>>> +/*
>>>> + * FreeLoader
>>>> + * Copyright (C) 2011 Hervé Poussineau
>>>> + *
>>>> + * This program is free software; you can redistribute it and/or
>>>> modify
>>>> + * it under the terms of the GNU General Public License as published
>>>> by
>>>> + * the Free Software Foundation; either version 2 of the License, or
>>>> + * (at your option) any later version.
>>>> + *
>>>> + * This program is distributed in the hope that it will be useful,
>>>> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
>>>> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
>>>> + * GNU General Public License for more details.
>>>> + *
>>>> + * You should have received a copy of the GNU General Public License
>>>> along
>>>> + * with this program; if not, write to the Free Software Foundation,
>>>> Inc.,
>>>> + * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
>>>> + */
>>>> +
>>>> + .text
>>>> + .code16
>>>> +
>>>> +#define ASM
>>>> +
>>>> +#include<arch.h>
>>>> +
>>>> +/*
>>>> + * U16 PxeCallApi(U16 Segment, U16 Offset, U16 Service, VOID
>>>> *Parameter);
>>>> + *
>>>> + * RETURNS:
>>>> + */
>>>> +_pxe_function:
>>>> + .word 0
>>>> +_pxe_entry_point:
>>>> + .long 0
>>>> +_pxe_buffer_segment:
>>>> + .word0
>>>> +_pxe_buffer_offset:
>>>> + .word0
>>>> +_pxe_result:
>>>> + .word 0
>>>> +
>>>> +EXTERN(_PxeCallApi)
>>>> + .code32
>>>> + pushl %ebp
>>>> + movl %esp,%ebp
>>>> +
>>>> +
>>>>
>>>
>
>
> ---------- Forwarded message ----------
> From: "Ged Murphy" <gedmurphy(a)gmail.com>
> To: "'ReactOS Development List'" <ros-dev(a)reactos.org>
> Date: Tue, 3 May 2011 17:12:03 +0100
> Subject: Re: [ros-dev] [freeldr] Add PXE "filesystem"
>
> Did you read Herve’s email??
>
> Are you volunteering to convert all the files he mentioned into intel
> syntax?
>
>
>
>
>
> *From:* ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] *On
> Behalf Of *Love Nystrom
> *Sent:* 03 May 2011 16:36
> *To:* ros-dev(a)reactos.org
> *Subject:* Re: [ros-dev] [freeldr] Add PXE "filesystem"
>
>
>
>
>
> Hi Hervé,
>
>
>
> No disrespect for your work, but I'm inclined to concur with Timo regrading
> AT&T vs. Intel.
>
>
>
> Even though I usually preach "don't fix it if it isn't broken', I really
> think that AT&T syntax
>
> is broken by design, and we should use only Intel assembly, which is *much*
> clearer.
>
> After all, we're programming Intel CPU's, not AT&T telephone switchboards
> ;)
>
>
>
> 1) AT&T does not conform with Intel instruction reference.
>
> Intel syntax conforms with the instruction reference.
>
>
>
> 2) AT&T has a lot of quaint obscure directive voodoo.
>
> What little directives exist in Intel is clear and concise.
>
>
>
> Eventually, I hope we'll get rid of all backwards & muddy AT&T assembly,
>
> but until then I think we should at least not use it for new code.
>
>
>
> Best Regards
>
> L.
>
>
>
>
>
> ---------- Forwarded message ----------
> From: "Hervé Poussineau" <hpoussin(a)reactos.org>
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Date: Mon, 02 May 2011 19:33:19 +0200
> Subject: Re: [ros-dev] [ros-diffs] [hpoussin] 51517: [freeldr] Add PXE
> "filesystem"
> Hi,
>
> The file is in AT&T syntax, as all asm files in
> reactos/boot/freeldr/freeldr/arch/i386/ , except fathelp.asm
> Sorry, I won't "fix" it, so you'll have to find someone to do it.
>
> Regards,
>
> Hervé
>
> Timo Kreuzer a écrit :
>
>
> Why did you write the asm code in AT&T syntax? Its both ugly and breaks
> compilation with MSVC.
> I've spent quite some time converting all asm code to MSVC friendly intel
> syntax.
> Could you please fix that?
>
> Regards,
> Timo
>
> Am 01.05.2011 10:11, schrieb hpoussin(a)svn.reactos.org:
>
> Author: hpoussin
> Date: Sun May 1 08:11:43 2011
> New Revision: 51517
>
> URL: http://svn.reactos.org/svn/reactos?rev=51517&view=rev
> Log:
> [freeldr] Add PXE "filesystem"
>
> Added:
> trunk/reactos/boot/freeldr/freeldr/arch/i386/i386pxe.S (with props)
> trunk/reactos/boot/freeldr/freeldr/fs/pxe.c (with props)
> trunk/reactos/boot/freeldr/freeldr/include/arch/i386/pxe.h (with
> props)
> trunk/reactos/boot/freeldr/freeldr/include/fs/pxe.h (with props)
> Modified:
> trunk/reactos/boot/freeldr/freeldr/arch/i386/machpc.c
> trunk/reactos/boot/freeldr/freeldr/arch/i386/pcdisk.c
> trunk/reactos/boot/freeldr/freeldr/freeldr_base.rbuild
> trunk/reactos/boot/freeldr/freeldr/freeldr_base64k.rbuild
> trunk/reactos/boot/freeldr/freeldr/fs/fs.c
> trunk/reactos/boot/freeldr/freeldr/include/arch/i386/hardware.h
> trunk/reactos/boot/freeldr/freeldr/include/arch/i386/machpc.h
> trunk/reactos/boot/freeldr/freeldr/include/freeldr.h
>
> Added: trunk/reactos/boot/freeldr/freeldr/arch/i386/i386pxe.S
> URL:
> http://svn.reactos.org/svn/reactos/trunk/reactos/boot/freeldr/freeldr/arch/…
> ==============================================================================
>
> --- trunk/reactos/boot/freeldr/freeldr/arch/i386/i386pxe.S (added)
> +++ trunk/reactos/boot/freeldr/freeldr/arch/i386/i386pxe.S [iso-8859-1] Sun
> May 1 08:11:43 2011
> @@ -1,0 +1,97 @@
> +/*
> + * FreeLoader
> + * Copyright (C) 2011 Hervé Poussineau
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License as published by
> + * the Free Software Foundation; either version 2 of the License, or
> + * (at your option) any later version.
> + *
> + * This program is distributed in the hope that it will be useful,
> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> + * GNU General Public License for more details.
> + *
> + * You should have received a copy of the GNU General Public License
> along
> + * with this program; if not, write to the Free Software Foundation,
> Inc.,
> + * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
> + */
> +
> + .text
> + .code16
> +
> +#define ASM
> +
> +#include<arch.h>
> +
> +/*
> + * U16 PxeCallApi(U16 Segment, U16 Offset, U16 Service, VOID *Parameter);
> + *
> + * RETURNS:
> + */
> +_pxe_function:
> + .word 0
> +_pxe_entry_point:
> + .long 0
> +_pxe_buffer_segment:
> + .word0
> +_pxe_buffer_offset:
> + .word0
> +_pxe_result:
> + .word 0
> +
> +EXTERN(_PxeCallApi)
> + .code32
> + pushl %ebp
> + movl %esp,%ebp
> +
> +
>
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
Hi Hervé,
No disrespect for your work, but I'm inclined to concur with Timo regrading
AT&T vs. Intel.
Even though I usually preach "don't fix it if it isn't broken', I really
think that AT&T syntax
is broken by design, and we should use only Intel assembly, which is *much*
clearer.
After all, we're programming Intel CPU's, not AT&T telephone switchboards ;)
1) AT&T does not conform with Intel instruction reference.
Intel syntax conforms with the instruction reference.
2) AT&T has a lot of quaint obscure directive voodoo.
What little directives exist in Intel is clear and concise.
Eventually, I hope we'll get rid of all backwards & muddy AT&T assembly,
but until then I think we should at least not use it for new code.
Best Regards
L.
---------- Forwarded message ----------
> From: "Hervé Poussineau" <hpoussin(a)reactos.org>
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Date: Mon, 02 May 2011 19:33:19 +0200
> Subject: Re: [ros-dev] [ros-diffs] [hpoussin] 51517: [freeldr] Add PXE
> "filesystem"
> Hi,
>
> The file is in AT&T syntax, as all asm files in
> reactos/boot/freeldr/freeldr/arch/i386/ , except fathelp.asm
> Sorry, I won't "fix" it, so you'll have to find someone to do it.
>
> Regards,
>
> Hervé
>
> Timo Kreuzer a écrit :
>
>>
>> Why did you write the asm code in AT&T syntax? Its both ugly and breaks
>> compilation with MSVC.
>> I've spent quite some time converting all asm code to MSVC friendly intel
>> syntax.
>> Could you please fix that?
>>
>> Regards,
>> Timo
>>
>> Am 01.05.2011 10:11, schrieb hpoussin(a)svn.reactos.org:
>>
>>> Author: hpoussin
>>> Date: Sun May 1 08:11:43 2011
>>> New Revision: 51517
>>>
>>> URL: http://svn.reactos.org/svn/reactos?rev=51517&view=rev
>>> Log:
>>> [freeldr] Add PXE "filesystem"
>>>
>>> Added:
>>> trunk/reactos/boot/freeldr/freeldr/arch/i386/i386pxe.S (with props)
>>> trunk/reactos/boot/freeldr/freeldr/fs/pxe.c (with props)
>>> trunk/reactos/boot/freeldr/freeldr/include/arch/i386/pxe.h (with
>>> props)
>>> trunk/reactos/boot/freeldr/freeldr/include/fs/pxe.h (with props)
>>> Modified:
>>> trunk/reactos/boot/freeldr/freeldr/arch/i386/machpc.c
>>> trunk/reactos/boot/freeldr/freeldr/arch/i386/pcdisk.c
>>> trunk/reactos/boot/freeldr/freeldr/freeldr_base.rbuild
>>> trunk/reactos/boot/freeldr/freeldr/freeldr_base64k.rbuild
>>> trunk/reactos/boot/freeldr/freeldr/fs/fs.c
>>> trunk/reactos/boot/freeldr/freeldr/include/arch/i386/hardware.h
>>> trunk/reactos/boot/freeldr/freeldr/include/arch/i386/machpc.h
>>> trunk/reactos/boot/freeldr/freeldr/include/freeldr.h
>>>
>>> Added: trunk/reactos/boot/freeldr/freeldr/arch/i386/i386pxe.S
>>> URL:
>>> http://svn.reactos.org/svn/reactos/trunk/reactos/boot/freeldr/freeldr/arch/…
>>> ==============================================================================
>>>
>>> --- trunk/reactos/boot/freeldr/freeldr/arch/i386/i386pxe.S (added)
>>> +++ trunk/reactos/boot/freeldr/freeldr/arch/i386/i386pxe.S [iso-8859-1]
>>> Sun May 1 08:11:43 2011
>>> @@ -1,0 +1,97 @@
>>> +/*
>>> + * FreeLoader
>>> + * Copyright (C) 2011 Hervé Poussineau
>>> + *
>>> + * This program is free software; you can redistribute it and/or modify
>>> + * it under the terms of the GNU General Public License as published by
>>> + * the Free Software Foundation; either version 2 of the License, or
>>> + * (at your option) any later version.
>>> + *
>>> + * This program is distributed in the hope that it will be useful,
>>> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
>>> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
>>> + * GNU General Public License for more details.
>>> + *
>>> + * You should have received a copy of the GNU General Public License
>>> along
>>> + * with this program; if not, write to the Free Software Foundation,
>>> Inc.,
>>> + * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
>>> + */
>>> +
>>> + .text
>>> + .code16
>>> +
>>> +#define ASM
>>> +
>>> +#include<arch.h>
>>> +
>>> +/*
>>> + * U16 PxeCallApi(U16 Segment, U16 Offset, U16 Service, VOID
>>> *Parameter);
>>> + *
>>> + * RETURNS:
>>> + */
>>> +_pxe_function:
>>> + .word 0
>>> +_pxe_entry_point:
>>> + .long 0
>>> +_pxe_buffer_segment:
>>> + .word0
>>> +_pxe_buffer_offset:
>>> + .word0
>>> +_pxe_result:
>>> + .word 0
>>> +
>>> +EXTERN(_PxeCallApi)
>>> + .code32
>>> + pushl %ebp
>>> + movl %esp,%ebp
>>> +
>>> +
>>>
>>
Why did you write the asm code in AT&T syntax? Its both ugly and breaks
compilation with MSVC.
I've spent quite some time converting all asm code to MSVC friendly
intel syntax.
Could you please fix that?
Regards,
Timo
Am 01.05.2011 10:11, schrieb hpoussin(a)svn.reactos.org:
> Author: hpoussin
> Date: Sun May 1 08:11:43 2011
> New Revision: 51517
>
> URL: http://svn.reactos.org/svn/reactos?rev=51517&view=rev
> Log:
> [freeldr] Add PXE "filesystem"
>
> Added:
> trunk/reactos/boot/freeldr/freeldr/arch/i386/i386pxe.S (with props)
> trunk/reactos/boot/freeldr/freeldr/fs/pxe.c (with props)
> trunk/reactos/boot/freeldr/freeldr/include/arch/i386/pxe.h (with props)
> trunk/reactos/boot/freeldr/freeldr/include/fs/pxe.h (with props)
> Modified:
> trunk/reactos/boot/freeldr/freeldr/arch/i386/machpc.c
> trunk/reactos/boot/freeldr/freeldr/arch/i386/pcdisk.c
> trunk/reactos/boot/freeldr/freeldr/freeldr_base.rbuild
> trunk/reactos/boot/freeldr/freeldr/freeldr_base64k.rbuild
> trunk/reactos/boot/freeldr/freeldr/fs/fs.c
> trunk/reactos/boot/freeldr/freeldr/include/arch/i386/hardware.h
> trunk/reactos/boot/freeldr/freeldr/include/arch/i386/machpc.h
> trunk/reactos/boot/freeldr/freeldr/include/freeldr.h
>
> Added: trunk/reactos/boot/freeldr/freeldr/arch/i386/i386pxe.S
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/freeldr/freeldr/arch/…
> ==============================================================================
> --- trunk/reactos/boot/freeldr/freeldr/arch/i386/i386pxe.S (added)
> +++ trunk/reactos/boot/freeldr/freeldr/arch/i386/i386pxe.S [iso-8859-1] Sun May 1 08:11:43 2011
> @@ -1,0 +1,97 @@
> +/*
> + * FreeLoader
> + * Copyright (C) 2011 Hervé Poussineau
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License as published by
> + * the Free Software Foundation; either version 2 of the License, or
> + * (at your option) any later version.
> + *
> + * This program is distributed in the hope that it will be useful,
> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> + * GNU General Public License for more details.
> + *
> + * You should have received a copy of the GNU General Public License along
> + * with this program; if not, write to the Free Software Foundation, Inc.,
> + * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
> + */
> +
> + .text
> + .code16
> +
> +#define ASM
> +
> +#include<arch.h>
> +
> +/*
> + * U16 PxeCallApi(U16 Segment, U16 Offset, U16 Service, VOID *Parameter);
> + *
> + * RETURNS:
> + */
> +_pxe_function:
> + .word 0
> +_pxe_entry_point:
> + .long 0
> +_pxe_buffer_segment:
> + .word0
> +_pxe_buffer_offset:
> + .word0
> +_pxe_result:
> + .word 0
> +
> +EXTERN(_PxeCallApi)
> + .code32
> + pushl %ebp
> + movl %esp,%ebp
> +
> +
SaveDword(hKey, _T("iPointSize"), Globals.lfFont.lfHeight);
shouldn't it be
SaveDword(hKey, _T("iPointSize"),
PointSizeFromHeight(Globals.lfFont.lfHeight));
Also, this would permit to simplify code a bit :-)
http://cia.vc/stats/project/ReactOS/.message/3522f92
Hello,
I want to remind you of the regular meeting, Thursday the 28th at 20:00 UTC at freenode #reactos-meeting.
The suggested meeting agenda is:
- Status of our GSoC participation
- Current ReactOS work. Developers saying what they are working on
- Action List proposal
- Status of the upcoming LinuxTag event preparations
- Website revamp. Current status, who is working, who is willing to help
If nobody else volunteers, Amine would be ready to take the minute taker position again in this meeting and I would lead the meeting. In case I am late, Amine will open the up meeting and I will join as soon as I get online.
The current list of ReactOS members is as follows. Only these people will be able to participate in the discussions and votings, please tell us if we have forgotten anybody or if you want to be added to this list:
- Giannis Adamopoulos (smiley1_)
- Johannes Anderwald (janderwald)
- Javier Agustìn Fernàndez Arroyo (elhoir)
- Maciej Bialas (niski)
- Aleksey Bragin (abragin)
- Colin Finck (Colin_Finck)
- Danny Götte (dangerground)
- Cameron Gutman (aicom)
- Ziliang Guo (ZWabbit)
- Rafal Harabien (rafalh)
- Kamil Hornicek (Pigglesworth)
- Amine Khaldi (AmineKhaldi)
- Timo Kreuzer (tkreuzer)
- Matthias Kupfer (Collibri)
- Michael Martin (mjmartin)
- Victor Martinez (vicmarcal)
- Roel Messiant (Mephisto)
- Andrew Munger (WaxDragon)
- Ged Murphy (GedMurphy)
- Sylvain Petreolle (Usurp)
- Hervé Poussineau (hpoussin)
- Daniel Reimer (dreimer)
- Pierre Schweitzer (HeisSpiter)
- Samuel Serapion (encoded)
- Olaf Siejka (Caemyr)
- James Tabor (jimtabor)
- Art Yerkes (arty)
Everybody may join the meeting channel as a non-participating observer though.
See you at the meeting today,
Aleksey Bragin.
April Meeting Minutes
2011-04-28
20:05 UTC
Freenode, #reactos-meeting
Participants
============
Adam Stachowicz
Aleksey Bragin
Amine Khaldi
Art Yerkes
Daniel Reimer
Gabriel Ilardi
Ged Murphy
Giannis Adamopoulos
Gregor Schneider
Hervé Poussineau
James Tabor
Javier Agustìn Fernàndez Arroyo
Johannes Anderwald
Maciej Białas
Matthias Kupfer
Olaf Siejka
Pierre Schweitzer
Rafał Harabień
Samuel Serapion
Timo Kreuzer
Victor Martinez
Ziliang Guo
Proceedings
===========
○ Meeting called to order at 20:05 UTC by Aleksey Bragin
○ Point 1 in the agenda: GSoC status update
===========================================
■ Amine mentioned that ReactOS has 6 slots this year, and that a great
care was put in the accepted projects selection with focus on UI and
stability, with the goal to release 0.4 shortly after a successful GSoC.
He also mentioned that the students will be granted commit access to
official branches, so that the community can follow their progress. Ged
and Amine asked the present members to do their best to help the
students in any way, not leaving them only to their mentors, and asked
the students not to hesitate to request help from anyone.
○ Point 2: Current ReactOS work
===============================
■ Amine: GSoC related tasks and coordination, CMake branch regression
tracking and fixing, with the help of Igor and Rafał, still into the
website revamp and the ideas around it.
■ Olaf: He has just updated VBox testbot to VBox 4.0.6, and with the
great help of Fireball and hackdog he finally got sysreg for it done as
well. Olaf also mentioned that our stdio problem of sysreg turned into
another less visible one, VBox serial output problem, typically for
heavy text output on virtual com via pipes.. The log is very good, but
sometimes short parts of text are relocated, like in
http://www.reactos.org/testman/detail.php?id=1763684. As a result of
these efforts, test repetitions should be more rare. He also suggested
to try to run it via com0com once Fireball signs the 64bit driver.
Another thing Olaf was working on is trying to shorten the patch queue
(http://www.reactos.org/wiki/Bug_Filters) and separate WIP patches from
the ready for review patches, and he also began committing translations.
■ Matthias: He is working on patches and minor bug-fixes, with focus on
win32 and win32k (espacially alt-tab). All the other ReactOS related
tasks have nothing to do with developing.
■ Gregor: He mentioned that he doesn't have as much time as last year,
since he works full time now, so he can only offer to help cleaning up
bugzilla from time to time, committing patches, reviewing etc. Expect
patches to random components from him, but he can't offer much irc
activity. He's going through application patches currently.
■ Daniel: Not much time lately. He still hopes to get a new RosBE done
in short term.
■ Javier: He tries to introduce new people to #reactos-es, and plans to
work more on translations and to also blog about ReactOS in Spanish.
■ Samuel: He is already working on secur32 and started msv1_0.
■ Aleksey: He's trying to finish the ldr rewrite and commit it. Two
blocker bugs are preventing him to do this: the first being the DLLs
registration failures in the 2nd stage, and the other one is a random
Firefox installer hang during file unpacking. When that's done, he plans
to move on to organize the massive winesync of the tree, simultaneously
trying to fix the remaining heap regressions (with someone?). The main
problem is that he's traveling quite often during this time range, and
thus can't work on ReactOS as he usually did, so any problem gets longer
to solve. He will also continue working on arwinss after those tasks
above are complete.
■ Gabriel: He keeps the forum clean on a daily basis (Spam mainly), and
he also does small updates to the wiki, Bugzilla maintenance, committing
translations and small patches, testing ReactOS and patches. He also
added the svn log to the front page of the website and is currently
giving some support to a guy that was interested in using ReactOS in his
company.
■ Jim: He's mainly working on bug-fixing, especially keyboard messages
and message in general.
■ Rafał: He's currently studying for his exams in May, and fixing random
bugs from bugzilla during his breaks. He'll eventually help in CMake.
■ Giannis: He started researching his GSoC project and doing some tests.
In the meantime he's trying to sort out any work that he started lately
but not completed.
■ Johannes: He's mainly working on USB, planning to reach Mike's
(mjmartin) driver state in the next few days, as most of the code
written now is based on his implementation. He mentioned that today was
good day for USB as lots of code got working. His initial goal is to get
mass storage working with Win XP (thats the bulk and control transfers),
then jump to hub driver and later the USB class driver, but he couldn't
really say how long this will take.
■ Timo: He is focusing on his GSoC project.
■ Victor: He was busy this month with real life, but he's trying to
create a Testing Forum Team, he hopes to start on it in the upcoming
days. He also helps with the website revamp, and he's now preparing for
the trip to Berlin for the LinuxTage event.
○ Point 3: Action List proposal
===============================
■ Amine referred to
http://www.reactos.org/pipermail/ros-dev/2011-April/014148.html for
context, and asked the members whether they have any
comments/suggestions about it. Nothing came up, so we proceeded to the
next point of this meeting.
○ Point 4: Status of the upcoming LinuxTag event preparations
=============================================================
■ Matthias mentioned that the booth is booked and tables and furniture
are ordered/reserved. Due to the lack of interest we have only 4 persons
as booth personnel. He will ask whether or not we need a day in advance
for preparation of booth, and he prefers to setup the booth on first
day, as long we don't have to set up a lot of things. Therefore, he
hasn't booked a hotel yet. His preferred hotel is too expensive, and as
long as we have some changes in persons he thinks it's easier to book
single rooms with a price around 50-70€ per night.
■ A brief discussion went on between Victor, Matthias and Gregor about
booking, sharing rooms, what to bring...etc
○ Point 5: Website revamp. Current status, who is working, who is
willing to help
=================================================================================
■ Ziliang mentioned that he's porting content over, trimming a lot of
stuff in terms of the 'About' and 'Why ReactOS' sections. He merged some
parts into the dev FAQ from the general FAQ, and got the location of the
Drupal install from Danny, so that he can start dropping in test modules
which will allow us to test main page layouts.
■ The rest of the discussion was just a reiteration of what's already in
the website revamp collaborative document.
○ Meeting ended at 23:10 UTC.
○ Minutes submitted by Amine Khaldi.
Below, a brief list of tasks i would propose for review at the next meeting.
Please post your proposals as well:
- LDR rewrite;
- HEAP rewrite regression fixup;
- CMake adoption;
- MSVC adoption;
- WineSync;
- LIBSync;
- Sysreg fixup (stdio problems, transition to pipe, automatical backtrace);
- WineTest-with-HEAP-debugging checkup (basically, running every test from
suite with heap debugging enabled);
- Video Driver fixup (fixing ReactOS to use real video drivers, bug #2286
and all connected);
Dear colleagues
We need to some short-term planning within our project, as the amount of
tasks awaiting will simply turn into chaos. I propose a list to be kept,
named "Action list". It should list our goals, things to be done, for
example Winesync, fixing some particular bug, etc. Every task should be
assigned to particular person, who would choose to be responsible for
getting it done. It doesn't need to be the only person working on this, but
rather someone making sure its done and not forgotten. Other variable
assigned to task would be a deadline - approximate one, susceptible to
extension when necessary. Goals are removed from the list when completed.
Action list should be reviewed at every meeting, by querying people
responsible for every task, being asked for an update.
I can keep such list.
Awaiting proposals for tasks if you think this makes sense.
Regards
Thanks for
attention tone
I was thinking of developing for ntfs
http://www.reactos.org/wiki/index.php?title=Special%3ASearch&search=NTFS
2011/4/25, ros-dev-request(a)reactos.org <ros-dev-request(a)reactos.org>:
> Send Ros-dev mailing list submissions to
> ros-dev(a)reactos.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.reactos.org/mailman/listinfo/ros-dev
> or, via email, send a message with subject or body 'help' to
> ros-dev-request(a)reactos.org
>
> You can reach the person managing the list at
> ros-dev-owner(a)reactos.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ros-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: Implementing ScmAssignNewTag (bug 6147) (Eric Kohl)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 24 Apr 2011 21:09:19 +0200
> From: Eric Kohl <eric.kohl(a)t-online.de>
> Subject: Re: [ros-dev] Implementing ScmAssignNewTag (bug 6147)
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Message-ID: <4DB4755F.1040003(a)t-online.de>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hello Thomas,
>
> your plan sounds good to me. Just implement ScmAssingnNewTag and attach
> the patch to bug #6147. I will review and and apply your patch if it is OK.
>
> Regards,
> Eric
>
>
> Thomas Faber wrote:
>> Hi,
>>
>> I'm thinking about implementing the ScmAssignNewTag function in
>> base\system\services\rpcserver.c because of
>> http://www.reactos.org/bugzilla/show_bug.cgi?id=6147
>>
>> My current plan would be: loop through all service keys in the
>> registry, check the Tag values for all that are in the same group,
>> and choose either max+1 or the first unused tag.
>>
>> Any opinions? Would it be important to observe how Windows calculates
>> tags? Perhaps Eric has a good overview and thus an opinion on this
>> service stuff? ;)
>>
>> Thanks. :)
>>
>> Regards,
>> Tom
>>
>> _______________________________________________
>> 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
>
> End of Ros-dev Digest, Vol 80, Issue 28
> ***************************************
>
Hi,
I'm thinking about implementing the ScmAssignNewTag function in
base\system\services\rpcserver.c because of
http://www.reactos.org/bugzilla/show_bug.cgi?id=6147
My current plan would be: loop through all service keys in the
registry, check the Tag values for all that are in the same group,
and choose either max+1 or the first unused tag.
Any opinions? Would it be important to observe how Windows calculates
tags? Perhaps Eric has a good overview and thus an opinion on this
service stuff? ;)
Thanks. :)
Regards,
Tom
Hi team,
I've found an rss service (http://www.rssinclude.com) that lets us add our svn activity in the frontage, result would like like this:
http://img15.imageshack.us/i/svni.jpg/
I'd like to publish it in our site for all languages, anyone disagrees ?
There are better ways to do it, but this is a fast one and we'll have more "news" (fresh info) in our homepage directly and right now....
Please answer.
Thanks.
Gabriel.
I have stumbled across this documentation
http://doc.sch130.nsc.ru/www.sysinternals.com/ntw2k/source/fmifs.shtml.
What it contains discusses how partitions are created. The very cool
thing is that by using FMIFS in the installer means that you can
delete,create and resize all the partitions that the disk manager
supports. This means it will make it a lot easier to add support to
both without duplicating efforts.(windows vista+ has resizing xp
doesn't seem to though)
The current text installer doesn't use this as this part of reactos
code is incomplete.
I would like to add this to my gsoc proposal. Though I know I'm
probably not going to get a place it may help me if I get a chance to
do it in the future or maybe this could give ideas to someone else who
tries.
Any thoughts or suggestions would be very much appreciated.
Hi all,
The subj.
I'm talking about Woodhead's GPL USB driver:
* Original page (and site) is dead ("Woodhead--NT4--USB"
http://www.geocities.com/mypublic99/index.html )
* But files are backed up, for example, here:
[ftp://piekraste.daba.lv/pub/Service_Pack/NT_4/NT4_USB/HS/]
(or look into internet wayback machine)
Regards,
M.A.
Hi all,
I'm going to implement dmesg.exe, a ROS application to read dmesg/kmsg
buffer (debug messages in kernel buffer),
which is filled in by appropriate patch 6018
(here: http://www.reactos.org/bugzilla/show_bug.cgi?id=6018 ) (BTW,
it's not yet reviewed and not applied!).
So I'm requesting advice on:
What would be the better way for user-mode code to get the contents of
kmsg buffer in kernel-space (kdbg)?
Shortly:
Linux has special system call "syslog" (man 2 syslog)
FreeBSD uses its special sysctl interface to kernel along with
'kern.msgbuf' parameter.
My questions:
Do we need special system call like Linux, or even more, the whole
family of them (sysctl('*')) as in BSD?
How to implement simple system call for it, now?
---
Now detailed info for unices:
Linux case:
* syslog(2) - read and/or clear kernel message ring buffer; set console_loglevel
int syslog(int type, char *bufp, int len);
* also /proc/kmsg virtual file, which when being read returns buffer contents
==excerpt from man proc ==
/proc/kmsg
This file can be used instead of the syslog(2) system
call to read kernel messages. A
process must have superuser privileges to read this
file, and only one process should read
this file. This file should not be read if a syslog
process is running which uses the sys‐
log(2) system call facility to log kernel messages.
Information in this file is retrieved with the dmesg(1) program.
==eo exerpt==
dmesg in FreeBSD:
Parameter 'kern.msgbuf' given to sysctl(3) returns contents of kernel
message buffer.
There is also 'kern.msgbuf_clear' to clean the buffer.
---
WBR,
Minas Abrahamyan
Am 09.04.2011 16:46, schrieb dreimer(a)svn.reactos.org:
> Author: dreimer
> Date: Sat Apr 9 14:46:37 2011
> New Revision: 51296
>
> URL: http://svn.reactos.org/svn/reactos?rev=51296&view=rev
> Log:
> - Sync all resource files with the English one.
> - Translate the new Dialog in the German one.
> - Normally we use BEGIN and END, no {}
> - DIALOG -> DIALOGEX
>
Hi,
This change breaks sndvol32. Have you run sndvol32 after your changes?
The reason is sndvol32 parses the dialog template code in memory, but it
uses the DIALOG resource format instead of the DIALOGEX resource format.
Please revert that partial change.
kind regards,
Johannes Anderwald
Hi Bryan,
Just like Aleksey, I would welcome an effort to simplify IFS implementation.
Seen as NTFS is (and always will be?) not well documented, I've been
thinking about
supporting some alternative, OSS, journaling file system in ReactOS, e.g.
ReiserFS,
to allow us to provide the (relative) fail-safety of file transaction
journaling that NTFS has.
Also, hopefully, to enable us to implement NT's access privilege
system (Security) on files.
So far, it remains just a thought, since I can't allocate the time to adapt
e.g ReiserFS to
an NT IFS, and if I'm not mistaken, our IFS implementation has shortcomings
of it's own
which You may need to address as well in implementing Your proposal.
In addition to "Windows NT File System Internals" I would also recommend
"Windows Internals, 4th Edition" for additional/complementary insight.
Especially Ch.12 "File Systems", but Ch.8-12 are all relevant, and the whole
book is strongly recommended (by everyone, I think).
It will be a BIG job I think (thesis big), and I hope You have the
structural
"common sense" to make it a success, and not a mess ;).
It would be most welcome !
Comment Your code scrupulously :)
Best Regards
// Love
On Sun, Apr 3, 2011 at 1:55 PM, <ros-dev-request(a)reactos.org> wrote:
> ---------- Forwarded message ----------
> From: Bryan Donlan <bdonlan(a)gmail.com>
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Date: Sat, 2 Apr 2011 18:26:23 -0400
> Subject: [ros-dev] [GSoC] IFS wrapper project proposal draft
> Hello,
>
> After reading the ReactOS GSoC ideas page, I became interested in the
> IFS wrapper driver project idea[1], and would appreciate any comments
> on my project proposal before I formally submit it.
>
> First, a bit about me. I am a student in a dual-major program,
> studying Computer Science and Japanese at the University of
> Massachusetts at Amherst. I have had some experience in kernel
> development previously; as part of an internship at a research project
> at my University, I wrote some network flow analysis code running in
> the Linux kernel. While filesystem work will be a first for me, I
> think it will be an interesting leaning experience. I am fluent in
> English and Japanese, and am in the UTC-0400 timezone (TZ=US/Eastern).
> My freenode username is bd_, and my myReactOS username is bdonlan.
>
> In preparation for writing this proposal, I obtained a copy of the
> "Windows NT File System Internals: A Developer's Guide" book from
> O'Reilly. Although a bit dated, it has been enourmously helpful in
> helping me get an idea of what I'm getting into.
>
> My goal in this project will be to write a library to significantly
> simplify writing a NT File System Driver. Although writing a
> kernel-mode filesystem will never be as easy as with, eg, FUSE, it
> should be possible to abstract away many of the idiosyncracies of the
> NT filesystem API, at least. For example, the wrapper library may
> handle:
> * Automatically queueing asynchronous filesystem operations on a worker
> thread
> * Parsing paths and invoking a FS-supplied traversal function for each
> directory element
> * Interfacing with the NT cache manager, including flushing data from
> the cache when a non-cached operation is performed on a cached file,
> and establishing cache maps for the underlying device for a disk-based
> file system
> * Providing a common implementation of byte range locks and oplocks,
> and disabling fast I/O when they are in use
> * Caching directory entry lookups
> * Performing typical input validation/security checks needed by all NT
> filesystems
> * Helper tools may also be provided to load pseudo-filesystems
> (filesystems with neither network nor disk backing) on an ad-hoc basis
>
> Essentially, the library should make it easy for the filesystem
> designer to focus on the actual filesystem, rather than the NT IFS
> interfaces - a read call would be able to skip all the preparation and
> checks, and directly go to perform the actual I/O.
>
> Major milestones for the project may include:
> - Prepare a sketch of the API and callbacks for the IFS helper library
> (subject to change if necessary)
> - Implement enough of the wrapper library to implement a simple
> pseudo-filesystem demonstrating non-cached reads and writes
> - Add support for cached reads/writes (interaction with the cache
> manager, caching for on-disk metadata)
> - Demonstrate a disk-based filesystem without metadata update support
> (MINIX FS or FAT?)
> - Demonstrate a disk-based filesystem with full read-write support
> - If time allows, add support for ancillary features, such as byte
> locks, oplocks, and notify watchers.
>
> The interfaces exposed by the filesystem library will of course be
> clearly documented. Filesystems needing more advanced support will
> also be able to override any IFS callbacks they choose.
>
> I have an existing consulting commitment that will take some of my
> time, but I expect to be able to put in 20-30 hours of work per week
> into this project. Further, I hereby swear that I have not used nor
> seen the source code to any version of the Windows operating system
> nor any Microsoft product that may be related to the proposed project
> that is under a license incompatible with contribution to ReactOS,
> including but not limited to the leaked Windows 2000 source code and
> the Windows Research Kernel.
>
> I would appreciate any comments on my proposal before formally
> submitting it to the GSoC site.
>
> Thanks,
>
> Bryan Donlan
>
>
Hi all,
Daniel Reimer wrote recently he is unable to organise due to a bereavement for
at least one week. So I will try to organise a little bit, even if i don't
know all things. To make it short, we need a list of booth personnel for the
period 11th May 2011 to 14th May 2011. We have to distinguish between booth
personnel and (even project members as) visitors, because as booth member you
can enter the fairground a little bit earlier. We have no hard limit, but we
should take care of the amount we request. Looking at the schedule we should
do this very soon, the deadline was 6th April. So please tell me/us when and
in which role you want to attend the LinuxTag in Berlin (we can get free
normal tickets for visitors and members if needed).
Maybe we should plan time for set up the booth on 10th May 2011. Do we need
any posters to prepare?
I already know, we are located in hall 7.2b
Suggestions, information remarks are very welcome, because I've lost the
overview and try to save the event.
Matthias
--
Matthias Kupfer phone +49 371 236 46 52
Wilhelm-Firl-Straße 21 mobile +49 160 859 43 54
09122 Chemnitz, Germany
--
Matthias Kupfer phone +49 371 236 46 52
Wilhelm-Firl-Straße 21 mobile +49 160 859 43 54
09122 Chemnitz, Germany
Hello all,
My name is Claudiu Mihail and I would like to introduce myself to the
ReactOS community. I am a computer science student from Bucharest, Romania.
I've been hanging around the IRC channel for sometime now under the nick
KlausM and I would like to participate in this year's GSoC un behalf of
ReactOS. As such I have opted for the "TCP/IP Driver Replacement Using lwIP"
idea. The reason why I chose this idea is because, after some discussions on
IRC with members of the community, it was setteled that this is something
that takes priority for ReactOS. I have basic kernel programming experience
on both Linux and Windows and am quite familiar with the Win32 API. I have
attached a PDF document with my resume and past projects in the hopes that
it will help determine if my skill set is compatible with the ReactOS
project demands.
Time commitment:
I will free to work on the ReactOS project I am applying for from the end of
april up until the end of august, the current year. I will have 2 week
period of exams from the beginning of July up until the 15th of July.
Legal Requirements:
I declare the following is *true:*
*
*
I have not used nor seen the source code to any version of the Windows
operating system nor any Microsoft product that may be related to the
proposed project that is under a license incompatible with contribution to
ReactOS, including but not limited to the leaked Windows 2000 source code
and the Windows Research Kernel.
Regarding the milestone part I have some basic sketches and would greatly
appreciate some pointers. After some discussions on IRC I have elarned that
there is already a branch dedicated to using lwIP. Bringing that branch up
to date should be the first task. Thus, during the community bonding period
I could do this task (if not earlier) and in so doing get familiarized with
the ReactOS codebase. After managing to bring the branch up to date versus a
trunk checkout I could further begin improving the replacement driver. Yet I
would very much appreciate some pointers as to more precise goals. In the
end there should be a fully functional driver and a suite of test cases,
that much is clear.
I don't have any previous experience with lwIP or protocol drivers but I
have some kernel programming experience and am willing to learn.
Thank you,
Claudiu
March Meeting Minutes
2010-03-31
20:30 UTC
Fezile IRC Server (fezile.reactos.org), #meeting
Participants
Present:
Giannis Adamopoulos
Johannes Anderwald
Javier Agustìn Fernàndez Arroyo
Maciej Białas
Aleksey Bragin
Colin Finck
Danny Götte
Ziliang Guo
Rafał Harabień
Kamil Hornicek
Amine Khaldi
Timo Kreuzer
Matthias Kupfer
Victor Martinez
Ged Murphy
Sylvain Petreolle
Hervé Poussineau
Daniel Reimer
Pierre Schweitzer
Samuel Serapion
Olaf Siejka
James Tabor
Art Yerkes
Proceedings
○ Meeting called to order at 20:30 UTC by Colin Finck
○ Point 1 in the agenda: ReactOS member definition
■ This point wasn’t easy to address, since there is no clear
criteria to apply in order to define the team members. As a result, a
discussion went on and ended up with an accepted proposal.
■ Colin Finck proposed that we skip a fixed definition of the term
"ReactOS Member", but instead maintain a list with names employing
the following rule: A person is added to this list if at least two
existing ReactOS members propose him and the list maintainer (Colin
Finck) or alternatively the backup list maintainer (Aleksey Bragin)
agrees with their proposal.
■ The participants accepted Colin’s proposal.
(15 yes votes, 2 no votes, 3 abstained)
○ Point 2: Current ReactOS work
■ Aleksey: Currently working on ntdll/ldr and kernel32/ldr loaders,
his next goal is undecided yet, he will look at what ReactOS needs
more from user perspective.
■ Amine: Currently working on the CMake branch, the website revamp
and the ideas around it.
■ Art: Currently working on fixing a few crashes running the
regression test CD on the NewCC branch.
■ Colin: He has been busy with preparing the 0.3.13 release, then
Chemnitz Linux Days, afterwards this meeting. He will be on a trip
abroad starting 9th April and will return 13th May, he’s not yet
sure what he will do then.
■ Daniel: He will continue to work on RosBE 1.6/2.0. Playing with
the new GCC 4.6 right now. He also regularly works on forum
moderation, translations and the rapps database.
■ Giannis: He has been working on fixing several bugs in win32k
lately. This included multiple issues in ancient code related to
handling desktops and window stations. He looks forward to apply for
GSoC and work on theming support.
■ Matthias: He is occasionally working on small bugfixes for the
ReactOS source tree. His main ReactOS work lies in leading the German
foundation and preparing ReactOS appearances at events in Germany
(passed Chemnitz Linux Days and upcoming LinuxTag in Berlin).
■ Maciej: Right now, he is investigating forum modules and
extensions for Drupal, which could be handy for our users. This is
part of the ongoing website revamp (point 6 in the meeting agenda).
■ Olaf: He has been working on our BuildBot, doing some cleanup work
and setting up some builders for the NewCC branch and patches. He
will handle the remaining issues like a need to backup the VBox test
logs. When the new RosBE is out, he is going to try to make use of it
within CMake build scripts. He has also been introducing the WIP
(Work In Progress) tag in our Bugzilla and is going to push some more
bugs marked with the PATCH tag to developers.
■ Pierre: For the moment, he is mainly cleaning up some parts of
kernel32, focusing on the code inside the “file” subdirectory.
This requires implementing the Mount Manager, which he is also doing.
This may help to bring several improvements elsewhere in ReactOS. His
work on FsRtl and especially the FsRtlIs*InExpression functions is
also still going on. The current implementation will be superseded by
a proper algorithm based on a NFA as soon as he has the time. He is
moving to the CERN starting on 4th April, so his involvement in the
project might change soon.
■ Samuel: He is already working on secur32, lsalib and schannel to
refine his GSoC proposal.
■ Sylvain: He has been busy with various tasks related to the CMake
branch, regression tests and bug fixing.
■ Timo: He is working on the GDI handle manager, better performance/
scalability, better tracking of errors that could lead to deadlocks/
leaks and minor interface improvements. Will take some time to get it
right.
■ Victor: He is continuing working on PR aspects. He has just
returned from another show in Huelva (Spain). Youtube videos will be
available soon. He will also work on the website revamp and on
improving the users forum experience, trying to create testing
coordination. He is open to any suggestion regarding PR and
attracting new users and developers.
■ Ziliang: Mostly doing GSoC preparation work at the moment. He is
also preparing his own GSoC application concerning performance counters.
○ Point 3: Status of our GSoC participation, in particular students
and mentors
■ Amine reported that we have got some student applications, but we
still await more. As to mentors, so far we need Hervé and Kamil to
register as mentors in the web platform, and we welcome more mentors
and at least co-mentors to do the same. So far, we have Aleksey, Art,
Ged, Pierre and Kamil as confirmed mentors. As to timeline, for
student applications it is 8th April, and to get everything sorted
out it is 22nd April.
○ Point 4: Upcoming LinuxTag event on 11th to 14th May
■ Matthias reported that our project has been accepted this week for
LinuxTag, so we would like to invite all ReactOS Team members to take
part. He stated that he will be there the whole time if necessary,
but he recommends that more members take part.
■ Victor expressed that he will be there from 11th to 13th.
■ Matthias thinks that we need at least 2 team members per day, and
3-4 team members overall. He also mentioned that, depending on the
count of persons, we cannot pay all expenses for accommodation and
transport.
■ Colin stressed out the fact that this is Europe's most-important
event regarding Open-Source, and that it would not just be a good
chance to present the project internationally, but also to get in
touch with other ReactOS members.
○ Point 5: Sum up of previous events, ideas for next ones
■ Colin reported that we recently had the Chemnitz Linux Days event
again. We presented ReactOS on 4 laptops there, two native and two in
VMs. Compared to last year, ReactOS was now able for two major
breakthroughs: One of the laptops running in a VM was capable of
streaming internet radio all day long, while on the other hand,
ReactOS was also able to run natively on a 4-year old system (with
SATA controller!). The only caveat preventing the real usefulness of
the native system was the lack of a working network driver for the
Intel PRO/1000 PL chip. Having an improved network/driver stack would
have made the presentation even better. He I assumes we had 50%
interested people who already knew about ReactOS and wanted to hear
about the updates in the last year, while the other half was
completely new to ReactOS. Colin thinks we still have enough
potential to make new people aware of the project and maybe even gain
more developers. That was just said to understand why we are so eager
about PR lately and have the next event in not much more than a month.
■ Victor reported that he has been holding 2 events lately. The
major one is Imaginatica'11. We had a booth there and a showroom, and
had a lot of visitors quite interested in ReactOS. Even more, we had
2 important visits from a company and CSIC (Spanish investigators)
who asked if a Windows driver would work in ReactOS, because they are
doing embedded systems. They also asked Victor if we would work on
sponsored specific compatibility aspects, which means "if I pay you a
certain amount for having OpenOffice and ContaPlus working, will you
work on it ?". Victor suggested as a result that this "Compatibility
On demand" concept is a possible market. He also was holding another
speech in Huelva: "Jornadas Tecnlogicas". The best thing about this
was that it is the first time an Event has contacted us to show
ReactOS. As a result of the recent events, he noticed that we have to
change our presentations style from the quite technical ones to the
quite general ones, for a wider audience. He also reported that he
was contacted by a new Spanish designer thanks to Imaginatica. This
was a direct result of his emphasis on the fact that we don't just
need developers, but also skilled members in the other departments,
including designers, bloggers, testers, users, etc. Victor will see
if this new designer has web design capabilities, in which case he
may join our website revamp efforts.
○ Point 6: Website revamp. Current status, who is working, who is
willing to help
■ Colin mentioned that we still want a complete revamp of our
website, starting from scratch with the articles and also dropping
RosCMS and basing everything around the Drupal CMS. He also mentioned
that while the design winner from 2009 is still the target design, it
needs to be adapted to Drupal now, not just due to the different
technology behind Drupal, but also because our Drupal website should
be more based on activity (as outlined in our website revamp google
document)
■ A technical discussion has been held to try to analyze the needs
and discuss how they will be addressed.
■ Victor is in contact with a Spanish designer, hopefully he can
work with him on the design department.
■ Ziliang will be taking care of the content department.
■ Maciej will handle the technical aspects of the website revamp, he
set up a testing server where we are going to test the Drupal 7-based
website revamp. Moving this server to an officially hosted VM is
planned.
■ Danny is handling the VM on the ReactOS server.
■ We agreed on working on these different departments in parallel.
○ Meeting ended at 23:57 UTC.
○ Minutes submitted by Amine Khaldi.
Hi James,
Yes, most interesting, but isn't it a little beside point?
I mean, we're still targeting the XP kernel in ReactOS, aren't we?
Or have I missed a re-targeting point in my absence?
WBR // Love
2011/3/31 <ros-dev-request(a)reactos.org>
> ---------- Forwarded message ----------
> From: James Tabor <jimtabor.rosdev(a)gmail.com>
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Date: Wed, 30 Mar 2011 19:23:40 -0500
> Subject: Re: [ros-dev] [ros-diffs] [gadamopoulos] 51115: [ntoskrnl] -
> Implement calling OkayToCloseProcedure callouts to win32k for desktop and
> window station objects - Fix a bug that caused ObpCloseHandle to return
> success even whe...
> Hi everyone,
> http://www.alex-ionescu.com/ Main Blog,
> http://www.alex-ionescu.com/?p=61 Black Hat 2008 Wrap-up <------- here
> http://www.alex-ionescu.com/BH08-AlexIonescu.pdf <------------------ read
>
> I would like everyone (new Developers) that haven't read this blog to
> do so and get up to date!
>
> I'm not sure if M$ fixed their issues, it may not be Server 2003 but
> at least 2008 plus or 7.
>
> Thanks,
> James
>
> ps I have the right to use M$ since 1983........
>
> On Tue, Mar 22, 2011 at 9:19 AM, Alex Ionescu <ionucu(a)videotron.ca> wrote:
> > It's hilarious how this new code has the exact same Windows security bug
> I gave a talk about at BlackHat 2-3 years ago (which Microsoft fixed in
> Vista).
> >
> > It's sad how this code ignores the exported PsSetProcessWindowStation API
> and relevant EPROCESS field.
> >
> > It's awesome how nothing changes whenever I prop up to see the
> "progress".
> >
> > --
> > Best regards,
> > Alex Ionescu
>
Thank You for understanding, Adam!
Here's an off-topic for all of You, my Brothers in Arms ..
http://www.youtube.com/watch?v=q2rx3IAEISA
<http://www.youtube.com/watch?v=q2rx3IAEISA>
Happy listening.
Peace
// Love
On Sun, Apr 3, 2011 at 2:21 PM, Adam <geekdundee(a)gmail.com> wrote:
> I know exactly what you mean. I live with autism (although not severe) and
> depression and it's not good stuff that these things occur. I have seen your
> past mails and they are not too shabby.
>
> Allocating time is a hard thing because unlike ReactOS I do not have a
> priority-driven round-robin scheduler.
>
> Hope you get better soon mate.
>
>
> On Sun, 03 Apr 2011 16:55:38 +1000, Love Nystrom <love.nystrom(a)gmail.com>
> wrote:
>
> As a side note, my shitty RL situation is largely responsible for my
>> occasional tantrums,
>> for which I am truly sorry. Taking my RL frustrations out on my Brothers
>> In Arms is *unfair*.
>> I am trying hard to find a more stable RL solution that will allow me to
>> allocate time to ReactOS
>> coding, but nothing is yet for certain .. all just a glimmer of hope.
>>
>
Hi all,
Even though Chemnitzer Linux-Tage has not been that long ago, I can
already announce that the ReactOS Project has received a sponsored booth
at LinuxTag 2011 in Berlin. LinuxTag is considered to be Europe's most
important Open-Source event and it takes place from 11th to 14th May at
the Berlin Fairgrounds.
As it is much more directed at an international audience compared to the
Chemnitz event, it would be nice if we can get many ReactOS team members
to attend it.
So far, I already got a positive answer from Aleksey for 1-2 days,
Matthias for the whole time and Victor for an unspecified time. I myself
will still be away from Germany during this time, so I won't be able to
come.
The German foundation might be able to refund some of the transport and
accomodation costs, but this also depends on the number of ReactOS
members present.
On the other hand, this mail should of course also serve as a call for
interested people to visit us in Berlin :-)
With best regards,
Colin
Hello,
After reading the ReactOS GSoC ideas page, I became interested in the
IFS wrapper driver project idea[1], and would appreciate any comments
on my project proposal before I formally submit it.
First, a bit about me. I am a student in a dual-major program,
studying Computer Science and Japanese at the University of
Massachusetts at Amherst. I have had some experience in kernel
development previously; as part of an internship at a research project
at my University, I wrote some network flow analysis code running in
the Linux kernel. While filesystem work will be a first for me, I
think it will be an interesting leaning experience. I am fluent in
English and Japanese, and am in the UTC-0400 timezone (TZ=US/Eastern).
My freenode username is bd_, and my myReactOS username is bdonlan.
In preparation for writing this proposal, I obtained a copy of the
"Windows NT File System Internals: A Developer's Guide" book from
O'Reilly. Although a bit dated, it has been enourmously helpful in
helping me get an idea of what I'm getting into.
My goal in this project will be to write a library to significantly
simplify writing a NT File System Driver. Although writing a
kernel-mode filesystem will never be as easy as with, eg, FUSE, it
should be possible to abstract away many of the idiosyncracies of the
NT filesystem API, at least. For example, the wrapper library may
handle:
* Automatically queueing asynchronous filesystem operations on a worker thread
* Parsing paths and invoking a FS-supplied traversal function for each
directory element
* Interfacing with the NT cache manager, including flushing data from
the cache when a non-cached operation is performed on a cached file,
and establishing cache maps for the underlying device for a disk-based
file system
* Providing a common implementation of byte range locks and oplocks,
and disabling fast I/O when they are in use
* Caching directory entry lookups
* Performing typical input validation/security checks needed by all NT
filesystems
* Helper tools may also be provided to load pseudo-filesystems
(filesystems with neither network nor disk backing) on an ad-hoc basis
Essentially, the library should make it easy for the filesystem
designer to focus on the actual filesystem, rather than the NT IFS
interfaces - a read call would be able to skip all the preparation and
checks, and directly go to perform the actual I/O.
Major milestones for the project may include:
- Prepare a sketch of the API and callbacks for the IFS helper library
(subject to change if necessary)
- Implement enough of the wrapper library to implement a simple
pseudo-filesystem demonstrating non-cached reads and writes
- Add support for cached reads/writes (interaction with the cache
manager, caching for on-disk metadata)
- Demonstrate a disk-based filesystem without metadata update support
(MINIX FS or FAT?)
- Demonstrate a disk-based filesystem with full read-write support
- If time allows, add support for ancillary features, such as byte
locks, oplocks, and notify watchers.
The interfaces exposed by the filesystem library will of course be
clearly documented. Filesystems needing more advanced support will
also be able to override any IFS callbacks they choose.
I have an existing consulting commitment that will take some of my
time, but I expect to be able to put in 20-30 hours of work per week
into this project. Further, I hereby swear that I have not used nor
seen the source code to any version of the Windows operating system
nor any Microsoft product that may be related to the proposed project
that is under a license incompatible with contribution to ReactOS,
including but not limited to the leaked Windows 2000 source code and
the Windows Research Kernel.
I would appreciate any comments on my proposal before formally
submitting it to the GSoC site.
Thanks,
Bryan Donlan
[1] - http://www.reactos.org/wiki/Google_Summer_of_Code_2011_Ideas#IFS_Wrapper_Dr…
Hi Colin,
Please put me on the list as well, would You?
Because of a real shitty RL situation I haven't been able to contribute the
way I would like to,
but believe me when I say I am committed to the success of the ReactOS
project.
I guess we all have our own reasons.. Mine is by and large to be free of
Microsoft!
As a side note, my shitty RL situation is largely responsible for my
occasional tantrums,
for which I am truly sorry. Taking my RL frustrations out on my Brothers In
Arms is *unfair*.
I am trying hard to find a more stable RL solution that will allow me to
allocate time to ReactOS
coding, but nothing is yet for certain .. all just a glimmer of hope.
Peace
// Love
On Tue, Mar 29, 2011 at 5:23 PM, <ros-dev-request(a)reactos.org> wrote:
>
> > Date: Tue, 29 Mar 2011 00:32:20 +0200
> > From: colin(a)reactos.org
> > To: ros-dev(a)reactos.org
> > Subject: [ros-dev] Meeting on Thursday
> >
> > Hi folks,
> >
> > As proposed in our urgent meeting in February, we are going to have
> > regular meetings at 20:00 UTC on the last Thursday of every month. Next
> > Thursday will be the first time to hold such a meeting.
> >
> > While I was preparing the technical side (we're going to have a
> > dedicated IRC server with voting capabilities this time), Amine and
> > Victor have come up with a meeting agenda. We have agreed on the
> > following points in this order:
> >
> > - ReactOS member definition. Proposal is not to establish a fixed
> > definition, but decide upon always keeping a list of people and just
> > giving hints on how you can get on this list
> > - Current ReactOS work. Developers saying what they are working on
> > - Status of our GSoC participation, in particular students and mentors
> > - Upcoming LinuxTag event on 11th to 14th May
> > - Sum up of previous events, ideas for next ones
> > - Website revamp. Current status, who is working, who is willing to help
> >
> > You see that the list is more about inquiring and getting information
> > than doing vital decisions this time. The agenda is also prioritized so
> > that people may leave if they don't want to participate in website
> > discussions for example.
> > If nobody else volunteers, Amine would be in the minute taker position
> > again and I would take the meeting leader role.
> >
> > My current list of ReactOS members is as follows. Only these people will
> > be able to participate in the discussions and votings, so please tell me
> > if I have forgotten anybody or if you want to be added to this list:
> >
> > - Giannis Adamopoulos (smiley1_)
> > - Johannes Anderwald (janderwald)
> > - Javier Agustìn Fernàndez Arroyo (elhoir)
> > - Maciej Bialas (niski)
> > - Aleksey Bragin (abragin)
> > - Colin Finck (Colin_Finck)
> > - Danny Götte (dangerground)
> > - Cameron Gutman (aicom)
> > - Ziliang Guo (ZWabbit)
> > - Rafal Harabien (rafalh)
> > - Kamil Hornicek (Pigglesworth)
> > - Amine Khaldi (AmineKhaldi)
> > - Timo Kreuzer (tkreuzer)
> > - Matthias Kupfer (Collibri)
> > - Michael Martin (mjmartin)
> > - Victor Martinez (vicmarcal)
> > - Roel Messiant (Mephisto)
> > - Andrew Munger (WaxDragon)
> > - Ged Murphy (GedMurphy)
> > - Sylvain Petreolle (Usurp)
> > - Hervé Poussineau (hpoussin)
> > - Daniel Reimer (dreimer)
> > - Pierre Schweitzer (HeisSpiter)
> > - Samuel Serapion (encoded)
> > - Olaf Siejka (Caemyr)
> > - James Tabor (jimtabor)
> > - Art Yerkes (arty)
>
Hi,
I am student IT technology college, I can programming in C, NASM or C#. I want try make project for GSoC. I have some teoretic knowledge about filesystem from school. Can you help me with choice ideas from project ?
Thank you
Hi folks,
As proposed in our urgent meeting in February, we are going to have
regular meetings at 20:00 UTC on the last Thursday of every month. Next
Thursday will be the first time to hold such a meeting.
While I was preparing the technical side (we're going to have a
dedicated IRC server with voting capabilities this time), Amine and
Victor have come up with a meeting agenda. We have agreed on the
following points in this order:
- ReactOS member definition. Proposal is not to establish a fixed
definition, but decide upon always keeping a list of people and just
giving hints on how you can get on this list
- Current ReactOS work. Developers saying what they are working on
- Status of our GSoC participation, in particular students and mentors
- Upcoming LinuxTag event on 11th to 14th May
- Sum up of previous events, ideas for next ones
- Website revamp. Current status, who is working, who is willing to help
You see that the list is more about inquiring and getting information
than doing vital decisions this time. The agenda is also prioritized so
that people may leave if they don't want to participate in website
discussions for example.
If nobody else volunteers, Amine would be in the minute taker position
again and I would take the meeting leader role.
My current list of ReactOS members is as follows. Only these people will
be able to participate in the discussions and votings, so please tell me
if I have forgotten anybody or if you want to be added to this list:
- Giannis Adamopoulos (smiley1_)
- Johannes Anderwald (janderwald)
- Javier Agustìn Fernàndez Arroyo (elhoir)
- Maciej Bialas (niski)
- Aleksey Bragin (abragin)
- Colin Finck (Colin_Finck)
- Danny Götte (dangerground)
- Cameron Gutman (aicom)
- Ziliang Guo (ZWabbit)
- Rafal Harabien (rafalh)
- Kamil Hornicek (Pigglesworth)
- Amine Khaldi (AmineKhaldi)
- Timo Kreuzer (tkreuzer)
- Matthias Kupfer (Collibri)
- Michael Martin (mjmartin)
- Victor Martinez (vicmarcal)
- Roel Messiant (Mephisto)
- Andrew Munger (WaxDragon)
- Ged Murphy (GedMurphy)
- Sylvain Petreolle (Usurp)
- Hervé Poussineau (hpoussin)
- Daniel Reimer (dreimer)
- Pierre Schweitzer (HeisSpiter)
- Samuel Serapion (encoded)
- Olaf Siejka (Caemyr)
- James Tabor (jimtabor)
- Art Yerkes (arty)
Everybody may join the meeting channel as a non-participating observer
though. I'll hand you all connection details when we're ready.
With best regards,
Colin
Hi!
My name is Ilie Halip, and I'm a student at the Faculty of Computer Science,
in Iasi, Romania. I'd like to take part in this year's Google Summer of
Code, and I was browsing the ideas page earlier.
What caught my eye was the Management Console, but after some discussions on
IRC, I got very excited about another thing not listed on the wiki page for
GSoC. It's about implementing support for Windows Error Reporting. It's
listed at http://reactos.org/wiki/Missing_ReactOS_Functionality. I think
it's doable in less than 3 months, and might prove to be helpful too (the
wiki page sais that :P). I'm not sure if you would accept this kind of
proposal, so I'm here to ask about that. Also, I would need a mentor to help
me with this project - so... would anyone be willing to mentor me, if this
project would be accepted? I was also looking at WMI, but I know it's huge,
and I'm not sure how much of it would be required to consider such a project
successful.
Also, another thing I should mention. I do have a full time job right now.
That's a reason I didn't dive into anything bigger listed on the ideas page.
Even though I do have some experience writing Windows drivers (I wrote a
file system filter driver 2 years back), I don't think I'd be able to write
an Intel HDA driver in less than 3 months. But I talked to my superiors, and
they are willing to let me work part-time during GSoC, so I should be able
to work for my would-be project about 30 hours/week. Do you think that's
enough?
Regards,
Ilie.
Hi Alexey,
Since you are still working on these LdrXXX functions then you maybe
find possibility
to add there some code to prevent them trapping into infinite cycle (bug 5881:
http://www.reactos.org/bugzilla/show_bug.cgi?id=5881 )
While booted up with RAM 25 or 24 MB ROS kernel falls into infinite
cycle there,
but being booted up with 15 Mbs ROS stalls and and hangs up.
To test it is enough to run it on any VM with 24Mb of RAM.
What occurs there is infinite recursive calls, in form of
LdrpLoadModule ->calls LdrFixupImports -> LdrpGetOrLoadModule ->
LdrpLoadModule and so forth.
(detailed bt is in bug 5881 description).
Maybe ROS kernel doesn't check memory availability, something like
XXXMalloc returning NULL or so.
Thanks!
-M.A.
On Wed, Mar 23, 2011 at 4:25 PM, <fireball(a)svn.reactos.org> wrote:
> Author: fireball
> Date: Wed Mar 23 12:25:53 2011
> New Revision: 51123
>
> URL: http://svn.reactos.org/svn/reactos?rev=51123&view=rev
> Log:
> [NTDLL/LDR]
> - Fix a few bugs (wrong variable usage, wrong variable initialization) which led to incorrect snapping of import address table.
> - Wrap LdrpSnapThunk() invocations into SEH.
>
> Modified:
> trunk/reactos/dll/ntdll/ldr/ldrpe.c
>
> Modified: trunk/reactos/dll/ntdll/ldr/ldrpe.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/dll/ntdll/ldr/ldrpe.c?rev=…
Hello fellow ReactOS developers and users,
Most of you might know me from IRC as encoded. I am a Computer Science
student at the Polytechnic University of Puerto Rico. Although at
times not the best IRC citizen, I've always had the best intentions
for ReactOS at heart. The following is my proposal/plan outline for
Implementing SSPI and secure authentication mechanisms for ReactOS,
including Interactive Logon.
First, some definitions:
Security Support Provider Interface (SSPI) allows applications to use
various security models available on a computer or network without
changing the interface to the security system. SSPI does not establish
logon credentials because that is generally a privileged operation
handled by the operating system(LSA).
Windows Challenge/Response (NTLM) is the authentication protocol used
on systems running Windows. NTLM credentials are based on data
obtained during the interactive logon process and consist of a domain
name, a user name, and a one-way hash of the user's password. NTLM
uses an encrypted challenge/response protocol to authenticate a user
without sending the user's password over the wire(in case there is a
wire). Instead, the system requesting authentication must perform a
calculation that proves it has access to the secured NTLM credentials.
Secure Channel, also known as Schannel, is a security support provider
(SSP) that contains a set of security protocols that provide identity
authentication and secure, private communication through encryption.
Mainly SSL and TLS, with a variety of cipher options.
Primary goals:
- Utilize wine secur32 as starting point for implementing SSPI.
- NTLM Security Support Provider (SSP)
-- Authentication
-- feature flags
-- SignMessage
-- VerifyMessage
-- EncryptMessage
-- DecryptMessage
- Small, low footprint, maintainable code
- Implement create credentials/logon/authentication in LSA
-- LogonUser
-- LsaConnectUntrusted
-- others, as necessary.
- Separate secur32 and schannel(wine has them unified)
Secondary goals:
- implement SSL/TLS/ptc SSP (using 3rd party libs)
-- GnuTLS, OpenSSL are huge and have many dependencies
-- secur32 is (theoretically) loaded and used by many system dlls,
would be very bad if it is a performance/memory hog.
-- Need to severely trim them down or use alternatives.
- run extensive tests/fix other system code paths that have been dormant/stubs
why wine secur32 is bad:
- Wine is a *nix program so its ok for them to use
dlopen(gnutls.so)... and use the system native library but we cant.
- Uses fork() to call a program in winbind(samba extra) package!
- if we want to use gnutls and such in reactos the following problems occur:
-- too many dependencies
-- problems running in native mode(lsa)
-- big footprint
-- too much code/hard to maintain
- Wine's implementation of schannel loads GnuTLS, and is barely functional.
- wine winhttp and wininet don't use schannel, and instead use OpenSSL
directly to implement SSL and TLS. This can lead to confusing
differences in certificate verification between applications. Ideally,
schannel would use crypt32 for certificate chain verification, and
winhttp and wininet would use schannel. (fixme later)
-- good news is, wine crypt32 is relatively good and feature complete
(at least seems that way).
Hi,
I guess I don't have to introduce myself all that much anymore ;)
Please see [1] if you disagree.
I plan to submit a GSoC project proposal concerning the kernel-mode
test suite, and would like to discuss a few key points to better shape
the project idea and its timeline.
Because of the broadness of the subject, I'm posting here to reach
as many ears (er... eyes) as possible, hoping for feedback from people
working on several different areas of ROS.
My "state of mind" is currently the following regarding the project:
Basic key points (I hope everyone agrees; please tell me if I'm wrong :p)
- follow Winetest "feeling" - syntax for writing tests should be almost
identical; like current kmtests demonstrate
- tests should be startable individually from a command line launcher and
follow Winetest behavior in that regard, so that an integration with
Testman is made easy
- code should be CMake and MSVC/WDK compatible from the beginning
Ideas I deem useful (would appreciate any comments)
- include buffer overrun checks, much like DPH (DPH can't be used for
this though, can it?), using e.g. a guard/noaccess page behind each
buffer. See [2] for a userland example; I'm working on a kernel-mode
one
- inspired by Winetest's broken(), one could make tests Windows-version
specific. Something like [but better thought-out in syntax]
ok(win2k3sp1(ret == 0) | win7x64sp1(ret == 1), ...)
This would help compare different versions of Windows and much
facilitate future kernel-target switching
Questions
- as there are ... many... kernel-mode functions, it is unfeasible to
write tests for all during the project. My idea would be to create
some very thorough sample tests, then focus on the most critical
functions. "If there's time", thinly covering a more broad area might
also be very useful (as extending existing tests is probably deemed
easier than creating new ones by people later on).
I have no doubt there's enough to do, ;) but would be interested to
hear if you agree with the general strategy and what you think those
"critical" areas might be.
So what do you guys think?
Excited for your input. Thanks. :)
Regards,
Tom
[1] Hi! I'm Thomas, 23, from Germany, currently studying Computer
Engineering in Berlin. I've been hanging out on IRC as ThFabba
for some time now and submitted some hopefully-not-totally-useless
patches ;) I'm interested in.... oh well, pretty much all parts
of ROS. *g* Nice to meet you!
[2] http://www.reactos.org/paste/index.php/8697/
Good day to all,
my name is Fabio Cristini. I work as a software designer and developer in
Italy, I'm a student in Software Engineering and I would like to apply for a
React OS project proposal.
I especially like the idea of implementing an SSH Service for Windows, and I
hope I can do it for you (I like to develop an OpenSSH clone).
Please let me know if you may be intrested.
Fabio Cristini
Italian, English +1 UTC
fcristini(a)gmail.com (not registered yet)
if you can contact me in private, I can give you more details and my full
contact informations.
Many thanks
Time Commitment
I can work at this project about 20 hours a week
Optional (But Suggested)
SSH Service for Windows
http://www.reactos.org/wiki/Google_Summer_of_Code_2011_Ideas#SSH_Service
Legal Requirements
Students are required to affirm that the following is true. I hereby swear
that I have not used nor seen the source code to any version of the Windows
operating system nor any Microsoft product that may be related to the
proposed project that is under a license incompatible with contribution to
ReactOS, including but not limited to the leaked Windows 2000 source code
and the Windows Research Kernel.
Hello friends,
I am Syed Armani, i am a 3rd year computer science student at DCE ,NCR,
INDIA
Email: dce3062(a)gmail.com
IRC: #armaan
Jabber: syedarmani(a)jabber.org
*ABOUT ME:*
I have experience of
- c/c++
- GUI development with c++.
- python
- java
- lua
- NETWORK PROTOCOLS
- NETWORK PROGRAMMING
- xhtml/css/javascript
- Assembly (mid level 8085 n 8086)
- BASH scripting.
- VIRTUALIZATION, WORKING OF HYPERVISORS AND LIBVERT.
- PHP
- MYSQL
- DEEP LEVEL LINUX OS
- BASH SCRIPTING
- LAMP/WAMP
- WEB 2.0
- Android apps development
I have a personality of a creative explorer and i always seek knowledge. I
consider experience as a very very important thing.
My wish is to take part in the development process of react os.
Regards
Syed Armani
Thanks for that guys, it's really helpful....
From: Ged Murphy [mailto:gedmurphy@gmail.com]
Sent: 29 March 2011 11:22
To: 'ReactOS Development List'
Subject: unanswered gsoc mails
I've noticed there are quite a few emails to ros-dev regarding GSoC
participation with no replies.
Can someone reply to these in my absence, I won't be around for a few more
days yet.
As usual, I'm contactable by email and msn.
Ged.
I've noticed there are quite a few emails to ros-dev regarding GSoC
participation with no replies.
Can someone reply to these in my absence, I won't be around for a few more
days yet.
As usual, I'm contactable by email and msn.
Ged.
I have been thinking about what will be needed for my gsoc proposal.
Merging the live cd and install cd of React OS is one of the goals.
Though the file structure is different on the install and live cd.
The install cd has all the React OS files in a cab file. While live cd
has everything in a folder.
I do understand the differences are larger than this. Though this has
a large duplication of files. I assume having the files in folders is
the best solution because the live cd needs access to the files
directly.
I was wondering what peoples preferred methods would be.
People mentioned various things on irc. like extracting from the cab
file on the fly, or installing the cab to ram disk and so on.
I was wondering what peoples views is on what they would want. Feel
free to say your preferences. I may not choose the best solution in my
proposal because I will only have 3 or 4 weeks to work on that part.
I personally don't think loosing the 100mb of saved space from the cab
is a bad thing. It will still fit on 1 cd(i'm guessing 150-200mb) and
is better than burning 2 cds(1 for live and 1 for install).
Any comments or advice are much appreciated.
>
> ---------- Forwarded message ----------
> From: Olaf Siejka <caemyr(a)gmail.com>
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Date: Sun, 27 Mar 2011 14:35:18 +0200
> Subject: Re: [ros-dev] MP/UP HAL issues
> "but *compile time* is not even 10% as important as *run time*."
>
> I think Love that you do not imagine what is the impact of buildtime in our
> project. As ReactOS is not getting smaller, increased buildtime is simply
> slowing down development pace by a considerable margin. It might be a worthy
> tradeoff for a project with production version already, but not in our case.
> Reaching over 10 minutes of buildtime requires really top of the line
> hardware, not to mention dedicating whole host system to this task. For
> average team member, it takes not 10 but even over 30-40 minutes to do a
> full build. Time that is often so precious to spare.
>
Yes, Olaf, I *do* consider the impact of build time. It used to take me ~30
min to do a full build.
This made me abandon the RAD "trial-and-error" rebuild paradigm, and return
to the old-fashioned
way of "running the code in my head" a number of times before doing another
build. Now I have a
faster machine and a full build takes ~10-15 min, but I still stick with the
old-fashioned way of coding
with those build times.
As for time spared, consider this, You may save 2-5 min build time, but that
time is paid
for by millions of users, over and over and over again... *That* is what I
mean.
WBR // Love
>
> ---------- Forwarded message ----------
> From: Timo Kreuzer <timo.kreuzer(a)web.de>
> Subject: Re: [ros-dev] MP/UP HAL issues
>
> Am 26.03.2011 11:45, schrieb Love Nystrom:
>
To me, performance is *everything* ..
> I gladly spend a *week* to gain significant performance,
> especially if it also makes the code clearer and more readable!
>
> And what if it makes the code harder to read and maintain or if its likely
> to introduce bugs later? Performance is great, but you need to be
> reasonable. Saving a few clock cycles, saving you a microsecond per minute
> runtime is not worth downgrading code quality. Its not even worth massively
> increasing build time.
>
Ah.. Yes, *code clarity* (and proper comments) is of course a primary. We
all know the headache
of fixing code we wrote a year ago and didn't take the time to make
stringent and/or comment properly.
Btw. when I mention performance improvements, I meant in the order of at
least > 5-10%.
We all know that's never achieved by a cpl of asm tweaks, always by improved
algorithms.
As for Win7 I can't tell either way, since I don't have it..
Just a general note that apps that would fit well in 3MB RAM if written
properly, now seem
to hog up at least 30MB wherever it comes from, and runtime has gone the
same way.
C# + .NET issue perhaps? Or just incompetent newbie programmers running
amok?
Dropping single core processor support sound like a bad idea to me.
>
> Tell that MS, they did that with Windows Vista already.
>
I tried telling MS a lot of things.. Like fixing some of their bugs that
*still live* since
the days of NT4 at least. All I I ever got was a blatant "Won't Fix". So.. F
them!
Also I wasn't even talking about dropping the up kernel, I suggested
> compiling it in a different manner, that would not allow inlining spinlock
> functions as its done currently, but would cause them to be called. The
> function would be linked as UP or SMP depending on whether we are using UP
> or SMP kernel (can be done at link time or even at runtime).
>
I understand.
> This way we save us the complete MP kernel build time (almost 2 minutes on
> my machine).
>
Well.. as I said.. personally I don't give a hoot about another 2 minutes
build time.
> IMO it would also make it easier to maintain the SMP kernel.
>
Now *that* (code clarity and maintainability) is a more important issue IMO.
In my book, that usually means using *the same code* with *minor* precomp
switches.
WBR // Love
>
>
>
> ---------- Forwarded message ----------
> From: Timo Kreuzer <timo.kreuzer(a)web.de>\
>
[abbreviated]
>
> I'm against wasting precious compile time for an MP hal that doesn't even
> work. And I would actually like to have the kernel being compiled the same
> way. I bet the performance improvements of inlining some spinlock code are
> really neglectable.
>
I hate being a spoilsport, especially on an issue that may have gone stale
already,
but *compile time* is not even 10% as important as *run time*.
I dunno about the particulars in this case, it's just a general priority
opinion.
To me, performance is *everything* ..
I gladly spend a *week* to gain significant performance,
especially if it also makes the code clearer and more readable!
Is it just I who think that software is getting slower and slower and bigger
and bigger these days?
And I mean particularly the goo gaa that comes out of Redmond these days :-/
But as everybody in the world seems to play "Follow John" with Microsoft,
users are left with software where they have to go for a coffe break after
giving a command
before their multicore superduper computers even give a burp, because
programmers
care less about runtime than compile time these days :(
Blame the RAD frenzy for that!
I'd even go as far as dropping UP support completely and hotpatching
> spinlock functions.
>
Dropping single core processor support sound like a bad idea to me.
W.B.R.
// Love
I'm looking to put in a proposal for gui 1st stage installer. I've
asked around a bit on IRC who would be the mentor. Though no one seems
to know. If anyone could point me in the right direction that would be
great.
I was thinking of how it would be implemented. I know the gui mostly
exists in svn. so that simplifies that.
I was thinking that the parts of the project would be setting it up so
that as much code is shared between text-mode installer and gui
installer.
1st stage gui installer should be able to run in windows as well as
ros(this could simplify the install when using windows and make it
easy to test the installer)
Also fixing the functions that are used. As it seems at the moment
disk drives are not appearing as devices.
I have been unable to find an api that creates partitions. I thought
this would be good rather than manipulating the disk directly as it
may provide the ability to create partitions for any file system as
long as a driver exists. Making it more flexible.
I am also rather excited about this project as the skills that I gain
from this could be used to make the disk manager, and other disk
utilities.
Any comments would be much appreciated.
We use SIZE_T throughout the kernel, so I don't understand why change
a couple of places (out of thousands) to size_t ? Is there an
incompatibility between strsafe headers and that type? Then it would
need fixing instead.
Also not sure if that was on purpose, but you also removed null-
termination in ex/init.c, but it's not mentioned in the commit message.
WBR,
Aleksey Bragin.
On Mar 26, 2011, at 12:42 AM, rharabien(a)svn.reactos.org wrote:
> Author: rharabien
> Date: Fri Mar 25 21:42:48 2011
> New Revision: 51135
>
> URL: http://svn.reactos.org/svn/reactos?rev=51135&view=rev
> Log:
> [PSDK]
> Import strsafe.h from mingw-w64. It's more complete compared to our
> headers
>
> [DDK]
> Import ntstrsafe.h from mingw-w64 (converted from strsafe.h). It's
> more complete compared to our headers
>
> [NTOSKRNL]
> Use sizeof instead of magic numbers
>
> Let's use strsafe functions now instead of strncpy/wcsncpy, which
> doesn't always NULL terminate :)
>
> Modified:
> trunk/reactos/base/applications/notepad/notepad.h
> trunk/reactos/include/ddk/ntstrsafe.h
> trunk/reactos/include/psdk/strsafe.h
> trunk/reactos/ntoskrnl/ex/init.c
>
> [This mail would be too long, it was shortened to contain the URLs
> only.]
>
> Modified: trunk/reactos/base/applications/notepad/notepad.h
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/base/
> applications/notepad/notepad.h?rev=51135&r1=51134&r2=51135&view=diff
>
> Modified: trunk/reactos/include/ddk/ntstrsafe.h
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/include/ddk/
> ntstrsafe.h?rev=51135&r1=51134&r2=51135&view=diff
>
> Modified: trunk/reactos/include/psdk/strsafe.h
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/include/psdk/
> strsafe.h?rev=51135&r1=51134&r2=51135&view=diff
>
> Modified: trunk/reactos/ntoskrnl/ex/init.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ex/
> init.c?rev=51135&r1=51134&r2=51135&view=diff
>
>
Hi!,
my name is Pedro, and i'm a 5th grade student of computer science in Universitat Autonoma de Barcelona ( Spain ).
I'd like to apply in this gsoc, i've always wanted to be part of an open-source project, i think it can be a really profitable and exciting experience to share ideas and discuss them with other motivated coders.
Now as i'm finishing my last year i've found myself attracted by low-level questions. I've been aware of ReactOS for some time now - couple of years ago I downloaded the code and submitted a patch for the build system - actually, very silly patch :).
About the projects proposed, some of them seem a bit heavy for me. At first the ACPI Hal cought my attention, since i'm doing my final year project en the energy-performance tradeoff in multi-cores, but it seems very daunting, i have no experience in kernel development nor drivers. Although is in Java where i'm really experienced, I'm confident with c and c++, and i'm very interested in COM, I've done some of it in DirectX and i really enjoyed that, so i thought the MMC Console seems more affordable.
Anyway, i'd like to get some advice, if that's possible, about where i could direct myself, which project my profile may fit better or which has greater priority, and what can i do to start getting in contact to the project and make a better apply proposal.
I hope this would be a beginning of a great and profitable experience for me and the community :)
This seems a little premature.
I assume Neeraj is aware that there's no guarantee that the audio mixer will be one of the selected GSoC projects?
I'm by no means suggesting that we would do this, but good business sense says that if someone is willing to work on a component outside of GSoC, isn't it counter-productive for the project to use one of their slots up?
Anyway, we'll see what we have on the April 8 deadline.
I wish Neeraj luck in both his application and his forthcoming work in reactos.
Ged.
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of cfinck(a)svn.reactos.org
Sent: 22 March 2011 12:46
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [cfinck] 51118: Create a branch for Neeraj Yadav's work on the Audio Mixer
Author: cfinck
Date: Tue Mar 22 12:45:40 2011
New Revision: 51118
URL: http://svn.reactos.org/svn/reactos?rev=51118&view=rev
Log:
Create a branch for Neeraj Yadav's work on the Audio Mixer
Added:
branches/nyadav-audio-branch/
- copied from r51117, trunk/
Hello,
My name is Neeraj Yadav. I am an undergraduate student of Indian Institute
of Technology, Delhi studying Textile Engineering.Besides my regular studies
I have interest in Multimedia, Networking, Network-Programming and
Security.I have a decent knowledge of C and C++ programming.I am familiar
with git and svn.I am familiar with Linux, windows and Symbian APIs.I have
experience of UI design with Qt.
ReactOS is coming as my new interest and luckily this year ReactOS has been
selected as a mentoring organisation.I find myself appropriate for SSH
server implementation and Audio Mixer Project.
Windows doesn't do any access checks in ProbeForRead, it only checks the
range and alignment. The MmUserProbeAddress access is used to raise an
exception with the appropriate parameters. So the old version was
correct (except for the misleading comment maybe)
Am 21.03.2011 15:43, schrieb rharabien(a)svn.reactos.org:
> Author: rharabien
> Date: Mon Mar 21 14:43:56 2011
> New Revision: 51108
>
> URL: http://svn.reactos.org/svn/reactos?rev=51108&view=rev
> Log:
> Fix ProbeForRead. It wasn't ever checking if memory can be accessed. Thanks to big-endian it wasn't breaking MmUserProbeAddress as well. Code is now nearly the same as in ProbeForWrite. It shouldn't break anything. If it does, it's not bug in this code. :)
>
> Modified:
> trunk/reactos/ntoskrnl/ex/exintrin.c
>
> Modified: trunk/reactos/ntoskrnl/ex/exintrin.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ex/exintrin.c?rev…
> ==============================================================================
> --- trunk/reactos/ntoskrnl/ex/exintrin.c [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/ex/exintrin.c [iso-8859-1] Mon Mar 21 14:43:56 2011
> @@ -103,6 +103,8 @@
> IN SIZE_T Length,
> IN ULONG Alignment)
> {
> + ULONG_PTR Last, Current = (ULONG_PTR)Address;
> + CHAR Temp;
> PAGED_CODE();
>
> /* Only probe if we have a valid length */
> @@ -115,18 +117,31 @@
> (Alignment == 8) ||
> (Alignment == 16));
>
> - /* Check for correct alignment */
> - if (((ULONG_PTR)Address& (Alignment - 1)) != 0)
> + /* Check the alignment */
> + if ((Current& (Alignment - 1)) != 0)
> {
> /* Incorrect alignment */
> ExRaiseDatatypeMisalignment();
> }
> - else if (((ULONG_PTR)Address + Length)< (ULONG_PTR)Address ||
> - ((ULONG_PTR)Address + Length)> (ULONG_PTR)MmUserProbeAddress)
> +
> + /* Get the end address */
> + Last = Current + Length - 1;
> + if ((Last< Current) || (Last>= (ULONG_PTR)MmUserProbeAddress))
> + {
> + /* Raise an access violation */
> + ExRaiseAccessViolation();
> + }
> +
> + /* Round down to the last page */
> + Last = PAGE_ROUND_DOWN(Last) + PAGE_SIZE;
> + do
> {
> /* Attempt a read */
> - *(volatile CHAR* const)MmUserProbeAddress = 0;
> - }
> + Temp = *(volatile CHAR*)Current;
> +
> + /* Go to the next address */
> + Current = PAGE_ROUND_DOWN(Current) + PAGE_SIZE;
> + } while (Current != Last);
> }
> }
>
>
>
>
Hi,
both doxygen.reactos.org & iso.reactos.org are down (which results in daily builds isos not being uploaded).
Anyone able to fix them?
Regards,
P. Schweitzer
Hi,
currently working on HAL and HAL targets (ACPI, MP, UP and so on), I discovered a quite bad issue in our build process.
Just look at the function HalInitSystem@8 (halinit.c), depending on the build target we don't add the same code (look at CONFIG_SMP, which is only defined for HAL MP). But, currently, as we are building using HAL library for reducing code redudancy, this halinit.c file is only built ONCE. So, build targets aren't taken into account (MP, ACPI).
So, two choices, or we break that model, and forget about lib, and just keep base .rbuild (hal.rbuild, halacpi.rbuild, and so forth) with all files defined in those.
Or with find something smarter better such as rebuilding the lib with the new flags for each build?
Or finding a way to include .rbuild files in other rbuild files?
I'm not really sure about the way to proceed, that's why I "release" that question to the whole ML. Furthermore, could CMAKE be any use here? To facilitate the process?
Regards,
P. Schweitzer
Hello RoS developers,
I introduce myself. I'm Guillaume Touron, I'm a French engineering student
at National School of Computer Science and Applied Mathematics with
specialization in information systems and security. Apart from my studies I
am interested in OS development, Windows internals and application security
(vulnerabilities, reverse engineering, rootkits...). I read a lot about how
Windows internals work (kernel data structures...) and Windows security. I
have also some experience in NT driver development and kernel debugger
(WinDBG).
For many months now, I study RoS source code, and especially ntoskrnl
source. This includes object manager, i/o manager, security layer,
traps/exceptions management... I checkouted source code and installed RoS
build environment and I'm ready to begin development. I also took a look at
Se* kernel exported APIs, and tried to understand how security checks were
performed. That's why I'm interested in RoS GSoC Idea 'Security Controls'.
Indeed, implementing this feature would be a good start to add multiuser
experience in RoS which is currently missing, and to manage efficiently
users and groups. I think I know what is needed to complete this project
successfully and I'm ready to write a detailed presentation/proposal to
explain what I understand and what would be my goals. I also did GSoC 2010
last year for Honeynet Project on network security area, but I'm more
interested in kernel development.
Finally, few questions : What should I do to propose in a formal way my
proposal to RoS community ? Is it an obligation to have already send some
patches or can we begin development as a new contributor ? Who can I
contact to speak about technical details ?
Thank you very much.
I have been doing some investigation on theming. I have been looking
into comctl32.
One of the issues is that windows version 5 of the control has not
theming and uses SxS so that applications that use version 6 will get
themed controls.
Currently comctl only has one version and applies theming regardless
of the version the application requests.
I have spoken on the Wine mailing list and the only person that
replied did not want to use SxS. I assume to make it easier to
maintain(though i don't understand why common parts cant share the
same files and build 2 dlls). I was wondering what React OS developers
think is the best choice.
The second issue is that if comctl32 version 6 is loaded in windows it
takes control of components that are usually in user32. Someone said
this was called ( window class redirection). I can't really find any
information on it. Though isn't this just registering the class except
from comctl32? or does this cause a race condition(with the last one
one loaded taking control)? is this is how "window class redirection"
is different?
Also the last thing is. Should sub classing be used? You should be
able to load another window proc method even from user32 and call it
when it is suitable from new control. I would imagine this could cause
issues when the default procedure can't handle something as the new
control would.
Any advise would be much appreciated.
Dear colleagues
I am very pleased to inform you that a new builder has been just made
operational. Named Patch_x86_GCCWin Debug, you can see it waterfall right
now. Based on x86 RBuild trunk, its capable of downloading a patch from
bugzilla, applying it to trunk, building reactos testcd and running
winetests on it via VBox sysreg.
To use it, just pass revision, as well as Parameter 1, name id, value:
attachement id.
For example, http://www.reactos.org/bugzilla/attachment.cgi?id=5989
name: id, value: 5989
Just the same way you use source for vbox retesting. Right now test ISOs are
stored, named with x86_Patch, revision and patch id. Logs itself will be
also stored (when i bugfix them)
If any issues arise, please mail me or catch me on irc.
Hi all,
let me forward this email that i have received
i dunno if this is useful for you, as its a *hardware *meeting, but
anyway.... have a look and let me know!
P.S.: email is in english language at the bottom
---------- Forwarded message ----------
From: Syvic <syvic(a)sindormir.net>
Date: 2011/3/18
Subject: [hm] Open Source Hardware Convention 2011 en Madrid
To: Hackmeeting <hackmeeting(a)listas.sindominio.net>
Buenas,
(Perdón si os llega por duplicado)
Hoy, tras unos cuantos meses de curro, lanzamos al mundo las OSHWCon 2011:
(Catalán e inglés más abajo)
La OSHWCon <http://oshwcon.org/es> es un encuentro anual de 3 días que
organiza el colectivo Synusia <http://synusia.es/> en un esfuerzo de
difundir el uso delHardware Libre<http://es.wikipedia.org/wiki/Hardware_libre>
y de promocionar la electrónica y la filosofía del «Hazlo tú
mismo<http://es.wikipedia.org/wiki/Diy>».
Tendrá lugar en el Centro de Formación Padre Piquer<http://www.padrepiquer.com/>
de Madrid los *días 23, 24 y 25 de Septiembre de 2011*.
Durante la OSHWCon se ofrecerán *charlas*, *talleres*, *mesas redondas*,
exposición de *proyectos personales* y sobre todo, un *lugar de encuentro
para profesionales y aficionados al mundo de la electrónica*. La *asistencia
* es *libre y gratuita* y está pensada para que nadie se quede fuera. Se
programarán desde actividades de iniciación, hasta charlas y talleres de
alto nivel técnico.
Estamos trabajando para que durante la OSHWCon todo el mundo disfrute
aprendiendo, intercambiando conocimientos, concursando e incluso jugando con
la electrónica o la robótica, siempre desde la filosofía del *Open Source
Hardware*. Contamos con *cuatro espacios* para celebrar varias *actividades
simultáneas*, de forma que siempre habrá algo que hacer.
Si tienes algo que aportar, quieres compartir tu última creación
electrónica, eres experto en cierta materia electrónica y deseas explicarlo
al mundo, háznoslo saber en el apartado «Propón tu
charla<http://jhl.synusia.es/propuesta_charla>».
Mira antes el «Call4Papers <http://jhl.synusia.es/call4papers>» para obtener
más información acerca de las actividades en las que estamos interesados. Si
quieres saber más acerca de qué nos motiva a realizar este encuentro,
consulta la página «Manifiesto <http://jhl.synusia.es/manifiesto>».
Estáis todos invitados a participar, ya sea como visitantes o como ponentes
durante la Con. *¡Te esperamos el fin de semana del 23 al 25 de Septiembre!*
Recuerda inscribirte <http://jhl.synusia.es/inscripcion> en la web si
tienes pensado asistir. Además, una vez finalizada la OSHWCon, pondremos a
disposición de todo el mundo las grabaciones de todas las actividades.
Sobre Synusia
Synusia <http://synusia.es/> es el grupo de trabajo de electrónica
establecido en el C.F. Padre Piquer <http://www.padrepiquer.com/> que
organiza esta Con. Synusia nació de la necesidad de crear un punto de
encuentro donde compartir libremente y profundizar en el conocimiento de
diferentes tecnologías electrónicas y el OSHW. Si estás interesado en
participar en la OSHWCon o en saber más acerca de Synusia, no dudes en
mandarnos un correo (Encontrarás más información en nuestra página
web<http://synusia.es/>).
Cualquier sugerencia será bienvenida.
CATALÀ
La Convenció de Hardware Lliure, Electrònica i Robòtica<http://oshwcon.org/ca>
és una trobada anual de 3 dies que organitza el col.lectiu Synusia en un
esforç per difondre l'ús del Maquinari Lliure i de promocionar l'electrònica
i la filosofia de “Fes-ho tu
mateix<http://ca.wikipedia.org/wiki/Do_It_Yourself>”
Tindrà lloc en el Centre de Formació Padre Piquer<http://www.padrepiquer.com/>
de Madrid els dies *23, 24 i 25 de setembre del 2011*.
Durant el OSHWCon s'oferiran *xerrades*, *tallers*, *taules rodones*,
exposició de *projectes personals* i, sobretot, un lloc de trobada pels
professionals i aficionats al món de l'electrònica. *L'assistència és lliure
i gratuïta* i està pensada perquè ningú es quedi fora. Es programaran des
d'activitats d'iniciació fins a xerrades i tallers d' un alt nivell tècnic.
Estem treballat per a que durant la convenció tothom disfruti aprenent,
concursant i, fins i tot, jugant amb l'electrònica o la robòtica, sempre des
de la filosofia de l' Open Source Hardware. Comptem amb *quatre espais* per
celebrar diverses*activitats simultànies*, de manera que sempre hi haurà
alguna cosa a fer.
Si tens alguna cosa per aportar, vols compartir la teva darrera creació
electrònica, ets expert en certa matèria electrònica i vols explicar-ho a
tothom, fes-nos-ho saber en l'apartat “Proposa la teva
xerrada<http://oshwcon.org/ca/proposa>”.
Mira abans el “Call4Papers <http://oshwcon.org/ca/call4papers>” per obtenir
més informació sobre les activitats que realitzem. Si vols saber més sobre
què ens motiva a realitzar aquesta trobada, consulta la pàgina
“Manifest<http://oshwcon.org/ca/manifest>
”.
Esteu tots convidats a participar, ja sigui com a visitants o com a membres
actius de el OSHWCon. *T'esperem el cap de setmana del 23 al 25 de setembre!
* Recorda inscriure't a la web si tens pensat assistir-hi. A més, una vegada
finalitzat la convenció, posarem a la disposició de tothom els
enregistraments de les activitats.
Sobre Synusia
Synusia <http://synusia.es/> és el grup de treball d'electrònica establert
en el C.F. Padre Piquer <http://www.padrepiquer.com/> que organitza aquesta
convenció. Synusia va nèixer de la necessitat de crear un punt de trobada on
es pogués compartir lliurement y profunditzar en el coneixement de diverses
tecnologies electròniques i el OSHW. Si estàs interessat en participar en
el OSHWCon o en saber més sobre Synusia, no dubtis en enviar-nos un correu
(Trobaràs més informació a la nostra pàgina web <http://synusia.es/>).
Qualsevol suggerència serà benvinguda.
ENGLISH
Open Source Hardware, Electronics and Robotics Convention<http://oshwcon.org/en>
is a 3-days event organized by the Synusia group in an effort to spread the
Open Source Software <http://en.wikipedia.org/wiki/Open-source_hardware> and
to promote Electronics and the philosophy of "do it
yourself<http://en.wikipedia.org/wiki/DIY>".
The event will take place in Madrid, in C. F. Padre
Piquer<http://www.padrepiquer.com/>,
from *23 to 25 September 2011*.
During the OSHWCon, visitors will be able to watch and participate in *talks,
workshops, round table discussions*,*personal projects exhibitions* and,
above all, we'll offer a meeting place for professionals and amateurs of the
world of electronics. *Attendance is free and open to everyone*. Activities
are intended to be for everybody: from beginners to hi-level talks and
workshops.
Our objective is for everybody to enjoy learning, sharing knowledge, taking
part or even playing with electronics and robotics throughout the OSHWCon...
All of it from the Open Source Hardware philosophy. There are *four
different rooms/halls* to hold several *simultaneous activities*, so there
will always be something interesting to do.
If you have something to contribute with, you want to share your latest
electronic creation or you are an expert on some electronic matters and you
want to explain it to the world, let us know in "Suggest your
talk<http://oshwcon.org/en/suggestyourtalk>".
Check out first "Call4Papers <http://oshwcon.org/en/call4papers>" for more
information about the activities we are into. In case you wonder what make
us organize this event, take a look at our
"Manifesto<http://oshwcon.org/en/manifesto>
".
You are all welcome to participate, either as a visitor or as an active
member of the OSHWCon. *We'll be waiting for you on September 23 to
25!* Please,
remember to register first on our site if you are intended to come. We'll
also offer the recordings of every activity once the OSHWCon come to close.
About Synusia
Synusia <http://synusia.es/> is the working group established in C. F. Padre
Piquer <http://www.padrepiquer.com/> that organizes this Convention.
Synusia<http://synusia.es/>
was born from the need of setting up a meeting point where sharing and
deepen into the knowledge of different electronic technologies. If you are
willing to participate in the OSHWCon or you want to know more about
Synusia, feel free to send us an email (you'll find out more in our
web site<http://synusia.es/>).
Any suggestions will be welcome!
_______________________________________________
HackMeeting mailing list
HackMeeting(a)listas.sindominio.net
https://listas.sindominio.net/mailman/listinfo/hackmeeting
I have been investigating a lot of aspects about theming, and my make
that my proposal.
Though I have been thinking that will not be of much valuable in the
short term or in learning ongoing skills that will be needed in
reactos. Of course on of the stated goals of gsoc or to give
programmers the skills to contribute in the long term.
So I was wondering what were your ideas on what would be considered
valuable short term and what would give the skills to to help reactos
in the long term.
I know it is still 18 hours until google summer of code organizations
are announced, but I'm sure reactos will be accepted.
Any thoughts or suggestions would be much appreciated.
Hiya
I would like to point out to actions in my opinion necessary to be done
after the release:
1. Syncing:
Starting a new development/release cycle is the best moment for winesync to
be performed. Syncing early will give us much time to find and wipe all
Wine-originated bugs, which are simply unavoidable. The Winesync itself
should be spreaded to as many revisions as its possible/feasible, as it will
help out testers to regress-test any issues more precisely.
Before Winesync can be performed, CMake branch should be synchronized with
current trunk and the revision synchronized - locked up as reference frame
for any Trunk-CMake comparison tests.
We would not want CMake effort to be delayed due to any issues with WINE
code in trunk.
2. Patches
Now guys, i know i`m repeating myself, but please be warned that i will not
drop this issue. The way our project is handling patches from outside is
absolutely counterproductive. This is the only way new devs can be recruited
and get commit access, but delays in reviewing and even reacting to patches
is disgraceful. We are driving away potential newcomers, something no one
should wonder about, if it often takes months for someone to write down a
simple question about the patch content... We are risking a potential
project dawnfall if we continue doing this way. I know you are busy with
real life, project and other stuff, but seriously, this approach will only
make things even more difficult. I did all things i could think of to help
you out. Patches are now clearly tagged, listed in accessible way (
http://www.reactos.org/wiki/Bug_Filters ), i even tried to filter them,
moving old and questionable stuff into separate directory (WIP aka Work in
progress). Right now i took the more direct step of assigning patches to
devs personally. It might be questionable, please react in such cases and
comment, i will gladly relocate, but please do react. Due to Daniel recent
issues and lack of free time, i volunteered for commit translation patches,
at least those that can be done easily. Next thing planned here, is a
builder dedicated to patch testing, but this is just a rough plan for futher
discussion. I would be grateful for ANY feedback from you, perhaps some
things could be done better/differently.
Thanks in advance for your comments
Hi all!
Since everyone works so fast to ride my ass for breaking things, I
hope one of you have a fix for this one and also hope this did not
make it into branch! The commit breaks things, I wanted Michael to
review the patch before hand. I'm sure any of the IRC archives can
find my comments.
Going on Holiday,
James
I made a mistake, this patch was written by Rafal Harabien.
WBR,
Aleksey Bragin.
On Mar 11, 2011, at 1:07 AM, fireball(a)svn.reactos.org wrote:
> Author: fireball
> Date: Thu Mar 10 22:07:56 2011
> New Revision: 51013
>
> URL: http://svn.reactos.org/svn/reactos?rev=51013&view=rev
> Log:
> [NOTEPAD]
> - Edijs: Zero initialize the caption string.
> See issue #5992 for more details.
>
> Modified:
> trunk/reactos/base/applications/notepad/dialog.c
Hi,
this commits just shows you didn't understand how that function works. If you had, you wouldn't have said:
"- Implement parameters checking in FsRtlIsNameInExpressionPrivate."
It's already done.
"- Add two shortcuts for common wildcard invocations to make the function faster."
If you look at the algorithm, it will take at maximum as much loop iterations as name length.
"- Second (main part of the function) is still under review."
Thanks for discussing the issue with the original author of the algorithm, especially since you don't understand it. Furthermore, if you're not happy with said algorithm, you were asked to review it more than a year ago, and for at least 6 months. Thing that you NEVER did.
So, now you discovered what my mail address is, contact me before committing anything wrong/useless to current code.
And as you said less than a week ago, focus on fixing things that don't work, instead of rewriting working code.
And as someone else also said once: 1:1 isn't the solution everywhere. Or if you think so, start dropping arwinss.
Of course, don't take that personal, I like everyone ;-).
Regards,
P. Schweitzer
On Mar 7, 2011, at 4:33 PM, jgardou(a)svn.reactos.org wrote:
> Author: jgardou
> /* Check if the CPU is too old to support SYSENTER */
> - if ((Prcb->CpuType < 6) ||
> - ((Prcb->CpuType == 6) && (Prcb->CpuStep < 0x0303)))
> + if ((Reg[0] & 0x0FFF3FFF) < 0x00000633)
> {
It was intentionally done over CpuType and CpuStep. Now you
criptified it back to a raw Reg[0] value and weird hardcoded
constant. Could you please 1) elaborate this change and 2) if you
still think it's correct, and if you still tihnk(!) Windows does it
same way, then rework it to use Prcb->Cpu* instead of these magic
values?
Not to say adding a hack for VirtualBox is far from being a
beautiful, and would need to be *at least* marked so that it's not
forgotten.
Thanks,
Aleksey Bragin.
[GDI32]
- Remove the old SetDIBBits, it severed us well.... Hold on to the win32k call.
- Tested, Area.exe, wine gdi32 bitmaps test, AbiWord 2.8.6, OOo 2.4.3,
SM 2.0.11 and ReactOS applications.
- Aimp 2.61.583 (FULL, painted okay), CoolPlayer 219, winamp 0.98d and
winamp 2.95 (not FUll). The rest have drawing issue with DIB. See bug
5886.
The sound applications have the same issue with revision 50933+
(region unassociated with the DC owner), except CoolPlayer and winamp
0.98d. There is also an issue with vbrun60spX too. I'm not sure how to
move on and start compressed bitmaps.
Thanks,
James
Hmm...
I remember I added it to enable the possibility for backtraces in 1st
stage for sysreg. Why does it now cause the opposite? And why is there
an inconsistency? In 2nd stage there is an option for debug mode, in 1st
stage there is none, so using kdserial (which imo is appropriate way to
do it, I always select it) as default is as consistent as using "normal"
debug, getting the input from the keyboard driver.
Just my 0,002 ct/kb
Timo
Am 04.03.2011 17:57, schrieb fireball(a)svn.reactos.org:
> Author: fireball
> Date: Fri Mar 4 16:57:56 2011
> New Revision: 50967
>
> URL: http://svn.reactos.org/svn/reactos?rev=50967&view=rev
> Log:
> - Revert 47615. Please fix actual sysreg instead of adding inconsistency between 1st, 2nd and 3rd stages debugging connections. This should fix sysreg3's inability to do backtraces.
> See issue #5811 for more details.
>
> Modified:
> trunk/reactos/boot/bootdata/txtsetup.sif
>
> Modified: trunk/reactos/boot/bootdata/txtsetup.sif
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/bootdata/txtsetup.sif…
> ==============================================================================
> --- trunk/reactos/boot/bootdata/txtsetup.sif [iso-8859-1] (original)
> +++ trunk/reactos/boot/bootdata/txtsetup.sif [iso-8859-1] Fri Mar 4 16:57:56 2011
> @@ -59,7 +59,7 @@
> [SetupData]
> DefaultPath = \ReactOS
> OsLoadOptions = "/NOGUIBOOT /NODEBUG"
> -DbgOsLoadOptions = "/NOGUIBOOT /DEBUGPORT=COM1 /FIRSTCHANCE /KDSERIAL"
> +DbgOsLoadOptions = "/NOGUIBOOT /DEBUGPORT=COM1 /FIRSTCHANCE"
> ;OsLoadOptions = "/NOGUIBOOT /DEBUGPORT=SCREEN"
> ;OsLoadOptions = "/NOGUIBOOT /DEBUGPORT=BOCHS"
>
>
>
>
Hi all,
im testing ROS right now in real hardware... As i cannot log into IRC (via
webchat.freenode.net, i cant even reach the page, i dont know why), let me
post this in ML
The think is, i have installed RealTek´s official driver for the NIC, and
hardware is recognized... but, dhcp dont get any IP...
any idea?
log is attached
btw, in the log there are many errors ("xxxx failed") about ndis.......
tkreuzer(a)svn.reactos.org wrote:
> Do raster operation on 4 bytes instead of only 3.
Quoting jgardou's commit before:
> - When applying raster operation, do so only on 24 bits, we don't
> support alpha channel in win32k
I have no idea about DIB code, but just from the commit message I
presume that this change to 24 bits has happened deliberately.
- Colin
Hi all,
I finished implementing main features of a special mechanism for
monitoring uesrmode heap allocations in ReactOS. This mechanism is
called Debug Page Heap, after the very similar mechanism present in
recent versions of Microsoft Windows NT.
Explaining the heap manager, the "usual" heap allocator (the one I
also developed earlier) also contains a heap corruption detector, but
it works post-factum, only after the respective block is freed its
patterns are checked (if such heap flags are specified) and if they
are damaged the block is reported. This makes debugging problematic,
because a lot of code is executed between the moment the corruption
occured and moment when the corrupted block is freed. Also it may be
so that block's patterns are untouched, but internal heap structures
are damaged. The usual heap allocator won't be able to catch this,
but will crash with undetermined exception.
Debug page heap (DPH) comes to solve this problem. Simply speaking it
guards every block with a no-access page either after or before the
block, so that when a badly written app wants to write beyond the
allowed area, an exception occurs showing exactly the faulty
instruction.
Not so simply speaking, it's a rather complicated debugging tool with
abilities to catch access-after-free cases also when they happen, and
do some other nice tricks too. If you want to read more about it,
look for "debug page heap" in MSDN and also visit URLs specified as
references in rtl/heappage.c.
How to use it? The best way is to use Microsoft's utility gflags.exe
which is part of the Debugging package of WDK. To make long things
short, just copy gflags.exe to C:\ReactOS\system32, boot your ReactOS
installation, fire up cmd prompt and type:
gflags /p /enable name.exe /full
Now, when you run your app called name.exe, it will use the DPH heap
allocator.
Detailed information about gflags.exe could be found here: http://
msdn.microsoft.com/en-us/library/ff549557%28VS.85%29.aspx
Also, I suggest looking in MSDN for page heap explanation (I provided
some references in heappage.c too).
Have fun!
Aleksey.
ReactOS Urgent Meeting
Preamble
=========
The following people which are generally considered as ReactOS-related
people have called for an urgent project meeting. They agree with the
meeting agenda and the rules for this meeting:
* Giannis Adamopoulos
* Johannes Anderwald
* Maciej Białas
* Aleksey Bragin
* Colin Finck
* Ziliang Guo
* Kamil Hornicek
* Amine Khaldi
* Timo Kreuzer
* Victor Martinez
* Roel Messiant
* Sylvain Petreolle
* Pierre Schweitzer
* Olaf Siejka
* James Tabor
* Art Yerkes
As we have not established any general rules for meetings yet, we
consider these demands enough to justify the need for such an urgent
meeting.
Based on the experiences Colin has from formal ReactOS Deutschland e.V.
foundation meetings, we need at least a discussion leader and a minute
taker to get an organized meeting done over IRC.
General Information
====================
* Date and Time: Tuesday, 22nd February, 2011 - 20:00 UTC
* Place: #reactos-meeting on Freenode
* Meeting leader: Colin Finck
* Minute taker: Amine Khaldi
* Allowed Participants
The following people are allowed to participate in the discussion
on that channel. This list is taken from the people which were
recently active on the #reactos-dev IRC channel. Others are not
included as they don’t have a chance to know about the recent
developments. If you consider yourself a ReactOS-related person,
you may still ask Colin Finck to put you on this list. Apart from
this, everybody may join as an observer.
o Giannis Adamopoulos (smiley1_)
o Johannes Anderwald (janderwald)
o Maciej Białas (niski)
o Aleksey Bragin (abragin)
o Colin Finck (Colin_Finck)
o Danny Götte (dangerground)
o Ziliang Guo (ZWabbit)
o Amine Khaldi (AmineKhaldi)
o Timo Kreuzer (rosdude)
o Matthias Kupfer (Collibri)
o Victor Martinez (vicmarcal)
o Roel Messiant (Mephisto)
o Ged Murphy (GedMurphy)
o Sylvain Petreolle (Usurp)
o Daniel Reimer (dreimer)
o Pierre Schweitzer (HeisSpiter)
o Samuel Serapion (encoded)
o Olaf Siejka (Caemyr)
o James Tabor (jimtabor)
o Art Yerkes (arty)
Meeting Agenda
===============
1. Agree on a preliminary definition for the term "ReactOS Team
Member".
To create a basis for the next regular meeting, we need to know
who may participate and who may not. As we need to focus on the
release right now, this definition should only be preliminary and
is subject to change in a future meeting.
Some participants will present proposals for such a definition.
2. Establish regular meetings every month.
This is the only chance to ensure discussions among a broad range
of ReactOS Team members with binding decisions. These meetings
should follow the rules of typical meetings, including meeting
leaders and minute takers. In contrast to this meeting, all team
members should be able to participate. Minutes should also be
published on the website.
Such regular meetings should begin after CLT2011 (after 20th
March) due to the time it takes to prepare this event.
3. Set up binding 0.3.13 Release Plans.
The CLT2011 event is a big PR chance for a new ReactOS release,
so we should look forward to get a release ready by then. This
point includes:
1. Getting information about the most annoying bugs and
regressions.
Victor Martinez and Olaf Siejka will report on this.
2. Building teams to care about each bug.
As soon as a bug is fixed, a team has to report back about
this to one of the release engineers. They will then add
you to another team. Of course, you may also suggest stuff
you want to work on afterwards.
3. Setting deadlines for the bugs.
We need to determine what bugs can be realistically fixed
in the given time. If a bug is not fixed by then, the
appropriate team has to report back about this to one of
the release engineers. They are then responsible for
finding a solution.
We believe that other topics, especially the ones discussed in the
"ReactOS Reaction" document should be covered in the first regular
meeting, so that we can focus on 0.3.13 right now.
Hi,
this debug wasn't supposed to be silent as it highlights a quite crappy situation in ReactOS. And that's even what one would call: "a hack".
That way, you could also silence IopParseDevice hack debug...
At least, you could have asked the author, I'm not that unreachable ;-).
Regards,
P. Schweitzer
I noticed this everywhere,
(subsystems/win32/win32k/objects/gdiobj.c:249) GDIOBJ_LockObj:
Attempted to lock object 0x10064, wrong reuse counter (Handle: 0x0,
Entry: 0x8)
(subsystems/win32/win32k/objects/dclife.c:726) Could not lock source DC 00010064
(subsystems/win32/win32k/ntuser/simplecall.c:349) Calling invalid
routine number 0x10 in NtUserCallOneParam(), Param=0x31
CallOneParam? Looks like a stack issue.
Hi,
recently amount of new features added to the trunk decreased, and
there were quite a lot of bugfixes coming in. In my opinion, it is a
very good time for a release. After release is branched, it would be
possible to sync wine shared code and continue with other changes.
If there are no objections, let's start the work right away. Testers
being the first team working, and Colin - when/if you have time for
this release?
WBR,
Aleksey Bragin.
Hi all,
Even if it has already been reported through the newsletter, here is the
announcement for mailing list readers: The ReactOS Project will have a
booth at the Chemnitzer Linux-Tage 2011, the second-largest
Open-Source-related exhibition in Germany, from 19th to 20th March.
Our project is going to be represented by the ReactOS developers Colin
Finck, Timo Kreuzer, Matthias Kupfer, Daniel Reimer and Christoph von
Wittich. This year, we will also be joined by Kai Tietz from the
MinGW-w64 Project.
Like in the last years, you will be able to try out the latest
development state of ReactOS as well as getting some merchandising articles.
So if you have the time to visit Chemnitz, stop by and say hello at our
booth.
Cheers,
Colin
I am just a new person who wants to debug ROS, so my questions may be stupid.
I have checked http://www.reactos.org/wiki/Debugging . It seems the
main debugging way is "Debugging through text messages" (I think it is
more like "checking logs"). If I want to use GDB, I have to use QEMU.
Would you please tell me is Kdbg the only way to debug code in VMWare
or VirtualBox?
And if I want to debug ReactOS, do I have to install QEMU or VMWare or
VirtualBox? Using "make install" in RosBE can generate many binary
files. Is there any build-in way to start ROS from these bin files
without any virtual machine?
Thank you in advance.
Hello all,
As you have certainly noticed, Amine, Olaf and me have upgraded the
BuildBot some days ago. While doing this, we have added Olaf's build
slaves which used to be available at http://reactos.ath.cx:8081.
The new BuildBot version finally enables authenticated access for
features like forcing a build. When you want to do this now, you have to
enter your SVN credentials into the respective fields. If you are a
tester and need these BuildBot features, please ask Aleksey or me for
getting the appropriate credentials.
In the next few days, we're probably going to make the testing results
of his CMake bot available at http://reactos.org/testman and upload his
builds to http://iso.reactos.org.
I might also change the BuildBot Web page design. Now that the main part
has got wider, we might remove the ReactOS design around it to get some
space for the real important stuff.
- Colin
spetreolle(a)svn.reactos.org wrote:
> + subversion_wc_info(${CMAKE_CURRENT_SOURCE_DIR} SVNINFO)
This will fail when we're not inside a working copy (see
http://www.vtk.org/Bug/view.php?id=10200), because the macro outputs an
error in this case.
Please take a look into
http://svn.reactos.org/svn/project-tools/trunk/rosev_ircsystem/src/CMakeLis…
to see how you can easily reimplement this step properly.
Apart from that, nice to see that we finally get rid of this old stuff! :-)
- Colin
Hi everybody,
I've been thinking about getting a license of an English Windows Server
2003 Standard 32-Bit for the project.
It could be installed on one of our servers and be made available over
RDP. This would enable project members to do development and testing
work on our actual target platform. Considering that some developers
even use a non-Windows platform for development work, it might simplify
their work as well.
We may as well use the license for other purposes (Buildslave,
Testslave, whatever), but at least native building could be done by any
Windows version. And in this case, I might be able to donate an XP Pro
license myself (German though).
As I don't know about the needs of the other members, I'd like to hear
your opinion about my idea. It would also be nice to hear if anybody
knows a cheap (but legal!) way to get such a license or can even donate
one (e.g. unused OEM license shipped with a server, unused license after
getting Server 2008, etc.)
English Windows licenses are rare/expensive on German eBay, so this
would only be a last resort :-)
Cheers,
Colin
P.S.: If you have the opposite problem and actually need a Linux VM
available over SSH/RDP (e.g. for testing build system changes), just let
me know and I could set it up.
Shouldn't that work the same way (at least if there is any hbmColor)?
Cursors can have a different size as well, so maybe we should rather
query the hbmMask, if hbmColor is 0(=) I didn't bother reading the
context of the function though.
Am 16.01.2011 13:51, schrieb mkupfer(a)svn.reactos.org:
> Author: mkupfer
> Date: Sun Jan 16 12:51:14 2011
> New Revision: 50398
>
> URL: http://svn.reactos.org/svn/reactos?rev=50398&view=rev
> Log:
> - Fix draw of cursors in static controls
> - Last part of fix for bug #4874
>
> Modified:
> trunk/reactos/dll/win32/user32/controls/static.c
>
> Modified: trunk/reactos/dll/win32/user32/controls/static.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/user32/controls/…
> ==============================================================================
> --- trunk/reactos/dll/win32/user32/controls/static.c [iso-8859-1] (original)
> +++ trunk/reactos/dll/win32/user32/controls/static.c [iso-8859-1] Sun Jan 16 12:51:14 2011
> @@ -863,7 +863,15 @@
> else
> {
> BITMAP bm;
> - if (!GetObjectW(info.hbmColor, sizeof(BITMAP),&bm)) return;
> + if (info.fIcon)
> + {
> + GetObjectW(info.hbmColor, sizeof(BITMAP),&bm);
> + }
> + else
> + {
> + bm.bmWidth = GetSystemMetrics(SM_CXCURSOR);
> + bm.bmHeight = GetSystemMetrics(SM_CYCURSOR);
> + }
> if (style& SS_CENTERIMAGE)
> {
> iconRect.left = (rc.right - rc.left) / 2 - bm.bmWidth / 2;
>
>
>
Am 13.01.2011 10:58, schrieb gadamopoulos(a)svn.reactos.org:
> Author: gadamopoulos
> Date: Thu Jan 13 09:58:04 2011
> New Revision: 50381
>
> URL: http://svn.reactos.org/svn/reactos?rev=50381&view=rev
> Log:
> [rosautotest]
> -Implement closing any dialog that shows and stays visible for some time. This way rosautotest can now continue if a test application crashes or asserts.
>
Seems it causes a regression in testbot:
*http://www.reactos.org/testman/compare.php?ids=4355,4356
*
Hi,
I'm currently working on the coordinate transformation code in win32k.
While Windows does this in win32k, I wonder why its not done in user
mode and if we could depart from windows design here.
The advantages would be decreased complexity in the kernel and no use of
floating point emulation on x86 (better performance).
Are there any things that would make it unreasonable?
I don't plan to go and change this now, I just like to discuss whether
we might or might not do that at some point.
Timo
I didn't know about this feature.
Will this help the effort towards a minwin effort in fixing the
dependency hierarchy (mess)?
Ged.
On 31 December 2010 16:49, <tkreuzer(a)svn.reactos.org> wrote:
> Author: tkreuzer
> Date: Fri Dec 31 16:49:49 2010
> New Revision: 50243
>
> URL: http://svn.reactos.org/svn/reactos?rev=50243&view=rev
> Log:
> [CMAKE]
> Add generation of a depencency graph for shared libraries.
> The output is a graphml file. Can be enabled with GENERATE_DEPENDENCY_GRAPH
> switch.
>
>
I have asked several times in #reactos and in #reactos-dev channels, so now time to ask again here: What happens with the server?
We are commiting a lot ( more than 25 commits/days last days) and we dont know if:
1)One of those commits (hopefully not) has broken building..
2)One of those commits (hopefully not) has broken booting..
Both of these are pain in the a...if regtesting is needed.
So: Can anyone fix this situation asap?
Merry Thanks and Many Christmas ;)
tkreuzer(a)svn.reactos.org wrote:
> LD is stupid and doesn't handle stdcall decoration as proper as
> dlltool does (after we provided a patch) [...]
Wouldn't it have been easier to just provide a similar patch for LD
then? It was a matter of changing a strchr() call to strrchr()...
(http://sourceware.org/bugzilla/show_bug.cgi?id=9766)
We can always use a patched binutils version in the next RosBE if the
patch is not applied to the upstream source in time.
Cheers,
Colin
Hi,
> Author: cgutman
> Date: Tue Dec 21 04:35:12 2010
> New Revision: 50077
>
> URL: http://svn.reactos.org/svn/reactos?rev=50077&view=rev
> Log:
> [USBDRIVER]
> - Fix a bug that resulted in us only copying half of the old keyboard data
> - CID 10402
>
> Modified:
> trunk/reactos/drivers/usb/nt4compat/usbdriver/keyboard.c
>
> Modified: trunk/reactos/drivers/usb/nt4compat/usbdriver/keyboard.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/usb/nt4compat/usbd…
> ==============================================================================
> --- trunk/reactos/drivers/usb/nt4compat/usbdriver/keyboard.c [iso-8859-1] (original)
> +++ trunk/reactos/drivers/usb/nt4compat/usbdriver/keyboard.c [iso-8859-1] Tue Dec 21 04:35:12 2010
> @@ -277,7 +277,7 @@
> }
>
> // Save old keyboard data
> - RtlCopyMemory(pdev_ext->kbd_old, data, sizeof(data));
> + RtlCopyMemory(pdev_ext->kbd_old, data, 8);
>
> // resubmit the urb
> status = usb_submit_urb(pdev_ext->dev_mgr, purb);
This change is really dangerous and should be changed to a correct fix. Using magic values on memory copying is a bad idea. Using magic values (in general) is a bad idea.
Please provide a better fix without magic value.
Regards,
P. Schweitzer
I have a doubt:
==============================================================================
--- trunk/reactos/ntoskrnl/mm/ARM3/virtual.c [iso-8859-1] (original)
+++ trunk/reactos/ntoskrnl/mm/ARM3/virtual.c [iso-8859-1] Wed Dec 22 21:59:27 2010
@@ -2446,6 +2446,9 @@
/* Check if this VAD is too high */
if (BaseVpn < Vad->StartingVpn)
{
+ /* Stop if there is no left child */
+ if (!Vad->LeftChild) break;
+
/* Search on the left next */
Vad = Vad->LeftChild;
}
@@ -2453,6 +2456,11 @@
{
/* Then this VAD is too low, keep searching on the right */
ASSERT(BaseVpn > Vad->EndingVpn);
+
+ /* Stop if there is no right child */
+ if (!Vad->LeftChild) break;
+
+ /* Search on the right next */
Vad = Vad->RightChild;
}
}========================================================
Look these lines:
+ /* Stop if there is no left child */
+ if (!Vad->LeftChild) break;
+ /* Stop if there is no right child */
+ if (!Vad->LeftChild) break;
1) Is there a typo in the copy-pasta condition?
2) Is the comment wrong or misleading?
3) Am I a complete noob?
I think the order is 3), 1), 2)
One of the latest changes has made ReactOS totally uninstallable(12 tries /12 fails) using less than 192MB Ram.It halts in first stage during copying files.
Merry Christmas!!
Hi!
I guess once long tyme ago, there was a little file called dos.h!
Need this #define _A_VOLID 0x08 /* Volume ID file */
VolumeLabelDirEntry.Fat.Attrib = 0x08;
}
I'm not able to get the wubble simulation working for the ua-ros-pkg at:
http://code.google.com/p/ua-ros-pkg
[Note: I'm a new comer to ROS]
Summary of Issue:
I am using the Q&A Format provided by the site above.
a. What steps will reproduce the problem?
1. Follow http://code.google.com/p/ua-ros-pkg/wiki/DeveloperInstall to
install uav-ros-pkg packages
2. Run roslaunch wubble_mapping simulation.launch
b. What is the expected output? What do you see instead?
Expected output: Runs as given in
http://code.google.com/p/ua-ros-pkg/wiki/ClassInstructions.
Observed output:
--------------
while processing
/opt/ros/cturtle/stacks/ua-ros-pkg-read-only/arrg/wubble_world/wubble_environments/launch/empty_blocks_world.launch:
while processing
/opt/ros/cturtle/stacks/ua-ros-pkg-read-only/arrg/wubble_world/wubble_environments/launch/world_common.launch:
Invalid roslaunch XML syntax: [Errno 2] No such file or directory:
u'/opt/ros/cturtle/stacks/ua-ros-pkg-read-only/arrg/wubble_world/wubble_environments/launch/world_common.launch'
------------
c. What version of the product are you using? On what operating system?
Latest trunk, on Ubuntu 10.04 /Lucid.
d. Additional Notes?
world_common isn't there in the given files, and neither does it get
generated during the build. Also, while running make-all.sh I get 'Built 46
packages with 1 failure'. My gearbox
has the following issue during the build:
==========================
mkdir -p build/gearbox-svn/build
cd `rospack find gearbox` && patch -d
build/gearbox-svn/src/hokuyo_aist/python --verbose < `rospack find
gearbox`/aist_python_mt.patch
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- CMakeLists.txt 2010-11-05 17:13:52.719057243 -0700
|+++ CMakeLists.txt.ros 2010-11-05 17:12:30.921672551 -0700
--------------------------
Patching file CMakeLists.txt using Plan A...
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
Hunk #1 ignored at 41.
1 out of 1 hunk ignored -- saving rejects to file CMakeLists.txt.rej
done
===========================
I wonder whether this is causing the problem, and am not totally clear as to
how to correct this.
Thanks!
--
Ganesh
$ g++ file.c -fblocks -Wall /usr/lib/bundle1.o -arch x86_64 -o file.out
pschweitzer(a)svn.reactos.org wrote:
>
> ASSERT(Name->Length);
> ASSERT(Expression->Length);
> ASSERT(!FsRtlDoesDbcsContainWildCards(Name));
It'd be preferable to wrap that last ASSERT so it isn't compiled into release builds.
Adding functions into asserts adds overhead on release builds as they're called for no reason.
Ged.
Hello all,
I'm currently developing two project tools which are going to be used by
the German ReactOS foundation (custom IRC Server and plugin for Jameica
- http://www.willuhn.de/products/jameica/).
They shall be committed into a public ReactOS SVN repository.
Since I believe that these tools are hardly useful for the average
ReactOS developer, I don't want to commit them to our current
/trunk/tools directory in the "reactos" repository. Among other
disadvantages, every commit to them would trigger a useless BuildBot
build, source checkouts would include unnecessary stuff, etc.
As this is generally the case with most of the stuff in /trunk/tools,
I'd like to move everything below this directory and the /irc directory
into a new repository called "project-tools".
We have already done a similar step in the past for the former "web"
directory.
Additionally, the "press-media" directory would be a similar candidate
for an own "press-media" repository. After these steps, our "reactos"
repository would finally contain only OS development related stuff.
For comparison, Wine already keeps its main repository free from
unrelated stuff and has several similar repositories (see
http://source.winehq.org/git/).
If there are no objections to my idea within the next two weeks, I will
proceed and set up "project-tools" and "press-media" repositories
(preserving as much SVN history as possible).
Cheers,
Colin
A worthy commit for r50000.
You've been waiting for this revision, haven't you .... haha.
Ged
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of fireball(a)svn.reactos.org
Sent: 10 December 2010 09:33
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [fireball] 50000: [HEAP] - Time has come to get rid of a slightly modified implementation of WINE's heap, which is a hack based on Windows 95's heap implementation, itself a hack of DOS memory mana...
Author: fireball
Date: Fri Dec 10 09:33:20 2010
New Revision: 50000
URL: http://svn.reactos.org/svn/reactos?rev=50000&view=rev
Log:
[HEAP]
- Time has come to get rid of a slightly modified implementation of WINE's heap, which is a hack based on Windows 95's heap implementation, itself a hack of DOS memory management. It supported 3 out of the 18 possible NT Heap Flags, did not support custom allocation/deallocation routines, and was about 50-80x slower with fragmentation rates up to 500x higher when compared to NT's LFH (WINE is lucky because the advanced NT Heap features are used in kernel-mode usually, not in user-mode, and they are crossing their fingers for this being the same). Several high-end SQL/Database applications would significantly benefit from custom heap features provided by NT. Not to say about removing crappy support for a custom Commit routine and crappy support for User-defined flags and the User-defined value.
- So, the glorious moment for a new heap manager, which is (to remind you) a totally new heap manager, resembling real NT heap manager, based on data structures similar to Windows 2003 and Vista+'s heap structures, supporting advanced heap flags (e.g. useful for debugging), having substantially lower fragmentation rates (and thus speed and reliability), having native support for user-defined flags and user-defined values, also native support for a custom commit routine, which is very important for trunk's win32 subsystem. It also reserves, commits, decommits and frees memory on the fly, unlike existing heap manager which prefers to reserve and commit as much as possible, and doesn't decommit when it's no longer necessary. Not to say about support for per process heaps, with a proper lock, and a further support for a special so-called debug heap allocator (to be implemented in heapdbg.c) which will be useful for finding heap corruptions.
Yeah, I'm not a fun person :D
Added:
trunk/reactos/lib/rtl/heap.c
- copied unchanged from r49999, trunk/reactos/lib/rtl/heap_rewrite.c
Removed:
trunk/reactos/lib/rtl/heap_rewrite.c
[This mail would be too long, it was shortened to contain the URLs only.]
Removed: trunk/reactos/lib/rtl/heap_rewrite.c
URL: http://svn.reactos.org/svn/reactos/trunk/reactos/lib/rtl/heap_rewrite.c?rev…
greatlrd(a)svn.reactos.org wrote:
> Sent: 03 December 2010 09:20
> To: ros-diffs(a)reactos.org
> Subject: [ros-diffs] [greatlrd] 49912: all code are in
> ReactOS trunk for ReactX delete the old branch and prepare
> create new one Most of the code will be focus on dxg.sys and
> few part of gdi32.dll in the new branch of ...
Hells bells, it's gratelood!
Good to see you back mate.
Ged.
Hi,
anyone (ie Colin or Christoph?) knows what's wrong with testbot? Since r49761 it can't reach 2nd stage & more. This revision has been reverted in r49767 but testbot keeps being broken. Any clue?
Regards,
P. Schweitzer
>
> I am new to reactos and i want to study it in detail. For that I wish to
> construct it manually. So can u tell me the important files needed to boot
> the reactos.
Thanking you.
Hello,
Why everyone else had been complaining on how we should revert changes that expose compiler bugs, I, on the other hand, have not even been able to build ReactOS anymore starting with recent revisions (probably related to C++ changes).
Anyone want to fix this, please?
[PCH] obj-i386/base/shell/explorer/.gch_explorer/precomp.h.gch
In file included from /usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/localefwd.h:42,
from /usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/string:45,
from base/shell/explorer/utility/utility.h:58,
from base/shell/explorer/precomp.h:33:
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/mingw32/bits/c++locale.h: In function 'int std::__convert_from_v(int* const&, char*, int, const char*, ...)':
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/mingw32/bits/c++locale.h:74: error: expected primary-expression before ',' token
In file included from /usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/string:46,
from base/shell/explorer/utility/utility.h:58,
from base/shell/explorer/precomp.h:33:
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h: In function 'void std::__ostream_write(std::basic_ostream<_CharT, _Traits>&, const _CharT*, std::streamsize)':
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h:48: error: expected primary-expression before '.' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h:50: error: expected primary-expression before '.' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h: In function 'void std::__ostream_fill(std::basic_ostream<_CharT, _Traits>&, std::streamsize)':
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h:60: error: expected primary-expression before '.' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h:63: error: expected primary-expression before '.' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h:66: error: expected primary-expression before '.' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h: In function 'std::basic_ostream<_CharT, _Traits>& std::__ostream_insert(std::basic_ostream<_CharT, _Traits>&, const _CharT*, std::streamsize)':
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h:85: error: expected primary-expression before '.' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h:88: error: expected primary-expression before '.' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h:92: error: expected primary-expression before ',' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h:93: error: expected primary-expression before '.' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h:94: error: expected primary-expression before ',' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h:95: error: expected primary-expression before '.' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h:96: error: expected primary-expression before ',' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h:99: error: expected primary-expression before ',' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h:100: error: expected primary-expression before '.' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h:104: error: expected primary-expression before '.' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream_insert.h:108: error: expected primary-expression before '.' token
In file included from /usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/iostream:40,
from base/shell/explorer/utility/utility.h:59,
from base/shell/explorer/precomp.h:33:
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream: In function 'std::basic_ostream<_CharT, _Traits>& std::operator<<(std::basic_ostream<_CharT, _Traits>&, _CharT)':
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream:447: error: expected primary-expression before ',' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream: In function 'std::basic_ostream<_CharT, _Traits>& std::operator<<(std::basic_ostream<_CharT, _Traits>&, char)':
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream:452: error: expected primary-expression before '<<' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream:452: error: expected primary-expression before '.' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream: In function 'std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, char)':
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream:458: error: expected primary-expression before ',' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream: In function 'std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, signed char)':
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream:464: error: expected primary-expression before '<<' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream: In function 'std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, unsigned char)':
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream:469: error: expected primary-expression before '<<' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream: In function 'std::basic_ostream<_CharT, _Traits>& std::operator<<(std::basic_ostream<_CharT, _Traits>&, const _CharT*)':
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream:491: error: expected primary-expression before '.' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream:493: error: expected primary-expression before ',' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream: In function 'std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, const char*)':
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream:508: error: expected primary-expression before '.' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream:510: error: expected primary-expression before ',' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream: In function 'std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, const signed char*)':
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream:519: error: expected primary-expression before '<<' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream: In function 'std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, const unsigned char*)':
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream:524: error: expected primary-expression before '<<' token
In file included from /usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream:565,
from /usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/iostream:40,
from base/shell/explorer/utility/utility.h:59,
from base/shell/explorer/precomp.h:33:
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream.tcc: In function 'std::basic_ostream<_CharT, _Traits>& std::operator<<(std::basic_ostream<_CharT, _Traits>&, const char*)':
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream.tcc:324: error: expected primary-expression before '.' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream.tcc:342: error: expected primary-expression before '.' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream.tcc:343: error: expected primary-expression before ',' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream.tcc:347: error: expected primary-expression before '.' token
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/bits/ostream.tcc:351: error: expected primary-expression before '.' token
In file included from /usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/iostream:40,
from base/shell/explorer/utility/utility.h:59,
from base/shell/explorer/precomp.h:33:
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream: In function 'std::basic_ostream<char, _Traits>& std::operator<<(std::basic_ostream<char, _Traits>&, const char*) [with _Traits = std::char_traits<char>]':
base/shell/explorer/utility/xmlstorage.h:2923: instantiated from here
/usr/local/RosBE/i386/lib/gcc/mingw32/4.4.2/include/c++/ostream:512: error: return-statement with no value, in function returning 'std::basic_ostream<char, std::char_traits<char> >&'
make: *** [obj-i386/base/shell/explorer/.gch_explorer/precomp.h.gch] Error 1
-r
Hi,
most of the justifications for r49691 have been included in the commit message. But here are needed addings.
Olaf made buildbot rebuild r49662 and retest it. Testbot manages to pass 3rd stage and to run tests. Then, Olaf retried with r49665, and it failed the same way it was failing earlier.
So, we are reverting to "last good known state", aka r49662. Only two issues have been seen there:
- one with MM: (ARM³::PAGFAULT:751) PAGE TABLES FAULTED IN!
You can find full log here: http://download.myreactos.com/Amine/49662%20testbot%20ouptput-stdio.7z (thanks to Sylvain)
- One with NPFS. Aleksey and Eric are already working on it. You can easily find it on testbot output.
Other issues may also be found as many commits were done while testbot was down.
Please don't start a drama on that revision. Whatever you may think about it, we cannot stay with a broken testbot forever and people keeping on committing. Taking a decision trying to sort out a mess is being professional.
All the help everyone will be able to give will be appreciated!
Thanks.
P. Schweitzer
PS: For ReactOS testbot raw results, don't forget: http://build.reactos.org:8010/
You'll find the tests ran today.
Hi,
finally this commit won't be reverted (unless someone explicitly asks for it) as it brings testman back and shows quite important bugs.
Feel free to find a nice bugfix instead.
WBR,
P. Schweitzer
Hiya
It looks like buildbot has crashed or been shut down. I restarted the master
but have no access to slaves. It will at least gather the build requests,
but the missing ones since last 6 hours need to be forced manually.
Christoph, could you take a look at the slaves??
Regards
Great work, one more driver incompatibility away!
WBR,
Aleksey Bragin.
On Nov 20, 2010, at 1:42 AM, ekohl(a)svn.reactos.org wrote:
> Author: ekohl
> Date: Fri Nov 19 22:42:53 2010
> New Revision: 49646
>
> URL: http://svn.reactos.org/svn/reactos?rev=49646&view=rev
> Log:
> [NPFS]
> - Rename DEVICE_EXTENSION to NPFS_VCB.
> - Add a type variable to distinguish FCBs and CCBs for device,
> directory or pipe.
> - Attach an FCB to the VCB that represents the root directory of
> the file system and implement an open routine for the root directory.
> - Make NpfsWaitPipe work when it is called for the root directory.
>
> [KERNEL32]
> - Remove the old version of WaitNamedPipeW.
>
> This patch fixes the broken wait pipe code. It was written and
> tested on r49458 because later revisions do not work for me.
Dear All,
Can you please kindly let me know which Virtualization tool I can use to run
ReactOS.
I am using Ubuntu currently and want to run ReactOS in top of that using a
VM.
Thanks a lot in advance!
Warm regards
Arko Provo Mukherjee
Just for the record:
The changes are between r7324487 and r7281232.
gdi32:palette +2 failures
shell32:shlexec: crash
user32:combo: +4 failures
user32:cursoricon: -8 tests / +8 failures
user32:edit: crash
user32:monitor: not run
user32:msg not run
user32:win: -5743 tests
winmm:mixer -192 tests
Hello together!
I'm currently poking around in the NDK headers very much and I noted a
small inconsistency in the declaration of one type.
The declaration is the following in include\ndk\rtltypes.h:
==== source begin ====
typedef struct RTL_DRIVE_LETTER_CURDIR
{
USHORT Flags;
USHORT Length;
ULONG TimeStamp;
UNICODE_STRING DosPath;
} RTL_DRIVE_LETTER_CURDIR, *PRTL_DRIVE_LETTER_CURDIR;
==== source end ====
Shouldn't it be "_RTL_DRIVE_LETTER_CURDIR" instead of
"RTL_DRIVE_LETTER_CURDIR"?
I don't know what influences this missing underscore has on compilation
and such, cause I can read C without big problems and write a bit as
well, but I don't understand every single bit a C compiler does ^^
Regards,
Sven
Doesn't windows use SxS to provide multiple versions of some dlls? I know
its not for exacly the same purpose but perhaps coupled with some sort of
app compat wizard we could really set hard version targets... but ofcourse
it would mean building many dlls more than once
On Nov 13, 2010 2:09 PM, "Colin Finck" <mail(a)colinfinck.de> wrote:
Dear reactos developers.
Once again, bringing reactos build to cmake arises questions. When this
"port" has begun, it was decided that import libraries would be shipped
with build environment, the now famous RosBE.
This decision was made considering that :
1) functions exported by dlls do not change often.
2) Building an import library is a process that requires unneeded
extra time.
3) 1 makes 2 unworthy.
4) If dll A imports function from dll B, it's not necessary to
build B before A.
5) Solving 4 solves the problem of cross-dependency.
As our target is win2k3 sp1 compatibility, a wise choice would be to
choose import libraries that expose function only present on win2k3 sp1.
The problem is that some wine dlls export functions that are from other
windows versions, and, worse, use them.
Let's see why this is a problem.
- function A is a vista function from dll foo
- function B is an XP function from dll bar
- for some reasons, B implementation calls A.
As you're clever developers ;-), you've seen that this would raise an
error from the linker, as A is not present in our libfoo.a
Hopefully, those cases are not too widespread, but they exist.
Let's consider solutions that have arisen as of now :
1) Implement A as an inline function in headers, so anyone
requiring it has it.
2) Linking bar.dll to some winefoo.dll, which forwards everything
from foo.dll and exports the function A.
3) Add a "#if WIN32_WINNT > 0x502" before the guilty part of code,
and "#else" with a win2k3 compliant implementation.
4) Oh dreams -> Ideally, convince wine to do it themself
(./configure --wintarget=2k3sp1).
5) Change our target to win7, so we're ahead of wine. :-p
6) Do not change anything, and let our user mode libraries be a
complete inconsistent anarchy.
As 4 and 5 won't happen in a short time, let's consider 1, 2, 3 and 6:
1 is the best solution for easy winesyncs. We guard inline
implementation by #ifndef BUILDING_FOO_DLL
2 would put a whole mess in system32 directory, but should be the
most easy thing to do.
3 requires some extra work when syncing wine dlls. Though doing it
often would reduce hassle.
6 isn't what I'd wish.
What do you think? Your input is much appreciated.
Best regards.
The french speaking cmake team :-)
Hi everyone,
I'm wondering whether our [PREFIXES] in commit messages are still useful
as of today?
If I recall correctly, they were once added to autogenerate a changelog.
I also remember that this dramatically failed when Ziliang created the
0.3.12 changelog and the full changelog needed to be redone from
scratch, manually of course.
Furthermore, I doubt that prefixes like "[SPRINTF]" (r49512) or faulty
ones like "{ASM]" (r49413) can still be reasonably associated to a
changelog category.
After all, we don't even have a list of valid prefixes, so one has to
first look at all used ones anyway.
Of course, I don't want them to be dropped instantly tomorrow, but I'm
interested in your opinions.
I also don't yet know about the planned method for creating the 0.3.13
changelog, so I might be wrong on this.
Cheers,
Colin
Hi,
I see you're busy discussing other stuff and my message went unnoticed :) I
made a look to existing network branches, found many of them. LWIP is
interesting. Alexey said the best way is to join your irc channel. I will
try to occasionally join, but in your project, mailing list must be a
primary point of discussion not irc channel.
I think I start from making a simple, but robust tcpip driver (with help of
numerously available source code of tcp/ip protocol implementations).
Hopefully you could give me branch access, it's gonna be hard to develop it
with patches.
// Oleg Baikalow.
P.S. I really like your "kernel coding style", quite rare to see that in
opensource projects. Most of foss projects utilize linux-alike stlye, whic
is harder to read and not that clean.
Hello,
we have a serious regression in trunk which started 23rd of October
with revision 49231 ("hook rewrite"). Considerable amount of time
passed, automatic testing is not possible thus I'm afraid we are
accumulating bugs.
I think there is a need to revert 49231 + its dependencies in trunk
to allow automated testing to work again and also fix regressions
caused by this rewrite, and move this rewrite to a branch if possible.
In future, it would be a good idea to:
a. Discuss such serious rewrite merges beforehand (like Timo did with
Yarotows).
b. Try not to merge all rewrites simulteneously.
E.g. I have to wait with heap rewrite merge (every rewrite contains a
certain amount of bugs, by definition) even though it's fully ready.
James - could you please share your opinion? The decision is yours,
as you are the author of that commit.
WBR,
Aleksey Bragin.
Hey everyone,
a few days ago, I started investigating a report in Bugzilla
containing an application that raises
an exception that goes unhandled, and the stack trace that gets
printed is clearly corrupt.
The report is the following:
http://www.reactos.org/bugzilla/show_bug.cgi?id=5684
At first I thought the context wasn't being recorded properly, since
both EBP and ESP are reported
as being 0 at the time the exception was raised. However, there are
applications for which we show
a correct stack trace in case of an unhandled exception, so this most
likely wasn't the case.
My next thought was that we were somehow corrupting the context, but
this wasn't the case either.
The exception is also being dispatched nicely: exception handlers get
the correct details.
Lastly, the UnhandledExceptionFilter seemed to be passing the context
on to the stack trace printing
function without altering it, so the problem isn't there either. So
where else could something be
happening? That's right, inside one of the exception handler functions.
Some of you may recognize the exception code (0xeedfade) in the bug
report as a Delphi exception.
I did too, so I fired up my copy of Delphi 6 and went digging in its
exception handler functions.
Every occurrence of UnhandledExceptionFilter in its exception handler
functions showed the context
wasn't being passed to it, but instead the registration frame was.
This happens in a very predictive
way however, so creating a patch (read: filthy hack) that detects this
and fixes up the context record
was easy. It is heavily tied to exactly this kind of defect, no general case.
Running the application still triggers the exception of course, but
now we get a reliable stack trace.
A naive search in Bugzilla indicates at least the following reports
are affected by this problem:
Bug 3602, bug 3927, bug 5123 and bug 5684.
I haven't tested them all, but the tell-tale signs are there.
What does one do when encountering such a bug in compiler? Check if
it still exists in the latest
version and file a bug report of course. I got confirmation that the
bug is present in the recently
released Delphi XE with the help of Marco van de Voort of the
FreePascal project (shameless plug, I know).
A bug report has been filed with what I consider an extreme amount of
detail and how to solve it in
their product. Did I mention the report also contains a shameless
plug to the ReactOS project?
Today, to my astonishment, I found another report on their site
which.. you guessed it.. mentions
this problem. This report appears to have been made in 2007, so
guessing when (newly compiled)
Delphi applications will finally start calling
UnhandledExceptionFilter correctly is an exercise
I leave to the reader.
Now to get to the question that some of you may already be asking, and
is the purpose of this mail:
Are we putting this hack into our codebase so we get a decent stack
trace when an application messes up in
the manner this mail is about, or not? Applications can mess this up
in a lot of different ways,
so it won't work on those.
I warmly invite everyone to weigh in on this attempt of a discussion
(which I hope will be productive),
and hope people will see (again) that not everything that goes wrong
in ReactOS is the fault of the OS.
References for those interested in the nasty details:
Bug report: http://qc.embarcadero.com/wc/qcmain.aspx?d=89377
Patch:
Index: dll/win32/kernel32/except/except.c
===================================================================
--- dll/win32/kernel32/except/except.c (revision 49448)
+++ dll/win32/kernel32/except/except.c (working copy)
@@ -218,6 +218,13 @@
PEXCEPTION_RECORD ExceptionRecord = ExceptionInfo->ExceptionRecord;
PCONTEXT ContextRecord = ExceptionInfo->ContextRecord;
+ /* Attempt to hack around bad calls of UnhandledExceptionFilter */
+ if ((ULONG_PTR) (ExceptionRecord->ExceptionAddress) !=
(ULONG_PTR) (ContextRecord->Eip))
+ {
+ DPRINT1("Bogus context detected, using context record HACK!!\n");
+ ContextRecord = (PCONTEXT) ExceptionInfo[1].ExceptionRecord;
+ }
+
/* Print a stack trace. */
DbgPrint("Unhandled exception\n");
DbgPrint("ExceptionCode: %8x\n", ExceptionRecord->ExceptionCode);
@@ -415,11 +422,17 @@
if (dwExceptionCode == 0xeedface)
{
- DPRINT1("Delphi Exception at address: %p\n",
ExceptionRecord.ExceptionInformation[0]);
+ DPRINT1("Delphi 2 Exception at address: %p\n",
ExceptionRecord.ExceptionInformation[0]);
DPRINT1("Exception-Object: %p\n",
ExceptionRecord.ExceptionInformation[1]);
DPRINT1("Exception text: %s\n",
ExceptionRecord.ExceptionInformation[2]);
}
+ if (dwExceptionCode == 0xeedfade)
+ {
+ DPRINT1("Delphi Exception at address: %p\n",
ExceptionRecord.ExceptionInformation[0]);
+ DPRINT1("Exception-Object: %p\n",
ExceptionRecord.ExceptionInformation[1]);
+ }
+
/* Trace the wine special error and show the modulename and functionname */
if (dwExceptionCode == 0x80000100 /*EXCEPTION_WINE_STUB*/)
{
WBR,
Roel Messiant
Hi,
when commiting translation changes in a patch, please modify every language resources file.
Think about our translators :).
Best regards,
P. Schweitzer
Exactly.
The current explorer is self contained and incorrect according to true win32 shell architecture.
Our shell libraries aren’t complete enough to support the new explorer.
Andrew Hill was working on these libraries along with a basic ATL implementation some time ago.
I haven’t heard from him for a while now though.
Ged.
From: Adam Kachwalla [mailto:geekdundee@gmail.com]
Sent: 03 November 2010 08:51
To: Ged Murphy
Subject: Re: [ros-dev] explorer_new
Interesting... so I guess the old explorer.exe implemented that from scratch - I guess the one in shell32 is incomplete then right?
On Wed, 03 Nov 2010 19:50:18 +1100, Ged Murphy <gedmurphy(a)gmail.com> wrote:
It’s implemented in shell32 as an undocumented COM object.
From: Adam Kachwalla [mailto:geekdundee@gmail.com]
Sent: 03 November 2010 08:34
To: Ged Murphy
Subject: Re: [ros-dev] explorer_new
It is part of the shell though isn't it? If start menu isn't part of explorer then what is it part of?
On Wed, 03 Nov 2010 19:32:53 +1100, Ged Murphy <gedmurphy(a)gmail.com> wrote:
That’s because the start menu isn’t part of explorer
From: Adam Kachwalla [mailto:geekdundee@gmail.com]
Sent: 03 November 2010 08:28
To: 'ReactOS Development List'; Ged Murphy
Subject: Re: [ros-dev] explorer_new
Although it seems completely non-functional in the latest trunk builds. Start menu doesn't work, etc.
On Wed, 03 Nov 2010 19:23:29 +1100, Ged Murphy <gedmurphy(a)gmail.com> wrote:
It’s relatively complete, it’s the support libraries which are incomplete.
The only people with then necessary COM and shell skills (which is only really 2 of the ros devs) are either busy with other things or on sabbatical.
Ged.
From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Adam Kachwalla
Sent: 03 November 2010 01:19
To: ReactOS Development List
Subject: [ros-dev] explorer_new
Can anybody tell me what explorer_new is meant to be there for?
I understand people used to be working on it before, but it seems abandoned.
--
Give a man a fish and he will eat for a day.
Teach a man to fish and he will eat for a lifetime.
Give a man religion and he will die praying for a fish.
--
Give a man a fish and he will eat for a day.
Teach a man to fish and he will eat for a lifetime.
Give a man religion and he will die praying for a fish.
--
Give a man a fish and he will eat for a day.
Teach a man to fish and he will eat for a lifetime.
Give a man religion and he will die praying for a fish.
Hi guys,
I'm reading win32k.sys right now. I found KeyboardThreadMain thread
only use KeyboardClass0 device. I want to know how to communicate
KeyboardClass1,KeyboardClass2, and so on?
Fan Zhang
Hi guys,
I'm reading win32k.sys right now. I found KeyboardThreadMain thread only use
KeyboardClass0 device. I want to know how to communicate
KeyboardClass1,KeyboardClass2, and so on?
Fan Zhang
I've just tried to build the cmake branch for the first time and hit the following error :
-- xmllite has no base address
-- win32csr has no base address
-- Configuring done
CMake Error in dll/ntdll/CMakeLists.txt:
Cannot find source file "ntdll.def". Tried extensions .c .C .c++ .cc .cpp
.cxx .m .M .mm .h .hh .h++ .hm .hpp .hxx .in .txx
Reverting the changes in this revision fixed it.
I know nothing about cmake, but this change appears to have broken the build?
Ged.
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of jgardou(a)svn.reactos.org
Sent: 01 November 2010 09:32
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [jgardou] 49396: [CMAKE] - put ntdll.def in source files
Author: jgardou
Date: Mon Nov 1 09:32:04 2010
New Revision: 49396
URL: http://svn.reactos.org/svn/reactos?rev=49396&view=rev
Log:
[CMAKE]
- put ntdll.def in source files
Modified:
branches/cmake-bringup/dll/ntdll/CMakeLists.txt
Modified: branches/cmake-bringup/dll/ntdll/CMakeLists.txt
URL: http://svn.reactos.org/svn/reactos/branches/cmake-bringup/dll/ntdll/CMakeLi…
==============================================================================
--- branches/cmake-bringup/dll/ntdll/CMakeLists.txt [iso-8859-1] (original)
+++ branches/cmake-bringup/dll/ntdll/CMakeLists.txt [iso-8859-1] Mon Nov 1 09:32:04 2010
@@ -21,10 +21,8 @@
rtl/libsupp.c
rtl/version.c
def/ntdll.rc
- def/ntdll.def)
+ ${CMAKE_CURRENT_BINARY_DIR}/def/ntdll.def)
-set_source_files_properties(def/ntdll.def PROPERTIES EXTERNAL_OBJECT TRUE)
-
if(ARCH MATCHES i386)
list(APPEND SOURCE dispatch/i386/dispatch.S)
elseif(ARCH MATCHES amd64)
@@ -48,7 +46,6 @@
endif()
target_link_libraries(ntdll
- ${CMAKE_CURRENT_BINARY_DIR}/def/ntdll.def
ntdllsys
libcntpr
pseh)
Hello,
The jgardou changes add thousands of whitespace changes which make it extremely hard to understand what is going on. Please to not arbitrarily change whitespace across 18 files in a patch!
Also, there is nothing wrong with the way ClassPNP was defined before. If you think "How on Earth did this work in trunk?", as quoted from the commit log, maybe you should ask others "Hey, how did this work?".
Please revert the changes and come ask how it worked, I'll be happy to help.
-r
Hi reactos developers.
As many of you know, the cmake branch development is going along and is
the occasion of many innovations in the way reactos is built.
One of this way is the reactos.dff file. Currently, it is a static file,
meaning that each time you want to add a module to reactos, you have to
edit this file. What I propose is to create this file dynamically, when
parsing the build system file. Adding a reactos module twould then be as
simple as (!) creating a new build file for this module.
For those who are concerned about slipstreaming or optional files like
wallpapers or whatever hacking they do with the current reactos.dff, it
will be as easy as before. There will be a file to edit, which will be
the "static" part of it. Whatever you'll write in this file will be
written back to reactos.dff, so there is no need to worry about that.
What do you think?
Regards.
Jérôme.
PS : The patch is there. It waits for your approval :-)
Where is my Server core style command prompt login? Screw explorer. Oh,
and I want RDP. ;0p
On Oct 27, 2010 4:18 PM, "Adam Kachwalla" <geekdundee(a)gmail.com> wrote:
We need to first fix up the logon screen. I have tried this, except the
problem lies with CreateDesktop() not wanting to create more than one
desktop within the Winlogon process.
At this stage, the logon/logoff functionality does not work at all, and some
processes still linger about.
It appears explorer shell is one of them.
On Thu, 28 Oct 2010 02:22:36 +1100, Javier Agustìn Fernàndez Arroyo <
elhoir(a)gmail.com> wrote:
> H...
--
Give a man a fish and he will eat for a day.
Teach a man to fish and he will eat for a lifetime.
Give a man religion and he will die praying for a fish.
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://ww...
Hello, devs!
ok, lets stop flaming and lets do anything useful 3:>
For the future:
will ReactOS support "true" multiuser sessions (that is, *simultaneously*)?
Is it possible?
that would be a big enhancement over Windows :)
I think that Wine Gecko should be integrated in the ReactOS releases. It
is needed IIRC for things like Winhlp32 (I think) and HTML Help
(defiitely) and applications which use IE browser controls.
Hi ReactOS friends and colleagues.
There have been exciting years, I first started to have an eye on the
freewin95 project. When I first found the ReactOS project and saw
that they actually gave away free zip-files with files to try it out
I was eager to test it my self, I first downloaded my first
“bochs-1.3-reactos-images.zip” the third april 2002, and it worked! I
was amazed, so I downloaded and tested everything that I could test.
A long time has gone since that time and I have seen a lot of
progress during the years, however it's a lot of years, for me about
nine years of downloading, compiling, testing and reading svn-
messages. For many people it has been too many years and many have
fallen away, now however we are close to something that can actually
be used, the kernel is pretty stable other parts of the OS is
improving and getting there too.
During the last many years we have had about 100 individuals in the
IRC channel at all time, it indicates in my mind that we attract as
many people as we loose, I guess that is kind of the status for our
project, we should be able to change that in a short while I think.
If we can release a some real-life applications for our OS we could
draw some attention that could be permanent and the project could
really start to grow for real.
I and Aleksey met in Björkvik, Sweden for a discussion on how to get
the ball rolling, we have some suggestions that could serve as step
stones for such development. The key is to release a package of the
project and see to that it can really do that but not everything
else, for example, a web server, it doesn't need all the OS but the
ones it needs it has to do really good.
Even with this in mind ReactOS isn't well suited for many real
applications, so we just looked at a few to see if it would be a way
to go, you could perhaps suggest some more, and we would welcome
that, we only have to ensure there isn't too much work to actually
come to the finish line. Here we present some ideas and what needs to
get in place to actually make it work.
Webserver
- Network subsystem (mainly tcpip.sys driver, and some winsock
improvement)
- VNC support (future RDP support)
- Apache/MySQL/PHP support
- XAMPP with toolbox
- WEBMIN
Thin Client (LiveCD or BootCD)
- Re-port our MSTSC.EXE
- Local printing (USB/LPT printer support?)
Please give us your opinion and please also add possible ideas that
you have and think through what needs to get in place to see it come
to pass.
Yours sincerely,
Aleksey & Jan (Jaix)
through Jan
Am 26.10.2010 18:01, schrieb jgardou(a)svn.reactos.org:
> +#ifdef __GCC__
> /* Note: this should return a CLIENT_CALL_RETURN, but calling convention for
> * returning structures/unions is different between Windows and gcc on i386. */
> LONG_PTR RPC_VAR_ENTRY
> @@ -659,6 +663,13 @@
> NdrAsyncClientCall( PMIDL_STUB_DESC pStubDescriptor, PFORMAT_STRING pFormat, ... );
> LONG_PTR RPC_VAR_ENTRY
> NdrDcomAsyncClientCall( PMIDL_STUB_DESC pStubDescriptor, PFORMAT_STRING pFormat, ... );
> +#else
> +CLIENT_CALL_RETURN RPC_VAR_ENTRY NdrClientCall2(
> + PMIDL_STUB_DESC pStubDescriptor,
> + PFORMAT_STRING pFormat,
> + ...
> +);
> +#endif
>
Is this hack even neccessary? I couldn't see any difference between gcc
and msvc with the correct prototype.
Both return the result in eax.
Hi,
good to see the branch work back in trunk, I suspected this work would be
left to rot and finally be forgotten (like in most other experimental
branches). Altogether this looks like a huge step forward, got to test those
mode switches it once I have enough time.
One thing I noticed from the diffs is the eng/mem.c file, which exceeded my
EVIL / HACK threshold. Is this supposed to stay - especially in the context
of ARM3's to be proven awesomeness?
--- snippet ---
EngSecureMem(PVOID Address, ULONG Length)
{ return (HANDLE)-1; // HACK!!! }
EngUnsecureMem(HANDLE Mem)
{ if (Mem == (HANDLE)-1) return; // HACK!!! }
--- snippet ---
Good work anyway, thanks to the people involved!
Regards,
Gregor
You could always run two installs in different directories.
On Oct 25, 2010 10:51 AM, "Bernd Blaauw" <bblaauw(a)home.nl> wrote:
Op 25-10-2010 16:09, Fan Zhang schreef:
>
> Thanks. But I don't know if i run ReactOS, how could I replace the kernel
file, such as ntoskrl...
So basicly running a ReactOS installation with RosBE installed as
application, sources downloaded and modified, and then you want a way to
update files from this ReactOS installation itself?
As long as ReactOS installs only on FAT filesystem, I guess you could use a
DOS bootdisk/installation to overwrite any files. It's not entirely
convenient.
Is there basicly a set of lists of ReactOS files for the following:
* which ReactOS files can be overwritten by a new file while you're still
running in ReactOS? .inf files? small games like solitaire?
* which ReactOS files can be overwritten, but require a reboot to be
properly noticed? some drivers perhaps?
* which ReactOS files require you to be outside of ReactOS in order to
replace them? ntoskrnl comes to mind, explorer I guess
All in all, mr Fan Zhang might be asking for some kind of update mechanism.
If you had an old machine which you run ReactOS on, together with same
casual data (audio files perhaps), do you need to reformat the disk to
update ReactOS? or only remove the installation directory? or pick a
different installation directory? or same directory? After all, you don't
want to lose any user data.
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://ww...
Hi guys,
I want to know how do you debug ReactOS. For example, when I change the
code, I used to execute 'Make bootcd'. After that, I will install the
ReactOS system by ReactOS.iso. So I'm confused if I have to install the whoe
system after compiling. Do you have some easy way?
Thanks.
Fan
Hi,
I thought I would drop a line here finally :)
My name is Oleg, I am from Russia (some 180km from Moscow :)). I worked with
Aleksey many years ago on some kernelmode networking-related tasks for
Windows NT 4.0 and later Windows 2000. Your recent 0.3.12 release news was
all over the place here on Russian news sites, my congratulations! ReactOS
is a great project, though I never had enough time to actually start
hacking, but recent achievements seems to motivate me more.
What is situation with networking in ReactOS? I think this could be my main
direction of work. I would glad if someone writes a current state of
networking in ROS, so I would know where to start.
// Oleg Baikalow.
Hi everyone,
I'd like to announce that I'm soon going to merge yarotows back into
trunk, if no other regressions are found. The current issues (red icons
and blue text on disabled buttons will be fixed, Kamil has already a fix.)
Last chance to test and object ;-)
Regards,
Timo
I am currently checking our 0.3.12 milestones. And the milestones status is:
**********(Bug 5517)Some icons look wrong (blue background)**********
There is a Hack for the release.
**********(Bug5560): Adobe Acrobat Reader 7.1 throws exception at start****
This is a Wine regression. It is not in our hands.We have to wait for a Fix.
**********(Bug 5472) comctl32: Keyboard shortcuts don't work after winesync***
Not as bad as it sounds. It does not work just in 2nd Installation Stage.
Anyway, there is a Hack for this issue too.
**********(Bug 5314) REGRESSION: Acrobat Reader: pen leak*******
It is supposed to be fixed, but it is Bug5560 dependant so it is impossible to confirm the Fixed status.
**********(Bug 5598) PATCH: Opera 9.64, FireFox 3.0+ crash when using Russian/Lithuanin/Ukrainian locale****
Reverting the *.nls changes solves the issue.
There is a Hack attached.
**********(Bug 5482)REGRESSION: ExplorerXP: black background on treeview area*****
This is a Wine regression. It is not in our hands. We have to wait for a Fix.
**********(Bug 4106) REGRESSION: Wrong text spacing in popup menus / icons after show a font in control applet / Remote Desktop*******
It is a minor regression since it has been there for a while. Also Yarotows seems to fix some of the issues.
**********(Bug 5591) REGRESSION: devmgr: wrong icons in the TreeView *****
Updating comctl32 will fix the issues. Or we can revert the comctl32 changes.
**************
* Summing up *
**************
There are 8 regressions.
4 has different options to be solved (Hack or Wine update/revert)
2 are current Wine regressions (we have to wait for a fix or revert Ole32/Comctl32 changes)
1 could be fixed (the Acrobar Reader leakage) but we need to fix Acrobat first(reverting?)
1 is a minor regression without a solution ( "Bug 4106")
So we can solve 7/8 regressions. Is it time to think about a 0.3.12 release? It is time to take decisions (reverting/updating/waiting Fixes) since there are solutions.
I don't think having the Trunk frozen is good for the project.
So, opinions?
I think its a good time to discuss current development cycle.
It become clear to me, that there is no way we can currently adhere to 3
months development cycle. Its pointless to stick to something we managed to
succeed only once or twice.
Agreeing with the fact we do need releases, for various reasons, i would
like to propose a new, longer cycle.
The most apparent choices to me are 4 and 6 month ones. At least half of the
cycle would be spent on all out development, with the following half turning
its concentration to stabilizing trunk, searching for regressions and bugs,
fixing them. The cycles would be separated by branching the release version.
The actual release would be taking place on the first month of the NEXT
DEVELOPMENT cycle. The actual emergency hacking, writing changelog etc. One
month is more than enough, to release two RC (at the branching and next one
- after two weeks). End of the month must result in final release. RC should
be rather released internally for testing purposes on a default iso.
The actual proposals are:
4 months:
month 1: Development on version x. At the same time, the Release x-1 is to
be final-tested, emergency-hacked, changelogged and shipped. The deadline is
end of month 1.
month 2: Development on version x. All development that can affect trunk
stability, but also will not be shipped with the release X should end or be
limited to branch only by the end of this month;
month 3: Switching from development more to stabilizing trunk, searching for
regressions, fixing bugs. Finalizing sub-projects that are to be included in
release x;
month 4; No new functionality/code, bug-fixing and hunting regressions. This
month should end with branching for release x;
6 months:
month 1: Development on version x. At the same time, the Release x-1 is to
be final-tested, emergency-hacked, changelogged and shipped. The deadline is
end of month 1.
month 2: Development on version x;
month 3: Development on version x. All development that can affect trunk
stability, but also will not be shipped with the release X should end or be
limited to branch only by the end of this month;
month 4: Switching from development more to stabilizing trunk, searching for
regressions, fixing bugs. Ongoing development work only for features that
are to be shipped with release x;
month 5: Switching from development more to stabilizing trunk, searching for
regressions, fixing bugs. Finalizing sub-projects that are to be included in
release x;
month 6: No new functionality/code, bug-fixing and hunting regressions. This
month should end with branching for release x;
Hi!
Since I'm starting to move around now and fell better. Let's just say,
I guess it's time to move from the window object and move to the wnd
one. I have two local branches here on the portable system, one for
Right to Left support (wine sync) I've started and the standard test
one. I would like to have all the available Win32 developers help out.
You too Ged! Try to get this done before to much goes into CMAKE and
have to rework it all.
>From window.h:
/* Scrollbar info */
PSBINFOEX pSBInfo; // convert to PSBINFO
/* Entry in the list of thread windows. */
LIST_ENTRY ThreadListEntry;
} WINDOW_OBJECT; /* PWINDOW_OBJECT already declared at top of file */
/* Window flags. */
#define WINDOWOBJECT_NEED_SIZE WNDS_SENDSIZEMOVEMSGS
#define WINDOWOBJECT_NEED_ERASEBKGND WNDS_ERASEBACKGROUND
#define WINDOWOBJECT_NEED_NCPAINT WNDS_SENDNCPAINT
#define WINDOWOBJECT_RESTOREMAX (0x00000020) // Set/Clr WS_MAXIMIZE &
#define WINDOWSTATUS_DESTROYING WNDS2_INDESTROY <----- "WNDS2"
state2 flag
#define WINDOWSTATUS_DESTROYED WNDS_DESTROYED <----- "WNDS" state flag
Move this to ntuser.h including the SBINFOEX too, not sure I did that
one yet, and start hacking it then test the hell out of it. The flags
just convert them to the correct ones, _RESTOREMAX may need more
research (another word for HAX).
Just writing this and it looks simple, but this is one file that
effects the whole w32k tree.
Thanks,
James
That will be hard to beat for r50000...
> Author: sir_richard
> Date: Tue Oct 5 15:59:47 2010
> New Revision: 49000
>
> URL: http://svn.reactos.org/svn/reactos?rev=49000&view=rev
> Log:
> [NTOS]: Fix whitespace typo in comment (two spaces instead of one).
> That's right. I'm not a fun person.
>
This is a possible fix for the initialization problem reactos suffers
from. Just let me know, how it goes with testing. ATM QEmu works okay
and no hardware test was run.
Thanks,
James
LOL!
Keeping it from running off the side of the page! Know one told you!?
The screen is flat! If you go out to far, the characters will fall
off!
@@ -217,7 +216,8 @@
!(pEH->Flags & WINEVENT_SKIPOWNPROCESS)) ||
!pEH->idProcess ) )
{
- Result = co_IntCallEventProc( UserHMGetHandle(pEH),
+ // What in the deuce is this right-aligned formatting?
+ co_IntCallEventProc( UserHMGetHandle(pEH),
Event,
UserHMGetHandle(pWnd),
idObject,
I'll audit your code and commit ass cocking comments too........
James