Hi
l've managed to fly in FS9 by simply mounting my Win partition. Now a lot of addons have registry entries so I wonder if I could bypass all this installation orgy somehow? Anyone tried to copy the original Windows registry to .wine? Also some paths would need adjustments?
Thanks
copy Windows registry
copy Windows registry
On 2010-07-06 (July, Tuesday) 06:28:50 ahso wrote:
prefix). Not only in Wine but in Windows too. Think about Wine prefix(es) as
clean installation(s) of another version of Windows; you can't copy the
registry from Windows 7 to Windows XP and vice-versa without breaking
everything; similarly, you can't copy the registry from Windows to Wine or
vice-versa without breaking everything.
Only way to bypass installation is by using programs like InstallRite but this
should be avoided (there a lot of reasons why such programs aren't perfect and
not always can replace real installation - remember that you should think about
Wine prefix like separate installation of Windows). If you can do normal
installation - do it. If you can't - report a bug.
If you don't want to reinstall your application every time something brakes
for whatever reason, install it in separate Wine prefix, back up it and use your
application; if something brakes or you will want to "install" it for another
user, use the "clean" backup of Wine prefix with the installed application. This
is the best way to avoid installation(s).
Of course if you are too lazy to even install your application at least once,
nothing will help you. For example if you are using Windows 7 and decided to
install Windows XP you will not be able to run most of your Windows
applications (installed in Windows 7) without reinstalling them (in Windows
XP). For Wine it is the same.
You can't do that (actually you can but it will brake EVERYTHING in your WineHi
l've managed to fly in FS9 by simply mounting my Win partition. Now a lot
of addons have registry entries so I wonder if I could bypass all this
installation orgy somehow? Anyone tried to copy the original Windows
registry to .wine? Also some paths would need adjustments? Thanks
prefix). Not only in Wine but in Windows too. Think about Wine prefix(es) as
clean installation(s) of another version of Windows; you can't copy the
registry from Windows 7 to Windows XP and vice-versa without breaking
everything; similarly, you can't copy the registry from Windows to Wine or
vice-versa without breaking everything.
Only way to bypass installation is by using programs like InstallRite but this
should be avoided (there a lot of reasons why such programs aren't perfect and
not always can replace real installation - remember that you should think about
Wine prefix like separate installation of Windows). If you can do normal
installation - do it. If you can't - report a bug.
If you don't want to reinstall your application every time something brakes
for whatever reason, install it in separate Wine prefix, back up it and use your
application; if something brakes or you will want to "install" it for another
user, use the "clean" backup of Wine prefix with the installed application. This
is the best way to avoid installation(s).
Of course if you are too lazy to even install your application at least once,
nothing will help you. For example if you are using Windows 7 and decided to
install Windows XP you will not be able to run most of your Windows
applications (installed in Windows 7) without reinstalling them (in Windows
XP). For Wine it is the same.
copy Windows registry
On 2010-07-06 (July, Tuesday) 07:36:58 ahso wrote:
itself). And for big applications with many addo-ons/plug-ins you should use
separate Wine prefix for better stability (of course, you should backup it in
this case too; this is actually general rule for everything (any digital data):
if you don't backup something you will lose it eventually). If you have a
backup and upgrading to new Wine ruins Wine prefix restored from your working
backup then it can be debugged and fixed or you can temporary revert to older
version of Wine. Without a backup you may brake your Wine prefix without
possibility to restore it.
As I said, backup your Wine prefix (and never run program(s) in the backuphmm that's what i feared. Now i did once a wine install but after a Linux
update, FS9 refused to start! - FS9 has hundreds of addons ,so i want to
avoid such by all means.
itself). And for big applications with many addo-ons/plug-ins you should use
separate Wine prefix for better stability (of course, you should backup it in
this case too; this is actually general rule for everything (any digital data):
if you don't backup something you will lose it eventually). If you have a
backup and upgrading to new Wine ruins Wine prefix restored from your working
backup then it can be debugged and fixed or you can temporary revert to older
version of Wine. Without a backup you may brake your Wine prefix without
possibility to restore it.
-
williams2329
- Newbie
- Posts: 2
- Joined: Wed Jul 07, 2010 6:23 am
i had the same problem which will be resolved by your help very soon. I will never make use of FS9 because it has many addons which I do not want and one more task I will do and that is to update my Linux. I have taken my backups on another external hard disk because I know it is beneficial at the time of this kind of situations.
