August 2004 - Wine-Devel - list.winehq.org

Re: config converting problem

by Henning Gerhardt

Hillo Vincent, your wrote: >If you want to fix it, the simplest way would be to create the following >symlinks in ~/.wine/dosdevices: > >ln -s ../fake_windows c: >ln -s /home/julian y: I get him the same advice and it works now. Regards, Henning

Aug. 11, 2004

Re: USB?

by Aric Stewart

Right, that is the theory but something else must be happening also. For example with the iPod (what i am concentrating on) the vendor id is 0x05ac which somehow translates to VEN_APPLE and the product id of 0x1201 somehow translates to PROD_IPOD however i cannot find any inf file or registry key that would show that transition. -aric Rolf Kalbermatter wrote: > Aric Stewart wrote: > > >>I do have some difficulty figuring out how win2k is translating vender >>and product ids into class and interface guids. The documentation >>reports that they look them up in inf files, however i am finding that >>not to be true. I am suspecting that some may be hardcoded in the usb >>support somewhere. > > > Wouldn't that be something which would be put in the registry somehow > for the well known IDs and for the rest I really assume the device > detection routine does check for all .inf files it finds on the devices > currently configured to be searched. If you look at PCI and USB inf > files you will notice that the manufacturer and device ID are actually > encoded in the key names which are to be added to the registry. That > encoding does not always seem to be equally consistent, I've seen at > least two different types, but it is obviously there. > > One entry for instance for the Logitec PageScanner would be > > %USB\VID_046D&PID_040f.DeviceDesc%=Model.PageScan_USB,USB\VID_046D&PID_040f > > USB\VID_046D&PID_040f.DeviceDesc="Storm Technology - Logitech PageScan USB" > > This is partly extracted from a logiscan.inf file on my W2K system. > > Rolf Kalbermatter > > >

Aug. 11, 2004

Re: config converting problem

by Rick Romero

On Wed, 2004-08-11 at 08:50, Mike Hearn wrote: > > You could have > > > > c: = ~/.wine/c_drive > > c:\My Documents\ = ~/Documents > > c:\Program Files\ = ~/Windows Progs > > d: = /mnt/cdrom > > > > Then wiping your ~/.wine would preserve your files, and with those apps > > that don't require registry settings would just work without a reinstall > > (Pegasus Mail is a good example). > > I think it would be better to figure out a way to do upgrades better. > Also when we change something, it seems we need to massively increase > the amount of time the old way is still valid for. The problem of being > installing ancient distros then upgrading won't go away anytime soon. I guess I was thinking more along the lines of a Wine reinstall to fix 'Windows' problems, not necessarily Wine upgrades. Just something else to think about :) -- -- Rick Romero IT Manager Valeo, Inc. ph: 262.695.4841 Sussex, WI. fax: 262.695.4850 Rick(a)valeoinc.com

Aug. 11, 2004

Re: config converting problem

by Marcus Meissner

On Wed, Aug 11, 2004 at 09:06:56AM -0400, Vincent Béron wrote: > Le mer 11/08/2004 à 08:38, Mike Hearn a écrit : > > > If you want to fix it, the simplest way would be to create the following > > > symlinks in ~/.wine/dosdevices: > > > > > > ln -s ../fake_windows c: > > > ln -s /home/julian y: > > > > Or to delete ~/.wine > > And lose fake_windows???? > > > > > I'm not sure what to do about this, except maybe to add back in support > > for ${HOME} style vars. It's clear that people are "using" (at least, > > installing) much older versions than we anticipated. > > > > The problem comes when upgrading from an old version (still supporting > ${HOME}) to a newer version (supporting either %HOME% or dosdevices). > > The older version, by itself, still works correctly. On SUSE: mv away the fake_windows directory (mv ~/.wine ~/.wine.old). run wineprefixcreate, it will create a new setup. Copy over the old tree. cp -a ~/.wine.old/fake_windows/* ~/.wine/fake_windows/ ... You might want to copy over the registries (system.reg and user.reg) too. Ciao, Marcus

Aug. 11, 2004

Re: winedbg doesn't find source files

by Saulius Krasuckas

On Wed, 11 Aug 2004, Mike Hearn wrote: > > The original message had this line: > > fixme:dbghelp:elf_load_debug_info Unsupported Dwarf2 information > > > > So I suspect your Wine is compiled with Dwarf2 debug symbols rather than > > stabs+. Which gcc version was used? > > Yep but I see this problem even without that fixme, so I think it's > generic ... Does this mean no developers are able to perform human-understandable stepping and nexting at winedbg prompt in some latest Wine versions?

Aug. 11, 2004

Re: config converting problem

by Mike Hearn

> You could have > > c: = ~/.wine/c_drive > c:\My Documents\ = ~/Documents > c:\Program Files\ = ~/Windows Progs > d: = /mnt/cdrom > > Then wiping your ~/.wine would preserve your files, and with those apps > that don't require registry settings would just work without a reinstall > (Pegasus Mail is a good example). I think it would be better to figure out a way to do upgrades better. Also when we change something, it seems we need to massively increase the amount of time the old way is still valid for. The problem of being installing ancient distros then upgrading won't go away anytime soon.

Aug. 11, 2004

Re: USB?

by Rolf Kalbermatter

Aric Stewart wrote: >I do have some difficulty figuring out how win2k is translating vender >and product ids into class and interface guids. The documentation >reports that they look them up in inf files, however i am finding that >not to be true. I am suspecting that some may be hardcoded in the usb >support somewhere. Wouldn't that be something which would be put in the registry somehow for the well known IDs and for the rest I really assume the device detection routine does check for all .inf files it finds on the devices currently configured to be searched. If you look at PCI and USB inf files you will notice that the manufacturer and device ID are actually encoded in the key names which are to be added to the registry. That encoding does not always seem to be equally consistent, I've seen at least two different types, but it is obviously there. One entry for instance for the Logitec PageScanner would be %USB\VID_046D&PID_040f.DeviceDesc%=Model.PageScan_USB,USB\VID_046D&PID_040f USB\VID_046D&PID_040f.DeviceDesc="Storm Technology - Logitech PageScan USB" This is partly extracted from a logiscan.inf file on my W2K system. Rolf Kalbermatter

Aug. 11, 2004

Re: config converting problem

by Rick Romero

On Wed, 2004-08-11 at 08:08, Mike Hearn wrote: > > Don't forget that My Documents is on c: by default. > > Hmm, that's true. That should definitely be fixed. I don't even think we > map the home directory in wineprefixcreate by default, do we? I think > Marcus' patch adds that. > > > Also, reinstalling all apps just because you upgraded Wine seems a bit > > overkill, no? > > Well, yeah, but over time I think it becomes necessary as the contents > of the initial registry/config file change etc ... it's hard to know > exactly what you need to do so reinstalling is the easiest way. > > It sucks, I agree. I shudder to mention it.. but Win2k supports mounting partitions as a directories under NTFS (like unix mount). Does anyone know where that functionality resides? So instead of just having: c: = ~/.wine/c_drive d: = /mnt/cdrom ..... You could have c: = ~/.wine/c_drive c:\My Documents\ = ~/Documents c:\Program Files\ = ~/Windows Progs d: = /mnt/cdrom Then wiping your ~/.wine would preserve your files, and with those apps that don't require registry settings would just work without a reinstall (Pegasus Mail is a good example). Rick -- -- Rick Romero IT Manager Valeo, Inc. ph: 262.695.4841 Sussex, WI. fax: 262.695.4850 Rick(a)valeoinc.com

Aug. 11, 2004

no scrollbar with native comctl

by Nicolai Kuntze

Hi, I have tried my bug (2302) with mostly every dll in the native version. But the scrollbars are unvisible. The programm works fine under Windows. Can someone help me? Nicolai ---- Diese Nachricht wurde auf Viren und andere gefaehrliche Inhalte sowie Spam untersucht.

Aug. 11, 2004

Re: config converting problem

by Fabian Cenedese

>>Also, reinstalling all apps just because you upgraded Wine seems a bit >>overkill, no? > >Well, yeah, but over time I think it becomes necessary as the contents of the initial registry/config file change etc ... it's hard to know exactly what you need to do so reinstalling is the easiest way. > >It sucks, I agree. What was the ultimate bugfix if you have a problem in Windows? Looks like wine is really getting close to become like Windows :) bye Fabi

Aug. 11, 2004