On Fri, Jul 08, 2005 at 08:38:38AM +0200, Rafal Kupiec
wrote:
> I think I shoudn't write here this.
> Person finds free time to do it and you're doing
> problems. I think i'll never more write information
> about bugs in your system.
I shall refrain from commenting.
> BTW. Please download HostiliX Sources from SVN (rev
> 42). Make CD Image and boot it in VmWare or on real
> hardware. This problems don't occure in HostiliX!
Ummm... and please sign up for the bugzilla system
to submit your bugs?
You, as a full-time employee, can't be bothered to
sign up for bugzilla, but you expect all of us to
go download the entire HostiliX repo (some on dialup),
compile it, and boot it... just to prove/disprove
that the bug does or doesn't exist in code that's not
even ours?
Methinks you're holding a double-standard -- a very
self-centered one at that. Your time is -so- precious
that you can't be bothered to go through, at most, a
30-minute, one-time process in order to properly
report a bug, yet you think our time is soooo
expendable that we should go through a process that
could easily take some of us over an hour to do. Not
only that, but the process you want -us- to go through
doesn't even result in work getting done -- it would
succeed only in stroking your ego. Look! ReactOS has a
bug that HostiliX doesn't! Whoop-de-doo! Now what? We
can't re-use your code, since it's considered
"tainted," so we don't gain anything by verifying that
the HostiliX code does/doesn't work.
For the record: How many people on this list have
full-time jobs not related to ReactOS?
When I joined the ReactOS Bugzilla, I was a full-time
college student (15 credits, 22 hours of class/travel
a week, another 20+ hours in homework easily).
-- Travis
__________________________________
Discover Yahoo!
Have fun online with music videos, cool games, IM and more. Check it out!
http://discover.yahoo.com/online.html
ekohl(a)svn.reactos.com wrote:
> Fix a string length calculation bug in StringTableDuplicate.
Thanks for fixing it properly, that was a really awkward mistake ;)
Best Regards,
Thomas
Rafal Kupiec wrote:
> I won't register there.
> Do it yourself.
> I've informed you.
You really are very rude and disrespectful.
Why don't you fix them in the hostilix branch and submit your changes back
to ROS?
Oh that's right, you want to give code, only take, (and claim as your own)
Ged
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
One of the things which has bothered me a bit is the code duplication we
have in our DIB engine (subsys/win32k/dib). Most of the BitBlt routines in
there are very similar. With the recent interest in optimizations a bunch of
new (almost identical) routines were added. Don't get me wrong, I'm not
saying that adding those optimizations was a bad idea, I'm just pointing out
that we have a lot of code duplication.
There are 256 possible ROP codes, we support 1bpp, 4bpp, 8bpp, 16bpp, 24bpp
and 32bpp, so in theory there could be 1536 routines with basically the same
structure. I've been playing around with the idea to write a code generator
which would generate the source code for those routines. That would cut down
on the duplicated source code and associated maintenance problems (you only
need to change the code generator) while still allowing optimized code for
each individual ROP code.
Just to give you an idea what such a code generator would look like, I've
attached my first attempt. Please note that it doesn't really try to
optimize the generated code yet, it's just to give an impression. The code
generated (16bpp only atm) is rather large, you can get it from
ftp://ftp.geldorp.nl/pub/ReactOS/dib16gen.c if you like (or compile the code
generator ("gcc -o gendib gendib.c") and run it).
A possible problem is that the generated code is quite large. When using the
generated 16bpp code, size of win32k.sys increases by about 350kb.
Extrapolating this for all bpps, it would mean that win32k.sys would triple
in size.
So, I'm wondering what you guys are thinking. Should we basically trade
memory for speed? Problem is that I can't quantify the speed increase at the
moment.
Gé van Geldorp.
navaraf(a)svn.reactos.com wrote:
>Put the page tables and hyperspace at the right place in memory (ie. Windows compatible).
>
>
>Updated files:
>trunk/reactos/boot/freeldr/freeldr/arch/i386/mb.S
>trunk/reactos/boot/freeldr/freeldr/multiboot.c
>trunk/reactos/ntoskrnl/mm/i386/page.c
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
>
>
Hi,
on windows the hyperspace area is always 4MB. If you change the size you
have also to change the mapping and initialisation functions.
- Hartmut
1) Task manager displays closed / killed software too. Maybe it cannot
kill software? Runned software window disappears but in task manager it
on runned application list. There's no info about this software in
process tab.
2) In browse window I cannot enter in folders. System want to change its
name when I double click on it.
3) In Task Manager there's 2x Windows posision in menu (sometimes).