Hi all,
Im writing a short mail to explain the recent USETUP improvements Im doing
in the
https://svn.reactos.org/svn/reactos/branches/setup_improvements/base/setup/
branch.
The aim is three-fold:
- To improve multi-OSes / bootloaders detection and solve
https://jira.reactos.org/browse/CORE-4870 ,
https://jira.reactos.org/browse/CORE-12672 ,
https://jira.reactos.org/browse/CORE-13188 ,
https://jira.reactos.org/browse/CORE-13226 in a consistent & reliable way,
and possibly having a look at https://jira.reactos.org/browse/CORE-13205 and
https://jira.reactos.org/browse/CORE-10898 (low priority for me at the
moment).
- A bit related to the previous point, have the possibility to
automatically detect existing installations of ReactOS (and of Windows) to
allow simple upgrade. For this latter part I have code that almost works: it
browses all the available partitions on all the disks, and for each,
attempts to see whether either freeldr or ntldr is installed, and if so,
open their respective configuration files, browse the latter, and from that,
deduce the candidate NT installations. On the following screenshot :
http://i.imgur.com/Nq67J1o.png , a Windows installation actually exists on
partition(1) but is not listed because it happens to be on an NTFS
partition. Then there is a ReactOS installation on a FAT partition(2), and
finally a Windows installation on another FAT partition(4) (all on the
same disk). The installation detector has respectively parsed freeldr.ini,
and boot.ini, to deduce the installations, and have removed installations
having the same disk and partition numbers and SystemRoot (otherwise you
would have seen many ReactOS (xxx) entries).
- To facilitate the future implementation of the 1st-stage GUI
setup by someone, all the code that can be made common between USETUP and
this future GUI setup, is placed into a library. At the time of writing,
this concerns the so-called generic lists functionality as well as the
partition lists & some file-system-related routines. It will certainly grow
up later.
Cheers,
Hermès
P.S.: Using a 8x8 font for the installer quickly hurts the eyes (and it has
been like that since ages). It would be great to use a more readable
resolution / font size
Fixing a bugcheck from usermode???
I'm guessing you mean avoid a bugcheck, and the real crash still needs investigating and fixing?
-----Original Message-----
From: Ros-diffs [mailto:ros-diffs-bounces@reactos.org] On Behalf Of phater(a)svn.reactos.org
Sent: 18 May 2017 09:48
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [phater] 74577: [MSTSC] Fix BSOD when we can't acquire context from CryptoAPI. CORE-13263 #resolve
Author: phater
Date: Thu May 18 08:47:30 2017
New Revision: 74577
URL: http://svn.reactos.org/svn/reactos?rev=74577&view=rev
Log:
[MSTSC] Fix BSOD when we can't acquire context from CryptoAPI. CORE-13263 #resolve
On 2017-05-15 03:59, hbelusca(a)svn.reactos.org wrote:
> Author: hbelusca
> Date: Mon May 15 01:59:28 2017
> New Revision: 74550
>
> URL: http://svn.reactos.org/svn/reactos?rev=74550&view=rev
> Log:
> [USETUP]: Continue implementing the NT OS installation detector.
> What remains to be done here, besides cleaning up the code from temporary comments and DPRINTs (and fixing potential bugs), is to actually parse the NTOS loader configuration files (freeldr.ini in ROS' case, or boot.ini in Win2k3's case, etc...) to retrieve the actual installation paths. So far these are currently hardcoded for testing purposes only.
> Note that I try to distinguish between ROS and Windows installations by checking at the company name vendor of the ntoskrnl.exe & ntdll.dll files, in order to allow the upgrade of ROS installations only.
> Suggestions are always welcome.
We should totally allow "upgrading" Windows installations with ROS.
We're obviously better ;)
The logo is just a temporary hack to prove stuff works. It will be removed
at some point, so I don't think bin2c'ing is worth it...
Best regards,
Alex Ionescu
On Mon, May 15, 2017 at 5:51 AM, Hermès BÉLUSCA-MAÏTO <hermes.belusca(a)sfr.fr
> wrote:
> What about using standard PE resources? Is it doable even in the EFI
> applications?
> Hermès
>
> -----Message d'origine-----
> De : Ros-dev [mailto:ros-dev-bounces@reactos.org] De la part de Thomas
> Faber
> Envoyé : lundi 15 mai 2017 12:04
> À : Alex Ionescu
> Cc : ros-dev(a)reactos.org
> Objet : Re: [ros-dev] [ros-diffs] [ion] 74546: BL Library now works 100%
> in paging, protected mode. A picture is worth a thousand commits:
> http://i.imgur.com/Zx2nQ6x.jpg [BOOTLIB]: Add support for protocol
> open/close/lookup while p...
>
> We have a bin2c tool that would make including the boot logo much nicer.
> You'll want to use something like the attached patch, and add the bmp file
> as app/rosload/logo.bmp. Then just include "logo.h"
> instead of the g_Logo array in rosload.c.
>
>
> On 2017-05-15 03:38, ion(a)svn.reactos.org wrote:
> > Author: ion
> > Date: Mon May 15 01:38:49 2017
> > New Revision: 74546
> >
> > URL: http://svn.reactos.org/svn/reactos?rev=74546&view=rev
> > Log:
> > BL Library now works 100% in paging, protected mode. A picture is
> > worth a thousand commits: http://i.imgur.com/Zx2nQ6x.jpg
> > [BOOTLIB]: Add support for protocol open/close/lookup while paging and
> protected mode is enabled.
> > [BOOTLIB]: Implement support for dozens of UEFI functions while under
> protected mode.
> > [BOOTLIB]: Fix bugs in existing UEFI functions which were switching to
> _protected_ mode instead of _real mode_ before making the UEFI call.
> > [BOOTLIB]: Free dynamic descriptor in MmMdFreeDescriptor.
> > [BOOTLIB]: Implement BlHtDelete.
> > [BOOTLIB]: Implement re-initialize-all path in DsppInitialize.
> > [BOOTLIB]: Fix small bug in BlDisplayInvalidateOemBitmap
> > [BOOTLIB]: Fix bigger bug in BlDisplayGetOemBitmap :)
> >
> > Modified:
> > trunk/reactos/boot/environ/app/rosload/rosload.c
> > trunk/reactos/boot/environ/include/bl.h
> > trunk/reactos/boot/environ/lib/firmware/efi/firmware.c
> > trunk/reactos/boot/environ/lib/io/device.c
> > trunk/reactos/boot/environ/lib/io/display/display.c
> > trunk/reactos/boot/environ/lib/io/display/efi/gop.c
> > trunk/reactos/boot/environ/lib/misc/util.c
> > trunk/reactos/boot/environ/lib/mm/descriptor.c
> > trunk/reactos/boot/environ/lib/platform/time.c
> >
> > [This mail would be too long, it was shortened to contain the URLs
> > only.]
> >
> > Modified: trunk/reactos/boot/environ/app/rosload/rosload.c
> > URL:
> > http://svn.reactos.org/svn/reactos/trunk/reactos/boot/environ/app/rosl
> > oad/rosload.c?rev=74546&r1=74545&r2=74546&view=diff
> >
> > Modified: trunk/reactos/boot/environ/include/bl.h
> > URL:
> > http://svn.reactos.org/svn/reactos/trunk/reactos/boot/environ/include/
> > bl.h?rev=74546&r1=74545&r2=74546&view=diff
> >
> > Modified: trunk/reactos/boot/environ/lib/firmware/efi/firmware.c
> > URL:
> > http://svn.reactos.org/svn/reactos/trunk/reactos/boot/environ/lib/firm
> > ware/efi/firmware.c?rev=74546&r1=74545&r2=74546&view=diff
> >
> > Modified: trunk/reactos/boot/environ/lib/io/device.c
> > URL:
> > http://svn.reactos.org/svn/reactos/trunk/reactos/boot/environ/lib/io/d
> > evice.c?rev=74546&r1=74545&r2=74546&view=diff
> >
> > Modified: trunk/reactos/boot/environ/lib/io/display/display.c
> > URL:
> > http://svn.reactos.org/svn/reactos/trunk/reactos/boot/environ/lib/io/d
> > isplay/display.c?rev=74546&r1=74545&r2=74546&view=diff
> >
> > Modified: trunk/reactos/boot/environ/lib/io/display/efi/gop.c
> > URL:
> > http://svn.reactos.org/svn/reactos/trunk/reactos/boot/environ/lib/io/d
> > isplay/efi/gop.c?rev=74546&r1=74545&r2=74546&view=diff
> >
> > Modified: trunk/reactos/boot/environ/lib/misc/util.c
> > URL:
> > http://svn.reactos.org/svn/reactos/trunk/reactos/boot/environ/lib/misc
> > /util.c?rev=74546&r1=74545&r2=74546&view=diff
> >
> > Modified: trunk/reactos/boot/environ/lib/mm/descriptor.c
> > URL:
> > http://svn.reactos.org/svn/reactos/trunk/reactos/boot/environ/lib/mm/d
> > escriptor.c?rev=74546&r1=74545&r2=74546&view=diff
> >
> > Modified: trunk/reactos/boot/environ/lib/platform/time.c
> > URL:
> > http://svn.reactos.org/svn/reactos/trunk/reactos/boot/environ/lib/plat
> > form/time.c?rev=74546&r1=74545&r2=74546&view=diff
> >
> >
>
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>