Re: Add filesytem type NTFS to config

[Andreas Mohr]

On Mon, Jan 13, 2003 at 09:06:28PM -0700, Tony Lambregts wrote:
> Some program (VirtualDub) checks the fsname returned by 
> GetVolumeInformation, to find the name of the file system, when it needs 
> to write files that are larger than 2GB. It refuses to create the file 
> when we return FAT but will successfully write the file when NTSF is 
> returned.
>
> Change Log: add configuration option to report NTFS as the file system 
> type for a drive.

Hmm, I'm not sure whether we should increase the preexisting Filesystem
type mess by doing that.
I've hated the "win95", "vfat" etc. syntax almost from the beginning
(well, to be fair, I think I'm not too innocent when it comes to its
implementation, but at some time I just came to the conclusion
that it sucked)

After all we're running on *Unix* file systems in many cases,
so "win95" does have no place here at all ! (neither does "vfat")
Not to mention that "win95" awfully collides with the "win95" winver...

And adding yet another "incorrect" "ntfs" setting makes my head
want to go bonkey ;-)

So I guess that it might be a good idea to think about how to solve this
configuration issue in a nicer way (and of course keep the old config
capabilities for about 2 years in order to have backward compatibility).

We might even want to think of introducing "nameless" filesystem type
settings (instead of having "broken" conflicting and "wrong" FS type names).
And of course it seems as if we also need a separate FS *name* setting
in order to have Wine return "NTFS" instead of "FAT" in your case...

So could we start a discussion about that perhaps ?
> Files changed: documentation/samples/config
>               documnetation/configuring.sgml
>               files/drive.c

Finally a beautifully implemented patch ! I hate having to clean up the
docu "after the fact".
> -;;   DON'T use "unix" unless you intend to port programs using Winelib !
> +;;   - "ntfs"  for ext2fs (some program need this to write files > 2GB)

^^^^^^^^ urks ! a significant portion of unix FS users
don't even use ext2fs...
> +;;   - "unix"  DO NOT USE unless you intend to port programs using Winelib !

Somehow that setting is also quite some pain...

Andreas Mohr

Add filesytem type NTFS to config

[Tony Lambregts]

Andreas Mohr wrote:
> On Mon, Jan 13, 2003 at 09:06:28PM -0700, Tony Lambregts wrote:
> > Some program (VirtualDub) checks the fsname returned by 
> > GetVolumeInformation, to find the name of the file system, when it needs 
> > to write files that are larger than 2GB. It refuses to create the file 
> > when we return FAT but will successfully write the file when NTSF is 
> > returned.
> >
> > Change Log: add configuration option to report NTFS as the file system 
> > type for a drive.
>
> Hmm, I'm not sure whether we should increase the preexisting Filesystem
> type mess by doing that.
> I've hated the "win95", "vfat" etc. syntax almost from the beginning
> (well, to be fair, I think I'm not too innocent when it comes to its
> implementation, but at some time I just came to the conclusion
> that it sucked)
>
> After all we're running on *Unix* file systems in many cases,
> so "win95" does have no place here at all ! (neither does "vfat")
> Not to mention that "win95" awfully collides with the "win95" winver...
>
> And adding yet another "incorrect" "ntfs" setting makes my head
> want to go bonkey ;-)

Well windows programs don't know what to do with ext3 et al so we tell 
them what they need to hear. Hell that _IS_ what wine does in general. 
You can go bonkey about it all you want.<g>
> So I guess that it might be a good idea to think about how to solve this
> configuration issue in a nicer way (and of course keep the old config
> capabilities for about 2 years in order to have backward compatibility).
>
> We might even want to think of introducing "nameless" filesystem type
> settings (instead of having "broken" conflicting and "wrong" FS type names).
> And of course it seems as if we also need a separate FS *name* setting
> in order to have Wine return "NTFS" instead of "FAT" in your case...
>
> So could we start a discussion about that perhaps ?

This is what I knew I was capable implementing. There was a thread about 
this when I took up the project and there was very little in it that 
made me want to do it another way.

http://www.winehq.com/hypermail/wine-devel/2002/12/0833.html

The thing is how many programs even care what file system is being used. 
At least one checks for CDFS and another checks for NTFS but I think 
that the vast majority couldn't care. This fixes the problem in a 
general way and I don't see an advantage to doing it in a more elegant 
way unless the need arises.

I am however curious what file system types the various implementations 
of windows will return. These are the ones I am aware of:

HPFS (from OS2's  High Performance File System)
NTFS
FAT  Floppies and older (small) hard drives
FAT32
CDFS (CD-ROMS)

What else am I missing such as what does Novell or Samba  return for one 
of thier mounted drives? What do DVD's report as thier file system on 
windows?  What about zip drives and other removable drives? Any other 
thing I missed?

IMO The "right" fix is to have Wine query the file system and report 
back what the current directory's file system is capable of emulating. 
If it is a unix fs or similar then "NTFS" if its a FAT or VFAT then 
"FAT" or FAT32. This solution is what _I_ would like to see. However 
unless I get a better handle on how to achieve _and_ there is a real 
need I am not about to put the effort into implementing it.  So there...<G>
> > Files changed: documentation/samples/config
> >              documnetation/configuring.sgml
> >              files/drive.c
>
> Finally a beautifully implemented patch ! I hate having to clean up the
> docu "after the fact".

Well I am on the documentation team. (Its where I started working on 
Wine BTW)
> > -;;   DON'T use "unix" unless you intend to port programs using Winelib !
> > +;;   - "ntfs"  for ext2fs (some program need this to write files > 2GB)
>                 ^^^^^^^^ urks ! a significant portion of unix FS users
>
> don't even use ext2fs...

What would you want it to say??  Unix FS? a non exaustive list such as 
"ext2, ext3, Rieser eg:"?
> > +;;   - "unix"  DO NOT USE unless you intend to port programs using Winelib !
>
> Somehow that setting is also quite some pain...

Yes and we tell the application that it is a "FAT" drive currently but 
we deal with filenames in a case sensitive way. I am not about to "FIX" 
this though, unless the wine-lib guys come up with some specs about what 
it sould really do.

Add filesytem type NTFS to config

[Francois Gouget]

On Tue, 14 Jan 2003, Tony Lambregts wrote:
[...]
> I am however curious what file system types the various implementations
> of windows will return. These are the ones I am aware of:
>
> HPFS (from OS2's  High Performance File System)
> NTFS
> FAT  Floppies and older (small) hard drives
> FAT32
> CDFS (CD-ROMS)
>
> What else am I missing such as what does Novell or Samba  return for one
> of thier mounted drives? What do DVD's report as thier file system on
> windows?  What about zip drives and other removable drives? Any other
> thing I missed?

AFAIK, read-write CDs use a special filesystem so they probably get
their own value. Samba probably reports whatever the share's underlying
filesystem is (at least if the server is a Windows machine). I suspect
zip drives just use what the user chooses, i.e. FAT or VFAT, maybe FAT32
though that seems quite unnecessary given their limited size.

Add filesytem type NTFS to config

[Tony Lambregts]

Francois Gouget wrote:
> On Tue, 14 Jan 2003, Tony Lambregts wrote:
> [...]
> > I am however curious what file system types the various implementations
> > of windows will return. These are the ones I am aware of:
> >
> > HPFS (from OS2's  High Performance File System)
> > NTFS
> > FAT  Floppies and older (small) hard drives
> > FAT32
> > CDFS (CD-ROMS)
> >
> > What else am I missing such as what does Novell or Samba  return for one
> > of thier mounted drives? What do DVD's report as thier file system on
> > windows?  What about zip drives and other removable drives? Any other
> > thing I missed?
>
> AFAIK, read-write CDs use a special filesystem so they probably get
> their own value. Samba probably reports whatever the share's underlying
> filesystem is (at least if the server is a Windows machine). I suspect
> zip drives just use what the user chooses, i.e. FAT or VFAT, maybe FAT32
> though that seems quite unnecessary given their limited size.

<bewilderment>

err... ahem.. Oh come on... I appreciate you want to help but... How do 
I say this nicely...

AFAICS you are just guessing. I can do that... but it is not a good way 
to build specs.

I recall we got better specs on compile times.

</bewilderment>

Add filesytem type NTFS to config

[Francois Gouget]

On Tue, 14 Jan 2003, Tony Lambregts wrote:
[...]
> > AFAIK, read-write CDs use a special filesystem so they probably get
> > their own value.

Confirmed: you can use ISO9660 (or ext2fs for that matter), but if you
want to use your CDRW as a big floppy drive on Windows, then you would
use UDF (google CDRW UDF).
> Samba probably reports whatever the share's underlying
> > filesystem is (at least if the server is a Windows machine).

IIRC, right-click -> Properties on a shared drive tells you what
filesystem the remote computer is using for that filesystem. It does not
mean that Windows is not returning some strange value in the function
you are concerned about but I don't have a way of checking that.  What
about providing a test app that would enumerate drives and dump the
values reported by Windows?
> I suspect
> > zip drives just use what the user chooses, i.e. FAT or VFAT, maybe FAT32
> > though that seems quite unnecessary given their limited size.

Confirmed. I asked a collegue who has a Zip drive and they behave just
like other removable media (floppies). So you use the usual way to
format such things so what you get is a FAT disk. Depends on your
Windows OS of course. On Windows 95 you would get VFAT, on Windows 98SE
you may get FAT32 instead.
Of course that does not mean that Windows is not checking that this is a
Zip drive+FAT combination to return 'foobar' rather than just FAT. But
it does seem relatively improbable.
> AFAICS you are just guessing. I can do that... but it is not a good way
> to build specs.

Not really guessing. Just providing a dump of my fuzzy memories of past
experiences and stuff I read in the hope that it can guide your search
about an exhaustive list of Windows supported filesystems.

You asked: Any other thing I missed?

At least you missed the filesystem used for CDRW: UDF. Again maybe the
function you are concerned about will call that CDFS or billfs. But now
you know that you need to ask someone with a CDRW drive to check what
the function returns for that drive.

Add filesytem type NTFS to config

[Philipp Wollermann]

From: "Francois Gouget"
> [...]
> At least you missed the filesystem used for CDRW: UDF. Again maybe the
> function you are concerned about will call that CDFS or billfs. But now
> you know that you need to ask someone with a CDRW drive to check what
> the function returns for that drive.

I just formatted a CDRW with Ahead InCD and Windows XP reports "FS_UDF" as
the filesystem.. (note, that WinXP still reports "NTFS", "FAT" and "CDFS";
it seems as UDF is the only filesystem where "FS_" is prefixed to the
name..)

Philipp

Add filesytem type NTFS to config

[Philipp Wollermann]

----- Original Message -----
From: "Philipp Wollermann"
> I just formatted a CDRW with Ahead InCD and Windows XP reports "FS_UDF" as
> the filesystem.. (note, that WinXP still reports "NTFS", "FAT" and "CDFS";
> it seems as UDF is the only filesystem where "FS_" is prefixed to the
> name..)

Well, I just checked what happens if I insert a DVD: It reports just "UDF"
as the filesystem.. maybe it's this InCD thing which has its own UDF driver
(which is known to Windows as "FS_UDF" whereas the normal Windows UDF driver
uses "UDF" as the name ...)

Philipp

Add filesytem type NTFS to config

[Sylvain Petreolle]

No need to guess anything.
Just re-read the Filesystems HOWTO. :)

http://www.google.fr/search?q=filesystems+HOWTO&ie=ISO-8859-1&hl=fr&...
> Not really guessing. Just providing a dump of my fuzzy memories of
> past
> experiences and stuff I read in the hope that it can guide your
> search
> about an exhaustive list of Windows supported filesystems.
>
> You asked: Any other thing I missed?

=====
Sylvain Petreolle
[e-mail] 
Fight against Spam ! http://www.euro.cauce.org/en/index.html
ICQ #170597259

"Don't think you are. Know you are." Morpheus, in "Matrix".

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

Add filesytem type NTFS to config

[Tony Lambregts]

Francois Gouget wrote:
> On Tue, 14 Jan 2003, Tony Lambregts wrote:
> [...]
> > > AFAIK, read-write CDs use a special filesystem so they probably get
> > > their own value.
>
> Confirmed: you can use ISO9660 (or ext2fs for that matter), but if you
> want to use your CDRW as a big floppy drive on Windows, then you would
> use UDF (google CDRW UDF).

OK CD-W/RW and DVD-R/RW can use UDF (Universal Disk Format) but what is 
reported by the various flavors of windows (right click - Properties)? 
My guess - CDFS
> > Samba probably reports whatever the share's underlying
> > > filesystem is (at least if the server is a Windows machine).
>
> IIRC, right-click -> Properties on a shared drive tells you what
> filesystem the remote computer is using for that filesystem. It does not
> mean that Windows is not returning some strange value in the function
> you are concerned about but I don't have a way of checking that.  What
> about providing a test app that would enumerate drives and dump the
> values reported by Windows?

Is there a real need for such a conformance test. It seems to me that it 
would be of little value (right click - Properties tells us the same thing)

I do not have another computer to test Samba but IIRC Novell returned 
FAT for its drives circa  Novell 3.1. and again IIRC Windows 98 returns 
NTFS when connected to a NTFS drive on a NT Server.  I could be wrong 
and have no way of checking for myself (aside from Google)
> > I suspect
> > > zip drives just use what the user chooses, i.e. FAT or VFAT, maybe FAT32
> > > though that seems quite unnecessary given their limited size.
>
> Confirmed. I asked a collegue who has a Zip drive and they behave just
> like other removable media (floppies). So you use the usual way to
> format such things so what you get is a FAT disk. Depends on your
> Windows OS of course. On Windows 95 you would get VFAT, on Windows 98SE
> you may get FAT32 instead.
> Of course that does not mean that Windows is not checking that this is a
> Zip drive+FAT combination to return 'foobar' rather than just FAT. But
> it does seem relatively improbable.

There was some kind of calculation that windows 95/8 does. Past 
experience has indicated that drives less than 128 MB can not be 
formated FAT32. A quick search of google points out that disks that are 
smaller than 260 mb are formated with a sector size 512KB. So some 
drives in the range 128 - 265 that have a minimum (built in) sector size 
of 1024 (lots of them) cannot be formated FAT32

This is rather academic since even  DVD-RW is limited to 1.7GB wich is 
less than the 2GB limit for FAT
> > AFAICS you are just guessing. I can do that... but it is not a good way
> > to build specs.
>
> Not really guessing. Just providing a dump of my fuzzy memories of past
> experiences and stuff I read in the hope that it can guide your search
> about an exhaustive list of Windows supported filesystems.
>
> You asked: Any other thing I missed?
>
> At least you missed the filesystem used for CDRW: UDF. Again maybe the
> function you are concerned about will call that CDFS or billfs. But now
> you know that you need to ask someone with a CDRW drive to check what
> the function returns for that drive.

It is not as if I could not make an educated guess myself about these 
things (and google is my friend) Most of the time FAT _works_ the fact 
that Virtual Dub checks for "FAT" is probably an annomaly.  When dealing 
with *nix drives does it matter whether we tell it  "FAT32" or "NTFS". 
They are both _LIES_, by adding "NTFS" It gives the user another 
CASE_PRESERVING option without confusing the user to much.

I would still like to know (for sure) what is retured by the for network 
drives (NT, Novell, Samba, Mac Server?) The same goes for CD/DVD-R/RW 
using UDF. So far I have seen no advantage in doing something more 
elegant (complicated).

Problems install ie5+ie6

[Boris]

I downloaded the latest wine cvs tonight and compiled it on my windows-less
system. I ran ie6setup and ie5setup.exe and it downloads the data from the
web but has problems during installation. Here are two of the current
errors.

1) /usr/local/bin/wine: cannot open builtin library for
'C:\windows\system\regsvr32.exe': /usr/local/lib/wine/regsvr32.exe.so:
invalid ELF header

2) When installing internet explorer 6, I get the following error.
 fixme:wininet:HttpOpenRequestW lpszVersion, lpszReferrer and
lpszAcceptTypes ignored
fixme:wininet:DeleteUrlCacheEntry STUB
(http://download.microsoft.com/download/ie6sp1/finrel/6_sp1/W98NT42KMeXP/EN-
US//HELPCONT.CAB)
fixme:urlmon:URLMonikerImpl_BindToStorage
(0x40453d18)->(0x429f28e8,(nil),{0000000c-0000-0000-c000-000000000046},0x404
15650): stub
fixme:wininet:HttpOpenRequestW lpszVersion, lpszReferrer and lpszAcceptTypes
ignored
fixme:wininet:DeleteUrlCacheEntry STUB
(http://download.microsoft.com/download/ie6sp1/finrel/6_sp1/W98NT42KMeXP/EN-
US//SCR56EN.CAB)
fixme:urlmon:URLMonikerImpl_BindToStorage
(0x429f2c08)->(0x429f2c38,(nil),{0000000c-0000-0000-c000-000000000046},0x404
15650): stub
fixme:wininet:HttpOpenRequestW lpszVersion, lpszReferrer and lpszAcceptTypes
ignored
fixme:wininet:DeleteUrlCacheEntry STUB
(http://download.microsoft.com/download/ie6sp1/finrel/6_sp1/W98NT42KMeXP/EN-
US//README.CAB)
fixme:reg:RegFlushKey (0x98): stub
Created not existing system directory 'C:\WINDOWS\Desktop'
fixme:reg:RegFlushKey (0x98): stub
fixme:reg:RegFlushKey (0x98): stub
fixme:cabinet:process_files (basecab == ^0x8091818): Memory leak.
fixme:cabinet:process_files (basecab == ^0x8092438): Memory leak.
wine: Unhandled exception
 starting debugger... <-And crashs at this point.

Problems install ie5+ie6

[Sylvain Petreolle]

2) did you try to run it with winedbg ?

--- Boris  a écrit : > I downloaded the latest
wine cvs tonight and compiled it on my
> windows-less
> system. I ran ie6setup and ie5setup.exe and it downloads the data
> from the
> web but has problems during installation. Here are two of the current
> errors.
> - /usr/local/bin/wine: cannot open builtin library for
>
> 'C:\windows\system\regsvr32.exe':
> /usr/local/lib/wine/regsvr32.exe.so:
> invalid ELF header
> - When installing internet explorer 6, I get the following error.
>
> fixme:wininet:HttpOpenRequestW lpszVersion, lpszReferrer and
> lpszAcceptTypes ignored
> fixme:wininet:DeleteUrlCacheEntry STUB

(http://download.microsoft.com/download/ie6sp1/finrel/6_sp1/W98NT42KMeXP/EN-
> US//HELPCONT.CAB)
> fixme:urlmon:URLMonikerImpl_BindToStorage

(0x40453d18)->(0x429f28e8,(nil),{0000000c-0000-0000-c000-000000000046},0x404
> 15650): stub
> fixme:wininet:HttpOpenRequestW lpszVersion, lpszReferrer and
> lpszAcceptTypes
> ignored
> fixme:wininet:DeleteUrlCacheEntry STUB

(http://download.microsoft.com/download/ie6sp1/finrel/6_sp1/W98NT42KMeXP/EN-
> US//SCR56EN.CAB)
> fixme:urlmon:URLMonikerImpl_BindToStorage

(0x429f2c08)->(0x429f2c38,(nil),{0000000c-0000-0000-c000-000000000046},0x404
> 15650): stub
> fixme:wininet:HttpOpenRequestW lpszVersion, lpszReferrer and
> lpszAcceptTypes
> ignored
> fixme:wininet:DeleteUrlCacheEntry STUB

(http://download.microsoft.com/download/ie6sp1/finrel/6_sp1/W98NT42KMeXP/EN-
> US//README.CAB)
> fixme:reg:RegFlushKey (0x98): stub
> Created not existing system directory 'C:\WINDOWS\Desktop'
> fixme:reg:RegFlushKey (0x98): stub
> fixme:reg:RegFlushKey (0x98): stub
> fixme:cabinet:process_files (basecab == ^0x8091818): Memory leak.
> fixme:cabinet:process_files (basecab == ^0x8092438): Memory leak.
> wine: Unhandled exception
>  starting debugger... <-And crashs at this point.

=====
Sylvain Petreolle
[e-mail] 
Fight against Spam ! http://www.euro.cauce.org/en/index.html
ICQ #170597259

"Don't think you are. Know you are." Morpheus, in "Matrix".

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

Problems install ie5+ie6

[Greg Turner]

On Tuesday 14 January 2003 09:46 pm, Boris wrote:
> I downloaded the latest wine cvs tonight and compiled it on my
> windows-less system. I ran ie6setup and ie5setup.exe and it downloads
> the data from the web but has problems during installation. Here are
> two of the current errors.
> fixme:cabinet:process_files (basecab == ^0x8091818): Memory leak.
> fixme:cabinet:process_files (basecab == ^0x8092438): Memory leak.
> wine: Unhandled exception
>  starting debugger... <-And crashs at this point.

quite possibly cabextract.c's fault.  i will test it when i get the 
chance.

btw, last I checked (only ~ two weeks ago), ie5 required "urlmon=n" (i 
think microsoft conveniently provides such a thing during the install), 
at the command line, and "windows=nt40", in the config.  ie6 didn't run 
at all, and certainly didn't get to any cabextract's... so this is the 
good kind of failure ;)

Problems install ie5+ie6

[Dominik Strasser]

Boris wrote:
Hello Boris,
> fixme:cabinet:process_files (basecab == ^0x8091818): Memory leak.
> fixme:cabinet:process_files (basecab == ^0x8092438): Memory leak.

There is a problem in cabinet.dll when it tries to free a non allocated 
LZW descriptor.
You can work around this problem by commenting line 1561 in 
cabextract.c. I haven't found the source of the problem yet.

Regards

Dominik

Problems install ie5+ie6

[Shachar Shemesh]

Did you run "wineboot" after the setup finished? As of the version 
currently in CVS, wineboot handles pending renames as well as the "run" 
keys. IE 5.5 adds its own handler to the "RunOnceEx" key, and so all the 
bootup processes should work (didn't work for me - the native RunOnceEx 
was stuck in a loop, but that's something we need to debug seperately).

Shachar

Boris wrote:
> I downloaded the latest wine cvs tonight and compiled it on my windows-less
> system. I ran ie6setup and ie5setup.exe and it downloads the data from the
> web but has problems during installation. Here are two of the current
> errors.
> - /usr/local/bin/wine: cannot open builtin library for
>
> 'C:\windows\system\regsvr32.exe': /usr/local/lib/wine/regsvr32.exe.so:
> invalid ELF header
> - When installing internet explorer 6, I get the following error.
>
> fixme:wininet:HttpOpenRequestW lpszVersion, lpszReferrer and
> lpszAcceptTypes ignored
> fixme:wininet:DeleteUrlCacheEntry STUB
> (http://download.microsoft.com/download/ie6sp1/finrel/6_sp1/W98NT42KMeXP/EN-
> US//HELPCONT.CAB)
> fixme:urlmon:URLMonikerImpl_BindToStorage
> (0x40453d18)->(0x429f28e8,(nil),{0000000c-0000-0000-c000-000000000046},0x404
> 15650): stub
> fixme:wininet:HttpOpenRequestW lpszVersion, lpszReferrer and lpszAcceptTypes
> ignored
> fixme:wininet:DeleteUrlCacheEntry STUB
> (http://download.microsoft.com/download/ie6sp1/finrel/6_sp1/W98NT42KMeXP/EN-
> US//SCR56EN.CAB)
> fixme:urlmon:URLMonikerImpl_BindToStorage
> (0x429f2c08)->(0x429f2c38,(nil),{0000000c-0000-0000-c000-000000000046},0x404
> 15650): stub
> fixme:wininet:HttpOpenRequestW lpszVersion, lpszReferrer and lpszAcceptTypes
> ignored
> fixme:wininet:DeleteUrlCacheEntry STUB
> (http://download.microsoft.com/download/ie6sp1/finrel/6_sp1/W98NT42KMeXP/EN-
> US//README.CAB)
> fixme:reg:RegFlushKey (0x98): stub
> Created not existing system directory 'C:\WINDOWS\Desktop'
> fixme:reg:RegFlushKey (0x98): stub
> fixme:reg:RegFlushKey (0x98): stub
> fixme:cabinet:process_files (basecab == ^0x8091818): Memory leak.
> fixme:cabinet:process_files (basecab == ^0x8092438): Memory leak.
> wine: Unhandled exception
> starting debugger... <-And crashs at this point.

Add filesytem type NTFS to config

[Sylvain Petreolle]

Why not only change _small_ FAT to FAT32 ?
> I am however curious what file system types the various
> implementations 
> of windows will return. These are the ones I am aware of:
>
> HPFS (from OS2's  High Performance File System)
> NTFS
> FAT  Floppies and older (small) hard drives
> FAT32
> CDFS (CD-ROMS)

=====
Sylvain Petreolle
[e-mail] 
Fight against Spam ! http://www.euro.cauce.org/en/index.html
ICQ #170597259

"Don't think you are. Know you are." Morpheus, in "Matrix".

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

Add filesytem type NTFS to config

[Tony Lambregts]

Sylvain Petreolle wrote:
> Why not only change _small_ FAT to FAT32 ?

Well floppies are obviously not FAT32.  No big deal but why stop at 
FAT32. Why not NTFS?

Add filesytem type NTFS to config

[Sylvain Petreolle]

--- Tony Lambregts  a écrit :
> Sylvain Petreolle wrote:
> > Why not only change _small_ FAT to FAT32 ?
>
> Well floppies are obviously not FAT32.  No big deal but why stop at 
> FAT32. Why not NTFS?

Im not against NTFS.  It was just the lazy approach.

But if we extend supported filesystems, see what filesystems are
recognized today by Windows :

floppies are FAT12 (is this vfat for Wine ?)
hard drives => FAT32 / NTFS / HFS (unofficial)
cdroms => CDFS / Audio / RAW
dvds => udf

=====
Sylvain Petreolle
[e-mail] 
Fight against Spam ! http://www.euro.cauce.org/en/index.html
ICQ #170597259

"Don't think you are. Know you are." Morpheus, in "Matrix".

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

Add filesytem type NTFS to config

[Keith Matthews]

On Wed, 15 Jan 2003 08:52:59 +0100 (CET)
Sylvain Petreolle  wrote:
> --- Tony Lambregts  a écrit :
> > Sylvain Petreolle wrote:
> > > Why not only change _small_ FAT to FAT32 ?
> >
> > Well floppies are obviously not FAT32.  No big deal but why stop at 
> > FAT32. Why not NTFS?
>
> Im not against NTFS.  It was just the lazy approach.

Perhaps we should be looking at it in another way ? for example does anyone
know of applications that use the fs type as a sort of 'work on 9X but
not NT' type of test. Given the variation of silly checks for the
registry this is a possibility and might be a major factor.

Add filesytem type NTFS to config

[Philipp Wollermann]

From: "Keith Matthews"
> Perhaps we should be looking at it in another way ? for example does

anyone
> know of applications that use the fs type as a sort of 'work on 9X but
> not NT' type of test. Given the variation of silly checks for the
> registry this is a possibility and might be a major factor.

I can't imagine any program beeing so silly to say "NTFS" = "Windows NT" and
"FAT" = "Windows 9x", as you can install WinNT on a FAT partition.. but you
never know. Why don't we make it configurable in the wine.conf (or is it?)?

By the way we could get rid of this "win95" = "vfat" thing, else we would
have to support "ntfs" = "winnt" as well. ;-)

Philipp

Add filesytem type NTFS to config

[Tony Lambregts]

Sylvain Petreolle wrote:
> --- Tony Lambregts  a écrit :
> > Sylvain Petreolle wrote:
> > > Why not only change _small_ FAT to FAT32 ?
> >
> > Well floppies are obviously not FAT32.  No big deal but why stop at 
> > FAT32. Why not NTFS?
>
> Im not against NTFS.  It was just the lazy approach.

The primary reason that I picked NTFS over FAT32 is simply that FAT32 
has a 4GB file size limitation. NTFS is limited only by disk size. Also 
IIRC a Windows 98 attached to an NTFS volume will return "NTFS" for that 
Drive.  So If we need to to save large files (>2GB) reporting NTFS is 
the logical way to go. I dont think of it a lazy approach. I just can't 
see the benifit of a more elegant (complicated) solution.
> But if we extend supported filesystems, see what filesystems are
> recognized today by Windows :
>
> floppies are FAT12 (is this vfat for Wine ?)

Currently FAT for wine  Windows 98 returns FAT
> hard drives => FAT32 / NTFS / HFS (unofficial)

drives < 128MB are always FAT16 (FAT in windows 98) Partitions over 2GB 
have to be FAT32 or NTFS. There is a FAT32x (extended) meant for 
Partitions over 8GB. I dont know what windows returns for this I am 
willing to bet FAT32.

Microsoft says that the minimum recomended size for NTFS is 10 MB and a 
1.44 floppy is too small to hold the MFT (Master File Table)which is a 
couple of MB by itself.

HPFS is for OS2 compatability and not terribly relevant.
> cdroms => CDFS / Audio / RAW

Windows 98 returns CDFS for audio CD's, CD's and CD-R's. (I don't have a 
CD-RW) Can anyone tell me of a time it returns anything else?
> dvds => udf

What does Windows report (in explorer "Right click - Properties)? My 
guess is that it reports CDFS

So we The way I see it Windows  knows about the following file systems. 
CDFS, FAT, FAT23, NTFS and HPFS.

HPFS is  irrelevent.
CDFS covers all CD like Media.
FAT will deal with all drives less that 2 GB.
NTFS can be used with  drive over 10MB.
FAT32 can be ignored.