Hello,
Is there a build command to install ReactOS to a folder. Something
equivalent to "make install" of good old RBuild days?
I used to install ReactOS on real hardware this way, because it allowed
me to have more control over the install process (aka control it
completely).
Thanks,
João Jerónimo
Hi all,
After finally setting up replication slaves for redundancy, our LDAP
setup went live today! BuildBot and all SVN repositories now
authenticate against a shared user directory.
If everything went well, you shouldn't notice a difference :)
Except that you can now change your SVN password yourself at
https://lam.reactos.org
Keep your credentials safe. We can now easily add more ReactOS developer
services like file sharing and Mumble without needing to duplicate all
user information. And we will do so!
Cheers,
Colin
Link, for ease of access: https://jira.reactos.org/browse/CORE-7864
The bug was assigned to me a while ago, but this seems to be primarily
win32k issues, which are outside my area of expertise. Someone else may be
able to handle it better.
Hi all !
In this video :
https://drive.google.com/file/d/0BzFtJhksW7viRDRVMzluTnFjMlU/view?usp=sharin
g
(with strong French accent, sorry :P, and it was my first attempt at making
a video with a camera in one hand while doing the other things with the
other hand ^^), I show an attempt to create a hybrid-USB key by configuring
freeldr to load either a livecd (shown in the video) or a bootcd in ramdisk.
Many remarks are in order:
- theres a crash when booting the bootcd image, early in phase 1 boot in Io
(can be reproduced locally on vbox for example, with similar freeldr.ini
parameters that I show in the video).
- the whole story consists in loading a ramdisk, so I avoid all the
USB-related storage problems we could (and certainly) encounter if I used
the USB key more like as we do for our current livecds, i.e. permanent reads
to the removable device.
- a ROS livecd that can be removable (in the sense that one can use another
cd to test something, while ROS is still running) should be done with some
kind of hdd image file instead, that is then loaded in memory (so that we
can then read and write to this virtual drive).
- something weird happens when freeldr loads the livecd iso in memory: first
it takes 7 minutes to just try to open the iso file, and then 7 other
minutes to load the iso proper. This problem needs to be investigated.
- we still report strange dates when listing files from the livecd (at least
when it is mounted as ramdisk), see the video.
- finally, when using Standard PC (non-ACPI) HAL, I dont really think we
reposition HDD heads into sleep position, because when I switch PC power
off with the button I can hear the HDD making the noise of the heads quickly
going back to sleep position, whereas I dont think this should happen if
the heads were being already in the correct position before I switch power
off (when using the shutdown command of FreeDOS, the other OS I have
installed in the PC, the noise isnt produced).
Cheers,
Hermès.
PS: I keep the right to remove the video at any time if I notice misuses.
And its not an official video (even if I was playing around with Windows
Movie Maker with the ReactOS logo during the first seven seconds, and with
the website links at the end) !!
Dear all,
Due to a hard disk dying, we'll attempt to anticipate its total death
tomorrow at noon CET to change it before it quits working.
It is a disk in one of our hypervisor. The following services will be hit:
-> ReactOS main website
-> Jira/Fisheye
-> Main DNS server
-> ReactOS community website
Sorry for the caused inconvenience.
With my best regards,
--
Pierre Schweitzer <pierre at reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.
Hi all,
As more and more computers these days come without optical drives, we're
thinking about switching from ReactOS CD giveaways to USB flash drive
giveaways on exhibitions (like this month's FOSDEM). ReactOS would then
come preinstalled in a VM on these drives. When ReactOS' USB support
gets better, we may even think about making these drives bootable.
Now the prices for 1GB USB drives haven't quite reached the costs of
blank CDs yet. Also many countries put a high fee on USB drives, because
you will for sure always use them to pirate copyrighted work... For
example, we're talking about a fee of 1€/unit here in Germany. Germany
is fair enough though to not apply the fee if you're ordering from
outside Germany. Maybe this also works the other way round, i.e. we as
ReactOS Deutschland e.V. order USB drives from another European country
and don't have to pay this fee.
Sooo, who of you knows a good supplier in your (European) country for
bulk ordering USB drives with the best per-unit price? Even better if
your supplier can print a custom logo on these drives.
Depending on the price, we're talking about 50-200 drives here.
Reply on the forum please:
https://reactos.org/forum/viewtopic.php?f=2&t=13917
Thanks for your help in making a great ReactOS presentation at exhibitions!
- Colin
From our investigations (Timo & I), there seems to be a memory
corruption when using a PXE boot on VBox.
You're committing a hack to workaround this memory corruption (which
replaces code which seems correct by some other code which is probably
correct), which lets you go a little bit further, where memory
corruption seems to strike again. And thus, this doesn't bring PXE boot
in better shape.
Furthermore, it appears that you're working around a bug which isn't in
ReactOS but in VBox. As a reminder, PXE boot works fine with Qemu, with
VMware. And when changing the ROM of VBox [1], then PXE boot works on
VBox as well.
Revert and report to VirtualBox instead. Our code is correct.
Thanks to Timo & Hervé for their help on digging into this issue.
[1]: https://git.ipxe.org/ipxe.git/blob/HEAD:/src/config/vbox/README
On 10/01/2015 01:21, hbelusca(a)svn.reactos.org wrote:
> Author: hbelusca
> Date: Sat Jan 10 00:21:33 2015
> New Revision: 66022
>
> URL: http://svn.reactos.org/svn/reactos?rev=66022&view=rev
> Log:
> [FREELDR]: Commit a temporary "hackfix" for (Pc)GetTime: on VBox when booting with PXE, for some mysterious reason, Int386(0x1A) call with AH = 0x02 (Get CMOS Time) *never ever* returns!! (however without PXE everything works). So... is it some kind of stack overflow or whatever that makes the Int386 function stack messy? Or something else? So in the meantime we use direct CMOS port reads. Timo, Hervé (and others), can you please review? And in particular why does it happen only with PXE?
>
> Modified:
> trunk/reactos/boot/freeldr/freeldr/arch/i386/pcrtc.c
>
> Modified: trunk/reactos/boot/freeldr/freeldr/arch/i386/pcrtc.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/freeldr/freeldr/arch/…
> ==============================================================================
> --- trunk/reactos/boot/freeldr/freeldr/arch/i386/pcrtc.c [iso-8859-1] (original)
> +++ trunk/reactos/boot/freeldr/freeldr/arch/i386/pcrtc.c [iso-8859-1] Sat Jan 10 00:21:33 2015
> @@ -20,10 +20,50 @@
>
> #define BCD_INT(bcd) (((bcd & 0xf0) >> 4) * 10 + (bcd &0x0f))
>
> +#ifndef INT386_WITH_INT_1A_AH_02_04__IS__FIXED
> +
> +/* CMOS Registers and Ports */
> +#define CMOS_CONTROL_PORT (PUCHAR)0x70
> +#define CMOS_DATA_PORT (PUCHAR)0x71
> +
> +#define RTC_REGISTER_A 0x0A
> +#define RTC_REG_A_UIP 0x80
> +
> +static UCHAR
> +HalpReadCmos(IN UCHAR Reg)
> +{
> + /* Select the register */
> + WRITE_PORT_UCHAR(CMOS_CONTROL_PORT, Reg);
> +
> + /* Query the value */
> + return READ_PORT_UCHAR(CMOS_DATA_PORT);
> +}
> +
> +#endif
> +
> TIMEINFO*
> PcGetTime(VOID)
> {
> static TIMEINFO TimeInfo;
> +
> +#ifndef INT386_WITH_INT_1A_AH_02_04__IS__FIXED
> +
> + /* Loop while update is in progress */
> + while ((HalpReadCmos(RTC_REGISTER_A)) & RTC_REG_A_UIP);
> +
> + /* Set the time data */
> + TimeInfo.Second = BCD_INT(HalpReadCmos(0));
> + TimeInfo.Minute = BCD_INT(HalpReadCmos(2));
> + TimeInfo.Hour = BCD_INT(HalpReadCmos(4));
> + TimeInfo.Day = BCD_INT(HalpReadCmos(7));
> + TimeInfo.Month = BCD_INT(HalpReadCmos(8));
> + TimeInfo.Year = BCD_INT(HalpReadCmos(9));
> +
> + /* Compensate for the century field */
> + TimeInfo.Year += (TimeInfo.Year > 80) ? 1900: 2000;
> +
> +#else
> +
> REGS Regs;
>
> for (;;)
> @@ -86,6 +126,9 @@
>
> break;
> }
> +
> +#endif
> +
> return &TimeInfo;
> }
>
>
>
--
Pierre Schweitzer <pierre at reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.
On 05/01/2015 00:49, hbelusca(a)svn.reactos.org wrote:
> Author: hbelusca
> Date: Sun Jan 4 23:49:18 2015
> New Revision: 65982
>
> URL: http://svn.reactos.org/svn/reactos?rev=65982&view=rev
> Log:
> [FREELDR]
> - Correctly append a backslash to the BootPath (if needed).
> - Be able to specify relative boot paths (relative to the current boot device): as a consequence, remove the "LiveCD" hackish special value that was introduced long long ago.
> - Fix BootPath retrieval in ReactOSSetup mode (via the SystemPath optional value), and use a better way to build the temporary txtsetup.sif full file names.
>
> As a consequence we can now build hybrid cds with the following architecture:
> \
> --> loader\ (bootsectors + free/setupldr.sys)
> --> myboot\ (contents of what_defaults_to_reactos directory for the bootcd)
> --> mylive\ (contents of what_defaults_to_reactos directory for the livecd)
> --> <regular_files>
> and
> freeldr.ini specifying the following values:
>
> ; The Setup entry
> [Setup]
> BootType=ReactOSSetup
> SystemPath=\myboot
>
> ; The LiveCD entry
> [LiveCD]
> BootType=Windows2003
> SystemPath=\mylive
> Options=/MININT
>
> Part 2/2
> CORE-9023
>
> Modified:
> trunk/reactos/boot/bootdata/livecd.ini
> trunk/reactos/boot/freeldr/freeldr/CHANGELOG
> trunk/reactos/boot/freeldr/freeldr/windows/setupldr.c
> trunk/reactos/boot/freeldr/freeldr/windows/winldr.c
>
> Modified: trunk/reactos/boot/freeldr/freeldr/windows/setupldr.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/freeldr/freeldr/windo…
> ==============================================================================
> --- trunk/reactos/boot/freeldr/freeldr/windows/setupldr.c [iso-8859-1] (original)
> +++ trunk/reactos/boot/freeldr/freeldr/windows/setupldr.c [iso-8859-1] Sun Jan 4 23:49:18 2015
> @@ -178,17 +178,40 @@
> HasSection = IniOpenSection(SectionName, &SectionId);
>
> UiDrawBackdrop();
> - UiDrawProgressBarCenter(1, 100, "Loading NT...");
> + UiDrawProgressBarCenter(1, 100, "Loading ReactOS Setup...");
>
> /* Read the system path is set in the .ini file */
> if (!HasSection ||
> !IniReadSettingByName(SectionId, "SystemPath", BootPath, sizeof(BootPath)))
> {
> + // MachDiskGetBootPath(BootPath, sizeof(BootPath));
> + // strcpy(BootPath, SectionName);
> + }
Why?
Can you please stop commenting out code without further explanations?
Either you comment out (better doing so with #if 0, for the record) and
you explain why you do so alongside in the code, for next developers
coming into the code, or you don't comment out.
So, just don't answer here, just commit an explanation ;-).
Cheers,
--
Pierre Schweitzer <pierre at reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.
Dear all,
ReactOS will be present this year at FOSDEM, in Brussels, on the 31st of
Jan & the 1st of Feb. More information at: https://fosdem.org/2015/
We will have a stand so that you can come and meet the people behind
ReactOS!
We will dispatch more information about the stand & its location when we
have them.
We're looking forward to seeing you at Brussels!
Cheers,
--
Pierre Schweitzer <pierre at reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.
Just a friendly reminder.
The remaining time to participate becomes lesser and lesser. I still think
we have good chances as this is organized by heise and they published much
news about ros in the last year, so I think they are really interested.
Here an English link: http://developerworld.heise.de/en/call-for-papers/
Am 04.12.2014 09:50 schrieb "Thomas Mueller" <mueller6723(a)twc.com>:
> Hey guys,
> I previously talked to daniel and colin about this thing and colin told me
> to write a mail to this list.
> I read about a big chance for the preject to show a presentation at the
> CeBIT, the biggest german IT convention.
> Sadly, I only have links to german websites but maybe you are satisfied
> with google translation.
> Here they are:
>
http://www.golem.de/news/call-for-papers-open-source-forum-sucht-experten-f…
>
http://www.linux-magazin.de/NEWS/Call-for-Papers-Open-Source-Forum-auf-der-…
> This would be a big chance for the project as there are people from all
> over the world and a bigger audience than the one of all Linux days
> together could learn about the project.
> Best Regards
> Robert
Sounds like a great idea. ReactOS could use the publicity, and it might
recruit more developers to ReactOS.
I have read about CeBIT on heise online (www.heise.de).
Tom
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
> A final note, too (plus question): since our recent PXE support (that
> appears to work! Thanks to Jérôme + Pierre effort, and numerous testers)
> somebody oriented me to how this is done in Windows: they have a
> STARTROM.0 file that is the bootstrap (downloaded and ran by PXE thing)
> which then loads a NTLDR (somewhat). I binary analyzed it and it seems to
be
> of the same nature as the STPBOOT.BIN file, i.e. 16-bit bootstraper.
> Question: does it load (after download) directly the 32-bit OSLOADER? OR
> does it load the full NTLDR instead?, i.e. loading the 16-bit NTLDR part
> (that then loads the 32-bit part)?
StartROM.0 (called startrom.com and startrom.n12 ins the installation media)
loads only a 32/64bit PE Setupldr.exe/Osloader.exe image, which is included
with every Windows versión based in the NT Kernel, in a compressed form ofc,
that's definitive. StartROM.0 is in effect the rought equivalent to
STPBOOT.BIN
in your example, but enabled for PXE booting.
The confusión comes because StartROM expects to find the loader image with
the
specific NTLDR file name, renaming process which is done by the built-in
Windows
Server RIS server, when you créate a Windows distribution directory with the
provided tools.
Hi all, Ive some questions/remarks about FreeLoader.
But first lets start with some introduction
On Windows (up to 2k3, things changed starting Vista), the boot loader is in
two flavours, the usual one (NTLDR) used for loading Windows when it is
installed, and another one (SETUPLDR) used only for text-mode setup.
NTLDR shows the classical OS menu (as we do in ReactOS), whereas SETUPLDR
can be seen when you boot with a Windows setup CD: it shows some kind of
text-mode blue-screen, displaying in a status bar the status of loading some
boot-time drivers, possibly allowing you to press a function key to be able
to give additional drivers to be loaded. After that, things are loaded (HAL,
kernel ) and the text-mode setup program proper is loaded (usetup.exe aka
smss.exe in the disc).
Whichever bootloader being considered, it is made of two parts
(concatenated):
- a 16 (real-mode)-to-32 bits part, lets call it STPBOOT.BIN (to follow the
convention of
http://reboot.pro/topic/5900-make-your-own-nt-os-loader-ntldrsetupldr/ ),
- and a 32-bit one.
The 16-bit part is some kind of stub which switches the CPU to 32 bit (and
may also contain some utility functions to make real-mode callbacks). This
stub is the same for both NTLDR and SETUPLDR, whereas the 32-bit part
differs.
In the Windows CD, in the \I386 directory you have those files, NTLDR and
SETUPLDR.BIN. But if you analyze them, and after noticing the (compressed)
files OSLOADER.NT_ (that expands to OSLOADER.NTD, but is in fact a native
.EXE), and SETUPLDR.EX_ (that expands to SETUPLDR.EXE, also native EXE),
you notice that in fact NTLDR == STPBOOT.BIN + OSLOADER.EXE and SETUPLDR.BIN
== STPBOOT.BIN + SETUPLDR.EXE .
(EDIT: During writing this mail I discovered that
http://en.wikipedia.org/wiki/Windows_NT_startup_process#CD-ROM_boot_image_ph
ase mentions the same thing in the Boot loader phase paragraph).
On ReactOS we do the same: our FREELDR.SYS is made of a 16-bit part
FRLDR16.BIN concatenated with FREELDR_PE.DLL (using the names of the
generated files when you compile ROS). Also we had two targets, FREELDR and
SETUPLDR, the former for generating the usual boot loader whereas the latter
was used for the bootcd. However starting revision 65832
(http://svn.reactos.org/svn/reactos?view=revision
<http://svn.reactos.org/svn/reactos?view=revision&revision=65832>
&revision=65832 ) both SETUPLDR and FREELDR became the same. Why? What
differed them was the support of the boot loading option ReactOSSetup:
SETUPLDR was in fact FREELDR *with* the support of this option (in some
revisions ago there was also support for some setup-like blue UI, see
revision 57933: http://svn.reactos.org/svn/reactos?view=revision
<http://svn.reactos.org/svn/reactos?view=revision&revision=57933>
&revision=57933 and references within). Starting r65832 the setup support is
automatically included in FREELDR. Therefore when we generate the bootcds,
we generate a FREELDR and a SETUPLDR but both files are the same
binary-wise.
Hence the question: Should we still keep the SETUPLDR target, or just
directly use FREELDR in all situations?. One may say keep it for
compatibility purposes (filename-wise), but then one might just keep only
the setupldr.sys file in the bootcd (and remove the freeldr.sys one)?
Another question would be: Should we restore a SETUPLDR target (i.e. put
setup-oriented code for SETUPLDR only and not in the usual FREELDR) in order
to be able, in the future, to implement some sort of on-demand extra driver
loading, as Windows SETUPLDR does?
A final note, too (plus question): since our recent PXE support (that
appears to work! Thanks to Jérôme + Pierre effort, and numerous testers)
somebody oriented me to how this is done in Windows: they have a
STARTROM.0 file that is the bootstrap (downloaded and ran by PXE thing)
which then loads a NTLDR (somewhat). I binary analyzed it and it seems to be
of the same nature as the STPBOOT.BIN file, i.e. 16-bit bootstraper.
Question: does it load (after download) directly the 32-bit OSLOADER? OR
does it load the full NTLDR instead?, i.e. loading the 16-bit NTLDR part
(that then loads the 32-bit part)?
Answers and comments are highly welcome!!
Happy new year to everyone!
Hermès.
On 2014-12-28 11:05, pschweitzer(a)svn.reactos.org wrote:
> +extern ERESOURCE IopSecurityResource;
This resource is only ever acquired shared, meaning it doesn't provide
any mutual exclusion at all. Is that intentional?
On 2014-11-22 23:13, hbelusca(a)svn.reactos.org wrote:
> + Status = NtCreateEvent(&Console->InputBuffer.ActiveEvent, EVENT_ALL_ACCESS,
> + &ObjectAttributes, NotificationEvent, FALSE);
> + if (!NT_SUCCESS(Status))
> + {
> + return STATUS_UNSUCCESSFUL;
> + // return Status;
> + }
This was a while ago, but I'm curious: what's the point of this?
Avoiding STATUS_UNSUCCESSFUL is usually a good thing.
Isn't the correct solution to use SxS with an activation context?
Best regards,
Alex Ionescu
On Sun, Dec 21, 2014 at 1:49 AM, <gadamopoulos(a)svn.reactos.org> wrote:
> Author: gadamopoulos
> Date: Sat Dec 20 16:49:31 2014
> New Revision: 65766
>
> URL: http://svn.reactos.org/svn/reactos?rev=65766&view=rev
> Log:
> [COMCTL32]
> * Do not add two additional pixels at the top margin of the toolbar. This
> is the behaviour of comctl32 v6 and our explorer depends on that to appear
> properly. We don't have a proper solution for these differences in behavior
> and since we already opt to use the v6 behavior I think it is fine.
>
> CORE-5483 #resolve #comment Committed a slightly different version of the
> patch, thanks.
>
> Modified:
> trunk/reactos/dll/win32/comctl32/toolbar.c
>
> Modified: trunk/reactos/dll/win32/comctl32/toolbar.c
> URL:
> http://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/comctl32/toolbar…
>
> ==============================================================================
> --- trunk/reactos/dll/win32/comctl32/toolbar.c [iso-8859-1] (original)
> +++ trunk/reactos/dll/win32/comctl32/toolbar.c [iso-8859-1] Sat Dec 20
> 16:49:31 2014
> @@ -244,7 +244,12 @@
>
> static inline int default_top_margin(const TOOLBAR_INFO *infoPtr)
> {
> +#if 0
> return (infoPtr->dwStyle & TBSTYLE_FLAT ? 0 : TOP_BORDER);
> +#else
> + /* This is the behaviour in comctl32 v6 */
> + return 0;
> +#endif
> }
>
> static inline BOOL TOOLBAR_HasDropDownArrows(DWORD exStyle)
>
>
>
Ideally, we'd fork comctl32 into two libraries like windows does, but that
would probably mean we'd have to fork from wine, moving the maintenance
effort to our side. That's why we did not do it yet.
Sent from my Windows Phone
------------------------------
From: Alex Ionescu
Sent: 21/12/2014 09:05
To: ReactOS Development List
Cc: Linda Wang; Filip
Subject: Re: [ros-dev] [ros-diffs] [gadamopoulos] 65766: [COMCTL32] * Do
not add two additional pixels at the top margin of the toolbar. This is the
behaviour of comctl32 v6 and our explorer depends on that to appear
properly. We do...
Isn't the correct solution to use SxS with an activation context?
Best regards,
Alex Ionescu
On Sun, Dec 21, 2014 at 1:49 AM, <gadamopoulos(a)svn.reactos.org> wrote:
> Author: gadamopoulos
> Date: Sat Dec 20 16:49:31 2014
> New Revision: 65766
>
> URL: http://svn.reactos.org/svn/reactos?rev=65766&view=rev
> Log:
> [COMCTL32]
> * Do not add two additional pixels at the top margin of the toolbar. This
> is the behaviour of comctl32 v6 and our explorer depends on that to appear
> properly. We don't have a proper solution for these differences in behavior
> and since we already opt to use the v6 behavior I think it is fine.
>
> CORE-5483 #resolve #comment Committed a slightly different version of the
> patch, thanks.
>
> Modified:
> trunk/reactos/dll/win32/comctl32/toolbar.c
>
> Modified: trunk/reactos/dll/win32/comctl32/toolbar.c
> URL:
> http://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/comctl32/toolbar…
>
> ==============================================================================
> --- trunk/reactos/dll/win32/comctl32/toolbar.c [iso-8859-1] (original)
> +++ trunk/reactos/dll/win32/comctl32/toolbar.c [iso-8859-1] Sat Dec 20
> 16:49:31 2014
> @@ -244,7 +244,12 @@
>
> static inline int default_top_margin(const TOOLBAR_INFO *infoPtr)
> {
> +#if 0
> return (infoPtr->dwStyle & TBSTYLE_FLAT ? 0 : TOP_BORDER);
> +#else
> + /* This is the behaviour in comctl32 v6 */
> + return 0;
> +#endif
> }
>
> static inline BOOL TOOLBAR_HasDropDownArrows(DWORD exStyle)
>
>
>
Hey,
since we skipped the meeting this week, I propose we do make a joint
November-December meeting somewhere in the middle of December. (as we
did in the previous year too).
How about 18th of December?
Regards,
Aleksey Bragin
Honestly, I don't see any point in these modifications. The next time
someone wants to use these debug routines, he will need to add it back.
Or he will start using DPRINT stuff again. I'd prefer to have this in
all files!
Am 12.12.2014 14:23, schrieb akhaldi(a)svn.reactos.org:
> Author: akhaldi
> Date: Fri Dec 12 13:23:45 2014
> New Revision: 65617
>
> URL: http://svn.reactos.org/svn/reactos?rev=65617&view=rev
> Log:
> [USER32] We're not using any debugging routines here.
>
> Modified:
> trunk/reactos/win32ss/user/user32/misc/rtlstr.c
>
> Modified: trunk/reactos/win32ss/user/user32/misc/rtlstr.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/win32ss/user/user32/misc/r…
> ==============================================================================
> --- trunk/reactos/win32ss/user/user32/misc/rtlstr.c [iso-8859-1] (original)
> +++ trunk/reactos/win32ss/user/user32/misc/rtlstr.c [iso-8859-1] Fri Dec 12 13:23:45 2014
> @@ -10,10 +10,6 @@
> /* INCLUDES ******************************************************************/
>
> #include <user32.h>
> -
> -#include <wine/debug.h>
> -
> -WINE_DEFAULT_DEBUG_CHANNEL(user32);
>
> /* FUNCTIONS *****************************************************************/
> VOID
>
>
>
Hi all,
Due to an OS upgrade on one of our VMs, the following services will
temporarily be down tomorrow (Monday):
* SVN
* BuildBot Buildmaster
* Git Mirror
* Secondary nameserver
* File server at svn.reactos.org
I'll try to get this done as fast as possible, so that the downtime will
be reduced to a minimum.
Sorry for the inconveniences!
Cheers,
Colin
Hi,
congratulations! It's a pity that MS hardcodes the C:\ at more and more
places... Original Windows NT 4.0 can boot completely even if the
drive-letter changes, WinNT + IE throws an error message but works, on
Windows 2000 one is automatically logged out again if it changes, on
Windows XP even the login-Screen doesn't appear...
Best regards,
Michael Fritscher
What is the biggest partition size compatible with 4096-byte (4 KB) cluster size, cluster size being the minimum amount of space taken by a file however small?
I googled some years ago and found it to be about 8 GB, however now I wonder if that was wrong, and I can accommodate a bigger partition.
>From what I read years back, minimum cluster size would go to 8 KB when partition size goes above 8 GB, 16 GB when partition size goes above 16 GB, 32 KB when partition size goes above 32 GB, meaning a lot of disk space wasted by small files.
I believe the best file system ReactOS can use so far is FAT32, true also for FreeDOS.
My first formatting might be done from FreeBSD, NetBSD or Linux, since I don't have ReactOS or MS-Windows installation currently.
Tom
On 2014-12-06 08:43, dreimer(a)svn.reactos.org wrote:
> [OSK]
> Fix german layout by moving the "#" button where it should be and adding the "<" button next to "Y"
Erm... hard-coding keyboard layouts into OSK is a broken design by the
way. It should determine the current layout from the OS and display
that.
(Point in case: some people *cough cough* use custom keyboard layouts)
Hello guys,
I have just read this sad news on facebook
Andrew´s wife has passed away this thursday evening. May i ask web
developers to put the attached image in the webpage?
for those who dont know who Andrew is, he is the first responsable of the
audio stack in ReactOS. He is known as silverblade in IRC and the web
My condolences to him and families and friends, from here.
Hey guys,
I previously talked to daniel and colin about this thing and colin told me
to write a mail to this list.
I read about a big chance for the preject to show a presentation at the
CeBIT, the biggest german IT convention.
Sadly, I only have links to german websites but maybe you are satisfied
with google translation.
Here they are:
http://www.golem.de/news/call-for-papers-open-source-forum-sucht-experten-f…http://www.linux-magazin.de/NEWS/Call-for-Papers-Open-Source-Forum-auf-der-…
This would be a big chance for the project as there are people from all
over the world and a bigger audience than the one of all Linux days
together could learn about the project.
Best Regards
Robert
The one who does it - please make sure to stick to the appropriate
Service Pack version too.
Regards,
Aleksey Bragin
On 29.11.2014 2:19, hbelusca(a)svn.reactos.org wrote:
> Author: hbelusca
> Date: Fri Nov 28 23:19:25 2014
> New Revision: 65519
>
> URL: http://svn.reactos.org/svn/reactos?rev=65519&view=rev
> Log:
> [WIN32K][ROSTESTS]
> So...
> ... first of all NtUserQueryInformationThread takes only 4 parameters in Win2k3 so do it as well...
> ... and since we claim at being compatible with Win2k3 (and not XP), one **MUST** review **ALL** our win32k exports, in win32ss/w32ksvc.db database first, and then in our w32kdll apitests !!!!!
> But I won't do it !
>
Hi !
While searching for something I stumbled upon this :
http://books.google.fr/books?id=YjwKAwAAQBAJ
<http://books.google.fr/books?id=YjwKAwAAQBAJ&pg=RA1-PA331&lpg=RA1-PA331&dq=
reactos+shell+new&source=bl&ots=D1hNcK_QQx&sig=n95n-VyBUgC326b3vbqg6p1QgXU&h
l=fr&sa=X&ei=7VZ3VN-5O8viaqbSgSg&ved=0CEgQ6AEwCQ#v=onepage&q=reactos%20shell
%20new&f=false>
&pg=RA1-PA331&lpg=RA1-PA331&dq=reactos+shell+new&source=bl&ots=D1hNcK_QQx&si
g=n95n-VyBUgC326b3vbqg6p1QgXU&hl=fr&sa=X&ei=7VZ3VN-5O8viaqbSgSg&ved=0CEgQ6AE
wCQ#v=onepage&q=reactos%20shell%20new&f=false
Read section: Creating a Custom Shell. They use ReactOS (and RosBE 1.5, a
piece of history ^^) for their purpose :D
Hermès.
Hey Pierre!
This flag
> + if (DeviceExt->VolumeFcb->Flags & VCB_CLEAR_DIRTY)
> + {
> + /* Set clean shutdown bit */
> + Status = GetNextCluster(DeviceExt, 1, &eocMark);
> + if (NT_SUCCESS(Status))
> + {
> + eocMark |= DeviceExt->CleanShutBitMask;
> + if (NT_SUCCESS(WriteCluster(DeviceExt, 1, eocMark)))
and that one
> + DeviceExt->VolumeFcb->Flags &= ~VCB_IS_DIRTY;
> + }
> + }
> +
> /* Flush volume & files */
> VfatFlushVolume(DeviceExt, (PVFATFCB)FileObject->FsContext);
>
>
>
don't really seem to match. Or is the former a part of a OR combination
defining the latter ?
Cheers.
Jérôme.
Hi all !
In the forums some spokesperson of an Indian company offering services
related to FOSS wants to add us to their online shop, see
http://www.reactos.org/forum/viewtopic.php?f=13
<http://www.reactos.org/forum/viewtopic.php?f=13&t=13780> &t=13780 for more
information. What do you think about this? How should we react? Should we
make clearer our line of conduct about such kind of things?
Cheers,
Hermès.
On 2014-11-23 10:49, pschweitzer(a)svn.reactos.org wrote:
> + ASSERT(NT_SUCCESS(RtlUpcaseUnicodeString(&IntFileName, FileName, TRUE)));
You need NT_VERIFY here or this will break debug builds.
Heheh, who could it be... ^^
It was always a event to watch you two arguing. ^^
Am 23.11.2014 21:57 schrieb Alex Ionescu <ionucu(a)videotron.ca>:
>
> I'm just going to chime in here and confirm that Timo does indeed own a master's diploma on surviving pissing contests, taught by the greatest master there ever was.
>
> Best regards,
> Alex Ionescu
>
> On Sat, Nov 22, 2014 at 11:47 AM, Timo Kreuzer <timo.kreuzer(a)web.de> wrote:
>>
>> Am 22.11.2014 11:39, schrieb Love Nystrom:
>>>
>>>
>>> On 2014-11-21 04.00, Timo Kreuzer wrote:
>>>>
>>>> Am 20.11.2014 14:18, schrieb Love Nystrom:
>>>>>
>>>>>
>>>>> Well... Actually not exactly the same.. ;)
>>>>> "if (f != FALSE)" requires an explicit comparison with a second operand,
>>>>
>>>> No, it does not. It requries the compiler to generate code that executes the following statement, when f is not 0.
>>>
>>>
>>> I suspect we look at it from two different viewpoints here..
>>> Yours is "C centric" and mine is "object code centric".
>>> You talk about what the compiler is required to do,
>>> and I talk about what comes out at the end of compilation.
>>
>> And what comes out at the end of the compilation is what the compiler creates. And the compiler is following the rules of the C standard and the rules of logic.
>> You claimed '"if (f != FALSE)" requires an explicit comparison with a second operand,' and that is factually wrong. No matter whether you are looking at it from the compiler perspective or from the perspective of an expressionist painter living in a yellow tree house on the bottom of Lake Tanganyika.
>>
>>>
>>> And.. dear friend.. don't turn this into a pissing contest.
>>
>> Don't even get me started. I battled the grand master and I survived.
>>
>>
>>> Let's check the egos in with the coat check girl at the entrance.
>>> May I ask how old you are?
>>
>> Are we talking about age or maturity?
>>
>> We better end this discussion, it's not leading anywhere. And you don't want me to turn into the Grinch and steal your Christmas.
>>
>> Thanks,
>> Timo
>>
>>
>> _______________________________________________
>> Ros-dev mailing list
>> Ros-dev(a)reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>
I don't know how many times I need to send the same link here but let's say that this is the last time:
this is a post about wpf but in the middle there is a paragraph about how win32k in windows processes mouse messages:
http://blogs.msdn.com/b/dwayneneed/archive/2008/09/08/transparent-windows-i…
And here is the important part:
Which HWND is the mouse over?
The operating system must respond very quickly to mouse movement. Windows uses a dedicated Raw Input Thread (RIT), running in the kernel, to handle the signals from the mouse hardware. The RIT quickly scans over the HWND hierarchy to see which window the mouse is over. Because the system must be responsive, no application code is invoked. For normal windows, the RIT checks the mouse position against the window's rectangle (or region, if one is set). But for layered windows, the RIT looks in the bitmap that specifies the content for the window and checks the effective transparency at that location (which can be affected by the constant opacity setting, the color key setting, or the per-pixel alpha channel). If the pixel is 100% transparent, the RIT skips the window and keeps looking. Once a window has been located, the mouse move flag is set on the thread that owns the window. This will cause the thread to receive a WM_MOUSEMOVE message the next time it calls GetMessage() and there are no other higher-priority messages.
Now let me explain why a flag is needed. The window manager needs to coalesce mouse move messages. If the mouse moves over a window and the system registers 10 positions over it, if the window doesn't process messages fast enough the unprocessed positions are dropped and only the last is kept. Even if another message gets between these mouse move messages get lost.
That's why the last mouse position is not stored in a message queue but in a field in the thread info. That's how the window manager worked the last 20 years in windows.
I'm sick and tired to see readable and correct code to be rewritten by shitty code, that is not readable and has obvious bugs without any reason why the previous implementation was wrong. I just give up. Do whatever you like with this shitty project of yours. I don't care anymore.
On 2014-11-15 13:34, dquintana(a)svn.reactos.org wrote:
> [SHELL32]
> * Commit the folder location fixes. They are mostly untested due to being unable to boot to desktop, but looking at the contents of the HDD after syssetup runs seems that the shortcuts are all created in their rightful place. If anyone is able to boot, feel free to test.
>
> Modified:
> branches/shell-experiments/dll/win32/shell32/wine/shellpath.c
So which is it; to Wine or not to Wine? If we need to fork this then
let's put it in another file? Or at least #ifdef __REACTOS__?
On 2014-09-29 19.00, ros-dev-request(a)reactos.org wrote:
> w0000t
> natively? via an emulator???
> what the....
> \o/
@ Javier
I just stumbled by and saw it..
Выглядит безумно, но я установил и запустил ReactOS через обертку
Qemu - Limbo ARM 7 на своем Samsung Galaxy S III mini.
It looks crazy, but I installed and started the ReactOS through wrapper
Qemu - Limbo ARM 7 on your Samsung Galaxy S III mini.
//
It might be interesting to try wedging an ARM build into the S3 though.
I was mulling over the possibility to squeeze it into an Maple Native..
Love
I saw an article on heise online (German-language website)
http://www.heise.de/newsticker/
on
ReactOS liest NTFS
http://www.heise.de/newsticker/meldung/ReactOS-liest-NTFS-2442615.html
Date is 05.11.2014, meaning just yesterday.
I subsequently looked on reactos.org and couldn't find any reference to this article.
So far, this is only for reading NTFS on ReactOS; writing ability stil has to be worked on.
This is the first article I've seen on this subject: looks like progress.
Some ReactOS developers must be familiar with this?
Tom
tcpip.c:264
/* Keep this list sorted */
InsertHeadList(ListEntry, &OutInstance->ListEntry);
This should probably be InsertTailList(), since you want to insert
before the current ListEntry
Am 12.11.2014 12:39, schrieb jgardou(a)svn.reactos.org:
> Author: jgardou
> Date: Wed Nov 12 11:39:13 2014
> New Revision: 65388
>
> URL: http://svn.reactos.org/svn/reactos?rev=65388&view=rev
> Log:
> [TCPIP]
> - Comment out an optimisation which doesn't work.
> Reviews of why would be most appreciated.
>
> Modified:
> branches/tcpip_revolution/drivers/network/tcpip/entities.c
>
> Modified: branches/tcpip_revolution/drivers/network/tcpip/entities.c
> URL: http://svn.reactos.org/svn/reactos/branches/tcpip_revolution/drivers/networ…
> ==============================================================================
> --- branches/tcpip_revolution/drivers/network/tcpip/entities.c [iso-8859-1] (original)
> +++ branches/tcpip_revolution/drivers/network/tcpip/entities.c [iso-8859-1] Wed Nov 12 11:39:13 2014
> @@ -309,9 +309,11 @@
> return STATUS_SUCCESS;
> }
>
> +#if 0
> /* The list is sorted, so we can cut the loop a bit */
> if (ID.tei_instance < Instance->InstanceId.tei_instance)
> break;
> +#endif
>
> ListEntry = ListEntry->Flink;
> }
>
>
>
Let me make a simple arrogant comment:
Don't try to fix hacks that I spent years trying to fix (and failed). They
just can't be fixed :P
Best regards,
Alex Ionescu
On Mon, Nov 10, 2014 at 1:45 AM, <pschweitzer(a)svn.reactos.org> wrote:
> Author: pschweitzer
> Date: Mon Nov 10 09:45:43 2014
> New Revision: 65352
>
> URL: http://svn.reactos.org/svn/reactos?rev=65352&view=rev
> Log:
> [NTOSKRNL]
> So... Because actual ReactOS mood is to worship hacks instead of looking
> for proper fixes to have decent behavior: reenable the IopParseDevice hack.
>
> But, so far, only reenable it for the 1st stage: the most intensive
> storage stack stage (unless you start playing with partitions & formating
> in 3rd stage).
>
> CORE-8732 #resolve #comment Bug is now properly hidden with r65352
>
> Modified:
> trunk/reactos/ntoskrnl/io/iomgr/file.c
>
> Modified: trunk/reactos/ntoskrnl/io/iomgr/file.c
> URL:
> http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/file.c?r…
>
> ==============================================================================
> --- trunk/reactos/ntoskrnl/io/iomgr/file.c [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/io/iomgr/file.c [iso-8859-1] Mon Nov 10
> 09:45:43 2014
> @@ -404,6 +404,27 @@
> /* Check if we can simply use a dummy file */
> UseDummyFile = ((OpenPacket->QueryOnly) || (OpenPacket->DeleteOnly));
>
> + /* FIXME: Small hack still exists, have to check why...
> + * This is triggered multiple times by usetup and then once per boot.
> + */
> + if (ExpInTextModeSetup &&
> + !(DirectOpen) &&
> + !(RemainingName->Length) &&
> + !(OpenPacket->RelatedFileObject) &&
> + ((wcsstr(CompleteName->Buffer, L"Harddisk")) ||
> + (wcsstr(CompleteName->Buffer, L"Floppy"))) &&
> + !(UseDummyFile))
> + {
> + DPRINT1("Using IopParseDevice() hack. Requested invalid
> attributes: %lx\n",
> + DesiredAccess & ~(SYNCHRONIZE |
> + FILE_READ_ATTRIBUTES |
> + READ_CONTROL |
> + ACCESS_SYSTEM_SECURITY |
> + WRITE_OWNER |
> + WRITE_DAC));
> + DirectOpen = TRUE;
> + }
> +
> /* Check if this is a direct open */
> if (!(RemainingName->Length) &&
> !(OpenPacket->RelatedFileObject) &&
>
>
>
Hi,
> + if (Sector->BytesPerSector * Sector->SectorsPerCluster > 32 * 1024)
> + {
> + return FALSE;
> + }
FAT supports cluster sizes until 64KB ;-) At least the WinNT series can
work with them.
Best regards,
Michael Fritscher
Thank you for working on this hack (partial) removal!
After all, having it only in the 1st stage is a win over having it
enabled all the time.
Regards,
Aleksey
On 10.11.2014 12:45, pschweitzer(a)svn.reactos.org wrote:
> Author: pschweitzer
> Date: Mon Nov 10 09:45:43 2014
> New Revision: 65352
>
> URL: http://svn.reactos.org/svn/reactos?rev=65352&view=rev
> Log:
> [NTOSKRNL]
> So... Because actual ReactOS mood is to worship hacks instead of looking for proper fixes to have decent behavior: reenable the IopParseDevice hack.
>
> But, so far, only reenable it for the 1st stage: the most intensive storage stack stage (unless you start playing with partitions & formating in 3rd stage).
>
> CORE-8732 #resolve #comment Bug is now properly hidden with r65352
>
> Modified:
> trunk/reactos/ntoskrnl/io/iomgr/file.c
>
> Modified: trunk/reactos/ntoskrnl/io/iomgr/file.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/file.c?r…
> ==============================================================================
> --- trunk/reactos/ntoskrnl/io/iomgr/file.c [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/io/iomgr/file.c [iso-8859-1] Mon Nov 10 09:45:43 2014
> @@ -404,6 +404,27 @@
> /* Check if we can simply use a dummy file */
> UseDummyFile = ((OpenPacket->QueryOnly) || (OpenPacket->DeleteOnly));
>
> + /* FIXME: Small hack still exists, have to check why...
> + * This is triggered multiple times by usetup and then once per boot.
> + */
> + if (ExpInTextModeSetup &&
> + !(DirectOpen) &&
> + !(RemainingName->Length) &&
> + !(OpenPacket->RelatedFileObject) &&
> + ((wcsstr(CompleteName->Buffer, L"Harddisk")) ||
> + (wcsstr(CompleteName->Buffer, L"Floppy"))) &&
> + !(UseDummyFile))
> + {
> + DPRINT1("Using IopParseDevice() hack. Requested invalid attributes: %lx\n",
> + DesiredAccess & ~(SYNCHRONIZE |
> + FILE_READ_ATTRIBUTES |
> + READ_CONTROL |
> + ACCESS_SYSTEM_SECURITY |
> + WRITE_OWNER |
> + WRITE_DAC));
> + DirectOpen = TRUE;
> + }
> +
> /* Check if this is a direct open */
> if (!(RemainingName->Length) &&
> !(OpenPacket->RelatedFileObject) &&
>
>
You add parentheses to conform to coding style (our coding style
guidelines do not require it) and on the other hand you convert a 2 line
if statement into one line, which does not conform to our coding style?
Am 09.11.2014 03:26, schrieb hbelusca(a)svn.reactos.org:
> Author: hbelusca
> Date: Sun Nov 9 02:26:49 2014
> New Revision: 65337
>
> URL: http://svn.reactos.org/svn/reactos?rev=65337&view=rev
> Log:
> [NTOS:PNPMGR]
> - Remove an unneeded ExFreePool(DeviceInstance.Buffer); call in IopGetInterfaceDeviceList because at this point DeviceInstance is not yet initialized. Fixes MSVC build.
> - No need to check for DeviceInstance.Buffer being NULL or not (in IopDeviceStatus), because in case it was NULL the IopCaptureUnicodeString call already failed.
> - Add some brackets to conform to code style.
>
> Modified:
> trunk/reactos/ntoskrnl/io/pnpmgr/plugplay.c
>
> Modified: trunk/reactos/ntoskrnl/io/pnpmgr/plugplay.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/pnpmgr/plugpla…
> ==============================================================================
> --- trunk/reactos/ntoskrnl/io/pnpmgr/plugplay.c [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/io/pnpmgr/plugplay.c [iso-8859-1] Sun Nov 9 02:26:49 2014
> @@ -199,8 +199,7 @@
> }
> _SEH2_EXCEPT(EXCEPTION_EXECUTE_HANDLER)
> {
> - if (Name.Buffer)
> - ExFreePool(Name.Buffer);
> + if (Name.Buffer) ExFreePool(Name.Buffer);
> Status = _SEH2_GetExceptionCode();
> }
> _SEH2_END;
>
Am 09.11.2014 02:46, schrieb hbelusca(a)svn.reactos.org:
> Author: hbelusca
> Date: Sun Nov 9 01:46:31 2014
> New Revision: 65336
>
> URL: http://svn.reactos.org/svn/reactos?rev=65336&view=rev
> Log:
> [NTVDM]: Use variable-length buffers in DisplayMessage, in case we display a very long message (uses the _vscwprintf CRT function, not available on Win2k. You need to recompile NTVDM with WIN2K_COMPLIANT define if you want to be able to run it on win2k. In that case DisplayMessage uses a quite large enough buffer for its needs). If somebody knows an alternative to _vscwprintf that does the very same job, and which exists on Win2k, I would be happy to use it instead.
Since _vscwprintf will do the whole work already anyway, you could as
well directly print it into the static buffer. You could use _vsnwprintf
or StringCbPrintfW, which internally uses the former, and use the result
to decide whether the buffer was large enough. This will be more
performant, since you only need to print once, when the buffer is large
enough.
Oh... Jérôme, I only just saw that you added this in r65140...
And my change does break the msi tests again. :\
Any idea what's going wrong here?
I'm relatively certain my change is correct because
vfatFCBInitializeCacheFromVolume takes one reference, and VfatCloseFile
invoked via ObDereferenceObject will remove that reference again.
So apparently we're leaking a directory reference somewhere else? :(
Not sure if your previous investigation into this issue can provide any
pointers. Otherwise I'll have to start digging for the leak all over
again...
Thanks.
-Thomas
On 2014-11-05 19:52, tfaber(a)svn.reactos.org wrote:
> --- trunk/reactos/drivers/filesystems/fastfat/cleanup.c [iso-8859-1] (original)
> +++ trunk/reactos/drivers/filesystems/fastfat/cleanup.c [iso-8859-1] Wed Nov 5 18:52:11 2014
> @@ -92,7 +92,6 @@
> pFcb->FileObject = NULL;
> CcUninitializeCacheMap(tmpFileObject, NULL, NULL);
> ObDereferenceObject(tmpFileObject);
> - vfatReleaseFCB(IrpContext->DeviceExt, pFcb);
> }
>
> CcPurgeCacheSection(FileObject->SectionObjectPointer, NULL, 0, FALSE);
>
>
Doesn't this change Windows behaviour?
No, luckily it does not change *Windows* behaviour.
It does not even change ReactOS behaviour, but only, because it was
already broken before.
Since MS implemented this function in an arbitrary and hard to
comprehend way, we need to follow this pattern. This means, the function
must not fail on process reference failure, unless certain conditions
are met, otherwise we will fail with the wrong Status code.
To fix the situation, we could remember the fact that the process
couldn't be referenced (possibly by setting Process to NULL) and later
check that after other checks were done. The alternative is referencing
the process individually in each and every case, which will make the
function even more huge and does not really help with it's readability.
Or we can factor our each case and implement it as a separate function.
It would add a lot of code duplication, but might help a bit with
readability and maintainability.
Am 03.11.2014 10:52, schrieb jgardou(a)svn.reactos.org:
> Author: jgardou
> Date: Mon Nov 3 09:52:08 2014
> New Revision: 65210
>
> URL: http://svn.reactos.org/svn/reactos?rev=65210&view=rev
> Log:
> [NTOS/PS]
> - Do not leak a reference to the process object when setting quotas.
>
> Modified:
> trunk/reactos/ntoskrnl/include/internal/ps.h
> trunk/reactos/ntoskrnl/ps/query.c
> trunk/reactos/ntoskrnl/ps/quota.c
>
> Modified: trunk/reactos/ntoskrnl/include/internal/ps.h
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/include/internal/…
> ==============================================================================
> --- trunk/reactos/ntoskrnl/include/internal/ps.h [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/include/internal/ps.h [iso-8859-1] Mon Nov 3 09:52:08 2014
> @@ -303,7 +303,7 @@
> NTSTATUS
> NTAPI
> PspSetQuotaLimits(
> - _In_ HANDLE ProcessHandle,
> + _In_ PEPROCESS Process,
> _In_ ULONG Unused,
> _In_ PVOID QuotaLimits,
> _In_ ULONG QuotaLimitsLength,
>
> Modified: trunk/reactos/ntoskrnl/ps/query.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ps/query.c?rev=65…
> ==============================================================================
> --- trunk/reactos/ntoskrnl/ps/query.c [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/ps/query.c [iso-8859-1] Mon Nov 3 09:52:08 2014
> @@ -1528,6 +1528,7 @@
> /* Validate the number */
> if ((BasePriority > HIGH_PRIORITY) || (BasePriority <= LOW_PRIORITY))
> {
> + ObDereferenceObject(Process);
> return STATUS_INVALID_PARAMETER;
> }
>
> @@ -1918,11 +1919,12 @@
>
> case ProcessQuotaLimits:
>
> - return PspSetQuotaLimits(ProcessHandle,
> + Status = PspSetQuotaLimits(Process,
> 1,
> ProcessInformation,
> ProcessInformationLength,
> PreviousMode);
> + break;
>
> case ProcessWorkingSetWatch:
> DPRINT1("WS watch not implemented\n");
>
> Modified: trunk/reactos/ntoskrnl/ps/quota.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ps/quota.c?rev=65…
> ==============================================================================
> --- trunk/reactos/ntoskrnl/ps/quota.c [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/ps/quota.c [iso-8859-1] Mon Nov 3 09:52:08 2014
> @@ -292,14 +292,13 @@
> NTSTATUS
> NTAPI
> PspSetQuotaLimits(
> - _In_ HANDLE ProcessHandle,
> + _In_ PEPROCESS Process,
> _In_ ULONG Unused,
> _In_ PVOID QuotaLimits,
> _In_ ULONG QuotaLimitsLength,
> _In_ KPROCESSOR_MODE PreviousMode)
> {
> QUOTA_LIMITS_EX CapturedQuotaLimits;
> - PEPROCESS Process;
> PEPROCESS_QUOTA_BLOCK QuotaBlock, OldQuotaBlock;
> BOOLEAN IncreaseOkay;
> KAPC_STATE SavedApcState;
> @@ -368,19 +367,6 @@
> }
> _SEH2_END;
>
> - /* Reference the process */
> - Status = ObReferenceObjectByHandle(ProcessHandle,
> - PROCESS_SET_QUOTA,
> - PsProcessType,
> - PreviousMode,
> - (PVOID*)&Process,
> - NULL);
> - if (!NT_SUCCESS(Status))
> - {
> - DPRINT1("Failed to reference process handle: 0x%lx\n", Status);
> - return Status;
> - }
> -
> /* Check the caller changes the working set size limits */
> if ((CapturedQuotaLimits.MinimumWorkingSetSize != 0) &&
> (CapturedQuotaLimits.MaximumWorkingSetSize != 0))
> @@ -418,7 +404,6 @@
> /* Check if the caller has the required privilege */
> if (!SeSinglePrivilegeCheck(SeIncreaseQuotaPrivilege, PreviousMode))
> {
> - ObDereferenceObject(Process);
> return STATUS_PRIVILEGE_NOT_HELD;
> }
>
> @@ -460,8 +445,6 @@
> Status = STATUS_SUCCESS;
> }
>
> - /* Dereference the process and return the status */
> - ObDereferenceObject(Process);
> return Status;
> }
>
>
>
>
Hi all,
Jan and I will finally install the remote management card in Fezile this
evening and verify the cabling of our UPS systems. This will cause a
short downtime of the Fezile server along with its testslaves, cppcheck,
Doxygen, Git and iso.reactos.org.
In case we notice a fault in UPS cabling, we may also be required to
temporarily shut down other servers, replug their power cables and boot
them up again. This may cause very short downtimes as well.
After this measure, we will be able to totally manage this important
server remotely, even if its OS has failed at some point. Proper UPS
cabling also ensures smooth operations in case of sudden power outages.
Thanks for your understanding!
Cheers,
Colin
On 2014-11-01 11:02, pschweitzer(a)svn.reactos.org wrote:
> - OutputBuffer->FileRecordLength = FileRecord->BytesInUse;
> - RtlCopyMemory(OutputBuffer->FileRecordBuffer, FileRecord, FileRecord->BytesInUse);
> + OutputBuffer->FileRecordLength = DeviceExt->NtfsInfo.BytesPerFileRecord;
> + RtlCopyMemory(OutputBuffer->FileRecordBuffer, FileRecord, DeviceExt->NtfsInfo.BytesPerFileRecord);
Wait, now there's no check against OutputBufferLength at all? It should
at least be
min(DeviceExt->NtfsInfo.BytesPerFileRecord,
Stack->Parameters.FileSystemControl.OutputBufferLength)
in the memcpy size. Or am I missing something?
Hey,
On 2014-10-31 10:22, akhaldi(a)svn.reactos.org wrote:
> @@ -90,6 +91,7 @@
> //Invalid parameter detected
> if (AllocAndLoadString(&lpIllegalMsg, GetModuleHandle(NULL), IDS_ILLEGAL_PARAM))
> _putts(lpIllegalMsg);
> + LocalFree(lpIllegalMsg);
> return FALSE;
> }
> }
>
This needs braces. Both puts and LocalFree should only be executed if
AllocAndLoadString succeeds (but return FALSE in either case).
Thanks!
Hi all,
As you can see in project-tools SVN, I've improved our Bash scripts for
Buildslaves. They're now also usable under Windows (in a Cygwin
environment) and I'm already doing this on our new Windows Buildslave
Carrier-Win7.
Bash on Windows may look hacky at first, but it's definitely more
comfortable than Batch! Moreover, we now only have a single version of
build scripts to maintain for all our Buildslaves!
This also involved some naming changes on the existing slaves to
maintain a consistent scheme. Tell me if anything broke.
Bringing all desired Windows builders back will still take some time.
I've only started with a RosBE-Windows based one right now and I need
your help here:
For some reason, VirtualBox 4.3.18 (used for reg-testing) doesn't want
to run headless. I can do a 'runas /user:buildbot VBoxManage controlvm
"ReactOS Testbot" poweroff' in a CMD and it will work well. The very
same command executed through BuildBot ends with:
====================================================================
VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Code E_ACCESSDENIED (0x80070005) - General access
denied error (extended info not available)
VBoxManage.exe: error: Most likely, the VirtualBox COM server is not
running or failed to start.
====================================================================
See
http://build.reactos.org/builders/Carrier-Win7%20VBox-Testbot/builds/6/step…
VBoxSVC.log isn't touched when BuildBot tries this command, so I have no
additional information.
Haven't found a solution yet, so I'm asking here if any of the VBox
experts know what could be going wrong.
Cheers,
Colin
Hello,
Let me invite you to the monthly status meeting taking place 30th of
October, 19:00 UTC (that's tomorrow!).
IRC service will only be started shortly before the meeting. 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. Hopefully it's not
much of inconvenience.
If someone still is not getting passwords sent before a meeting - please
email Pierre before the meeting started to get one.
Please send agenda proposals to me before the meeting, so that we can
start with a proposed agenda.
Regards,
Aleksey Bragin
On 2014-10-23 11:32, jgardou(a)svn.reactos.org wrote:
> - if ( dwFileSize < (sizeof(*dir) + sizeof(dir->idEntries[0])*(dir->idCount-1)) )
> + if (dwFileSize < (sizeof(*dir) + FIELD_OFFSET(CURSORICONFILEDIR, idEntries[dir->idCount])))
Did you mean to remove the sizeof(*dir)?
Am 22.10.2014 00:58, schrieb khornicek(a)svn.reactos.org:
> - if (LVText != NULL)
> + if (_tcslen(LVText))
> {
> WriteFile(hFile,
> LVText,
I think LVText might not be zero terminated, when the SendMessage call
fails.
What about if (dwTextLength != 0)?
On 2014-10-17 19.00, ros-dev-request(a)reactos.org wrote:
> Fastcall passes 64 bit arguments on the stack.
Aaagh.. I didn't know that.. Thanks for pointing it out.
IMO that's incredibly stupid, as a 32-bit CPU (or x64 running 32bit)
uses the register combination EAX:EDX for 64 bit integers, and
EAX:EDX is used for 64 bit return values (again in 32bit mode).
The compiler designers need to smarten up!
Best Regards
Love
> And yes, this is about an ntdll/ntoskrnl export, so we must be binary
> compatible with what Windows does.
> But the implementation that is normally used is an inline/intrinsic
> function anyway. This is just about the export (or rather, importing
> it).
>
> On 2014-10-17 00:24, Love Nystrom wrote:
>> >@Timo, @Thomas, @Ged
>> >
>> >Byte order swappers should always be fastcall for perfomance reasons.
>> >They have no need for the benefits of the cdecl call convention.
>> >Using cdecl in this case would make the binary code pitifully slow.
>> >
>> >Think about it for a bit.. Some pseudocode show what I mean:
>> >
>> >..CDECL...
>> >
>> > push hi
>> > push lo
>> > call Swapper
>> > mov dsthi, edx
>> > mov dstlo, eax
>> > add esp, 4
>> > ...
>> >
>> >// UINT64 __cdecl
>> >Swapper:
>> > push ebp
>> > mov ebp, esp
>> > mov eax, ebp+8 // lo
>> > mov eax, ebp+12 // hi
>> > bswap
>> > xchg eax, edx
>> > bswap
>> > pop ebp
>> > ret
>> >
>> >..FASTCALL...
>> >
>> > mov edx, hi
>> > mov eax, lo
>> > call Swapper
>> > mov dsthi, edx
>> > mov dstlo, eax
>> > ...
>> >
>> >// UINT64 __declspec(naked) __fastcall
>> >Swapper:
>> > bswap
>> > xchg eax, edx
>> > bswap
>> > ret
>> >
>> >Sadly the compiler designers were not (yet) clever enough
>> >to make the fastcall regs EAX, EDX, ECX, in that exact order,
>> >but even as it stands today..
>> >
>> >Swapper:
>> > mov eax, ecx
>> > bswap
>> > xchg eax, edx
>> > bswap
>> > ret
>> >
>> >
>> >(If you actually link against a binary swapper compiled out of your
>> >control with
>> >cdecl convention, the argument falls of course, as you must comply with
>> >the binary.)
>> >
>> >Keep up the good work..
>> >Best Regards
>> >// Love
>
Hi all,
As the question usually arises: The video of Daniel's and my ReactOS presentation at Kieler Linux Tage is online: http://youtu.be/oQsKzW_Rx3k
Do whatever you want with it ;)
This is probably the first ever ReactOS presentation held using ReactOS itself! And it worked like a charm!
We also met an author of German news site heise.de there, who wants to publish an article about the current state ReactOS soon.
Cheers,
Colin
On 2014-10-18 01:28, akhaldi(a)svn.reactos.org wrote:
> [CMAKE]
> * Make the minimum required version 2.8.
As Víctor just found out the hard way, using target_include_directories
makes our minimum version 2.8.11. Should we set that as the minimum to
create a more obvious error message?
Current error:
CMake Error at dll/keyboard/CMakeLists.txt:92 (target_include_directories):
Unknown CMake command "target_include_directories".
@Timo, @Thomas, @Ged
Byte order swappers should always be fastcall for perfomance reasons.
They have no need for the benefits of the cdecl call convention.
Using cdecl in this case would make the binary code pitifully slow.
Think about it for a bit.. Some pseudocode show what I mean:
..CDECL...
push hi
push lo
call Swapper
mov dsthi, edx
mov dstlo, eax
add esp, 4
...
// UINT64 __cdecl
Swapper:
push ebp
mov ebp, esp
mov eax, ebp+8 // lo
mov eax, ebp+12 // hi
bswap
xchg eax, edx
bswap
pop ebp
ret
..FASTCALL...
mov edx, hi
mov eax, lo
call Swapper
mov dsthi, edx
mov dstlo, eax
...
// UINT64 __declspec(naked) __fastcall
Swapper:
bswap
xchg eax, edx
bswap
ret
Sadly the compiler designers were not (yet) clever enough
to make the fastcall regs EAX, EDX, ECX, in that exact order,
but even as it stands today..
Swapper:
mov eax, ecx
bswap
xchg eax, edx
bswap
ret
(If you actually link against a binary swapper compiled out of your
control with
cdecl convention, the argument falls of course, as you must comply with
the binary.)
Keep up the good work..
Best Regards
// Love
What is the *root* reason for this problem (ok Ive seen in the comment,
paged code and holding spin lock, but it doesnt answer my question)?
Because Ive looked at our code of RtlEqualUnicodeString and I see that it
just calls RtlCompareUnicodeString that in turns just loops over the two
memory buffers, checks their contents (and in case we check for char case,
calls RtlUpcaseUnicodeChar). And RtlCompareMemory does that, too? What Im
missing?
Hermès.
-------------------------------------------------------------------------
Author: tfaber
Date: Thu Oct 16 16:40:13 2014
New Revision: 64762
URL: http://svn.reactos.org/svn/reactos?rev=64762&view=rev
Log:
[NPFS]
- Don't call RtlEqualUnicodeString (paged code) while holding a spin lock.
Powered by Driver Verifier.
Modified:
trunk/reactos/drivers/filesystems/npfs/waitsup.c
Modified: trunk/reactos/drivers/filesystems/npfs/waitsup.c
URL:
http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/filesystems/npfs/wa
itsup.c?rev=64762&r1=64761&r2=64762&view=diff
============================================================================
==
--- trunk/reactos/drivers/filesystems/npfs/waitsup.c [iso-8859-1]
(original)
+++ trunk/reactos/drivers/filesystems/npfs/waitsup.c [iso-8859-1] Thu Oct
16 16:40:13 2014
@@ -97,6 +97,22 @@
{
InitializeListHead(&WaitQueue->WaitList);
KeInitializeSpinLock(&WaitQueue->WaitLock);
+}
+
+static
+BOOLEAN
+NpEqualUnicodeString(IN PCUNICODE_STRING String1,
+ IN PCUNICODE_STRING String2)
+{
+ SIZE_T EqualLength;
+
+ if (String1->Length != String2->Length)
+ return FALSE;
+
+ EqualLength = RtlCompareMemory(String1->Buffer,
+ String2->Buffer,
+ String1->Length);
+ return EqualLength == String1->Length;
}
NTSTATUS
@@ -156,7 +172,8 @@
PipeName.MaximumLength = PipeName.Length;
}
- if (RtlEqualUnicodeString(&WaitName, &PipeName, FALSE))
+ /* Can't use RtlEqualUnicodeString with a spinlock held */
+ if (NpEqualUnicodeString(&WaitName, &PipeName))
{
/* Found a matching wait. Cancel it */
RemoveEntryList(&WaitIrp->Tail.Overlay.ListEntry);
On 2014-10-15 22:23, pschweitzer(a)svn.reactos.org wrote:
> +/* See:
> + -> http://msdn.microsoft.com/en-us/library/ms724228
> + -> http://bos.asmhackers.net/docs/filesystems/ntfs/standard.html#layout
> + */
> +VOID
> +NtfsDateTimeToFileTime(ULONGLONG NtfsTime,
> + PLARGE_INTEGER SystemTime)
> +{
> +
> + SystemTime->QuadPart = NtfsTime + 116444736000000000;
> +}
Doesn't NTFS use FILETIME directly? I thought that's the reason it's
called "file time" in the first place. ;)
Wikipedia says
"Date range: 1 January 1601 – 28 May 60056 (File times are 64-bit
numbers counting 100-nanosecond intervals (ten million per second)
since 1601, which is 58,000+ years)"
and your link doesn't seem to disagree.
tfaber(a)svn.reactos.org wrote:
> - DbgPrint(DbgString);
> + OutputDebugStringA(DbgString);
FYI, we had OutputDebugStringA there in the first place, but I changed
it to DbgPrint in r40147.
IIRC, output from DbgPrint was directly sent to the debug port while
OutputDebugStringA buffers the data first. This is especially bad, when
a test crashes the OS and we lose several kilobytes of log data before
they are printed out.
Probably, a DbgPrint("%s", DbgString) is the better alternative here.
- Colin
Windows does. Why shouldn't we? It's a non-documented API.
Best regards,
Alex Ionescu
On Sat, Oct 11, 2014 at 1:52 AM, <tkreuzer(a)svn.reactos.org> wrote:
> Author: tkreuzer
> Date: Sat Oct 11 08:52:33 2014
> New Revision: 64658
>
> URL: http://svn.reactos.org/svn/reactos?rev=64658&view=rev
> Log:
> [NTDLL]
> Don't assert that the caller of exported APIs passes correct parameters.
>
> Modified:
> trunk/reactos/dll/ntdll/ldr/ldrapi.c
>
> Modified: trunk/reactos/dll/ntdll/ldr/ldrapi.c
> URL:
> http://svn.reactos.org/svn/reactos/trunk/reactos/dll/ntdll/ldr/ldrapi.c?rev…
>
> ==============================================================================
> --- trunk/reactos/dll/ntdll/ldr/ldrapi.c [iso-8859-1] (original)
> +++ trunk/reactos/dll/ntdll/ldr/ldrapi.c [iso-8859-1] Sat Oct 11
> 08:52:33 2014
> @@ -209,9 +209,6 @@
> /* A normal failure */
> return STATUS_INVALID_PARAMETER_3;
> }
> -
> - /* Do or Do Not. There is no Try */
> - ASSERT((Disposition != NULL) || !(Flags &
> LDR_LOCK_LOADER_LOCK_FLAG_TRY_ONLY));
>
> /* If the flag is set, make sure we have a valid pointer to use */
> if ((Flags & LDR_LOCK_LOADER_LOCK_FLAG_TRY_ONLY) && !(Disposition))
>
>
>
The ASSERT is there because of the missing functionality. Please see the
comment just above.
Best regards,
Alex Ionescu
On Sun, Oct 5, 2014 at 2:57 AM, <jgardou(a)svn.reactos.org> wrote:
> Author: jgardou
> Date: Sun Oct 5 09:57:02 2014
> New Revision: 64537
>
> URL: http://svn.reactos.org/svn/reactos?rev=64537&view=rev
> Log:
> [NTOS/MM]
> - Do not assert in case of stack overflow, just let the page fault
> handler raise STATUS_STACK_OVERFLOW
>
> Modified:
> trunk/reactos/ntoskrnl/mm/ARM3/pagfault.c
>
> Modified: trunk/reactos/ntoskrnl/mm/ARM3/pagfault.c
> URL:
> http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/ARM3/pagfault.…
>
> ==============================================================================
> --- trunk/reactos/ntoskrnl/mm/ARM3/pagfault.c [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/mm/ARM3/pagfault.c [iso-8859-1] Sun Oct 5
> 09:57:02 2014
> @@ -82,7 +82,6 @@
> {
> /* We don't -- Windows would try to make this guard page valid
> now */
> DPRINT1("Close to our death...\n");
> - ASSERT(FALSE);
> return STATUS_STACK_OVERFLOW;
> }
>
>
>
>
Would be great to have JIRA issues associated to such fixes as well as a
test proving the change is correct. For example, are you merely assuming
that you should return "STATUS_NO_MEMORY", or do you know for a fact that
STATUS_CONFLICTING_ADDRESSES is the wrong code here?
Best regards,
Alex Ionescu
On Wed, Oct 8, 2014 at 12:38 AM, <tkreuzer(a)svn.reactos.org> wrote:
> Author: tkreuzer
> Date: Wed Oct 8 07:38:56 2014
> New Revision: 64595
>
> URL: http://svn.reactos.org/svn/reactos?rev=64595&view=rev
> Log:
> [NTOSKRNL]
> Fix a status code
>
> Modified:
> trunk/reactos/ntoskrnl/mm/ARM3/vadnode.c
>
> Modified: trunk/reactos/ntoskrnl/mm/ARM3/vadnode.c
> URL:
> http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/ARM3/vadnode.c…
>
> ==============================================================================
> --- trunk/reactos/ntoskrnl/mm/ARM3/vadnode.c [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/mm/ARM3/vadnode.c [iso-8859-1] Wed Oct 8
> 07:38:56 2014
> @@ -261,7 +261,7 @@
> {
> DPRINT1("Not enough free space to insert this VAD node!\n");
> KeReleaseGuardedMutex(&CurrentProcess->AddressCreationLock);
> - return STATUS_CONFLICTING_ADDRESSES;
> + return STATUS_NO_MEMORY;
> }
>
> ASSERT(StartingAddress != 0);
>
>
>
Seriously?
Am 11.10.2014 01:07, schrieb aandrejevic(a)svn.reactos.org:
> + /* Count the leading zeros */
> + while (!(Data->Mantissa & (1 << (63 - LeadingZeros)))) LeadingZeros++;
@Timo
Yes of course.. It was a fleeting idea it would be cute to run on a
computer 5x10x1 cm. ;-)
I didn't realize the ARM branch was in poor condition though.
But it stands to reason.. Porting Intel assembly to ARM assembly and
considering all the archiectural differences is/would be a gargantuan job.
Keep up the good work..
Love
On 2014-10-09 19.00, ros-dev-request(a)reactos.org wrote:
> Guys, I don't want to spoil your hopes, but native ARM support is far
> away from being usable. It doesn't even compile. There is no native ARM!
> And there won't be for ages, until we have a really knowledged ARM
> hacker, with the kernel and hardware knowledge of Alex, who would invest
> a huge lot of time into getting it up and running. So unless we want to
> hire someone fulltime for at least half a year, who would probably like
> to be paid a normal software engineer wage, which we cannot afford, we
> won't have ARM support anytime soon.
> x64 is a much more reasonable task, mostly lacking stuff in Mm.
> And that will still require a lot of work.
> And I have more than enough other things to do
On 2014-10-02 09:30, tkreuzer(a)svn.reactos.org wrote:
> -add_executable(dllimport_test
> +add_library(dllimport_test
> dllimport_framedyn.cpp)
Isn't the point of this test to check for linker errors?
A few remarks:
- There should be only one SEH, not for performance, but since the
KeyNameInfo->NameLength = 0; needs to be in SEH as well
- The function duplicates a lot of code from CmpConstructName, possibly
even incomplete
- There was already an implementation in the kernel-fun branch
Unrelated to your code, just something I spotted in that file:
- CmpQueryKeyData cannot be wrapped in SEH (it would cause reference
leaks on exception), but is wrapped in SEH in CmEnumerateKey
- CmpQueryKeyData does not use SEH, but is called with user mode
pointers from CmQueryKey
Timo
Am 29.09.2014 18:27, schrieb jgardou(a)svn.reactos.org:
> Author: jgardou
> Date: Mon Sep 29 16:27:16 2014
> New Revision: 64396
>
> URL: http://svn.reactos.org/svn/reactos?rev=64396&view=rev
> Log:
> [NTOS/CM]
> - Add NtQueryKey(KeyNameInformation) implementation.
> CORE-8581 #resolve
>
>
As PDF in Foxit Reader. But yeah ^^
Von Samsung Mobile gesendet
<div>-------- Ursprüngliche Nachricht --------</div><div>Von: Hermès BÉLUSCA - MAÏTO <hermes.belusca(a)sfr.fr> </div><div>Datum:24.09.2014 20:13 (GMT+01:00) </div><div>An: 'ReactOS Development List' <ros-dev(a)reactos.org> </div><div>Cc: </div><div>Betreff: Re: [ros-dev] Video of our ReactOS presentation online </div><div>
</div>Also, were you actually running your powerpoint presentation *in* ROS ?! :D
De : Ros-dev [mailto:ros-dev-bounces@reactos.org] De la part de Hermès BÉLUSCA - MAÏTO
Envoyé : mercredi 24 septembre 2014 19:37
À : 'ReactOS Development List'
Objet : Re: [ros-dev] Video of our ReactOS presentation online
Wow !! 43 minuten of video ^^
H.
De : Ros-dev [mailto:ros-dev-bounces@reactos.org] De la part de Colin Finck
Envoyé : mardi 23 septembre 2014 22:17
À : ros-dev(a)reactos.org
Objet : [ros-dev] Video of our ReactOS presentation online
Hi all,
As the question usually arises: The video of Daniel's and my ReactOS presentation at Kieler Linux Tage is online: http://youtu.be/oQsKzW_Rx3k
Do whatever you want with it ;)
This is probably the first ever ReactOS presentation held using ReactOS itself! And it worked like a charm!
We also met an author of German news site heise.de there, who wants to publish an article about the current state ReactOS soon.
Cheers,
Colin
Hello,
Let me invite you to the monthly status meeting taking place 25th of
September, 19:00 UTC. If there are any proposals regarding moving the
meeting date/time - please send them today.
IRC service will only be started shortly before the meeting. 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. Hopefully it's not
much of inconvenience.
If someone still is not getting passwords sent before a meeting - please
email Pierre before the meeting started to get one.
Please send agenda proposals to me before the meeting, so that we can
start with a proposed agenda.
Proposed agenda points so far:
- Agile missing in Jira (looks like an incompatible version)
- new on-demand builders (Clang, VC, x64, arm, branch, patch)
- testbot on a win 2003 machine
Let me know if any of those is already resolved. Thanks!
Regards,
Aleksey Bragin
Am 17.09.2014 11:54, schrieb jgardou(a)svn.reactos.org:
> Author: jgardou
> Date: Wed Sep 17 09:54:14 2014
> New Revision: 64176
>
> URL: http://svn.reactos.org/svn/reactos?rev=64176&view=rev
> Log:
> [GDI32]
> - Fix up values got from win32k in GetOutlineTextMetrics and do not fail if the provided buffersize is only sizeof(OUTLINETEXTMETRICW).
> CORE-8507 #resolve
>
> Modified:
> trunk/reactos/win32ss/gdi/gdi32/objects/font.c
>
> Modified: trunk/reactos/win32ss/gdi/gdi32/objects/font.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/win32ss/gdi/gdi32/objects/…
> ==============================================================================
> --- trunk/reactos/win32ss/gdi/gdi32/objects/font.c [iso-8859-1] (original)
> +++ trunk/reactos/win32ss/gdi/gdi32/objects/font.c [iso-8859-1] Wed Sep 17 09:54:14 2014
> @@ -9,8 +9,19 @@
>
> #include <precomp.h>
>
> +#include <math.h>
> +
> #define NDEBUG
> #include <debug.h>
> +
> +/* Rounds a floating point number to integer. The world-to-viewport
> + * transformation process is done in floating point internally. This function
> + * is then used to round these coordinates to integer values.
> + */
> +static __inline INT GDI_ROUND(FLOAT val)
> +{
> + return (int)floor(val + 0.5);
> +}
roundf() is the appropriate function here. The older MS crt headers
don't have the *round*() functions, but VS 2013 headers seem to have
them (according MSDN).
I propose adding them inside some #ifdef, instead of reimplementing them
in different places.
For the other functions: strange coding style. Is this taken from wine?
Hi,
I'd like to propose some topics for the next meeting:
- Agile missing in Jira (looks like an incompatible version)
- new on-demand builders (Clang, VC, x64, arm, branch, patch)
- testbot on a win 2003 machine
Timo
Awesome stuff!
Am 11.09.2014 22:55, schrieb jgardou(a)svn.reactos.org:
> Author: jgardou
> Date: Thu Sep 11 20:55:42 2014
> New Revision: 64121
>
> URL: http://svn.reactos.org/svn/reactos?rev=64121&view=rev
> Log:
> [KDGDB]
> - introduce KDGDB, a KDCOM-like DLL, wrapping the KD protocol and the GDB remote protocol together.
> It is not fully functional, but for now it permits source-level debugging in some modules. More will be added as I feel the need and find the time to work a bit more on it. (That is, unless an angel comes and resume the work)
> To use it, set GDB and _WINKD_ to TRUE in your CMakeCache.txt. Using separate debug symbols is also a good idea.
>
>
while(1); is not really a good solution. It should be something that is
visible in GDB.
But I fear that a KeBugCheck() won't work here, since it will rely on a
working KD connection.
Maybe a KD_ASSERT() macro, that calls KdAssert() on failure or
something, resets the GDB connection somehow, issues a debug print and
then halts.
Am 12.09.2014 22:23, schrieb jgardou(a)svn.reactos.org:
> Author: jgardou
> Date: Fri Sep 12 20:23:08 2014
> New Revision: 64127
>
> URL: http://svn.reactos.org/svn/reactos?rev=64127&view=rev
> Log:
> [KDGDB]
> - Add a callback mechanism permitting to "simulate" KD send <-> receive loop without having to actually communicate to GDB
> - Use that to update the program counter when cont'ing a breakpoint
> Now cont'ing an assertion failure is possible, since we actually get beyond the int 3 instruction
>
> Modified:
> trunk/reactos/drivers/base/kdgdb/gdb_input.c
> trunk/reactos/drivers/base/kdgdb/kdgdb.h
> trunk/reactos/drivers/base/kdgdb/kdpacket.c
>
> +)
> +{
> + DBGKD_MANIPULATE_STATE64* State = (DBGKD_MANIPULATE_STATE64*)MessageHeader->Buffer;
> +
> + /* We just confirm that all went well */
> + if ((PacketType != PACKET_TYPE_KD_STATE_MANIPULATE)
> + || (State->ApiNumber != DbgKdSetContextApi)
> + || (State->ReturnStatus != STATUS_SUCCESS))
> + {
> + /* Should we bugcheck ? */
> + while (1);
> + }
> +}
> +
> +static
> +KDSTATUS
> +SetContext(
> + _Out_ DBGKD_MANIPULATE_STATE64* State,
> + _Out_ PSTRING MessageData,
> + _Out_ PULONG MessageLength,
> + _Inout_ PKD_CONTEXT KdContext,
> + _In_opt_ KDP_MANIPULATESTATE_HANDLER ManipulateStateHandler
> +)
> +{
> + State->ApiNumber = DbgKdSetContextApi;
> + State->Processor = CurrentStateChange.Processor;
> + State->ReturnStatus = STATUS_SUCCESS;
> + State->ProcessorLevel = CurrentStateChange.ProcessorLevel;
> + MessageData->Length = sizeof(CurrentContext);
> +
> + if (MessageData->MaximumLength < sizeof(CurrentContext))
> + {
> + while (1);
> + }
> +
>
Making the member conditional but writing to it unconditionally seems
like it would overflow the stack variable on GCC?
On 2014-09-07 23:40, tkreuzer(a)svn.reactos.org wrote:
> +#ifdef __clang__
> + void *ReturnAddress;
> #endif
> + /* Safe the return address */
> + mov ebx, [esp]
> + mov [eax + SEH3_REGISTRATION_FRAME_ReturnAddress], ebx
Am 01.09.2014 01:00, schrieb hbelusca(a)svn.reactos.org:
> Author: hbelusca
> Date: Sun Aug 31 23:00:29 2014
> New Revision: 64017
>
> URL: http://svn.reactos.org/svn/reactos?rev=64017&view=rev
> Log:
> [BOOTVID]
> - Synchronize correctly arm/bootdata.c with i386, as it was done previously.
Why is that file duplicated at all, if the contents are identical?
This seems strange. I understand that NT 5.x has a limitation of 64 MB MDLs on x86, but direct I/O was designed for exactly this case of large I/O operations. Has anyone verified that 2k3 doesn’t do MDL chaining for direct I/O when the transfer is larger than a single MDL can hold?
Also aren’t there changes to the IRP dispatch routines required to cope with not having an Irp->MdlAddress pointer anymore?
Cameron
From: tfaber(a)svn.reactos.org
Sent: Tuesday, August 26, 2014 6:41 AM
To: ros-diffs(a)reactos.org
Author: tfaber
Date: Tue Aug 26 13:41:57 2014
New Revision: 63953
URL: http://svn.reactos.org/svn/reactos?rev=63953&view=rev
Log:
[FASTFAT]
- Do not use direct I/O since it limits read/write operations to 64 MB
CORE-8410 #resolve
Modified:
trunk/reactos/drivers/filesystems/fastfat/fsctl.c
Modified: trunk/reactos/drivers/filesystems/fastfat/fsctl.c
URL: http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/filesystems/fastfa…
==============================================================================
--- trunk/reactos/drivers/filesystems/fastfat/fsctl.c [iso-8859-1] (original)
+++ trunk/reactos/drivers/filesystems/fastfat/fsctl.c [iso-8859-1] Tue Aug 26 13:41:57 2014
@@ -442,8 +442,7 @@
goto ByeBye;
}
- DeviceObject->Flags = DeviceObject->Flags | DO_DIRECT_IO;
- DeviceExt = (PVOID) DeviceObject->DeviceExtension;
+ DeviceExt = DeviceObject->DeviceExtension;
RtlZeroMemory(DeviceExt, ROUND_UP(sizeof(DEVICE_EXTENSION), sizeof(ULONG)) + sizeof(HASHENTRY*) * HashTableSize);
DeviceExt->FcbHashTable = (HASHENTRY**)((ULONG_PTR)DeviceExt + ROUND_UP(sizeof(DEVICE_EXTENSION), sizeof(ULONG)));
DeviceExt->HashTableSize = HashTableSize;
On 2014-08-24 15:28, jgardou(a)svn.reactos.org wrote:
> -// FT_Set_Pixel_Sizes(ft_face,
> -// TextObj->logfont.elfEnumLogfontEx.elfLogFont.lfWidth,
> + FT_Set_Pixel_Sizes(ft_face,
> + TextObj->logfont.elfEnumLogfontEx.elfLogFont.lfWidth,
The abs() was added in the second version of the patch because this
way it breaks tests.
See https://jira.reactos.org/browse/CORE-4657?focusedCommentId=60379&page=com.a…
On 2014-08-24 17:40, hbelusca(a)svn.reactos.org wrote:
> + mciSendCommand(wDeviceId, MCI_PUT, MCI_DGV_PUT_DESTINATION | MCI_DGV_RECT | MCI_WAIT, (DWORD)&mciPut);
A DWORD cannot fit a pointer. This function takes DWORD_PTR.
Dear all,
As you've certainly noticed, one of our main servers providing the
www.reactos.org website along with JIRA and FishEye was down yesterday.
Problems began yesterday around 13:00 UTC and lasted till some minutes ago.
This has happened due to a severe hardware failure on the hypervisor
machine serving the affected VMs. Our hosting provider needed two
attempts to find and replace the failed hardware.
Finally, the crash has caused one database table to get corrupted. This
one was repaired just now. No data has been lost though.
All services should be up again now. If you still notice anything not
working, please report to me.
We're sorry for the caused inconveniences!
Best regards,
--
Colin Finck
System & Network Administrator
ReactOS Deutschland e.V.
TL;DR
=====
Your SVN account == "ReactOS development account", because it will be
used for more services than just SVN. You can now change the password on
your own at https://lam.reactos.org
Hi all,
I've been trying to centralize our user accounts for some time now and
finally have something to show. Your known SVN credentials have been
imported into an LDAP-based user directory now.
This gives us the ability to easily plug various services for developers
into the directory: SVN, BuildBot, the participant list for meetings,
especially the upcoming services like Mumble, development VMs and file
sharing.
You can view your account details and change your password on your own
now. Just visit https://lam.reactos.org to do so. The E-Mail address
shown there will be used e.g. for sending meeting invitations.
As we all want the migration to go flawlessy, I've set up a temporary
SVN repository at svn://svn.reactos.org/sasltest
This should work just like our "reactos" repository: If you have write
access there, you have write access in "sasltest" as well. It already
works well for me and my SVN client, but I want confirmations from
others too. Please do so by committing some junk into sasltest :)
We have some members, who don't have SVN write access but participate in
the monthly meetings. They will shortly receive an E-Mail with their
account details. That doesn't give you SVN write access though, it's
just for participating in the meetings for now :P
I'll keep you informed when we finally plug our main repositories into
the LDAP database.
Note that this doesn't change anything with the ReactOS Website accounts
and IServ mail accounts. Former ones will always be in a separate
database as everybody can sign up there.
Cheers,
Colin
On 2014-08-04 18:25, hbelusca(a)svn.reactos.org wrote:
> [KERNEL32]
> Add a bunch of missing _SEH_YIELD in 'return' clues in _SEH_TRY clauses.
That should be pointless with PSEH3. I believe Timo has in fact been
removing them.
Hello,
Let me invite you to the monthly status meeting taking place tomorrow,
31st of July, 19:00 UTC. If there are any proposals regarding moving the
meeting date/time - please send them today.
IRC service will only be started shortly before the meeting. 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. Hopefully it's not
much of inconvenience.
If someone still is not getting passwords sent before a meeting - please
email Pierre before the meeting started to get one.
Please send agenda proposals to me before the meeting, so that we can
start with a proposed agenda.
Also all developers, please, may I so kindly ask you to prepare a very
brief one-two lines message containing two things:
1. What you did since the previous meeting
2. What you are going to do in the coming month
This is needed to understand who is working on what, to plan things, etc.
Prepare that in advance! Everyone will have max 1 minute!
Regards,
Aleksey Bragin
Hi all,
Fezile, one of our servers in Sweden, unexpectedly disappeared after a
reboot today. Unfortunately, this is one of our older servers without an
IPMI module, so we have to wait till it's rebooted manually. I'll keep
you informed when this is done.
The server outage affects the following services:
* iso.reactos.org
* doxygen.reactos.org
* cppcheck.reactos.org
* VMware Player Test slave
* VMware Player Patchbot
We apologize for the inconveniences!
If you have any idea where we can still get a suitable IPMI module for
these servers, we would be highly interested!
The needed models are ASUS ASMB3 and Tyan M3291.
Best regards,
Colin Finck
Daniel, do you have a written permission to put these third-party files
under LGPL? Which is essentially what you're doing when adding the files
to our cards.dll.
Same goes for the Bavarian cards and decks. I doubt they have been put
in the public domain..
We already needed to "fix" cards.dll once for not using GPLed cards,
let's not repeat this again.
- Colin
That name seems slightly misleading (PFN is usually associated with
physical ranges, this is a virtual range). Maybe something like
MM_VPN_BITS_SIZE would be better.
If it is not used anywhere else, I'd just use an #ifdef _WIN64 ...
(assuming it's the same for all 32 bit and the same for all 64 bit
architectures)
Am 30.07.2014 15:11, schrieb jgardou(a)svn.reactos.org:
> +#define MM_PAGE_FRAME_NUMBER_SIZE 52
Hi guys!
Good news!
ReactOS has been featured in RedUsers, one of the best southamerican IT blogs.
http://www.redusers.com/noticias/entrevista-reactos-clon-windows-open-sourc…
Of course it has spread fast as powder around all blogs there:
http://goo.gl/BovDKU
Hopefuly tomorrow I will have the Shop online and running (we can't miss the strike!) with my account or the German one, whatever happens first.
Cool USBs ReactOS Community Special Edition! You can't miss it!
Best regards,
Victor
Hello,
Let me invite you to the monthly status meeting taking place next
Thursday, 3rd of July, 19:00 UTC.
The meeting is one week off from the classic scheme due to various
reasons (previous meeting was too close, and, you know, Germany - USA on
Thursday).
IRC service will only be started shortly before the meeting. 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. Hopefully it's not
much of inconvenience.
If someone still is not getting passwords sent before a meeting - please
email Pierre before the meeting started to get one.
Please send agenda proposals to me before the meeting, so that we can
start with a proposed agenda.
Also all developers, please, may I so kindly ask you to prepare a very
brief one-two lines message containing two things:
1. What you did since the previous meeting
2. What you are going to do in the coming month
This is needed to understand who is working on what, to plan things,
etc. Thanks, I hope it's not that much to ask for.
Prepare that in advance! Everyone will have max 1 minute!
Regards,
Aleksey Bragin
Am 25.06.2014 00:18, schrieb jgardou(a)svn.reactos.org:
> - * Copyright 2006 Hervé Poussineau
> + * Copyright 2006 Herv� Poussineau
I think you are not using UTF-8.
On 15/06/2014 19:47, hbelusca(a)svn.reactos.org wrote:
> + /* Trick: on Windows, pressing the CTRL key forces the task to be ended */
> + BOOL ForceEndTask = !!(GetKeyState(VK_CONTROL) & 0x8000);
> +
Was it really meant to be '!!'?
--
Pierre Schweitzer<pierre at reactos.org>
System Administrator
ReactOS Foundation
All is down!
> Fixed.
>
> On 15/06/2014 00:56, Alexander Rechitskiy wrote:
>
>> https://code.reactos.org/ does NOT work
>> 15.06.2014, 02:40, "Pierre Schweitzer" <pierre(a)reactos.org>:
>>> As a side note, upgrade to Fisheye 3.4.4 didn't fix ONLINE-461 (which was the
>>> main reason behind the upgrade).
>>>
>>> On 15/06/2014 00:36, Zachary Gorden wrote:
>>>> Fisheye was upgraded successfully, Jira went off the rails and took us
>>>> about three hours to recover from. Please report any data loss as we had to
>>>> restore from backups.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Ros-dev mailing list
>>>> Ros-dev(a)reactos.org <mailto:Ros-dev@reactos.org>
>>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>
>>>
>>> --
>>> Pierre Schweitzer<pierre at reactos.org>
>>> System Administrator
>>> ReactOS Foundation
>>> ,
>>>
>>> _______________________________________________
>>> Ros-dev mailing list
>>> Ros-dev(a)reactos.org <mailto:Ros-dev@reactos.org>
>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>
>> --
>> Best regards,
>>
>> _______________________________________________
>> Ros-dev mailing list
>> Ros-dev(a)reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>
> --
> Pierre Schweitzer<pierre at reactos.org>
> System Administrator
> ReactOS Foundation
--
--
Best regards,
Fisheye was upgraded successfully, Jira went off the rails and took us
about three hours to recover from. Please report any data loss as we had to
restore from backups.
This helps find logic errors, mostly where the programmer thought the
variable was signed but it's actually unsigned, e.g. if (ret < 0) for a
function that returns (ULONG)-1.
I also don't see how the fix would be complicated in most cases.
(x <= 0) becomes (x == 0), (x < 0) becomes (x == (ULONG)-1) or whatever
(after a logic review).
I know that it'll be problematic if resulting from a macro... but I
think it's worth finding a workaround for those cases.
Most of the warnings I remember from our code base though (especially
ntoskrnl) didn't involve macros and were actually cases of questionable
logic... although maybe I recall incorrectly.
On 2014-05-31 23:26, tkreuzer(a)svn.reactos.org wrote:
> [CMAKE] Get rid of -Wtype-limits, it's noisy, it doesn't provide any reasonable benefit and it's almost impossible to "fix" these warnings without huge haxxory.
Hello,
Let me invite you to the monthly status meeting taking place first
Thursday of this month, 5th of June, 19:00 UTC. And this date is very
close to now! The meeting was rescheduled from the usual date because of
my trips and my illness. Sorry about that.
IRC service will only be started shortly before the meeting. 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. Hopefully it's not
much of inconvenience.
If someone still is not getting passwords sent before a meeting - please
email Pierre before the meeting started to get one.
Please send agenda proposals to me before the meeting, so that we can
start with a proposed agenda. However the most demanded topic is ReactOS
fundraising campaign and its outcome :-)
Also all developers, please, may I so kindly ask you to prepare a very
brief one-two lines message containing two things:
1. What you did since the previous meeting
2. What you are going to do in the coming month
This is needed to understand who is working on what, to plan things,
etc. Thanks, I hope it's not that much to ask for.
Regards,
Aleksey Bragin
Hi,
I'm working on network virtualization support in ReactOS.
At this time, PoC works but I reach a point where I need a solution that would allow to add and remove TAP (TAP-Win32 from OpenVPN for exemple) Network Devices from kernel space, without user intervention.
The problem right now is that there seems to be impossible in ReactOS to have a proper way or tips and tricks to add/remove TAP devices without rebooting the system. What should be fixed/edit to instanciate of TAP device on the fly on the current implementation (r63193) ?
Thanks
--
Daniel Maxime
Linux version 3.6.9-maxux64 (emy) (gcc version 4.7.3 (Gentoo 4.7.3-r1 p1.4, pie-0.5.5) ) #3 SMP PREEMPT Wed Feb 19 16:40:22 CET 2014
17:15:01 up 1 day, 1:44, 1 user, load average: 0.29, 0.28, 0.35
On 2014-05-20 23:11, tkreuzer(a)svn.reactos.org wrote:
> --- trunk/reactos/ntoskrnl/mm/ARM3/virtual.c [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/mm/ARM3/virtual.c [iso-8859-1] Tue May 20 21:11:43 2014
> @@ -4593,8 +4593,8 @@
> // on the user input, and then compute the actual region size once all the
> // alignments have been done.
> //
> + EndingAddress = (((ULONG_PTR)PBaseAddress + PRegionSize - 1) | (PAGE_SIZE - 1));
> StartingAddress = (ULONG_PTR)PAGE_ALIGN(PBaseAddress);
> - EndingAddress = (((ULONG_PTR)PBaseAddress + PRegionSize - 1) | (PAGE_SIZE - 1));
> PRegionSize = EndingAddress - StartingAddress + 1;
>
> //
Can you explain this a bit? I don't see any logic change.
>[LSASRV]
>
>- Just run again the loop if LsarOpenAccount call failed (that also
>avoids a call to LsarClose on a NULL handle, that is trapped by the
>kdbg if one enabled "set condition * first always").
>
>- Free the memory and the opened handles before returning in case of
>failure of LsapAddPrivilegeToTokenPrivileges. Maybe this cleaning step
>can be done more elegantly.
>
>Eric, can you please review that? It should be good I think.
The change is OK!
This is not the right solution. SVN has terrible UTF-16 handling so we
should not convert these back to UTF-16.
https://jira.reactos.org/browse/CORE-7703https://jira.reactos.org/browse/CORE-8221
On 2014-05-25 22:17, cwittich(a)svn.reactos.org wrote:
> Author: cwittich
> Date: Sun May 25 20:17:25 2014
> New Revision: 63452
>
> URL: http://svn.reactos.org/svn/reactos?rev=63452&view=rev
> Log:
> [bootdata]
> convert hivecls.inf and hivedef.inf to UTF16LE
> fixes CORE-7614
>
> Modified:
> trunk/reactos/boot/bootdata/hivecls.inf (contents, props changed)
> trunk/reactos/boot/bootdata/hivedef.inf (contents, props changed)
>
I would like to applaud Eric for his outstanding work with ROS partition
handling, which we are able to experience since recently. Eric himself
had tested this code including GParted, but i`ve that is not all. 7z is
able to read FAT partition image files, but this didn't work at all.
Right now i was able to open up ROS vmdk image, created by ReactOS
itself and view/extract anything of its contents. I cannot express
enough how handy this is going to be, allowing to access ROS vm hard
disk contents without the pesky hdd mounting (which never really work
reliably for me), transferring anything out of the vm by LAN/Internet or
booting other VM with those HDDs co-mounted.
Simply I cannot thank you enough for your work.
Pic included as proof.
--
With best regards
Caemyr
Lol so maybe you should think twice next time you see "FIXFIX REACTOS
HACK" like I originally wrote it ;-)
Best regards,
Alex Ionescu
On Sat, May 17, 2014 at 4:42 PM, <ekohl(a)svn.reactos.org> wrote:
> Author: ekohl
> Date: Sat May 17 14:42:28 2014
> New Revision: 63330
>
> URL: http://svn.reactos.org/svn/reactos?rev=63330&view=rev
> Log:
> [NTOSKRNL]
> Partial revert of r63326! The correct partition numbers cause boot failures.
>
> Modified:
> trunk/reactos/ntoskrnl/fstub/disksup.c
>
> Modified: trunk/reactos/ntoskrnl/fstub/disksup.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/fstub/disksup.c?r…
> ==============================================================================
> --- trunk/reactos/ntoskrnl/fstub/disksup.c [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/fstub/disksup.c [iso-8859-1] Sat May 17 14:42:28 2014
> @@ -1655,7 +1655,9 @@
> UInt32x32To64(GET_PARTITION_LENGTH(PartitionDescriptor),
> SectorSize);
>
> - PartitionInfo->PartitionNumber = (!IsContainerPartition(PartitionType)) ? i : 0;
> + // BUGBUGBUG: The correct partition numbers seem to cause boot failures!!!
> +// PartitionInfo->PartitionNumber = (!IsContainerPartition(PartitionType)) ? i : 0;
> + PartitionInfo->PartitionNumber = i + 1;
> }
> else
> {
>
>
Hi everybody!
During some little maintenance of rosapps I was doing during some work
pause, I wanted to know from where we found our still unused (until someone
programs the defragmentation API :P) defragger called Fraginator. Since it
doesnt contain any information about his initial author I tried to check
into the SVN log, and I found that it was added in our codebase in 2006 by
Ged: see the commit log http://svn.reactos.org/svn/reactos?view=revision
<http://svn.reactos.org/svn/reactos?view=revision&revision=21411>
&revision=21411 ; notice that the committer mentioned that [Fraginator] is
pretty hard to come by on the net now. Nevertheless nothing is said about
his author.
However (!!) googling at fraginator defragger, I fell on this webpage,
certainly written by the actual Fraginator author:
http://blog.getpaint.net/2012/03/28/college-adventures-in-open-source-fragin
ator-edition/ . In this blog entry you have the story of the Fraginator
defragger! (if someone can add an entry, he/shes welcome).
Nice reading!
Hermès.
Hi Christoph !
Are you sure that before committing this fix in Wine code, you: 1- made a
patch to wine's code, 2- sent it to them, and 3- checked that they merged
too in their code base? Because otherwise your fix here might be lost in the
next Wine code sync...
Cheers,
Hermès.
-----Message d'origine-----
Author: cwittich
Date: Sun May 11 05:04:56 2014
New Revision: 63225
URL: http://svn.reactos.org/svn/reactos?rev=63225&view=rev
Log:
[comctl32]
Notify the parent on a return key press.
fixes return key in device manager
Modified:
trunk/reactos/dll/win32/comctl32/treeview.c
Modified: trunk/reactos/dll/win32/comctl32/treeview.c
URL:
http://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/comctl32/treeview
.c?rev=63225&r1=63224&r2=63225&view=diff
============================================================================
==
--- trunk/reactos/dll/win32/comctl32/treeview.c [iso-8859-1] (original)
+++ trunk/reactos/dll/win32/comctl32/treeview.c [iso-8859-1] Sun May 11
05:04:56 2014
@@ -5242,6 +5242,10 @@
newSelection = TREEVIEW_GetNextListItem(infoPtr, prevItem);
break;
+ case VK_RETURN:
+ TREEVIEW_SendSimpleNotify(infoPtr, NM_RETURN);
+ break;
+
case VK_HOME:
newSelection = infoPtr->root->firstChild;
break;
Am 09.05.2014 03:57, schrieb hbelusca(a)svn.reactos.org:
> Author: hbelusca
> Date: Fri May 9 01:57:43 2014
> New Revision: 63202
>
> URL: http://svn.reactos.org/svn/reactos?rev=63202&view=rev
> Log:
> [RPCRT4]
> Detect whether we are connecting to a pipe on the local machine and use the \\.\ prefix instead of the full machine name.
> This patch modifies ReactOS-specific code (that was introduced by Eric in revision 53630) (Wine still supports only local pipes), so I also update our rpcrt4_ros.diff file accordingly, r63201 with respect to the latest Wine 1.7.17 rpcrt4 code.
> Modified: trunk/reactos/dll/win32/rpcrt4/rpcrt4_ros.diff
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/rpcrt4/rpcrt4_ro…
> ==============================================================================
> [...]
>
> +diff -prudN .\wine\dlls\rpcrt4/msvc.S .\reactos\dll\win32\rpcrt4/msvc.S
> +--- .\wine\dlls\rpcrt4/msvc.S 1970-01-01 01:00:00.000000000 +0100
> ++++ .\reactos\dll\win32\rpcrt4/msvc.S 2012-02-14 21:27:35.943001900 +0100
> +@@ -0,0 +1,146 @@
>
> +diff -prudN .\wine\dlls\rpcrt4/precomp.h .\reactos\dll\win32\rpcrt4/precomp.h
> +--- .\wine\dlls\rpcrt4/precomp.h 1970-01-01 01:00:00.000000000 +0100
> ++++ .\reactos\dll\win32\rpcrt4/precomp.h 2014-03-14 01:43:22.357516600 +0100
>
> +diff -prudN .\wine\dlls\rpcrt4/unix_func.c .\reactos\dll\win32\rpcrt4/unix_func.c
> +--- .\wine\dlls\rpcrt4/unix_func.c 1970-01-01 01:00:00.000000000 +0100
> ++++ .\reactos\dll\win32\rpcrt4/unix_func.c 2013-01-25 00:19:53.278052800 +0100
Why add these to the diff?
Hi,
http://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/msgina/gui.c?r1=…
Is there a point in that DuplicateHandle call?
"When SetThreadDesktop is called the system closes the desktop handle
when needed
so we have to create a new handle because this handle may still be in
use by winlogon"
Sorry, I re-read that comment a few times and still can't understand. I
take it that SetThreadDesktop closes the old handle which was set
before. And it may, for some reason, be used by winlogon. Shouldn't that
be a place to fix, rather than the hack in r58367?
And why is the SetThreadDesktop(OldDesk) is removed by this revision?
Regards,
Aleksey Bragin
On 2014-04-29 13:14, dquintana(a)svn.reactos.org wrote:
> [SHELL32]
> * Make use of IID_NULL_PPV_ARG in all the calls to GetUIObjectOf, and fix one instance of mismatched riid/pointer.
I don't see that mismatch. What am I missing? ;)
Let's bring up the webOS topic again. There is an interesting idea to port Nyx portability layer to Win32 and thus make Open webOS running in ReactOS/Windows. Nice user interface would be a benefit!
http://www.openwebosproject.org/docs/architecture#.U1l8Uvl_vTo
--
Best regards,
Alexander Reachitskiy
Hello,
Let me invite you to the monthly status meeting taking place last
Thursday of this month, 24th of April, 19:00 UTC. And this date is very
close to now!
IRC service will only be started shortly before the meeting. 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. Hopefully it's not
much of inconvenience.
If someone still is not getting passwords sent before a meeting - please
email Pierre before the meeting started to get one.
Please send agenda proposals to me before the meeting, so that we can
start with a proposed agenda.
Regards,
Aleksey Bragin
On 2014-04-22 22:46, aandrejevic(a)svn.reactos.org wrote:
> --- branches/ntvdm/subsystems/ntvdm/ntvdm.c [iso-8859-1] (original)
> +++ branches/ntvdm/subsystems/ntvdm/ntvdm.c [iso-8859-1] Tue Apr 22 20:46:50 2014
> @@ -196,6 +197,11 @@
> EmulatorInterrupt(0x23);
> break;
> }
> + case CTRL_LAST_CLOSE_EVENT:
> + {
> + if (CommandThread) TerminateThread(CommandThread, 0);
> + break;
> + }
> default:
> {
> /* Stop the VDM if the user logs out or closes the console */
Wasn't there an event to tell that thread to exit?
Using TerminateThread like this feels icky.
Hey!
That's indeed a typo!
Can someone commit a fix? I can't before Monday evening.
Thanks!
Pierre
-------- Message original --------
Objet : Re: [ros-dev] [ros-diffs] [pschweitzer] 62779: [CDFS] Convert FCB pathname from simple buffer to unicode string. Please carefully review if I missed something
De : Alexander Andrejevic <theflash(a)sdf.lonestar.org>
À : ReactOS Development List <ros-dev(a)reactos.org>
Cc :
Hi,
Correct me if I'm wrong, but the original version didn't modify the string length.
Are you sure that should be "=" and not "=="?
Regards,
Alex
On Sat, Apr 19, 2014 at 09:31:44AM +0200, Thomas Faber wrote:
> On 2014-04-18 23:40, pschweitzer(a)svn.reactos.org wrote:
> > --- trunk/reactos/drivers/filesystems/cdfs/fcb.c [iso-8859-1] (original)
> > +++ trunk/reactos/drivers/filesystems/cdfs/fcb.c [iso-8859-1] Fri Apr 18 21:40:02 2014
> > @@ -129,7 +131,7 @@
> > BOOLEAN
> > CdfsFCBIsRoot(PFCB Fcb)
> > {
> > - return(wcscmp(Fcb->PathName, L"\\") == 0);
> > + return (Fcb->PathName.Length = sizeof(WCHAR) && Fcb->PathName.Buffer[0] == L'\\');
> > }
>
> ==
>
>
>
> Generally I'm seeing a lot of manual work where
> RtlInitEmptyUnicodeString and RtlCopyUnicodeString could be used.
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
--
Alexander Andrejevic <theflash(a)sdf.lonestar.org>
SDF Public Access UNIX System - http://sdf.lonestar.org
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
I couldn't resist. As a publisher...maybe you shouldn't run ad block eh? :)
On Thu, Apr 17, 2014 at 12:09 AM, Sergey Bugaev (JIRA)
<noreply(a)reactos.org>wrote:
>
> [
> http://jira.reactos.org/browse/ONLINE-446?page=com.atlassian.jira.plugin.sy…]
>
> Sergey Bugaev resolved ONLINE-446.
> ----------------------------------
>
> Resolution: Cannot Reproduce
>
> > "Prove you are a human" game is hidden by AdBlock
> > -------------------------------------------------
> >
> > Key: ONLINE-446
> > URL: http://jira.reactos.org/browse/ONLINE-446
> > Project: ReactOS Online Service
> > Issue Type: Improvement
> > Reporter: Sergey Bugaev
> > Assignee: Aleksey Bragin
> >
> > https://www.reactos.org/user/register (use incognito mode or just log
> out to see the issue)
> > There is a game to prove you are a human.
> > However if you are using AdBlock (
> https://chrome.google.com/webstore/detail/adblock/gighmmpiobklfepjocnamgkkb…,
> the most popular Chrome extension with more than 15 million users) the game
> is not visible, so newcomer can't register.
> > The error message is "You didn't pass the game", which is not very
> informative in that case.
> > Should be something like "You didn't pass the game, try disabling
> AdBlock to see it". The best solution would be making the game visible
> anyway.
> > Tested in Google Chrome
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
> _______________________________________________
> Ros-bugs mailing list
> Ros-bugs(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-bugs
>
Dear all,
In case you don't use SSL/TLS on our infrastructure (web sites - drupal,
jira, fisheye), skip reading (and reconsider your choices about such
non-usage).
As you may (should?) have heard recently, OpenSSL has suffered a
critical security vulnerability (CVE-2014-0160), known as Heartbleed Bug
(http://heartbleed.com/). Most of our services were using an affected
release of OpenSSL, with heartbeat feature activated. Be it, mails
services, web services (Drupal, Jira).
We reacted quickly passed the public announcement, and the availability
of the fix to apply it on our infrastructure to limit the risks. Anyway,
this might have been enough (actually, the issue has been here for two
years!) to allow potentials attackers to, for instance, steal our SSL
private keys. So, we took the decision to renew all our certificates and
private keys to guarantee safe infrastructure usage.
Due to the nature of the security issue, we don't know what may have
been compromised in the infrastructure and in the user database. Hence
our drastic measures.
What does it mean for you? It means that your account information
(username + password) might have been compromised, and your account
itself could have been compromised (cookie stealth with the attack).
We highly recommend you to change your passwords and check that
everything is fine on your account. I shall remind you that password
change can take up to 6h to propagate to Fisheye & Jira.
As a side note, we enabled a while ago Perfect Forward Secrecy on our
infrastructure that should ensure that even if our private keys leaked,
your past communications (so, login on the infrastructure, for instance)
can't be deciphered. Unless your session ticket leaked as well...
We are really sorry for the caused inconvenience. I'm available by email
or on IRC to answer your questions and clear your doubts.
With my best regards,
--
Pierre Schweitzer<pierre at reactos.org>
System Administrator
ReactOS Foundation
Hi all,
With this few words I would like to share the joyous event of MMIO-based
serial port implementation
has finally worked for me.
This is the equivalent of earlycon serial port implementation in Linux with
some extension
(so now it is even better then Linux one)
Some work yet is needed to be done to transform the work into the normal
patch, but the good news is
it is working, and still doesn't require PNPmanager for work, i.e. it
starts very early in kernel and writes kernel log messages.
I use ExpressCard 34 extension board Serial RS232 port, on laptop,
but think it will work fro PC Cards too (former name PCMCIA).
==Importance: Touching the hardware==
For the more developers we need more working PC models ( Real Hardware)
Almost all modern PCs are laptops with PCIe bus (the rest are desktops)
(but few of them able to boot the ReactOS)
Modern serial ports are recommended to use /often use MMIO-based data
transfer instead of former I/O ports.
So now possibility appears to debug these new computers and force the
ReactOS to work on this important part of new PCs.
Thanks for attention
-Minas Abrahamyan
PS Curious note: for catching the debug logs I use the (small and cheap)
soap box-sized microcontroller board with LCD (ready-unit), and I call it
"ReactOS debug logger" appliance. It doesn't take space and doesn't produce
any noise
I don't really see the reason here. Whether using the secure function or
not is is a question of whether we need null-termination or not.
If we need it the secure function will do the right thing. If we do not
need null-termination the non-secure function does the right thing and
the secure function would not add any security, but simply do the wrong
thing.
MSDN says about the lfFaceName member of the LOGFONT structure "A
null-terminated string that specifies the typeface name of the font. "
So we want it to be null-terminated and adding one more character does
not add anything useful, but will result in a broken structure.
Another difference is that the non-secure function pads the destination
array with nulls, the secure function does - afaik - not. If that is the
reason, I'd prefer zeroing it out before copying the string.
Am 06.04.2014 22:20, schrieb pschweitzer(a)svn.reactos.org:
> Author: pschweitzer
> Date: Sun Apr 6 20:20:39 2014
> New Revision: 62675
>
> URL: http://svn.reactos.org/svn/reactos?rev=62675&view=rev
> Log:
> [CHARMAP]
> Use rather wcsncpy(). A bit less safe, but at least, data are copied till possible
>
> Modified:
> trunk/reactos/base/applications/charmap/lrgcell.c
> trunk/reactos/base/applications/charmap/map.c
>
> Modified: trunk/reactos/base/applications/charmap/lrgcell.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/base/applications/charmap/…
> ==============================================================================
> --- trunk/reactos/base/applications/charmap/lrgcell.c [iso-8859-1] (original)
> +++ trunk/reactos/base/applications/charmap/lrgcell.c [iso-8859-1] Sun Apr 6 20:20:39 2014
> @@ -48,9 +48,9 @@
> hdc);
>
> lf.lfCharSet = DEFAULT_CHARSET;
> - wcscpy_s(lf.lfFaceName,
> - sizeof(lf.lfFaceName) / sizeof(lf.lfFaceName[0]),
> - lpFontName);
> + wcsncpy(lf.lfFaceName,
> + lpFontName,
> + sizeof(lf.lfFaceName) / sizeof(lf.lfFaceName[0]));
>
> hFont = CreateFontIndirectW(&lf);
>
>
> Modified: trunk/reactos/base/applications/charmap/map.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/base/applications/charmap/…
> ==============================================================================
> --- trunk/reactos/base/applications/charmap/map.c [iso-8859-1] (original)
> +++ trunk/reactos/base/applications/charmap/map.c [iso-8859-1] Sun Apr 6 20:20:39 2014
> @@ -228,9 +228,9 @@
> ReleaseDC(infoPtr->hMapWnd, hdc);
>
> infoPtr->CurrentFont.lfCharSet = DEFAULT_CHARSET;
> - wcscpy_s(infoPtr->CurrentFont.lfFaceName,
> - sizeof(infoPtr->CurrentFont.lfFaceName) / sizeof(infoPtr->CurrentFont.lfFaceName[0]),
> - lpFontName);
> + wcsncpy(infoPtr->CurrentFont.lfFaceName,
> + lpFontName,
> + sizeof(infoPtr->CurrentFont.lfFaceName) / sizeof(infoPtr->CurrentFont.lfFaceName[0]));
>
> infoPtr->hFont = CreateFontIndirectW(&infoPtr->CurrentFont);
>
>
>
>
This will make any failure messages in the loop useless, since you
won't know which test they're about.
Just because the tests are succeeding now doesn't mean they always will.
On 2014-04-06 17:51, hbelusca(a)svn.reactos.org wrote:
> @@ -188,7 +190,6 @@
>
> for (i = 0; i < TestCount; i++)
> {
> - trace("i = %d\n", i);
> switch (TestCases[i].PrefixType)
> {
> case PrefixNone:
>
>
Nice one :-). I thought you'd commit your ReactOS 1.0 patch today!
Beware though, you're sitting BUGCODE_NDIS_DRIVER.
Regards,
--
Pierre Schweitzer <pierre(a)reactos.org>
System Administrator
ReactOS Foundation
Working on DB server atm (hence the fails). Results will be properly
submitted later on.
Ignore failed shell errors for the next hour.
Sorry about that.
On 04/01/2014 11:24 AM, buildbot(a)reactos.org wrote:
> The Buildbot has detected a failed build on builder Linux_AMD64_2 VMWPlayer-Test while building ReactOS.
> Full details are available at:
> http://build.reactos.org/builders/Linux_AMD64_2%20VMWPlayer-Test/builds/3636
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Linux_AMD64_2
>
> Build Reason: Triggerable(Linux_AMD64_1 KVM-Test Trigger)
> Build Source Stamp: 62598
> Blamelist:
>
> BUILD FAILED: failed shell
>
> sincerely,
> -The Buildbot
>
>
>
>
--
Pierre Schweitzer <pierre(a)reactos.org>
System Administrator
ReactOS Foundation
Hi,
Is it possible to install a driver (virtual network interface) witout reboot the system ?
I tried TAP interface (installation with devcon: devcon install inf-file tap0901) but the interface is only loaded during the next reboot (same for a ndis sample from DDK)
Is there a way to load a driver interface with a true plug'n'play mechanism ?
--
Daniel Maxime
Linux version 3.6.9-maxux64 (emy) (gcc version 4.7.3 (Gentoo 4.7.3-r1 p1.4, pie-0.5.5) ) #3 SMP PREEMPT Wed Feb 19 16:40:22 CET 2014
16:33:29 up 24 days, 8 min, 1 user, load average: 0.31, 0.68, 0.72
from "David Quintana (gigaherz)" <gigaherz(a)gmail.com>:
> [-- Type: multipart/alternative, Encoding: 7bit, Size: 5.8K --]
> Content-Type: multipart/alternative; boundary=001a1135f7ac55c1ca04f557713d
> Content-Type: text/plain; charset=UTF-8
> First of all, I'm not an expert when it comes to what ReactOS supports in
> terms of real hardware.
> I believe (someone will correct me if I'm wrong), that ReactOS is not
> currently able to boot from USB, and in fact, will fail to boot at all if
> an incompatible USB controller (which is most of them, I think?) is
> present. Burning a CD-ROM with the setup or livecd images, and possibly
> disabling the USB controllers from your bios config, may give you better
> results.
> I'm assuming that your intention is to try ReactOS in real hardware,
> otherwise it would be better advised to just use VMware, VirtualBox, or
> QEMU, as those work mostly out of the box.
> Ideally, your real-hardware testing platform should have a serial port, and
> this serial port should be connected to another computer with a serial
> port, by using a null-modem cable. This way you could see debug messages
> through the serial port, and interact with the remote debugger driver when
> (more than if) it crashes.
> ReactOS currently only supports FAT32, because it's a simple driver that
> does not need advanced features of the storage system. As the storage stack
> improves, it will be possible to attempt using more complex drivers. We
> already have an EXT2 driver, but last I heard it was not stable enough to
> be able to boot from it.
> That's all I know. If it's not enough, maybe someone with more experience
> can add to it.
Thanks for response, but surely one-part plain text would be better than multipart/alternative?
I could try commands such as drivemap in GRUB 2, but then ReactOS would be lost when trying to boot.
Would MS-Windows drivers work in ReactOS when running from within VirtualBox or QEMU?
I don't really want to try ReactOS on the same disk with FreeBSD and Linux installations that I want to keep intact, might be too hazardous.
I don't have any serial ports but have serial headers on motherboard, could conceivably make a serial port.
FreeDOS can boot from USB stick thanks to recognition by the BIOS/UEFI.
I really would want to install ReactOS to something rewritable; having to burn a new CD for every little change is too much.
With ReactOS being far from ready for production use, I figure I would have to make frequent changes/adjustments.
I downloaded the installation iso for ReactOS 0.3.15, burned to CD, but that failed to boot.
I believe Linux and *BSD are far more flexible in where they can install to than MS-Windows or OS/2. I hope ReactOS could rise above such Windows booting limitations.
I ran OS/2 from 16-bit 1.3 in 1990 or 1991 to OS/2 Warp 4 in the single-digit days of April 2001. Then following a crash, on the next boot, CHKDSK, which ran automatically on the uncleanly-dismounted file system, ran amok and trashed everything on the hard drive. I was never again able to boot OS/2 after that. Now Linux and FreeBSD capabilities seem to far surpass OS/2 and its successor eComStation.
Tom
Hello,
Let me invite you to the monthly status meeting taking place last
Thursday of this month, 27th of March, 19:00 UTC. Put that into your
calendars so you don't forget.
IRC service will only be started shortly before the meeting. 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. Hopefully it's not
much of inconvenience.
If someone still is not getting passwords sent before a meeting - please
email Pierre before the meeting started to get one.
Please send agenda proposals to me.
Regards,
Aleksey Bragin
Hi,
I'm trying to compile and test the netvmini ndis 5 adapter code from WDK, at first to understand how it works, then to modify it for another purpose.
At this time I:
- put the code on driver/network/dd/netvmini and adapted CMakeLists
- put the inf on media/inf and adapted CMakeLists
- fixed the code, it builds
- add an entry to hivesys.inf to load the driver at boot
The driver is well displayed during boot, debug message appears (the DriverEntry), on NtObj, the driver is visible and it appears on "Non Plug and Play" on device manager.
Now, I don't know exactly what to do with it. How can I call the driver and add an adapter ?
The userland tool given with the code works (I needed to comment some functions and add _DEV_BROADCAST_HANDLE struct by hand, it seems to not be implemented on dbt.h).
When I run the userland tools, it fails with EnumDevices.
Some help ?
Thanks
Because I was recently shocked (if I may say :D) that, for building a
2003-class operating system, we need 2010+ tools, I was wondering whether it
was still possible to build ReactOS with MSVC 2008 and 2005. Ive created a
task for that in Jira: http://jira.reactos.org/browse/CORE-8023 . After
application of the configure.cmd patch that I give in the report, plus few
tweaks in two headers (and adding some stdint.h in the correct directory for
MSVC, needed for compiling host-tools, because this file is not included in
default MSVC installation until MSVC 2010+), I was able to build a full
bootcd and livecd (see the details in the abovementioned report, basically
it currently builds with MSVC 2008 but not 2005). However there happens an
interesting thing: the [boot|live]cd boots (freeldr seems to work and load
the kernel and drivers), but after that, the kernel (debugged in WinDbg)
hangs indefinitely here:
Windows Server 2003 Kernel Version 3790 UP Checked x86 compatible
Built by: 20140326-r62565
Machine Name:
Kernel base = 0x80400000 PsLoadedModuleList = 0x005fcf88
System Uptime: not available
(f:\ros_vs_test\ntoskrnl\ke\i386\cpu.c:494) Supported CPU features :
KF_V86_VIS KF_RDTSC KF_CR4 KF_CMOV KF_GLOBAL_PAGE KF_LARGE_PAGE KF_MTRR
KF_CMPXCHG8B KF_MMX KF_WORKING_PTE KF_PAT KF_FXSR KF_FAST_SYSCALL KF_XMMI
KF_XMMI64 KF_NX_BIT
(f:\ros_vs_test\ntoskrnl\ke\i386\cpu.c:801) Prefetch Cache: 64 bytes L2
Cache: 0 bytes L2 Cache Line: 64 bytes L2 Cache Associativity: 0
<_hangs_forever_here_>
If some of you have an idea what *might* happen there, Im all ears!
Cheers,
Hermès.
Hello, dear developers!
Sorry if I am doing something wrong, but I am not sure, if everyone who
may help would be notified by JIRA.
I made some bug hunting on CORE-7965 and now need some assistance in
finding way to fix it. I have posted the results in my last comment on
JIRA:
http://jira.reactos.org/browse/CORE-7965?focusedCommentId=57456&page=com.at…
In short: a bug is related to some interprocess virtual address
transmission that is leading to access attempt on unallocated virtual
memory, that finally crashes ReactOS.
That's illegal, macros can't be overloaded.
drivers/filesystems/ext2/inc/ext2fsd.h:64:0: warning: "try_return" redefined [enabled by default]
You could try
#define try_return(...) { __VA_ARGS__; goto try_exit; }
If that doesn't do it, it might simply need a separate macro
(I'm not sure to what extent this is third party code though)
(also if these were the last instances of that -- and I think so --, we
might want to make 4003 an error)
On 2014-03-24 23:20, hbelusca(a)svn.reactos.org wrote:
> Author: hbelusca
> Date: Mon Mar 24 22:20:52 2014
> New Revision: 62562
>
> URL: http://svn.reactos.org/svn/reactos?rev=62562&view=rev
> Log:
> [EXT2]
> try_return() == try_return(S) with nothing in S . The code sometimes use it.
> Shut up MSVC warning C4003: not enough actual parameters for macro 'try_return'.
>
> Modified:
> trunk/reactos/drivers/filesystems/ext2/inc/ext2fsd.h
>
> Modified: trunk/reactos/drivers/filesystems/ext2/inc/ext2fsd.h
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/filesystems/ext2/i…
> ==============================================================================
> --- trunk/reactos/drivers/filesystems/ext2/inc/ext2fsd.h [iso-8859-1] (original)
> +++ trunk/reactos/drivers/filesystems/ext2/inc/ext2fsd.h [iso-8859-1] Mon Mar 24 22:20:52 2014
> @@ -60,6 +60,7 @@
> extern Ext2Data Ext2GlobalData;
>
> // try-finally simulation
> +#define try_return() { goto try_exit; }
> #define try_return(S) { S; goto try_exit; }
> #define try_return1(S) { S; goto try_exit1; }
> #define try_return2(S) { S; goto try_exit2; }
>
>
I would like to build and install ReactOS from source but may be strapped for where to install it.
I have USB sticks, 3 TB SATA hard drives, and 3 TB USB 3.0 hard drive.
Hard drives are GPT-partitioned, which ReactOS apparently doesn't support.
I have some old IDE hard drives which I access with USB 2.0 enclosure: 1271 MB and 40 GB.
I also have an old 341 MB IDE hard drive that I can't read through USB 2.0 enclosure.
I could compile from Linux or FreeBSD with ROSBE, could do further builds that way or with Wine and MinGW under Linux or FreeBSD.
I don't want to do heavy compiling on USB stick if I can avoid it.
I believe the only file system ReactOS currently supports is FAT16 or FAT32, which limits possible partition size compared to NTFS or Linux or BSD file systems.
Can I install to USB stick, 4GB or 8 GB, and are there any other possibilities with my hardware?
Tom
Hi all!
Since some time now, most of our build bots are unavailable (see
http://build.reactos.org/builders , the ones maintained by Olaf). What is
happening to them? I sent him a mail but no answer so far I have received.
We *need* those bots! , and especially the patch-bot that I am waiting for,
because I have two big patches in my local wc that need to be tested and I
cannot proceed further for now (and surely other have too, according to some
recent Jira reports).
Please fix them asap. if possible :D
Cheers,
Hermès
Hi, I've been following the project for years and I've even used explorer
implementation on Windows. I also went to the Montreal event.
I'm a linux user so I won't be a full time user any time soon.
What I think would make a really good Kickstarter, having watched the
Thorium Core progress:
Developers Delight:
What ReactOS or Thorium D has going for it is fully debugable and
fundamental understanding of how Windows works. Microsoft has Visual
Studio Online but it's pretty bad, at least at the moment it's a mess to
set
up.
Having a way to run your MinGW-w64 projects, possible compile them.
Having support for Clang msvc implementation.
And last and not the least is the Visual Studio, which of course is the
hardest. Even without that it's going to be really solid.
An extra plus is being able to make Windows Embedded development
stack running, because Trimble are really tied to that. Also Delphi and
what ever other development you can think of.
Having git support with CI type workflow is going to be great and with
kernel level debug reports what could be better.
The MingGW-w64 is going to great for all the open source software
developers that need something to develop windows software without
touching windows.
You should talk with OpenShot they were having problems with that
kind of development.
This is going to be a double benefit for you guys, not only will it
provide you with information about what people are using and what
bugs are in your system but also provide a lot of foss software on
your platform.
Embedded dreams:
Now that XP is through people need an embedded version, Windows
Embedded isn't it, because it has a really weird api. Vista isn't really
there or 7 so, where is your chance. Banks are paying Microsoft to
extend XP for their ATMs but not every one can afford it. Enter
Thorium E, for all those kiosks and POS. You have greater control
so you can build a kit for Embedded user where they decide what's
going to be included and what comes up, like not having a screen
saver, virus software, IE, only allowing one or two exe files to run
and only certain dlls. This would also be perfect to make single
use virtual images with only one program running.
If you need any help with making the video or with the campaign I
would love to help.
Regards,
Olaf
Hi developers,
Passed a week after I provided a ready for review and apply patch, a
simplest solution for simplest bug.
Could anyone review, test, and apply it?
https://jira.reactos.org/browse/CORE-7969
Thanks
Hi all !
ReactOS severely needs to be self-hostable for many reasons, one of it
because it could allow people who only have Linux to be able to program /
debug ReactOS with Windows tools (e.g. we have some people here and there
complaining that they cannot use powerful debugging programs for debugging
ReactOS (e.g. WinDbg and so on with MSVC builds of ReactOS) and therefore
restrain themselves in using the Goode Olde GCC + DPRINT method, because
they are running only on Linux). Something more personal is that I really
want to program ReactOS on itself (in a VM) when it becomes self-hostable.
But there are *only* few steps remaining before ReactOS can really be in
such situation !!
Ive already tested RosBE on it and I was able to download and configure a
build. But there *are still* problems.
Here is my setup on a VM: main HDD of letter drive C: with ReactOS, second
HDD of letter drive D: with ROS source code in D:\rossrc, third HDD of
letter drive E: with build output files in E:\rosbuild .
After having successfully configured a build in the usual way (E:\rosbuild>
D:\rossrc\configure.cmd), I first tried to compile the host-tools (cd
host-tools && ninja). The first thing that Ive noticed is that doing so
retriggered a configure, then the compilation as wanted. I retried again,
and again it reconfigured the build before actually rebuilding the
host-tools. The same phenomenon appears then when trying to build ReactOS
proper.
After analyzing produced files by the configuration step and comparing with
a clean build on windows 2k3, it became clear that few files were missing,
because obviously not generated:
E:\rosbuild\host-tools\CMakeFiles\2.8.10.2-ReactOS\CMakeCCompiler.cmake and
CMakeCXXCompiler.cmake . The other .cmake files that should also be present
here (CMakeRCCompiler.cmake and CMakeSystem.cmake) as well as two .bin files
and two subdirectories where present (and contain the same things).
I was suggesting it might be a problem with the command-line interpreter, so
I changed our cmd.exe with the one of windows 2000 (not win2k3, because the
latter makes extra calls to some security APIs of advapi32 not implemented
on ReactOS before running .bat / .cmd files, and it fails), but nothing
changed, the files were not still present.
After having enabled extra debug output of cmake (that is called when
configuring a build) by adding the flags --debug-output --trace (without
quotes) in the cmake calls in configure.cmd (and after redirecting console
stdout + stderr to a file when retrigerring a clean configuration), doing
that on ReactOS *and* on win2k3 for comparison purposes, I saw that, at some
point, some cmake flags concerning compiler recognition (à la:
CMAKE_GCC_EXISTS for example) werent set to TRUE or FALSE, but were kept
empty.
So Im wondering whether it is actually some issue, either concerning our C
runtime library (e.g. some called sprintf-like function fails or whatever)
is buggy and something fails, OR, something file-system related. Concerning
file-system, you know that we have LOTS of kernel32:file winetests failing,
about problems for deleting files, recreating (or just creating) them, and
so on Maybe for some reason cmake fails to create those
CMake(C/CXX)Compiler.cmake files for the same reason one of the
kernel32:file tests fail ?
I dont know, this previous point being speculative since I didnt test
anything regarding that.
Therefore it would be very nice *to see you all* trying to uncover where
this bug comes from so that you can *finally* declare ReactOS self-hostable
before, maybe, the next release !!
Cheers,
Hermès
Valve has publushed Direct3D -> OpenGL translation layer with BSD like license
https://github.com/ValveSoftware/ToGL
Taken directly from the DOTA2 source tree; supports:
Limited subset of Direct3D 9.0c
Bytecode-level HLSL -> GLSL translator
Some SM3 support: Multiple Render Targets, no Vertex Texture Fetch
This most likely won't build by itself and is provided as-is and completely unsupported. Feel free to use it for your reference, incorporate it into your projects or send us modifications.
Be wary that some parts are hardcoded to match Source Engine behavior; see CentroidMaskFromName() and ShadowDepthSamplerMaskFromName() in dxabstract.cpp.
Please refer to the LICENSE file for more information.
--
Best regards
Alexander Rechitskiy
Hello,
I need to use NDIS NdisIMRegisterLayeredMiniport functions to provide a virtual ethernet card. I read the documentation on MSDN and it seems that this functions is required to build an adapter without physical link (eg, with no hardware IRQ).
The problem is that this function is not implemented yet on reactos (svn rev. 62083). Is someone can tell me if it's implementable or if there is an alternative to build a virtual ethernet adapter with current implementation of NDIS.
Thanks.
--
Daniel Maxime
Linux version 3.6.9-maxux64 (emy) (gcc version 4.7.3 (Gentoo 4.7.3-r1 p1.4, pie-0.5.5) ) #3 SMP PREEMPT Wed Feb 19 16:40:22 CET 2014
14:02:53 up 1 day, 21:38, 1 user, load average: 0.17, 0.26, 0.23
Hi guys !
It seems to appear that some games need standard APIs hotpatchable, in the
sense of MS: few extra bytes present in the prologue of the functions that
allow somebody to detour the API. I knew that this feature was useful for
windows updates, but what I didnt know is that there are other programs
that use it: see this answer from James on the Epic Win! forum thread:
http://www.reactos.org/forum/viewtopic.php?f=2
<http://www.reactos.org/forum/viewtopic.php?f=2&t=10972&p=106823#p106814>
&t=10972&p=106823#p106814 , and the following post is something that Ive
found about this subject, and the fact that Wine already have done something
about that.
So my question: should we support/create hotpatchable images (of the
standard dlls and maybe ?? exes) in ReactOS ? Is it already done ? If not,
what needs to be added ? It seems that MSVC and GCC handle that a bit
differently.
Cheers,
Hermès BÉLUSCA - MAÏTO
Hello!
I have registered on main site, because I want to login to JIRA, but
JIRA says now that my login is incorrect. Does it need some time to make
JIRA accout accessible after registration? Or I need to do some actions?
Do I need to request account for JIRA separately?
Hi all,
In the process of improving the performance of our website and finally
getting rid of old.reactos.org, I'm moving away the Testman database to
a new VM tomorrow.
This will cause a short downtime, in which you're unable to browse
Testman results or submit new ones. Even if something goes wrong during
that process, the downtime shouldn't last longer than 2 hours.
With best regards,
Colin
Hello,
Let me invite you to the monthly status meeting taking place last
Thursday of this month, 27th of February, 19:00 UTC. Put that into your
calendars so you don't forget. And that's in two days!
IRC service will only be started shortly before the meeting. 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. Hopefully it's not
much of inconvenience.
If someone still is not getting passwords sent before a meeting - please
email Pierre before the meeting started to get one.
The agenda will be posted shortly before the meeting, suggestions are
welcome (send them to me shortly before the meeting starts).
Regards,
Aleksey Bragin
-------- Original Message --------
Subject: [ReactOS Deutschland e.V.] Your organization application has
been rejected.
Date: Mon, 24 Feb 2014 18:40:28 +0000
From: no-reply(a)google-melange.appspotmail.com
To: amine.khaldi(a)reactos.org
Thank you for submitting ReactOS Deutschland e.V.'s application to
Google Summer of Code 2014. Unfortunately, we were unable to accept your
organization's application at this time. Every year we receive many more
applications than we are able to accommodate, and we would encourage you
to reapply for future instances of the program.
If you would like some general feedback on why your organization was not
accepted, please consider attending the IRC meeting in #gsoc on Freenode
on Friday, 28 February, 2014 at 16:00 UTC. Please note that the feedback
meeting will be limited to the first 50 organizations to queue up
(queuing in the channel will begin at 15:30 UTC).
Best regards,
Could somebody visit and represent ReactOS to VIA Embedded at Embedded World 2014?
http://www.embedded-world.de/en/
February 25th - 27th in Nuremberg Germany
--
Best regards,
Alexander Rechitskiy
Hi all,
I've added the "project-tools" and "web" repositories to FishEye today,
so you can browse through their changes as well now.
My ultimate plan is to remove "CORE", "ROSAPPS" and "ROSTESTS" too and
replace all of them by the already existing "reactos" repository. This
resembles our SVN counterparts exactly.
I was told this has already been tried in the past with no success due
to severe performance issues. As FishEye is running on a more powerful
server now, please try again and tell me if there are any problems with
using "reactos" instead of "CORE".
If not, I will get rid of the redundant repositories soon.
Apart from this, we're now also using post-commit hooks to update the
repositories in FishEye. This gives you instant information about new
commits and reduces the server load a bit.
Cheers,
Colin