[Wine] Re: CadStd Access Violation Problem

Alan_H wineforum-user at winehq.org
Mon Feb 28 10:41:13 CST 2011


Hi James, and thanks for responding, especially so soon.

The other program is FutureTax, a Canadian income tax program.  It likely doesn't have enough users to warrant a lot of maintenance effort.  I posted a note on the AppDB to update the status for anyone interested based on my experience.

As to running double versions of Wine I realize it's an option, but I'm loathe to do it simply because it complicates maintenance and upgrades on the system as a whole and introduces risk more than its worth to me.  I don't need CadStd that badly, and not as urgently as the tax program.  It would be nice to have them both running, but the my world won't shake if they don't.

Is there any way of tracking what program access is triggering the message?  I tried running winedbg, but it doesn't seem to generate any trace information.  I'm not sure it's even working, as CadStd quits almost as soon as it starts under this control.  (I have to stop it normally).

Alan







More information about the wine-users mailing list