frustrated
2005-Aug-10 09:07 UTC
[Wine]config file (or lack thereof) question, turning off ttydrv
I am TRYING to use the most recent release of wine.
Am I correct to assume that there is no longer a .wine/config file?
Am I also correct to assume that all documentation still refers to the
.wine/config file, and gives NO F*CKING help about how to use the new
system?
If these two assumptions are correct, it seems to be a real stupid way to do
things. How is a new user EVER supposed to get this SH*T figured out??
I was trying to take care of the problem where my terminal spews crap like:
13369376): stub
fixme:ttydrv:TTYDRV_DC_StretchBlt (0x20c, 352, 0, 32, 32,
0x46c, 0, 0, 32, 64, 13369376): stub
fixme:ttydrv:TTYDRV_GetBitmapBits (0x478, 0x7be2698c, 32): stub
fixme:ttydrv:TTYDRV_GetBitmapBits (0x474, 0x7be269ac, 32):
stub
err:imagelist:ImageList_ReplaceIcon no color!
fixme:ttydrv:TTYDRV_DC_StretchBlt (0x1d4, 192, 0, 16, 16, 0x480, 0, 0, 16,
32, 13369376): stub
fixme:ttydrv:TTYDRV_DC_StretchBlt (0x1dc, 192, 0, 16, 16, 0x480, 0, 0, 16,
32, 13369376): stub
fixme:ttydrv:TTYDRV_GetBitmapBits (0x48c, 0x7be2698c, 128): stub
fixme:ttydrv:TTYDRV_GetBitmapBits (0x488, 0x7be26a0c, 128): stub
err:imagelist:ImageList_ReplaceIcon no color!
fixme:ttydrv:TTYDRV_DC_StretchBlt (0x204, 384, 0, 32, 32,
0x494, 0, 0, 32, 64, 13369376): stub
fixme:ttydrv:TTYDRV_DC_StretchBlt (0x20c, 384, 0, 32, 32, 0x494, 0, 0, 32,
64, 13369376): stub
fixme:ttydrv:TTYDRV_GetBitmapBits (0x4a0, 0x7be269f4, 32): stub
fixme:ttydrv:TTYDRV_GetBitmapBits (0x49c, 0x7be26a14, 32): stub
err:imagelist:ImageList_ReplaceIcon no color!
fixme:ttydrv:TTYDRV_DC_StretchBlt (0x1d4, 208, 0, 16, 16, 0x4a8, 0, 0, 16,
32, 13369376): stub
fixme:ttydrv:TTYDRV_DC_StretchBlt (0x1dc, 208, 0, 16, 16, 0x4a8, 0, 0, 16,
32, 13369376): stub
fixme:ttydrv:TTYDRV_GetBitmapBits (0x4b4, 0x7be269f4, 128): stub
fixme:ttydrv:TTYDRV_GetBitmapBits (0x4b0, 0x7be26a74, 128): stub
err:imagelist:ImageList_ReplaceIcon no color!
fixme:ttydrv:TTYDRV_DC_StretchBlt (0x204, 416, 0, 32, 32, 0x4bc, 0, 0, 32,
64, 13369376): stub
fixme:ttydrv:TTYDRV_DC_StretchBlt (0x20c, 416, 0, 32, 32, 0x4bc, 0, 0, 32,
64, 13369376): stub
fixme:ttydrv:TTYDRV_GetBitmapBits (0x4c8, 0x7be269f4, 32): stub
fixme:ttydrv:TTYDRV_GetBitmapBits (0x4c4, 0x7be26a14, 32): stub
fixme:ttydrv:TTYDRV_GetBitmapBits (0x4d0, 0x7be26aa4, 128): stub
fixme:ttydrv:TTYDRV_GetBitmapBits (0x4cc, 0x7be26b24,
128): stub
fixme:ttydrv:TTYDRV_GetBitmapBits (0x4d8, 0x7be26dbc, 32): stub
fixme:ttydrv:TTYDRV_GetBitmapBits (0x4d4, 0x7be26ddc, 32): stub
err:imagelist:ImageList_ReplaceIcon no color!
fixme:ttydrv:TTYDRV_DC_StretchBlt (0x1d4, 224, 0, 16, 16, 0x4e0, 0, 0, 16,
32, 13369376): stub
fixme:ttydrv:TTYDRV_DC_StretchBlt
(0x1dc, 224, 0, 16, 16, 0x4e0, 0, 0, 16, 32, 13369376): stub
fixme:ttydrv:TTYDRV_GetBitmapBits (0x4ec, 0x7be26dbc, 128): stub
fixme:ttydrv:TTYDRV_GetBitmapBits
(0x4e8, 0x7be26e3c, 128): stub
err:imagelist:ImageList_ReplaceIcon no color!
fixme:ttydrv:TTYDRV_DC_StretchBlt (0x204, 448, 0, 32, 32, 0x4f4, 0, 0, 32,
64, 13369376): stub
fixme:ttydrv:TTYDRV_DC_StretchBlt (0x20c, 448, 0, 32, 32, 0x4f4, 0, 0, 32,
64, 13369376): stub
fixme:ttydrv:TTYDRV_GetBitmapBits (0x500,
0x7be26e04, 32): stub
I found that I probably need to configure the x11drv, or tell wine to use
that instead of ttydrv, but how does one do that when the documentation
politely tells you that these settings are configured in ~/.wine/config?
It seems like development is going well, but you guys really don't care
about alienating new adoptees.
I've set up a lot of linux apps, including mythtv, but the obtuseness of the
documentation vs. the product is bewieldering.
TIA,
Frustrated
Walt Ogburn
2005-Aug-10 13:25 UTC
[Wine]config file (or lack thereof) question, turning off ttydrv
Hi Frustrated, I'm assuming that you compiled this yourself. If so, the issue is that you need to have the X11 headers installed when you compile wine (in some distros they come in a package named xf86-devel or xorg-devel or something like that). If these are missing when you run "./configure", you'll get a message at the end that tells you you'll only have ttydrv output. The config file (or lack thereof) shouldn't be involved at all. Try installing X11 headers and compile again. - Walter
Jonathan Ernst
2005-Aug-11 04:18 UTC
[Wine]Re: config file (or lack thereof) question, turning off ttydrv
Le mercredi 10 ao?t 2005 ? 10:07 -0400, frustrated a ?crit :> I am TRYING to use the most recent release of wine. > > Am I correct to assume that there is no longer a .wine/config file? > > Am I also correct to assume that all documentation still refers to the > .wine/config file, and gives NO F*CKING help about how to use the new > system?If you want to change your wine configuration (most apps doesn't need it), just run winecfg. -- Jonathan Ernst <Jonathan@ErnstFamily.ch> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://www.winehq.org/pipermail/wine-users/attachments/20050811/8c5aaa64/attachment.pgp
Dan Sawyer
2005-Aug-12 22:59 UTC
[Wine]config file (or lack thereof) question, turning off ttydrv
Thank you. frustrated wrote:> I am TRYING to use the most recent release of wine. > Am I correct to assume that there is no longer a .wine/config file? > Am I also correct to assume that all documentation still refers to the > .wine/config file, and gives NO F*CKING help about how to use the new > system? > If these two assumptions are correct, it seems to be a real stupid way > to do things. How is a new user EVER supposed to get this SH*T > figured out?? > I was trying to take care of the problem where my terminal spews crap > like: > 13369376): stub > fixme:ttydrv:TTYDRV_DC_StretchBlt (0x20c, 352, 0, 32, > 32, 0x46c, 0, 0, 32, 64, 13369376): stub > > fixme:ttydrv:TTYDRV_GetBitmapBits (0x478, 0x7be2698c, 32): stub > fixme:ttydrv:TTYDRV_GetBitmapBits (0x474, 0x7be269ac, > 32): stub > > err:imagelist:ImageList_ReplaceIcon no color! > > fixme:ttydrv:TTYDRV_DC_StretchBlt (0x1d4, 192, 0, 16, 16, 0x480, 0, 0, > 16, 32, 13369376): stub > > fixme:ttydrv:TTYDRV_DC_StretchBlt (0x1dc, 192, 0, 16, 16, 0x480, 0, 0, > 16, 32, 13369376): stub > fixme:ttydrv:TTYDRV_GetBitmapBits (0x48c, 0x7be2698c, 128): stub > > fixme:ttydrv:TTYDRV_GetBitmapBits (0x488, 0x7be26a0c, 128): stub > > err:imagelist:ImageList_ReplaceIcon no color! > fixme:ttydrv:TTYDRV_DC_StretchBlt (0x204, 384, 0, 32, > 32, 0x494, 0, 0, 32, 64, 13369376): stub > > fixme:ttydrv:TTYDRV_DC_StretchBlt (0x20c, 384, 0, 32, 32, 0x494, 0, 0, > 32, 64, 13369376): stub > > fixme:ttydrv:TTYDRV_GetBitmapBits (0x4a0, 0x7be269f4, 32): stub > > fixme:ttydrv:TTYDRV_GetBitmapBits (0x49c, 0x7be26a14, 32): stub > err:imagelist:ImageList_ReplaceIcon no color! > > fixme:ttydrv:TTYDRV_DC_StretchBlt (0x1d4, 208, 0, 16, 16, 0x4a8, 0, 0, > 16, 32, 13369376): stub > fixme:ttydrv:TTYDRV_DC_StretchBlt (0x1dc, 208, 0, 16, 16, 0x4a8, 0, > 0, 16, 32, 13369376): stub > > fixme:ttydrv:TTYDRV_GetBitmapBits (0x4b4, 0x7be269f4, 128): stub > fixme:ttydrv:TTYDRV_GetBitmapBits (0x4b0, 0x7be26a74, 128): stub > > err:imagelist:ImageList_ReplaceIcon no color! > > fixme:ttydrv:TTYDRV_DC_StretchBlt (0x204, 416, 0, 32, 32, 0x4bc, 0, 0, > 32, 64, 13369376): stub > > fixme:ttydrv:TTYDRV_DC_StretchBlt (0x20c, 416, 0, 32, 32, 0x4bc, 0, 0, > 32, 64, 13369376): stub > > fixme:ttydrv:TTYDRV_GetBitmapBits (0x4c8, 0x7be269f4, 32): stub > > fixme:ttydrv:TTYDRV_GetBitmapBits (0x4c4, 0x7be26a14, 32): stub > > fixme:ttydrv:TTYDRV_GetBitmapBits (0x4d0, 0x7be26aa4, 128): stub > fixme:ttydrv:TTYDRV_GetBitmapBits (0x4cc, > 0x7be26b24, 128): stub > > fixme:ttydrv:TTYDRV_GetBitmapBits (0x4d8, 0x7be26dbc, 32): stub > > fixme:ttydrv:TTYDRV_GetBitmapBits (0x4d4, 0x7be26ddc, 32): stub > > err:imagelist:ImageList_ReplaceIcon no color! > > fixme:ttydrv:TTYDRV_DC_StretchBlt (0x1d4, 224, 0, 16, 16, 0x4e0, 0, 0, > 16, 32, 13369376): stub > > fixme:ttydrv:TTYDRV_DC_StretchBlt (0x1dc, 224, 0, 16, 16, 0x4e0, 0, 0, > 16, 32, 13369376): stub > > fixme:ttydrv:TTYDRV_GetBitmapBits (0x4ec, 0x7be26dbc, 128): stub > > fixme:ttydrv:TTYDRV_GetBitmapBits (0x4e8, 0x7be26e3c, 128): stub > > err:imagelist:ImageList_ReplaceIcon no color! > > fixme:ttydrv:TTYDRV_DC_StretchBlt (0x204, 448, 0, 32, 32, 0x4f4, 0, 0, > 32, 64, 13369376): stub > > fixme:ttydrv:TTYDRV_DC_StretchBlt (0x20c, 448, 0, 32, 32, 0x4f4, 0, 0, > 32, 64, 13369376): stub > fixme:ttydrv:TTYDRV_GetBitmapBits (0x500, > 0x7be26e04, 32): stub > I found that I probably need to configure the x11drv, or tell wine to > use that instead of ttydrv, but how does one do that when the > documentation politely tells you that these settings are configured in > ~/.wine/config? > It seems like development is going well, but you guys really don't > care about alienating new adoptees. > I've set up a lot of linux apps, including mythtv, but the obtuseness > of the documentation vs. the product is bewieldering. > TIA, > Frustrated > > _______________________________________________ > wine-users mailing list > wine-users@winehq.org > http://www.winehq.org/mailman/listinfo/wine-users >
Jonathan Ernst
2005-Aug-13 08:43 UTC
[Wine]Re: config file (or lack thereof) question, turning off ttydrv
winecfg stores it's settings in the registry. You can edit every settings (including the ones that are not in winecfg) using regedit and going to HKEY_LOCAL_MACHINE/SOFTWARE/WINE or by editing it using a text editor (edit ~/.wine/user.reg). Le vendredi 12 ao?t 2005 ? 22:41 +0100, Liam Kurmos a ?crit :> Jonathan Ernst wrote: > > >Le mercredi 10 ao?t 2005 ? 10:07 -0400, frustrated a ?crit : > > > > > >>I am TRYING to use the most recent release of wine. > >> > >>Am I correct to assume that there is no longer a .wine/config file? > >> > >>Am I also correct to assume that all documentation still refers to the > >>.wine/config file, and gives NO F*CKING help about how to use the new > >>system? > >> > >> > > > > > > > i think your right. Still, can't complain; they're working hard to make > us free software. > > >If you want to change your wine configuration (most apps doesn't need > >it), just run winecfg. > > > > > > > do you know where winecfg saves it's settings? > I'm wondering if there's an editable config file somewhere with more > functionality, or if the settings are now all saved in some binary way.-- Jonathan Ernst <Jonathan@ErnstFamily.ch> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://www.winehq.org/pipermail/wine-users/attachments/20050813/8d689333/attachment.pgp
Jonathan Ernst
2005-Aug-14 08:14 UTC
[Wine]Re: config file (or lack thereof) question, turning off ttydrv
winecfg stores it's settings in the registry. You can edit every settings (including the ones that are not in winecfg) using regedit and going to HKEY_LOCAL_MACHINE/SOFTWARE/WINE or by editing it using a text editor (edit ~/.wine/user.reg). Le vendredi 12 ao?t 2005 ? 22:41 +0100, Liam Kurmos a ?crit :> Jonathan Ernst wrote: > > >Le mercredi 10 ao?t 2005 ? 10:07 -0400, frustrated a ?crit : > > > > > >>I am TRYING to use the most recent release of wine. > >> > >>Am I correct to assume that there is no longer a .wine/config file? > >> > >>Am I also correct to assume that all documentation still refers to the > >>.wine/config file, and gives NO F*CKING help about how to use the new > >>system? > >> > >> > > > > > > > i think your right. Still, can't complain; they're working hard to make > us free software. > > >If you want to change your wine configuration (most apps doesn't need > >it), just run winecfg. > > > > > > > do you know where winecfg saves it's settings? > I'm wondering if there's an editable config file somewhere with more > functionality, or if the settings are now all saved in some binary way.-- Jonathan Ernst <Jonathan@ErnstFamily.ch> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://www.winehq.org/pipermail/wine-users/attachments/20050814/a4762562/attachment.pgp