[ros-dev] [ros-diffs] [ekohl] 61145: [FASTFAT] FsdGetFsVolumeInformation: Return volume creation time.

[Magnus Olsen]

Hi
About  discussions about MS license. the question is if
the license agreement to restrict only to Microsoft Windows is valid in EU.
I do not think so. But only a lawyers can tell about that. Rest of the
world I do not known.

In sweden lest we got so call negative license agreement. That mean part of
a license   agreement is not valid for it is bad for user or goes
against any law.




2013/12/2 Steven Edwards <winehacker at gmail.com>

> Look at how the Core Fonts for the Web are handled. We should have generic
> drivers that are 'good enough' to be able get online and download the
> Microsoft ones if the user wants to take the risk of violating Microsofts
> license.
>
>
> On Mon, Dec 2, 2013 at 9:27 AM, Alex Ionescu <ionucu at videotron.ca> wrote:
>
>> These are all legitimate concerns for a FAT driver, but keep in mind the
>> WDK library also has things like large chunks of the storage stack, the
>> input stack, the floppy stack, audio and network stuff, etc...
>>
>> We could decide to keep our current FAT driver (or find a workaround),
>> but still implement this idea for the other drivers.
>>
>> Best regards,
>> Alex Ionescu
>>
>>
>> On Mon, Dec 2, 2013 at 6:37 AM, Michael Fritscher <michael at fritscher.net>wrote:
>>
>>> Hi,
>>>
>>> normally, I wouldn't have any problem with having drivers on a second
>>> disc
>>> / image. But FAT (and in particular cdfs) are core-drivers in my opinion,
>>> which are needed almost every time - also for booting from CD for
>>> installation. FAT is widely used still today, e.g. on usb-sticks.
>>>
>>> What are currently the biggest problems in these drivers? If remember
>>> correctly, our cache manager isn't compatible to the one in Windows, and
>>> these drivers have workarounds, is it?
>>>
>>> Perhaps the drivers could be written by a GSoC project or something like
>>> that?
>>>
>>> Additionally, what about NTFS? Is there a ntfs-driver in the MSDN-library
>>> as is the FAT-driver? If not, almost nothing is won if we use the
>>> fat-driver from MS: The OS- dependent part of the ntfs-driver need to be
>>> written from scratch from us anyway, which could then be reused by our
>>> FAT-driver. And hey, the filesystem part of the FAT-driver shouldn't be
>>> too complicated if we managed to write a NTFS-driver^^
>>>
>>> Best regards,
>>> Michael Fritscher
>>>
>>>
>>> _______________________________________________
>>> Ros-dev mailing list
>>> Ros-dev at reactos.org
>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>
>>
>>
>> _______________________________________________
>> Ros-dev mailing list
>> Ros-dev at reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>
>
>
> --
> Steven Edwards
>
> "There is one thing stronger than all the armies in the world, and that is
> an idea whose time has come." - Victor Hugo
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev at reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.reactos.org/pipermail/ros-dev/attachments/20131202/0241ed94/attachment.html>