The source code for ReactOS is only 30MB. The project has been going for 10 years so why so small?
Is there a need for any developers who can program assembler? I use the ReactOS assembler. RosAsm. http://www.rosasm.org
Or do you only program in C and C++?
The source code for ReactOS is about 200MB last time I checked. Please disregard this message as spam.
Also, FYI, RosASM is a non-approved, trademark-violating project that misrepresents itself as a ReactOS-funded/supported utility. This is probably one of their developers spam email.
From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Jason Ward Sent: March-25-07 9:35 AM To: ros-dev@reactos.org Subject: [ros-dev] Why so small?
The source code for ReactOS is only 30MB. The project has been going for 10 years so why so small? Is there a need for any developers who can program assembler? I use the ReactOS assembler. RosAsm. http://www.rosasm.org Or do you only program in C and C++?
Why is that assembler called RosASM anyway?
On 3/25/07, Alex Ionescu ionucu@videotron.ca wrote:
The source code for ReactOS is about 200MB last time I checked. Please disregard this message as spam.
Also, FYI, RosASM is a non-approved, trademark-violating project that misrepresents itself as a ReactOS-funded/supported utility. This is probably one of their developer's spam email.
From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Jason Ward Sent: March-25-07 9:35 AM To: ros-dev@reactos.org Subject: [ros-dev] Why so small?
The source code for ReactOS is only 30MB. The project has been going for 10 years so why so small?
Is there a need for any developers who can program assembler? I use the ReactOS assembler. RosAsm. http://www.rosasm.org
Or do you only program in C and C++?
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
As an attempt to gain some sort of credibility. The people behind it (betov & co) are well-known and hated among the professional ASM development community (most notably on the ASM newsgroups).
-----Original Message----- From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Anders Bergh Sent: March-25-07 1:21 PM To: ReactOS Development List Subject: Re: [ros-dev] Why so small?
Why is that assembler called RosASM anyway?
On 3/25/07, Alex Ionescu ionucu@videotron.ca wrote:
The source code for ReactOS is about 200MB last time I checked. Please disregard this message as spam.
Also, FYI, RosASM is a non-approved, trademark-violating project that misrepresents itself as a ReactOS-funded/supported utility. This is
probably
one of their developer's spam email.
From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Jason Ward Sent: March-25-07 9:35 AM To: ros-dev@reactos.org Subject: [ros-dev] Why so small?
The source code for ReactOS is only 30MB. The project has been going for 10 years so why so small?
Is there a need for any developers who can program assembler? I use the ReactOS assembler. RosAsm. http://www.rosasm.org
Or do you only program in C and C++?
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
I didn't know that. I started using that assembler in December. I started this message. It is not spam.
RosBE, where can I get this? what does it stand for? So you use NASM. I would be happy to help. Although I know nothing about OS development.
So you only use C. Not C++? Great, it would probably be a faster OS that way.
But if the project has been going fo 10 years then why hasn't a stable version been released yet?
Is all the necessary documentation that I need on the ReactOS site?
Remember, I am a complete noob when it comes to OS programming.
Thanks for the info about RosAsm. I will switch to NASM.
Just because a project is started does not mean any code is written right away. There's a planning stage a lot of times with new projects. And the devs (as far as I know) don't get paid so there time is limited to when they have free time.
But if the project has been going fo 10 years then why hasn't a stable version been released yet?
Go to the ReactOS home page, click the big download button, and you'll see a link for the build environment.
All mainstream operating systems use C. And finally, it took Microsoft five years to get Vista out the door, and that's building on an existing codebase. ReactOS wrote most things from scratch.
In the last 3 years an Amazing amount of work has gone into ReactOS. I'm sure that if these bright minds tried to make a non-nt-os from scratch they would already have a stable version however they are implementing NT. The project only goes as fast as the community that supports it. We are still in alpha yet reactos can run most of the apps that I care about for windows. That's pretty good. It will be way worth it when more drivers can be supported and a new cache manager is written.
On 3/26/07, Zachary Gorden drakekaizer666@gmail.com wrote:
Go to the ReactOS home page, click the big download button, and you'll see a link for the build environment.
All mainstream operating systems use C. And finally, it took Microsoft five years to get Vista out the door, and that's building on an existing codebase. ReactOS wrote most things from scratch.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
And... don't forget that ppl that works in ROS are not paid at all for their work. And that probably at M$ there are lots of programmers working full time on top of the beast and being well paid. Probably a lot more than on top of ROS. To me is simply amazing, and I never had doubts about ROS not even when there where no graphics at all and no page file. Remember those days? I missed a lot of fun lately :(.
On 3/26/07, Zachary Gorden drakekaizer666@gmail.com wrote:
Go to the ReactOS home page, click the big download button, and you'll see a link for the build environment.
All mainstream operating systems use C. And finally, it took Microsoft five years to get Vista out the door, and that's building on an existing codebase. ReactOS wrote most things from scratch.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ok I want to start developing for reactos. I will use NASM. Not C/C++.
So how do I start? do you send me a list of things you want done and then I do them? It would take me too long to go through all the source code so I figured that I could just write whatever you ask me to.
I am a Com Sci undergraduate. I can program in RosAsm so I shouldn't have too much trouble converting to NASM. I can read C++. I can program in python, some basic, pascal. And I am learning Java in University.
I have next to no knowledge of the win32api. I know quite a bit of OpenGL though. No Directx knowledge.
On Monday 02 April 2007 06:40, Jason Ward wrote:
Ok I want to start developing for reactos. I will use NASM. Not C/C++.
So how do I start? do you send me a list of things you want done and then I do them? It would take me too long to go through all the source code so I figured that I could just write whatever you ask me to.
I am a Com Sci undergraduate. I can program in RosAsm so I shouldn't have too much trouble converting to NASM. I can read C++. I can program in python, some basic, pascal. And I am learning Java in University.
I have next to no knowledge of the win32api. I know quite a bit of OpenGL though.
First things first, get yourself a copy of theForger's Tutorial: http://www.winprog.org/tutorial/ Then a copy of Petzold's "Programming Windows". It will give you a start in understanding the Win32 API, which is nothing like the POSIX API.
Ignore books like "Windows 2000 Developer's Guide" and so - they tend to be MFC-heavy and Win32 API-light. MFC's only useful if you're intending to do serious Windows applications development, and so, it's useless for an MS Windows-class operating system project like ReactOS. And besides, MFC's only available for people who pay the big bucks for Visual Studio - it's Microsoft's proprietary extensions built on top of the Win32 API.
To get your head around the ReactOS kernel, you should take a look at Gary Nebbett's "Windows NT/2000 Native API Reference". Russinovich and Solomon's "Windows Internals" is a good start to get your head around the MS WinNT structure/architecture - it used to be "Inside Windows [NT|2000|etc]".
Hope this helps.
Wesley Parish
No Directx knowledge.
I could be wrong of course, but isn't MFC available in VC++ 2005 Express, which is free?
On 4/2/07, Wesley Parish wes.parish@paradise.net.nz wrote:
On Monday 02 April 2007 06:40, Jason Ward wrote:
Ok I want to start developing for reactos. I will use NASM. Not C/C++.
So how do I start? do you send me a list of things you want done and then I do them? It would take me too long to go through all the source code so I figured that I could just write whatever you ask me to.
I am a Com Sci undergraduate. I can program in RosAsm so I shouldn't have too much trouble converting to NASM. I can read C++. I can program in python, some basic, pascal. And I am learning Java in University.
I have next to no knowledge of the win32api. I know quite a bit of OpenGL though.
First things first, get yourself a copy of theForger's Tutorial: http://www.winprog.org/tutorial/ Then a copy of Petzold's "Programming Windows". It will give you a start in understanding the Win32 API, which is nothing like the POSIX API.
Ignore books like "Windows 2000 Developer's Guide" and so - they tend to be MFC-heavy and Win32 API-light. MFC's only useful if you're intending to do serious Windows applications development, and so, it's useless for an MS Windows-class operating system project like ReactOS. And besides, MFC's only available for people who pay the big bucks for Visual Studio - it's Microsoft's proprietary extensions built on top of the Win32 API.
To get your head around the ReactOS kernel, you should take a look at Gary Nebbett's "Windows NT/2000 Native API Reference". Russinovich and Solomon's "Windows Internals" is a good start to get your head around the MS WinNT structure/architecture - it used to be "Inside Windows [NT|2000|etc]".
Hope this helps.
Wesley Parish
No Directx knowledge.
-- Clinersterton beademung, with all of love - RIP James Blish
Mau e ki, he aha te mea nui? You ask, what is the most important thing? Maku e ki, he tangata, he tangata, he tangata. I reply, it is people, it is people, it is people. _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
No. ATL and MFC is in Visual Studio only
On 4/2/07, Anders Bergh anders@andersman.org wrote:
I could be wrong of course, but isn't MFC available in VC++ 2005 Express, which is free?
On 4/2/07, Wesley Parish wes.parish@paradise.net.nz wrote:
On Monday 02 April 2007 06:40, Jason Ward wrote:
Ok I want to start developing for reactos. I will use NASM. Not C/C++.
So how do I start? do you send me a list of things you want done and
then I
do them? It would take me too long to go through all the source code so I
figured
that I could just write whatever you ask me to.
I am a Com Sci undergraduate. I can program in RosAsm so I shouldn't
have
too much trouble converting to NASM. I can read C++. I can program in python, some basic, pascal. And I am learning Java in University.
I have next to no knowledge of the win32api. I know quite a bit of
OpenGL
though.
First things first, get yourself a copy of theForger's Tutorial: http://www.winprog.org/tutorial/ Then a copy of Petzold's "Programming Windows". It will give you a
start in
understanding the Win32 API, which is nothing like the POSIX API.
Ignore books like "Windows 2000 Developer's Guide" and so - they tend to
be
MFC-heavy and Win32 API-light. MFC's only useful if you're intending to
do
serious Windows applications development, and so, it's useless for an MS Windows-class operating system project like ReactOS. And besides, MFC's
only
available for people who pay the big bucks for Visual Studio - it's Microsoft's proprietary extensions built on top of the Win32 API.
To get your head around the ReactOS kernel, you should take a look at
Gary
Nebbett's "Windows NT/2000 Native API Reference". Russinovich and Solomon's "Windows Internals" is a good start to get your head around
the MS
WinNT structure/architecture - it used to be "Inside Windows
[NT|2000|etc]".
Hope this helps.
Wesley Parish
No Directx knowledge.
-- Clinersterton beademung, with all of love - RIP James Blish
Mau e ki, he aha te mea nui? You ask, what is the most important thing? Maku e ki, he tangata, he tangata, he tangata. I reply, it is people, it is people, it is people. _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- Anders _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Isn't it available through the windows sdk (PSDK) ? A free download.
On 4/2/07, Justin Haygood jhaygood@spsu.edu wrote:
No. ATL and MFC is in Visual Studio only
On 4/2/07, Anders Bergh anders@andersman.org wrote:
I could be wrong of course, but isn't MFC available in VC++ 2005 Express, which is free?
On 4/2/07, Wesley Parish wes.parish@paradise.net.nz wrote:
On Monday 02 April 2007 06:40, Jason Ward wrote:
Ok I want to start developing for reactos. I will use NASM. Not C/C++.
So how do I start? do you send me a list of things you want done and
then I
do them? It would take me too long to go through all the source code so I
figured
that I could just write whatever you ask me to.
I am a Com Sci undergraduate. I can program in RosAsm so I shouldn't
have
too much trouble converting to NASM. I can read C++. I can program in python, some basic, pascal. And I am learning Java in University.
I have next to no knowledge of the win32api. I know quite a bit of
OpenGL
though.
First things first, get yourself a copy of theForger's Tutorial: http://www.winprog.org/tutorial/ Then a copy of Petzold's "Programming Windows". It will give you a
start in
understanding the Win32 API, which is nothing like the POSIX API.
Ignore books like "Windows 2000 Developer's Guide" and so - they tend to
be
MFC-heavy and Win32 API-light. MFC's only useful if you're intending to
do
serious Windows applications development, and so, it's useless for an MS Windows-class operating system project like ReactOS. And besides, MFC's
only
available for people who pay the big bucks for Visual Studio - it's Microsoft's proprietary extensions built on top of the Win32 API.
To get your head around the ReactOS kernel, you should take a look at
Gary
Nebbett's "Windows NT/2000 Native API Reference". Russinovich and Solomon's "Windows Internals" is a good start to get your head around
the MS
WinNT structure/architecture - it used to be "Inside Windows
[NT|2000|etc]".
Hope this helps.
Wesley Parish
No Directx knowledge.
-- Clinersterton beademung, with all of love - RIP James Blish
Mau e ki, he aha te mea nui? You ask, what is the most important thing? Maku e ki, he tangata, he tangata, he tangata. I reply, it is people, it is people, it is people. _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- Anders _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
I don't think so. At least, its not in the Windows Vista SDK?
On 4/9/07, Samuel serapion samdwise51@gmail.com wrote:
Isn't it available through the windows sdk (PSDK) ? A free download.
On 4/2/07, Justin Haygood jhaygood@spsu.edu wrote:
No. ATL and MFC is in Visual Studio only
On 4/2/07, Anders Bergh anders@andersman.org wrote:
I could be wrong of course, but isn't MFC available in VC++ 2005 Express, which is free?
On 4/2/07, Wesley Parish wes.parish@paradise.net.nz wrote:
On Monday 02 April 2007 06:40, Jason Ward wrote:
Ok I want to start developing for reactos. I will use NASM. Not
C/C++.
So how do I start? do you send me a list of things you want done
and
then I
do them? It would take me too long to go through all the source code so I
figured
that I could just write whatever you ask me to.
I am a Com Sci undergraduate. I can program in RosAsm so I
shouldn't
have
too much trouble converting to NASM. I can read C++. I can program
in
python, some basic, pascal. And I am learning Java in University.
I have next to no knowledge of the win32api. I know quite a bit of
OpenGL
though.
First things first, get yourself a copy of theForger's Tutorial: http://www.winprog.org/tutorial/ Then a copy of Petzold's "Programming Windows". It will give you a
start in
understanding the Win32 API, which is nothing like the POSIX API.
Ignore books like "Windows 2000 Developer's Guide" and so - they
tend to
be
MFC-heavy and Win32 API-light. MFC's only useful if you're
intending to
do
serious Windows applications development, and so, it's useless for
an MS
Windows-class operating system project like ReactOS. And besides,
MFC's
only
available for people who pay the big bucks for Visual Studio - it's Microsoft's proprietary extensions built on top of the Win32 API.
To get your head around the ReactOS kernel, you should take a look
at
Gary
Nebbett's "Windows NT/2000 Native API Reference". Russinovich and Solomon's "Windows Internals" is a good start to get your head
around
the MS
WinNT structure/architecture - it used to be "Inside Windows
[NT|2000|etc]".
Hope this helps.
Wesley Parish
No Directx knowledge.
-- Clinersterton beademung, with all of love - RIP James Blish
Mau e ki, he aha te mea nui? You ask, what is the most important thing? Maku e ki, he tangata, he tangata, he tangata. I reply, it is people, it is people, it is people. _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- Anders _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- encoded Samuel Serapión Vega Computer Engineering, Polytechnic University of Puerto Rico.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
And I haven't seen it in the Win2k3 SDK or the WinXP SDK.
But as I say, MFC's only useful if you want to write Win32 applications in C++.
On Tuesday 10 April 2007 06:56, Justin Haygood wrote:
I don't think so. At least, its not in the Windows Vista SDK?
On 4/9/07, Samuel serapion samdwise51@gmail.com wrote:
Isn't it available through the windows sdk (PSDK) ? A free download.
On 4/2/07, Justin Haygood jhaygood@spsu.edu wrote:
No. ATL and MFC is in Visual Studio only
On 4/2/07, Anders Bergh anders@andersman.org wrote:
I could be wrong of course, but isn't MFC available in VC++ 2005 Express, which is free?
On 4/2/07, Wesley Parish wes.parish@paradise.net.nz wrote:
On Monday 02 April 2007 06:40, Jason Ward wrote:
Ok I want to start developing for reactos. I will use NASM. Not
C/C++.
So how do I start? do you send me a list of things you want done
and
then I
do them? It would take me too long to go through all the source code so I
figured
that I could just write whatever you ask me to.
I am a Com Sci undergraduate. I can program in RosAsm so I
shouldn't
have
too much trouble converting to NASM. I can read C++. I can program
in
python, some basic, pascal. And I am learning Java in University.
I have next to no knowledge of the win32api. I know quite a bit of
OpenGL
though.
First things first, get yourself a copy of theForger's Tutorial: http://www.winprog.org/tutorial/ Then a copy of Petzold's "Programming Windows". It will give you a
start in
understanding the Win32 API, which is nothing like the POSIX API.
Ignore books like "Windows 2000 Developer's Guide" and so - they
tend to
be
MFC-heavy and Win32 API-light. MFC's only useful if you're
intending to
do
serious Windows applications development, and so, it's useless for
an MS
Windows-class operating system project like ReactOS. And besides,
MFC's
only
available for people who pay the big bucks for Visual Studio - it's Microsoft's proprietary extensions built on top of the Win32 API.
To get your head around the ReactOS kernel, you should take a look
at
Gary
Nebbett's "Windows NT/2000 Native API Reference". Russinovich and Solomon's "Windows Internals" is a good start to get your head
around
the MS
WinNT structure/architecture - it used to be "Inside Windows
[NT|2000|etc]".
Hope this helps.
Wesley Parish
No Directx knowledge.
-- Clinersterton beademung, with all of love - RIP James Blish
Mau e ki, he aha te mea nui? You ask, what is the most important thing? Maku e ki, he tangata, he tangata, he tangata. I reply, it is people, it is people, it is people. _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- Anders _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- encoded Samuel Serapión Vega Computer Engineering, Polytechnic University of Puerto Rico.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
On Monday 02 April 2007 06:40, Jason Ward wrote:
Ok I want to start developing for reactos. I will use NASM. Not C/C++.
So how do I start? do you send me a list of things you want done and then I do them? It would take me too long to go through all the source code so I figured that I could just write whatever you ask me to.
I am a Com Sci undergraduate. I can program in RosAsm so I shouldn't have too much trouble converting to NASM. I can read C++. I can program in python, some basic, pascal. And I am learning Java in University.
I have next to no knowledge of the win32api. I know quite a bit of OpenGL though.
In addendum: Iczelion's Win32 Assembler Homepage: http://win32assembly.online.fr/tutorials.html is a good place to start for learning the Win32 API through Assembler.
Enjoy!
Wesley Parish
No Directx knowledge.
Jason Ward wrote:
RosBE, where can I get this? what does it stand for? So you use NASM. I would be happy to help. Although I know nothing about OS development.
So you only use C. Not C++? Great, it would probably be a faster OS that way.
Any operating system's kernel needs to include some ASM, because the kernel needs to perform some low-level processor-specific operations that aren't supported by high level languages...
And ASM code is generally faster that C code, so.....
But if the project has been going fo 10 years then why hasn't a stable version been released yet?
A project of this kind and dimension includes plenty of reverse engeneering and implementing poorly documented stuff, so the time is entirely compreensible...
Is all the necessary documentation that I need on the ReactOS site?
I don't think so...
JJ
_______________________________________________________ Yahoo! Mail - Sempre a melhor opção para você! Experimente já e veja as novidades. http://br.yahoo.com/mailbeta/tudonovo/
2007/3/25, Jason Ward irnyad@gmail.com:
The source code for ReactOS is only 30MB. The project has been going for 10 years so why so small?
33 MB is the zipped archive of ReactOS 0.3.1 source code. Source code (text files) can be zipped up to ratio 10% of the original size.
Is there a need for any developers who can program assembler?
We are always looking for new devs, everyone who want to help is welcome. Most parts of ReactOS are written in C. Some kernel-mode parts are written in ASM. Please join the #reactos irc channel, most of the ReactOS devs hang out there. http://www.reactos.org/en/community_irc.html
I use the ReactOS assembler. RosAsm. http://www.rosasm.org
RosAsm and ReactOS projects are independent. The RosAsm projects use the ReactOS brand without permission for markting purpose, such acting is not tolerable.
The ReactOS project uses its own build package which consists of Mingw (+ a few patches) and NASM (and more); it's called RosBE.