Hi, Sorry if this has been discussed before but I could not find a searchable archieve of the list. For some time now Microsoft Office 97 installs almost perfect. However, in the end of the instalation it warns about vbe.dll could not regiter itself. Then the instalation ends with an error. Even with the error, everything is in place. The registries are correct (at least they seem to be). Word and Excel runs nicely. Everything in a windows/native dlls free environment. I found this document about the issue from Microsoft: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q162627 I check everything it says and everything seems to be correct. As more people have tryied Office 97/2000 with wine, this error might be already known. (I hope so) So, why does it happen? Is it a bug or something not implemented (or half implemented) in wine? Is this caused by some missing file/dll/registry entry ? Is this some ugly undocumented hack that office 97 installer does? btw, the version is Office 97 Pro in pt_BR. []'s Raul Dias
--- Raul Dias <chaos(a)swi.com.br> wrote:
Hi,
Sorry if this has been discussed before but I could not find a searchable archieve of the list.
Use Google. It indexes archives, stored on www.winehq.com.
For some time now Microsoft Office 97 installs almost perfect. However, in the end of the instalation it warns about vbe.dll could not regiter itself.
I'm not sure, but it is possible that installer could not find and execulte regsvr32 - the application, which registers dlls. Wine version was added to the main tree not so long time ago. Plus, until recently the wine applications were not installed with wine. Be sure you have this application and it is installed. Alternatively you can try to use Windows regsvr32, but I'm curious how things will go with a native one. Let us know about results. BTW, this kind of problems is better to dicsuss on wine-users mailing list. Andriy Palamarchuk __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com
Andriy Palamarchuk <apa3a(a)yahoo.com> wrote:
Sorry if this has been discussed before but I could not find a searchable archieve of the list.
Use Google. It indexes archives, stored on www.winehq.com.
Downloading the archivies and letting my MUA search was better. :)
For some time now Microsoft Office 97 installs almost perfect. However, in the end of the instalation it warns about vbe.dll could not regiter itself.
I'm not sure, but it is possible that installer could not find and execulte regsvr32 - the application, which registers dlls. Wine version was added to the main tree not so long time ago. Plus, until recently the wine applications were not installed with wine. Be sure you have this application and it is installed.
I have it installed and working (as opposed to regedit) in my /usr/bin . However wine apps doesn't seem to find it. Should I rename it to regsvr32.exe and move (with the regsvr32.so) to my %windows dir ? If so, wouldn't it be better to let wine applications (win32) call native linux applications? Maybe a replacement section in the config which would accept stuff like: #This would let a call to a generic (search in wine's #Path) notepad and call a generic (in the user's unix #Path) gvim "notepad.exe" = "gvim" #This would be a more restricted one #only if the application called matchs the dir "c:\windows\sol.exe" = "/usr/X11R6/bin/solitaire" This would also avoid a linking hell in the c:\ tree. If wine can already call unix applications, or a replacement section as I suggest works, I can write an app to sync wine mime and extention registries (as windows explorer does on windows) with KDE/Gnome/mailcap/mime . I am not familiar with wine insides other than compiling it, but this might be a way I can help. -Raul Dias
--- Raul Dias <chaos(a)swi.com.br> wrote:
For some time now Microsoft Office 97 installs almost perfect. However, in the end of the instalation it warns about vbe.dll could not regiter itself.
I'm not sure, but it is possible that installer could not find and execulte regsvr32 - the application, which registers dlls. Wine version was added to the main tree not so long time ago. Plus, until recently the wine applications were not installed with wine. Be sure you have this application and it is installed.
I have it installed and working (as opposed to regedit) in my /usr/bin .
However wine apps doesn't seem to find it. Should I rename it to regsvr32.exe and move (with the regsvr32.so) to my %windows dir ?
The current wineinstall script should create *.exe->wine and *.exe.so->*.so links in the windows directory and wine should find the app there.
If so, wouldn't it be better to let wine applications (win32) call native linux applications? Maybe a replacement section in the config which would accept stuff like:
I think you can call Linux apps from Windows applications.
#This would let a call to a generic (search in wine's #Path) notepad and call a generic (in the user's unix #Path) gvim "notepad.exe" = "gvim"
#This would be a more restricted one #only if the application called matchs the dir "c:\windows\sol.exe" = "/usr/X11R6/bin/solitaire"
This would also avoid a linking hell in the c:\ tree.
All this can be implemented with "links hell", right? ;-)
If wine can already call unix applications, or a replacement section as I suggest works, I can write an app to sync wine mime and extention registries (as windows explorer does on windows) with KDE/Gnome/mailcap/mime .
I am not familiar with wine insides other than compiling it, but this might be a way I can help.
Sounds good for me. Anybody else can give a feedback? Andriy __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com
Andriy Palamarchuk <apa3a(a)yahoo.com> wrote:
I think you can call Linux apps from Windows applications.
#This would let a call to a generic (search in wine's #Path) notepad and call a generic (in the user's unix #Path) gvim "notepad.exe" = "gvim"
#This would be a more restricted one #only if the application called matchs the dir "c:\windows\sol.exe" = "/usr/X11R6/bin/solitaire"
This would also avoid a linking hell in the c:\ tree.
All this can be implemented with "links hell", right? ;-)
I was trying to avoid it. This can become a burnier hell if you keep on fake-windows tree for each installed app (thru $WINEPREFIX var) as I do. []'s Raul Dias
participants (2)
-
Andriy Palamarchuk -
Raul Dias