Re: [CAD_CAM_EDM_DRO] Future CNC man

dlantz@... wrote:

> Shawn, yes there are several ways to get .dwg's to work under
> linux. the most direct way is to get vmware (www.vmware.com),
> and simply run autocad under a windows98 (tm) window.

<ANAL RESPONSE>
When you run VMWare under Linux, you aren't really running Linux.
You are running a virtual machine and Windows.
</ANAL RESPONSE>

Given the cost of VMWare (at least a commercial copy, $300), plus
the cost of Windows itself (typically another $50-150), it might be
more cost effective to build a second, $300 headless Linux box and
use a program like VNC. Your main workstation should be the system
that you do most of your primary work on -- i.e. Windows if you
mainly use Windows, or Linux if you mainly use Linux. VNC to the
other system, which doesn't need its own monitor, keyboard or mouse.

Just a suggestion.

> i do that with autocad2000, it is a touch slow, but i have an
> old machine.

Memory is recommended. Remember, with VMWare, you are running
virtually two (or more) machines, so you need double (or X) the
normal amount of memory. Win4Lin is cheaper (~$50) and requires
less overhead, because it virtualizes just below the MS-DOS kernel
(so you're limited to Windows 9x), so you might consider it
(although there might be a few compatibility issues). You still
need a Windows license though.

Alternatively, the WINE project's open source Windows Emulator
translates Windows functions into direct Linux/X-Windows calls, but
that means compatibility is even less. The advantage of WINE is
that it doesn't require Windows at all (although a working Windows
partition is recommended, largely for DLLs and other support
libraries), and it can do 3D natively c/o OpenGL (if your Windows
app uses it). But I seriously doubt AutoCAD works under WINE, given
that Microsoft blackmailed (long story) AutoDesk and forced them to
drop all non-Windows versions and AutoLisp (so expect undocumented
Win32 functions in the code, just like MS Office).

-- TheBS

P.S. Of course, getting away from the .DWG "standard" is probably
most ideal, since it is a "moving target" and AutoDesk does not
maintain file compatibility for more than one release back, and it
is never complete at that (just like Microsoft). But that will all
depend on your application and tool needs, and existing documents.
And the longer you use a closed file format, the more hard work is
bound by it. A catch-22 that only you can decide what to do on.

--
Bryan "TheBS" Smith mailto:b.j.smith@... chat:thebs413
Engineer AbsoluteValue Systems, Inc. http://www.linux-wlan.org
President SmithConcepts, Inc. http://www.SmithConcepts.com