CrossOver Support - Community Forums

Im trying to make the Ford auto service CD's work in Crossover. No version I have will install properly.

The Ford installer appears to finish the job without errors, but the application does not appear in the Crossover applications folder

installation log shows dozens of messages like this:

trace:cxassocscan:get_value unable to get the size of L".css"->(null) (2)
trace:cxassocscan:do_ext L".dib"
trace:cxassocscan:do_ext mimetype=L"image/bmp"
trace:cxassocscan:get_value unable to get the size of L".dib"->(null) (2)
trace:cxassocscan:do_ext L".dll"
trace:cxassocscan:do_ext mimetype=L"application/x-msdownload"
trace:cxassocscan:get_value unable to get the size of L".dll"->(null) (2)

installation log shows dozens of messages like this:

trace:seh:raise_exception code=c0000005 flags=0 addr=0x7b88e155 ip=0x7b88e155 tid=001e
trace:seh:raise_exception info[0]=00000000
trace:seh:raise_exception info[1]=00001250
trace:seh:raise_exception eax=00000000 ebx=00000000 ecx=00000100 edx=12571257 esi=00000000 edi=00000000
trace:seh:raise_exception ebp=000026e4 esp=000026bc cs=0017 ds=1217 es=001f fs=11ff gs=0037 flags=00010246
trace:seh:call_vectored_handlers calling handler at 0x7b82b32a code=c0000005 flags=0
trace:seh:call_vectored_handlers handler at 0x7b82b32a returned 0
trace:seh:call_stack_handlers calling handler at 0x7b88de25 code=c0000005 flags=0
trace:seh:call_stack_handlers handler at 0x7b88de25 returned 0

Can anyone explain why this is failing, or tell me what kind of error an "exception c0000005" represents?

Are there some files from the Windows CD that I need to put in the bottle?

The trace:cxassocscan lines don't mean anything useful, the trace:seh stuff usually means the program just isn't going to run in Crossover. You can check out http://www.codeweavers.com/support/wiki/CXOffice_UnsupportedTips for ideas on how you can try to help your unsupported program along and maybe get it working in Crossover.

I was almost ready to give up on this when I noticed the installer succeeded in copying its files to the bottle, despite all those error messages. I supposed it was failing on each file copy operation. Turns out this was not the case:

The only thing the installer failed to do was place a shortcut in the Start Menu. So I copied that over from a working Windows installation. Then I noticed the program did not appear in the Crossover applications folder. After opening various utilities in the "manage bottles" section, somehow I got it to rebuild the contents of the applications folder and now it appears.

(I think you need a button especially for that purpose if some installers are not going to work. Or maybe it could just scan for new shortcuts when Crossover launches.)

Now the app is prompting for the data CD to be inserted when its already inserted. Wine configuration shows the disc mounted as both D: & E: (?)

After ejecting the physical disc, E: disappeared--but a phantom disc is still mounted as D:

The phantom disc in D: is still present after a reboot (!)

If I press Auto Detect the real disc appears as E:

I removed the phantom D: but the app still cant find the real disc in E:

(the app is supposed to find the library disc in any CD-ROM drive)

This app was designed for Win 95 or 98, but it runs just fine on XP & Vista. I suspect that maybe they are using a deprecated method of accessing removable drives that is still supported by 32-bit Windows but not by Crossover. Is there a published guide anywhere that details a manual work-around for this issue?

Hi,

Regardless of whether it runs ok in winxp/vista, I would try running
the app using a win98/win2000 bottle/wine profile just to be sure (I
have seen such make a difference in crossover/wine)...

If the app is utilizing some of the older *.vxd drivers as used in the
win98/95 OS environments, then I already know they are either broken
and/or needing lots of work in wine - that said, you are using MacOSX
and are therefore subject to the limitations of the MacOSX scsi drivers
..ie; they are known to be broken in the crossover/wine environments
and/or need a lot of work being rewritten/reimplemented (in wine itself)

What you've described so far, looks suspiciously like some kind of DRM
incorporate of the software/disc_media itself -- I really can't comment
to the 'phantom drive' business, as I don't run Mac/OSX...however, if
this is the case (DRM/disk_check routine), it's unlikely to work on Mac
at all at this time due to scsi driver limitation, and I'd even think
linux would have trouble here too (gut feeling) - all speculation of
course (I don't have the software in front of me :), but don't overlook
this angle -- it might not be normal file/filesystem access troubles,
but low-level driver access issues instead.

Just my thoughts ;)

Cheers!

I would try running the app using a win98/win2000 bottle/wine profile just to be sure

I did; no success. But when I created a new bottle there were no more problems with phantom discs. I think I was going in the wrong direction by installing various other Windows components here. Thanks for mentioning that.

Some other info:

When the app runs from the XP bottle, its not listed in task manager
When the app runs from the 98 bottle, it appears in task manager normally

I tried to install Process Explorer to get a better view of whats going on, but PE says it could not create its driver. (The driver actually was created in system32). After hours of research & testing, I still cant find any extended task manager or process monitor that runs in the Crossover environment.

An observation:

I inserted the CD and waited for the drive to spin down. One time when the app prompted for the CD, I heard the drive spin up. But I could never get that to happen again. Simulating a reboot and restarting Crossover made no difference. Even ejecting the disc and re-inserting it made no difference. There was just one time when clicking on the OK button in the viewer app made the drive spin up. It did not see the CD though. If I eject the disc, it still appears in Winecfg unless I quit and restart Winecfg. The Autodetect button does not refresh the drive status when ejecting the disc--it only does that when a disc has been inserted.

With regard to my first post:

I determined that I can refresh the Applications folder and see my app by launching another installer. But when that installer completes, the app disappears again. (Not really a problem, just something I wanted to mention.)

Further testing:

I installed a file browser called WinNavigator and I can browse the CD via the Win98 bottle. If the installer is able to read from the CD, it would seem the viewer should be able to do that too. I understand why this would appear to be a DRM issue, but am virtually certain its not. I see no DRM wrappers and a backup copy works fine on a Windows box.

The app is basically a simple HTML viewer with a custom layout mechanism. When you click on a menu button, it appears that a DLL is executed which allows you to choose a page on the CD that you want to view by clicking on its title. Whatever method they are using to scan for the mounted volume, its not working in Crossover. I found a program called ExeScope which allows you to see the functions in a 16-bit DLL but I am no closer to determining if there is anything I could change to get this going.

I will always appreciate the suggestions others may have, but CD-ROM access is such a universal function, it seems to me that this is the first thing Wine developers would want to get working reliably. It was explicitly stated that the application is supposed to run on XP, but I noticed that it does so in the 16-bit virtual machine on XP. I dont necessarily expect that should work in an XP bottle under Wine, but I do think a 98 bottle should support any CD-ROM access methods that are supported by the Microsoft 16-bit virtual machine.

Hi again,

Thanks for the follow-ups...it's still sounding like the Mac scsi drivers..

Have you tried creating/mounting an iso of the disc? Same result?

If you can grab a debug log of a clean attempt at running this app, and
post same to a public repo. like rapidshare.com and post the URL back
to this thread, I can download it and have a look - perhaps there will
be a clue in the trace that indicated what's going on.

Cheers!

Wow, thanks for the prompt reply. :)

Have you tried creating/mounting an iso of the disc? Same result?

Sure did; no luck there. I even took care to give the virtual volume the same name & serial number as the physical disc in Winecfg.

If you can grab a debug log of a clean attempt at running this app

Looks like someone already did this:

[Wine] Ford Tech Serv app does not work
http://www.winehq.org/pipermail/wine-users/2007-April/027076.html

Another interesting post -- I dont know if this feature was ever implemented in Wine:

not ready yet for cvs inclusion (yet), this patch implements two things:

• it replaces the wine internal & proprietary cdrom interface (used
  in MCICDA and MSCDEX/int2F) with the proper win32 ioctl:s calls

• it allows opening any device with CreateFile (using the name "\.\E:")
  (this is still very hackish, but not worse than what already existed)

http://www.winehq.org/pipermail/wine-devel/2001-December/003037.html

According to the change log, the latest version of Crossover is: 8.0.0 - June 16, 2009

http://www.codeweavers.com/products/cxmac/change_log/

So a fix like the one below would not be in Crossover, right?

2009-10-21
[PATCH] ntdll: Implement CDROM_GetDeviceNumber() on Mac OS.

http://marc.info/?l=wine-patches&m=125616565804390&w=2

No problem..

Okay...seems like you've isolated the issue (and given credence to my hunching ;)

It also explains why it appears like DRM issues...

I'm not exactly sure of the state of play wrt the patches cited and the crossover
wine build - one of the codeweavers devs will have a succinct answer for sure...

In that regard, there's enough 'triage' here to be worth doing the following;

Email info@codeweavers.com explaining this issue - be sure to include a link back to this thread
The (still beta) crossover 9.0 wine_build may include these patches, I am unsure but one of
the devs will know -- if that is the case, ask them if you can try the CO-9.0 beta

Otherwise, the situation will be that such patches have to be approved/incorporated in
wine first before they become part of crossover's wine build -- that said, it never hurts
to alert the devs here of what features people want/need in crossover ; it gives them
some idea of what feature sets to incorporate in future crossover releases.

Thanks for digging all the info/clues here - good sleuthing work on your part (;

Cheers!