Ros-general

ros-general@reactos.org

3 participants
1050 discussions

by Ziliang Guo

The ReactOS project recently initiated a Kickstarter campaignin the form of Thorium Core, a cloud desktop environment that allows one to have a consistent computing environment with the same applications and settings anywhere one has a reliable broadband connection. To achieve this, Thorium intends to complete the work needed to bring ReactOS to a state where it is useable for day to day activities as well as tune it for usage in various virtual environments. Due to ReactOS' lightweight nature, a Thorium Core instance will have more resources to dedicate to the things that matter most to a user, running their applications. Of course, Thorium isn't about just a cloud desktop. It's very much about ReactOS itself. The project has gotten close, very close, to being ready for general use. Rough edges are being polished at a daily rate and in the preparation for 0.4.0, the team has put significant effort into not just the system's stability but also the user friendliness of a new explorer shell. With Thorium's success, the project can work on other issues that stand in the way of ReactOS being ready for day to day use. So for ReactOS supporters, Thorium offers the chance to bring ReactOS out of alpha, into beta, and maybe even into production. If you've been waiting years for ReactOS to be to the point where you can replace your soon to be retired Windows XP install, then here's a chance to help the project make that final push to be ready.

10 years, 11 months

ReactOS ISO support has been added in Rufus

by Pete Batard

Hi, I'm the author of Rufus [1], and I was pleasantly surprised to see it referenced on the ReactOS Live USB creation wiki [2]. So first of all, thanks for that. Now, considering that the documented method of creating a Live USB using Rufus can't exactly be qualified as very user-friendly, I have just added native support for the ReactOS bootcd/livecd ISOs in Rufus, so that you should just be able to point the app to one of those ISOs, and it will automatically create a complete bootable USB, with no need to download an invoke GRUB4DOS, 7-zip, etc. If you want to test, you can pick the latest ALPHA from: http://rufus.akeo.ie/downloads/ Currently, the way this works is through installing Syslinux (v4.07) and mboot.c32 so that setupldr.sys can then be invoked (see the /syslinux.cfg created by Rufus on the drive). Also, for the time being, only setupldr.sys will be referenced (no freeldr.sys) on account that: 1. The Syslinux's menu.c32 file is rather large, and I want to keep Rufus small, so I don't want to embed it in the application (which is also the mais reason why Rufus doesn't include native GRUB support). But this means that user selection from a menu is not available. 2. When testing, I couldn't get freeldr.sys to do much when booted from USB... though that was most likely because I hadn't actually installed ReactOS anywhere. Also note that, using 61492, even though the process seems to boot OK, I wasn't able to get a live ReactOS actually running from USB. On 2 of the machines I tried, the boot process eventually failed with "Fatal System Error 0x0000007b" in the USB stack. But I also got the exact same error with GRUB4DOS when following the steps from the wiki, so I don't think this has much to do with Rufus. I haven't really had a chance to investigate this issue yet, for lack of time. Still, I'm hoping that making the creation of a bootable UFD easier for ReactOS will help encourage more people to test it and help the project. Of course, I'm also open to suggestions to try to improve support for ReactOS in Rufus, if you want something specific. For instance, I should point out that the syslinux.cfg created by Rufus is written before any of the ISO files are copied over. Thus, if the ReactOS ISOs were to include their own syslinux.cfg & menu.c32/vesamenu.c32, it would be very easy to provide menu selection for the user when booting from USB, even as the ISOs are not Syslinux/Isolinux based. Regards, /Pete [1] http://rufus.akeo.ie/ [2] http://www.reactos.org/wiki/LiveUSB#Installing_the_MBR_.28from_64-bit_Windo…

10 years, 11 months

Announcement: Server downtime on 28th December

by Colin Finck

https://reactos.org/node/739

11 years

Fezile server down

by Colin Finck

Hi all, Apart from the critical servers hosted in Germany, we can operate our own network in Sweden by courtesy of Jan Blomqvist-Kinander. Today, the infrastructure team has set up a new switch there, which is meant to increase the network performance, allow a better intrusion detection and offer more ports. Most of our machines could be successfully moved to that switch, except for Fezile. Due to unexpected networking problems, this machine became unavailable even for us and needs to be rebooted manually. It's also one of our older servers without an IPMI module, so we can't remotely reboot it. The server outage affects the following services: * iso.reactos.org * doxygen.reactos.org * cppcheck.reactos.org * VMware Player Test slave I'm very sorry for the additional downtime this has caused. Once the server is up again, we'll do our best to prevent this from happening again. Take my word that I'll write a report for the website about the recent infrastructure changes, so you can get an idea of our additional resources :) With best regards, Colin

11 years

Server downtime on Saturday

by Colin Finck

Hi all, In the process of improving the performance of our infrastructure, we will upgrade the first of two servers this Saturday. This will result in a downtime for the following services: * SVN * Mail and mailing lists * BuildBot * Testman * GIT mirror * File server at svn.reactos.org * Compatibility Database * ev.reactos.org * Second nameserver * RosKGB bot The upgrade will in particular increase CPU performance as well as RAM and HDD sizes, so we will have more resources available afterwards. Our current server has served us well since 2009, so don't expect such an upgrade to happen again in the next few years. We're aware that this affects many core services, so we will do our best to keep the downtime as low as possible. Our target is <12h. Gladly, we have already done such an upgrade in the past, so it mainly boils down to the speed of transferring files over the network. Meanwhile, we apologize for the caused inconveniences. With best regards and on behalf of the whole infrastructure team, Colin Finck

11 years

ReactOS website issues

by Pierre Schweitzer

Hi all, This is an acknowledgment and informative email. Since we migrated the ReactOS website to Drupal, you all have spotted critical performances issues. We did our best to address most of them in the following days to ensure smooth browsing on the website. Unfortunately we could not fix them all. Even worse, nowadays, ReactOS website faces a kind of "shutdown" everyday (approximately between 2:45 AM CET and 4:45 AM CET). This is a really long and critical downtime that affects mainly US users due to timezones. Be sure we are aware about it. Unfortunately, this is not something we can fix from a day to the following. This is due to our backup policies that completely lock the MySQL server to ensure consistent backups. We are currently working on getting this fixed as fast as possible. But this will require (besides the rest) a two hardware upgrades on our infrastructure. Indeed, Drupal stresses our infrastructure much more than old RosCMS. And we have to fully rethink our web infrastructure and redistribute it, which we cannot do at the moment due to hardware constraints. Upgrading our hardware will be in our first steps (obviously, expect downtimes at that moment). Then, we will finally be able to replicate our MySQL server to perform load-balancing and prevent shutdowns on backup. We, the sysadmins team and the website team, agreed on a plan about how to enhance and strengthen the infrastructure, and thus fix all the issues we are currently facing. This will take some time, but we are working together to get ReactOS website back into a decent shape. Be assured that we are doing our best to make your place nice. Meanwhile, please forgive us the caused inconvenience. With my best regards, on behalf of the guys working behind the scene, -- Pierre Schweitzer<pierre at reactos.org> System Administrator ReactOS Foundation

11 years, 1 month

Status of accessibility components (MSAA/iAccessibility/UIA), NVDA compatibility etc

by Geoff Shang

Hi, I realise it's somewhat bad form to jump on a mailing list and immediately start posting, so I hope you'll forgive me. But it looked like the most appropriate place to ask this. I've been watching the project from afar for some time. I am a big fan of open source and have been using console-mode Debian Linux as my primary operating system for almost 15 years. But I am pragmatic enough to realise that we need alternatives, and that Windows cannot be ignored. A free Windows alternative would be fantastic if realised. As a blind person, I am very interested in the ability to use ReactOS with screen reading software such as NVDA which is open source, and others which are not. Last time I looked into the status of accessibility APIs in ReactOS, it appeared that not much had been done. After watching a presentation from Alex Ionescu yesterday on ReactOS and where it's at right now, and with Windows XP about to be end-of-lifed, I thought I'd look at this again. A google of various appropriate terms turned up a number of encouraging things, most notably doxygen documentation which indicated work on the iaccessible/MSAA accessibility API. This is most exciting, as the successor to this, iaccessible2, is I believe freely available and should not need to be reimplemented. I don't know if there are plans to extend implementation to that provided by UI Automation in more recent operating systems and back-ported rather buggily to Windows XP, but my understanding is that this would provide even greater possibility for access (particularly if it didn't include the bugs!). What I did not find, how ever, is any indication of the current status of this. I didn't find any mention of it on the Wiki in Current Status, Missing Functionality or Community Funded Ideas. There was nothing obvious to me in the Tech Wiki or the reference section, nor in the two most recent GSOC pages (I didn't go back any further). I did find something on a page entitled Change Taskforce, basically saying that this would be a good thing to support and may lead to greater support from people like GSOC, but nothing else. I also found a couple of emails like this one which don't appear to have been answered. In case further justification is needed for this, apart from the obvious goal of enabling screen reader users to use ReactOS, the NVDA project has shown what blind developers are capable of. Blind users would be able to report on accessibility issues in other parts of ReactOS and its various applications, and some would even be able to contribute by writing code or submitting translations. It's pretty much impossible for a blind person to contribute to ReactOS if they can't use it. Finally, it may be possible for the ReactOS project to either use existing software or develop their own that can conduct automated testing of ReactOS by using the accessibility APIs to both activate UI components and monitor the results. I am writing to ask about the status, but I am also asking that this status be made available somewhere where people are likely to look for it, probably on the relevant wiki page. This would mean that blind people would be able to start testing ReactOS if support is complete/near complete, and it would attract the interest of developers and interested doners if it is not. Any information on this subject would be most welcome. Thanks, Geoff.

11 years, 1 month

reactos.org down for maintenance

by Aleksey Bragin

Hello, ReactOS project website is going to be inaccessible for a period up to 2 hours due to software updates and maintenance we need to perform. Regards, Aleksey Bragin

11 years, 2 months

Re: [ros-general] Install on Dell GX270/280/ older hardware

by Thomas Mueller

> Shouldn't you be posting these questions on the forums? > I applied to this mailing list to hear news about ReactOS not to hear you > guys ask technical questions back and forth. > On Mon, Aug 26, 2013 at 4:24 PM, Bob Puff@NLE <bob(a)nleaudio.com> wrote: > Hello, > > I've tried to install both the 0.3.15 as well as the latest snapshot > > version of ReactOS on a few different machines here. I've got all the way > > through the installer, to the main bootup, but I get either a BSOD or it > > just locks. Is there ACPI or other stuff that needs to be disabled for > > this to work? I'd really like to try this. A pointer to a webpage with > > suggestions would be fine. > Bob Surely this message is appropriate to the ros-general list, or if not, then the ros-dev list. Being technical in nature, maybe the ros-dev list? But surely not spam! If I knew the answer, I'd speak up, but am strapped for where to install ReactOS. I don't think installing to USB stick is supported, and hard drive is GPT-partitioned. IDE hard drive in a USB 2.0 SATA/IDE hard-drive enclosure? And then the ReactOS 0.3.15 installation CD failed to boot. Tom

11 years, 3 months

Install on Dell GX270/280/ older hardware

by Bob Puff＠NLE

Hello, I've tried to install both the 0.3.15 as well as the latest snapshot version of ReactOS on a few different machines here. I've got all the way through the installer, to the main bootup, but I get either a BSOD or it just locks. Is there ACPI or other stuff that needs to be disabled for this to work? I'd really like to try this. A pointer to a webpage with suggestions would be fine. Bob

11 years, 3 months

← Newer
1
...
5
6
7
8
9
10
11
...
105
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Ros-general