Francois Gouget wrote:
On Fri, 4 Mar 2005, Andreas Mohr wrote:
[...]
Free space detection is strictly being based on the properties of the
current "main" partition mapping, as it should be.
There really isn't any way for Wine to account for a "mysteriously much
bigger" "special" directory inside th
On Fri, 4 Mar 2005, Andreas Mohr wrote:
[...]
Free space detection is strictly being based on the properties of the
current "main" partition mapping, as it should be.
There really isn't any way for Wine to account for a "mysteriously much
bigger" "special" directory inside the current drive that Wi
Mike Hearn wrote:
3) The artwork in the file pickers sucks ass. Sorry, it does. It's ugly as
sin and for some reason the Desktop icon is an arrow, not a desk.
This doesn't matter when you only have C: and Z: drives. It does matter
when you have 2 CD drives, 2 Windows drives, a floppy and a
Hi Andres,
--- Andreas Mohr <[EMAIL PROTECTED]> wrote:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/kmarch/hh/kmarch/PlugPlay_289c8080-9400-4cd0-9d44-d637210e8567.xml.asp
> and maybe
> http://support.microsoft.com/default.aspx?scid=kb;en-us;867819
> for how Windows does drive l
Mike Hearn wrote:
So, there are 4 obvious problems with our current drive management code:
1) We add links to the floppy drive. We should blacklist it, as it causes
a big delay in the file open dialogs as we poll the drive which sits
there spinning its motors naval-gazing. How many people still
Andreas Mohr wrote:
Hi,
On Fri, Mar 04, 2005 at 01:57:55PM +0100, Holly Bostick wrote:
Speaking of free disk space detection I have had it happen with at
least 2 different programs (I can document more fully, just not this
second) that if I have a 20 GB partition ("games", 6GB free) mounted
On Fri, 04 Mar 2005 09:54:09 +, Mike Hearn <[EMAIL PROTECTED]> wrote:
> So, there are 4 obvious problems with our current drive management code:
>
> 1) We add links to the floppy drive. We should blacklist it, as it causes
>a big delay in the file open dialogs as we poll the drive which si
Hi,
On Fri, Mar 04, 2005 at 01:57:55PM +0100, Holly Bostick wrote:
> Mike Hearn wrote:
> >On Fri, 2005-03-04 at 11:18 +0100, Alexandre Julliard wrote:
> >>Mike Hearn <[EMAIL PROTECTED]> writes:
> >>
> >>>2) We don't add any device symlinks. Some programs need these
> >>> eg d:: -> /dev/cdrom
> >>
Mike Hearn wrote:
On Fri, 2005-03-04 at 11:18 +0100, Alexandre Julliard wrote:
Mike Hearn <[EMAIL PROTECTED]> writes:
2) We don't add any device symlinks. Some programs need these
eg d:: -> /dev/cdrom
That should never be needed on a standard setup. If you know of a case
where it's required that
> Ah, so this means that the directory change
> notification mechanism
> applies to volume notification as well? Or is it
> still a somewhat separate
> API?
>
> Nevermind, at least you just told us that this API
> exists, so we should
> try to get the hal/hotplug/fam stuff integratedf
> towards th
> Ah, so this means that the directory change
> notification mechanism
> applies to volume notification as well? Or is it
> still a somewhat separate
> API?
>
> Nevermind, at least you just told us that this API
> exists, so we should
> try to get the hal/hotplug/fam stuff integratedf
> towards th
Hi,
On Fri, Mar 04, 2005 at 01:08:27PM +0200, Boaz Harrosh wrote:
>
>
> Andreas Mohr wrote:
>
> >Are you sure the apps get notified, too?
> >ISTR XP doesn't automatically update the Explorer view after you have
> >plugged in a USB stick, or maybe I'm wrong?
> >
> >
> >
> Yes it does. and any p
Guido Draheim <[EMAIL PROTECTED]> writes:
> Thanks reminding the "exotic" setups. I did just stop updating
> to the latest wine at some point. Too many exotic changes in
> wine since then. :-)=)
> http://bugs.winehq.org/show_bug.cgi?id=1283
As it says in the bug, this should no longer be an issue
Mike Hearn wrote:
> On Fri, 2005-03-04 at 11:30 +0100, Alexandre Julliard wrote:
>
>>It's not needed for low level drive access either, it's all
>>automatically detected. The exception is with "exotic" setups like the
>>ones using an automounter (though that could probably be fixed too, it
>>jus
Andreas Mohr wrote:
Are you sure the apps get notified, too?
ISTR XP doesn't automatically update the Explorer view after you have
plugged in a USB stick, or maybe I'm wrong?
Yes it does. and any program can. There is an API to watch for File
System changes. From files (for editors), to folder
On Fri, 2005-03-04 at 11:30 +0100, Alexandre Julliard wrote:
> It's not needed for low level drive access either, it's all
> automatically detected. The exception is with "exotic" setups like the
> ones using an automounter (though that could probably be fixed too, it
> just hasn't been done yet).
> "Alexandre" == Alexandre Julliard <[EMAIL PROTECTED]> writes:
Alexandre> Mike Hearn <[EMAIL PROTECTED]> writes:
>> 2) We don't add any device symlinks. Some programs need these eg d::
>> -> /dev/cdrom
Alexandre> That should never be needed on a standard setup. If you know
Hi,
On Fri, Mar 04, 2005 at 09:54:09AM +, Mike Hearn wrote:
> 4) We don't detect new drives as they are mounted into the system, eg if I
>start a Windows program and then realize that my work is actually on a
>USB key, if I plug that key in Nautilus and GTK+ (and probably KDE)
>app
Mike Hearn <[EMAIL PROTECTED]> writes:
> At least, I seem to recall adding the :: symlinks being the answer to
> quite a few tech support queries on #winehq, and I know I've needed to
> do it before. Is there anything apart from low level drive access where
> the device symlink is needed?
It's no
On Fri, 2005-03-04 at 11:18 +0100, Alexandre Julliard wrote:
> Mike Hearn <[EMAIL PROTECTED]> writes:
>
> > 2) We don't add any device symlinks. Some programs need these
> >eg d:: -> /dev/cdrom
>
> That should never be needed on a standard setup. If you know of a case
> where it's required th
Mike Hearn <[EMAIL PROTECTED]> writes:
> On Fri, 04 Mar 2005 09:54:09 +, Mike Hearn wrote:
> > 1) We add links to the floppy drive. We should blacklist it, as it causes
> >a big delay in the file open dialogs as we poll the drive which sits
> >there spinning its motors naval-gazing. Ho
Mike Hearn <[EMAIL PROTECTED]> writes:
> 2) We don't add any device symlinks. Some programs need these
>eg d:: -> /dev/cdrom
That should never be needed on a standard setup. If you know of a case
where it's required that should be considered a bug.
--
Alexandre Julliard
[EMAIL PROTECTED]
On Fri, 04 Mar 2005 09:54:09 +, Mike Hearn wrote:
> 1) We add links to the floppy drive. We should blacklist it, as it causes
>a big delay in the file open dialogs as we poll the drive which sits
>there spinning its motors naval-gazing. How many people still use
>floppy disks in 200
So, there are 4 obvious problems with our current drive management code:
1) We add links to the floppy drive. We should blacklist it, as it causes
a big delay in the file open dialogs as we poll the drive which sits
there spinning its motors naval-gazing. How many people still use
floppy
24 matches
Mail list logo
