There's a constant for this INVALID_HANDLE_VALUE...
On 10-Jan-09, at 7:33 AM, dchapyshev(a)svn.reactos.org wrote:
> case 0xFFFFFFFF: /* File does not exist */
Best regards,
Alex Ionescu
Hi!
Why to use extern inline there, FORCEINLINE macro uses static. Extern
inline — GCC extension — does not work as needed in c99/gnu99 mode
(non-inline functions are emitted as well). GCC documentation says it
will be the default in the future.
Since Arty just mentioned GIT, I think it's about time to uncover a
ReactOS GIT mirror I've been setting up recent couple of weeks.
It works pretty good so far, autoupdates every 10 minutes, so it
stays quite up-to-date.
URLs:
git://git.reactos.org/ - for git cloning.
http://git.reactos.org - for web viewing.
As for branches, it was actually my main intention in using a DVCS,
because SVN branches are greatly uncomfortable to develop anything
because of the need to keep the branch up-to-date.
But, to prevent any gossips, SVN stays as our main repository, and
GIT mirror is just for exploration of new possibilities, and for
comfortability of working with branches - if someone wants to try
that out. Usual SVN branches are still permitted.
WBR,
Aleksey Bragin.
Hello,
I recently spent some time experimenting with various Cc rewrites we
have in our tree, and before that I extensively tested our fastfat
driver in a real NT environment (MS Windows 2003).
The conclusion of the above work is that our fastfat driver either
needs serious bugfixing, or a rewrite is needed. It corrupts
directory tables in a real NT, leads to unusual behaviour of cc-
rewrite branch, and may have side effects on arty's newcc.
Before this is done (bugfixing or rewriting, developing and testing
against a Windows 2003 at least, not ReactOS), it's meaningless to
continue any other work on Cc and related Mm parts.
WBR,
Aleksey Bragin.
Hi all!
Here is the test program provided by BugBoy. It also shows another
bug, see bug 3971. Please test before and after the patch.
Thanks,
James
PS
Good Job, Michael!
Hi,guys
I'm just a fan of ReactOS,now I have two questions.
1, Is(or will be) there an disk management utility for ReactOS, or in
another way, will we make an implementation of Microsoft diskmgmt.msc?
2, Will ReactOS group make an implementation of Microsoft Management
Console for ReactOS?
Thank you!
Yeah, sorry, the target device should be used to send a
TARGET_DEVICE_CUSTOM_NOTIFICAITON of type GUID_IO_VOLUME_CHANGE at the
end of the function (IoReportTargetDeviceChange).
FYI, Pierre, when you implement the notification system.
On 4-Jan-09, at 5:12 AM, fireball(a)svn.reactos.org wrote:
> Author: fireball
> Date: Sun Jan 4 04:12:38 2009
> New Revision: 38552
>
> URL: http://svn.reactos.org/svn/reactos?rev=38552&view=rev
> Log:
> - Revert changes to NtSetVolumeInformationFile made in 38550, it
> should indeed use IoGetRelatedDeviceObject, not target device.
>
> Modified:
> trunk/reactos/ntoskrnl/io/iomgr/iofunc.c
>
> Modified: trunk/reactos/ntoskrnl/io/iomgr/iofunc.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/iofunc.c…
> =
> =
> =
> =
> =
> =
> =
> =
> ======================================================================
> --- trunk/reactos/ntoskrnl/io/iomgr/iofunc.c [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/io/iomgr/iofunc.c [iso-8859-1] Sun Jan 4
> 04:12:38 2009
> @@ -3307,8 +3307,7 @@
> }
>
> /* Get the device object */
> - Status = IoGetRelatedTargetDevice(FileObject, &DeviceObject);
> - if (!NT_SUCCESS(Status)) return Status;
> + DeviceObject = IoGetRelatedDeviceObject(FileObject);
>
> /* Clear File Object event */
> KeClearEvent(&FileObject->Event);
>
Best regards,
Alex Ionescu