Translations must be commited first, i would also have as many fix patches
in, as possible. Otherwise, i agree.
2010/9/21 Aleksey Bragin
> Let's branch & release 0.3.12 then, and finally unlock trunk.
>
> WBR,
> Aleksey Bragin.
>
___
Ros-dev mailing l
Breaking the boot into multiple stages would certainly fix the problem, and
as long as it gets implemented the PE version of FreeLoader should be fine.
But I do have to wonder if we'll then see a push to make the first-stage
boot code into a PE file also to make it easier to debug? (sorry, I could
The limitation that I see is that you cannot guarantee the fathelper code
will always be within the first cluster of the FreeLoader PE file. This is a
pretty severe limitation in that it means you cannot guarantee the system
will even boot. Granted, this is only a problem when trying to boot from
s
Brian Palmer schrieb:
> It seems there are some severe technical limitations to a PE FreeLoader.
>
Can you please elaborate on that? What limitations are there?
I can only see one minor limitation: Booting from a floppy or harddisk
with FAT16, which is smaller than 300MB, where freeldr gets frag
Hello,
I propose a compromise similar to what embedded systems and Windows itself do:
A first-stage, 16-bit, raw loader (startup.com in Microsoft lingo).
A second-stage, 32-bit, protected mode loader (osloader.exe in Microsoft lingo).
The first part would be the low-level parts of FreeLDR that a
It seems there are some severe technical limitations to a PE FreeLoader.
Unless there are good reasons for it to remain a PE file (and I don't think
easier debugging is a good reason), I would like to see the PE changes to
FreeLoader reverted.
-Original Message-
From: ros-dev-boun...@react
> Ros Arm wrote:
> > Hello,
> >
> > After the switch in 48124 to PE FreeLDR, I am unable to boot FreeLDR any
> > longer.
> >
> > I have tried official, as well as various unofficial freeldr.sys, none
> > worked.
> >
> > 47892 version works fine, 48124 does not.
> >
> > On a 512MB IDE disk, I got
Let's branch & release 0.3.12 then, and finally unlock trunk.
WBR,
Aleksey Bragin.
On Sep 21, 2010, at 3:01 PM, victor martinez wrote:
I am currently checking our 0.3.12 milestones. And the milestones
status is:
**(Bug 5517)Some icons look wrong (blue background)**
There is
I am currently checking our 0.3.12 milestones. And the milestones status is:
**(Bug 5517)Some icons look wrong (blue background)**
There is a Hack for the release.
**(Bug5560): Adobe Acrobat Reader 7.1 throws exception at start
This is a Wine regression. It is not i
Actually, release build is broken.
Here is a fix for that, gDebugChannel has to be only defined for debug builds.
http://www.reactos.org/paste/index.php/7755/
Please test & report comments.
Kind regards,
Sylvain Petreolle
- Message d'origine
> De : James Tabor
> À : ReactOS Develop
10 matches
Mail list logo
