You could start by writing Wine instead of WINEruelle wrote:So..
What we have to do??
I suggest to extend this need to a large number of people and get more visibility for all the WINE project.. (and AutoCAD bugs)..
Talk about WINE (and AutoCAD support) in our blogs, IT publications, big forums (like ubuntu?)...
Maybe there's someone capable to solve (AutoCAD) bugs..
What do you think? What we have to do?
P.S. what about AutoCAD2008 "platinum" as WINE 1.* feature??
I tried. Install procedure finished OK, but I can not start them...ruelle wrote:Why don't you give it a try..
and let us know in AppDB...
i have 2004 but not 2005...
Code: Select all
fixme:win:EnumDisplayDevicesW ((null),0,0x32f66c,0x00000000), stub!
fixme:wtsapi:WTSRegisterSessionNotification Stub 0x10030 0x00000000
fixme:dbghelp:dump_system_info fill in CPU vendorID and feature set
In addition to Wine Gurus, you might want to ask Audodesk to certifysorry Grof I don't know how to help you...
we need the attention of Wine gurus...
I tried install AutoCAD 2008, and I succeed! Without any patch and recompile wine 1.1.4, only known winetricks...ruelle wrote:sorry Grof I don't know how to help you...
we need the attention of Wine gurus...
Sorry but I'm little sceptic about this. Why?Dotan Cohen wrote: In addition to Wine Gurus, you might want to ask Audodesk to certify
AutoCAD for Wine:
http://usa.autodesk.com/adsk/servlet/in ... id=1073074
Don't forget to mention that now that there is a 1.0 release of Wine,
they can certify against that stable branch.
--
Dotan Cohen
While Autodesk may never have a native Linux version of AutoCAD, theySorry but I'm little sceptic about this. Why?
Because the newest ACAD 2009 use .NET 3.0 technology and Wine do not support .NET 3.0 (only .NET 2.0 via winetricks)
that thread has some amusing commentsGrof wrote:This is your text, or you copied them from Autodesk forums??
Why I ask? Because Autodesk implement the newest Microsoft's technologies as .NET 3.0 and they do not want to downgrade products only for reasons like working on Wine...
I vote for that (working acad under Wine direct from Autodesk), but I do not believe that will be happen!
Here is the very interesting text about AutoCAD and Linux....
Sorry to say it, but as much as I'm not a big fan of
Microsoft, the idea that Autodesk is going to to spend
hundreds of millions of dollars only to accomodate a
handful of Microsoft-haters and cheapskates, borders
on delusional.
My own words. I am unfamiliar with the AutoCAD forums, I am more intoThis is your text, or you copied them from Autodesk forums??
Of course they will not rewrite the software in another technology.Why I ask? Because Autodesk implement the newest Microsoft's
technologies as .NET 3.0 and they do not want to downgrade products
only for reasons like working on Wine...
It won't happen anytime soon. But if we start letting them know nowI vote for that (working acad under Wine direct from Autodesk), but I do
not believe that will be happen!
Wrong! They ARE switched to .NET 3.0.Dotan Cohen wrote: Of course they will not rewrite the software in another technology.
However, had they known that running AutoCAD in Wine was important,
they might not have switched to .NET 3.0 before it runs in Wine.
Likewise, if you start letting them know _now_ that there is demand
for AutoCAD on Linux, then in the future they won't switch from .NET
3.0 to .NET 4.0 before it runs in Wine.
This is wrong. My application (even if not Autocad) is still working with .NET 2 and has a Vista version (god knows how long) but a .NET 2 application CAN run under Vista.Grof wrote: All MS Vista is under .NET 3.0. So if you want to make apps compatible with Vista, than use .NET 3.0... This is another politics, too!
The CUI error is due to (IIRC) msxml3 (must be native) and because of the registry bug on which I wrote 3 patches but none of them was applied to wine three.Grof wrote: I tried install AutoCAD 2008, and I succeed! Without any patch and recompile wine 1.1.4, only known winetricks...
but acad 2008 is unstable (errors in initialize CUI....)
Of course they can, .NET 3.0 is downward compatible with .NET 2.0.Timeout wrote: This is wrong. My application (even if not Autocad) is still working with .NET 2 and has a Vista version (god knows how long) but a .NET 2 application CAN run under Vista.
For Codeweavers, probably yes, since it is turning money in. Idealism won't pay the tax bills and Outlook will probably be the law of the most return for the least effort (compared to AutoCad).ruelle wrote:http://bugs.winehq.org/show_bug.cgi?id=13801#c40
http://www.winehq.org/pipermail/wine-de ... 67927.html
Outlook is more important than AutoCAD?
Funny...Timeout wrote:For Codeweavers, probably yes, since it is turning money in. Idealism won't pay the tax bills and Outlook will probably be the law of the most return for the least effort (compared to AutoCad).ruelle wrote:http://bugs.winehq.org/show_bug.cgi?id=13801#c40
http://www.winehq.org/pipermail/wine-de ... 67927.html
Outlook is more important than AutoCAD?
I agree (partially) about M$ Office, we should make our customers used to Openoffice, as it's free. I DON'T agree about outlook, it's just inferior to Linux couterparts and you don't need it to deploy anything.Timeout wrote:Because you can't understand that to need office != to want Windows.
Seriously I am on Linux, I have on my distro OpenOffice + MS Office, but still OpenOffice is being used but I will never make a last check of a file without MS office because there are still a lot messed around between the two when you are using it more than for your private letters.
I am happy that Wine and Crossover makes me possible not to have to go to Windows every day, but for the sake of my business, I can't forget MS office when clients complains that their files comes back with an awkward formatting.
