Hi, I didn't find any clue in the documentation, so I'm posting my problem here. I'm trying to use wine with a special prefix, whose drive_c/ is containing a whole Windows C: drive. The problem is that I can't launch the binaries, because the wine reg files aren't in sync with the Windows registry. I tried to "reg export" the keys corresponding to system.reg and user.reg, convert the files to utf8, change the header to match Wine's one, replaced all the \ by \\ in the keys' path, changed the keys 'path to be relative like the Wine's reg file... My binaries are launching a bit better, but it looks like my exports are not perfect still. My question : Is it possible to export an existing Windows registry cleanly to Wine ? Thanks in advance, Sebastien. PS : I guess it is registry related, because I can install these programs through Wine. But I just wanted to launch through a complete C drive :) -- www.pleyo.com Join OWB team on freenode IRC, channel #owb -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.winehq.org/pipermail/wine-users/attachments/20071217/9d6cc17b/attachment.htm
Am 17.12.2007 um 19:20 schrieb Sebastien Roret:> PS : I guess it is registry related, because I can install these > programs > through Wine. But I just wanted to launch through a complete C > drive :)It's generally considered the wrong approach to map a "real" C: drive to Wine's drive_c. That said, it's intuitive to do so, many people do it (intuitively) and running applications installed natively has some benefits. For example, you avoid installer hassles; for example, you don't have to install and maintain software twice. Obviously, it would be a great enhancement to make Wine using and/or syncronising the registry of a native Windows installation. Please file a bug/enhancement report (http://bugs.winehq.org/) and include what you've already tried. "Exporting the registry" is beyond the average user's knowledge. Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/
On Monday December 17 2007 18:20, Sebastien Roret wrote:> Hi, > > I didn't find any clue in the documentation, so I'm posting my problem > here. I'm trying to use wine with a special prefix, whose drive_c/ is > containing a whole Windows C: drive. > The problem is that I can't launch the binaries, because the wine reg files > aren't in sync with the Windows registry.Run Konsole or any other Xshell you like and run this: rm -rf ~/.wine wineprefixcreate Now you should be able to install and use Windows programs you need in the same way as you do in Windows (if not report a bug at http://bugs.winehq.org ). Make to NOT change default settings for C: drive in WINE and NEVER try to import registry or its parts from Windows or from another WINE prefix. If you will not obey above recommendations no one will be able to help you, sorry. And for good reason: because Windows doesn't work support this either. For example if you install fresh copy of Windows and try to import whole registry and all program files from another Windows installation - Microsoft and other software companies will refuse to support you in case of *any* problems because of this, they will just ask you to reinstall Windows and programs properly.> My question : Is it possible to export an existing Windows registry cleanly > to Wine ?If you ask Microsoft "Is it possible to export an existing Windows registry cleanly to another Windows installation?" guess what answer you will get? WINE prefix (~/.wine by default) is essentially the same thing as separate Windows installation (with obvious differences).> I just wanted to launch through a complete C drive :)You just should install program in WINE in the way you typically do in Windows. I see no reason to not do this. If you have *really* big program and want to use it in both Windows and WINE you may (but shouldn't) try to install it in WINE to corresponding location in Windows drive where you have installed the program in Windows. This of course UNSUPPORTED and if it doesn't work - this is expected result, it shouldn't work! But it has more chances to work than your current approach. Anyway, if you really want to try it - make sure to backup any important files and remember that only supported way is installation of programs for WINE only. This is true for Windows too: if you install program in Windows you shouldn't try to use it in another Windows (or WINE prefix). If you try and something doesn't work - this is normal and expected result unless the program in question officially support installation-less launching.
Main reason to run "native": No longer have distribution, license keys, or installation does not work in Wine. Another reason to install additionally in Wine: So as not to disrupt .ini files with options that may be largely not compatible! Need for native Windows registry--the only one I can think of is license keys are often placed there and if I cannot reinstall from scratch... Another idea might be that certain dlls need be registered to be used and that data is there--examples are DirectX plugins (which probably would not work in Wine anyway). I have had little problems running native installations in Wine. Indeed, any buggy behavior I found existed both ways. I would not expect Wine to explicitely support running native installations but this is in fact a test of its capabilities. To simply flame anyone who tries it is also not the best practice. The information is useful. BTW, emulator virtual machines will not support running off or duplicating native windows installations. Windows installs for the hardware at hand and the real hardware is not necessarily related to the emulated hardware (Only Parallels on an Intel-Mac can do this). VirtualBox has problems with Win98 and must provide its own faked hardware (they call it "guest additions"--they have none for Win98) to run other Windows correctly. Qemu fakes more or less standard hardware for which Windows has drivers.