I'm by far no expert, nor am I even on this developer list, but it
doesn't make sense to me that Open Source NT cannot be supported being
compiled in a completely open source environment - Richard Stallman
would probably have a fit to hear this!
Nathan Lane
-----Original Message-----
From: ros-general-bounces(a)reactos.org
[mailto:ros-general-bounces@reactos.org] On Behalf Of Mikhail Y.
Zvyozdochkin
Sent: Wednesday, January 10, 2007 12:58 PM
To: ReactOS General List
Subject: Re: [ros-general] Important News and Updates
Alex Ionescu wrote:
>I'm hoping most of you are
>now using the official RosBE, the ReactOS Building Environment. If
>you're not, please do so (on Windows). It is the *only* supported
>environment. If you're having problems with headers, compiling, or are
>seeing boot failures, please do not come to ask us for help until you
>are using the RosBE.
>
Hmm...
Is it mean that cross-compilation of ReactOS under *nix not supported
longer? It's no good...
WBR,
DarkHobbit
_______________________________________________
Ros-general mailing list
Ros-general(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-general
Hi,
I am new to this project. I have been experimenting with the QEmu
package that is available for download on your site, and I have come up
against: every time I install an application, specifically the Mozilla
ActiveX plugin for any of the Internet browsers I get a blue screen of
death. Here is the info on it:
How do I get around this problem? I'm a pretty good QEmu user I think,
so if you have any ideas, then I'd appreciate it.
Thanks,
Nathan
Hi!,
im currently working in the ext2 driver, although only in my local copy (i'm still
learning about the ReactOS kernel...). I currently got it to compile with the current
trunk, after solving some header problems (the ext2 branch is based on the old ReactOS
tree structure and it doesnt work (at least the last time i checked)). Note that i have
applied all my changes to a CC patched trunk.
The CC branch is currently working, applied to a recent version of the trunk. It has
a "minor" problem under QEMU which slows down disk access at the middle of the
installation. I dont know why this happens.
I had taken a look at the ReiserFS v3 driver in the vendor folder in the SVN. Im trying to
get it to compile, but i'm having problems with SEH (i took some parts from the ext2
branch to disable it).
At this moment my time is very limited. I hope to have some time in the next months to
continue working on this.
Thats it,
Regards,
Logan_V8
PS: Resending due to wrong format :P
--
_______________________________________________
Get your free email from http://www.linuxmail.org
Powered by Outblaze
Hi!,
im currently working in the ext2 driver, although only in my local copy (i'm still learning about the ReactOS kernel...). I currently got it to compile with the current trunk, after solving some header problems (the ext2 branch is based on the old ReactOS tree structure and it doesnt work (at least the last time i checked)). Note that i have applied all my changes to a CC patched trunk.
The CC branch is currently working, applied to a recent version of the trunk. It has a "minor" problem under QEMU which slows down disk access at the middle of the installation. I dont know why this happens.
I had taken a look at the ReiserFS v3 driver in the vendor folder in the SVN. Im trying to get it to compile, but i'm having problems with SEH (i took some parts from the ext2 branch to disable it).
At this moment my time is very limited. I hope to have some time in the next months to continue working on this.
Thats it,
Regards,
Logan_V8
--
_______________________________________________
Get your free email from http://www.linuxmail.org
Powered by Outblaze
Hello,
www.reactos.org may be unavailable for some time in 1-2 hours from
now because of a change in the web server software.
With the best regards,
Aleksey Bragin
Hello everybody!
My name is Roman Högg (RomanH) and I have occasionally posted to this
mailing list and the web site forum in the past for a variety of reasons.
(offering/asking for help, submitting the Swiss German keyboard layout,
etc.) I now contact you for something completely different.
Together with the Helsinki School of Economics, Luleå University of
Technology, Nokia and IBM Business Services, our institute (
http://www.mcm.unisg.ch ) is conducting a study called
"Collabora-tion4Innovation (C4I)". The study is funded by the European
Commission and is examining the im-pact of diversity within teams on
factors such as innovation, creativity and productivity. By diversity we
mean things like cultural diversity, different skills, different
educational backgrounds, etc.
In the first phase of the project we are currently conducting a number of
case studies from a variety of areas. The goal is to find the "state of
the art" and later define areas in which further research is needed (e.g.
organisational aspects such as process design, improving collaboration
technologies, etc.) Since ReactOS is - as far as I can see - developed by
a pretty diverse set of people (developers from different countries,
probably with different skills and non-developers/users/testers that try
to improve the software in whatever way they can) I wanted to ask whether
it would be possible to conduct a "Reac-tOS Case Study". I think it would
be nice to not only have companies in the case studies. If you agree to
this idea, I would like to conduct interviews with 2-3 persons of you (in
English or German, most likely via phone). Each interview would last
between 45 minutes and 1,5h maximum. (or I could send the
questionnaire/interview guide in advance and we would only discuss the
more open questions over the phone). After the interviews I would condense
everything into a 3-4 page description of the project and the aspect of
diversity. You would then get that text and could tell me whether you
agree with it or whether I would have to change things. Nothing will be
published without your consent! Unfortunately I can't offer you any money
for the collaboration, but I think the study will give the project some
additional promotion and, if you want to, you may of course use my text
for documenta-tion purposes.
Please let me know what you think and thank you very much!!!
kind regards
Roman
------------------------------------------
Roman Högg
Research Assistant
=mcm institute
for Media and Communications Management
University of St. Gallen, Switzerland
Blumenbergplatz 9, 9000 St. Gallen
Phone +41 (0)71 224 34 39
Mobile +41 (0)79 418 59 13
e-mail roman.hoegg(a)unisg.ch
http://www.mcm.unisg.chhttp://www.alexandria.unisg.ch/Personen/Roman_Hoegg
I've just read the filesystems section of the Developer FAQ and it says:
*
--------------------------------------------------------------------------------------------------
- Q* Why don't you implement Ext2/3 instead of focusing on NTFS?*
- A* Because NTFS is a major feature which must be supported at some
time. Ext2/3 is of course a topic for us, however there are already
projects whose goal it is to implement Ext2/3 for NT. We will utilize
these drivers when they are good enough.
--------------------------------------------------------------------------------------------------
So... if you are going to use the code from one of the many projects for
ext2/3 drivers around there "when they are good enough", why do the ROS
source has a driver in /reactos/drivers/filesystems/ext2? Is it one of
the popular IFS ext2/3 drivers that has, meanwhile, become "good
enough"? Or is it a ReactOS internal subproject?
And what about NTFS? Does the driver in
/reactos/drivers/filesystems/ntfs do something? Does it read?
Is it an internal project?
JJ
_______________________________________________________
Novidade no Yahoo! Mail: receba alertas de novas mensagens no seu celular. Registre seu aparelho agora!
http://br.mobile.yahoo.com/mailalertas/
Hi
everyone have notice ReactOS website, svn, mailing list, went down.
The svn and web server was never down the problem was the
DNS server whent down by hardware failour and it took time
getting it back online again. Longer that we did expect.
Hi everybody!
I have some problems with ReactOS. Today, I've tried to
install the latest stable release ("0.2.x") to my old DOS
gaming computer. The computer booted the installer, I set
the preferences of the system, I formatted the hard disk,
the file copying was successfull. At the end of the
installation, the installer ordered me to remove all media,
so I removed the install CD. The last screen said that the
installer is checking the files on the hard disk, and when
it's done, the system will reboot automatically. But
something is wrong: the progress indicator at the bottom of
the screen said: "Flushing cache", and my machine locked up
completely. After I did a hard reset, the bootloader said:
"Disk error". I've tried to reinstall ReactOS about 3 times,
but the installer always locked up at the last screen.
The system is:
CPU: Pentium II (with MMX), 300 MHz
RAM: 64 Mb
Graphics card: S3 Trio64
Hard disk: Quantum Fireball, 540 Mb
Later, I've created a ReactOS LiveCD. It boots up corretly,
but the system is weird: when I drag an icon in the
explorer, then I release the mouse button, I get a
completely empty Blue Screen of Death. I've also tried to
set the video preferences, so I've opened up the controll panel,
then opened up the screen preferences. But when I clicked in
the last tab, the system closed the window. When I open an
explorer window, the content of the window is messed up. But
when I drag the window to a different location, the content
is displayed correctly.
What can I do now?
Best regards,
Escorter
____________________________________________________________________
FotoMarket - digitális fotókidolgozás már 25 Ft-tól.
http://ad.adverticum.net/b/cl,1,6022,99786,162268/click.prm
