A new version of ReactOS has arrived on SourceForge.Net
Release Candidate 2 of version 0.2.8 has been finished last night and
upped. As usual you're welcome to download and test.
At this space some personal note:
This is the first publish the new Releasemanager Brandon Turner did. For
an unknown time, he'll do all future releases, since I go on some longer
jorney. I'll not disappear from ROS but at least for some time. But I'm
coming back within a year or so.
When is this planned?
I thought it was Monday
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Hi,
for a sample program, I have to specify a linker script file. I'm using the following xml-file:
<module name="lowalign" type="win32cui" installbase="bin" installname="lowalign.exe">
<include base="lowalign">.</include>
<define name="__USE_W32API" />
<file>lowalign.c</file>
<linkerflag>-Wl,-T,modules/myapps/lowalign/ldscript</linkerflag>
<linkerflag>-Wl,--file-alignment=0x80</linkerflag>
<linkerflag>-Wl,--section-alignment=0x80</linkerflag>
</module>
I would like it if I can remove the absolute path from the linker script file. Any ideas?
- Hartmut
This is just an idea - there's no need to go crazy and bombard me with
reasons why not.
Just a thought, wouldn't it be better to ask for all the data (in the
textual part of the setup for ReactOS) to be asked and then do all the
proccessing? At the moment, it goes like so:
* ....
* Ask questions about drives
* Apply drive stuff
* Ask question about location of ReactOS
* Apply ReactOS location (and copy files)
* Ask question about booting
* Apply booting stuff
* Reboot PC
Wouldn't it be better to do:
* ....
* Ask questions about drives
* Ask question about location of ReactOS
* Ask question about booting
* Apply drive stuff
* Apply ReactOS location (and copy files)
* Apply booting stuff
* Reboot PC
This is just an idea, remember.
Jonny
I have looked at the successful Debian project for inspiration
on how to make decisions in a large distributed project like
ReactOS. I have drafted a constitution for the ReactOS project
which is similar to the Debian project constitution. You may
find it here: http://www.reactos.org/wiki/index.php/Constitution.
The constitution explains the decision making entities, their
abilities and the decision making processes of the ReactOS
project.
Feel free to comment, suggest changes, etc.
Casper
> From: ekohl(a)svn.reactos.com
>
> - Implement ScmrChangeServiceConfigW stub.
> - CreateServiceW calls ScmrCreateServiceW.
This breaks the build:
lib\advapi32\service\scm.c: In function `ChangeServiceConfigW':
lib\advapi32\service\scm.c:149: warning: implicit declaration of function
`ScmrChangeServiceConfigW'
I've disabled the code in r18735.
Gé van Geldorp.
Using LOADLIN with FreeLDR didn't work to load ReactOS from DOS, so I
remembered the GRUB4DOS program.
Please download but don't distribute in any way the following file (this
is just a demo, I don't feel like listing sites for sourcefiles)
http://odin.fdos.org/odin2005/freeldr.img
bootsequence:
1) bootfloppy
2) FreeDOS bootsector (see kernel ; GPL )
3) FreeDOS kernel (kernel 2035A, www.freedos.org ; GPL )
4) FreeDOS command.com (FreeCOM, see www.fdos.org/kernel ; GPL )
5) Batchfile (autoexec.bat, see below ; just a script, public domain thus)
6) GRUB (compresses nicely with UPX ; GPL)
7) FreeLDR (compresses nice with zip, but not bootable then. Can't be
compressed by UPX unfortunately)
Same configuration can be done on harddisk, I think (fat32 also???),
which means you can now boot FreeLDR from harddisk even without a
FreeLDR realmode install program or associated bootsector.
configuration might be even more lightweight if I omitted FreeCOM
(command.com) and used
"SHELL=A:\GRUB.EXE --config-file="kernel (fd0)/freeldr.sys" instead.
Some small misc. bugs on ReactOS:
FreeLDR: Title part has issues when it's too long, overwrites Brian
Palmer's name, and at right side it's cut-off
CMD: why does "EXIT /?" (give helpscreen for EXIT command) close the
cmd-window?
@echo off
cdd a:\
echo.
echo Welcome to FreeDOS (http://www.freedos.org)
echo Booting FreeLDR 2.0.0 through GRUB4DOS. Press CTRL-C to abort or
pause
grub --config-file="kernel (fd0)/freeldr.sys
I was looking at the Wiki's "New Homepage Content", and it mentioned
you needed volunteers, to scan the mailing lists, etc, for a useful
end-of-week Newsletter.
Well, I'd like to volunteer. I use Gmail to subscribe to The ROS and
VLC lists, and it presents Emails as Conversations, minimising search
time for specific parts of an email. That, and I religiously digest
what I can, both on ROS, ROS-Dev, and the ROS-Dev SVN Commits.
I'd like to do something to help contribute to ReactOS, and a Weekly
Newsletter sounds quite appealing. I've done the odd article for a few
IRL ones, so this is hopefully taking the next logical step.
I've got a good grasp of English (Or so I'd like to think, but I swear
the typo demon is about to leap out of my keyboard, and remove an "e"
when I least expect it...), and good English is an excellent way to
tell a user, "Wow, these guys aren't just another amateur batch of
programmers!"
So.. yeah, consider me Vounteered.
-Stuart Robbins
--
"I had a handle on life, but then it broke"
As you might know this is the last release Robert will be able to do for
a while(long term). So I will be trying to fill his spot while he is
gone. Monday works out for us to be the best time where we can work
together and he can show me everything that goes into packaging the
release. Because of this we are going to do RC2 on this day. I need
the experience and to learn from him other wise I will go into doing it
blind. I know there is a lot of talk about deciding when to release and
such. And no vote was taken on this, but we are stuck between a rock
and a hard spot. Please understand why this decision was made. Feel
free to express your views on this, and if there is over whelming
opposition we can probably work something out.
Brandon