Dear Devs,
I've tested a win32 port of rdesktop for linux, and it works in current
trunk (http://img440.imageshack.us/my.php?image=rdesktop3hi1.jpg), since our
rdp client doesn't work, I was wondering if this one could be included
instead, it's released under gpl, perhaps adding a gui, I don't think it's a
lot of work, correct me if I'm wrong, you can find the sources here:
http://os.american-data.com/rdesktop/win32/
Best regards,
gabriel_it
Have a nice day!
_________________________________________________________________
Scarica GRATIS Internet Explorer 7 personalizzato MSN
http://optimizedie7.msn.com/default.aspx?mkt=it-it
This should go into rosapps, unless it's being used during the setup
process for example (which it is not).
WBR,
Aleksey Bragin.
On Aug 14, 2007, at 12:52 AM, gedmurphy(a)svn.reactos.org wrote:
> Author: gedmurphy
> Date: Tue Aug 14 00:52:47 2007
> New Revision: 28324
>
> URL: http://svn.reactos.org/svn/reactos?rev=28324&view=rev
> Log:
> - fix the code, untested
> *note, shouldn't this be in rosapps?
>
> Modified:
> trunk/reactos/base/applications/network/dwnl/dwnl.c
> trunk/reactos/base/applications/network/dwnl/dwnl.rbuild
>
Hi ReactOS guy's,
are you not able to discuss a topic in your forum or why did you delete my
post in http://www.reactos.org/forum/viewtopic.php?t=4307 ?
Here is it again:
[quote="jimtabor"]
The irc meetings, there are two I think. It was voting on how to do the
audit. Later if I remember right, we started movie review and joking around
with unrelated issues.
[/quote]
I'm missing something about the meetings. [url=
http://www.reactos.org/archives/public/ros-dev/2006-January/007478.html]Ste…'s
mail[/url] starts with:
[quote="Steven Edwards"]
There has been a lot of talk about possible tainted code in ReactOS and or
developers that had access to leaked Microsoft source code.
[/quote]
and later
[quote="Steven Edwards"]
We know of four developers who have had access to leaked sources prior to
working on ReactOS..
[/quote]
Depend on the [url=http://www.reactos.org/en/dev_legalreview.html]ReactOSproject
development policy[/url]
[quote="ReactOS project development policy"]
Developers who have had access to proprietary source code that would have
originally fallen under trade secret protection (including, for example, the
leaked Microsoft Windows source code) are a special case. The copyright
issues are unchanged, as are the patent issues, but any developer who has
the code is clearly either under an NDA or else does not have a license to
possess the code. In the latter case, there is a clear violation of the
relevant trade secrets by the developer. As such, this kind of code is
unsuitable even for research and understanding. It is the policy of the
Project to not take submissions from developers who have or use any such
proprietary code in their development efforts for ReactOS.
[/quote]
this developers have to be banned from the project. Steven's mail or the
developer's voting wasn't so restrictive:
[quote="Steven Edwards"]
4) any developer that had access to leaked sources is baned from
contributing code to the project for any of the modules that are the
same as leaked sources they examined.
[/quote]
The question is, why are the tainted developers not banned? If only a few of
the developers had access to the leaked windows source code, it is not a
problem to ban them. I think more than four developers had access to the
leaked windows source code. In this case it will never get a vote for
banning the tainted developers, because they must ban itself. It exists the
'Open letter to all' from Alex. I've got the original mail with all the
names from one of the developers.
[quote="Alex's 'Open letter to all'"]
/*Steven, Aleksey, Mike and myself had leaked windows code and looked at it.
KJK, Eric, Filip, Magnus and Marteen had IDA and used it for reverse
engineering. 9 developers, and these are only some cases.*/ Herve too,
sometimes used IDA to verify some flags (I once helped him understand a
weird DEVICE_EXTENSION structure), and Thomas, although against
reverse-engineering, also used IDA to verify some implementations, although
he said he never used it to actually reverse-engineer, and I believe him,
although, once you have seen the taint, it's hard to really psycologically
prove how much you were, or were not influenced by it. /*With more then
2/3rds of the entire developer team having broken the law and/or our IP
policy, I continued my work in the same way.*/
[/quote]
Now the story make sense. The implementation of ReactOS is based on the
leaked windows source code and possible more than the four named developers
had or have access to this code.
[quote="jimtabor"]
As you all can see, things have gone on to this project. Money was the key
word here. Wine, Casper, GvG, hbirr etc,,, mass manipulation to gain from
other peoples work.
[/quote]
And now it makes sense why you accuse some of the developers, which had left
the project, that they have done something for money...
The only developer, which has something to do with money, is Alex. In May he
was bought by Microsoft.
Hi!
When will ROS 0.3.3 comming out?
On July, 21th you anounced 0.3.3 RC1 at
http://www.reactos.org/archives/public/ros-dev/2007-July/009571.html
You have also changed the front-page, that the actual version is 0.3.3 RC1
and on the downloadside there is now also only 0.3.3 RC1.
Will 0.3.3 any time really comming or existing now 0.3.3 RC1 for it instead
and the next one will be 0.3.4 ?
Btw: On the download-side the links to the CD-Booklets don't exists.
It showns now to 0.3.3-RC booklets, but the only one which exists are 0.3.1
booklets.
Greatings
theuserbl
_________________________________________________________________
Sie suchen E-Mails, Dokumente oder Fotos? Die neue MSN Suche Toolbar mit
Windows-Desktopsuche liefert in sekundenschnelle Ergebnisse. Jetzt neu!
http://desktop.msn.de/ Jetzt gratis downloaden!
Hi all,
I wonder if the RosBE-Windows must be the one which removes autogenerated files.
In this case , we have to :
- merge the list into RosBE-Unix
- publish updated versions when the list changes.
- last but not least, the user must have the svn versions of RosBE to get a completely clean tree.
Colin suggested we can put it into the Makefile, which would be simpler and more efficient.
Kind regards,
Sylvain Petreolle (aka Usurp)
--- --- --- --- --- --- --- --- --- --- --- --- ---
Run your favorite Windows apps with free ReactOS : http://www.reactos.org
Listen to non-DRMised Music: http://www.jamendo.com
Hi
is betov are moreon or idot or brian dead person
I can not longer keep my feeling in shape thanks to him
It seam that betov is out damges every good open source
project on the market. Let see now which project he is trying
damges
1.ReactOS
It is well known he dislike us, and my advice we ignore him
it seam he does not known what his is talking about, and
it seam in my eyes his claim is not vaild
2. Sano
ReactOS borro some code from this project
and that code betov trying convice it is illage
3. SDL
Almost same code can be found in SDL
for same part we talking about, the code
are almost same as Sano code. That
mean Betov trying destor this project
as well
4. Nasm32
what he have gone after NASM 32, now
and claim it is illage for they do not ship
the source code in the binary. or the
licen agreemtn, and some other stuff
more we can read about his stupied
http://groups.google.com/group/alt.lang.asm/browse_thread/thread/35cd7e11ff…
it is not wonder people do not take him serius he is like a big moron
and trying sabtages opensource project world wide for people do not
support his rosasm project. And I have follow now his writting for few
month and more I read, more it seam it is something wrong with his
brain. he calling people with bad names and attact people when
they ask him simple question, it mean he socal skill is bad or
is is brain dead, that is my cludtions after reading his vaurs stuff
he writitning on the net. Or even better bethov is getting pay leading
sabtages agaist opensource project that is well known, He maybe getting
pay from MS/DMCA/NOVELL how knowns, but it seam not in this case
it seam he is complete brian dead.
Hello list,
I'm new here, so at first I'd like to greet everyone ;)
second: I had some problems running rbuild on WinXP SP2
self compiled with msvc 8.0 (Express) to produce .vcproj files.
I've found the problem in vcprojmaker.cpp and another thing, which
prevents me from building rbuild in genguid.cpp and I would like to
contribute a patch.
Kind regards,
Michael Sprauer
Fixed in 28257.
WBR,
Aleksey Bragin.
On Aug 9, 2007, at 9:37 AM, James Tabor wrote:
> ./include/internal/kd.h:212:KdpKdbgInit(
>
> obj-i386/ntoskrnl/kd/kdinit.o: In function `KdInitSystem@8':
> /mnt/reactos/fullrel/build/ntoskrnl/kd/kdinit.c:(.data+0x24):
> undefined reference to `_KdpKdbgInit@8'
From the SDK!
Come on! get upto date!
W32KAPI BOOL APIENTRY
NtGdiAlphaBlend(
__in HDC hdcDst,
__in LONG DstX,
__in LONG DstY,
__in LONG DstCx,
__in LONG DstCy,
__in HDC hdcSrc,
__in LONG SrcX,
__in LONG SrcY,
__in LONG SrcCx,
__in LONG SrcCy,
__in BLENDFUNCTION BlendFunction,
__in HANDLE hcmXform // I saw a zero here.
);
We have this in psdk/ntgdi.h
W32KAPI
BOOL
APIENTRY
NtGdiSetIcmMode(
IN HDC hdc,
IN ULONG nCommand, // see below,,,, I saw 1 -> 4 here.
IN ULONG ulMode
);
/* NtGdiSetIcmMode */
#define ICM_SET_MODE 1
#define ICM_SET_CALIBRATE_MODE 2
#define ICM_SET_COLOR_MODE 3
#define ICM_CHECK_COLOR_MODE 4
Using a good hook and compare eax to the list will set you free.
James