Ubuntu-fr

l'autre

ReactOS 0.3.0

bonjour!

à l'occasion de la sortie de ReactOS en version 0.3.0 (sorti le 27 août), je me pose quelques questions:

Est-ce que quelqu'un a déjà testé ce système (éventuellement dans une ancienne version)? qu'est-ce que ça donne niveau compatibilité matérielle/logicielle?

EDIT: ok, une bonne partie des réponses ici

Dernière modification par l'autre (Le 29/08/2006, à 15:01)

---

Si tu donnes à quelqu'un un poisson que tu as volé, il mangera une fois. Si tu lui apprends à voler, il mangera toute sa vie

fredbezies

Re : ReactOS 0.3.0

Et coté stabilité, c'est pire que 95 !

Sous VMWare server, Impossible de le lancer après l'installation si on lui rajoute les pilotes VMWare...

Dommage, car la 0.3rc2 le permettait

www.rzr.online.fr

Re : ReactOS 0.3.0

Le site de reactos est down il semble ..
par contre j'ai testé le Vmx fournis comment partager des fichiers entre les 2 VM
le support reseau de samba ne semble pas fonctionnel encore si ?

@ http://rzr.online.fr/q/WinNT

---

# http://identi.ca/rzr # tel mobiles sous linux ca rulez ! (maemo, openmoko, android etc)
# http://rzr.online.fr/q/apt # svp testez mes .deb's         
# http://rzr.online.fr/q/unicorn.fr # BeWan USB gris : (marche sur dapper)
# http://go.cur.lv/files# files to be shared or email me

alexisj

Re : ReactOS 0.3.0

http://sourceforge.net/projects/reactos/

MulX

Re : ReactOS 0.3.0

Effectivement le site de ROs et HS.
Voila une copie de ce que j'ai pus voir le 22/12

Failure Note

ReactOS Project

Latest News: Server Copy Ready, all data Recovered, HDDs on the way to the Hostingsite again

19.12.1006 IMPORTANT update: After 3 Times crashing of the Copy machine (1HE system) we switched to a normal PC. after 22 hours of "copy and dd"  - but the copy process is still running ....

we have this status:  - i do not think i have to comment this

:-)

Time Line and Status: (what we know so far)

    * Thursday 00.05 Raid Controller on HostSystem where Reactos Backend is running decided to do a Raid Rebuild.... (maybe triggerd by a dead hdd..unknown - Logfile is unclear about this)
    * Thursday 03.15 Raid Controller on Hostsystem Crashed the System, as it took Raidset offline
    * Thursday 09.00 Technicans investigated local to find the problem of the "crash" -- was unknown Why it crashed .. and came with the cool news "on reboot, the server writes: No operating system found..."
    * Thursday 15.00 It was clear, that the Raid controller inside the Server failed, and they "forgot" all Raid partitions. (reason unknown)

Background: Reactos is splitted into a frontend and Backup system, Backup System resides inside a Vmware Session. The problem is, that the Vmware Session (disk) is on this failed Raid Controller. (also the daily backups) -- only an old 1 Month backup is avaliabe but this is indeeed VERY old.

Atm we are dumping down the Data from the Raid Disks disk with dd to a Transfer disk manually.

The 3'rd.. 4'th ..  attempt was already VERY successful, the filesystem mounted almost without errors, but it was still not 100%.

We are Sorry, that this takes long, but did you ever dd a 1TB system ? to a new hdd ?

Really, I have seen EVERYTHING in my life ...
But we have never seen a Raidcontroller, who kills the Raidset so brutal, that not even a new Raidcontroller sees the Raid partition. (looks like a Software glitch in the Raidcontroller)

Future

We work hard, that over the Weekend the System comes up again. (all necessary Parts needed are bought already)
The chance that all this happened everything without loosing any data is a clear 99%.

Even, if we could, we could give more details, Like: Type of Raidcontroller, and so. But i do not want to Release this public, as "Bugs" can happen everywhere, and even Raidcontroller Programmers are People who can do mistakes. (maybe it was a failure of the RAM on the Raidcontroller...)

But i can garantee you here, that the Hardware is not a kind of <10k$ system ....

So keep cool, stay tuned, and do not panic, and do some X-Mas Party

(Thats indeed one of the problems we have, as all people needed to work on this are logically "on holiday", "drunk", ... --- > as always .. - and logically we are hit by Murphy's Laws  (Anything that can go wrong, will go wrong.)...)