After several weeks of meaning to, today I finally got around to trying SAPGUI for Windows (the client application for most SAP solutions) under CrossOver Office 5.0. After a few false starts, I managed to get it to install and run (the installer wouldn’t even start correctly under CrossOver 4.2). Woot! It doesn’t work properly (or even well enough to be usable), but CodeWeavers and the Wine team are making some good progress.

Some tips:

  • Install into a Windows 98 bottle. Even though SAPGUI no longer supports Windows 98, when using a Windows 2000 bottle the installer continually reboots the Wine session.
  • Install Internet Explorer 6.0 before installing SAPGUI.
  • Once SAPGUI is installed, guilogon.exe doesn’t seem to work correctly (possible a Unicode issue) – it runs, but any entries that are added don’t get displayed in the logon pad. In addition, it doesn’t pass parameters to sapgui.exe correctly. The solution is to execute sapgui.exe directly, passing it the server details (for example, sapgui.exe /H/my.sapsystem.com/S/3200).

I used the GA version of CrossOver Office Professional 5.0 on a Debian 3.1 system running kernel 2.6.13. I did the installation from the SAPGUI 6.40 Compilation 3 DVD.

If you’re interested in checking the progress or testing SAPGUI under CrossOver, be sure to check out its entry in their compatibility list.

 
cxoffice_sapgui_01
Logon screen
cxoffice_sapgui_02
Easy access
cxoffice_sapgui_03
Transaction OS06
cxoffice_sapgui_04
Transaction SE38
cxoffice_sapgui_06
The IMG
 
cxoffice_sapgui_05
SE38 control shortdump
 

  • Share/Save/Bookmark