[Bug 8795] Excel 2003 on AMD64: Visual Basic not working

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=8795





------- Additional Comments From claus.fischer(a)clausfischer.com  2007-12-07 18:08 -------
Summary
*******

I compiled Wine 0.9.40 both on 32 and on 64 bit Debian etch.

The error is still present on Wine 0.9.40,
probably both on 32 bit and 64 bit host systems.

But on 64 bit systems an X protocol error prohibits
full installation, so it does not behave exactly the same.



The details:
************

    Note: all files can be found on http://www.clausfischer.com/winebug/

0.  Prepare Wine packages for Debian.

    I created my own patch from the Debian 0.9.34 packages.
    See wine_0.9.40-1.diff
    - unpacked wine-0.9.40.tar.bz2
    - cd wine-0.9.40
    - pach -p1 <../wine_0.9.40-1.diff
    - chmod +x debian/rules
    - comment out the line with 'arts' in debian/rules
    - dpkg-buildpackage -rfakeroot
    - install all packages

1.  Configure Wine
    Pretty regular configuration.
    Changed OSS to Alsa sound driver (but don't know if it works).
    
2.  Change system.reg (set default user and company name).
    
3.  Install Excel 2003 and Word 2003:
    
    wine 'd:\setup.exe'
    
    See the screenshots 1-4.
    
    Notably, excel does not show the required storage (see screen3).
    
4.  When clicking 'Finish', wine seems to hang in the 'tee' command.
    After clicking Ctrl-C, wine reports: Wine exited with a successful status.
    
5.  wine 'c:\Program Files\Microsoft Office\Office11\EXCEL.EXE'
    
    Excel prompts for my username and initials.
    I enter 'cfischer', empty string.
    No screenshot, unfortunately.
> From here on, the versions on 32 and on 64 bit behave differently:

6a. On 32-bit, Excel is satisfied.
    I can start Excel regularly, and get the error that I originally
    reported, i.e. the 'Error Accessing File'.

6b. On 64-bit, Excel asks whether I accept the license.
    I accept, but Excel then seems to crash.
    Apparently wine produces a bad X lib call.

    Wine gives an error log: wine.log.excel_first_start_crash

7b. Same command again.

    Wine reports the 'Error Accessing File'.
    Afterwards reports "excel was not installed for this user"
    then crashes again. Probably a consequence of the first crash.
   
    Error log: wine.log.excel.second-crash



-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.