wine users - Feb 2005 - BricsCAD won't start

Hello,

I run Mandrakelinux 10.1 with wine-20040813-2mdk. I have  BricsCAD version 
5.1.0012-1 installed. Upon start, I get this wine error message:

can't open file icad.log error=5  (Access to icad.log was denied)


[pablo@localhost bricscad]$ /opt/bricscad/bcad.sh
fixme:ole:CoRegisterMessageFilter stub
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:wintab32:WTOverlap (0xc00, 0): stub
fixme:wintab32:WTOverlap (0xc04, 0): stub
fixme:wintab32:WTOverlap (0xc08, 0): stub
fixme:ole:CoCreateInstance no classfactory created for CLSID 
{eab38d64-26dc-11d2-98c0-00104b24170b}, hres is 0x80040154
err:x11drv:X11DRV_CreateWindow invalid window width 735338766
err:x11drv:X11DRV_CreateWindow invalid window width 735338766
err:x11drv:X11DRV_CreateWindow invalid window width 735338766
err:x11drv:X11DRV_CreateWindow invalid window width 735338766
fixme:storage:StgCreateDocfile Transacted mode not implemented.
fixme:wintab32:WTOverlap (0xc00, 1): stub
fixme:wintab32:WTOverlap (0xc04, 1): stub
fixme:wintab32:WTOverlap (0xc08, 1): stub
wine: Unhandled exception (thread 0039), starting debugger...
err:seh:start_debugger Couldn't start debugger ("winedbg --debugmsg
-all 56
428") (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
fixme:wintab32:WTOverlap (0xc00, 0): stub
fixme:wintab32:WTOverlap (0xc04, 0): stub
fixme:wintab32:WTOverlap (0xc08, 0): stub

Any help greatly appreciated.
Thanks
-- 
Pablo Ort?zar

--- Pablo Ortuzar <portuzar@wanadoo.fr> a ?crit : 
> Hello,
> 
> I run Mandrakelinux 10.1 with wine-20040813-2mdk. I have  BricsCAD version 
> 5.1.0012-1 installed. Upon start, I get this wine error message:
> 
> can't open file icad.log error=5  (Access to icad.log was denied)
You should update wine. (wine 20050211 is out)
Make sure you have write access to icad.log

> wine: Unhandled exception (thread 0039), starting debugger...
> err:seh:start_debugger Couldn't start debugger ("winedbg
--debugmsg -all 56
> 428") (2)
> Read the Wine Developers Guide on how to set up winedbg or another debugger
Make sure winedbg is in your $PATH.
Otherwise, it looks like there is a wine installation problem.



====Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word