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?