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
Hi,
since some days (weeks?), I get a nice error message during compilation, if I add the '-ftracer' switch:
gcc -c hal\halx86\mp\mpconfig.c -o .\up\obj-i386\hal\halx86\mp\mpconfig.o -Ihal\halx86\include -Intoskrnl\include
-D_DISABLE_TIDENTS -DCONFIG_SMP -D_NTHAL_ -D__USE_W32API -Iinclude -Iinclude\reactos -Iinclude\libs -Iinclude\drivers
-Iinclude\subsys -Iw32api\include -Iw32api\include\ddk -D_M_IX86 -DDBG -Wall -ftracer -Wpointer-arith -g -pipe -Werror
-D_SEH_NO_NATIVE_NLG
hal\halx86\mp\mpconfig.c: In function `HaliScanForMPConfigTable':
hal\halx86\mp\mpconfig.c:552: internal compiler error: in cfg_layout_merge_blocks, at cfgrtl.c:2631
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.mingw.org/bugs.shtml> for instructions.
_make: *** [.\up\obj-i386\hal\halx86\mp\mpconfig.o] Error 1
I can fix the problem
a) if I remove one of the case statements after line #514 in mpconfig.c or
b) if I remove the return statement at line #542 in mpconfig.c.
I'm using gcc 3.4.2 for windows.
Does someone see the same bug?
- Hartmut
Hi,
A lot of people have requested to see try out the new ws2_32.dll binary.
It's not complete yet, and I know the following applications don't work:
- Possibly all cygwin apps that use fork() and sockets
- tracert, and other XP applications which use getnameinfo().
IE6, Filezilla, Thunderbird, Firefox, MIRC, MSN, Outlook Express all
work for me, but I'd be interested in other big applications that have
trouble.
Instructions:
1) Unzip zip file contents to the directory of the program you wish to test
2) Create a blank file in that directory, named program.exe.local,
where program is the name of your app. Example: iexplore.exe.local
Please make sure that you are using Microsoft Windows XP or higher for
your tests.
I'd be happy to receive any news of application crashes or
incompatibilities. I'm most interested in games.
Best regards,
Alex Ionescu
PS. This is a debug build. It prints out a lot of debug messages if you
have a debugger attached and is also built without any optimizations. As
such, network throughput might be slower. This is normal.
hpoussin(a)svn.reactos.com wrote:
> Revert r18628, as we don't have any RTL8139 driver in ReactOS repository
>
>
> Added files:
> trunk/reactos/media/inf/netamd.inf
>
> Updated files:
> trunk/reactos/media/inf/inf.xml
>
> Deleted files:
> trunk/reactos/media/inf/netrtsnt.inf
>
I was able to install successfully the realtek 8138 nic using the
customized "netrtsnt.inf" file provided by hpoussin and to ping
www.reactos.org
The wiki driver page has to be updated accordingly as this is the
new/required method to install this nic with head
Note : Still issue around ipconfig which does not display properly (
Registry setting ? )
Regards
Gge
hpoussin(a)svn.reactos.com wrote:
> Big Plug-and-Play patch for ReactOS:
> - Install drivers for devices at first boot
> - Remove now useless entries in hivesys.inf
> At the moment, driver installation only uses .inf files in ReactOS\Inf directory, and the needed files have to be in ReactOS\Inf or their final location (ReactOS\system32 or ReactOS\system32\drivers) + the user can't provide a custom driver
> Plug-and-Plays devices are only USB controllers (OHCI and UHCI) and serial ports now.
>
>
> Updated files:
> trunk/reactos/bootdata/hivesys.inf
> trunk/reactos/ntoskrnl/io/driver.c
> trunk/reactos/services/umpnpmgr/umpnpmgr.c
>
How the nic driver ( realtek 8139 for example ) can be installed now ?
Upto now , it was installed manually by adding "rtl8139 entries" in the
registry ( hiveinst.inf file) as per wiki driver page.
Regards
Gge
