I'm going to install ReactOS on a computer which does not have support
for bootable CD's. I can copy the install files to the target
computer's HD, but is it possible to initiate the installation
afterwards? Custom boot disk?
/nitro2k01
--
The blog of nitro2k01: <http://soundandcomplete.blogspot.com/>
Saliga äro de som kan stava till 2k01!
Hi all,
There is a very nice sideshow here
http://shots.osdir.com/slideshows/slideshow.php?release=487&slide=1
Something that I have not seen on reactos.org. It is a good place to point
interested people to.
Having see most of the selection of screen shots and not having installed
any of the releases this year, I can say wow, what a difference a year
makes. Well done devs.
Regards,
jh
The voting is closed and ReactOS now has a new project coordinator.
Steven Edwards has been appointed as Jason Filby's successor.
Congratulations, and good luck ;)
Speech ! ! !
************************************************************************
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
Just a datapoint: we now have more than 2000 accounts registered on our
website. For reference, there were 964 accounts when we switched to the new
website end of September, so the number of accounts more than doubled in the
last two months.
Yes, I know that some people registered more than one account because of
problems and yes, probably not all accounts are active, but I still see this
as a sign that interest in ReactOS is rising.
Gé van Geldorp.
João Jerónimo Barata de Oliveira wrote:
> Well, indeed there's a boot loader that works very much like this...
> GRUB uses that sector to store some parts of the program... but I don't
> know if it stores there the config and I think that would be essencial
> (because, in my opinion, a boot loader needs to be independent from
> operating systems so, for example, there could be configuration floppy
> disks for changing its configuration)...
> As Grub is very similar (or parhaps identic) to my description of the
> ideal boot loader, I would like you to chose Grub as ReactOS boot loader
> (either by modifying it's configuration or by installing it from
> scratch, depending on the pré-install configuration)... That is, of
> course, also making ReactOS multiboot-compilant if it isn't already (It
> doesn't look like that)...
Any ReactOS boot loader must be able to read the registry and detect
hardware. It's the way NT works, because NTLDR does sort of the same
thing as well. Freeldr isn't a generic boot loader, it's the ReactOS
boot loader. It's been said time and again, if you like Grub, then set
Freeldr timeout to 0 (it won't display any menu and will immediately
boot ReactOS), and chainload Freeldr through Grub. I really don't at all
see what this idea of yours might have to do with ReactOS. Not only
that, but it's very OT to this ML discussion.
mf
Hi,
I recall having heard several suggestions to make freeldr easier on the
eyes (don't underestimate 60Hz VGA resolutions on a CRT) and/or make it
look more familiar to ntldr. I have experimented with editing bootsup.c
and the result implements both suggestions. The black background makes
it less flickery on CRT displays and looks more in line with ntldr (the
Windows boot loader). Please see the attached image and tell me your
thoughts and observations.
Best Regards,
mf.
Hi,
Here's a curious (and very easy to reproduce) error in ReactOS explorer.
After downloading qemu preloaded with ReactOS and running it, going to
ReactOS explorer shows two hard drive: C and D while qemu has only one
mounted (I can see a c.img but no d.img in qemu's folder). Clicking on D
produces a "*0x3ed unknown error*" (I have attached a screenshot).
I guess this issue has two solutions:
- Either, the problem comes from qemu reporting an nonexistant hard drive,
in which case, the 0x3ED exception should be intercepted and be displayed
instead as: "Unable to access D drive".
- Or qemu's indeed not reporting the D drive in which case the bug comes
from the ReactOS kernel or ReactOS explorer.
I could have implemented the corrections in the sources myself and sent
them here already, but I haven't done so since (1) I wasn't sure whether the
issue came from qemu reporting nonexistent hard drives to the ReactOS
kernel, from the kernel reporting nonexistent hard drives to ReactOS
explorer or from the ReactOS explorer reporting an nonexistent hard drive to
the user. (2) I didn't know where the error strings are located in the
source files (it would be great if somebody pointed me to the string table
for ReactOS explorer) and, even after a lookup on Internet, couldn't find
the exact string corresponding to the 0x3ED error code.
- Warz Cannon.
Hello,
most of the time when I choose logoff I get into a blue screen
saying I can turn the computer off.
But sometimes I get into an empty black screen.
What does it mean? Has the filesystem been flushed at this time?
-Hanspeter
From dev mailing list archive
>From bblaauw at home.nl Thu Nov 17 16:09:23 2005
>From: bblaauw at home.nl (Bernd Blaauw)
>Date: Thu Nov 17 16:12:08 2005
>Subject: [ros-dev] 0.3 release plan - Again
>
>Would "USB working" also mean "boot from USB" ? Not even MS allows this.
>Sadly no PC BIOS supports "boot from FireWire", like Apples do. Guess
>we'd need LinuxBIOS for that, as current motherboard manufacturers don't
>want to pay AMI/Phoenix/Award for including the "boot from firewire" >module.
>
>Bernd
>
Would these be of any interest.
http://freebios.sourceforge.net/http://www.openbios.info/
I am not subscribed to the dev mailing list, so does anyone want to pass
this on.
Regards,
jh
Hi,
What about hiding things that haven't been implemented? There are many
places in Control Panel with such items.
Showing things like accessibility which is tottaly unimplemented doesnt do
anything good. Every normal user goes in each release and check if this is
working.
In near futere there will be probably many bug reports saying: something
from Control Panel doesn't work.
Actually things that work aren't visible. They are somewhere between
unimplemented stuff.
What about showing things that should work already?
Sebastian
ps. sorry for my poor english :]
