Hi all,
Fezile, one of our servers in Sweden, unexpectedly disappeared after a
reboot today. Unfortunately, this is one of our older servers without an
IPMI module, so we have to wait till it's rebooted manually. I'll keep
you informed when this is done.
The server outage affects the following services:
* iso.reactos.org
* doxygen.reactos.org
* cppcheck.reactos.org
* VMware Player Test slave
* VMware Player Patchbot
We apologize for the inconveniences!
If you have any idea where we can still get a suitable IPMI module for
these servers, we would be highly interested!
The needed models are ASUS ASMB3 and Tyan M3291.
Best regards,
Colin Finck
Dear All
I have inherited a Packard Bell EasyNote, with no OS on it, but it was
previously Vista. Here is the specification [1 GB RAM, 120GB HDD, Dual
core Intel Core 2 duo T5250, 1.6GHz]
First I tried to use the Live CD which I made today Sunday 22nd June,
version 0.3.16. The CD started to load
Selected LiveCD option from the menu, the first option not the default
LiveCD (Debug) option
Various messages at the bottom including
loading system hive
Loading NT
Loading boot drivers
Splash screen appears
then a blue screen with a long message I shall summarise as follows:
# Problem detected and shut down to prevent damage
# Check you have adequate disc space
# Check BIOS updates
# disable BIOS caching or shadowing
# UNIATA.SYS - Address F79D2502 base at F79C0000, Date Stamp 52eefbe6
So I tried the installation CD.
black screen: loading boot drivers etc
blank screen, Optical drive stops
I went into the BIOS but could not find anything about caching or
shadowing and I read your FAQ. I have tried these two methods of
installationon other PCs and laptops and never been able to install.
Although I have not kept details as I have presented today.
Any help appreciated
Stephanos
Dear All
I have installed React OS as a virtual machine on my Linux computer.
It works. But I just want to clarify if React OS does not yet support
USB memory sticks and other USB devices.
If it does I will install it onto an old laptop to experiment further.
Thanks and wait to hear
Stephenos
---- Geoff Shang <geoff(a)QuiteLikely.com> wrote:
> On Wed, 9 Apr 2014, mueller6723(a)twc.com wrote:
> >> As some of you know the ReactOS Project recently launched an Indiegogo campaign (https://www.indiegogo.com/projects/reactos-community-edition) to fund development of a Community Edition where backers get a say in priority for software and hardware support. The project has been going strong but we're still a long way from the finish goal.
> > That www.indiegogo.com URL was invalid when I just clicked on it.
> Worked for me.
> Geoff.
I made the URL work indirectly from the webmail interface by copying and pasting with the mouse. Maybe the URL that failed was the webmail-doctored version, which was
http://webmail.twc.com/do/redirect?url=https%253A%252F%252Fwww.indiegogo.co…
One annoying feature of webmail is messing up the web links.
Tom
As some of you know the ReactOS Project recently launched an Indiegogo campaign (https://www.indiegogo.com/projects/reactos-community-edition) to fund development of a Community Edition where backers get a say in priority for software and hardware support. The project has been going strong but we're still a long way from the finish goal.
Backers can choose from a range of rewards from votes for their desired hardware or software to collectables like USB sticks, shirts, and the elusive Hackbunny of yore to even getting your name embedded into the Community Edition. Who knows, depending on how well we do, there might even be cake. So come on by and show your support. Together we can make the dream that is ReactOS a reality.
Dear all,
In case you don't use SSL/TLS on our infrastructure (web sites - drupal,
jira, fisheye), skip reading (and reconsider your choices about such
non-usage).
As you may (should?) have heard recently, OpenSSL has suffered a
critical security vulnerability (CVE-2014-0160), known as Heartbleed Bug
(http://heartbleed.com/). Most of our services were using an affected
release of OpenSSL, with heartbeat feature activated. Be it, mails
services, web services (Drupal, Jira).
We reacted quickly passed the public announcement, and the availability
of the fix to apply it on our infrastructure to limit the risks. Anyway,
this might have been enough (actually, the issue has been here for two
years!) to allow potentials attackers to, for instance, steal our SSL
private keys. So, we took the decision to renew all our certificates and
private keys to guarantee safe infrastructure usage.
Due to the nature of the security issue, we don't know what may have
been compromised in the infrastructure and in the user database. Hence
our drastic measures.
What does it mean for you? It means that your account information
(username + password) might have been compromised, and your account
itself could have been compromised (cookie stealth with the attack).
We highly recommend you to change your passwords and check that
everything is fine on your account. I shall remind you that password
change can take up to 6h to propagate to Fisheye & Jira.
As a side note, we enabled a while ago Perfect Forward Secrecy on our
infrastructure that should ensure that even if our private keys leaked,
your past communications (so, login on the infrastructure, for instance)
can't be deciphered. Unless your session ticket leaked as well...
We are really sorry for the caused inconvenience. I'm available by email
or on IRC to answer your questions and clear your doubts.
With my best regards,
--
Pierre Schweitzer<pierre at reactos.org>
System Administrator
ReactOS Foundation
Hi,
If anyone is interested in a doing a ReactOS related documentation project
and making an extra $50 for the time they put in, I'd like to have someone
publicly document the steps required to:
1. Signup for an Azure Trial Account
2. Install the Azure client tools in a windows system
3. Download and convert the ReactOS vbox.vmdk to VDI image for Azure
4. Upload the image to Azure storage library
5. Build a Windows compatible VM with the ReactOS disk image and attempt to
launch it
Getting ReactOS to actually work in Azure is outside of the scope of this
contract, as I don't really expect it to work, or even for you to get any
results at all. Maybe you can get lucky, I am not sure how consoles work in
Azure or if you would need to setup serial debugging or if we would need to
try to get VNC working or something else.
I've been playing around with it a bit, but just don't have the few hours
right now to devote to working on it, so if you want to help out ReactOS
and make an extra $50, send me an email.
Thanks
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and that is
an idea whose time has come." - Victor Hugo
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.
_______________________________________________
Ros-announce mailing list
Ros-announce(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-announce
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.
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…
