Subject: Re: dosdevices/c not present.. how is it created?
On 7/12/2011 11:30 AM, Roger Cruz wrote:
> I'm getting the following error when running Wine.
>
> Using the debugger, I think I found where the problem is:
>
> 2140 int fd = open( unix_name, O_RDONLY | O_DIRECT
ory, I can see that the c: directory
> is not there
[snip]
> How does that c: directory get created and by whom? I have deleted the
> $WINEPREFIX several times already to no avail.
dlls/ntdll/server.c:774
/* create the drive symlinks */
mkdir( "drive_c", 0777 )
ound where the problem is:
2140 int fd = open( unix_name, O_RDONLY | O_DIRECTORY );
(gdb) p unix_name
$25 = 0x4040b2e8 "/data/winehome/dosdevices/c:"
(gdb) n
2141 if (fd != -1)
(gdb) p fd
$26 = -1
(gdb) where
#0 find_file_in_dir (unix_name=0x4040b2e8 "/dat
a user is having trouble because the symlinks in ~/.wine/dosdevices
>>> don't work when on a Samba share.
>
> In my opinion CIFS is unsuitable for such Unixy things as home
> directories.
That's certainly been the bias of Unix folks for a long time,
but Jeremy Allison
2009/6/22 Dan Kegel :
> On Sun, Jun 21, 2009 at 7:25 PM, Dan Kegel wrote:
>> According to
>> http://groups.google.com/group/Google-Labs-Picasa-for-Linux/browse_thread/thread/9b0c746965d34f73
>> a user is having trouble because the symlinks in ~/.wine/dosdevices
>> don&#
On Sun, Jun 21, 2009 at 7:25 PM, Dan Kegel wrote:
> According to
> http://groups.google.com/group/Google-Labs-Picasa-for-Linux/browse_thread/thread/9b0c746965d34f73
> a user is having trouble because the symlinks in ~/.wine/dosdevices
> don't work when on a Samba share.
>
&
According to
http://groups.google.com/group/Google-Labs-Picasa-for-Linux/browse_thread/thread/9b0c746965d34f73
a user is having trouble because the symlinks in ~/.wine/dosdevices
don't work when on a Samba share.
It's unfortunate at this late date to realize that one
of the key choices
Wednesday, June 7, 2006, 9:03:43 AM, Konstantin Petrov wrote:
> changed test for function FindFirstFileA to find dosdevices.
> As function FindFirstFile must accept such paths as
> "c:\\windows\\win.ini"
> "c:\\NUL",
> "c:\\COM1",
> "c:\\LPT1&
Konstantin Petrov wrote:
(Patch Edited)
There were the problem while I advert to dosdevices through WINE. I made the
test (Windows vs Wine), which shows that in Windows there are available
dosdevices-files (such as NUL, COM1, COM2,.., LPT1, ..), and in Wine aren't.
The characteristic pro
Robert Lunnon <[EMAIL PROTECTED]> writes:
> Assuming this works, you say that other places load files cia a dos drive
> (and
> I see a mkdir across this link too) is there a key place to put the resolving
> code to catch these accesses too ?
Do functions like mkdir really fail on these too? I
On Friday 21 April 2006 03:35, Alexandre Julliard wrote:
> Robert Lunnon <[EMAIL PROTECTED]> writes:
> > This is the approach I took before but for some reason you didn't accept
> > the patch in process.c related to starting unix lib type applications.
> > The work-around was to change to the lib
Robert Lunnon <[EMAIL PROTECTED]> writes:
> This is the approach I took before but for some reason you didn't accept the
> patch in process.c related to starting unix lib type applications. The
> work-around was to change to the lib directory locate the pwd chdir back,
> then start the lib usi
On Wednesday 19 April 2006 04:26, Alexandre Julliard wrote:
> Robert Lunnon <[EMAIL PROTECTED]> writes:
> > All,
> > I am having some considerable problems dealing with a simple issue.
> > In .wine/dosdevices, devices are listed followed by a colon like in dos.
> >
Robert Lunnon <[EMAIL PROTECTED]> writes:
> All,
> I am having some considerable problems dealing with a simple issue.
> In .wine/dosdevices, devices are listed followed by a colon like in dos. This
> makes perfect sense except that the colon is often used in UNIX to separat
On Tue, 18 Apr 2006 22:38:11 +1000
Robert Lunnon <[EMAIL PROTECTED]> wrote:
> All,
> I am having some considerable problems dealing with a simple issue.
> In .wine/dosdevices, devices are listed followed by a colon like in dos. This
> makes perfect sense except that the colo
All,
I am having some considerable problems dealing with a simple issue.
In .wine/dosdevices, devices are listed followed by a colon like in dos. This
makes perfect sense except that the colon is often used in UNIX to separate
elements of a path description and has special meaning tto some
Sunday, November 13, 2005, 6:35:54 PM, Peter Berg Larsen wrote:
> and do not have
> B)
> /home/pebl/.wine/dosdevices > ls -l
> total 0
> lrwxrwxrwx 1 pebl pebl 10 Nov 10 17:21 c: -> /mnt/windows/
>
> A implies that I cannot run programs installed under windows. B impl
d
"on" or "installed on")
> You program looking for "c:\Program Files\". That means "Program Files"
> directory on drive c: For wine (in default configuration) c: drive means
> ~/.wine/drive_c. Or more precisely where ~/.wine/dosdevices/c: points
> to
Am Sonntag, den 13.11.2005, 23:53 +0100 schrieb Peter Berg Larsen:
> Ah, ah. This is where I complete fail in my understanding. I had the idea
> that wine was able to run any window program (modulo registry etc.) no
> matter how I did the install.
This is TRUE, but that depends on the Program!
e/drive_c. Or more precisely where ~/.wine/dosdevices/c: points to.
> with; wine does not support running a program installed under
> /mnt/windows/ I would only had to ask once.
Of corse it does. If you can make program look for it's files somewhere else.
Because that's what you are
On Sun, 13 Nov 2005, Vitaliy Margolen wrote:
> That's you who can't read. I will repeat again: "~/.wine/dosdevices/c: points
> to
> what windows programs will see as a "c:" drive."
> Please read it again (if that's what it takes). Then thing
On Sun, 13 Nov 2005, Michael Druing wrote:
> If you don't want to install the game in wine but rather use an existing
> Windows installation you should either copy and/or link to your existing
> installation, but bear in mind that this might - as others have already
> pointed out - break your ins
everyone is telling you.
dosdevices/c: has NOTHING to do with your true windows installation, it
would be just the same if there was no windows installation on that
machine.
Wine is not designed to run software installed on a windows operating
system from Linux. You need to install your sof
ing the idear behind how devices are suppose to work.
>
> > >> If any of that documentation is unclear, let me know and I'll rewrite
> > >> it to make it better.
>
> > > I have read this, but is does not explain what the behavour is/suppose to
> > &g
Hi,
> Hmm, you are the third to answer me, but none so far have answered my
> questions.
>
> >>>
> Are files first looked up in dosdevices/c: and the in
> /mnt/windows/ if
> not found?
>
> The reason I ask is that icewind dale on /mnt/windows/ does a
>
d how devices are suppose to work.
>> >> If any of that documentation is unclear, let me know and I'll rewrite
>> >> it to make it better.
>> > I have read this, but is does not explain what the behavour is/suppose to
>> > be when there exists an /m
unclear, let me know and I'll rewrite
> >> it to make it better.
> > I have read this, but is does not explain what the behavour is/suppose to
> > be when there exists an /mnt/windows. dosdevices/c: always points to
> > ../drive_c. So the doc does not answer the q
it better.
> I have read this, but is does not explain what the behavour is/suppose to
> be when there exists an /mnt/windows. dosdevices/c: always points to
> ../drive_c. So the doc does not answer the questions I asked:
>
> But how are dosdevices/c: related to my /mnt/windows? Are f
to
be when there exists an /mnt/windows. dosdevices/c: always points to
../drive_c. So the doc does not answer the questions I asked:
>>
But how are dosdevices/c: related to my /mnt/windows? Are files first
looked up in dosdevices/c: and the in /mnt/windows/ if not found?
The reason I ask
/config-wine-main#AEN265
If any of that documentation is unclear, let me know and I'll rewrite
it to make it better.
-Brian
I usually cd to ~/.wine/dosdevices
ln -s /mnt/dvd h:
to add my dvd burner to install stuff from.
bash-3.00#ls -ail
total 8
410764 drwxr-xr-x 2 wino users
On 11/13/05, Peter Berg Larsen <[EMAIL PROTECTED]> wrote:
>
> I am missing the idear behind how devices are suppose to work.
Wine User Guide section on that:
http://www.winehq.com/site/docs/wineusr-guide/config-wine-main#AEN265
If any of that documentation is unclear, let me know and I'll rewrit
behind how devices are suppose to work.
>
>>From the wiki it seems that the dosdevices/c: is use when installing a
>program under wine. But how are dosdevices/c: related to my /mnt/windows?
>Are files first looked up in dosdevices/c: and the in /mnt/windows/ if
>not found?
I am missing the idear behind how devices are suppose to work.
>From the wiki it seems that the dosdevices/c: is use when installing a
program under wine. But how are dosdevices/c: related to my /mnt/windows?
Are files first looked up in dosdevices/c: and the in /mnt/windows/ if
not fo
Hi,
On Fri, Oct 28, 2005 at 01:44:22AM +0200, [EMAIL PROTECTED] wrote:
> Disappointing start to 0.9 , I wonder what new user would make of that.
I really should have written a mail that I thought that the 0.9 release
notification was *much* too short.
I would have expected this to be in the realms
Thursday, October 27, 2005, 5:44:22 PM, [EMAIL PROTECTED] wrote:
> Hi,
> just getting into a fresh installation with 0.9
> ran up winecfg and tried to add a device for my dvd burner.
> editing the device name is unusable. No cursor , then after a first
> character is entered the edit seems to
I noticed this as well last night when I was testing some Windows
programs for compatibility. I'm glad Wino mentioned it here, because I
almost forgot.
I went into the dosdevices directory and set up the links manually,
because it's real hard to get non-fubar'd results with w
Hi,
just getting into a fresh installation with 0.9
ran up winecfg and tried to add a device for my dvd burner.
editing the device name is unusable. No cursor , then after a first
character is entered the edit seems to jump to insert mode and puts the
cursor at the begingin of the line. The
Hello,
I found an email by Fergal Daly
(http://www.mail-archive.com/[EMAIL PROTECTED]/msg08815.html) which
kind of patches configuring.sgml to document dosdevices/unc.
I transformed it into a proper patch for configuring.sgml
Tobias
Index: configuring.sgml
28 -
@@ -963,7 +963,8 @@
Windows shares can are mapped into the unc/
directory so anything trying to access
\\machinename\some\dir\and\file will look in
- ~/.wine/dosdevices/unc/machinename/some/dir/and/file.
+ ~/.wine/dosdevices/unc/machinename/some/dir/
39 matches
Mail list logo
