Hi,
It was Steven's idea that I should post this emai and I agreedl, so
please don't take it as my personal childish attempt to get attention,
unless you find that both I and Steven (our Project Coordinator) are
children.
Steven has recently expressed his opinion that: (modified quote so that
"your" -> "my")
"My arrogant attitude hurts this project more then any amount of code or
patches I commit will ever help it."
Therefore, since:
1) I really care about this project
2) I don't wish to spend time writing useless code (since no amount of
code will help the project more then I hurt it, then the code is
useless, like heating a room where the windows are open in winter).
I think it's important to know if this is a public opinion or not, so I
am opening a public ML vote. If it is, then I will gladly leave and stop
hurting this project, since those were not my intentions when I joined.
If this is the case, then I only regret for having stayed here so long
and done nothing but hurt the project for almost two years now, and I'm
sorry.
[ ] Alex's arrogant attitude hurts this project more then his code helps
it. Alex should therefore leave, so that the project can stop being hurt.
[ ] Alex's arrogant attitude is annoying at times but his presence in
this project significantly helps it grow and move towards reaching its
goals, and does not hurt the project.
Best regards,
Alex Ionescu
At the moment, there's one blocker bug registered, 1107: Opening a Command
Prompt (console) window causes the desktop to hang.
A lot of networking apps crash, all due to the same bug. Arty is working on
that one.
On each boot, I have to get rid of 5 device install screens. I'm not
complaining, I understand PnP is a work in progress, but if nobody objects
I'll change the code in the branch to never pop up the device install
screens.
Last item is perhaps a bit controversial. I don't like the huge icons in the
start menu. It also makes the start menu not fit in 640x480. Can we please
go back to smaller icons?
Other than these items (only 1 of them serious as far as I'm concerned) I
like the branch and I believe it will become a good release.
GvG
> From: Alex Buell
>
> I just got the following when trying to ftp to my host
> machine from ReactOS running in VMware. Are there any
> documentation out there that can help me make sense of what's
> happening below? Thanks.
>
> hal/halx86/generic/irql.c:272 CurrentIrql 2 NewIrql 1
> KeBugCheck at hal/halx86/generic/irql.c:273
Yes, this happens with a lot of networking programs at the moment. Art is
working on it.
GvG
2005/12/11, Alex Buell <alex.buell(a)munted.org.uk>:
>
> The patch that I issued for main.cpl DOES work - if you call control.exe
> directly and select either the keyboard and mouse applets you'll notice
> the patch works.
>
> Care to explain why you think the patch I sent in doesn't work?
>
sorry,
that's true.
I know that this is fluff, but I would like to contribute a good, honest
attempt at making a screensaver program for ReactOS. Basically, what I
am looking for is how is the API set up for ReactOS to write programs
for it? I am familiar with writing programs for Windows, and I know the
basic ins and outs of making a screensaver for
Windows (including it's registry settings), however there is some API
specific code that I need in order to give this a shot.
Do you guys have a reference of some kind as to what API functions,
constants, etc. that you have implemented in ReactOS that mirror those
of Windows?
Thanks in advance, and if there isn't enough in ReactOS yet for me to
try this out yet, then I'll try to help on something else that I would
be capable of.
And I must say, and I'm not trying to kiss ass here, but I really
appreciate what you guys are working at here. Keep it up.
Kenneth Armstrong
Hi,
First of all I would like to introduce myself. My name is Martin and I am
currently attempting to go through and audit the ReactOS source code for
security vulnerabilities. I've been keeping an eye on the project for
about a year now and I think as development is now rapidly increasing,
security must take more and more of a priority.
I started with the kernel32 library on Friday (9th) and have found a
number of possible security vulnerabilies. These have been filed with
bugzilla and i'm very impressed with the rate that these were fixed. So
well done on that count!
However, after submitting bugs #1102 and #1103 (now fixed by
BrandonTurner) it became apparent that incorrect usage of the
RtlAllocateHeap function (and its alias HeapAlloc) is quite common. It
may return NULL if memory cannot be allocated and in some parts of the
code this is not checked. This would lead to a segmentation fault on
reading / writing.
Through some judicious use of grep I went through the source code and
extracted calls to this function with their context. After going through
each one and investigating it I have now found another twenty occurances
of the same bug (This is just in the kernel32 library).
I am writing this to let all developers know that they must check their
return values. Errors can exist, resources may be starved and the call
may fail. Make sure your code can cope with this.
Finally, as I am fairly new to bugzilla, should I submit each of these
twenty bugs individually or should I submit them all as one bug?
Cheers,
Martin
Can't we include Mozilla Control in ReactOS? So that we build it with
our ROS Build Environment or whatever is used to compile ReactOS, put it
on bootcd and install it with ReactOS?
Greets,
David Hinz
gvg(a)svn.reactos.com schrieb:
> Files to create Mozilla Control installer with correct DLL
>
>
>
> Added files:
> trunk/tools/
> trunk/tools/MozillaControl/
> trunk/tools/MozillaControl/README.txt
> trunk/tools/MozillaControl/control-ros.nsi
> trunk/tools/MozillaControl/files.nsh
> trunk/tools/MozillaControl/local.nsh
> trunk/tools/MozillaControl/redist/
>
> _______________________________________________
> Ros-svn mailing list
> Ros-svn(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-svn
>
> From: gvg(a)svn.reactos.com
>
> Files to create Mozilla Control installer with correct DLL
I've created a "fixed" version of the Mozilla Control installer which
includes the correct MSVCP60.DLL and put it in our SourceForge download
area. shdocvw.dll will now download/install that fixed version.
GvG