I'm very confused as usual. I have an NTFS/Linux dual boot. I usually run from kde. If I understand correctly, wine, when it runs a program will 1. see it ask for a function in a dll 2. check up in the config file for that dll and note if native or built-in or nothing has been noted. 3. from there, it will either use built-in, or native file in the order written. So, if I install and app, "blah", I need to: 1. Figure out all dlls that are needed. 2. Make sure that I have all those needed dlls in the .wine/.../windows/system (but not sys32?) folder. If necessary, I need to dig it up from my winnt directory and copy it over to the .wine directory. 3. Go to the config file and make sure that all the dlls are in it. If necessary, say some of the dlls are built-in and others are native for this app. I figure this last part has some points that I'm missing right now, but I need to get the main points straight. 4. If not in the config file, I need to add them in. I'm fairly sure I won't need to ever add a built-in dll, but will need to add some of the native files. What if the dll resides in the Program Files folder? I believe I still have to put it into the config file. Right now, most of the apps that I have attempted to install are: 1. Failed attempts. Dies dead on install. 2. Installed or failed in installed and got working anyhow but with major problems that render them unusable. 3. Success or partial success but with later problems coming up that renders them unusable. One of this last worked partially in gnome as it used to in kde. It now comes up in kde as a maximized as a very small window and then dies. By the way, I downloaded winetools, but I don't want to use any of the programs that it is supposed to set up. Neither do I know what that bit about the base directory means and see no reason for having one if I won't be using any of the other programs. Am I missing even more than I suspect? blessings, David L. Smith
Most of the DLLs that Wine uses are stored in a global shared directory for the system, and not in the fake windows drive Wine creates. If Wine can't find them locally, Wine will look in its own folder. Simply try installing and running the app without doing anything special before mucking around with non-Wine DLLs. -Scott Ritchie On Sat, 2005-01-01 at 03:03 -0600, David L. Smith wrote:> I'm very confused as usual. > > I have an NTFS/Linux dual boot. I usually run from kde. > If I understand correctly, wine, when it runs a program will > 1. see it ask for a function in a dll > 2. check up in the config file for that dll and note if native or built-in or > nothing has been noted. > 3. from there, it will either use built-in, or native file in the order > written. > > So, if I install and app, "blah", I need to: > 1. Figure out all dlls that are needed. > 2. Make sure that I have all those needed dlls in the .wine/.../windows/system > (but not sys32?) folder. If necessary, I need to dig it up from my winnt > directory and copy it over to the .wine directory. > 3. Go to the config file and make sure that all the dlls are in it. If > necessary, say some of the dlls are built-in and others are native for this > app. I figure this last part has some points that I'm missing right now, but > I need to get the main points straight. > 4. If not in the config file, I need to add them in. I'm fairly sure I won't > need to ever add a built-in dll, but will need to add some of the native > files.> blessings, > David L. Smith > _______________________________________________ > wine-users mailing list > wine-users@winehq.org > http://www.winehq.org/mailman/listinfo/wine-users
David L. Smith wrote:> I'm very confused as usual. > > I have an NTFS/Linux dual boot. I usually run from kde. > If I understand correctly, wine, when it runs a program will > 1. see it ask for a function in a dll > 2. check up in the config file for that dll and note if native or built-in or > nothing has been noted. > 3. from there, it will either use built-in, or native file in the order > written. > > So, if I install and app, "blah", I need to: > ...I think you are trying to make this way too complicated. In general, you should never care what DLLs the application uses. In most cases, Wine will work just fine without any config file at all. This assumes you are using a current version of Wine, and that is something that you should be doing.> > What if the dll resides in the Program Files folder? I believe I still have to > put it into the config file.You should not be putting any DLL entries in the config file, except in certain special cases. Trying to figure out whether a DLL override is needed for a particular application is somewhat of a black art. But the general method is, if an application breaks at about the same time a "fixme" method is printed out, then you might want to try a native version of that particular DLL. You should make DLL overrides application specific; that is with entries like: [AppDefaults\\dcom98.exe\\DllOverrides] "ole32" = "native" The one exception might be that in general, a native Windows msvcrt.dll is almost always better than the Wine version, so go ahead and install that DLL and add a global override for it.> > Right now, most of the apps that I have attempted to install are: > 1. Failed attempts. Dies dead on install. > 2. Installed or failed in installed and got working anyhow but with major > problems that render them unusable. > 3. Success or partial success but with later problems coming up that renders > them unusable. One of this last worked partially in gnome as it used to in > kde. It now comes up in kde as a maximized as a very small window and then > dies.With most apps? What apps are you trying to install? There is currently a significant amount of work going on with installers. Installers tend to be the most difficult thing for Wine to handle. Use the latest Wine version if you are not already.
Am Sa, Jan 01, 2005 at 03:03:40 -0600 schrieb David L. Smith:> By the way, I downloaded winetools, but I don't want to use any of the > programs that it is supposed to set up. Neither do I know what that bit about > the base directory means and see no reason for having one if I won't be using > any of the other programs. Am I missing even more than I suspect?Yes. There is a menu entry called "Base setup". You should definitely go through this step. It installs DCOM98 and IE6 which both bring many DLLs later needed for setup and other software. Also the config installed during this process is a good start for all other attempts. After the Base setup you might want to update the Windows Installer found in the menu called "Install Windows system software". After that you can try to install the software you want to use. Regards Joachim -- "Never touch a running system! Never run a touching system? Never run a touchy system!!!"
Duane Clark wrote:>I think you are trying to make this way too complicated. In general, youshould never care what DLLs the application uses I agree. But only one of the apps that I have installed before winetools worked. Thank you Stefan for your good info. I'm glad to see that there was a ray of truth in my usual dark understanding. And for Joachim: WineTools worked, and I figure because of the dlls it brought in, so did wine. Dunno, of course. I was able to install one thing that I wasn't able to install before. I'll continue installing other things when I can. Thanks. Two bellyachins, though. One is that the installation of IE failed. I received two messages about a wineserver laying around for 600 seconds. I was afraid to do anything about the first, but eventually clicked the close box button. When it came up again I hit the okay button. At that time I got a message that the installation failed. People like me tend to panic, but I somehow managed not to stop the download (one and a half hours if my guess at the German was correct). Later ran install again and somehow pressed the right buttons and it worked. Assuming that message box shuts off the wineserver & installation if one presses the okay button, why not add "don't click 'okay' if the installation is in a long download." And for the second growl, I don't want to hurt your feelings, sir, but putting IE on my linux feels like giving someone AIDS to cure their allergies. I did it, but I'll be looking over my shoulder a lot. Finally, I was not able to run another install. pstree shows a sleeping wine-preloader, which winetools marked as defunct but wouldn't kill it. I cannot kill the thing. Gave it kill 15, 9 and waved a clove of garlic but it still wouldn't go away. Winetools wouldn't kill it either. (Not blaming wineTools - assuming wine had the problem) Am I: 1. Missing/forgetting something simple in the manuals? 2. Not using the wrong kill signal or garlic variety? 3. Needing to reboot linux? 4. Don't worry about it? -- blessings David L. Smith