Ros-general October 2005

ros-general@reactos.org

50 participants
86 discussions

by jwalsh＠bigpond.net.au

Thank you Casper. In a nutshell ! ! I only wish I could have put it so succinctly. The problem with ros at the moment (and it is not life threatening) is: There is no space set aside for private discussion, but which, at the same times allows for returning to the ros-general thread again. Because of that (design failure not code failure), we all stay in the ros-general public space and argue over the top of one another. Sometimes it seems like the floor of the NYSE, where people must waive and shout to get attention to their particular issue. Good fun for some but agony for others. Regards and rosuccess Justin ---- Casper Hornstrup <ch(a)csh-consult.dk> wrote: > You have to know when to use it. I think we do okay in that area. > We have assembler optimized versions of string functions which are > often executed during operation, but we also have C versions of > these functions to make ReactOS easier to port to new architectures. > We have assembler code for very low-level code which would be > impossible to do in C. I believe there should be a minimum of > assembly used to increase maintainability/portability and when used, > it should be because there is a major speed difference during > _normal operation_ of the OS. If a function which is called only > once during startup of the OS could be made 1ns faster using > assembly, then it doesn't really make ReactOS feel faster to the > user even though running the function 10000 times in a loop might > show a 1000% average speed increase. If the function was run 1000 > times a second during normal operation then the user might feel > a difference. There are other ways to make ReactOS faster than > resorting to assembly. You could use better algorithms for > instance. > > Casper > > > -----Original Message----- > > From: ros-general-bounces(a)reactos.org [mailto:ros-general-bounces@reactos.org] On Behalf Of Kevin > > Lawton > > Sent: 18. oktober 2005 10:30 > > To: ReactOS General List > > Subject: RE: [ros-general] New to ReactOS > > > > Yeah, okay, but . . . > > With C being a 'higher level' language than assembler it will always be > > easier for a group of humans to work on a project in. You could take this > > further and use something like Java, though not for an op-system kernel as > > Java programs need something below them to run the run-time virtual machine. > > C is a good language for writing an op system in because that is why it was > > designed (by Kerningham and Ritchie - their book on C is still the best work > > of its kind). It was created to write the Unix op system in and the > > combination of high and low-level features will always make it ideal for > > such a task. In terms of generating nice tight machine code when compiled, C > > is probably the best high-level language in this respect. > > Modern computers are so enormously powerful that most projects feel that it > > is unnecessary to use assembler for the extreme efficiency it offers - C is > > more than 'good enough'. But, when projects ARE written for modern machines > > using assembler we then start to see just how fast things can go. We might > > feel that the 'average' PC is plenty fast enough performing day-to-day tasks > > with an op system written in C and applications in Java or VB, and it > > probably is, but give it a chance to run software written in good assembler > > and you can get quite a surprise. Even if we think we can spare it, those > > high-level language programs (incl op system) can perform nothing like the > > blistering performance you can get from really good assembler code. You also > > find that because assembler programming is so 'direct' then the resulting > > machine code tends to be far more compact than that generated from other > > languages. Smaller programs (op systems included) use less room on disk, > > load faster into a smaller memory space and tend to have shorter execution > > paths. > > It is all fine and dandy that ReactOS will be a working 'clone' of Windows > > but Windows is often criticised for being large and slow. What if ReactOS > > could achieve full Windows compatibility while being much smaller and faster > > ? > > Kevin. > > _______________________________________________ > ros-general mailing list > ros-general(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-general

18 years, 11 months

RE: [ros-general] New to ReactOS

by Murphy, Ged (Bolton)

jwalsh(a)bigpond.net.au wrote: > Who uses assembler for serious anything these days? <snip> > If anybody from ros is really in need of assembler then something is sus. Considering you can't build ROS without an assembler, something must be sus. If you look at the ReactOS kernel, you will find many asm files. My point was that the vast majority is written in C and is generally preferred. 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

18 years, 11 months

On Assembly Language [Re: [ros-general] New to ReactOS]

by jwalsh＠bigpond.net.au

In retrospect there is one important area for the Assembly Language Programmer. It would only be interesting to the serious enthusiast. It is writing primitives for very tight Smalltalk. It is the area of embedded systems. Owing to a buggys Windows98se I cannot send attachments (indirectly a good thing). An Example is below. Regards and rosuccess ---- Redefined Horizons <redefined.horizons(a)gmail.com> wrote: > Wow! Great news! > Now let me ask about volunteering to help with the project. I'd like to get > some experience programming in assembly language and/or machine code. > Is there any need for this on the ReactOS project? Can I start on some > simple assembly language programming tasks for ReactOS and have someone that > can guide me through the tough spots? > Let me know if I can help in this area. > Scott > > On 10/17/05, KJKHyperion <hackbunny(a)reactos.com> wrote: > > > > Redefined Horizons wrote: > > > > > [1] Is ReactOS built on a Unix core, or is it a new operating > > > sytem from the ground up? > > > > ReactOS is all-original, written from the ground up as a clone of the > > Windows design > > > > > [2] Can you dual boot with ReactOS and a Linux operating system like > > > Debian? If you can, is there a place where I can find instructions on > > > how to do so? > > > > yes, see > > <http://www.reactos.org/wiki/index.php/HOWTO/boot_FreeLoader_from_GRUB> > > > > > [3] Does an application that runs on Microsoft Windows have to be > > > ported before it can be run on ReactOS? > > > > No > > > > > Can I try installing the program to see how it works? > > > > Yes > > _______________________________________________ > > ros-general mailing list > > ros-general(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-general > > ------------------------------------------------------------------------------- PAGE 85,132 TITLE User Defined Primitive #92 (INT 62H) ; This is an example of a possible user defined primitive. ; The primitive below "primitive92" is an implementation ; of the String at: primitive. ; ; The first part of the code "installs" the primitive ; "segment and offset" address into INT 62H vector. ; The second part, "primitive92" defines the code that ; will be executed when primitive number 92 from ; "Smalltalk/V" is invoked. PAGE INCLUDE fixdptrs.usr IF1 INCLUDE access.usr ENDIF PAGE code SEGMENT ASSUME CS:code,DS:code,ES:code ORG 100H start: JMP installPrim PAGE primitive92 PROC FAR ; This is code that will be executed everytime primitive ; number 92 is invoked from "Smalltalk/V" enterPrimitive ;enter primitive macro (see macro ;listings) MOV CX,DI ;copy receiver in CX ; getClass DI,DX,ES ;put class of receiver in DX ; ; CMP DX,ClassStringPtr ;if class of receiver is not ; JNE failure ;String then primitive fails ; ;(This check is commnet since it is ; ;not necessary but it is shown here ; ;as an example on how to use the ; ;getClass macro MOV DI,[BP+16] ;put index argument in DI SHR DI,1 ;shift right and MOV AX,DI ;copy in AX JNC smallInt ;if no carry (even number) then RCL DI,1 ;its a small integer and jump else ;restore the index object ptr MOV DX,SS ;set ES to address classes segment SHR DX,1 MOV ES,DX CMP WORD PTR ES:[DI],ClassLargePosInt ;if class of index object JNE failure ;pointer is LargePositiveInteger ;then continue else primitive fails getObjectAddress DI,BX,ES ;get address of index object ptr CMP WORD PTR ES:[BX],4 ;size of this large positive JNE failure ;integer must be 4 (2 bytes for ;size header + 2 bytes for the ;number itself) - not 4 suggests ;that number is more than 2 bytes ;long and primitive fails else MOV AX,ES:[BX+2] ;move 2 byte integer into AX and JMP haveIndex ;jump to haveIndex smallInt: JLE failure ;if after shift sign of integer ;changes or its zero then ;primitive fails (index must be ;greater than zero) haveIndex: INC AX ;index +1 to correct byte access JZ failure ;later on; if value goes to 0 then ;index was too large and primitive ;fails MOV BX,CX ;set BX to receiver object ptr and getObjectAddress BX,DI,ES ;get address of receiver (string) isSizeEven BX,CX,DS ;check even/odd length of string ;object (JZ for even length) MOV BX,ES:[DI] ;move size of string to BX JZ even ;if isSizeEven result is zero DEC BX ;condition flag then length ;of string is even (BX - 2 bytes ;for size header) else length of ;string is odd (BX - 3) so adjust ;size of string (BX) by -1 even: CMP AX,BX ;adjusted index must be less than JAE failure ;BX (string size) else primitive ;fails ;now we must get the character ;from the string and turn it into ;an object pointer XOR CH,CH ;set CH to zero MOV BX,AX ;set BX to be adjusted index MOV CL,ES:[DI+BX] ;move to CL the char from string SHL CX,1 ;multiply CX by 2 ADD CX,FirstCharacterPtr ;add to CX the base character ptr MOV BX,CX ;set BX to result char pointer exitWithSuccess 1 ;and enter into successful exit ;macro with arg count 1 (the index) failure: exitWithFailure 1 ;failure macro with arg count 1 primitive92 ENDP primitive92end LABEL BYTE ;label for exit and stay resident ; This is primitive "installation code" with the exit and ; stay resident installPrim PROC NEAR MOV AX,CS ;set DS to address code segment MOV DS,AX MOV DX,OFFSET primitive92 ;load DX with primitive offset MOV AX,2562H ;use DOS to set address of INT 62H INT 21H LEA DX,primitive92end ;load DX with address beyond last INT 27H ;byte - exit and stay resident installPrim ENDP SUBTTL PAGE code ENDS END start

18 years, 11 months

Re: [ros-general] Wait a second...

by jwalsh＠bigpond.net.au

Since this is still [ros-general], emphasis on "general": When I first saw your ros home page I was very impressed with the amount of effort which must have gone into it. There were some errors but tolerable. Some of the loose references to ros being "buggy" is not helpfull either. Preserving the Windows "buggyness" is a little too extreme. I imagined that a lot of money must have secured ros the top system designers. Amazing that it has all been done on "the smell of and oil rag". Congratulations !. I also thought that focussing on some obvious (to us) mistakes would be "nit picking". However it is now becoming a serious issue, which I feel can be addressed by a few simple "adjustments". Perhaps I'm overreacting. But, falling back on regulation is throwing good energy after bad. I don't see that it is necessary. Is it appropriate to discuss it here? As for this: > > Just code, don't talk works fine...when you are a two people project. I would suggest they retire to minGW-Msys where they can talk code "until the cows come home" and be gently diciplined by Earnie Boyd, its a great list. Then maybe [ros-general] can stay as it is "general". Regards and rosuccess Justin ---- K McI <uniq(a)wwsvr.bounceme.net> wrote: > Casper Hornstrup wrote: > > Just code, don't talk works fine...when you are a two people project. > > I agree exactly. Governments have constitutions to prevent seizures of > or misallocation of power, or worse, total inaction do to fear of those > things. Projects have them to prevent infighting (As I recently noticed > on another, different project) and the above. > > Also, that rule applies best when there are few, well known and trusted > people in a project and little major outside knowledge or information > because it assumes everyone is trustworthy and there's no inclination to > duplicity or malice. > > The new site seems to have elevated ROS a new level, most especially now > that BugZilla is usable, things are definitely moving faster. IMAO, I > suggest this be done (However), if for nothing else then to hopefully > preclude the recent vote-fights I've been seeing on the ML. > > Thanx, > > -uQ > _______________________________________________ > ros-general mailing list > ros-general(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-general

18 years, 11 months

Re: [ros-general] Wait a second...

by jwalsh＠bigpond.net.au

Since this is still [ros-general], emphasis on "general": When I first saw your ros home page I was very impressed with the amount of effort which must have gone into it. There were some errors but tolerable. Some of the loose references to ros being "buggy" is not helpfull either. Preserving the Windows "buggyness" is a little too extreme. I imagined that a lot of money must have secured ros the top system designers. Amazing that it has all been done on "the smell of and oil rag". Congratulations !. I also thought that focussing on some obvious (to us) mistakes would be "nit picking". However it is now becoming a serious issue, which I feel can be addressed by a few simple "adjustments". Perhaps I'm overreacting. But, falling back on regulation is throwing good energy after bad. I don't see that it is necessary. Is it appropriate to discuss it here? As for this: > > Just code, don't talk works fine...when you are a two people project. I would suggest they retire to minGW-Msys where they can talk code "until the cows come home" and be gently diciplined by Earnie Boyd, its a great list. Then maybe [ros-general] can stay as it is "general". Regards and rosuccess Justin Justin ---- K McI <uniq(a)wwsvr.bounceme.net> wrote: > Casper Hornstrup wrote: > > Just code, don't talk works fine...when you are a two people project. > > I agree exactly. Governments have constitutions to prevent seizures of > or misallocation of power, or worse, total inaction do to fear of those > things. Projects have them to prevent infighting (As I recently noticed > on another, different project) and the above. > > Also, that rule applies best when there are few, well known and trusted > people in a project and little major outside knowledge or information > because it assumes everyone is trustworthy and there's no inclination to > duplicity or malice. > > The new site seems to have elevated ROS a new level, most especially now > that BugZilla is usable, things are definitely moving faster. IMAO, I > suggest this be done (However), if for nothing else then to hopefully > preclude the recent vote-fights I've been seeing on the ML. > > Thanx, > > -uQ > _______________________________________________ > ros-general mailing list > ros-general(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-general

18 years, 11 months

New to ReactOS

by Redefined Horizons

I have just migrated from Windows to Linux, and I am very curious about ReactOS. I have a couple of newbie questions I was hoping I could get answered. (I have already checked the developer and user FAQs on the ReactOS website.) [1] Is ReactOS built on a Unix core, or is it a new operating sytem from the ground up? [2] Can you dual boot with ReactOS and a Linux operating system like Debian? If you can, is there a place where I can find instructions on how to do so? [3] Does an application that runs on Microsoft Windows have to be ported before it can be run on ReactOS? Can I try installing the program to see how it works? Thanks, Scott Huey

18 years, 11 months

Re: [ros-general] Wait a second...

by Tim Jobling

I chime in even less than Richard, but I have to say I whole heartedly agree with his sentiment. Perhaps we should take a lesson from the early history of this project and get back to letting the code talk for it's self. Reactos started at with an "emphasis on results -- on written code rather than endless talk". Famous words, I'm sure we have all read 100 times, but now seems like a really good time to remind everyone of them. Kind regards, Tim Jobling ----- Original Message ----- From: "Richard Campbell" <eek2121(a)comcast.net> To: "ReactOS General List" <ros-general(a)reactos.org> Sent: Sunday, October 16, 2005 6:49 PM Subject: [ros-general] Wait a second... > Now, i've been reading the lists the past few days...I may chime in from > time to time with my thoughts here and there, but for the most part i've > tried to keep my mouth shut. > > Lately however, there has been so much bickering going on. Every thread > has been turning into a flame war. Several developers have left, are > threatening to leave. I think everyone needs to CHILL OUT for a moment. > > There is so much argument over who should be doing what, what their > rights should be, etc. There is no sense in this. ReactOS is supposed > to be a fun project, yet suddenly we are caught up in politics. We > really need to find a better way of doing this. Flaming each other, > getting mad, threatening to, or in some cases leaving the project is NOT > the right thing to do. What will end up happening is that the project > will slowly fade away into obscurity, and I for one do not want this to > happen. > > While I don't have any recommendations as to how to do this, i do think > that there is a solution, and i will be thinking about this over the > next few hours/days. > > Regards, > Richard ___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com

18 years, 11 months

Re: [ros-dev] Gudie Lines for SVN Write access

by Magnus Olsen

My point is we starting getting alot of people, and yes the currenct rules works but not for long. we are now lest 35 people with commit access. And we need a system how u getting svn access it must be bit harder getting svn write access. 1. I know we got bugzlla, I wrote Bugzila or mailing list 2. A patch need always be tested and exaim before it been accpect I can not count how many time this year I got bad patcher from people and I need test the code, I got some patcher that doing BSOD in some case. Yes U need always test and examin the patcher from people that does not have svn write access. 3. Not with the time. we are goving alot. We need start thing about futer so we do not land up with example over 100 commicters. Yes it should be good with full name and commit name on reactos website some where. So public can get know how is how. I still stand we need these gudlines I worte. ----- Original Message ----- From: Casper Hornstrup To: 'ReactOS Development List' Sent: den 16 October 2005 00:26 Subject: RE: [ros-dev] Gudie Lines for SVN Write access 1.. We have a Patches component in Bugzilla for this. 2.. The committer should do minimal testing even if he didn't create the patch. At least check that ReactOS can still be built and boot. 3.. It is enough to have a well-known committer recommend you get repository access. This is usually the person that has committed most of your patches. I see no reason for this to change since it is simple and works quite well. I can maintain a page in wiki containing full name and username of each committer if needed. Btw. Christoph von Wittich has posted to the mailing list several times. Casper ------------------------------------------------------------------------------ From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Magnus Olsen Sent: 16. oktober 2005 00:01 To: ReactOS General List; ReactOS Development List Subject: [ros-dev] Gudie Lines for SVN Write access Hi I should love to see some new gudieles how to get svn access. Today it seam anyone that provide with a patch that is coder can getting svn access. But I think we need start think how we should handle it, Here is some ideas how it can be 1. A maling list with patch or in Bugzila I love see a maling list with the patch 2. When people have submit the patch to us we start examing it see if it any godd (we are doning that already) 3. To get SVN write access u need lest provide patch in regual basic under 6 month lest, Then after 6 month the provider can write to mailing list see if can getting SVN write access before he grant SVN write access, the full name and mailing address must be provided, and we should have a vote if that provder can getting SVN write access. no accpect from all this rules. Yestday some was granted svn access his name was not on the mailing list why he got one, he did not write either on the mailing list asking for svn access that why I want see new guide lines how svn write access handles. so every one know how he is and why he was granted to be granted after few patcher are not accpect in my eys. For we are starting getting alot with people with svn write access. And new guide lines must be create. BestReagds Magnus Olsen ------------------------------------------------------------------------------ _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev ------------------------------------------------------------------------------ No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.12.0/134 - Release Date: 2005-10-14

18 years, 11 months

RE: [ros-general] Wait a second...

by jwalsh＠bigpond.net.au

A constitution is a set of rules: do's and don'ts. Is that what you want? It is a regulatory mechanism to control behaviour. It sits between Law ands no Law at all. It is a formality commonly associated with corporations. So far I don't see any reason for current behaviour to change. Your founding principles seem quite sound to me. Why the panic? Perhaps your current Strategic Plan could be a bit more flexible. But there are all sorts of sub-forums which can deal with superficial issues. I suggest a cool down period, and agreement to disagree on particulars only. But never a compromise on principle: they are either right or wrong. If a better principle emerges then drop the old one and take on the new. Otherwise let the opponents prove their point. Earnie Boyd at MinGW-Msys is a good example of control by principle. Regards and rosuccess Justin ---- Casper Hornstrup <ch(a)csh-consult.dk> wrote: > Just code, don't talk works fine...when you are a two people project. > > ReactOS isn't a two people project anymore. We need a fair way to > settle disagreements and we need a way to remember the decisions > we make. Fair meaning that everyone has equal opportunity to > influence the decision. We need a constitution. > > Casper > > > -----Original Message----- > > From: ros-general-bounces(a)reactos.org [mailto:ros-general-bounces@reactos.org] On Behalf Of Tim > > Jobling > > Sent: 16. oktober 2005 22:55 > > To: ros-general(a)reactos.org > > Subject: Re: [ros-general] Wait a second... > > > > I chime in even less than Richard, but I have to say I > > whole heartedly agree with his sentiment. > > > > Perhaps we should take a lesson from the early history > > of this project and get back to letting the code talk > > for it's self. > > > > Reactos started at with an "emphasis on results -- on > > written code rather than endless talk". Famous words, > > I'm sure we have all read 100 times, but now seems > > like a really good time to remind everyone of them. > > > > Kind regards, > > Tim Jobling > > > > _______________________________________________ > ros-general mailing list > ros-general(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-general

18 years, 11 months

Re: [ros-general] Wait a second...

by jwalsh＠bigpond.net.au

Sorry, Wesley. But all Maxims (an adage is merely that) of behaviour, good or bad, are unreliable. They are mostly to be found on desk calendars or on fridge doors. I call them Fridge Magnetisms. Whatsmore they can never be taken as Law; they actually contradict the term Law. Such adages can, under certain conditions, even be utter nonsense like: WYSIWYG, "The best way to predict the future is to invent it", "Power comes from the barrel of a gun", "suck it and See". Or be quite sensible like: Keep It Sweet and Simple", "what goes up must come down". However I do agree that delivering something to argue over is better than empty theory. So please keep making your point. Both sense and nonsense are necessary (necessety ~ law) part of our human makeup. They must live together: but in two houses with a tall fence between. Why not then, create two categories of ros-general according to the law of: Theory and Practice. Perhaps it already exists? An old man like me does not want to spend the rest of his life arguing with the young, but merely be nearby to lend a bit of advice now and again (behind a tall fence). For what it is worth. Regards and rosucceed Justin ---- Wesley Parish <wes.parish(a)paradise.net.nz> wrote: > Remember that adage of the Free and Open Source community? "Code is Law"? > > Meaning that arguing's not anything worth near as much as a good file of code. > > Just my 0.02c (inflation - it's obvious ;) > > Wesley Parish > > On Mon, 17 Oct 2005 10:03, TwoTailedFox wrote: > > I had exactly the same thought, Tim. > > > > Maybe that should be the 'ReactOS Motto'? > > > > On 10/16/05, Tim Jobling <tjob800(a)yahoo.co.uk> wrote: > > > I chime in even less than Richard, but I have to say I > > > whole heartedly agree with his sentiment. > > > > > > Perhaps we should take a lesson from the early history > > > of this project and get back to letting the code talk > > > for it's self. > > > > > > Reactos started at with an "emphasis on results -- on > > > written code rather than endless talk". Famous words, > > > I'm sure we have all read 100 times, but now seems > > > like a really good time to remind everyone of them. > > > > > > Kind regards, > > > Tim Jobling > > > > > > ----- Original Message ----- > > > From: "Richard Campbell" <eek2121(a)comcast.net> > > > To: "ReactOS General List" <ros-general(a)reactos.org> > > > Sent: Sunday, October 16, 2005 6:49 PM > > > Subject: [ros-general] Wait a second... > > > > > > > Now, i've been reading the lists the past few > > > > > > days...I may chime in from > > > > > > > time to time with my thoughts here and there, but > > > > > > for the most part i've > > > > > > > tried to keep my mouth shut. > > > > > > > > Lately however, there has been so much bickering > > > > > > going on. Every thread > > > > > > > has been turning into a flame war. Several > > > > > > developers have left, are > > > > > > > threatening to leave. I think everyone needs to > > > > > > CHILL OUT for a moment. > > > > > > > There is so much argument over who should be doing > > > > > > what, what their > > > > > > > rights should be, etc. There is no sense in this. > > > > > > ReactOS is supposed > > > > > > > to be a fun project, yet suddenly we are caught up > > > > > > in politics. We > > > > > > > really need to find a better way of doing this. > > > > > > Flaming each other, > > > > > > > getting mad, threatening to, or in some cases > > > > > > leaving the project is NOT > > > > > > > the right thing to do. What will end up happening > > > > > > is that the project > > > > > > > will slowly fade away into obscurity, and I for one > > > > > > do not want this to > > > > > > > happen. > > > > > > > > While I don't have any recommendations as to how to > > > > > > do this, i do think > > > > > > > that there is a solution, and i will be thinking > > > > > > about this over the > > > > > > > next few hours/days. > > > > > > > > Regards, > > > > Richard > > > > > > ___________________________________________________________ > > > Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with > > > voicemail http://uk.messenger.yahoo.com > > > _______________________________________________ > > > ros-general mailing list > > > ros-general(a)reactos.org > > > http://www.reactos.org/mailman/listinfo/ros-general > > > > -- > > "I had a handle on life, but then it broke" > > > > _______________________________________________ > > ros-general mailing list > > ros-general(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-general > > -- > Clinersterton beademung, with all of love - RIP James Blish > ----- > Mau e ki, he aha te mea nui? > You ask, what is the most important thing? > Maku e ki, he tangata, he tangata, he tangata. > I reply, it is people, it is people, it is people. > _______________________________________________ > ros-general mailing list > ros-general(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-general

18 years, 11 months

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Ros-general October 2005