WaxDragon wrote:
> The only bug
> I'm concerned about right now is the broken links in the start menu,
> which I think is even fixed in trunk. Nothing else can really be
> addressed at this point.
That is easily fixed with a small hack in the explorer code.
It's certainly not a correct fix, but it will ensure the links work for this
release and allow us to move on.
If you agree, I'll change it tonight.
Ged.
Dear ReactOS Developers,
I apologize for taking these extra ordinary steps in this matter but I
could not locate another way of bringing this issue to attention on your
site.
I was in the IRC channel on the 11th July '06 from about 3am to 5am
GMT... I was posing some very interesting and fundamental questions
about how the project began, it's direction. I was pleased that after a
few minutes most of the users had agreed that ReactOS is intending to be
much more than just NT compatible but in a sense 'Windows + Better'.
After this there was many hours of discussion of how to make it more
than just a windows clone, many of such involving the idea of ReactOS
being similar to Linux in some senses and how to get a Linux feel while
maintaining windows compatibility.
Near the end of the log (I hope these are saved, I have no copies
myself) an 'Alex_Ionescu' joined in on the conversation. He had many
interesting views that greatly heightened the debate to whether ReactOS
should intend to be more than windows now, or at a later date. I was
for the view that in order to gain a user base quicker that it must at
least intent to be more than a clone and was trying to illustrate why.
I first tried to illustrate this and got shot down due to my poor
phrasing of what I meant.
I tried to rephrase my point, and I began with a sentence talking about
firefox as a metaphor of another great piece of floss software. I was
interrupted by Alex_Ionescu (whom is an op in that channel) who told me
i 'must' state my reason using a single statement only and began quoting
regulations of the English language and structuring a proper argument...
so many regulations in fact i feel even if I did comply it would be
difficult to fit it in one statement.
I decided to wait until Alex_Ionescu had given up on such a silly and
clear attempt at limiting my free speech in this matter. However he
persisted to want to know what my point was on this matter, when trying
again... he shut me down. Eventually he set the entire channel to
moderated status only so only those he selected could discuss the
matter. Apparently this was until I could phrase my argument using just
one statement.
I waited until this was lifted and it was not, eventually I came back...
spoke Spanish and under another nick! Granted this was to yet again
give my point across... instead of this they knew who I was and quickly
identified me. A silly tactic I know, but having done this I was
quickly misquoted in the channel from my conversation with Alex_Ionescu
about things I was trying to explain to him as well as very childish
remarks as tho I had said "I love cock". I have high hopes for this
project and wish it every success, I had a very enlightened experience
up until meeting this person with the arguments put and listened and
responded to them well. Alex_Ionescu on the other hand obviously has no
understanding of what it means to express oneself freely, and it would
seem has a childish nature too.
I ask that the decision to give this person power of the level of
communication about the project in the channel be reviewed as quickly as
possible in light of these or other past events.
Thank you,
--
Steven Maddox
(Cyorxamp)
Cyorxamp
http://www.cyorxamp.info
Reactos can be ported to VMI instead:
http://www.vmware.com/interfaces/vmi_specs.htmlhttp://www.vmware.com/pdf/vmi_specs.pdf
It will allow reactos to switch between VMI and native HW on the fly.
Dmitriy Budko
VMware
________________________________
From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] On
Behalf Of Jerry
Sent: Saturday, July 08, 2006 11:54 AM
To: ReactOS Development List
Subject: Re: [ros-dev] Status of xen port?
Can reactos be made to run on Xen or native hardware by detecting either one
on the fly?
Steven Edwards wrote:
On 7/7/06, Pablo Menichini <pablo(a)menichini.com.ar>
<mailto:pablo@menichini.com.ar> wrote:
I look at xen port and it hasn't been touch in a year. Is it possible
to
port reactos to xen or is the kernel not mature enought? If it's
possible, how long can it take to have a bare minimum port?
Its possible there has just been a lack of developer resources. One of
the developers had the boot loader ported however those changes were
not merged in to the trunk.
fireball(a)svn.reactos.org wrote:
> Author: fireball
> Date: Tue Jul 11 01:03:26 2006
> New Revision: 23005
>
> URL: http://svn.reactos.org/svn/reactos?rev=23005&view=rev
> Log:
> [FORMATTING] / [AUDIT]
> - Cleanup a big coding-style mess
> - Add UNIMPLEMENTED macro in empty functions (otherwise we will never know if they are being called by a 3rd-party driver)
> - Add proper debug headers inclusion in every file
> - Add documentation headers into almost every file (except mcb.c and context.c - will be added later)
> - Standardize per-file headers (some files still lack contributors names, they will be added later too)
>
> No code change except for adding UNIMPLEMENTED macros in the code. Name.c unlocked because the implementations of functions are trivial and in fact could be derived from their names. Not documented functions will be further reviewed.
>
Good work... two things:
1) I think Brandon wrote a tool which does documentation headers using
TinyKRNL syntax. Since ROS's is the same (afaik), maybe you could talk
to him about it instead of doing everything by hand :).
2) Most of the functions are documented in te IFS, I'm not aware of any
undocumented FsRtl stuff... Captive also has implementations for nearly
all of them, and Captive was clean-roomed.
Best regards,
Alex Ionescu
Brandon Turner wrote:
> I have added a debug bootcd build of RC1 to sourceforge.
> So anyone out there looking to get there hands one for
> troubleshooting 0.3.0 can hop on there and grab it.
We've had this up for 3 weeks now.
Changes to trunk have been so heavy since we branched 0.3, we effectively
now have two _very_ different versions of ReactOS .... heh
Maybe our release process needs reviewing slightly ;)
Ged.
Brandon Turner wrote:
> Perhaps I am
> mistaken on the process and missed the time I should have
> made another
> release. If this is the case please feel free to let me know
> what I can
> do to resolve the the problem.
>
> Brandon
No no, nothing has gone wrong, I was just making an observation and putting
some traffic on ros-dev ;)
IIRC, a 2 month release cycle has been mentioned in the past.
Going off our recent release speed, we'd struggle to hit 1 per year ;)
At least we know ROS development is moving fast internally, even if releases
aren't.
Ged.
I opted for a different porting strategy than I originally thought. I
simply couldn't work effectively outside of Visual Studio, so I decided
to create a test application (rdesktop-core-tester), and turn the
smallest subset possible of rdesktop into a statically-linked library
(rdesktop-core). It needs a lot more work, but the results are very
encouraging
Here is the first screenshot *ever* of rdesktop running on pure Win32:
<http://img209.imageshack.us/my.php?image=whohoo3ts.png>
What's wrong with this picture, and why? All text is missing: text
output in RDP is tedious. I'll rip the code off from the X11 version,
but it's not vital for now. All bitmaps are black: this is a bug, or
rather a peculiarity, of rdesktop, which passes only part of raster
operation codes (specifically, the "source" mask), forcing me to do some
bit-juggling to turn them back into valid GDI raster operation codes -
just passing the "mutilated" code resulted in the code for the BLACKNESS
operation every time, and I think it shows. "Shut down..." is upside
down: this is a bitmap painted directly to the screen, without a raster
operation, so it worked out of the box, unlike the Windows logo in the
upper half of the dialog. It turns out RDP bitmaps are top-down, like
the framebuffer but unlike regular bitmaps. Easily solved by creating
all bitmaps with negative heights!
Also, I could not go further than this point at the time, because
keyboard input wasn't hooked up yet! I whipped up some quick support
(very easy, just pass the scancodes on the wire), and of course fixed
the aforementioned issues, tweaked a couple more things, blind-typed the
password (no text output) and...
<http://img62.imageshack.us/my.php?image=meh9ct.png>
... eh. I expected a lot better. So many bugs. And I really don't
understand why the strange "tile" effect... debugging drawing routines
is a pain, let me tell you. I would love to have a night-time bug-hunt,
but I have some *terrible* back pain, and it's becoming really hard to
sit at my desk
All in all, I must say I'm a bit disappointed that the rdesktop authors,
who in general stayed true to the Win32 equivalents of RDP features,
here and there placed annoying little idiosyncracies - like mutilating
rasterops, or using their own structures instead of the "standard"
LOGPEN, LOGBRUSH, etc. or calculating and passing around coordinates of
left-top + dimensions when they're actually RECTs on the wire, forcing
me to recalculate the RECT, and so on, and so on - that I *know* are
going to cause me headaches in the days to come (the off-by-one-pixel
bug must be caused by something like that)
Well, that's all for this week! see you soon!
Aleksey Bragin wrote:
> thanks for sharing, we appreciate more often and better communication
> with our SoC participants.
sorry for the long periods of silence, but I'm currently without
internet connectivity outside of weekends. It should go a lot better
starting next week!