Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
I have successfully printed HTML pages with single embedded DWF files (from the File Print Menu), however when prnting a HTML page with two DWF files, IE5.0 crashes with the following error message box :-
[snip]
Microsoft Visual C++ Debug Library
Debug Error
Program: C:\Program Files\Internet Explorer\IEXPLORE.EXE
abnormal program termination
(press Retry to deug application)
[snip]
After pressing Ignore or Retry, a second similar dialogue appears with only an OK button. IE then closes down completely.
When I remove one of the DWF objects the page prints out fine. Printing individual drawings from the VVE right click menu works.
The HTML code for a typical DWF object is as shown below :-
[snip]
[snip]
DWF files have been created with AutoCAD R14.01, Operating System = Windows 95 (4.00.950 B), Browser = IE 5.0 (5.00.2314.1003). I have Volo View Express (build 129) and Volo View (build 130) installed. The same problem occurs on PC's without Volo View Installed.
I didn't think that posting the code extract would try and display the drawing. I've reposted it below with semi-colons at the start of each line to try and stop it displaying.
--
Joshua Tapp ( josht@scm-ae.com )
Designer/Intern - Architecture Group - SCM Consultants, Inc. -
http://www.scm-ae.com - A part of Infrastructure Northwest Group -
http://www.ttinw.com - Division of Tetra Tech, Inc. - http://tetratech.com
aiclark wrote in message
news:ef36470.1@WebX.SaUCah8kaAW...
> Sorry folk that didn't work either.
>