In order for this site to work correctly we need to store a small file (called a cookie) on your computer. Most every site in the world does this, however since the 25th of May 2011, by law we have to get your permission first. Please abandon the forum if you disagree.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
Print problem
-
Ingo Junge-Herrmann
- Mensajes: 339
- Registrado: Lun Jul 02, 2007 7:17 pm
Print problem
Hi,
after selecting the printer I'm converting the array with the print positions
from cm to pixels with the following code
WITH OBJECT Printer:oCanvas
:oFont:=oFont
:nMapMode:=mmHIMETRICS
ProcessMessages()
For nX:=1 TO LEN(aPos)
aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
ProcessMessages()
next
:nMapMode:=mmPIXELS
END WITH
aPos is STATIC
aPix is LOCAL
Sometimes - not always - I got the GPF as shown in the picture and the following
LogDebug lines
#1: HEAP[mwin.exe]:
#2: Heap block at 0019F0B0 modified at 0019F194 past requested size of dc
#3: HEAP[mwin.exe]:
#4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
#5: Heap corruption detected at 0019F1B0
#6: Heap corruption detected at 0019F1B0
#7: Heap corruption detected at 0019F1B0
#8: HEAP[mwin.exe]:
#9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
#10: Heap corruption detected at 0019F1B0
#11: HEAP[mwin.exe]:
#12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
#13: Heap corruption detected at 0019F1B0
#14: HEAP[mwin.exe]:
#15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
#16: Heap corruption detected at 0019F1B0
#17: HEAP[mwin.exe]:
#18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
#19: Heap corruption detected at 0019F1B0
#20: HEAP[mwin.exe]:
#21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
#22: Heap corruption detected at 0019F1B0
#23: HEAP[mwin.exe]:
#24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
#25: Heap corruption detected at 0019F1B0
#26: Heap corruption detected at 0019F1B0
#27: Heap corruption detected at 0019F1B0
#28: Heap corruption detected at 0019F1B0
#29: Heap corruption detected at 0019F1B0
#30: HEAP[mwin.exe]:
#31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
#32: Heap corruption detected at 0019F1B0
#33: HEAP[mwin.exe]:
#34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
#35: Heap corruption detected at 0019F1B0
#36: HEAP[mwin.exe]:
#37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
Any idea what's wrong with my code?
Thanks in advance
Ingo
--
Attached files error.zip (5.9 KB)Â
-
ignacio
- Site Admin
- Mensajes: 9253
- Registrado: Lun Abr 06, 2015 8:00 pm
- Ubicación: Madrid, Spain
- Contactar:
Print problem
Ingo,
I highly recommend to take off those ProcessMessages(), but I do not think
that are the cause of those LogDebug lines.
Be aware that the LogDebug() mechanism built in Xailer is just a connection
with the standart OutputDebugString() API function that is internally used
by a lot of software, and even Windows itself. In your case, I almost sure
that those lines are not generated by Xailer, but by a 'mwin.exe' program
that it seems to be malicous software.
http://www.bleepingcomputer.com/startup ... -7941.html
Best regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Hi,
>
> after selecting the printer I'm converting the array with the print
> positions
> from cm to pixels with the following code
>
> WITH OBJECT Printer:oCanvas
> :oFont:=oFont
> :nMapMode:=mmHIMETRICS
> ProcessMessages()
> For nX:=1 TO LEN(aPos)
>
> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
> ProcessMessages()
> next
> :nMapMode:=mmPIXELS
> END WITH
>
> aPos is STATIC
> aPix is LOCAL
> Sometimes - not always - I got the GPF as shown in the picture and the
> following
> LogDebug lines
>
> #1: HEAP[mwin.exe]:
> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size of dc
>
> #3: HEAP[mwin.exe]:
> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>
> #5: Heap corruption detected at 0019F1B0
>
> #6: Heap corruption detected at 0019F1B0
>
> #7: Heap corruption detected at 0019F1B0
>
> #8: HEAP[mwin.exe]:
> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #10: Heap corruption detected at 0019F1B0
>
> #11: HEAP[mwin.exe]:
> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #13: Heap corruption detected at 0019F1B0
>
> #14: HEAP[mwin.exe]:
> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #16: Heap corruption detected at 0019F1B0
>
> #17: HEAP[mwin.exe]:
> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #19: Heap corruption detected at 0019F1B0
>
> #20: HEAP[mwin.exe]:
> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #22: Heap corruption detected at 0019F1B0
>
> #23: HEAP[mwin.exe]:
> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #25: Heap corruption detected at 0019F1B0
>
> #26: Heap corruption detected at 0019F1B0
>
> #27: Heap corruption detected at 0019F1B0
>
> #28: Heap corruption detected at 0019F1B0
>
> #29: Heap corruption detected at 0019F1B0
>
> #30: HEAP[mwin.exe]:
> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #32: Heap corruption detected at 0019F1B0
>
> #33: HEAP[mwin.exe]:
> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #35: Heap corruption detected at 0019F1B0
>
> #36: HEAP[mwin.exe]:
> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> Any idea what's wrong with my code?
>
> Thanks in advance
>
> Ingo
I highly recommend to take off those ProcessMessages(), but I do not think
that are the cause of those LogDebug lines.
Be aware that the LogDebug() mechanism built in Xailer is just a connection
with the standart OutputDebugString() API function that is internally used
by a lot of software, and even Windows itself. In your case, I almost sure
that those lines are not generated by Xailer, but by a 'mwin.exe' program
that it seems to be malicous software.
http://www.bleepingcomputer.com/startup ... -7941.html
Best regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Hi,
>
> after selecting the printer I'm converting the array with the print
> positions
> from cm to pixels with the following code
>
> WITH OBJECT Printer:oCanvas
> :oFont:=oFont
> :nMapMode:=mmHIMETRICS
> ProcessMessages()
> For nX:=1 TO LEN(aPos)
>
> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
> ProcessMessages()
> next
> :nMapMode:=mmPIXELS
> END WITH
>
> aPos is STATIC
> aPix is LOCAL
> Sometimes - not always - I got the GPF as shown in the picture and the
> following
> LogDebug lines
>
> #1: HEAP[mwin.exe]:
> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size of dc
>
> #3: HEAP[mwin.exe]:
> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>
> #5: Heap corruption detected at 0019F1B0
>
> #6: Heap corruption detected at 0019F1B0
>
> #7: Heap corruption detected at 0019F1B0
>
> #8: HEAP[mwin.exe]:
> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #10: Heap corruption detected at 0019F1B0
>
> #11: HEAP[mwin.exe]:
> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #13: Heap corruption detected at 0019F1B0
>
> #14: HEAP[mwin.exe]:
> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #16: Heap corruption detected at 0019F1B0
>
> #17: HEAP[mwin.exe]:
> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #19: Heap corruption detected at 0019F1B0
>
> #20: HEAP[mwin.exe]:
> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #22: Heap corruption detected at 0019F1B0
>
> #23: HEAP[mwin.exe]:
> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #25: Heap corruption detected at 0019F1B0
>
> #26: Heap corruption detected at 0019F1B0
>
> #27: Heap corruption detected at 0019F1B0
>
> #28: Heap corruption detected at 0019F1B0
>
> #29: Heap corruption detected at 0019F1B0
>
> #30: HEAP[mwin.exe]:
> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #32: Heap corruption detected at 0019F1B0
>
> #33: HEAP[mwin.exe]:
> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #35: Heap corruption detected at 0019F1B0
>
> #36: HEAP[mwin.exe]:
> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> Any idea what's wrong with my code?
>
> Thanks in advance
>
> Ingo
Print problem
Ingo,
I highly recommend to take off those ProcessMessages(), but I do not think
that are the cause of those LogDebug lines.
Be aware that the LogDebug() mechanism built in Xailer is just a connection
with the standart OutputDebugString() API function that is internally used
by a lot of software, and even Windows itself. In your case, I almost sure
that those lines are not generated by Xailer, but by a 'mwin.exe' program
that it seems to be malicous software.
http://www.bleepingcomputer.com/startup ... -7941.html
Best regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Hi,
>
> after selecting the printer I'm converting the array with the print
> positions
> from cm to pixels with the following code
>
> WITH OBJECT Printer:oCanvas
> :oFont:=oFont
> :nMapMode:=mmHIMETRICS
> ProcessMessages()
> For nX:=1 TO LEN(aPos)
>
> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
> ProcessMessages()
> next
> :nMapMode:=mmPIXELS
> END WITH
>
> aPos is STATIC
> aPix is LOCAL
> Sometimes - not always - I got the GPF as shown in the picture and the
> following
> LogDebug lines
>
> #1: HEAP[mwin.exe]:
> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size of dc
>
> #3: HEAP[mwin.exe]:
> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>
> #5: Heap corruption detected at 0019F1B0
>
> #6: Heap corruption detected at 0019F1B0
>
> #7: Heap corruption detected at 0019F1B0
>
> #8: HEAP[mwin.exe]:
> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #10: Heap corruption detected at 0019F1B0
>
> #11: HEAP[mwin.exe]:
> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #13: Heap corruption detected at 0019F1B0
>
> #14: HEAP[mwin.exe]:
> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #16: Heap corruption detected at 0019F1B0
>
> #17: HEAP[mwin.exe]:
> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #19: Heap corruption detected at 0019F1B0
>
> #20: HEAP[mwin.exe]:
> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #22: Heap corruption detected at 0019F1B0
>
> #23: HEAP[mwin.exe]:
> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #25: Heap corruption detected at 0019F1B0
>
> #26: Heap corruption detected at 0019F1B0
>
> #27: Heap corruption detected at 0019F1B0
>
> #28: Heap corruption detected at 0019F1B0
>
> #29: Heap corruption detected at 0019F1B0
>
> #30: HEAP[mwin.exe]:
> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #32: Heap corruption detected at 0019F1B0
>
> #33: HEAP[mwin.exe]:
> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #35: Heap corruption detected at 0019F1B0
>
> #36: HEAP[mwin.exe]:
> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> Any idea what's wrong with my code?
>
> Thanks in advance
>
> Ingo
I highly recommend to take off those ProcessMessages(), but I do not think
that are the cause of those LogDebug lines.
Be aware that the LogDebug() mechanism built in Xailer is just a connection
with the standart OutputDebugString() API function that is internally used
by a lot of software, and even Windows itself. In your case, I almost sure
that those lines are not generated by Xailer, but by a 'mwin.exe' program
that it seems to be malicous software.
http://www.bleepingcomputer.com/startup ... -7941.html
Best regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Hi,
>
> after selecting the printer I'm converting the array with the print
> positions
> from cm to pixels with the following code
>
> WITH OBJECT Printer:oCanvas
> :oFont:=oFont
> :nMapMode:=mmHIMETRICS
> ProcessMessages()
> For nX:=1 TO LEN(aPos)
>
> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
> ProcessMessages()
> next
> :nMapMode:=mmPIXELS
> END WITH
>
> aPos is STATIC
> aPix is LOCAL
> Sometimes - not always - I got the GPF as shown in the picture and the
> following
> LogDebug lines
>
> #1: HEAP[mwin.exe]:
> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size of dc
>
> #3: HEAP[mwin.exe]:
> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>
> #5: Heap corruption detected at 0019F1B0
>
> #6: Heap corruption detected at 0019F1B0
>
> #7: Heap corruption detected at 0019F1B0
>
> #8: HEAP[mwin.exe]:
> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #10: Heap corruption detected at 0019F1B0
>
> #11: HEAP[mwin.exe]:
> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #13: Heap corruption detected at 0019F1B0
>
> #14: HEAP[mwin.exe]:
> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #16: Heap corruption detected at 0019F1B0
>
> #17: HEAP[mwin.exe]:
> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #19: Heap corruption detected at 0019F1B0
>
> #20: HEAP[mwin.exe]:
> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #22: Heap corruption detected at 0019F1B0
>
> #23: HEAP[mwin.exe]:
> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #25: Heap corruption detected at 0019F1B0
>
> #26: Heap corruption detected at 0019F1B0
>
> #27: Heap corruption detected at 0019F1B0
>
> #28: Heap corruption detected at 0019F1B0
>
> #29: Heap corruption detected at 0019F1B0
>
> #30: HEAP[mwin.exe]:
> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #32: Heap corruption detected at 0019F1B0
>
> #33: HEAP[mwin.exe]:
> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> #35: Heap corruption detected at 0019F1B0
>
> #36: HEAP[mwin.exe]:
> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>
> Any idea what's wrong with my code?
>
> Thanks in advance
>
> Ingo
-
Ingo Junge-Herrmann
- Mensajes: 339
- Registrado: Lun Jul 02, 2007 7:17 pm
Print problem
Ignacio,
the lines with ProcessMessages() are one try to workaround. I deleted them.
Mwin.exe is the project I'm building with Xailer and it was running from
the IDE when the error occured. It is not a 'malicious' software. It is the
16-bit software I'm trying to convert from FW16 to 32 bit by Xailer. Till
now I have more problems with the bugs in Xailer than with transfering my
sourcecode.
The error must be caused in the line of converting cm to pixel and as I found
out now it occurs if Canon Pixma iP 4000 is selected. The difficulty is
that it happens not every time.
I had hoped the problem is known by otherones but nevertheless thanks for
answering.
Ingo
"Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>Ingo,
>
>I highly recommend to take off those ProcessMessages(), but I do not think
>that are the cause of those LogDebug lines.
>
>Be aware that the LogDebug() mechanism built in Xailer is just a connection
>with the standart OutputDebugString() API function that is internally used
>by a lot of software, and even Windows itself. In your case, I almost sure
>that those lines are not generated by Xailer, but by a 'mwin.exe' program
>that it seems to be malicous software.
>
>http://www.bleepingcomputer.com/startup ... -7941.html
>
>Best regards,
>
>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>
>> Hi,
>>
>> after selecting the printer I'm converting the array with the print
>> positions
>> from cm to pixels with the following code
>>
>> WITH OBJECT Printer:oCanvas
>> :oFont:=oFont
>> :nMapMode:=mmHIMETRICS
>> ProcessMessages()
>> For nX:=1 TO LEN(aPos)
>>
>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>> ProcessMessages()
>> next
>> :nMapMode:=mmPIXELS
>> END WITH
>>
>> aPos is STATIC
>> aPix is LOCAL
>> Sometimes - not always - I got the GPF as shown in the picture and the
>> following
>> LogDebug lines
>>
>> #1: HEAP[mwin.exe]:
>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size of
dc
>>
>> #3: HEAP[mwin.exe]:
>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>
>> #5: Heap corruption detected at 0019F1B0
>>
>> #6: Heap corruption detected at 0019F1B0
>>
>> #7: Heap corruption detected at 0019F1B0
>>
>> #8: HEAP[mwin.exe]:
>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #10: Heap corruption detected at 0019F1B0
>>
>> #11: HEAP[mwin.exe]:
>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #13: Heap corruption detected at 0019F1B0
>>
>> #14: HEAP[mwin.exe]:
>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #16: Heap corruption detected at 0019F1B0
>>
>> #17: HEAP[mwin.exe]:
>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #19: Heap corruption detected at 0019F1B0
>>
>> #20: HEAP[mwin.exe]:
>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #22: Heap corruption detected at 0019F1B0
>>
>> #23: HEAP[mwin.exe]:
>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #25: Heap corruption detected at 0019F1B0
>>
>> #26: Heap corruption detected at 0019F1B0
>>
>> #27: Heap corruption detected at 0019F1B0
>>
>> #28: Heap corruption detected at 0019F1B0
>>
>> #29: Heap corruption detected at 0019F1B0
>>
>> #30: HEAP[mwin.exe]:
>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #32: Heap corruption detected at 0019F1B0
>>
>> #33: HEAP[mwin.exe]:
>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #35: Heap corruption detected at 0019F1B0
>>
>> #36: HEAP[mwin.exe]:
>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> Any idea what's wrong with my code?
>>
>> Thanks in advance
>>
>> Ingo
>
>
the lines with ProcessMessages() are one try to workaround. I deleted them.
Mwin.exe is the project I'm building with Xailer and it was running from
the IDE when the error occured. It is not a 'malicious' software. It is the
16-bit software I'm trying to convert from FW16 to 32 bit by Xailer. Till
now I have more problems with the bugs in Xailer than with transfering my
sourcecode.
The error must be caused in the line of converting cm to pixel and as I found
out now it occurs if Canon Pixma iP 4000 is selected. The difficulty is
that it happens not every time.
I had hoped the problem is known by otherones but nevertheless thanks for
answering.
Ingo
"Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>Ingo,
>
>I highly recommend to take off those ProcessMessages(), but I do not think
>that are the cause of those LogDebug lines.
>
>Be aware that the LogDebug() mechanism built in Xailer is just a connection
>with the standart OutputDebugString() API function that is internally used
>by a lot of software, and even Windows itself. In your case, I almost sure
>that those lines are not generated by Xailer, but by a 'mwin.exe' program
>that it seems to be malicous software.
>
>http://www.bleepingcomputer.com/startup ... -7941.html
>
>Best regards,
>
>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>
>> Hi,
>>
>> after selecting the printer I'm converting the array with the print
>> positions
>> from cm to pixels with the following code
>>
>> WITH OBJECT Printer:oCanvas
>> :oFont:=oFont
>> :nMapMode:=mmHIMETRICS
>> ProcessMessages()
>> For nX:=1 TO LEN(aPos)
>>
>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>> ProcessMessages()
>> next
>> :nMapMode:=mmPIXELS
>> END WITH
>>
>> aPos is STATIC
>> aPix is LOCAL
>> Sometimes - not always - I got the GPF as shown in the picture and the
>> following
>> LogDebug lines
>>
>> #1: HEAP[mwin.exe]:
>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size of
dc
>>
>> #3: HEAP[mwin.exe]:
>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>
>> #5: Heap corruption detected at 0019F1B0
>>
>> #6: Heap corruption detected at 0019F1B0
>>
>> #7: Heap corruption detected at 0019F1B0
>>
>> #8: HEAP[mwin.exe]:
>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #10: Heap corruption detected at 0019F1B0
>>
>> #11: HEAP[mwin.exe]:
>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #13: Heap corruption detected at 0019F1B0
>>
>> #14: HEAP[mwin.exe]:
>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #16: Heap corruption detected at 0019F1B0
>>
>> #17: HEAP[mwin.exe]:
>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #19: Heap corruption detected at 0019F1B0
>>
>> #20: HEAP[mwin.exe]:
>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #22: Heap corruption detected at 0019F1B0
>>
>> #23: HEAP[mwin.exe]:
>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #25: Heap corruption detected at 0019F1B0
>>
>> #26: Heap corruption detected at 0019F1B0
>>
>> #27: Heap corruption detected at 0019F1B0
>>
>> #28: Heap corruption detected at 0019F1B0
>>
>> #29: Heap corruption detected at 0019F1B0
>>
>> #30: HEAP[mwin.exe]:
>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #32: Heap corruption detected at 0019F1B0
>>
>> #33: HEAP[mwin.exe]:
>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #35: Heap corruption detected at 0019F1B0
>>
>> #36: HEAP[mwin.exe]:
>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> Any idea what's wrong with my code?
>>
>> Thanks in advance
>>
>> Ingo
>
>
-
Ingo Junge-Herrmann
- Mensajes: 339
- Registrado: Lun Jul 02, 2007 7:17 pm
Print problem
Ignacio,
the lines with ProcessMessages() are one try to workaround. I deleted them.
Mwin.exe is the project I'm building with Xailer and it was running from
the IDE when the error occured. It is not a 'malicious' software. It is the
16-bit software I'm trying to convert from FW16 to 32 bit by Xailer. Till
now I have more problems with the bugs in Xailer than with transfering my
sourcecode.
The error must be caused in the line of converting cm to pixel and as I found
out now it occurs if Canon Pixma iP 4000 is selected. The difficulty is
that it happens not every time.
I had hoped the problem is known by otherones but nevertheless thanks for
answering.
Ingo
"Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>Ingo,
>
>I highly recommend to take off those ProcessMessages(), but I do not think
>that are the cause of those LogDebug lines.
>
>Be aware that the LogDebug() mechanism built in Xailer is just a connection
>with the standart OutputDebugString() API function that is internally used
>by a lot of software, and even Windows itself. In your case, I almost sure
>that those lines are not generated by Xailer, but by a 'mwin.exe' program
>that it seems to be malicous software.
>
>http://www.bleepingcomputer.com/startup ... -7941.html
>
>Best regards,
>
>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>
>> Hi,
>>
>> after selecting the printer I'm converting the array with the print
>> positions
>> from cm to pixels with the following code
>>
>> WITH OBJECT Printer:oCanvas
>> :oFont:=oFont
>> :nMapMode:=mmHIMETRICS
>> ProcessMessages()
>> For nX:=1 TO LEN(aPos)
>>
>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>> ProcessMessages()
>> next
>> :nMapMode:=mmPIXELS
>> END WITH
>>
>> aPos is STATIC
>> aPix is LOCAL
>> Sometimes - not always - I got the GPF as shown in the picture and the
>> following
>> LogDebug lines
>>
>> #1: HEAP[mwin.exe]:
>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size of
dc
>>
>> #3: HEAP[mwin.exe]:
>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>
>> #5: Heap corruption detected at 0019F1B0
>>
>> #6: Heap corruption detected at 0019F1B0
>>
>> #7: Heap corruption detected at 0019F1B0
>>
>> #8: HEAP[mwin.exe]:
>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #10: Heap corruption detected at 0019F1B0
>>
>> #11: HEAP[mwin.exe]:
>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #13: Heap corruption detected at 0019F1B0
>>
>> #14: HEAP[mwin.exe]:
>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #16: Heap corruption detected at 0019F1B0
>>
>> #17: HEAP[mwin.exe]:
>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #19: Heap corruption detected at 0019F1B0
>>
>> #20: HEAP[mwin.exe]:
>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #22: Heap corruption detected at 0019F1B0
>>
>> #23: HEAP[mwin.exe]:
>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #25: Heap corruption detected at 0019F1B0
>>
>> #26: Heap corruption detected at 0019F1B0
>>
>> #27: Heap corruption detected at 0019F1B0
>>
>> #28: Heap corruption detected at 0019F1B0
>>
>> #29: Heap corruption detected at 0019F1B0
>>
>> #30: HEAP[mwin.exe]:
>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #32: Heap corruption detected at 0019F1B0
>>
>> #33: HEAP[mwin.exe]:
>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #35: Heap corruption detected at 0019F1B0
>>
>> #36: HEAP[mwin.exe]:
>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> Any idea what's wrong with my code?
>>
>> Thanks in advance
>>
>> Ingo
>
>
the lines with ProcessMessages() are one try to workaround. I deleted them.
Mwin.exe is the project I'm building with Xailer and it was running from
the IDE when the error occured. It is not a 'malicious' software. It is the
16-bit software I'm trying to convert from FW16 to 32 bit by Xailer. Till
now I have more problems with the bugs in Xailer than with transfering my
sourcecode.
The error must be caused in the line of converting cm to pixel and as I found
out now it occurs if Canon Pixma iP 4000 is selected. The difficulty is
that it happens not every time.
I had hoped the problem is known by otherones but nevertheless thanks for
answering.
Ingo
"Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>Ingo,
>
>I highly recommend to take off those ProcessMessages(), but I do not think
>that are the cause of those LogDebug lines.
>
>Be aware that the LogDebug() mechanism built in Xailer is just a connection
>with the standart OutputDebugString() API function that is internally used
>by a lot of software, and even Windows itself. In your case, I almost sure
>that those lines are not generated by Xailer, but by a 'mwin.exe' program
>that it seems to be malicous software.
>
>http://www.bleepingcomputer.com/startup ... -7941.html
>
>Best regards,
>
>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>
>> Hi,
>>
>> after selecting the printer I'm converting the array with the print
>> positions
>> from cm to pixels with the following code
>>
>> WITH OBJECT Printer:oCanvas
>> :oFont:=oFont
>> :nMapMode:=mmHIMETRICS
>> ProcessMessages()
>> For nX:=1 TO LEN(aPos)
>>
>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>> ProcessMessages()
>> next
>> :nMapMode:=mmPIXELS
>> END WITH
>>
>> aPos is STATIC
>> aPix is LOCAL
>> Sometimes - not always - I got the GPF as shown in the picture and the
>> following
>> LogDebug lines
>>
>> #1: HEAP[mwin.exe]:
>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size of
dc
>>
>> #3: HEAP[mwin.exe]:
>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>
>> #5: Heap corruption detected at 0019F1B0
>>
>> #6: Heap corruption detected at 0019F1B0
>>
>> #7: Heap corruption detected at 0019F1B0
>>
>> #8: HEAP[mwin.exe]:
>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #10: Heap corruption detected at 0019F1B0
>>
>> #11: HEAP[mwin.exe]:
>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #13: Heap corruption detected at 0019F1B0
>>
>> #14: HEAP[mwin.exe]:
>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #16: Heap corruption detected at 0019F1B0
>>
>> #17: HEAP[mwin.exe]:
>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #19: Heap corruption detected at 0019F1B0
>>
>> #20: HEAP[mwin.exe]:
>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #22: Heap corruption detected at 0019F1B0
>>
>> #23: HEAP[mwin.exe]:
>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #25: Heap corruption detected at 0019F1B0
>>
>> #26: Heap corruption detected at 0019F1B0
>>
>> #27: Heap corruption detected at 0019F1B0
>>
>> #28: Heap corruption detected at 0019F1B0
>>
>> #29: Heap corruption detected at 0019F1B0
>>
>> #30: HEAP[mwin.exe]:
>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #32: Heap corruption detected at 0019F1B0
>>
>> #33: HEAP[mwin.exe]:
>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> #35: Heap corruption detected at 0019F1B0
>>
>> #36: HEAP[mwin.exe]:
>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>
>> Any idea what's wrong with my code?
>>
>> Thanks in advance
>>
>> Ingo
>
>
-
ignacio
- Site Admin
- Mensajes: 9253
- Registrado: Lun Abr 06, 2015 8:00 pm
- Ubicación: Madrid, Spain
- Contactar:
Print problem
Ingo,
> now I have more problems with the bugs in Xailer than with transfering my
> sourcecode.
Please, would you mind to give a list of those bugs. I will highly
appreciate your feedback. We know that moving to a new developing
environment is not easy, but please be patient and give your self the time
to learn Xailer
> The error must be caused in the line of converting cm to pixel and as I
> found
> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty is
> that it happens not every time.
I guess you are wrong, the routine for converting cm to pixels DOES NOT
CALL ABSOLUTELY any API function, IS JUST A BUNCH OF ARITHMETICAL
CALCULATIONS. So I guess the problem is not there. BTW, if you are able to
reproduce your bug on a simply application we will be glad to do some
research.
Regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:440d647a$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> the lines with ProcessMessages() are one try to workaround. I deleted
> them.
> Mwin.exe is the project I'm building with Xailer and it was running from
> the IDE when the error occured. It is not a 'malicious' software. It is
> the
> 16-bit software I'm trying to convert from FW16 to 32 bit by Xailer. Till
> now I have more problems with the bugs in Xailer than with transfering my
> sourcecode.
>
> The error must be caused in the line of converting cm to pixel and as I
> found
> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty is
> that it happens not every time.
>
> I had hoped the problem is known by otherones but nevertheless thanks for
> answering.
>
> Ingo
>
> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>Ingo,
>>
>>I highly recommend to take off those ProcessMessages(), but I do not think
>
>>that are the cause of those LogDebug lines.
>>
>>Be aware that the LogDebug() mechanism built in Xailer is just a
>>connection
>
>>with the standart OutputDebugString() API function that is internally used
>
>>by a lot of software, and even Windows itself. In your case, I almost sure
>
>>that those lines are not generated by Xailer, but by a 'mwin.exe' program
>
>>that it seems to be malicous software.
>>
>>http://www.bleepingcomputer.com/startup ... -7941.html
>>
>>Best regards,
>>
>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>
>>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>
>>> Hi,
>>>
>>> after selecting the printer I'm converting the array with the print
>>> positions
>>> from cm to pixels with the following code
>>>
>>> WITH OBJECT Printer:oCanvas
>>> :oFont:=oFont
>>> :nMapMode:=mmHIMETRICS
>>> ProcessMessages()
>>> For nX:=1 TO LEN(aPos)
>>>
>>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>>> ProcessMessages()
>>> next
>>> :nMapMode:=mmPIXELS
>>> END WITH
>>>
>>> aPos is STATIC
>>> aPix is LOCAL
>>> Sometimes - not always - I got the GPF as shown in the picture and the
>
>>> following
>>> LogDebug lines
>>>
>>> #1: HEAP[mwin.exe]:
>>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size of
> dc
>>>
>>> #3: HEAP[mwin.exe]:
>>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>>
>>> #5: Heap corruption detected at 0019F1B0
>>>
>>> #6: Heap corruption detected at 0019F1B0
>>>
>>> #7: Heap corruption detected at 0019F1B0
>>>
>>> #8: HEAP[mwin.exe]:
>>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #10: Heap corruption detected at 0019F1B0
>>>
>>> #11: HEAP[mwin.exe]:
>>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #13: Heap corruption detected at 0019F1B0
>>>
>>> #14: HEAP[mwin.exe]:
>>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #16: Heap corruption detected at 0019F1B0
>>>
>>> #17: HEAP[mwin.exe]:
>>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #19: Heap corruption detected at 0019F1B0
>>>
>>> #20: HEAP[mwin.exe]:
>>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #22: Heap corruption detected at 0019F1B0
>>>
>>> #23: HEAP[mwin.exe]:
>>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #25: Heap corruption detected at 0019F1B0
>>>
>>> #26: Heap corruption detected at 0019F1B0
>>>
>>> #27: Heap corruption detected at 0019F1B0
>>>
>>> #28: Heap corruption detected at 0019F1B0
>>>
>>> #29: Heap corruption detected at 0019F1B0
>>>
>>> #30: HEAP[mwin.exe]:
>>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #32: Heap corruption detected at 0019F1B0
>>>
>>> #33: HEAP[mwin.exe]:
>>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #35: Heap corruption detected at 0019F1B0
>>>
>>> #36: HEAP[mwin.exe]:
>>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> Any idea what's wrong with my code?
>>>
>>> Thanks in advance
>>>
>>> Ingo
>>
>>
>
> now I have more problems with the bugs in Xailer than with transfering my
> sourcecode.
Please, would you mind to give a list of those bugs. I will highly
appreciate your feedback. We know that moving to a new developing
environment is not easy, but please be patient and give your self the time
to learn Xailer
> The error must be caused in the line of converting cm to pixel and as I
> found
> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty is
> that it happens not every time.
I guess you are wrong, the routine for converting cm to pixels DOES NOT
CALL ABSOLUTELY any API function, IS JUST A BUNCH OF ARITHMETICAL
CALCULATIONS. So I guess the problem is not there. BTW, if you are able to
reproduce your bug on a simply application we will be glad to do some
research.
Regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:440d647a$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> the lines with ProcessMessages() are one try to workaround. I deleted
> them.
> Mwin.exe is the project I'm building with Xailer and it was running from
> the IDE when the error occured. It is not a 'malicious' software. It is
> the
> 16-bit software I'm trying to convert from FW16 to 32 bit by Xailer. Till
> now I have more problems with the bugs in Xailer than with transfering my
> sourcecode.
>
> The error must be caused in the line of converting cm to pixel and as I
> found
> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty is
> that it happens not every time.
>
> I had hoped the problem is known by otherones but nevertheless thanks for
> answering.
>
> Ingo
>
> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>Ingo,
>>
>>I highly recommend to take off those ProcessMessages(), but I do not think
>
>>that are the cause of those LogDebug lines.
>>
>>Be aware that the LogDebug() mechanism built in Xailer is just a
>>connection
>
>>with the standart OutputDebugString() API function that is internally used
>
>>by a lot of software, and even Windows itself. In your case, I almost sure
>
>>that those lines are not generated by Xailer, but by a 'mwin.exe' program
>
>>that it seems to be malicous software.
>>
>>http://www.bleepingcomputer.com/startup ... -7941.html
>>
>>Best regards,
>>
>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>
>>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>
>>> Hi,
>>>
>>> after selecting the printer I'm converting the array with the print
>>> positions
>>> from cm to pixels with the following code
>>>
>>> WITH OBJECT Printer:oCanvas
>>> :oFont:=oFont
>>> :nMapMode:=mmHIMETRICS
>>> ProcessMessages()
>>> For nX:=1 TO LEN(aPos)
>>>
>>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>>> ProcessMessages()
>>> next
>>> :nMapMode:=mmPIXELS
>>> END WITH
>>>
>>> aPos is STATIC
>>> aPix is LOCAL
>>> Sometimes - not always - I got the GPF as shown in the picture and the
>
>>> following
>>> LogDebug lines
>>>
>>> #1: HEAP[mwin.exe]:
>>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size of
> dc
>>>
>>> #3: HEAP[mwin.exe]:
>>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>>
>>> #5: Heap corruption detected at 0019F1B0
>>>
>>> #6: Heap corruption detected at 0019F1B0
>>>
>>> #7: Heap corruption detected at 0019F1B0
>>>
>>> #8: HEAP[mwin.exe]:
>>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #10: Heap corruption detected at 0019F1B0
>>>
>>> #11: HEAP[mwin.exe]:
>>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #13: Heap corruption detected at 0019F1B0
>>>
>>> #14: HEAP[mwin.exe]:
>>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #16: Heap corruption detected at 0019F1B0
>>>
>>> #17: HEAP[mwin.exe]:
>>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #19: Heap corruption detected at 0019F1B0
>>>
>>> #20: HEAP[mwin.exe]:
>>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #22: Heap corruption detected at 0019F1B0
>>>
>>> #23: HEAP[mwin.exe]:
>>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #25: Heap corruption detected at 0019F1B0
>>>
>>> #26: Heap corruption detected at 0019F1B0
>>>
>>> #27: Heap corruption detected at 0019F1B0
>>>
>>> #28: Heap corruption detected at 0019F1B0
>>>
>>> #29: Heap corruption detected at 0019F1B0
>>>
>>> #30: HEAP[mwin.exe]:
>>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #32: Heap corruption detected at 0019F1B0
>>>
>>> #33: HEAP[mwin.exe]:
>>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #35: Heap corruption detected at 0019F1B0
>>>
>>> #36: HEAP[mwin.exe]:
>>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> Any idea what's wrong with my code?
>>>
>>> Thanks in advance
>>>
>>> Ingo
>>
>>
>
Print problem
Ingo,
> now I have more problems with the bugs in Xailer than with transfering my
> sourcecode.
Please, would you mind to give a list of those bugs. I will highly
appreciate your feedback. We know that moving to a new developing
environment is not easy, but please be patient and give your self the time
to learn Xailer
> The error must be caused in the line of converting cm to pixel and as I
> found
> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty is
> that it happens not every time.
I guess you are wrong, the routine for converting cm to pixels DOES NOT
CALL ABSOLUTELY any API function, IS JUST A BUNCH OF ARITHMETICAL
CALCULATIONS. So I guess the problem is not there. BTW, if you are able to
reproduce your bug on a simply application we will be glad to do some
research.
Regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:440d647a$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> the lines with ProcessMessages() are one try to workaround. I deleted
> them.
> Mwin.exe is the project I'm building with Xailer and it was running from
> the IDE when the error occured. It is not a 'malicious' software. It is
> the
> 16-bit software I'm trying to convert from FW16 to 32 bit by Xailer. Till
> now I have more problems with the bugs in Xailer than with transfering my
> sourcecode.
>
> The error must be caused in the line of converting cm to pixel and as I
> found
> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty is
> that it happens not every time.
>
> I had hoped the problem is known by otherones but nevertheless thanks for
> answering.
>
> Ingo
>
> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>Ingo,
>>
>>I highly recommend to take off those ProcessMessages(), but I do not think
>
>>that are the cause of those LogDebug lines.
>>
>>Be aware that the LogDebug() mechanism built in Xailer is just a
>>connection
>
>>with the standart OutputDebugString() API function that is internally used
>
>>by a lot of software, and even Windows itself. In your case, I almost sure
>
>>that those lines are not generated by Xailer, but by a 'mwin.exe' program
>
>>that it seems to be malicous software.
>>
>>http://www.bleepingcomputer.com/startup ... -7941.html
>>
>>Best regards,
>>
>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>
>>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>
>>> Hi,
>>>
>>> after selecting the printer I'm converting the array with the print
>>> positions
>>> from cm to pixels with the following code
>>>
>>> WITH OBJECT Printer:oCanvas
>>> :oFont:=oFont
>>> :nMapMode:=mmHIMETRICS
>>> ProcessMessages()
>>> For nX:=1 TO LEN(aPos)
>>>
>>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>>> ProcessMessages()
>>> next
>>> :nMapMode:=mmPIXELS
>>> END WITH
>>>
>>> aPos is STATIC
>>> aPix is LOCAL
>>> Sometimes - not always - I got the GPF as shown in the picture and the
>
>>> following
>>> LogDebug lines
>>>
>>> #1: HEAP[mwin.exe]:
>>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size of
> dc
>>>
>>> #3: HEAP[mwin.exe]:
>>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>>
>>> #5: Heap corruption detected at 0019F1B0
>>>
>>> #6: Heap corruption detected at 0019F1B0
>>>
>>> #7: Heap corruption detected at 0019F1B0
>>>
>>> #8: HEAP[mwin.exe]:
>>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #10: Heap corruption detected at 0019F1B0
>>>
>>> #11: HEAP[mwin.exe]:
>>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #13: Heap corruption detected at 0019F1B0
>>>
>>> #14: HEAP[mwin.exe]:
>>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #16: Heap corruption detected at 0019F1B0
>>>
>>> #17: HEAP[mwin.exe]:
>>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #19: Heap corruption detected at 0019F1B0
>>>
>>> #20: HEAP[mwin.exe]:
>>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #22: Heap corruption detected at 0019F1B0
>>>
>>> #23: HEAP[mwin.exe]:
>>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #25: Heap corruption detected at 0019F1B0
>>>
>>> #26: Heap corruption detected at 0019F1B0
>>>
>>> #27: Heap corruption detected at 0019F1B0
>>>
>>> #28: Heap corruption detected at 0019F1B0
>>>
>>> #29: Heap corruption detected at 0019F1B0
>>>
>>> #30: HEAP[mwin.exe]:
>>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #32: Heap corruption detected at 0019F1B0
>>>
>>> #33: HEAP[mwin.exe]:
>>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #35: Heap corruption detected at 0019F1B0
>>>
>>> #36: HEAP[mwin.exe]:
>>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> Any idea what's wrong with my code?
>>>
>>> Thanks in advance
>>>
>>> Ingo
>>
>>
>
> now I have more problems with the bugs in Xailer than with transfering my
> sourcecode.
Please, would you mind to give a list of those bugs. I will highly
appreciate your feedback. We know that moving to a new developing
environment is not easy, but please be patient and give your self the time
to learn Xailer
> The error must be caused in the line of converting cm to pixel and as I
> found
> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty is
> that it happens not every time.
I guess you are wrong, the routine for converting cm to pixels DOES NOT
CALL ABSOLUTELY any API function, IS JUST A BUNCH OF ARITHMETICAL
CALCULATIONS. So I guess the problem is not there. BTW, if you are able to
reproduce your bug on a simply application we will be glad to do some
research.
Regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:440d647a$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> the lines with ProcessMessages() are one try to workaround. I deleted
> them.
> Mwin.exe is the project I'm building with Xailer and it was running from
> the IDE when the error occured. It is not a 'malicious' software. It is
> the
> 16-bit software I'm trying to convert from FW16 to 32 bit by Xailer. Till
> now I have more problems with the bugs in Xailer than with transfering my
> sourcecode.
>
> The error must be caused in the line of converting cm to pixel and as I
> found
> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty is
> that it happens not every time.
>
> I had hoped the problem is known by otherones but nevertheless thanks for
> answering.
>
> Ingo
>
> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>Ingo,
>>
>>I highly recommend to take off those ProcessMessages(), but I do not think
>
>>that are the cause of those LogDebug lines.
>>
>>Be aware that the LogDebug() mechanism built in Xailer is just a
>>connection
>
>>with the standart OutputDebugString() API function that is internally used
>
>>by a lot of software, and even Windows itself. In your case, I almost sure
>
>>that those lines are not generated by Xailer, but by a 'mwin.exe' program
>
>>that it seems to be malicous software.
>>
>>http://www.bleepingcomputer.com/startup ... -7941.html
>>
>>Best regards,
>>
>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>
>>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>
>>> Hi,
>>>
>>> after selecting the printer I'm converting the array with the print
>>> positions
>>> from cm to pixels with the following code
>>>
>>> WITH OBJECT Printer:oCanvas
>>> :oFont:=oFont
>>> :nMapMode:=mmHIMETRICS
>>> ProcessMessages()
>>> For nX:=1 TO LEN(aPos)
>>>
>>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>>> ProcessMessages()
>>> next
>>> :nMapMode:=mmPIXELS
>>> END WITH
>>>
>>> aPos is STATIC
>>> aPix is LOCAL
>>> Sometimes - not always - I got the GPF as shown in the picture and the
>
>>> following
>>> LogDebug lines
>>>
>>> #1: HEAP[mwin.exe]:
>>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size of
> dc
>>>
>>> #3: HEAP[mwin.exe]:
>>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>>
>>> #5: Heap corruption detected at 0019F1B0
>>>
>>> #6: Heap corruption detected at 0019F1B0
>>>
>>> #7: Heap corruption detected at 0019F1B0
>>>
>>> #8: HEAP[mwin.exe]:
>>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #10: Heap corruption detected at 0019F1B0
>>>
>>> #11: HEAP[mwin.exe]:
>>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #13: Heap corruption detected at 0019F1B0
>>>
>>> #14: HEAP[mwin.exe]:
>>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #16: Heap corruption detected at 0019F1B0
>>>
>>> #17: HEAP[mwin.exe]:
>>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #19: Heap corruption detected at 0019F1B0
>>>
>>> #20: HEAP[mwin.exe]:
>>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #22: Heap corruption detected at 0019F1B0
>>>
>>> #23: HEAP[mwin.exe]:
>>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #25: Heap corruption detected at 0019F1B0
>>>
>>> #26: Heap corruption detected at 0019F1B0
>>>
>>> #27: Heap corruption detected at 0019F1B0
>>>
>>> #28: Heap corruption detected at 0019F1B0
>>>
>>> #29: Heap corruption detected at 0019F1B0
>>>
>>> #30: HEAP[mwin.exe]:
>>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #32: Heap corruption detected at 0019F1B0
>>>
>>> #33: HEAP[mwin.exe]:
>>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> #35: Heap corruption detected at 0019F1B0
>>>
>>> #36: HEAP[mwin.exe]:
>>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>
>>> Any idea what's wrong with my code?
>>>
>>> Thanks in advance
>>>
>>> Ingo
>>
>>
>
-
Ingo Junge-Herrmann
- Mensajes: 339
- Registrado: Lun Jul 02, 2007 7:17 pm
Print problem
Ignacio,
you're asking for a list of the bugs I found?
I informed you about them here and in the public ng. Remember sometimes I
had to write again and again to convince you that there was a bug in Xailer
and not a mistake by myself.
I decided me on Xailer because I'm still the meaning that it is the best
developing environment for all the xBase-developers especially the one coming
from FiveWin. But beside the time I need to learn the new dev.-environment
I must spend much time to find out if it is a bug in Xailer or a bug in my
code when something was going wrong here even though it is working in the
16-bit application.
If you really want a list of the bugs please take a look at this ng
- AnsiToOem()
- Preview
- TReport
- TLabel
- Xailer.res
- TIni:GetSection
- TDbfDataSet
- TDBBrowse
for example, but I hope it was only a rhetoric question of you.
The printer problem I could only locate in the line of the conversion call.
Sorry, without the sourcecode of Xailer I can not see how the mm to pixel
conversion works. I can only tell you what happened. Maybe I can separate
this part of my application when I finished it but now I have a lot of work
in front of me.
I'm yearning for the new (and fixed) release maybe it will be looking better.
Regards
Ingo
"Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>Ingo,
>
>> now I have more problems with the bugs in Xailer than with transfering
my
>> sourcecode.
>
>Please, would you mind to give a list of those bugs. I will highly
>appreciate your feedback. We know that moving to a new developing
>environment is not easy, but please be patient and give your self the time
>to learn Xailer
>
>> The error must be caused in the line of converting cm to pixel and as
I
>> found
>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
is
>> that it happens not every time.
>
>I guess you are wrong, the routine for converting cm to pixels DOES NOT
>CALL ABSOLUTELY any API function, IS JUST A BUNCH OF ARITHMETICAL
>CALCULATIONS. So I guess the problem is not there. BTW, if you are able
to
>reproduce your bug on a simply application we will be glad to do some
>research.
>
>Regards,
>
>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>news:440d647a$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>
>> Ignacio,
>>
>> the lines with ProcessMessages() are one try to workaround. I deleted
>> them.
>> Mwin.exe is the project I'm building with Xailer and it was running from
>> the IDE when the error occured. It is not a 'malicious' software. It is
>> the
>> 16-bit software I'm trying to convert from FW16 to 32 bit by Xailer. Till
>> now I have more problems with the bugs in Xailer than with transfering
my
>> sourcecode.
>>
>> The error must be caused in the line of converting cm to pixel and as
I
>> found
>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
is
>> that it happens not every time.
>>
>> I had hoped the problem is known by otherones but nevertheless thanks
for
>> answering.
>>
>> Ingo
>>
>> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>>Ingo,
>>>
>>>I highly recommend to take off those ProcessMessages(), but I do not think
>>
>>>that are the cause of those LogDebug lines.
>>>
>>>Be aware that the LogDebug() mechanism built in Xailer is just a
>>>connection
>>
>>>with the standart OutputDebugString() API function that is internally
used
>>
>>>by a lot of software, and even Windows itself. In your case, I almost
sure
>>
>>>that those lines are not generated by Xailer, but by a 'mwin.exe' program
>>
>>>that it seems to be malicous software.
>>>
>>>http://www.bleepingcomputer.com/startup ... -7941.html
>>>
>>>Best regards,
>>>
>>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>>
>>>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>>
>>>> Hi,
>>>>
>>>> after selecting the printer I'm converting the array with the print
>>>> positions
>>>> from cm to pixels with the following code
>>>>
>>>> WITH OBJECT Printer:oCanvas
>>>> :oFont:=oFont
>>>> :nMapMode:=mmHIMETRICS
>>>> ProcessMessages()
>>>> For nX:=1 TO LEN(aPos)
>>>>
>>>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>>>> ProcessMessages()
>>>> next
>>>> :nMapMode:=mmPIXELS
>>>> END WITH
>>>>
>>>> aPos is STATIC
>>>> aPix is LOCAL
>>>> Sometimes - not always - I got the GPF as shown in the picture and the
>>
>>>> following
>>>> LogDebug lines
>>>>
>>>> #1: HEAP[mwin.exe]:
>>>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size
of
>> dc
>>>>
>>>> #3: HEAP[mwin.exe]:
>>>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>>>
>>>> #5: Heap corruption detected at 0019F1B0
>>>>
>>>> #6: Heap corruption detected at 0019F1B0
>>>>
>>>> #7: Heap corruption detected at 0019F1B0
>>>>
>>>> #8: HEAP[mwin.exe]:
>>>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #10: Heap corruption detected at 0019F1B0
>>>>
>>>> #11: HEAP[mwin.exe]:
>>>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #13: Heap corruption detected at 0019F1B0
>>>>
>>>> #14: HEAP[mwin.exe]:
>>>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #16: Heap corruption detected at 0019F1B0
>>>>
>>>> #17: HEAP[mwin.exe]:
>>>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #19: Heap corruption detected at 0019F1B0
>>>>
>>>> #20: HEAP[mwin.exe]:
>>>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #22: Heap corruption detected at 0019F1B0
>>>>
>>>> #23: HEAP[mwin.exe]:
>>>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #25: Heap corruption detected at 0019F1B0
>>>>
>>>> #26: Heap corruption detected at 0019F1B0
>>>>
>>>> #27: Heap corruption detected at 0019F1B0
>>>>
>>>> #28: Heap corruption detected at 0019F1B0
>>>>
>>>> #29: Heap corruption detected at 0019F1B0
>>>>
>>>> #30: HEAP[mwin.exe]:
>>>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #32: Heap corruption detected at 0019F1B0
>>>>
>>>> #33: HEAP[mwin.exe]:
>>>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #35: Heap corruption detected at 0019F1B0
>>>>
>>>> #36: HEAP[mwin.exe]:
>>>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> Any idea what's wrong with my code?
>>>>
>>>> Thanks in advance
>>>>
>>>> Ingo
>>>
>>>
>>
>
>
you're asking for a list of the bugs I found?
I informed you about them here and in the public ng. Remember sometimes I
had to write again and again to convince you that there was a bug in Xailer
and not a mistake by myself.
I decided me on Xailer because I'm still the meaning that it is the best
developing environment for all the xBase-developers especially the one coming
from FiveWin. But beside the time I need to learn the new dev.-environment
I must spend much time to find out if it is a bug in Xailer or a bug in my
code when something was going wrong here even though it is working in the
16-bit application.
If you really want a list of the bugs please take a look at this ng
- AnsiToOem()
- Preview
- TReport
- TLabel
- Xailer.res
- TIni:GetSection
- TDbfDataSet
- TDBBrowse
for example, but I hope it was only a rhetoric question of you.
The printer problem I could only locate in the line of the conversion call.
Sorry, without the sourcecode of Xailer I can not see how the mm to pixel
conversion works. I can only tell you what happened. Maybe I can separate
this part of my application when I finished it but now I have a lot of work
in front of me.
I'm yearning for the new (and fixed) release maybe it will be looking better.
Regards
Ingo
"Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>Ingo,
>
>> now I have more problems with the bugs in Xailer than with transfering
my
>> sourcecode.
>
>Please, would you mind to give a list of those bugs. I will highly
>appreciate your feedback. We know that moving to a new developing
>environment is not easy, but please be patient and give your self the time
>to learn Xailer
>
>> The error must be caused in the line of converting cm to pixel and as
I
>> found
>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
is
>> that it happens not every time.
>
>I guess you are wrong, the routine for converting cm to pixels DOES NOT
>CALL ABSOLUTELY any API function, IS JUST A BUNCH OF ARITHMETICAL
>CALCULATIONS. So I guess the problem is not there. BTW, if you are able
to
>reproduce your bug on a simply application we will be glad to do some
>research.
>
>Regards,
>
>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>news:440d647a$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>
>> Ignacio,
>>
>> the lines with ProcessMessages() are one try to workaround. I deleted
>> them.
>> Mwin.exe is the project I'm building with Xailer and it was running from
>> the IDE when the error occured. It is not a 'malicious' software. It is
>> the
>> 16-bit software I'm trying to convert from FW16 to 32 bit by Xailer. Till
>> now I have more problems with the bugs in Xailer than with transfering
my
>> sourcecode.
>>
>> The error must be caused in the line of converting cm to pixel and as
I
>> found
>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
is
>> that it happens not every time.
>>
>> I had hoped the problem is known by otherones but nevertheless thanks
for
>> answering.
>>
>> Ingo
>>
>> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>>Ingo,
>>>
>>>I highly recommend to take off those ProcessMessages(), but I do not think
>>
>>>that are the cause of those LogDebug lines.
>>>
>>>Be aware that the LogDebug() mechanism built in Xailer is just a
>>>connection
>>
>>>with the standart OutputDebugString() API function that is internally
used
>>
>>>by a lot of software, and even Windows itself. In your case, I almost
sure
>>
>>>that those lines are not generated by Xailer, but by a 'mwin.exe' program
>>
>>>that it seems to be malicous software.
>>>
>>>http://www.bleepingcomputer.com/startup ... -7941.html
>>>
>>>Best regards,
>>>
>>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>>
>>>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>>
>>>> Hi,
>>>>
>>>> after selecting the printer I'm converting the array with the print
>>>> positions
>>>> from cm to pixels with the following code
>>>>
>>>> WITH OBJECT Printer:oCanvas
>>>> :oFont:=oFont
>>>> :nMapMode:=mmHIMETRICS
>>>> ProcessMessages()
>>>> For nX:=1 TO LEN(aPos)
>>>>
>>>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>>>> ProcessMessages()
>>>> next
>>>> :nMapMode:=mmPIXELS
>>>> END WITH
>>>>
>>>> aPos is STATIC
>>>> aPix is LOCAL
>>>> Sometimes - not always - I got the GPF as shown in the picture and the
>>
>>>> following
>>>> LogDebug lines
>>>>
>>>> #1: HEAP[mwin.exe]:
>>>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size
of
>> dc
>>>>
>>>> #3: HEAP[mwin.exe]:
>>>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>>>
>>>> #5: Heap corruption detected at 0019F1B0
>>>>
>>>> #6: Heap corruption detected at 0019F1B0
>>>>
>>>> #7: Heap corruption detected at 0019F1B0
>>>>
>>>> #8: HEAP[mwin.exe]:
>>>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #10: Heap corruption detected at 0019F1B0
>>>>
>>>> #11: HEAP[mwin.exe]:
>>>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #13: Heap corruption detected at 0019F1B0
>>>>
>>>> #14: HEAP[mwin.exe]:
>>>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #16: Heap corruption detected at 0019F1B0
>>>>
>>>> #17: HEAP[mwin.exe]:
>>>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #19: Heap corruption detected at 0019F1B0
>>>>
>>>> #20: HEAP[mwin.exe]:
>>>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #22: Heap corruption detected at 0019F1B0
>>>>
>>>> #23: HEAP[mwin.exe]:
>>>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #25: Heap corruption detected at 0019F1B0
>>>>
>>>> #26: Heap corruption detected at 0019F1B0
>>>>
>>>> #27: Heap corruption detected at 0019F1B0
>>>>
>>>> #28: Heap corruption detected at 0019F1B0
>>>>
>>>> #29: Heap corruption detected at 0019F1B0
>>>>
>>>> #30: HEAP[mwin.exe]:
>>>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #32: Heap corruption detected at 0019F1B0
>>>>
>>>> #33: HEAP[mwin.exe]:
>>>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #35: Heap corruption detected at 0019F1B0
>>>>
>>>> #36: HEAP[mwin.exe]:
>>>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> Any idea what's wrong with my code?
>>>>
>>>> Thanks in advance
>>>>
>>>> Ingo
>>>
>>>
>>
>
>
-
Ingo Junge-Herrmann
- Mensajes: 339
- Registrado: Lun Jul 02, 2007 7:17 pm
Print problem
Ignacio,
you're asking for a list of the bugs I found?
I informed you about them here and in the public ng. Remember sometimes I
had to write again and again to convince you that there was a bug in Xailer
and not a mistake by myself.
I decided me on Xailer because I'm still the meaning that it is the best
developing environment for all the xBase-developers especially the one coming
from FiveWin. But beside the time I need to learn the new dev.-environment
I must spend much time to find out if it is a bug in Xailer or a bug in my
code when something was going wrong here even though it is working in the
16-bit application.
If you really want a list of the bugs please take a look at this ng
- AnsiToOem()
- Preview
- TReport
- TLabel
- Xailer.res
- TIni:GetSection
- TDbfDataSet
- TDBBrowse
for example, but I hope it was only a rhetoric question of you.
The printer problem I could only locate in the line of the conversion call.
Sorry, without the sourcecode of Xailer I can not see how the mm to pixel
conversion works. I can only tell you what happened. Maybe I can separate
this part of my application when I finished it but now I have a lot of work
in front of me.
I'm yearning for the new (and fixed) release maybe it will be looking better.
Regards
Ingo
"Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>Ingo,
>
>> now I have more problems with the bugs in Xailer than with transfering
my
>> sourcecode.
>
>Please, would you mind to give a list of those bugs. I will highly
>appreciate your feedback. We know that moving to a new developing
>environment is not easy, but please be patient and give your self the time
>to learn Xailer
>
>> The error must be caused in the line of converting cm to pixel and as
I
>> found
>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
is
>> that it happens not every time.
>
>I guess you are wrong, the routine for converting cm to pixels DOES NOT
>CALL ABSOLUTELY any API function, IS JUST A BUNCH OF ARITHMETICAL
>CALCULATIONS. So I guess the problem is not there. BTW, if you are able
to
>reproduce your bug on a simply application we will be glad to do some
>research.
>
>Regards,
>
>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>news:440d647a$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>
>> Ignacio,
>>
>> the lines with ProcessMessages() are one try to workaround. I deleted
>> them.
>> Mwin.exe is the project I'm building with Xailer and it was running from
>> the IDE when the error occured. It is not a 'malicious' software. It is
>> the
>> 16-bit software I'm trying to convert from FW16 to 32 bit by Xailer. Till
>> now I have more problems with the bugs in Xailer than with transfering
my
>> sourcecode.
>>
>> The error must be caused in the line of converting cm to pixel and as
I
>> found
>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
is
>> that it happens not every time.
>>
>> I had hoped the problem is known by otherones but nevertheless thanks
for
>> answering.
>>
>> Ingo
>>
>> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>>Ingo,
>>>
>>>I highly recommend to take off those ProcessMessages(), but I do not think
>>
>>>that are the cause of those LogDebug lines.
>>>
>>>Be aware that the LogDebug() mechanism built in Xailer is just a
>>>connection
>>
>>>with the standart OutputDebugString() API function that is internally
used
>>
>>>by a lot of software, and even Windows itself. In your case, I almost
sure
>>
>>>that those lines are not generated by Xailer, but by a 'mwin.exe' program
>>
>>>that it seems to be malicous software.
>>>
>>>http://www.bleepingcomputer.com/startup ... -7941.html
>>>
>>>Best regards,
>>>
>>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>>
>>>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>>
>>>> Hi,
>>>>
>>>> after selecting the printer I'm converting the array with the print
>>>> positions
>>>> from cm to pixels with the following code
>>>>
>>>> WITH OBJECT Printer:oCanvas
>>>> :oFont:=oFont
>>>> :nMapMode:=mmHIMETRICS
>>>> ProcessMessages()
>>>> For nX:=1 TO LEN(aPos)
>>>>
>>>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>>>> ProcessMessages()
>>>> next
>>>> :nMapMode:=mmPIXELS
>>>> END WITH
>>>>
>>>> aPos is STATIC
>>>> aPix is LOCAL
>>>> Sometimes - not always - I got the GPF as shown in the picture and the
>>
>>>> following
>>>> LogDebug lines
>>>>
>>>> #1: HEAP[mwin.exe]:
>>>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size
of
>> dc
>>>>
>>>> #3: HEAP[mwin.exe]:
>>>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>>>
>>>> #5: Heap corruption detected at 0019F1B0
>>>>
>>>> #6: Heap corruption detected at 0019F1B0
>>>>
>>>> #7: Heap corruption detected at 0019F1B0
>>>>
>>>> #8: HEAP[mwin.exe]:
>>>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #10: Heap corruption detected at 0019F1B0
>>>>
>>>> #11: HEAP[mwin.exe]:
>>>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #13: Heap corruption detected at 0019F1B0
>>>>
>>>> #14: HEAP[mwin.exe]:
>>>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #16: Heap corruption detected at 0019F1B0
>>>>
>>>> #17: HEAP[mwin.exe]:
>>>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #19: Heap corruption detected at 0019F1B0
>>>>
>>>> #20: HEAP[mwin.exe]:
>>>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #22: Heap corruption detected at 0019F1B0
>>>>
>>>> #23: HEAP[mwin.exe]:
>>>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #25: Heap corruption detected at 0019F1B0
>>>>
>>>> #26: Heap corruption detected at 0019F1B0
>>>>
>>>> #27: Heap corruption detected at 0019F1B0
>>>>
>>>> #28: Heap corruption detected at 0019F1B0
>>>>
>>>> #29: Heap corruption detected at 0019F1B0
>>>>
>>>> #30: HEAP[mwin.exe]:
>>>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #32: Heap corruption detected at 0019F1B0
>>>>
>>>> #33: HEAP[mwin.exe]:
>>>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #35: Heap corruption detected at 0019F1B0
>>>>
>>>> #36: HEAP[mwin.exe]:
>>>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> Any idea what's wrong with my code?
>>>>
>>>> Thanks in advance
>>>>
>>>> Ingo
>>>
>>>
>>
>
>
you're asking for a list of the bugs I found?
I informed you about them here and in the public ng. Remember sometimes I
had to write again and again to convince you that there was a bug in Xailer
and not a mistake by myself.
I decided me on Xailer because I'm still the meaning that it is the best
developing environment for all the xBase-developers especially the one coming
from FiveWin. But beside the time I need to learn the new dev.-environment
I must spend much time to find out if it is a bug in Xailer or a bug in my
code when something was going wrong here even though it is working in the
16-bit application.
If you really want a list of the bugs please take a look at this ng
- AnsiToOem()
- Preview
- TReport
- TLabel
- Xailer.res
- TIni:GetSection
- TDbfDataSet
- TDBBrowse
for example, but I hope it was only a rhetoric question of you.
The printer problem I could only locate in the line of the conversion call.
Sorry, without the sourcecode of Xailer I can not see how the mm to pixel
conversion works. I can only tell you what happened. Maybe I can separate
this part of my application when I finished it but now I have a lot of work
in front of me.
I'm yearning for the new (and fixed) release maybe it will be looking better.
Regards
Ingo
"Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>Ingo,
>
>> now I have more problems with the bugs in Xailer than with transfering
my
>> sourcecode.
>
>Please, would you mind to give a list of those bugs. I will highly
>appreciate your feedback. We know that moving to a new developing
>environment is not easy, but please be patient and give your self the time
>to learn Xailer
>
>> The error must be caused in the line of converting cm to pixel and as
I
>> found
>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
is
>> that it happens not every time.
>
>I guess you are wrong, the routine for converting cm to pixels DOES NOT
>CALL ABSOLUTELY any API function, IS JUST A BUNCH OF ARITHMETICAL
>CALCULATIONS. So I guess the problem is not there. BTW, if you are able
to
>reproduce your bug on a simply application we will be glad to do some
>research.
>
>Regards,
>
>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>news:440d647a$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>
>> Ignacio,
>>
>> the lines with ProcessMessages() are one try to workaround. I deleted
>> them.
>> Mwin.exe is the project I'm building with Xailer and it was running from
>> the IDE when the error occured. It is not a 'malicious' software. It is
>> the
>> 16-bit software I'm trying to convert from FW16 to 32 bit by Xailer. Till
>> now I have more problems with the bugs in Xailer than with transfering
my
>> sourcecode.
>>
>> The error must be caused in the line of converting cm to pixel and as
I
>> found
>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
is
>> that it happens not every time.
>>
>> I had hoped the problem is known by otherones but nevertheless thanks
for
>> answering.
>>
>> Ingo
>>
>> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>>Ingo,
>>>
>>>I highly recommend to take off those ProcessMessages(), but I do not think
>>
>>>that are the cause of those LogDebug lines.
>>>
>>>Be aware that the LogDebug() mechanism built in Xailer is just a
>>>connection
>>
>>>with the standart OutputDebugString() API function that is internally
used
>>
>>>by a lot of software, and even Windows itself. In your case, I almost
sure
>>
>>>that those lines are not generated by Xailer, but by a 'mwin.exe' program
>>
>>>that it seems to be malicous software.
>>>
>>>http://www.bleepingcomputer.com/startup ... -7941.html
>>>
>>>Best regards,
>>>
>>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>>
>>>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>>
>>>> Hi,
>>>>
>>>> after selecting the printer I'm converting the array with the print
>>>> positions
>>>> from cm to pixels with the following code
>>>>
>>>> WITH OBJECT Printer:oCanvas
>>>> :oFont:=oFont
>>>> :nMapMode:=mmHIMETRICS
>>>> ProcessMessages()
>>>> For nX:=1 TO LEN(aPos)
>>>>
>>>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>>>> ProcessMessages()
>>>> next
>>>> :nMapMode:=mmPIXELS
>>>> END WITH
>>>>
>>>> aPos is STATIC
>>>> aPix is LOCAL
>>>> Sometimes - not always - I got the GPF as shown in the picture and the
>>
>>>> following
>>>> LogDebug lines
>>>>
>>>> #1: HEAP[mwin.exe]:
>>>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size
of
>> dc
>>>>
>>>> #3: HEAP[mwin.exe]:
>>>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>>>
>>>> #5: Heap corruption detected at 0019F1B0
>>>>
>>>> #6: Heap corruption detected at 0019F1B0
>>>>
>>>> #7: Heap corruption detected at 0019F1B0
>>>>
>>>> #8: HEAP[mwin.exe]:
>>>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #10: Heap corruption detected at 0019F1B0
>>>>
>>>> #11: HEAP[mwin.exe]:
>>>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #13: Heap corruption detected at 0019F1B0
>>>>
>>>> #14: HEAP[mwin.exe]:
>>>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #16: Heap corruption detected at 0019F1B0
>>>>
>>>> #17: HEAP[mwin.exe]:
>>>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #19: Heap corruption detected at 0019F1B0
>>>>
>>>> #20: HEAP[mwin.exe]:
>>>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #22: Heap corruption detected at 0019F1B0
>>>>
>>>> #23: HEAP[mwin.exe]:
>>>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #25: Heap corruption detected at 0019F1B0
>>>>
>>>> #26: Heap corruption detected at 0019F1B0
>>>>
>>>> #27: Heap corruption detected at 0019F1B0
>>>>
>>>> #28: Heap corruption detected at 0019F1B0
>>>>
>>>> #29: Heap corruption detected at 0019F1B0
>>>>
>>>> #30: HEAP[mwin.exe]:
>>>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #32: Heap corruption detected at 0019F1B0
>>>>
>>>> #33: HEAP[mwin.exe]:
>>>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> #35: Heap corruption detected at 0019F1B0
>>>>
>>>> #36: HEAP[mwin.exe]:
>>>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>
>>>> Any idea what's wrong with my code?
>>>>
>>>> Thanks in advance
>>>>
>>>> Ingo
>>>
>>>
>>
>
>
-
ignacio
- Site Admin
- Mensajes: 9253
- Registrado: Lun Abr 06, 2015 8:00 pm
- Ubicación: Madrid, Spain
- Contactar:
Print problem
Ingo,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:440d98ba$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> you're asking for a list of the bugs I found?
>
> I informed you about them here and in the public ng. Remember sometimes I
> had to write again and again to convince you that there was a bug in
> Xailer
> and not a mistake by myself.
>
> I decided me on Xailer because I'm still the meaning that it is the best
> developing environment for all the xBase-developers especially the one
> coming
> from FiveWin. But beside the time I need to learn the new dev.-environment
> I must spend much time to find out if it is a bug in Xailer or a bug in my
> code when something was going wrong here even though it is working in the
> 16-bit application.
>
> If you really want a list of the bugs please take a look at this ng
> - AnsiToOem()
> - Preview
> - TReport
> - TLabel
> - Xailer.res
> - TIni:GetSection
> - TDbfDataSet
> - TDBBrowse
>
> for example, but I hope it was only a rhetoric question of you.
>
> The printer problem I could only locate in the line of the conversion
> call.
> Sorry, without the sourcecode of Xailer I can not see how the mm to pixel
> conversion works. I can only tell you what happened. Maybe I can separate
> this part of my application when I finished it but now I have a lot of
> work
> in front of me.
>
> I'm yearning for the new (and fixed) release maybe it will be looking
> better.
>
> Regards
>
> Ingo
>
> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>Ingo,
>>
>>> now I have more problems with the bugs in Xailer than with transfering
> my
>>> sourcecode.
>>
>>Please, would you mind to give a list of those bugs. I will highly
>>appreciate your feedback. We know that moving to a new developing
>>environment is not easy, but please be patient and give your self the time
>
>>to learn Xailer
>>
>>> The error must be caused in the line of converting cm to pixel and as
> I
>>> found
>>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
> is
>>> that it happens not every time.
>>
>>I guess you are wrong, the routine for converting cm to pixels DOES NOT
>
>>CALL ABSOLUTELY any API function, IS JUST A BUNCH OF ARITHMETICAL
>>CALCULATIONS. So I guess the problem is not there. BTW, if you are able
> to
>>reproduce your bug on a simply application we will be glad to do some
>>research.
>>
>>Regards,
>>
>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>
>>news:440d647a$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>
>>> Ignacio,
>>>
>>> the lines with ProcessMessages() are one try to workaround. I deleted
>
>>> them.
>>> Mwin.exe is the project I'm building with Xailer and it was running from
>>> the IDE when the error occured. It is not a 'malicious' software. It is
>
>>> the
>>> 16-bit software I'm trying to convert from FW16 to 32 bit by Xailer.
>>> Till
>>> now I have more problems with the bugs in Xailer than with transfering
> my
>>> sourcecode.
>>>
>>> The error must be caused in the line of converting cm to pixel and as
> I
>>> found
>>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
> is
>>> that it happens not every time.
>>>
>>> I had hoped the problem is known by otherones but nevertheless thanks
> for
>>> answering.
>>>
>>> Ingo
>>>
>>> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>>>Ingo,
>>>>
>>>>I highly recommend to take off those ProcessMessages(), but I do not
>>>>think
>>>
>>>>that are the cause of those LogDebug lines.
>>>>
>>>>Be aware that the LogDebug() mechanism built in Xailer is just a
>>>>connection
>>>
>>>>with the standart OutputDebugString() API function that is internally
> used
>>>
>>>>by a lot of software, and even Windows itself. In your case, I almost
> sure
>>>
>>>>that those lines are not generated by Xailer, but by a 'mwin.exe'
>>>>program
>>>
>>>>that it seems to be malicous software.
>>>>
>>>>http://www.bleepingcomputer.com/startup ... -7941.html
>>>>
>>>>Best regards,
>>>>
>>>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el
>>>>mensaje
>>>
>>>>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>>>
>>>>> Hi,
>>>>>
>>>>> after selecting the printer I'm converting the array with the print
>>>>> positions
>>>>> from cm to pixels with the following code
>>>>>
>>>>> WITH OBJECT Printer:oCanvas
>>>>> :oFont:=oFont
>>>>> :nMapMode:=mmHIMETRICS
>>>>> ProcessMessages()
>>>>> For nX:=1 TO LEN(aPos)
>>>>>
>>>>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>>>>> ProcessMessages()
>>>>> next
>>>>> :nMapMode:=mmPIXELS
>>>>> END WITH
>>>>>
>>>>> aPos is STATIC
>>>>> aPix is LOCAL
>>>>> Sometimes - not always - I got the GPF as shown in the picture and the
>>>
>>>>> following
>>>>> LogDebug lines
>>>>>
>>>>> #1: HEAP[mwin.exe]:
>>>>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size
> of
>>> dc
>>>>>
>>>>> #3: HEAP[mwin.exe]:
>>>>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>>>>
>>>>> #5: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #6: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #7: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #8: HEAP[mwin.exe]:
>>>>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>>
>>>>> #10: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #11: HEAP[mwin.exe]:
>>>>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #13: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #14: HEAP[mwin.exe]:
>>>>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #16: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #17: HEAP[mwin.exe]:
>>>>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #19: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #20: HEAP[mwin.exe]:
>>>>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #22: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #23: HEAP[mwin.exe]:
>>>>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #25: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #26: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #27: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #28: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #29: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #30: HEAP[mwin.exe]:
>>>>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #32: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #33: HEAP[mwin.exe]:
>>>>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #35: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #36: HEAP[mwin.exe]:
>>>>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> Any idea what's wrong with my code?
>>>>>
>>>>> Thanks in advance
>>>>>
>>>>> Ingo
>>>>
>>>>
>>>
>>
>>
>
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:440d98ba$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> you're asking for a list of the bugs I found?
>
> I informed you about them here and in the public ng. Remember sometimes I
> had to write again and again to convince you that there was a bug in
> Xailer
> and not a mistake by myself.
>
> I decided me on Xailer because I'm still the meaning that it is the best
> developing environment for all the xBase-developers especially the one
> coming
> from FiveWin. But beside the time I need to learn the new dev.-environment
> I must spend much time to find out if it is a bug in Xailer or a bug in my
> code when something was going wrong here even though it is working in the
> 16-bit application.
>
> If you really want a list of the bugs please take a look at this ng
> - AnsiToOem()
> - Preview
> - TReport
> - TLabel
> - Xailer.res
> - TIni:GetSection
> - TDbfDataSet
> - TDBBrowse
>
> for example, but I hope it was only a rhetoric question of you.
>
> The printer problem I could only locate in the line of the conversion
> call.
> Sorry, without the sourcecode of Xailer I can not see how the mm to pixel
> conversion works. I can only tell you what happened. Maybe I can separate
> this part of my application when I finished it but now I have a lot of
> work
> in front of me.
>
> I'm yearning for the new (and fixed) release maybe it will be looking
> better.
>
> Regards
>
> Ingo
>
> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>Ingo,
>>
>>> now I have more problems with the bugs in Xailer than with transfering
> my
>>> sourcecode.
>>
>>Please, would you mind to give a list of those bugs. I will highly
>>appreciate your feedback. We know that moving to a new developing
>>environment is not easy, but please be patient and give your self the time
>
>>to learn Xailer
>>
>>> The error must be caused in the line of converting cm to pixel and as
> I
>>> found
>>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
> is
>>> that it happens not every time.
>>
>>I guess you are wrong, the routine for converting cm to pixels DOES NOT
>
>>CALL ABSOLUTELY any API function, IS JUST A BUNCH OF ARITHMETICAL
>>CALCULATIONS. So I guess the problem is not there. BTW, if you are able
> to
>>reproduce your bug on a simply application we will be glad to do some
>>research.
>>
>>Regards,
>>
>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>
>>news:440d647a$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>
>>> Ignacio,
>>>
>>> the lines with ProcessMessages() are one try to workaround. I deleted
>
>>> them.
>>> Mwin.exe is the project I'm building with Xailer and it was running from
>>> the IDE when the error occured. It is not a 'malicious' software. It is
>
>>> the
>>> 16-bit software I'm trying to convert from FW16 to 32 bit by Xailer.
>>> Till
>>> now I have more problems with the bugs in Xailer than with transfering
> my
>>> sourcecode.
>>>
>>> The error must be caused in the line of converting cm to pixel and as
> I
>>> found
>>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
> is
>>> that it happens not every time.
>>>
>>> I had hoped the problem is known by otherones but nevertheless thanks
> for
>>> answering.
>>>
>>> Ingo
>>>
>>> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>>>Ingo,
>>>>
>>>>I highly recommend to take off those ProcessMessages(), but I do not
>>>>think
>>>
>>>>that are the cause of those LogDebug lines.
>>>>
>>>>Be aware that the LogDebug() mechanism built in Xailer is just a
>>>>connection
>>>
>>>>with the standart OutputDebugString() API function that is internally
> used
>>>
>>>>by a lot of software, and even Windows itself. In your case, I almost
> sure
>>>
>>>>that those lines are not generated by Xailer, but by a 'mwin.exe'
>>>>program
>>>
>>>>that it seems to be malicous software.
>>>>
>>>>http://www.bleepingcomputer.com/startup ... -7941.html
>>>>
>>>>Best regards,
>>>>
>>>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el
>>>>mensaje
>>>
>>>>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>>>
>>>>> Hi,
>>>>>
>>>>> after selecting the printer I'm converting the array with the print
>>>>> positions
>>>>> from cm to pixels with the following code
>>>>>
>>>>> WITH OBJECT Printer:oCanvas
>>>>> :oFont:=oFont
>>>>> :nMapMode:=mmHIMETRICS
>>>>> ProcessMessages()
>>>>> For nX:=1 TO LEN(aPos)
>>>>>
>>>>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>>>>> ProcessMessages()
>>>>> next
>>>>> :nMapMode:=mmPIXELS
>>>>> END WITH
>>>>>
>>>>> aPos is STATIC
>>>>> aPix is LOCAL
>>>>> Sometimes - not always - I got the GPF as shown in the picture and the
>>>
>>>>> following
>>>>> LogDebug lines
>>>>>
>>>>> #1: HEAP[mwin.exe]:
>>>>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size
> of
>>> dc
>>>>>
>>>>> #3: HEAP[mwin.exe]:
>>>>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>>>>
>>>>> #5: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #6: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #7: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #8: HEAP[mwin.exe]:
>>>>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>>
>>>>> #10: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #11: HEAP[mwin.exe]:
>>>>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #13: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #14: HEAP[mwin.exe]:
>>>>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #16: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #17: HEAP[mwin.exe]:
>>>>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #19: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #20: HEAP[mwin.exe]:
>>>>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #22: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #23: HEAP[mwin.exe]:
>>>>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #25: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #26: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #27: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #28: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #29: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #30: HEAP[mwin.exe]:
>>>>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #32: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #33: HEAP[mwin.exe]:
>>>>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #35: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #36: HEAP[mwin.exe]:
>>>>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> Any idea what's wrong with my code?
>>>>>
>>>>> Thanks in advance
>>>>>
>>>>> Ingo
>>>>
>>>>
>>>
>>
>>
>
Print problem
Ingo,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:440d98ba$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> you're asking for a list of the bugs I found?
>
> I informed you about them here and in the public ng. Remember sometimes I
> had to write again and again to convince you that there was a bug in
> Xailer
> and not a mistake by myself.
>
> I decided me on Xailer because I'm still the meaning that it is the best
> developing environment for all the xBase-developers especially the one
> coming
> from FiveWin. But beside the time I need to learn the new dev.-environment
> I must spend much time to find out if it is a bug in Xailer or a bug in my
> code when something was going wrong here even though it is working in the
> 16-bit application.
>
> If you really want a list of the bugs please take a look at this ng
> - AnsiToOem()
> - Preview
> - TReport
> - TLabel
> - Xailer.res
> - TIni:GetSection
> - TDbfDataSet
> - TDBBrowse
>
> for example, but I hope it was only a rhetoric question of you.
>
> The printer problem I could only locate in the line of the conversion
> call.
> Sorry, without the sourcecode of Xailer I can not see how the mm to pixel
> conversion works. I can only tell you what happened. Maybe I can separate
> this part of my application when I finished it but now I have a lot of
> work
> in front of me.
>
> I'm yearning for the new (and fixed) release maybe it will be looking
> better.
>
> Regards
>
> Ingo
>
> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>Ingo,
>>
>>> now I have more problems with the bugs in Xailer than with transfering
> my
>>> sourcecode.
>>
>>Please, would you mind to give a list of those bugs. I will highly
>>appreciate your feedback. We know that moving to a new developing
>>environment is not easy, but please be patient and give your self the time
>
>>to learn Xailer
>>
>>> The error must be caused in the line of converting cm to pixel and as
> I
>>> found
>>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
> is
>>> that it happens not every time.
>>
>>I guess you are wrong, the routine for converting cm to pixels DOES NOT
>
>>CALL ABSOLUTELY any API function, IS JUST A BUNCH OF ARITHMETICAL
>>CALCULATIONS. So I guess the problem is not there. BTW, if you are able
> to
>>reproduce your bug on a simply application we will be glad to do some
>>research.
>>
>>Regards,
>>
>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>
>>news:440d647a$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>
>>> Ignacio,
>>>
>>> the lines with ProcessMessages() are one try to workaround. I deleted
>
>>> them.
>>> Mwin.exe is the project I'm building with Xailer and it was running from
>>> the IDE when the error occured. It is not a 'malicious' software. It is
>
>>> the
>>> 16-bit software I'm trying to convert from FW16 to 32 bit by Xailer.
>>> Till
>>> now I have more problems with the bugs in Xailer than with transfering
> my
>>> sourcecode.
>>>
>>> The error must be caused in the line of converting cm to pixel and as
> I
>>> found
>>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
> is
>>> that it happens not every time.
>>>
>>> I had hoped the problem is known by otherones but nevertheless thanks
> for
>>> answering.
>>>
>>> Ingo
>>>
>>> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>>>Ingo,
>>>>
>>>>I highly recommend to take off those ProcessMessages(), but I do not
>>>>think
>>>
>>>>that are the cause of those LogDebug lines.
>>>>
>>>>Be aware that the LogDebug() mechanism built in Xailer is just a
>>>>connection
>>>
>>>>with the standart OutputDebugString() API function that is internally
> used
>>>
>>>>by a lot of software, and even Windows itself. In your case, I almost
> sure
>>>
>>>>that those lines are not generated by Xailer, but by a 'mwin.exe'
>>>>program
>>>
>>>>that it seems to be malicous software.
>>>>
>>>>http://www.bleepingcomputer.com/startup ... -7941.html
>>>>
>>>>Best regards,
>>>>
>>>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el
>>>>mensaje
>>>
>>>>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>>>
>>>>> Hi,
>>>>>
>>>>> after selecting the printer I'm converting the array with the print
>>>>> positions
>>>>> from cm to pixels with the following code
>>>>>
>>>>> WITH OBJECT Printer:oCanvas
>>>>> :oFont:=oFont
>>>>> :nMapMode:=mmHIMETRICS
>>>>> ProcessMessages()
>>>>> For nX:=1 TO LEN(aPos)
>>>>>
>>>>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>>>>> ProcessMessages()
>>>>> next
>>>>> :nMapMode:=mmPIXELS
>>>>> END WITH
>>>>>
>>>>> aPos is STATIC
>>>>> aPix is LOCAL
>>>>> Sometimes - not always - I got the GPF as shown in the picture and the
>>>
>>>>> following
>>>>> LogDebug lines
>>>>>
>>>>> #1: HEAP[mwin.exe]:
>>>>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size
> of
>>> dc
>>>>>
>>>>> #3: HEAP[mwin.exe]:
>>>>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>>>>
>>>>> #5: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #6: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #7: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #8: HEAP[mwin.exe]:
>>>>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>>
>>>>> #10: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #11: HEAP[mwin.exe]:
>>>>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #13: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #14: HEAP[mwin.exe]:
>>>>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #16: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #17: HEAP[mwin.exe]:
>>>>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #19: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #20: HEAP[mwin.exe]:
>>>>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #22: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #23: HEAP[mwin.exe]:
>>>>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #25: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #26: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #27: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #28: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #29: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #30: HEAP[mwin.exe]:
>>>>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #32: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #33: HEAP[mwin.exe]:
>>>>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #35: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #36: HEAP[mwin.exe]:
>>>>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> Any idea what's wrong with my code?
>>>>>
>>>>> Thanks in advance
>>>>>
>>>>> Ingo
>>>>
>>>>
>>>
>>
>>
>
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:440d98ba$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> you're asking for a list of the bugs I found?
>
> I informed you about them here and in the public ng. Remember sometimes I
> had to write again and again to convince you that there was a bug in
> Xailer
> and not a mistake by myself.
>
> I decided me on Xailer because I'm still the meaning that it is the best
> developing environment for all the xBase-developers especially the one
> coming
> from FiveWin. But beside the time I need to learn the new dev.-environment
> I must spend much time to find out if it is a bug in Xailer or a bug in my
> code when something was going wrong here even though it is working in the
> 16-bit application.
>
> If you really want a list of the bugs please take a look at this ng
> - AnsiToOem()
> - Preview
> - TReport
> - TLabel
> - Xailer.res
> - TIni:GetSection
> - TDbfDataSet
> - TDBBrowse
>
> for example, but I hope it was only a rhetoric question of you.
>
> The printer problem I could only locate in the line of the conversion
> call.
> Sorry, without the sourcecode of Xailer I can not see how the mm to pixel
> conversion works. I can only tell you what happened. Maybe I can separate
> this part of my application when I finished it but now I have a lot of
> work
> in front of me.
>
> I'm yearning for the new (and fixed) release maybe it will be looking
> better.
>
> Regards
>
> Ingo
>
> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>Ingo,
>>
>>> now I have more problems with the bugs in Xailer than with transfering
> my
>>> sourcecode.
>>
>>Please, would you mind to give a list of those bugs. I will highly
>>appreciate your feedback. We know that moving to a new developing
>>environment is not easy, but please be patient and give your self the time
>
>>to learn Xailer
>>
>>> The error must be caused in the line of converting cm to pixel and as
> I
>>> found
>>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
> is
>>> that it happens not every time.
>>
>>I guess you are wrong, the routine for converting cm to pixels DOES NOT
>
>>CALL ABSOLUTELY any API function, IS JUST A BUNCH OF ARITHMETICAL
>>CALCULATIONS. So I guess the problem is not there. BTW, if you are able
> to
>>reproduce your bug on a simply application we will be glad to do some
>>research.
>>
>>Regards,
>>
>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>
>>news:440d647a$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>
>>> Ignacio,
>>>
>>> the lines with ProcessMessages() are one try to workaround. I deleted
>
>>> them.
>>> Mwin.exe is the project I'm building with Xailer and it was running from
>>> the IDE when the error occured. It is not a 'malicious' software. It is
>
>>> the
>>> 16-bit software I'm trying to convert from FW16 to 32 bit by Xailer.
>>> Till
>>> now I have more problems with the bugs in Xailer than with transfering
> my
>>> sourcecode.
>>>
>>> The error must be caused in the line of converting cm to pixel and as
> I
>>> found
>>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
> is
>>> that it happens not every time.
>>>
>>> I had hoped the problem is known by otherones but nevertheless thanks
> for
>>> answering.
>>>
>>> Ingo
>>>
>>> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>>>Ingo,
>>>>
>>>>I highly recommend to take off those ProcessMessages(), but I do not
>>>>think
>>>
>>>>that are the cause of those LogDebug lines.
>>>>
>>>>Be aware that the LogDebug() mechanism built in Xailer is just a
>>>>connection
>>>
>>>>with the standart OutputDebugString() API function that is internally
> used
>>>
>>>>by a lot of software, and even Windows itself. In your case, I almost
> sure
>>>
>>>>that those lines are not generated by Xailer, but by a 'mwin.exe'
>>>>program
>>>
>>>>that it seems to be malicous software.
>>>>
>>>>http://www.bleepingcomputer.com/startup ... -7941.html
>>>>
>>>>Best regards,
>>>>
>>>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el
>>>>mensaje
>>>
>>>>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>>>
>>>>> Hi,
>>>>>
>>>>> after selecting the printer I'm converting the array with the print
>>>>> positions
>>>>> from cm to pixels with the following code
>>>>>
>>>>> WITH OBJECT Printer:oCanvas
>>>>> :oFont:=oFont
>>>>> :nMapMode:=mmHIMETRICS
>>>>> ProcessMessages()
>>>>> For nX:=1 TO LEN(aPos)
>>>>>
>>>>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>>>>> ProcessMessages()
>>>>> next
>>>>> :nMapMode:=mmPIXELS
>>>>> END WITH
>>>>>
>>>>> aPos is STATIC
>>>>> aPix is LOCAL
>>>>> Sometimes - not always - I got the GPF as shown in the picture and the
>>>
>>>>> following
>>>>> LogDebug lines
>>>>>
>>>>> #1: HEAP[mwin.exe]:
>>>>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size
> of
>>> dc
>>>>>
>>>>> #3: HEAP[mwin.exe]:
>>>>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>>>>
>>>>> #5: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #6: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #7: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #8: HEAP[mwin.exe]:
>>>>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>>
>>>>> #10: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #11: HEAP[mwin.exe]:
>>>>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #13: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #14: HEAP[mwin.exe]:
>>>>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #16: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #17: HEAP[mwin.exe]:
>>>>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #19: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #20: HEAP[mwin.exe]:
>>>>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #22: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #23: HEAP[mwin.exe]:
>>>>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #25: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #26: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #27: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #28: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #29: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #30: HEAP[mwin.exe]:
>>>>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #32: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #33: HEAP[mwin.exe]:
>>>>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #35: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #36: HEAP[mwin.exe]:
>>>>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> Any idea what's wrong with my code?
>>>>>
>>>>> Thanks in advance
>>>>>
>>>>> Ingo
>>>>
>>>>
>>>
>>
>>
>
-
ignacio
- Site Admin
- Mensajes: 9253
- Registrado: Lun Abr 06, 2015 8:00 pm
- Ubicación: Madrid, Spain
- Contactar:
Print problem
Ingo,
> If you really want a list of the bugs please take a look at this ng
> - AnsiToOem()
> - Preview
> - TReport
> - TLabel
> - Xailer.res
> - TIni:GetSection
> - TDbfDataSet
> - TDBBrowse
Sorry, but you are certenly unfair with your critics. I am sure almost none
of your bugs reported were critic and some of them are just cosmetic issues.
It seems you have forgot that you boughht a PRE-RELEASE version and BTW any
of your questions has been asnwered and corrected in record time.
> Sorry, without the sourcecode of Xailer I can not see how the mm to pixel
> conversion works. I can only tell you what happened. Maybe I can separate
> this part of my application when I finished it but now I have a lot of
> work
> in front of me.
Up to you. Other guys have no problem making a small sample that we can
reproduce to fix our bugs. I hope you find the bug yourself, if you haven't
do it yet.
> I'm yearning for the new (and fixed) release maybe it will be looking
> better.
I really expect so, but if it does not, be free to ask for a refund.
Best regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:440d98ba$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> you're asking for a list of the bugs I found?
>
> I informed you about them here and in the public ng. Remember sometimes I
> had to write again and again to convince you that there was a bug in
> Xailer
> and not a mistake by myself.
>
> I decided me on Xailer because I'm still the meaning that it is the best
> developing environment for all the xBase-developers especially the one
> coming
> from FiveWin. But beside the time I need to learn the new dev.-environment
> I must spend much time to find out if it is a bug in Xailer or a bug in my
> code when something was going wrong here even though it is working in the
> 16-bit application.
>
> If you really want a list of the bugs please take a look at this ng
> - AnsiToOem()
> - Preview
> - TReport
> - TLabel
> - Xailer.res
> - TIni:GetSection
> - TDbfDataSet
> - TDBBrowse
>
> for example, but I hope it was only a rhetoric question of you.
>
> The printer problem I could only locate in the line of the conversion
> call.
> Sorry, without the sourcecode of Xailer I can not see how the mm to pixel
> conversion works. I can only tell you what happened. Maybe I can separate
> this part of my application when I finished it but now I have a lot of
> work
> in front of me.
>
> I'm yearning for the new (and fixed) release maybe it will be looking
> better.
>
> Regards
>
> Ingo
>
> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>Ingo,
>>
>>> now I have more problems with the bugs in Xailer than with transfering
> my
>>> sourcecode.
>>
>>Please, would you mind to give a list of those bugs. I will highly
>>appreciate your feedback. We know that moving to a new developing
>>environment is not easy, but please be patient and give your self the time
>
>>to learn Xailer
>>
>>> The error must be caused in the line of converting cm to pixel and as
> I
>>> found
>>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
> is
>>> that it happens not every time.
>>
>>I guess you are wrong, the routine for converting cm to pixels DOES NOT
>
>>CALL ABSOLUTELY any API function, IS JUST A BUNCH OF ARITHMETICAL
>>CALCULATIONS. So I guess the problem is not there. BTW, if you are able
> to
>>reproduce your bug on a simply application we will be glad to do some
>>research.
>>
>>Regards,
>>
>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>
>>news:440d647a$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>
>>> Ignacio,
>>>
>>> the lines with ProcessMessages() are one try to workaround. I deleted
>
>>> them.
>>> Mwin.exe is the project I'm building with Xailer and it was running from
>>> the IDE when the error occured. It is not a 'malicious' software. It is
>
>>> the
>>> 16-bit software I'm trying to convert from FW16 to 32 bit by Xailer.
>>> Till
>>> now I have more problems with the bugs in Xailer than with transfering
> my
>>> sourcecode.
>>>
>>> The error must be caused in the line of converting cm to pixel and as
> I
>>> found
>>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
> is
>>> that it happens not every time.
>>>
>>> I had hoped the problem is known by otherones but nevertheless thanks
> for
>>> answering.
>>>
>>> Ingo
>>>
>>> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>>>Ingo,
>>>>
>>>>I highly recommend to take off those ProcessMessages(), but I do not
>>>>think
>>>
>>>>that are the cause of those LogDebug lines.
>>>>
>>>>Be aware that the LogDebug() mechanism built in Xailer is just a
>>>>connection
>>>
>>>>with the standart OutputDebugString() API function that is internally
> used
>>>
>>>>by a lot of software, and even Windows itself. In your case, I almost
> sure
>>>
>>>>that those lines are not generated by Xailer, but by a 'mwin.exe'
>>>>program
>>>
>>>>that it seems to be malicous software.
>>>>
>>>>http://www.bleepingcomputer.com/startup ... -7941.html
>>>>
>>>>Best regards,
>>>>
>>>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el
>>>>mensaje
>>>
>>>>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>>>
>>>>> Hi,
>>>>>
>>>>> after selecting the printer I'm converting the array with the print
>>>>> positions
>>>>> from cm to pixels with the following code
>>>>>
>>>>> WITH OBJECT Printer:oCanvas
>>>>> :oFont:=oFont
>>>>> :nMapMode:=mmHIMETRICS
>>>>> ProcessMessages()
>>>>> For nX:=1 TO LEN(aPos)
>>>>>
>>>>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>>>>> ProcessMessages()
>>>>> next
>>>>> :nMapMode:=mmPIXELS
>>>>> END WITH
>>>>>
>>>>> aPos is STATIC
>>>>> aPix is LOCAL
>>>>> Sometimes - not always - I got the GPF as shown in the picture and the
>>>
>>>>> following
>>>>> LogDebug lines
>>>>>
>>>>> #1: HEAP[mwin.exe]:
>>>>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size
> of
>>> dc
>>>>>
>>>>> #3: HEAP[mwin.exe]:
>>>>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>>>>
>>>>> #5: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #6: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #7: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #8: HEAP[mwin.exe]:
>>>>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>>
>>>>> #10: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #11: HEAP[mwin.exe]:
>>>>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #13: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #14: HEAP[mwin.exe]:
>>>>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #16: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #17: HEAP[mwin.exe]:
>>>>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #19: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #20: HEAP[mwin.exe]:
>>>>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #22: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #23: HEAP[mwin.exe]:
>>>>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #25: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #26: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #27: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #28: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #29: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #30: HEAP[mwin.exe]:
>>>>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #32: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #33: HEAP[mwin.exe]:
>>>>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #35: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #36: HEAP[mwin.exe]:
>>>>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> Any idea what's wrong with my code?
>>>>>
>>>>> Thanks in advance
>>>>>
>>>>> Ingo
>>>>
>>>>
>>>
>>
>>
>
> If you really want a list of the bugs please take a look at this ng
> - AnsiToOem()
> - Preview
> - TReport
> - TLabel
> - Xailer.res
> - TIni:GetSection
> - TDbfDataSet
> - TDBBrowse
Sorry, but you are certenly unfair with your critics. I am sure almost none
of your bugs reported were critic and some of them are just cosmetic issues.
It seems you have forgot that you boughht a PRE-RELEASE version and BTW any
of your questions has been asnwered and corrected in record time.
> Sorry, without the sourcecode of Xailer I can not see how the mm to pixel
> conversion works. I can only tell you what happened. Maybe I can separate
> this part of my application when I finished it but now I have a lot of
> work
> in front of me.
Up to you. Other guys have no problem making a small sample that we can
reproduce to fix our bugs. I hope you find the bug yourself, if you haven't
do it yet.
> I'm yearning for the new (and fixed) release maybe it will be looking
> better.
I really expect so, but if it does not, be free to ask for a refund.
Best regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:440d98ba$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> you're asking for a list of the bugs I found?
>
> I informed you about them here and in the public ng. Remember sometimes I
> had to write again and again to convince you that there was a bug in
> Xailer
> and not a mistake by myself.
>
> I decided me on Xailer because I'm still the meaning that it is the best
> developing environment for all the xBase-developers especially the one
> coming
> from FiveWin. But beside the time I need to learn the new dev.-environment
> I must spend much time to find out if it is a bug in Xailer or a bug in my
> code when something was going wrong here even though it is working in the
> 16-bit application.
>
> If you really want a list of the bugs please take a look at this ng
> - AnsiToOem()
> - Preview
> - TReport
> - TLabel
> - Xailer.res
> - TIni:GetSection
> - TDbfDataSet
> - TDBBrowse
>
> for example, but I hope it was only a rhetoric question of you.
>
> The printer problem I could only locate in the line of the conversion
> call.
> Sorry, without the sourcecode of Xailer I can not see how the mm to pixel
> conversion works. I can only tell you what happened. Maybe I can separate
> this part of my application when I finished it but now I have a lot of
> work
> in front of me.
>
> I'm yearning for the new (and fixed) release maybe it will be looking
> better.
>
> Regards
>
> Ingo
>
> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>Ingo,
>>
>>> now I have more problems with the bugs in Xailer than with transfering
> my
>>> sourcecode.
>>
>>Please, would you mind to give a list of those bugs. I will highly
>>appreciate your feedback. We know that moving to a new developing
>>environment is not easy, but please be patient and give your self the time
>
>>to learn Xailer
>>
>>> The error must be caused in the line of converting cm to pixel and as
> I
>>> found
>>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
> is
>>> that it happens not every time.
>>
>>I guess you are wrong, the routine for converting cm to pixels DOES NOT
>
>>CALL ABSOLUTELY any API function, IS JUST A BUNCH OF ARITHMETICAL
>>CALCULATIONS. So I guess the problem is not there. BTW, if you are able
> to
>>reproduce your bug on a simply application we will be glad to do some
>>research.
>>
>>Regards,
>>
>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>
>>news:440d647a$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>
>>> Ignacio,
>>>
>>> the lines with ProcessMessages() are one try to workaround. I deleted
>
>>> them.
>>> Mwin.exe is the project I'm building with Xailer and it was running from
>>> the IDE when the error occured. It is not a 'malicious' software. It is
>
>>> the
>>> 16-bit software I'm trying to convert from FW16 to 32 bit by Xailer.
>>> Till
>>> now I have more problems with the bugs in Xailer than with transfering
> my
>>> sourcecode.
>>>
>>> The error must be caused in the line of converting cm to pixel and as
> I
>>> found
>>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
> is
>>> that it happens not every time.
>>>
>>> I had hoped the problem is known by otherones but nevertheless thanks
> for
>>> answering.
>>>
>>> Ingo
>>>
>>> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>>>Ingo,
>>>>
>>>>I highly recommend to take off those ProcessMessages(), but I do not
>>>>think
>>>
>>>>that are the cause of those LogDebug lines.
>>>>
>>>>Be aware that the LogDebug() mechanism built in Xailer is just a
>>>>connection
>>>
>>>>with the standart OutputDebugString() API function that is internally
> used
>>>
>>>>by a lot of software, and even Windows itself. In your case, I almost
> sure
>>>
>>>>that those lines are not generated by Xailer, but by a 'mwin.exe'
>>>>program
>>>
>>>>that it seems to be malicous software.
>>>>
>>>>http://www.bleepingcomputer.com/startup ... -7941.html
>>>>
>>>>Best regards,
>>>>
>>>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el
>>>>mensaje
>>>
>>>>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>>>
>>>>> Hi,
>>>>>
>>>>> after selecting the printer I'm converting the array with the print
>>>>> positions
>>>>> from cm to pixels with the following code
>>>>>
>>>>> WITH OBJECT Printer:oCanvas
>>>>> :oFont:=oFont
>>>>> :nMapMode:=mmHIMETRICS
>>>>> ProcessMessages()
>>>>> For nX:=1 TO LEN(aPos)
>>>>>
>>>>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>>>>> ProcessMessages()
>>>>> next
>>>>> :nMapMode:=mmPIXELS
>>>>> END WITH
>>>>>
>>>>> aPos is STATIC
>>>>> aPix is LOCAL
>>>>> Sometimes - not always - I got the GPF as shown in the picture and the
>>>
>>>>> following
>>>>> LogDebug lines
>>>>>
>>>>> #1: HEAP[mwin.exe]:
>>>>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size
> of
>>> dc
>>>>>
>>>>> #3: HEAP[mwin.exe]:
>>>>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>>>>
>>>>> #5: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #6: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #7: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #8: HEAP[mwin.exe]:
>>>>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>>
>>>>> #10: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #11: HEAP[mwin.exe]:
>>>>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #13: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #14: HEAP[mwin.exe]:
>>>>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #16: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #17: HEAP[mwin.exe]:
>>>>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #19: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #20: HEAP[mwin.exe]:
>>>>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #22: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #23: HEAP[mwin.exe]:
>>>>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #25: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #26: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #27: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #28: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #29: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #30: HEAP[mwin.exe]:
>>>>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #32: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #33: HEAP[mwin.exe]:
>>>>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #35: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #36: HEAP[mwin.exe]:
>>>>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> Any idea what's wrong with my code?
>>>>>
>>>>> Thanks in advance
>>>>>
>>>>> Ingo
>>>>
>>>>
>>>
>>
>>
>
Print problem
Ingo,
> If you really want a list of the bugs please take a look at this ng
> - AnsiToOem()
> - Preview
> - TReport
> - TLabel
> - Xailer.res
> - TIni:GetSection
> - TDbfDataSet
> - TDBBrowse
Sorry, but you are certenly unfair with your critics. I am sure almost none
of your bugs reported were critic and some of them are just cosmetic issues.
It seems you have forgot that you boughht a PRE-RELEASE version and BTW any
of your questions has been asnwered and corrected in record time.
> Sorry, without the sourcecode of Xailer I can not see how the mm to pixel
> conversion works. I can only tell you what happened. Maybe I can separate
> this part of my application when I finished it but now I have a lot of
> work
> in front of me.
Up to you. Other guys have no problem making a small sample that we can
reproduce to fix our bugs. I hope you find the bug yourself, if you haven't
do it yet.
> I'm yearning for the new (and fixed) release maybe it will be looking
> better.
I really expect so, but if it does not, be free to ask for a refund.
Best regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:440d98ba$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> you're asking for a list of the bugs I found?
>
> I informed you about them here and in the public ng. Remember sometimes I
> had to write again and again to convince you that there was a bug in
> Xailer
> and not a mistake by myself.
>
> I decided me on Xailer because I'm still the meaning that it is the best
> developing environment for all the xBase-developers especially the one
> coming
> from FiveWin. But beside the time I need to learn the new dev.-environment
> I must spend much time to find out if it is a bug in Xailer or a bug in my
> code when something was going wrong here even though it is working in the
> 16-bit application.
>
> If you really want a list of the bugs please take a look at this ng
> - AnsiToOem()
> - Preview
> - TReport
> - TLabel
> - Xailer.res
> - TIni:GetSection
> - TDbfDataSet
> - TDBBrowse
>
> for example, but I hope it was only a rhetoric question of you.
>
> The printer problem I could only locate in the line of the conversion
> call.
> Sorry, without the sourcecode of Xailer I can not see how the mm to pixel
> conversion works. I can only tell you what happened. Maybe I can separate
> this part of my application when I finished it but now I have a lot of
> work
> in front of me.
>
> I'm yearning for the new (and fixed) release maybe it will be looking
> better.
>
> Regards
>
> Ingo
>
> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>Ingo,
>>
>>> now I have more problems with the bugs in Xailer than with transfering
> my
>>> sourcecode.
>>
>>Please, would you mind to give a list of those bugs. I will highly
>>appreciate your feedback. We know that moving to a new developing
>>environment is not easy, but please be patient and give your self the time
>
>>to learn Xailer
>>
>>> The error must be caused in the line of converting cm to pixel and as
> I
>>> found
>>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
> is
>>> that it happens not every time.
>>
>>I guess you are wrong, the routine for converting cm to pixels DOES NOT
>
>>CALL ABSOLUTELY any API function, IS JUST A BUNCH OF ARITHMETICAL
>>CALCULATIONS. So I guess the problem is not there. BTW, if you are able
> to
>>reproduce your bug on a simply application we will be glad to do some
>>research.
>>
>>Regards,
>>
>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>
>>news:440d647a$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>
>>> Ignacio,
>>>
>>> the lines with ProcessMessages() are one try to workaround. I deleted
>
>>> them.
>>> Mwin.exe is the project I'm building with Xailer and it was running from
>>> the IDE when the error occured. It is not a 'malicious' software. It is
>
>>> the
>>> 16-bit software I'm trying to convert from FW16 to 32 bit by Xailer.
>>> Till
>>> now I have more problems with the bugs in Xailer than with transfering
> my
>>> sourcecode.
>>>
>>> The error must be caused in the line of converting cm to pixel and as
> I
>>> found
>>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
> is
>>> that it happens not every time.
>>>
>>> I had hoped the problem is known by otherones but nevertheless thanks
> for
>>> answering.
>>>
>>> Ingo
>>>
>>> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>>>Ingo,
>>>>
>>>>I highly recommend to take off those ProcessMessages(), but I do not
>>>>think
>>>
>>>>that are the cause of those LogDebug lines.
>>>>
>>>>Be aware that the LogDebug() mechanism built in Xailer is just a
>>>>connection
>>>
>>>>with the standart OutputDebugString() API function that is internally
> used
>>>
>>>>by a lot of software, and even Windows itself. In your case, I almost
> sure
>>>
>>>>that those lines are not generated by Xailer, but by a 'mwin.exe'
>>>>program
>>>
>>>>that it seems to be malicous software.
>>>>
>>>>http://www.bleepingcomputer.com/startup ... -7941.html
>>>>
>>>>Best regards,
>>>>
>>>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el
>>>>mensaje
>>>
>>>>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>>>
>>>>> Hi,
>>>>>
>>>>> after selecting the printer I'm converting the array with the print
>>>>> positions
>>>>> from cm to pixels with the following code
>>>>>
>>>>> WITH OBJECT Printer:oCanvas
>>>>> :oFont:=oFont
>>>>> :nMapMode:=mmHIMETRICS
>>>>> ProcessMessages()
>>>>> For nX:=1 TO LEN(aPos)
>>>>>
>>>>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>>>>> ProcessMessages()
>>>>> next
>>>>> :nMapMode:=mmPIXELS
>>>>> END WITH
>>>>>
>>>>> aPos is STATIC
>>>>> aPix is LOCAL
>>>>> Sometimes - not always - I got the GPF as shown in the picture and the
>>>
>>>>> following
>>>>> LogDebug lines
>>>>>
>>>>> #1: HEAP[mwin.exe]:
>>>>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size
> of
>>> dc
>>>>>
>>>>> #3: HEAP[mwin.exe]:
>>>>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>>>>
>>>>> #5: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #6: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #7: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #8: HEAP[mwin.exe]:
>>>>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>>
>>>>> #10: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #11: HEAP[mwin.exe]:
>>>>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #13: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #14: HEAP[mwin.exe]:
>>>>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #16: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #17: HEAP[mwin.exe]:
>>>>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #19: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #20: HEAP[mwin.exe]:
>>>>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #22: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #23: HEAP[mwin.exe]:
>>>>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #25: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #26: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #27: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #28: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #29: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #30: HEAP[mwin.exe]:
>>>>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #32: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #33: HEAP[mwin.exe]:
>>>>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #35: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #36: HEAP[mwin.exe]:
>>>>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> Any idea what's wrong with my code?
>>>>>
>>>>> Thanks in advance
>>>>>
>>>>> Ingo
>>>>
>>>>
>>>
>>
>>
>
> If you really want a list of the bugs please take a look at this ng
> - AnsiToOem()
> - Preview
> - TReport
> - TLabel
> - Xailer.res
> - TIni:GetSection
> - TDbfDataSet
> - TDBBrowse
Sorry, but you are certenly unfair with your critics. I am sure almost none
of your bugs reported were critic and some of them are just cosmetic issues.
It seems you have forgot that you boughht a PRE-RELEASE version and BTW any
of your questions has been asnwered and corrected in record time.
> Sorry, without the sourcecode of Xailer I can not see how the mm to pixel
> conversion works. I can only tell you what happened. Maybe I can separate
> this part of my application when I finished it but now I have a lot of
> work
> in front of me.
Up to you. Other guys have no problem making a small sample that we can
reproduce to fix our bugs. I hope you find the bug yourself, if you haven't
do it yet.
> I'm yearning for the new (and fixed) release maybe it will be looking
> better.
I really expect so, but if it does not, be free to ask for a refund.
Best regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:440d98ba$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> you're asking for a list of the bugs I found?
>
> I informed you about them here and in the public ng. Remember sometimes I
> had to write again and again to convince you that there was a bug in
> Xailer
> and not a mistake by myself.
>
> I decided me on Xailer because I'm still the meaning that it is the best
> developing environment for all the xBase-developers especially the one
> coming
> from FiveWin. But beside the time I need to learn the new dev.-environment
> I must spend much time to find out if it is a bug in Xailer or a bug in my
> code when something was going wrong here even though it is working in the
> 16-bit application.
>
> If you really want a list of the bugs please take a look at this ng
> - AnsiToOem()
> - Preview
> - TReport
> - TLabel
> - Xailer.res
> - TIni:GetSection
> - TDbfDataSet
> - TDBBrowse
>
> for example, but I hope it was only a rhetoric question of you.
>
> The printer problem I could only locate in the line of the conversion
> call.
> Sorry, without the sourcecode of Xailer I can not see how the mm to pixel
> conversion works. I can only tell you what happened. Maybe I can separate
> this part of my application when I finished it but now I have a lot of
> work
> in front of me.
>
> I'm yearning for the new (and fixed) release maybe it will be looking
> better.
>
> Regards
>
> Ingo
>
> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>Ingo,
>>
>>> now I have more problems with the bugs in Xailer than with transfering
> my
>>> sourcecode.
>>
>>Please, would you mind to give a list of those bugs. I will highly
>>appreciate your feedback. We know that moving to a new developing
>>environment is not easy, but please be patient and give your self the time
>
>>to learn Xailer
>>
>>> The error must be caused in the line of converting cm to pixel and as
> I
>>> found
>>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
> is
>>> that it happens not every time.
>>
>>I guess you are wrong, the routine for converting cm to pixels DOES NOT
>
>>CALL ABSOLUTELY any API function, IS JUST A BUNCH OF ARITHMETICAL
>>CALCULATIONS. So I guess the problem is not there. BTW, if you are able
> to
>>reproduce your bug on a simply application we will be glad to do some
>>research.
>>
>>Regards,
>>
>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>
>>news:440d647a$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>
>>> Ignacio,
>>>
>>> the lines with ProcessMessages() are one try to workaround. I deleted
>
>>> them.
>>> Mwin.exe is the project I'm building with Xailer and it was running from
>>> the IDE when the error occured. It is not a 'malicious' software. It is
>
>>> the
>>> 16-bit software I'm trying to convert from FW16 to 32 bit by Xailer.
>>> Till
>>> now I have more problems with the bugs in Xailer than with transfering
> my
>>> sourcecode.
>>>
>>> The error must be caused in the line of converting cm to pixel and as
> I
>>> found
>>> out now it occurs if Canon Pixma iP 4000 is selected. The difficulty
> is
>>> that it happens not every time.
>>>
>>> I had hoped the problem is known by otherones but nevertheless thanks
> for
>>> answering.
>>>
>>> Ingo
>>>
>>> "Ignacio Ortiz de Zúñiga" <NoName@xailer.com> wrote:
>>>>Ingo,
>>>>
>>>>I highly recommend to take off those ProcessMessages(), but I do not
>>>>think
>>>
>>>>that are the cause of those LogDebug lines.
>>>>
>>>>Be aware that the LogDebug() mechanism built in Xailer is just a
>>>>connection
>>>
>>>>with the standart OutputDebugString() API function that is internally
> used
>>>
>>>>by a lot of software, and even Windows itself. In your case, I almost
> sure
>>>
>>>>that those lines are not generated by Xailer, but by a 'mwin.exe'
>>>>program
>>>
>>>>that it seems to be malicous software.
>>>>
>>>>http://www.bleepingcomputer.com/startup ... -7941.html
>>>>
>>>>Best regards,
>>>>
>>>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el
>>>>mensaje
>>>
>>>>news:440d4d7d$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>>>
>>>>> Hi,
>>>>>
>>>>> after selecting the printer I'm converting the array with the print
>>>>> positions
>>>>> from cm to pixels with the following code
>>>>>
>>>>> WITH OBJECT Printer:oCanvas
>>>>> :oFont:=oFont
>>>>> :nMapMode:=mmHIMETRICS
>>>>> ProcessMessages()
>>>>> For nX:=1 TO LEN(aPos)
>>>>>
>>>>> aPix[nX]:=:PointToPixels((aPos[nX,2]*100)+nLeft,(aPos[nX,1]* 100)+nTop)
>>>>> ProcessMessages()
>>>>> next
>>>>> :nMapMode:=mmPIXELS
>>>>> END WITH
>>>>>
>>>>> aPos is STATIC
>>>>> aPix is LOCAL
>>>>> Sometimes - not always - I got the GPF as shown in the picture and the
>>>
>>>>> following
>>>>> LogDebug lines
>>>>>
>>>>> #1: HEAP[mwin.exe]:
>>>>> #2: Heap block at 0019F0B0 modified at 0019F194 past requested size
> of
>>> dc
>>>>>
>>>>> #3: HEAP[mwin.exe]:
>>>>> #4: Invalid Address specified to RtlFreeHeap( 00150000, 0019F0B8 )
>>>>>
>>>>> #5: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #6: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #7: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #8: HEAP[mwin.exe]:
>>>>> #9: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was freed
>>>>>
>>>>> #10: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #11: HEAP[mwin.exe]:
>>>>> #12: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #13: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #14: HEAP[mwin.exe]:
>>>>> #15: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #16: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #17: HEAP[mwin.exe]:
>>>>> #18: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #19: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #20: HEAP[mwin.exe]:
>>>>> #21: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #22: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #23: HEAP[mwin.exe]:
>>>>> #24: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #25: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #26: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #27: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #28: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #29: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #30: HEAP[mwin.exe]:
>>>>> #31: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #32: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #33: HEAP[mwin.exe]:
>>>>> #34: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> #35: Heap corruption detected at 0019F1B0
>>>>>
>>>>> #36: HEAP[mwin.exe]:
>>>>> #37: HEAP: Free Heap block 19f1a8 modified at 19f1b8 after it was
>>>>> freed
>>>>>
>>>>> Any idea what's wrong with my code?
>>>>>
>>>>> Thanks in advance
>>>>>
>>>>> Ingo
>>>>
>>>>
>>>
>>
>>
>
Print problem
Ingo, Ignacio,
please, let's calm down.
Ingo, I'm certainly sure that Xailer has had several bugs, and I'm sure too
that all of them will be fixed. There is no product of software fully free
of bugs. However, we are doing a hard job trying to make Xailer the most
stable, solid and productive development tool for xbase. And I belive that
it is so, even while Xailer is still a pre-release.
Respecting the printing problem, those messages are not generated by Xailer,
neither by xHarbour. I've searched along all Xailer's and xHarbour's source
files (even inside all BCC libraries), and there are no such messages at
all. They are generated *for sure* by the printer driver. Please, test the
same code using another printer and tell me the result. Even, try to update
that driver.
ITOH, it's possible to cause a "printer driver exception" from our code, but
I'm almost sure that this is not the case. Moreover, I cannot understand how
calling ProcessMessages() can avoid the problem.
--
Regards,
Jose F. Gimenez
please, let's calm down.
Ingo, I'm certainly sure that Xailer has had several bugs, and I'm sure too
that all of them will be fixed. There is no product of software fully free
of bugs. However, we are doing a hard job trying to make Xailer the most
stable, solid and productive development tool for xbase. And I belive that
it is so, even while Xailer is still a pre-release.
Respecting the printing problem, those messages are not generated by Xailer,
neither by xHarbour. I've searched along all Xailer's and xHarbour's source
files (even inside all BCC libraries), and there are no such messages at
all. They are generated *for sure* by the printer driver. Please, test the
same code using another printer and tell me the result. Even, try to update
that driver.
ITOH, it's possible to cause a "printer driver exception" from our code, but
I'm almost sure that this is not the case. Moreover, I cannot understand how
calling ProcessMessages() can avoid the problem.
--
Regards,
Jose F. Gimenez
Print problem
Ingo, Ignacio,
please, let's calm down.
Ingo, I'm certainly sure that Xailer has had several bugs, and I'm sure too
that all of them will be fixed. There is no product of software fully free
of bugs. However, we are doing a hard job trying to make Xailer the most
stable, solid and productive development tool for xbase. And I belive that
it is so, even while Xailer is still a pre-release.
Respecting the printing problem, those messages are not generated by Xailer,
neither by xHarbour. I've searched along all Xailer's and xHarbour's source
files (even inside all BCC libraries), and there are no such messages at
all. They are generated *for sure* by the printer driver. Please, test the
same code using another printer and tell me the result. Even, try to update
that driver.
ITOH, it's possible to cause a "printer driver exception" from our code, but
I'm almost sure that this is not the case. Moreover, I cannot understand how
calling ProcessMessages() can avoid the problem.
--
Regards,
Jose F. Gimenez
please, let's calm down.
Ingo, I'm certainly sure that Xailer has had several bugs, and I'm sure too
that all of them will be fixed. There is no product of software fully free
of bugs. However, we are doing a hard job trying to make Xailer the most
stable, solid and productive development tool for xbase. And I belive that
it is so, even while Xailer is still a pre-release.
Respecting the printing problem, those messages are not generated by Xailer,
neither by xHarbour. I've searched along all Xailer's and xHarbour's source
files (even inside all BCC libraries), and there are no such messages at
all. They are generated *for sure* by the printer driver. Please, test the
same code using another printer and tell me the result. Even, try to update
that driver.
ITOH, it's possible to cause a "printer driver exception" from our code, but
I'm almost sure that this is not the case. Moreover, I cannot understand how
calling ProcessMessages() can avoid the problem.
--
Regards,
Jose F. Gimenez
-
Ingo Junge-Herrmann
- Mensajes: 339
- Registrado: Lun Jul 02, 2007 7:17 pm
Print problem
Jose,
the problem occurs only with the Canon Pixma IP4000. An other Canon printer
I haven't. With my Lexmark - no problem. With my HP Laserjet - no prblem.
With my HP Officejet - no problem.
The driver is the actual driver vers. 1.8.
To test it yourself you can download the driver from
http://es.software.canon-europe.com/Pri ... e_Jet_Prin ters/PIXMA_iP400010095.asp
I attach a sample.
Run the sample from the IDE. Click on the "print" button and select the installed
IP4000. After closing the preview, clicking on "print" again and selecting
the IP4000 the following message is here shown in the debug window:
#1: HEAP[testprint.exe]:
#2: Heap block at 00169D88 modified at 00169E6C past requested size of dc
#3: HEAP[testprint.exe]:
#4: Invalid Address specified to RtlFreeHeap( 00150000, 00169D90 )
If you run the sample outside the IDE it works very well.
Regards
Ingo
--
Attached files testprint.zip (2.3 KB)Â
-
Ingo Junge-Herrmann
- Mensajes: 339
- Registrado: Lun Jul 02, 2007 7:17 pm
Print problem
Jose,
the problem occurs only with the Canon Pixma IP4000. An other Canon printer
I haven't. With my Lexmark - no problem. With my HP Laserjet - no prblem.
With my HP Officejet - no problem.
The driver is the actual driver vers. 1.8.
To test it yourself you can download the driver from
http://es.software.canon-europe.com/Pri ... e_Jet_Prin ters/PIXMA_iP400010095.asp
I attach a sample.
Run the sample from the IDE. Click on the "print" button and select the installed
IP4000. After closing the preview, clicking on "print" again and selecting
the IP4000 the following message is here shown in the debug window:
#1: HEAP[testprint.exe]:
#2: Heap block at 00169D88 modified at 00169E6C past requested size of dc
#3: HEAP[testprint.exe]:
#4: Invalid Address specified to RtlFreeHeap( 00150000, 00169D90 )
If you run the sample outside the IDE it works very well.
Regards
Ingo
--
Attached files testprint.zip (2.3 KB)Â
Print problem
Ingo,
sorry for the delay; i was in a travel yesterday. I hope the problem is
solved and all works fine now.
--
Regards,
Jose F. Gimenez
sorry for the delay; i was in a travel yesterday. I hope the problem is
solved and all works fine now.
--
Regards,
Jose F. Gimenez
Print problem
Ingo,
sorry for the delay; i was in a travel yesterday. I hope the problem is
solved and all works fine now.
--
Regards,
Jose F. Gimenez
sorry for the delay; i was in a travel yesterday. I hope the problem is
solved and all works fine now.
--
Regards,
Jose F. Gimenez
-
Ingo Junge-Herrmann
- Mensajes: 339
- Registrado: Lun Jul 02, 2007 7:17 pm
Print problem
Jose,
Ignacio has solved the problem. With the new obj's he attached his post from
the 8th the project runs now from the IDE without the reported error when
printing on Canon printers.
Thanks for the request
Ingo
Ignacio has solved the problem. With the new obj's he attached his post from
the 8th the project runs now from the IDE without the reported error when
printing on Canon printers.
Thanks for the request
Ingo
-
Ingo Junge-Herrmann
- Mensajes: 339
- Registrado: Lun Jul 02, 2007 7:17 pm
Print problem
Jose,
Ignacio has solved the problem. With the new obj's he attached his post from
the 8th the project runs now from the IDE without the reported error when
printing on Canon printers.
Thanks for the request
Ingo
Ignacio has solved the problem. With the new obj's he attached his post from
the 8th the project runs now from the IDE without the reported error when
printing on Canon printers.
Thanks for the request
Ingo