When I start a windows application using wine (currently wine-20041019) on RedHat 9, I receive the following: [jmmckee@server jmmckee]$ wine sol Please use the registry key HKEY_CURRENT_CONFIG\Software\Fonts\LogPixels to set the screen resolution and remove the "Resolution" entry in the config file err:wave:OSS_WaveOutInit /dev/mixer1: No such device err:wave:OSS_WaveInInit /dev/mixer1: No such device I tried wine regedit to look at HKEY_CURRENT_CONFIG. The display clearly shows a plus sign to the left. But, when I click on it, it does not expand. The other keys do expand. So, this actually is two questions: 1) Why does it show as if it could be expanded, but does not expand? Are other keys missing? I have done wine --version. 2) What is an appropriate entry for LogPixels The two err: above has me totally confused. I do not know where to even being to look to resolve the messages. Thanks for assistance. John McKee
John McKee wrote:> When I start a windows application using wine (currently wine-20041019) > on RedHat 9, I receive the following: > > [jmmckee@server jmmckee]$ wine sol > Please use the registry key HKEY_CURRENT_CONFIG\Software\Fonts\LogPixels > to set the screen resolution and remove the "Resolution" entry in the > config fileTo get rid of this message, just go into your ~/.wine/config and delete the line that looks like: "Resolution" = "96" You don't really need any registry entry.> err:wave:OSS_WaveOutInit /dev/mixer1: No such device > err:wave:OSS_WaveInInit /dev/mixer1: No such deviceAre you trying to do something with audio that is not working? Otherwise, you can probably safely ignore the messages.
(Please respond to the list, rather than only to me) John McKee wrote:> > ... > I had an older version of wine working. I think it was wine-20040615, but > can't recall. I was able to (partially) use CompuServe software from a few > years ago. The ole component didn't work, but I was able to check mail. > Sound worked at that point as well, as I received a voice message at the > start and end of the session (the famous "You have mail", as well). > > After upgrading to wine20041019, I cannot run that coftware anymore. I > receive errors about missing DLLs (see below). Do I have to do something > beyond copying Windows DLLs to Windows\System and Windows\System32?Normally that is all that is needed for the DLLs listed below.> Were DLLs that I had previously copied replaced during the upgrade? > > Line 105: Malformed value name '"CS3COR.DLL" 'native, builtin"'Take a close look at your ~/.wine/config file. There is apparently a typo somewhere.> err:module:import_dll Library MFC42.DLL (which is needed by > L"C:\\CServe\\CS3\\CS3COR.DLL") not foundIf you have those installed in the Windows directory, then maybe whatever is messed up in the config file is somehow causing the problem.
> > > to set the screen resolution and remove the "Resolution" entry in the > > > config file > > > err:wave:OSS_WaveOutInit /dev/mixer1: No such device > > > err:wave:OSS_WaveInInit /dev/mixer1: No such device > > > > > > > > > I tried wine regedit to look at HKEY_CURRENT_CONFIG. The display > > > clearly shows a plus sign to the left. But, when I click on it, it > > > does not expand. The other keys do expand. So, this actually is two > > > questions: > > > 1) Why does it show as if it could be expanded, but does not expand? > > > Are other keys missing? I have done wine --version. > > > > > > 2) What is an appropriate entry for LogPixels > > > > just look in your config file in the resolution section and copy the > > value to the registry (96 is the default value, i guess). i usually open > > the registry with a text editor to change the wine settings and use > > regedit only to import windows registry files. i don't know wether > > regedit works for wine specific entries. > > > > to get rid of the last two errors you should look into your config file > > and choose the correct sound device. (search for "wineoss") > > > > cu, > > > > Stefan > > I appreciate your prompt response. I must be missing something, or > misunderstanding. By "registry", are you referring to ~/.wine/system.reg? > If not, what is the name of the file and where (usually) is it located?i looked in my .reg files (they are in ~/.wine) and found no resolution entry so i think it is save to just delete it in the config file.> > And, as to the two err: I am receiving, below is the section from my > ~/.wine/config file. Sound work fine under Linux. Where else do I need to > be looking? > > > "Drivers" = "wineoss.drv" ; default for most common configurations > ;"Drivers" = "winearts.drv" ; for KDE > ;"Drivers" = "winealsa.drv" ; for ALSA users > ;"Drivers" = "winejack.drv" ; for Jack sound server > ;"Drivers" = "winenas.drv" ; for NAS sound system > ;"Drivers" = "wineaudioio.drv" ; for Solaris machines > ;"Drivers" = "" ; to disable sound > "WaveMapper" = "msacm.drv" > "MidiMapper" = "midimap.drv"i would try to comment the first line (;"Drivers" = "wineoss.drv"). if you need sound in wine you must uncomment the line with the sound driver that is installed on your system.> > I apologize for what seem to me as naive questions.no problem, hope it helps.
Duane Clark wrote:> John McKee wrote: > > Duane Clark wrote: > > > > > >>(Please respond to the list, rather than only to me) > >> > >>John McKee wrote: > >> ... > >>>err:module:import_dll Library MFC42.DLL (which is needed by > >>>L"C:\\CServe\\CS3\\CS3COR.DLL") not found > >> > >>If you have those installed in the Windows directory, then maybe > >>whatever is messed up in the config file is somehow causing the problem. > > > > ... > > So, I tried running the app again. CS3CORR.DLL was never in either > > Windows\System or Windows\System32. The installer put it (along with other > > custom DLLs) into the application directory. > > > > You are misinterpreting the message. CS3CORR was found ok. But CS3CORR > is trying to use MFC42, and that is the one not being found (along with > several others). It is MFC42 and company that you need installed in the > windows directory. > > CS3CORR can be left in the application directory, and nothing needs to > be added to the config file to find it. In general, if there is not a > Wine equivalent for a DLL, then Wine will expect to find a real windows > DLL, and will print the above message if it cannot. > >I must still have some configuration issue. When I try to run the application now, I get this: [jmmckee@server CS3]$ wine CS3 err:module:import_dll Library MFC42.DLL (which is needed by L"C:\\CServe\\CS3\\CS3COR.DLL") not found err:module:import_dll Library MSVCIRT.dll (which is needed by L"C:\\CServe\\CS3\\CS3COR.DLL") not found err:module:import_dll Library CS3COR.DLL (which is needed by L"C:\\CServe\\CS3\\CS3.exe") not found err:module:import_dll Library MFC42.DLL (which is needed by L"C:\\CServe\\CS3\\CS3.exe") not found err:module:import_dll Library MSVCIRT.dll (which is needed by L"C:\\CServe\\CS3\\CS3.exe") not found err:module:LdrInitializeThunk Main exe initialization for L"C:\\CServe\\CS3\\CS3.exe" failed, status c0000135 But, here is directory showing info on MFC42: [jmmckee@server System]$ pwd /home/home/wine/c/Windows/System [jmmckee@server System]$ ls -l |grep [Mm][Ff][Cc] -rw-r--r-- 1 jmmckee users 940304 Nov 20 21:11 mfc42.dll -rw-r--r-- 1 jmmckee users 995383 Sep 26 1998 MFC42.DLL and in ~/.wine.config, I have this: "mfc42" = "native, builtin" So what do I need, and where should it be? In the above case, there are two versions of MFC42. Is wine getting confused? Which one should I keep, and should it stay in windows\system? Is something else potentially wrong? Thanks for assistance. John McKee
<snip>> > I must still have some configuration issue. When I try to run the > application now, I get this: > > [jmmckee@server CS3]$ wine CS3 > err:module:import_dll Library MFC42.DLL (which is needed by > L"C:\\CServe\\CS3\\CS3COR.DLL") not found > err:module:import_dll Library MSVCIRT.dll (which is needed by > L"C:\\CServe\\CS3\\CS3COR.DLL") not found > err:module:import_dll Library CS3COR.DLL (which is needed by > L"C:\\CServe\\CS3\\CS3.exe") not found > err:module:import_dll Library MFC42.DLL (which is needed by > L"C:\\CServe\\CS3\\CS3.exe") not found > err:module:import_dll Library MSVCIRT.dll (which is needed by > L"C:\\CServe\\CS3\\CS3.exe") not found > err:module:LdrInitializeThunk Main exe initialization for > L"C:\\CServe\\CS3\\CS3.exe" failed, status c0000135 > > > But, here is directory showing info on MFC42: > > [jmmckee@server System]$ pwd > /home/home/wine/c/Windows/System > [jmmckee@server System]$ ls -l |grep [Mm][Ff][Cc] > -rw-r--r-- 1 jmmckee users 940304 Nov 20 21:11 mfc42.dll > -rw-r--r-- 1 jmmckee users 995383 Sep 26 1998 MFC42.DLL > > and in ~/.wine.config, I have this: > > "mfc42" = "native, builtin" > > > So what do I need, and where should it be? In the above case, there are > two versions of MFC42. Is wine getting confused? Which one should I keep, > and should it stay in windows\system?try to copy MFC42.dll, MSVCIRT.dll from your windows system to be sure you are using the corresponding version of these dlls. if you have any dlls of the same name (caseinsensitive!) in your wine windows/ system dir delete them.> > Is something else potentially wrong? > > Thanks for assistance. > > John McKee
John McKee wrote:> > ... > I must still have some configuration issue. When I try to run the application > now, I get this: > > [jmmckee@server CS3]$ wine CS3 > err:module:import_dll Library MFC42.DLL (which is needed by > L"C:\\CServe\\CS3\\CS3COR.DLL") not found > err:module:import_dll Library MSVCIRT.dll (which is needed by > L"C:\\CServe\\CS3\\CS3COR.DLL") not found > err:module:import_dll Library CS3COR.DLL (which is needed by > L"C:\\CServe\\CS3\\CS3.exe") not found > err:module:import_dll Library MFC42.DLL (which is needed by > L"C:\\CServe\\CS3\\CS3.exe") not found > err:module:import_dll Library MSVCIRT.dll (which is needed by > L"C:\\CServe\\CS3\\CS3.exe") not found > err:module:LdrInitializeThunk Main exe initialization for > L"C:\\CServe\\CS3\\CS3.exe" failed, status c0000135 > > > But, here is directory showing info on MFC42: > > [jmmckee@server System]$ pwd > /home/home/wine/c/Windows/System > [jmmckee@server System]$ ls -l |grep [Mm][Ff][Cc] > -rw-r--r-- 1 jmmckee users 940304 Nov 20 21:11 mfc42.dll > -rw-r--r-- 1 jmmckee users 995383 Sep 26 1998 MFC42.DLL >It is hard to say what is wrong; that should work, assuming /home/home/wine/c really is your Wine C: drive. You might want to post the output of ls -al ~/.wine/dosdevices , and grep winsysdir ~/.wine/*.reg Finally, try running WINEDEBUG=module,loaddll wine CS3 >& wine.log Then open wine.log in a text editor, and search for MFC42. There should be some lines describing the search for it. Post a group of lines around that section.
Stefan Munz wrote:> Am Sonntag, 21. November 2004 21:25 schrieb Duane Clark: > >>John McKee wrote: >> >>>Attached is the log segment, after running gzip. >> >>Well, something strange is going on, but so far I cannot figure out >>what. > > <snip> > > maybe this is too obvious but I run into the the same problem some time ago: > when you copy your windows dir from the windows drive, did you check that in > > /home/home/wine/c > > you have only one windows dir? i suspect (you can find this in the debug ouput > that you posted in some of the mails before) that wine made a "windows" dir > and you copied a "Windows" (capitalisation!). in that case you should merge > the real win dir into the one, wine created and delete it then. >That would certainly explain things. Yes, check for a duplicate Windows directory, and also a duplicate Windows/System directory.
----- Original Message ----- From: Duane Clark [mailto:dclark@akamail.com] Sent: 11/22/2004 10:03:11 AM To: wine-users@winehq.com Subject: Re: [Wine]Error with wine-20041019 Stefan Munz wrote:> Am Sonntag, 21. November 2004 21:25 schrieb Duane Clark: > >>John McKee wrote: >> >>>Attached is the log segment, after running gzip. >> >>Well, something strange is going on, but so far I cannot figure out >>what. > > <snip> > > maybe this is too obvious but I run into the the same problem some time ago: > when you copy your windows dir from the windows drive, did you check that in > > /home/home/wine/c > > you have only one windows dir? i suspect (you can find this in the debug ouput > that you posted in some of the mails before) that wine made a "windows" dir > and you copied a "Windows" (capitalisation!). in that case you should merge > the real win dir into the one, wine created and delete it then. >That would certainly explain things. Yes, check for a duplicate Windows directory, and also a duplicate Windows/System directory. I will check for this, probably won't be able to get to it before Friday. Thanks. I will let you know what I found.