Forums Ultimate UI for Windows Forms
Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
Close
Howard
1467
Document Engine Can Cause Windows XP Crashes
posted

Just a warning ...

 

Hi Chandradeep, Thank you for your response. Luckily, we can work around the problem by asking our IT department not to use PCL 6 drivers with HP 4240 printers on Windows XP. So as far as I am concerned, the incident is closed. Basically, what you are saying is that, although you have my sample code that reproduces the problem, you are going to do nothing about the fact that you new Documents engine will cause OS crashes under certain conditions. I would think that you would proceed further by working with HP and/or Microsoft to fix the problem. But that's up to you. --Howard  

-----Original Message-----
From: SUPPORT.Net [mailto:SUPPORT.Net@infragistics.com]
Sent: Tuesday, April 08, 2008 5:28 AM
To: Howard
Subject: RE: Incident Number: UWG29168

 Hello Howard, Our developers have completed their review of development incident BR31541.  They have determined that this is "not a bug" for the following reasons: [Though we can reproduce this issue since we happen to have the same printer and driver, this remains an issue that we do not have any control over.  There is no specific code that is causing this issue, since when debugging it the crash will occur in different places, but rather seems to be a combination of setting a transform on the underlying graphics object (the result of FitToMargins) along with other aspects related to saving and restoring the clip region.  We have tried a couple approaches to working around this issue in our code, but since the bug is in the GDI/printer driver logic, we cannot debug this issue further.  As stated in the previous notes, this is further evidenced by the fact that other drivers (i.e. Office Document Image Writer) work as well as the same driver on Vista, not to mention that the PCL 5e drivers don't seem to have a problem either.] Thanks for your patience in this regards. Please let me know if I may close this incident, or if you have further questions regarding this incident. Sincerely,Chandradeep MishraDeveloper Support EngineerInfragistics, Inc._________________Review your Incidents and Bug Reports in the DevCenter Support menu:<http://devcenter.infragistics.com/Protected/MyIncidents.Aspx><http://devcenter.infragistics.com/Protected/MyBugReports.Aspx><http://devcenter.infragistics.com/Protected/IncidentBugReportSearch.aspx> -----Original Message-----From: SUPPORT.NetSent: Tuesday, April 01, 2008 5:35 PMTo: 'Howard'Subject: RE: Incident Number: UWG29168 Hello Howard, I have resubmitted the development issue [BR31541] with your comments in our tracking system. I will get back to you as soon I will get any update on this. If you would like to check on the status of this development issue, you can do so online via the following link: <http://devcenter.Infragistics.com/Protected/MyBugReports.aspx?type=Search&bugnum=BR31541> Thanks for your patience in this regards. Sincerely,Chandradeep MishraDeveloper Support EngineerInfragistics, Inc._________________Review your Incidents and Bug Reports in the DevCenter Support menu:<http://devcenter.infragistics.com/Protected/MyIncidents.Aspx><http://devcenter.infragistics.com/Protected/MyBugReports.Aspx><http://devcenter.infragistics.com/Protected/IncidentBugReportSearch.aspx>________________________________________From: Howard Weisberg [Howard@nospam.com]Sent: Monday, March 31, 2008 11:27 PMTo: SUPPORT.NetSubject: RE: Incident Number: UWG29168 I do not agree that this is "Not a Bug," and would like you to reconsider this decision. First, let me add some new information. I have found that the problem persists even when I upgrade to the latest printer driver, a PCL 6 driver. However, when I install the latest PCL 5e driver instead, the Windows XP crashes stop. I now know that the problem occurs when all the following conditions are true: 1. Outlook-style grouping2. Summaries in Group-By rows3. Calculated summaries using the UltraWinCalcManager4. Windows XP5. HP 4240 printer6. PCL 6 driver (not PCL 5e)7. Preferences.Printing.FitToMargins = true8. Calling Report.Print() I have provided you with a complete sample application that may enable you to reproduce the problem, provided you have the correct printer and driver. Unfortunately, if Infragistics does not understand why this is a bug that is important to fix, my explanation is unlikely to help. If you have a concern with delivering a high-quality product (including the perception of high quality) you should understand this need without my explanation. It is true that the root cause is the HP driver or printer firmware. Also, Microsoft should perhaps have included validation to guarantee that under no conditions can Windows XP crash even with a faulty printer driver and with any edge case graphics call. However, from the end user's point of view, we have a printer and OS that has worked perfectly well for several years for many applications. Now we add a new application (using Infragistics) and suddenly we have Windows reboots and driver incompatibilities. The end user sees a quality problem with the software built on Infragistics, and not with the OS or printer products.