Ros-dev

ros-dev@reactos.org

5788 discussions

by Dmitriy Budko

Reactos can be ported to VMI instead: http://www.vmware.com/interfaces/vmi_specs.html http://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.

18 years, 2 months

Re: [ros-dev] [ros-diffs] [fireball] 23005: [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 addin

by Alex Ionescu

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

18 years, 2 months

Re: [ros-dev] 0.3.0 RC1 Update

by Murphy, Ged (Bolton)

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.

18 years, 2 months

Re: [ros-dev] 0.3.0 RC1 Update

by Murphy, Ged (Bolton)

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.

18 years, 2 months

Status report on Remote Desktop client - with screenshots!

by Michele Cicciotti

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!

18 years, 2 months

0 lines patch

by Timo Kreuzer

| \|/ 22802 <http://www.anonymizer.ru/cgi-bin/webproxy?session=demo&url=http://svn.react…> trunk/reactos/subsystems/win32/csrss/win32csr/ <http://www.anonymizer.ru/cgi-bin/webproxy?session=demo&url=http://svn.react…> resource.h <http://www.anonymizer.ru/cgi-bin/webproxy?session=demo&url=http://svn.react…> 0/0 <http://www.anonymizer.ru/cgi-bin/webproxy?session=demo&url=http://svn.react…> Mon Jul 3 19:59:50 2006 UTC greatlrd *Log:* wrong propyty on inlcude file it is not a executable format Looks like this patch got lost somewhere...

18 years, 2 months

Re: [ros-dev] Hello list!

by Michele Cicciotti

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!

18 years, 2 months

Hello list!

by Michele Cicciotti

I thought I might share my current progress on my Google Summer of Code project with this lovely project... Briefly, I don't have a lot of code but, I believe, a pretty solid design & a well laid down plan. Here is a writeup I have made about it on my PlanetSoC 2006 blog: <http://2006.planet-soc.com/node/361> It's quite long, so I hope you understand why this here post is so short :-) I'd love any kind of comment on it See you all soon(er)!

18 years, 2 months

Status of xen port?

by Pablo Menichini

Hi, 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? Thanks, Pablo

18 years, 2 months

Must read for all ReactOS devs: Status Report requests

by Aleksey Bragin

Hello, in the process of writing a ReactOS quarterly Status Report, I need every ReactOS Developer (with some exceptions to passive developers too) to write me a private email, stating what they have been doing recently, what they plan to do in near future (near future == 6 months), and what did you achieve from the last status report (january 1st) -- I suppose this will be your favorite section, because it actually gives every developer a chance to show his most prominent work, and make others be proud of it. These emails must be sent as soon as possible, but preferably not later than Wednesday, 5th of July, 2006. If you are really late and did not warn me, you risk not being included into this issue of Status Report. Thank you, With the best regards, Aleksey Bragin ReactOS Project Coordinator

18 years, 2 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev