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);
>
>