Re: Question about ~/.wine/dosdevices/
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 implies > that wine is writing something (to registry whatever) to c: which will > brake windows. (Note: B is not my setup) Not necessarily. That implies that if a program depends on: - Some registry settings that it created during the install. - Hardcoded path to C:\Program Files\my_program\ - Created files in C:\window or C:\WINNT one can not copy this program from one computer to another computer. And that program have to be reinstalled in order to work. Also Wine is something that _emulates_ windows environment inside *nix system. Wine does not use nor requires any parts of an existent windows installation. Wine is designed that way so one can use programs written for windows working on *nix. With that said, you may call Wine dumb for not being able to find existent windows installation. But we calling it "Windows replacement". So all the cases when someone has an access to a partition with functioning windows mean nothing to Wine. > Plenty who have answered have stated B, but I do not see what this has to > do with wines ability to run a program installed under windows. You are correct, it doesn't. It's a program's inability to be copied. Wine, as well as a program might (and will) create/write/change/delete files under C:\Windows. This is dangerous on a working windows drive. While at any time you can remove ~/.wine dir and start with a clean "windows" environment, you have to reinstall whole windows if it brakes. > As it does not state on the wiki nor the docs that I must have installed > the program under wine to expect it to run, I expected wine to do clever Correct again. It is stated in the program's readme, that the program has to be installed. Vitaliy
RE: Question about ~/.wine/dosdevices/
WARNING: it is 3 in the night, and the better part of me said I should have got some sleep before answering. Am Sonntag, den 13.11.2005, 23:53 +0100 schrieb Peter Berg Larsen: >Use one Harddisk, install windows on "C:" and your Programs on "D:". >Add a second Harddisk with a Primary Partition (Drive-Letter has changed >from "D:" to "E:") and see, how many Programs are broken. Every program that uses absolute paths. > > But neither wiki or the docs said anything about this, which was why I > > asked. > Is the warning "Do not use your existing Windows installation as C: in > wine" gone? Properly not, but I do not see this a relevant to me or the question. More below. On Sun, 13 Nov 2005, Vitaliy Margolen wrote: > Can you run a program that you installed on wine in windows? I do not think there is a correlation between this and my questions as "Wine makes it possible to run Windows programs alongside any Unix-like operating system, particularly Linux.". Ms does not state the opposite. (I think is the word "alongside" I am reading wrong here; I would have used "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. Answer below. > > 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 doing. The path is hardcoded, so I cannot change the behaviour of the program. > And like I've mentioned before, please, don't run programs directly from > your windows drive. That won't make it any better. But that might brake > your windows. Hmm, no you said: > Please never point your c: drive to the real windows drive - that won't > help wine at all but it might brake your windows beyond repair. The difference to me is: A) do not /mnt/windows/program files/railroad tycoon 3 > wine rt3.exe 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 implies that wine is writing something (to registry whatever) to c: which will brake windows. (Note: B is not my setup) Plenty who have answered have stated B, but I do not see what this has to do with wines ability to run a program installed under windows. As it does not state on the wiki nor the docs that I must have installed the program under wine to expect it to run, I expected wine to do clever things to get it rigth. Like looking in both places or noticing the path of the exe. In either case I had a program that this "clever" mechanism did not worked for, and as I could find any thing clever part in wine I asked wine-devel and not wine-user. Peter
RE: Question about ~/.wine/dosdevices/
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! Use one Harddisk, install windows on "C:" and your Programs on "D:". Add a second Harddisk with a Primary Partition (Drive-Letter has changed from "D:" to "E:") and see, how many Programs are broken. > But neither wiki or the docs said anything about this, which was why I > asked. Is the warning "Do not use your existing Windows installation as C: in wine" gone? PS: This is related to "wine-users", not "wine-devel" -- By By ... ... Detlef
Re: Question about ~/.wine/dosdevices/
Sunday, November 13, 2005, 4:10:55 PM, Peter Berg Larsen wrote:
> The reason I ask is that icewind dale on /mnt/windows/ does a
> FindFirstFileA("C:/program...") which wine translates to dosdevice/c: and
> ofcause does not find anything. Am I suppose to make a link to where the
> program is installed, as if I had installed it with wine?
Can you run a program that you installed on wine in windows?
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.
> 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 doing.
And like I've mentioned before, please, don't run programs directly from your
windows drive. That won't make it any better. But that might brake your windows.
Vitaliy
Re: Question about ~/.wine/dosdevices/
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 about "what does c:
> drive or any other drive means on windows".
I read it and it only answered one of my questions which wasnt enough.
On Sun, 13 Nov 2005, [EMAIL PROTECTED] wrote:
> On Sun, 13 Nov 2005 23:04:14 +0100, Peter Berg Larsen <[EMAIL PROTECTED]>
> wrote:
> > Hmm, you are the third to answer me, but none so far have answered my
> > questions.
> That's because you have a preconceived idea of what the answer is
> supposed to be and you are not taking in what everyone is telling you.
Yes, that is half true. But had anyone answered all questions, like:
>>>
The reason I ask is that icewind dale on /mnt/windows/ does a
FindFirstFileA("C:/program...") which wine translates to dosdevice/c: and
ofcause does not find anything. Am I suppose to make a link to where the
program is installed, as if I had installed it with wine?
<<<
with; wine does not support running a program installed under
/mnt/windows/ I would only had to ask once.
Peter
RE: Question about ~/.wine/dosdevices/
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 installation on windows for some reason or another > and is generally not suggested. 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. You are saing "do not run a windows program unless you installed the program with wine"? (or atleast do not expect it to work). > Wine cannot guess where your existing windows partition is mounted. I saw three solution for that: A) It look at ~/.wine/c:/ and then in /mnt/windows/ B) Notices that the program started in a /mnt/windows/ path. C) If installed under /mnt/windows/ you must manual make some extra links. But neither wiki or the docs said anything about this, which was why I asked. Peter
Re: Question about ~/.wine/dosdevices/
On Sun, 13 Nov 2005 23:04:14 +0100, Peter Berg Larsen <[EMAIL PROTECTED]> wrote: Hmm, you are the third to answer me, but none so far have answered my questions. That's because you have a preconceived idea of what the answer is supposed to be and you are not taking in what 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 software using wine under linux to somewhere under .wine/drive_c (or whatever you chose to call it) Then any reference in the software to C:/Program files/blah blah/hick will point to something meaningful. HTH
Re: Question about ~/.wine/dosdevices/
Le dimanche 13 novembre 2005 à 23:04 +0100, Peter Berg Larsen a écrit :
> On Sun, 13 Nov 2005, Vitaliy Margolen wrote:
>
> > Sunday, November 13, 2005, 12:46:34 PM, Peter Berg Larsen wrote:
> > > On Sun, 13 Nov 2005, Brian Vincent wrote:
> > >> > I am missing 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
> > > 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
>
> > It doesn't. ~/.wine/dosdevices/c: points to what windows programs will see
> > as a
> > "c:" drive.
>
> > Please never point your c: drive to the real windows drive - that won't help
> > wine at all but it might brake your windows beyond repair.
>
> 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
> FindFirstFileA("C:/program...") which wine translates to dosdevice/c: and
> ofcause does not find anything. Am I suppose to make a link to where the
> program is installed, as if I had installed it with wine?
> <<<
>
> So I will try and refraise the questions:
>
> How does wine differentiate whether I have installed a program under
> ~/.wine/drive_c/ or under /mnt/windows/, when it does a
> FindFirstFileA("c:/Program Files/")? In the first case it should translate
> it to ~/.wine/dosdevices/c:/Program Files/ and in the latter
> ~/.wine/dosdevices/z:/mnt/windows/Program Files/?
If it searches for c:\program files then it will search it in
~/.wine/dosdevices/c:/Program Files/. ~/.wine/dosdevices/c: can then
point to anything you decided.
>
> If I have a program that does this, should I then make a link from
> ~/.wine/drice_c/Program Files/foo to /mnt/windows/Program Files/foo? (This
> will work with this program, but I have newer read such recommendation).
Yes you could do that.
--
Jonathan Ernst <[EMAIL PROTECTED]>
signature.asc
Description: Ceci est une partie de message numériquement signée
RE: Question about ~/.wine/dosdevices/
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
> FindFirstFileA("C:/program...") which wine translates to
> dosdevice/c: and
> ofcause does not find anything. Am I suppose to make a link
> to where the
> program is installed, as if I had installed it with wine?
> <<<
Wine uses a subdirectory under your home directory as its "C:\" drive. So if
you install Icewind Dale (or anything else) under wine, it will copy its
files to "~/.wine/dosdevices/c:/Program Files/...". When you start the
program and it does the FindFirstA("C:\Program Files\..."), wine correctly
translates that back to "~/.wine/dosdevices/c:/Program Files/..." for you,
so everything is fine.
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 installation on windows for some reason or another
and is generally not suggested.
>
> So I will try and refraise the questions:
>
> How does wine differentiate whether I have installed a program under
> ~/.wine/drive_c/ or under /mnt/windows/, when it does a
> FindFirstFileA("c:/Program Files/")? In the first case it
> should translate
> it to ~/.wine/dosdevices/c:/Program Files/ and in the latter
> ~/.wine/dosdevices/z:/mnt/windows/Program Files/?
Wine cannot guess where your existing windows partition is mounted.
>
> If I have a program that does this, should I then make a link from
> ~/.wine/drice_c/Program Files/foo to /mnt/windows/Program
> Files/foo? (This
> will work with this program, but I have newer read such
> recommendation).
This is one solution if you don't want to install the game under wine. It
should work for everything that doesn't change the registry or install
system-wide DLLs. Icewind Dale (and pretty much all other Infinity Engine
based games) should work with that kludge.
--Michael
P.S.: If you're a developer, you could check out the gemrb project at
Sourceforge, which tries to create an open-source crossplatform Infinity
Engine implementation, which one day will run Icewind Dale (and other games)
natively on Linux ;-)
Re: Question about ~/.wine/dosdevices/
Sunday, November 13, 2005, 3:04:14 PM, Peter Berg Larsen wrote: > On Sun, 13 Nov 2005, Vitaliy Margolen wrote: >> Sunday, November 13, 2005, 12:46:34 PM, Peter Berg Larsen wrote: >> > On Sun, 13 Nov 2005, Brian Vincent wrote: >> >> > I am missing 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 >> > 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 >> It doesn't. ~/.wine/dosdevices/c: points to what windows programs will see >> as a >> "c:" drive. >> Please never point your c: drive to the real windows drive - that won't help >> wine at all but it might brake your windows beyond repair. > Hmm, you are the third to answer me, but none so far have answered my > questions. 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 about "what does c: drive or any other drive means on windows". The rest of your Linux file system, is like "unpartitioned" space for windows programs. Can install a program on windows to unpartitioned space (or partition that is not assigned a drive or reparse point)? Vitaliy
Re: Question about ~/.wine/dosdevices/
On Sun, 13 Nov 2005, Vitaliy Margolen wrote:
> Sunday, November 13, 2005, 12:46:34 PM, Peter Berg Larsen wrote:
> > On Sun, 13 Nov 2005, Brian Vincent wrote:
> >> > I am missing 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
> > 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
> It doesn't. ~/.wine/dosdevices/c: points to what windows programs will see as
> a
> "c:" drive.
> Please never point your c: drive to the real windows drive - that won't help
> wine at all but it might brake your windows beyond repair.
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
FindFirstFileA("C:/program...") which wine translates to dosdevice/c: and
ofcause does not find anything. Am I suppose to make a link to where the
program is installed, as if I had installed it with wine?
<<<
So I will try and refraise the questions:
How does wine differentiate whether I have installed a program under
~/.wine/drive_c/ or under /mnt/windows/, when it does a
FindFirstFileA("c:/Program Files/")? In the first case it should translate
it to ~/.wine/dosdevices/c:/Program Files/ and in the latter
~/.wine/dosdevices/z:/mnt/windows/Program Files/?
If I have a program that does this, should I then make a link from
~/.wine/drice_c/Program Files/foo to /mnt/windows/Program Files/foo? (This
will work with this program, but I have newer read such recommendation).
Peter
Re: Question about ~/.wine/dosdevices/
Sunday, November 13, 2005, 12:46:34 PM, Peter Berg Larsen wrote: > On Sun, 13 Nov 2005, Brian Vincent wrote: >> > I am missing 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 > 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 It doesn't. ~/.wine/dosdevices/c: points to what windows programs will see as a "c:" drive. Please never point your c: drive to the real windows drive - that won't help wine at all but it might brake your windows beyond repair. Vitaliy
Re: Question about ~/.wine/dosdevices/
On Sun, 13 Nov 2005, Brian Vincent wrote:
> > I am missing 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
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 is that icewind dale on /mnt/windows/Program... does a
FindFirstFileA("C:/program...") which wine translates to dosdevice/c: and
ofcause does not find anything. Am I suppose to make a link to where the
program is installed, as if I had installed it with wine?
<<
When then program uses relative paths, wine translates it correctly to a
z: path.
Peter
Re: Question about ~/.wine/dosdevices/
On Sun, 13 Nov 2005 19:33:46 +0100, Brian Vincent <[EMAIL PROTECTED]> wrote: 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 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 4096 Nov 13 18:36 . 410726 drwxr-xr-x 9 wino users 4096 Nov 13 19:21 .. 410923 lrwxrwxrwx 1 wino users 16 Nov 13 18:30 c: -> /home/wino/.wine 410924 lrwxrwxrwx 1 wino users 11 Nov 13 18:30 d: -> /home/wino/ 410928 lrwxrwxrwx 1 wino users8 Nov 13 18:36 h: -> /mnt/dvd Does the example make it clearer? HTH
Re: Question about ~/.wine/dosdevices/
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 rewrite it to make it better. -Brian
Re: Question about ~/.wine/dosdevices/
I would not point my WINE C: to an actual Windows installation C: drive
- you're likely to end up with lots problems, if it works at all.
Run winecfg and create another drive letter pointing to /mnt/windows
(let's say 'h:' for this example). Use that drive letter if you have to
give your programs any paths. You can even create a batch script that
executes when you start Windows that uses the 'assign' command to mirror
h: to c: under Windows - in case an application stores full paths in an
INI in the program directory.
What I've always done on my home system is to install Windows on a
separate partition from Windows applications (and put data on a third
partition). By doing this, it was pretty easy for me to use the exact
same drive letters for the apps under both WINE and Windows.
-Jesse
Peter Berg Larsen wrote:
>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 found?
>
>The reason I ask is that icewind dale on /mnt/windows/ does a
>FindFirstFileA("C:/program...") which wine translates to dosdevice/c: and
>ofcause does not find anything. Am I suppose to make a link to where the
>program is installed, as if I had installed it with wine?
>
>Peter
>
>
>
>
>
>
