This is an archive of CompuServe forum messages from 1985 to 1995, as saved in transcripts by John Foust.
Search Results (12 messages)
C# Oh…Thank Yew all so veeery much… I'd like to thank all the members of the Academy… my parents… my 1st-grade teacher… my 2nd-grade teacher… my 3rd-grade teacher… my 4th-grade teacher… . . . Jeez, Craig, this floppy's worthless! I'll never be able to read the files off it now!…
Gale! No…*I'm* sorry if it appeared to you that I took umberage! That last was *supposed* to have been in the nature of a "playful reposte." Alas, my inferior communications skills strike again… Believe me Gale, if I'm ever even slightly upset with ya, you can rest assured that you…
C#, ???Ken interviewed AYA??? Oh Keeennn…hows about a copy of that AYAnterview, please? BTW – how many more points do I need? Mark Burns – TKLP Inc.
Gale, Did something I said strike close to a nerve, or are you just attempting to correct my ignorance on this general subject? …and XENIX may very well be a bit better at handling the DOS-format files due to it's PC-based heritage (and long association with DOS files) I cannot…
Larry… Yeah…you'd better Duck! Let's just say that it took the Bugs in the AES-produced DXF file to uncover a BUG in AutoCAD, OK? Mark Burns – TKLP Inc.
Duff, All I'm suggesting is *allowing the user the option to choose* which End-of-line format to create a DXF file with. I'm not asking you to change the default mechanisms that you already have in place…I think I know a little bit better than that by now… This would permit…
Duff, Yes, I did understood that from your first message. However, the need to fix errors in the DXF file in a DOS-based editor did/does make it necessary to massage the DOS s into place. Perhaps, since *NIX-based ACAD can handle this anyway, the scheme should, at least optionally, be…
Duff, Rats. I was hoping I'd gotten it wrong… Oh well…at least you folks know about the problem for R12 now… and If need be I can edit the faulty DXF files into acceptable shape (PITA that that'll be), so I guess I can live with this…but BOY was it…
Papa, You are correct in pointing out the fact that the AES DXF translator does not produce a "correct" DXF file. It has *many* *many* bugs, and for that reason it did not pass our evaluation tests. Accordingly, we did not purchase it. Regarding testing the problem files with *NIX…
Larry, I have/had ACAD configured to do an automatic AUDIT following a DXFIN, IGESIN, or DXBIN (check your #8 system options in the configuration menu – item #9). Enabling this feature will cause ACAD to automatically fire up the AUDIT function after any drawing import commands is executed. Note: this…
Duff, I figgured that if I pushed hard enough I'd finally get SOMEBODY from Adesk to respond in a definitive manner… Thanks for the response. Yes, we are *VERY* aware of a large number of bugs with the AES DXF translator. Because of all those bugs we chose not to…
Larry, Well…the bug COULDN'T have existed prior to R11, because there was not AUDIT function available before R11, Remember? …or, more correctly, the BUG (which probably DID exist prior to R11 – sorta) couldn't manifest itself in this manner prior to R11. Regards, Mark Burns – TKLP Inc.