http://bugs.winehq.org/show_bug.cgi?id=8178
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|msi |gdiplus
--- Comment #11 from Dan Kegel dank@kegel.com 2008-10-16 23:23:46 --- BTW, the disc seems to have been badly mastered. I had to mount the cdrom with the 'norock' option, else the files on the disk are not readable.
The outer setup.exe still has problems. I tried
winetricks -q volnum win2k wine setup
and it seemed to sucessfully install mdac and dotnet11 (modulo the usual crashes). It however had a stack overflow error trying to install the actual product. (Possibly because the .msi file is expected to be named greatplains.msi, but is named greatp~1.msi because of the norock problem.)
To work around the short names created by mounting norock, I created a directory full of symlinks to the files on the cdrom, but with long names. This changed things; now it failed with wine: Call from 0x7ee11140 to unimplemented function gdiplus.dll.GdiplusNotificationHook, aborting fixme:gdiplus:GdipGetLineSpacing stub!
Adding 'winetricks gdiplus' helped! The setup init screen looked snazzier. It then fell over with
fixme:shell:URL_ParseUrl failed to parse L"Microsoft.Dynamics.GP.Deployment.CommonDialogs.resources" and the dialog "Failed to load resources from resource file."
So we're getting quite close. Let's call it a gdiplus bug for now.
(FWIW: The following recipe lets you install the product without using the outer setup: winetricks -q volnum dotnet11 win2k wine bin/mdac/mdac_typ.exe wine msiexec /i bin/greatp~1.msi After doing that, the inner installer runs to completion nicely, modulo two cosmetic problems, list of countries looked like it hadn't been expanded, couldn't access EULA)