Unregistered
October 29, 2002, 17:19:44
Hello,
Using the C++ Class Library (TX-Version 9.1) causes a crash of Tx32.dll when the name of the Windows Standard Printer is very long.
This occurs typically with LAN-Printers and in a Windows-Terminal-Server (Citrix) environment.
Details:
- CTXView::OnCreate() calls SelectPrinter()
- SelectPrinter() creates a printer device string which is build in the form
"Devicename,Drivername,Output port"
The printer device string on a WTS for example looks like
"Client\P23027E0#\Kyocera FS-1750(KPDL2),winspool,Client\P23027E0#\Kyocera FS-1750(KPDL-2)"
- SelectPrinter() then calls SetDevicePrinter() with the printer device string as parameter
- SetDevicePrinter() calls SetDeviceHelper()
- SetDeviceHelper() sends the message TX_SETDEVICE to the TX-Control,
lParam contains the adress of the printer device string
If this string is longer than 79 chars, TX crashes with an access violation.
Is this an already known bug and more important, will this bug be fixed in one of the next service packs?
thanks in advance
Herbert
This message was originally posted by Herbert Roegner in the old TX Text Control Support Forum.
Using the C++ Class Library (TX-Version 9.1) causes a crash of Tx32.dll when the name of the Windows Standard Printer is very long.
This occurs typically with LAN-Printers and in a Windows-Terminal-Server (Citrix) environment.
Details:
- CTXView::OnCreate() calls SelectPrinter()
- SelectPrinter() creates a printer device string which is build in the form
"Devicename,Drivername,Output port"
The printer device string on a WTS for example looks like
"Client\P23027E0#\Kyocera FS-1750(KPDL2),winspool,Client\P23027E0#\Kyocera FS-1750(KPDL-2)"
- SelectPrinter() then calls SetDevicePrinter() with the printer device string as parameter
- SetDevicePrinter() calls SetDeviceHelper()
- SetDeviceHelper() sends the message TX_SETDEVICE to the TX-Control,
lParam contains the adress of the printer device string
If this string is longer than 79 chars, TX crashes with an access violation.
Is this an already known bug and more important, will this bug be fixed in one of the next service packs?
thanks in advance
Herbert
This message was originally posted by Herbert Roegner in the old TX Text Control Support Forum.