Tried installing QuickBooks 2006 Pro on Ubuntu 5.10 / Linux 2.6.12-10 / Pentium M 1.7GHz, 1GB physical memory with Crossover Office Standard 5.0. The stated OS requirements are WinXP or Win2000 with IE6SP1, .NET Framework 1.1, and Flash player. I chose to use a win2000 bottle for this reason. The CD includes IE, CLR, and Flash Player in the event they're needed.
After installing the IE6SP1 for win2000 bottles target into a fresh bottle, I selected the QuickBooks supported target. DCOM95 installed, then the QB installer popped up a dialog to the effect that it could not open %windir%\system\kernel32.dll. Touching this file and restarting the QB install got a similar error dialog, this time complaining that kernel32.dll was invalid.
I copied kernel32.dl_ from the Windows 2000 Pro install CD into the bottle's %windir%\system32 and exploded it using cabextract. The next run of the QB installer gave an identical "cannot open DLL" dialog, this time for ntdll.dll. In all, there are 17 DLLs that the installer wants to grope around inside before doing anything else. Here's the list:
kernel32
ntdll
user32
gdi32
advapi32
wsock32
ws2_32
ws2help
snmpapi
shfolder
version
lz32
winmm
comdlg32
shlwapi
comctl32
shell32
After copying and expanding all the above DLLs into %windir%\system (which could itself be poisoning the results) and restarting the QB installer, the error dialogs ceased but no installer windows appeared. I went to dinner at this point for a couple hours. Upon my return, still no installer windows, just the CX Tk window waiting. There was one wineserver and one wine-preloader running, the latter of which was aimlessly gnawing on the CPU, making the system pretty sluggish. Killing these off let the CX setup app declare the installation failed, and the system came back to full responsiveness.
I don't mind pouring some more time and effort into this app, but I'll need guidance. I've been dorking around with wine for a number of years now, but have never gotten into its internals, though I have a better than average understanding of how Win32 works (sic). From what I'm reading elsewhere, the CLR might be the real killer here.