Hi all,
I was pleasantly surprised to notice that the symbolic computation program «
Wolfram Mathematica », in its version 8.0.4 (later versions are for Vista+
only), actually works quite pretty well on ReactOS (as of r74550): see the
screen-capture at http://i.imgur.com/KegyW79.png .
This software is broadly used in many scientific, engineering, mathematical,
and computing fields. This is for example used intensively in theoretical
physics (in high-energy physics, statistical physics etc.) due to the
existence of numerous packages that have been developed for it. The only
problem of this software resides in its price
On the screen-capture I demonstrate an infinitesimal portion of what
Mathematica can do: for the non-connoisseurs :) the picture shows the
computation of the integral (area under the curve) of the 1-dimensional
Gaussian function over the whole real axis (the result is square-root of
pi), and then I plot in 3 dimensions the map of a 2-D Gaussian function,
where on the horizontal plane there are the x and y axes, and the vertical
axis is the z axis. The 3-D graph can be rotated, zoomed-in and out with the
mouse, it can be edited, etc The software also proposes an extensive and
interactive help documentation. Finally I show the fancy text-mode only
interface of Mathematica, that nobody actually uses (it is only used when
computing stuff in batch-mode).
There are almost no graphical glitches. Few font problems can be seen (see
the about-box, and the minus signs on the graph replaced by boxes). There
are few keyboard shortcut problems such as pressing (on French keyboards)
AltGr-5 to enter [ doesnt work, but anyways
Enjoy!
Best,
Hermès
I'd say it should stay as fallback solution.
Am 21.05.2017 18:27 schrieb "Colin Finck" <colin(a)reactos.org>:
Hey Hermès,
Great work on the setup components! I especially like the library that
paves the way for a feature-rich graphical installer :)
Am 18.05.2017 um 20:02 schrieb Hermès BÉLUSCA-MAÏTO:
> 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…
Oh yes, I'm all for a good looking installer with nicely readable texts
in all languages. Which brings us to the GUI installer and to the
question what we would still need the text-mode installer for when the
GUI one is perfect?
- Colin
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
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
>
Sounds like a bug in their migration/etc tool. MS has history going
back to 1984 and migrated everything to Git with zero problems.
At some point you should apply Ionescu's Razor: "Hmmm, a company of
150,000 developers and the most complicated and oldest series of
repositories in the world, was able to move to Git, including while
employing people who have been there for 30 years and used to other,
older systems.... but 30 open source developers can't make that change
because X". It follows from this that X is bullshit.
On the polluting history, again, just read commits that have [FOOBAR]
in them, and ignore others. Write a post-commit hook to rewrite/squash
them.
Best regards,
Alex Ionescu
On Thu, Feb 16, 2017 at 9:41 AM, Zachary Gorden
<drakekaizer666(a)gmail.com> wrote:
> The project that I worked with using git has history going back to 1988.
> They certainly didn't start with git, nor did they necessarily start with
> any revision control at the beginning, but after they migrated to it they
> discovered the history problem.
>
> On Thu, Feb 16, 2017 at 10:42 AM, Colin Finck <colin(a)reactos.org> wrote:
>>
>> Am 16.02.2017 um 14:40 schrieb Alex Ionescu:
>> > That being said, that type of "dirty history" only happens if you
>> > heavily work with branches. That's not how reactos developers work -- we
>> > don't open PRs and separate branches for every checkin.
>> >
>> > These ALL sound like manufactured problems or poor/strange use of git.
>>
>> That merge hell is easily reproducible using my default Git setup:
>>
>> 1) Change something in your clone of master and do a "git commit".
>> 2) Let someone else change something in his clone of master and let him
>> "git commit" and "git push" it.
>> 3) Try to "git push" your commit, won't work because of the commit of
>> the other person.
>> 4) Do a "git pull" to fix the problem in 3) -> Bam! Git will do an
>> automatic merge of both masters and pollute your history.
>>
>> You see, not a single extra branch is involved and yet we get two
>> parallel streams of history.
>>
>> Rafal's mentioned "pull.rebase" option sounds promising, but can we
>> enforce that somehow?
>>
>>
>> - Colin
>>
>> _______________________________________________
>> Ros-dev mailing list
>> Ros-dev(a)reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
Hello, folks!
As most of you already know, ReactOS Community Changelogs are a community based effort to describe development progress better, directly to end-user. This increases both developers' and users' morale. Adress: https://reactos.org/wiki/Community_Changelogs
All infastructure work on Wiki are complete, this means that the Changelogs can be announced now. Would you consider doing this when announcing ReactOS 0.4.5?
Finally, I want to send my big thanks to anyone who helped! Comments and suggestions are always welcome!
With my best regards!
Can Taşan
Congrats Community!
You did it!!
Thanks to your votes casted, ReactOS is finalist in the "Best IT Community" category. Even more! ReactOS was the MOST VOTED project in such category!
https://a.cstmapp.com/p/18092?fromgroup=1
ReactOS: 229 votes
2nd. KeepCoding: 190 votes
As you may know, ReactOS was also trying to be finalist as the "Best Innovative project". We were literally just ONE vote away to be one of the five finalists. 202 casted, 203 needed.
https://a.cstmapp.com/entries/18085/sort:votes/direction:desc
So even if we weren't finalist it in this category I want to thank in name of the ReactOS project all your help, votes, and support to make it possible.
Our strategy of waiting until last minute helped us to overtake and surprise really big and amazing projects as the Drupal Association, Geo developers or gvSig, but also projects supported/created by well stablished companies and public governments.
Thanks Community! We'll keep you updated! More info soon as a blogpost!
Víctor Martinez Calvo
ReactOS PR & Product strategy coordinator
Hi guys!
We made it!
But we need your help to be in the top 5! Just 24 hours to do it!
ReactOS has been selected as one of the most important projects in two different categories in the OpenAwards, an international opensource event based in Madrid. The 5 most voted will be widely announced, PRed, and finally one of them will be selected as a winner. The exposure is a need for us, you know that, so please help us by casting a vote. Takes just a second.
Categories are:
- Best Opensource Community: https://a.cstmapp.com/p/18092?fromgroup=1#
<https://a.cstmapp.com/p/18092?fromgroup=1#>
- Most innovative project: https://a.cstmapp.com/p/18085?fromgroup=1
Instructions:
- Find ReactOS in each link.
- Click in the button which says "Votar" (Vote) next to it.
- It asks for a Name, Surname, an a valid email. Please confirm the vote!.
- Done.
I'm sure we can push ReactOS to the top!
Let's surprise them with our voting boost!
Hi all!
Daniel and me collected some additional ideas for GSoC today, which I've
added to our Wiki Ideas list:
https://reactos.org/wiki/Google_Summer_of_Code_2017_Ideas
In particular:
* Fundamental WiFi components
* USBXHCI driver for supporting USB 3.x controllers
* Bluetooth Stack
* WebKit-based MSHTML implementation
I'm open for comments and suggestions!
We can still add ideas until March 20, so let's give students a large
pool to draw from.
Cheers,
Colin
Hello,
Let me invite you to the monthly status meeting taking place 27th of
April, 19:00 UTC.
We do it either in #reactos-meeting on Freenode, or on a very own
standalone IRC server. In that case your participation passwords and
server address will be emailed to you shortly before the meeting starts,
and they are going to be different once again as they are not stored in
any database. And everyone is fine with that.
Please send agenda proposals to me before the meeting so we don't waste
time trying to setup the agenda directly during the meeting.
Regards,
Aleksey Bragin