Jonathan Wilson wrote:
> Basicly, there are 2 kinds of users.
> There are those who have windows and and NTFS partition and want to access
> it from ROS. (perhaps dual boot ROS and win from the one NTFS partition
> ambie if that is something ROS can be made to do). These people can use
> ntfs.sys from MS since they have windows.
>
> Then there are those who dont have windows, dont have an existing NTFS
> partion and dont have a copy of ntfs.sys.
> Those people can use whatever other solution we come up with (ReactOS
> implementation of NTFS, some unix FS like ext/reiser etc or whatever else
> we come up with).
That seems to make perfect sense.
Why would anyone need/want to use NTFS if they don't need to access existing
NTFS drives?
If they do have existing NTFS drives, then as Jonathan says, they should
also have the driver from MS to access it.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Mark Junker wrote:
> simply use ReiserFS 4 because it implements all (!) features that are
provided by NTFS.
That would be my choice of filesystem also.
I don't see a reason for trying to implement ext2/3 when we have ReiserFS at
our disposal.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
--- Casper Hornstrup <ch(a)csh-consult.dk> wrote:
> Probably, but they won't have the same casing as in the Platform SDK then.
Yes but Windows is case insensitive so matching the PSDK case is just a waste of time. Besides the
rest of the w32api is in lower case so anyone importing a project on mingw-linux already has to
adjust the case. If there are no objections I will change the GDIplus headers and the source for
the stub dll.
Thanks
Steven
Yahoo! Mail
Stay connected, organized, and protected. Take the tour:
http://tour.mail.yahoo.com/mailtour.html
Hi,
--- chorns(a)svn.reactos.com wrote:
> Re-add local w32api changes
> Added files:
> trunk/reactos/w32api/include/GdiPlus.h
This has bothered me for a while. Can we make the filenames all lowercase? Having mixed cases
causes a problem when people develop on Windows and don't check to make sure they have used the
correct case in source files resulting in broken builds of Linux developers.
Thanks
Steven
Yahoo! Mail
Stay connected, organized, and protected. Take the tour:
http://tour.mail.yahoo.com/mailtour.html
I spent some time doing a mingw port of GCC4 lately and here's my
experimental mingw-special-reactos port for win32:
http://www.reactsoft.com/mingw-special-reactos-20050510.zip
The reactos tree fully compiles from rev. 15198 on and appears to work
fine. However, please read notes.txt inside the archive to get it to
work properly (default paths are messed up, so you have to set up three
environment variables).
Compiling reactos with it will produce quite a bunch of warnings, mostly
from 3rd party libraries (e.g. oskittcp, mesa32), the imported wine code
and explorer.
Best Regards,
Thomas
ion(a)svn.reactos.com wrote:
>Make the remaning code match the current formatting instead of being really ugly,
>
>and make some changes to IoCreateFileStreamObject (which is wrong anyways, since it's doing what *Lite should do)
>
>
>
This breaks usetup/vfat/whatever. I'll fix it until I have time to look
at the whole picture. (Well actually I'll add back the incorrect parts
of the code :P)
Best regards,
Alex Ionescu
Hi there,
It'd be very appreciated if some fellow with write access can commit
this patch.
It implements SeCreateAccessState, SeDeleteAccessState and
SeSetAccessStateGenericMapping.
It defines an opaque structure for _ACCESS_STATE too.
Best regards,
-Javier
Hi,
--- Thomas Weidenmueller <w3seek(a)reactos.com> wrote:
> If you know, why shouldn't he know? From what I understand the entire
> structure is opaque, so my guess is that the names are just guessed,
> based on the obviously known layout.
I googled for quite a while and found next to nothing about these functions or that structure. A
little birdy told me that a IDA lookup does not even show a third member.
Thanks
Steven
Yahoo! Mail
Stay connected, organized, and protected. Take the tour:
http://tour.mail.yahoo.com/mailtour.html
ion(a)svn.reactos.com wrote:
>Fix NtWriteFile: Get right Deviceobject, Use FileObject->FinalStatus, use FileObject-.CurrentByteOffset if ByteOffset == FILE_USER_FILE_POINTER_POSITION, add SEH, use right event requested access, set IRP_WRITE_OPERATION flag, add support for IRP_NOCACHE and add support for SL_WRITE_THROUGH if FO_WRITE_THROUGH is enabled.
>
>
>
>
Hey Steven, I don't know what happened but this commit added a bunch of
whitespaces back!? I don't know why, I already had updated to the latest
version. Anyways, please run your script again I guess. (on file.c)
Best regards,
Alex Ionescu