Estaré fuera de la oficina hasta el 21-02-2012 En casos urgentes, ruego reenvíe su e-mail a Luis Garcia, luis.garcia(a)vaix.com.ar
Gracias y disculpe las molestias que mi ausencia pueda ocasionarle.
Saludos cordiales,
---
Lic. Julián Talin | IT Manager | VAIX Argentina |
0810 345 VAIX (8249) int. 104
Tte. Gral. J. D. Perón 1671 piso: 5 depto: A
C1037ACE - Cdad. Autónoma de Buenos Aires
http://www.vaix.com.ar
?-------------------------------------------------------------------------------------------------------------------------------
I will be out of the office until 21-02-2012 In urgent cases please forward your e-mail to Luis Garcia, luis.garcia(a)vaix.com.ar
Thank you and sorry for any inconvenience my absence may cause you.
Best regards,
---
Lic. Julián Talin | IT Manager | VAIX Argentina |
0810 345 VAIX (8249) int. 104
Tte. Gral. J. D. Perón 1671 piso: 5 depto: A
C1037ACE - Cdad. Autónoma de Buenos Aires
http://www.vaix.com.ar
Estaré fuera de la oficina hasta el 21-02-2012 En casos urgentes, ruego reenvíe su e-mail a Luis Garcia, luis.garcia(a)vaix.com.ar
Gracias y disculpe las molestias que mi ausencia pueda ocasionarle.
Saludos cordiales,
---
Lic. Julián Talin | IT Manager | VAIX Argentina |
0810 345 VAIX (8249) int. 104
Tte. Gral. J. D. Perón 1671 piso: 5 depto: A
C1037ACE - Cdad. Autónoma de Buenos Aires
http://www.vaix.com.ar
?-------------------------------------------------------------------------------------------------------------------------------
I will be out of the office until 21-02-2012 In urgent cases please forward your e-mail to Luis Garcia, luis.garcia(a)vaix.com.ar
Thank you and sorry for any inconvenience my absence may cause you.
Best regards,
---
Lic. Julián Talin | IT Manager | VAIX Argentina |
0810 345 VAIX (8249) int. 104
Tte. Gral. J. D. Perón 1671 piso: 5 depto: A
C1037ACE - Cdad. Autónoma de Buenos Aires
http://www.vaix.com.ar
Hello!
We are asking you for some help from the Open Source communities.
As researchers at the University of Tennessee we are interested in
discovering more about learning and interactions of members of the open
source forums. This research is conducted through the University of
Tennessee and is in no way associated with any forum organization. To
further our research we would like input from forum members. The responses
are very important to us so we can better understand what tools help forum
members learn and have a productive experience in participation.
To help: Take a survey about the tools you use in the forum.
We are requesting approximately 15 minutes of your time to participate in
our survey.
Survey link: http://survey.utk.edu/mrIWeb/mrIWeb.dll?I.Project=FORUMLEARN
*As a thank you, upon exiting the survey you will be given an opportunity to
submit information to be entered in a drawing for a tablet computer ($500.00
Gift Card). *
Please be assured that your answers will be confidential. No individual’s
answers will ever be identified in any report. Should you have any questions
about the project or our interest in using the results, we encourage you to
contact Lila Holt, at lholt(a)utk.edu) or Vandana Singh at vandana(a)utk.edu.
Contact information you provide for the drawing is completely separate from
your survey answers and there will be no way to identify participants in the
actual survey responses. Nor will contact information be used for any other
purpose. The odds of being selected will depend on the number of respondents
to this survey.
Hello
I tried ReactOS in Vmware and liked very much what I saw. Only the
installation of latest Firefox freezes (through Applications Manager).
Can I install ReactOS on Acer Aspire One as a non-developer? Are there
wireless drivers? How is the battery life?
Dennis
hi,everyone
today,i download the latest version of ReactOS,and burn it into CD
to boot & install it.
when i enter the FreeLoader,and after the program loaded the system
files,it gives me an ERROR "ReactOS can not find Hard Disk".
then Press "Enter" to reboot. install failed.
my Hard Driver is Hitachi 120GB SATA HD,and my laptop is HP compaq 6510b
model,please help me with it.thanks~
--
Best regards,
Sharl.Jimh.Tsin (From China *Obviously Taiwan INCLUDED*)
Using Gmail? Please read this important notice: http://www.fsf.org/campaigns/jstrap/gmail?10073.
Dear ReactOS members,
Following the advice of vicmarcal, I would like to herewith kindly propose a topic for discussion at the next ReactOS meeting (whenever it is scheduled):
I. Authorisation
The question is how a person shall be empowered to act or speak for ReactOS, to what degree in what way, with what binding effect and for what area; as well, how such powers can be transferred and withdrawn. The scope shall at least cover all NON-TECHNICAL aspects of ReactOS.
The motive for this proposal is this:
1. You have a lot of people who would like to help SOMEHOW, but not in a technical manner. Many people have superior talents though not in the area of software development; you have brilliant marketing people, economists, artists, lawyers etc. out there, yet so far you lack any organised way to tie them efficiently into the project. (You, being developers, of course know how to tie in developers; but that is exactly what I am NOT talking about.) Figure the people who neither wish to develop, nor wish to test, nor wish to translate... but would not mind to order 200 pens and distribute them to IT students while giving out some juice or something; basically stuff that someone may do for 100 EUR or less, but which, if done by 20-50 people over 5 years, may start to have an effect.
2. We are talking about NON-TECHNICAL aspects. You have a working system for development, there is no need to mess it up and this proposal would wind up in a fruitless and infinite discussion. I propose to therefore not include development into this.
The proposal may also be, of course, declined - especially if you prefer to remain small for the time being. But that, just like the alternative of allowing such help, should be a clear decision.
II. Organisation
Should the authorisation idea not be discussible or decidable at the time being, i.e. if there are too many open questions and you can say neither "yes" nor "no", then I propose alternatively to discuss organisation: WHO may decide WHAT under what circumstances and with what effect; and especially, what is to be done if people dissent. - Because the above is not a big deal, and if you cannot decide on the above, then chances are that you may wish to streamline your decision-making process.
A few points to consider:
- Is it a more "democratic" system (broader consent, but sluggish and often without clear direction) or a more "dictatorial" system (faster and clearer decisions, but maybe at times against majoritary sentiments; the dictators may rotate, e.g. you are always dictator for e.g. one calendar month, then comes the next person - maybe you apply the dictatorial principle only for the everyday stuff, while big stuff needs common approval - which is not unlike to how a government or a company works);
- What is needed to meet what decisions (e.g., BIG decisions, as such involving entering into legally binding agreements with other entities in the name of ReactOS will need more thorough consideration than inviting to a pizza & coke event to promote ReactOS; you may set up rules on quorums and majorities);
- What means shall be there to perform tasks - and yes, the money question will come up here. (Even the pizza & coke event needs some money.) You could say, up to 5% of some certain fonds (to be filled by donations) may be used by ... for the purposes of ... - You could also say, the person in charge of ... may do with his OWN money whatever he likes, as long as he does not ... (please fill in as considered proper).
These are just my humble proposals and it is up to you to decide on whether and how they might be implemented or further explored. If you have any ideas to improve or change them, please do not hesitate to comment accordingly.
Kind regards,
Aeneas
--
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!
Jetzt informieren: http://www.gmx.net/de/go/freephone
Hello,
There was no sound driver installed in the system at that moment. After reading some replies here I've tried later installing the sound driver and it seems failing. The audio card is present in Device manager, but just after startup, it gives error messages about memory in userinit and rundll.
wojo664
01-09-11
I have been following ROS for a while now and I see a few issues that
need to be solved before it can grow.
1. Setup a PR group: This group will advertise, recruit and get
supporters. It will be the job to spread word of ros, they will first
attempt to recruit developers until a time that ros is out of alpha
and can be use for daily use. They will also look for funding for ros
by contacting possible donators. This group will need to be tiered so
that we can organize what we need to do and when and have the leg
workers able to carry it out.
2. Delegation / authority: We need to setup a bit of authority
especially when it comes to the PR group. These people will be able to
delegate time sensitive/ priority jobs to personal and have a way of
communication between PR and Devs.
3. Website: The website needs to be updated (Which I have been told is
in the works) The PR’s first goal should be finding some people able
to manage that. They will need to have a template of what has
currently been done and a design of what needs to be completed.
4. Project Information for new devs: We need to update the list of
things that are “TODO” , the best list I have seen for something like
this is... http://www.reactos.org/wiki/Google_Summer_of_Code_2011_Ideas
This will give developers who check out the project a clear goal that
they might want to pick up. This can be bundled with the way GSoC has
a mentor program and have available mentors if someone needed more
guidance.
Hi all,
Even though Chemnitzer Linux-Tage has not been that long ago, I can
already announce that the ReactOS Project has received a sponsored booth
at LinuxTag 2011 in Berlin. LinuxTag is considered to be Europe's most
important Open-Source event and it takes place from 11th to 14th May at
the Berlin Fairgrounds.
As it is much more directed at an international audience compared to the
Chemnitz event, it would be nice if we can get many ReactOS team members
to attend it.
So far, I already got a positive answer from Aleksey for 1-2 days,
Matthias for the whole time and Victor for an unspecified time. I myself
will still be away from Germany during this time, so I won't be able to
come.
The German foundation might be able to refund some of the transport and
accomodation costs, but this also depends on the number of ReactOS
members present.
On the other hand, this mail should of course also serve as a call for
interested people to visit us in Berlin :-)
With best regards,
Colin
The ReactOS team is proud to announce the release of ReactOS 0.3.13.
This version continues building on the work first previewed in
0.3.12, ranging from memory management improvements to better sound
and display control. A Coverity scan also occurred between 0.3.12 and
0.3.13, helping the team clean up potential security holes and also
help improve general stability by enforcing more care in memory
operations.
Some of the biggest system changes happened with memory management
with the introduction of a new heap manager based on the Windows 2003/
Vista architecture, significantly increasing ReactOS’ compatibility
with advanced memory allocation types and providing proper kernel
mode heap management used by win32k. Performance should also see a
significant boost for many memory operations even without the
addition of optimizations on top of the new heap. The addition of a
debug heap manager late in the release cycle also spurred on a series
of fixes to memory usage across ReactOS, from the operating system to
bundled applications. These changes should significantly improve
system stability, moving ReactOS one step closer to being a viable
daily use operating system.
Other improvements include the merging in of work done in the
yarotows branch for improved display driver loading and dynamic mode
changing, significantly increasing ReactOS’ usability.
During the preparation of this release, 282 bugs were fixed,
including 50 regressions with the oldest regression being issue #4811
("comctl32.dll sync broke Abiword toolbar"). The oldest bug fixed is
#1567 "Taskmanager still showing processes while they are
closed" (almost 5 years old). 382 new bugs were opened since the
release of 0.3.12.
Previous releases 0.3.11 and 0.3.12 were downloaded 238 and 526
thousand times, which totals up to an amazing amount of 764 000
downloads, and a significant increase looks very promising.
Some of the most important changes:
Implemented dynamic video mode switch and improved graphics drivers
compatibillity.
Fixed several graphic issues.
Completely rewritten heap manager with additional debugging
capabilities for detecting out of bounds operations.
Improved management of audio mixer lines, preventing application
sounds from becoming garbled due to overlapping lines.
Heavy bug fixing in user subsystem ( improved handling of user mouse
input, messages and timers).
Visual artifacts fixed in some apps as Firefox and Thunderbird.
Fixed several bugs in the installer.
Improved apps compatibility: Stellarium 0.10.2, LHelp,
winpcap,FlashPlayer 10.1 and Mono 2.8, OllyDbg 1.10, Xenon 2000, VLC
1.1.5, Foobar 2000, Skype 4.0.0 work now.
More SATA devices are supported.
Lots of test cases were fixed.
Many improvements in the memory manager that fix several bugs and
make it more compatible with NT memory manager.
The detailed 0.3.13 changelog is also available.
Main news link: http://www.reactos.org/en/news_page_65.html
Download link: http://www.reactos.org/en/download.html
--
Aleksey Bragin
ReactOS Foundation President
http://www.reactos.org
_______________________________________________
Ros-announce mailing list
Ros-announce(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-announce
