Alexandre Goujon writes:
> The cdrom test file will be used to test ioctl (results, structure size...)
> Each drive is tested and skipped gracefully if ioctl not supported or not a
> CDROM drive.
I don't see a need for a new file, particularly since disk extents are
not CDROM
On Tue, Jan 25, 2011 at 12:29 AM, Ken Thomases wrote:
> Loïc,
>
> Your mailer seems to have mangled your patch with line wrapping. There are
> some suggestions on Wine's SubmittingPatches wiki page for avoiding this.
> Primarily, you should attach the patch to your email. If you already did
>
---
dlls/ntdll/cdrom.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/dlls/ntdll/cdrom.c b/dlls/ntdll/cdrom.c
index 59f85a0..6a6d8e0 100644
--- a/dlls/ntdll/cdrom.c
+++ b/dlls/ntdll/cdrom.c
@@ -1121,6 +1121,10 @@ static NTSTATUS CDROM_Verify(int dev, int fd)
On 25 January 2011 01:06, Charles Davis wrote:
> Uh, you mean git send-email, right?
Right.
On 1/24/11 4:51 PM, Henri Verbeet wrote:
> On 25 January 2011 00:29, Ken Thomases wrote:
>> Your mailer seems to have mangled your patch with line wrapping. There are
>> some suggestions on Wine's SubmittingPatches wiki page for avoiding this.
>> Primarily, you should attach the patch to your
On 25 January 2011 00:29, Ken Thomases wrote:
> Your mailer seems to have mangled your patch with line wrapping. There are
> some suggestions on Wine's SubmittingPatches wiki page for avoiding this.
> Primarily, you should attach the patch to your email. If you already did
> that, then you m
Loïc,
Your mailer seems to have mangled your patch with line wrapping. There are
some suggestions on Wine's SubmittingPatches wiki page for avoiding this.
Primarily, you should attach the patch to your email. If you already did that,
then you may need to use a different mailer. For example,
---
dlls/ntdll/cdrom.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/dlls/ntdll/cdrom.c b/dlls/ntdll/cdrom.c
index 59f85a0..6a6d8e0 100644
--- a/dlls/ntdll/cdrom.c
+++ b/dlls/ntdll/cdrom.c
@@ -1121,6 +1121,10 @@ static NTSTATUS CDROM_Verify(int dev, int fd)
r
On Jan 22, 2011, at 8:35 AM, Loïc Maury wrote:
> I have add comment in the code for the patch.
> @@ -1121,6 +1121,10 @@ static NTSTATUS CDROM_Verify(int dev, int fd)
> return STATUS_SUCCESS;
> else
> return STATUS_NO_MEDIA_IN_DEVICE;
> +/* At this point, we know that we hav
Hello,
I have add comment in the code for the patch.
Thank you
Loïc
---
dlls/ntdll/cdrom.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/dlls/ntdll/cdrom.c b/dlls/ntdll/cdrom.c
index 59f85a0..d65850d 100644
--- a/dlls/ntdll/cdrom.c
+++ b/dlls/ntdll/cdrom.c
@@ -112
On Thu, Dec 30, 2010 at 11:20 AM, maury loïc wrote:
> Hello,
>
> it's my first patch, and it implement the CDROM_Verify()
> to work on Mac Os.
>
> merci
>
> Loïc
>
> ---
> dlls/ntdll/cdrom.c |2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/dlls/ntdll/cdrom.c b/dlls/
On 1/1/11 4:07 AM, maury loïc wrote:
On Sat, Jan 1, 2011 at 2:22 AM, James McKenzie
mailto:jjmckenzi...@earthlink.net>> wrote:
On 12/31/10 1:50 PM, Charles Davis wrote:
On 12/31/10 1:11 PM, Ken Thomases wrote:
I should add that this patch seem correct to me. It
On Sat, Jan 1, 2011 at 2:22 AM, James McKenzie
wrote:
> On 12/31/10 1:50 PM, Charles Davis wrote:
>
>> On 12/31/10 1:11 PM, Ken Thomases wrote:
>>
>>> I should add that this patch seem correct to me. It couldn't hurt to get
>>> Charles Davis's input, of course.
>>>
>> I agree, for now. He should
On 12/31/10 1:50 PM, Charles Davis wrote:
On 12/31/10 1:11 PM, Ken Thomases wrote:
I should add that this patch seem correct to me. It couldn't hurt to get
Charles Davis's input, of course.
I agree, for now. He should at least put a comment in to the effect of
"if we got this far, there's alr
On 12/31/10 1:11 PM, Ken Thomases wrote:
> I should add that this patch seem correct to me. It couldn't hurt to get
> Charles Davis's input, of course.
I agree, for now. He should at least put a comment in to the effect of
"if we got this far, there's already media in the drive."
> MSDN documents
On Dec 31, 2010, at 1:38 PM, Ken Thomases wrote:
> Why does that matter? The question is, under what circumstances does it end
> up in CDROM_Verify()? What is the right behavior of CDROM_Verify() and how
> would that be implemented on Mac OS X?
I should add that this patch seem correct to me.
On Dec 30, 2010, at 9:36 AM, James McKenzie wrote:
> This has been critically examined by several people and if the solution were
> this simple it would have been put in place a long time ago. Charles Davis
> has spend over a year looking at how to implement CDROM functionality for
It create the
>device, only if the media
>is already present. Logically, CDROM_Verify() return success, because when
>we are in CDROM_Verify()
>we already know the device.
>
>What do you think ?
>
This has been critically examined by several people and if the solution were
this simple it
Hello Ken and the Wine community,
For what i understood, The function CDROM_Verify(), verify if the media is
present on the device, and Wine try to open
the device(in Mac Os case), before call the CDROM_Verify().
But Mac Os manage the device differently from the other Os. It create the
device, on
Hi Loïc,
On Dec 30, 2010, at 4:20 AM, maury loïc wrote:
> it's my first patch, and it implement the CDROM_Verify()
> to work on Mac Os.
I think most people are going to need more explanation for why this is a
legitimate way to implement this function on Mac OS X. :)
Cheers,
Ken
Hello,
it's my first patch, and it implement the CDROM_Verify()
to work on Mac Os.
merci
Loïc
---
dlls/ntdll/cdrom.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/dlls/ntdll/cdrom.c b/dlls/ntdll/cdrom.c
index 59f85a0..185f397 100644
--- a/dlls/ntdll/cdrom.c
+++ b/dl
* On Fri, 3 Sep 2010, joerg-cyril.hoe...@t-systems.com wrote:
>
> Saulius Krasuckas wrote:
> >Then we would know for sure :)
> As far as MCICDA is concerned, it doesn't look like it knows about
> multi-sessions. All it offers is to play music. Therefore the mcicda
> tests is not the right place
Saulius,
Saulius Krasuckas wrote:
>It would be nice to indicate disks containing tracks of different types
>(sessions) in the log and to extract some info from the data track.
>Drive info would be also interesting to see in the log.
It is on purpose that I did not write too specific info to the lo
* On Thu, 2 Sep 2010, joerg-cyril.hoe...@t-systems.com wrote:
>
> According to http://de.wikipedia.org/wiki/Compact_Disc
> "CD-Extra" is a multi-session disc. So it would be like Jeff Zaroyko's
> disc.
Yes, both K3B and "Nero Info Tool v2" reports two sessions on my disk.
> I don't know whether
Hi,
Saulius Krasuckas wrote:
>(I found one such CD today and realised it isn't a Mixed Mode CD which
>the test needs for the sake of completeness)
Thanks for caring about avoiding skipping tests.
>would CD Extra disk (with different types of tracks on the same disk) also
>be interesting to test?
Hello,
* On Wed, 4 Aug 2010, joerg-cyril.hoe...@t-systems.com wrote:
>
> Jeff Zaroyko wrote:
>
> >> mcicda: 98 tests executed (0 marked as todo, 2 failures), 0 skipped.
> >With a dual mode cd which has a data and audio tracks:
> >mcicda: 90 tests executed (0 marked as todo, 14 failures), 0 skipp
Guys... I just started looking into developing for the ipad... am i
going to have the same issues?
I know, i know.. i'm a newbie with objective c. lemme know...
On Thu, Aug 5, 2010 at 8:14 AM, wrote:
> Jeff,
>
>>if I:
>>> resume c # yields MCIERR_HARDWARE
>>nothing printed
> This is not compatib
Jeff,
>if I:
>> resume c # yields MCIERR_HARDWARE
>nothing printed
This is not compatible with the test that does not report failure on your
system:
+err = mciSendString("resume c", buf, sizeof(buf), hwnd);
+ok(err == MCIERR_HARDWARE, "resume without play: %s\n", dbg_mcierr(err));
/* not
On Thu, Aug 5, 2010 at 11:51 PM, wrote:
> Hi,
>
>> Things you can try out using the interactive MCI shell:
>> open cdaudio alias c
>> status c type track 1
>> set c time format tmsf
>> seek c to start
>> play c from 1 to 2 wait
>>This works - I hear music.
> What the test does is not fundamentall
Hi,
> Things you can try out using the interactive MCI shell:
> open cdaudio alias c
> status c type track 1
> set c time format tmsf
> seek c to start
> play c from 1 to 2 wait
>This works - I hear music.
What the test does is not fundamentally different. I'd
appreciate if you could isolate the
On Thu, Aug 5, 2010 at 6:39 PM, > Hi,
>
> Jeff Zaroyko wrote:
>>mcicda.c:355: Test failed: PLAY from 1 notify: MCIERR_HARDWARE
>>mcicda: 90 tests executed (0 marked as todo, 14 failures), 0 skipped.
>
> All failures are explained by your drive's inability to play any piece
> of music from the CD
Hi,
Jeff Zaroyko wrote:
>mcicda.c:355: Test failed: PLAY from 1 notify: MCIERR_HARDWARE
>mcicda: 90 tests executed (0 marked as todo, 14 failures), 0 skipped.
All failures are explained by your drive's inability to play any piece
of music from the CD in your system. PLAY fails, causing other test
Hi,
Jeff Zaroyko wrote:
>> mcicda: 98 tests executed (0 marked as todo, 2 failures), 0 skipped.
>With a dual mode cd which has a data and audio tracks:
>mcicda: 90 tests executed (0 marked as todo, 14 failures), 0 skipped.
>Tried a different cd with audio tracks only:
>mcicda: 90 tests executed (
On Wed, Aug 4, 2010 at 4:27 PM, Jeff Zaroyko wrote:
> I noticed the midi notes playing, didn't think much of it.
That's nothing, some tests record whatever comes via the microphone
then play it back. Might be scary if you forget about the tests :)
Octavian
On Wed, Aug 4, 2010 at 10:36 PM, wrote:
> Hi,
>
> Wine's testbt job #4280
> http://testbot.winehq.org/JobDetails.pl?Key=4280
> contains both a patch and a binary for new MCICDA=MCI CD-audio tests.
>
> It already contains most of what I want in the initial release but
> would benefit from testing
Hi,
Wine's testbt job #4280
http://testbot.winehq.org/JobDetails.pl?Key=4280
contains both a patch and a binary for new MCICDA=MCI CD-audio tests.
It already contains most of what I want in the initial release but
would benefit from testing on a broad range of native MS systems.
Please invoke it
> I know. I have patches for all that. Did I not just write an email back
> to Roderick talking about the SCSITaskDevice?
Easy now. I didn't get your reply to Roderick until after Emmanuel's
response. Not only that, but with pretty large differences in time
zone, it's normal to have delayed resp
Emmanuel Maillard wrote:
> Hi,
>
> For peoples interested with cd-rom support on Mac OS X, i think that you
> need to investigated in IOKit,
> especially in SCSITaskDeviceInterface and MMCDeviceInterface.
>
> Emmanuel
I know. I have patches for all that. Did I not just write an email back
to Rode
Roderick Colenbrander wrote:
> Hi,
>
> I don't know much about the cd-rom stuff on osx but I expect there are
> much more issues of which some are more severe than this (and the
> solution might fix all the issues). I believe that on osx there is no
> such thing as direct cd-rom access (anymore) a
joerg-cyril.hoe...@t-systems.com wrote:
> Chip,
>
> I had hoped that your patch would allow mcicda to work,
> cf. bug #20323, alas it is not so. Instead I get to see
>
> ERR("This version of Mac OS X does not support IOCDAudioControl"
> on Leopard.
>
> I googled slightly and found a message fro
Hi,
For peoples interested with cd-rom support on Mac OS X, i think that
you need to investigated in IOKit,
especially in SCSITaskDeviceInterface and MMCDeviceInterface.
Emmanuel
Le 14 oct. 2009 à 17:50, Roderick Colenbrander a écrit :
Hi,
I don't know much about the cd-rom stuff on osx
Hi,
I don't know much about the cd-rom stuff on osx but I expect there are
much more issues of which some are more severe than this (and the
solution might fix all the issues). I believe that on osx there is no
such thing as direct cd-rom access (anymore) and due to this I think
wine can't read au
Chip,
I had hoped that your patch would allow mcicda to work,
cf. bug #20323, alas it is not so. Instead I get to see
ERR("This version of Mac OS X does not support IOCDAudioControl"
on Leopard.
I googled slightly and found a message from 2004:
http://lists.apple.com/archives/darwin-drivers/200
attrs = GetFileAttributesA(drive);
> +if (attrs == INVALID_FILE_ATTRIBUTES)
> +{
> +trace("Unmounted CDROM with type DRIVE_CDROM\n");
> + ok(GetLastError() == ERROR_NOT_READY,
> + "Expected ERROR_NOT_REA
M even when no CD is mounted */
+if (type == 5)
+{
+DWORD attrs;
+
+SetLastError(0xdeadbeef);
+attrs = GetFileAttributesA(drive);
+if (attrs == INVALID_FILE_ATTRIBUTES)
+{
+ trace("Unmounted CDRO
On 4/3/07, Tom Spear <[EMAIL PROTECTED]> wrote:
On 4/3/07, Jesse Allen <[EMAIL PROTECTED]> wrote:
> Slackware will have hal soon though.
Really? As in v11.1, or as in v12? I dont care about having to add
them manually either, but some people are really annoyed by it.. One
thing I should note
On Di, 2007-04-03 at 12:20 -0500, Tom Spear wrote:
> On 4/3/07, Jesse Allen <[EMAIL PROTECTED]> wrote:
> > Slackware will have hal soon though.
> One thing I should note is that even in my config.log, there isnt
> any sort of big warning about hal not being there
> like there is about fontforge o
On 4/3/07, Tom Spear <[EMAIL PROTECTED]> wrote:
On 4/3/07, Jesse Allen <[EMAIL PROTECTED]> wrote:
> Slackware will have hal soon though.
Really? As in v11.1, or as in v12? I dont care about having to add
them manually either, but some people are really annoyed by it.. One
thing I should note
The drives are present when you run winecfg?, I've treid on several distros
and they aren't present.
From: "Jesse Allen" <[EMAIL PROTECTED]>
To: "EA Durbin" <[EMAIL PROTECTED]>
CC: wine-devel@winehq.org, [EMAIL PROTECTED]
Subject: Re: wineprefixcre
On 4/3/07, Jesse Allen <[EMAIL PROTECTED]> wrote:
Slackware will have hal soon though.
Really? As in v11.1, or as in v12? I dont care about having to add
them manually either, but some people are really annoyed by it.. One
thing I should note is that even in my config.log, there isnt any sor
On 4/3/07, EA Durbin <[EMAIL PROTECTED]> wrote:
The drives are not created under dosdevices in Ubuntu/Gentoo. I always have
to go in and add the drom drive manually in winecfg under both distros.
When I tried last Ubuntu it worked just fine. Slackware 11 is
currently the only big one that doe
On 4/3/07, Alexander Nicolaysen Sørnes <[EMAIL PROTECTED]> wrote:
Tirsdag 03 april 2007 14:07, skrev EA Durbin:
> The drives are not created under dosdevices in Ubuntu/Gentoo. I always have
> to go in and add the drom drive manually in winecfg under both distros.
>
They are added fine for me in
and that wine is built with the appropriate use flags.
Regards,
Alexander N. Sørnes
> >From: Marcus Meissner <[EMAIL PROTECTED]>
> >To: EA Durbin <[EMAIL PROTECTED]>
> >CC: [EMAIL PROTECTED], wine-devel@winehq.org
> >Subject: Re: wineprefixcreate - create symli
o symlink the :: to the cdrom devices
(d:: -> /dev/cdwhatever)
Ciao, Marcus
Well, Slackware 11 for one. Of course I had never actually checked
out gentoo before, and was just told exactly what it is, so now I'm
switching to it.. But its gonna be a while.
--
Thanks
Tom
Check out th
Subject: Re: wineprefixcreate - create symlink to cdrom drives(Try 2)
Date: Tue, 3 Apr 2007 07:10:32 +0200
On Mon, Apr 02, 2007 at 06:41:09PM -0500, EA Durbin wrote:
> Is there anything wrong with this?
We do this dynamically using "hal" in explorer.exe already...
What OS do you use that it
On Mon, Apr 02, 2007 at 06:41:09PM -0500, EA Durbin wrote:
> Is there anything wrong with this?
We do this dynamically using "hal" in explorer.exe already...
What OS do you use that it does not work?
Also you should also symlink the :: to the cdrom devices
(d:: -> /dev/cdwhatever)
Ciao, Marcus
Is there anything wrong with this?
From dd27e3eafa77b216d940538e38f0442736b67bc7 Mon Sep 17 00:00:00 2001
From: EA Durbin <[EMAIL PROTECTED]>
Date: Mon, 2 Apr 2007 18:37:43 -0500
Subject: Create symlinks to cdrom drives
---
tools/wineprefixcreate.in | 21 +
1 files c
On 4/1/07, EA Durbin <[EMAIL PROTECTED]> wrote:
>From: Vitaliy Margolen <[EMAIL PROTECTED]>
>To: EA Durbin <[EMAIL PROTECTED]>
>CC: wine-devel@winehq.org
>Subject: Re: winecfg and cdrom drives
>Date: Sun, 01 Apr 2007 11:14:55 -0600
>
>EA Durbin wrote:
&g
From: Vitaliy Margolen <[EMAIL PROTECTED]>
To: EA Durbin <[EMAIL PROTECTED]>
CC: wine-devel@winehq.org
Subject: Re: winecfg and cdrom drives
Date: Sun, 01 Apr 2007 11:14:55 -0600
EA Durbin wrote:
>
>
>> Aren't we doing this already?
>>
>>
>> Al
EA Durbin wrote:
>
>
>> Aren't we doing this already?
>>
>>
>> Alexander N. Sørnes
>>
>> > >> >
>> > >> >cd rom drives should be detected without user intervention, imho
>> > >> >
>> > >> >users shouldn't have to run a special gui config tool to get their
>> > >> >drives recognized
>> > >> >
>>
ves recognized
> >> >
> >> >so if it needs fixing, let's fix it in e.g. wineprefixcreate
> >
> >--
> >Wine for Windows ISVs: http://kegel.com/wine/isv
No, we aren't. I have to setup the cdrom drive manually on every distro I've
tried. W
Søndag 01 april 2007 18:11, skrev EA Durbin:
> Does anyone who is Mac saavy have ideas on the best way to accomplish cdrom
> detection in wineprefixcreate across Mac OSX and *nix platforms?
>
> >From: "Dan Kegel" <[EMAIL PROTECTED]>
> >To: "EA Durbin&qu
Does anyone who is Mac saavy have ideas on the best way to accomplish cdrom
detection in wineprefixcreate across Mac OSX and *nix platforms?
From: "Dan Kegel" <[EMAIL PROTECTED]>
To: "EA Durbin" <[EMAIL PROTECTED]>
Subject: Re: winecfg and cdrom drives
Date: S
On 6/1/06, Jesse Allen <[EMAIL PROTECTED]> wrote:
What about the device node symlink? It's needed for the games alot and
it's the number one thing I get asked for help for now. We don't have
an easy way to detect it, although HAL should be able fix it.
Right well that's us being borked somewher
On 6/1/06, Mike Hearn <[EMAIL PROTECTED]> wrote:
The location CD drives are mounted changes between systems, this patch is
essentially specific to yours. Wine already supports HAL, which should
solve this in a more correct manner (though we have reports it doesn't
work for some games!), so how co
"Vincent Povirk" <[EMAIL PROTECTED]> writes:
> So the HAL thing doesn't work for everyone, and this works for a lot
> of people. When you see /media/cdrom, you can be sure it's a cd-rom
> drive. So why not use it?
Because HAL is supposed to work (assuming you
s!), so how comes that's not enough?
thanks -mike
I think /media/cdrom is actually some sort of standard. A google
search led me to
http://www.pathname.com/fhs/pub/fhs-2.3.html#MEDIAMOUNTPOINT
I don't know where this standard gets any authority, but most modern
linux distros I've s
The location CD drives are mounted changes between systems, this patch is
essentially specific to yours. Wine already supports HAL, which should
solve this in a more correct manner (though we have reports it doesn't
work for some games!), so how comes that's not enough?
thanks -mike
On Thu, 1 Jun 2006, Mike McCormack wrote:
+ln -s /media/cdrom "$WINEPREFIX/dosdevices/m:"
Wouldn't it be better to create it as the d: drive?
That's usually where CD-ROM drives end up on Windows...
--
Francois Gouget <[EMAIL PROTECTED]> http://fg
On Mon, 2005-03-14 at 11:47 +0100, Thomas Zeeman wrote:
> So far it seems my memory wasn't all that good, because 2.6.4, 2.6.6
> and 2.6.7 did not work. I'm working on some logs with relay and seh,
> but relay seems to be failing on me with the latest wine release
> (using wine's deb for 2005-03-10
Hi Jesse,
On Sun, 13 Mar 2005 21:46:19 -0700, Jesse Allen <[EMAIL PROTECTED]> wrote:
> they actually should be both exhibiting trouble on x86-64. Also, Andi
> Kleen has made up x86-64 patches, but hasn't merged them because they
> are untested. I offered to have them tested. So perhaps I'll get
On Sun, 13 Mar 2005 03:55:37 -0500, Gavriel State <[EMAIL PROTECTED]> wrote:
>
> Actually, we first learned about the issue in the November-December
> timeframe, and mentioned it in our 4.2 release notes in December. In
> general, we still recommend that people use 2.4 kernels, since the
> sche
Jesse Allen wrote:
On Mon, 7 Mar 2005 18:28:36 -0700, Jesse Allen <[EMAIL PROTECTED]> wrote:
Well, even if cedega works, it doesn't help us. I'm sure their copy
protection support is completely different. When copy protection
broke on x86 and wine, the cedega side was completely
On Mon, 7 Mar 2005 18:28:36 -0700, Jesse Allen <[EMAIL PROTECTED]> wrote:
>
> Well, even if cedega works, it doesn't help us. I'm sure their copy
> protection support is completely different. When copy protection
> broke on x86 and wine, the cedega side was completely quiet on it.
Well, I've l
Le lun 07/03/2005 à 15:34, T.J. Zeeman a écrit :
[snip]
> PS Are the Debian maintainer and wine on speaking terms again? An
> apt-get update showed that 20050211 has entered sid and it wanted to
> replace my current install from winehq.
Ove Kaaven (Debian's Wine maintainer) released a 20050111 pac
gt; answer my memory can serve.
>
> The last thing I noted was a slight difference in behaviour on mounting
> the cdrom. With 2.6.8 I have to become root in the chroot to do an
> umount -f /cdrom to get it unmounted in the chroot. With 2.6.10 and .11
> I could do it as an ordinary
der which I played it then. It was an earlier version of
debian's pure64 and a sid chroot from around that time is the best
answer my memory can serve.
The last thing I noted was a slight difference in behaviour on mounting
the cdrom. With 2.6.8 I have to become root in the chroot to do an
umount -
to work with 2.6.8 either. Both .8 and .10 give
> > the same dialog asking for the cdrom to be inserted.
>
> Oh do you know any kernel version that does work?
I don't know of any kernel-version that does work, but I have asked on
the debian-amd64 list and someone over there claimed
On Thu, 3 Mar 2005 09:22:59 +0100, Thomas Zeeman <[EMAIL PROTECTED]> wrote:
>
> OK, if 2.6.8 is supposed to work, then this is likely another problem.
> I can't get Warcraft 3 to work with 2.6.8 either. Both .8 and .10 give
> the same dialog asking for the cdrom to be in
On Thu, 3 Mar 2005 09:22:59 +0100, Thomas Zeeman <[EMAIL PROTECTED]> wrote:
>
> OK, if 2.6.8 is supposed to work, then this is likely another problem.
> I can't get Warcraft 3 to work with 2.6.8 either. Both .8 and .10 give
> the same dialog asking for the cdrom to be i
ve
the same dialog asking for the cdrom to be inserted.
[snip strace output]
> This is from the test program?
Yes.
regards,
Thomas
On Wed, 2 Mar 2005 09:59:29 -0700, Jesse Allen <[EMAIL PROTECTED]> wrote:
> You need to make sure that 2.6.8 works and
> 2.6.9-rc1 or 2 breaks it, for this to be the same case. I know the
> initial two patches did touch amd64, and the later fixes have not been
> migrated to amd64.
>
Here Andi
On Wed, 02 Mar 2005 12:52:38 +, Mike Hearn <[EMAIL PROTECTED]> wrote:
> > I guess you meant the problems refered to in WWN250
> > (http://www.winehq.com/?issue=250). I checked and the patch there is
> > only for i386. I ported those to the x86_64 files (see attachments) and
> > tried again to n
T.J. Zeeman wrote:
Warcraft still complains about the CD-rom being MIA though :( I'll see
if I can dig up a few hints from the log this weekend.
Make sure your kernel hsa the ptrace regression fixes in.
I guess you meant the problems refered to in WWN250
(http://www.winehq.com/?issue=250). I check
> Message du 15/04/04 00:35> De : Alexandre Julliard <[EMAIL PROTECTED]>> A : Christian Costa <[EMAIL PROTECTED]>> Copie à : wined <[EMAIL PROTECTED]>> Objet : Re: statvfs and cdrom problem> Christian Costa <[EMAIL PROTECTED]>writes:> > > Yes,
Christian Costa <[EMAIL PROTECTED]> writes:
> Yes, this works fine. Thanks. :-)
> When do you plan to rewrite GetFreeDiskSpace?
In a few days I guess. There are still some missing features in
NtCreateFile that need to be done first.
--
Alexandre Julliard
[EMAIL PROTECTED]
Alexandre Julliard wrote:
Christian Costa <[EMAIL PROTECTED]> writes:
I'm trying to make GetFreeDiskSpace working with CDROM because a game
needs it.
However, I'm experiencing problem with statvfs...
Indeed, statvfs always returns f_frsize = 0 and f_blocks = 0.
If I cd to /mnt
Christian Costa <[EMAIL PROTECTED]> writes:
> I'm trying to make GetFreeDiskSpace working with CDROM because a game
> needs it.
> However, I'm experiencing problem with statvfs...
> Indeed, statvfs always returns f_frsize = 0 and f_blocks = 0.
> If I cd to /mnt/c
Hi,
I'm trying to make GetFreeDiskSpace working with CDROM because a game
needs it.
However, I'm experiencing problem with statvfs...
Indeed, statvfs always returns f_frsize = 0 and f_blocks = 0.
If I cd to /mnt/cdrom or edit a file in it, this does not help however
if I run a grep
I am working on a Solaris CDROM plugin, but can't seem to get past the
configuration stage. I get
ASPI_GetNumControllers Could not open HKEY_DYN_DATA\WineScsi
How do I get wine to setup this key ?
Thanks
Bob
n Erics rewrite?
the plan is that all physical volumes and cdrom will have the correctly
configured device (which can be overriden)
A+
On Wed, 2004-01-21 at 23:18, Alexandre Julliard wrote:
> We obviously can't print warnings on the console for every config
> parameter that might be wrong. That's a job for winecheck.
OK. Is there a reason this isn't autodetected anyway, or is that coming
up in Erics rewrite?
Mike Hearn <[EMAIL PROTECTED]> writes:
> OK, so I forgot the changelog entry. Apart from that, any reason this
> patch bounced?
We obviously can't print warnings on the console for every config
parameter that might be wrong. That's a job for winecheck.
--
Alexandre Julliard
[EMAIL PROTECTED]
OK, so I forgot the changelog entry. Apart from that, any reason this
patch bounced?
On Tue, 13 Jan 2004 19:11:17 +, Mike Hearn wrote:
> I wasted half and hour tracing through the cdrom subsystem to find out why
> halflife wasn't playing any music, only to find it was a config fil
Well, I used c:\windows\cdplayer.exe :) It works perfectly, in fact...
On Wed, 14 Jan 2004 07:40:04 +1000, Robert Lunnon wrote:
> I have just finished embelishing the cdrom driver to support solaris but I
> have nothing to test it against. Can anyone recommend a good test progr
I have just finished embelishing the cdrom driver to support solaris but I
have nothing to test it against. Can anyone recommend a good test program for
excercising CDROM ioctls ?
Thanks
Bob
> "Vitaly" == Vitaly Lipatov <[EMAIL PROTECTED]> writes:
Vitaly> On 20 äÅËÁÂÒØ 2003 22:34, Hans Verkuil wrote:
>> planning to make a patch for the DeviceIOControls? I've added them
>> myself in order to allow DVD Shrink to use encrypted DVDs. As the
>> implementation is just pa
On 20 Декабрь 2003 22:34, Hans Verkuil wrote:
> planning to make a patch for the DeviceIOControls? I've added
> them myself in order to allow DVD Shrink to use encrypted
> DVDs. As the implementation is just passing on the
Really we will can use any disks with copy protection system?
--
Lav
Vitaly
Hello Uwe,
Uwe Bonnes wrote:
> appended patch opens the devicefile connected to a drive as connected by
> the user in ~/.wine/config [Drive X] "Device" = "/dev/yyy".
> The appropriate action on that file ( read, write, set_file_pointer, ...)
> succeed according the the righte the user has on that
On 07 Oct 2003 11:28:51 +0200, you wrote:
> Hi,
> fixme:cdrom:CDROM_GetInterfaceInfo CD-ROM device (11, 0) not supported
>
> what it mean?
I see this as well. And it is a bug.
I just send in a proposed fix for it to wine-patches.
>
> this is my cd is (11, 0) and then?
> brw-rw1 moreno
1 - 100 of 101 matches
Mail list logo
