Alaska Software Inc. - printerspooler after migration
Username: Password:
AuthorTopic: printerspooler after migration
RCBprinterspooler after migration
on Mon, 05 Apr 2010 19:17:16 +0200
hello,
1.
after i migrated an old clipperprogramm into xbase++ (nongui) all worked ok
but : printing started only after quitting the programm. I tried all sorts 
of printersettings and avoided processoroverloads -but nothing helped. Iam 
using printersequences for LQ850 direct to LPT1.
2. i was not used to getting an XPPFATAL-LOG all the time - is that the 
normal answer for all sorts of errors in a migrated nongui-system ? Is there 
any better error.prg in use ?
Would be nice to hear from any migrating-expert 
Rainer
James Loughner Re: printerspooler after migration
on Mon, 05 Apr 2010 13:34:14 -0400
1) how are you printing? ie what commands. It sounds like you are not
shutting down the printing correctly when the report is done and it is
stuck in the Windows spooler which is then released when you quit.

2) A fatal error is one that is basiclly unknown to the error system. It
can be caused by an error in the error handler that cause recursion.
Post some examples.

Jim



On 04/05/2010 01:17 PM, RCB wrote:
> hello,
> 1.
> after i migrated an old clipperprogramm into xbase++ (nongui) all worked ok
> but : printing started only after quitting the programm. I tried all sorts 
> of printersettings and avoided processoroverloads -but nothing helped. Iam 
> using printersequences for LQ850 direct to LPT1.
> 2. i was not used to getting an XPPFATAL-LOG all the time - is that the 
> normal answer for all sorts of errors in a migrated nongui-system ? Is there 
> any better error.prg in use ?
> Would be nice to hear from any migrating-expert 
> Rainer 
> 
>
RCBRe: printerspooler after migration
on Mon, 05 Apr 2010 22:04:51 +0200
hi James ...you are right : i forgot to close the job ..
Thank you ...
for example : a fieldname of a database was wrong ... XPPFATALERROR
and other simple things ... I used the alaska error-file ....
What I noticed is a xtimes recursion ... sort of endless file g
I try to send an example ..
Rainer

"James Loughner" <jwrl@suddenlink.net> schrieb im Newsbeitrag 
news:4aee07f0$189afb5c$5eb13@news.alaska-software.com...
> 1) how are you printing? ie what commands. It sounds like you are not
> shutting down the printing correctly when the report is done and it is
> stuck in the Windows spooler which is then released when you quit.
>
> 2) A fatal error is one that is basiclly unknown to the error system. It
> can be caused by an error in the error handler that cause recursion.
> Post some examples.
>
> Jim
>
>
>
> On 04/05/2010 01:17 PM, RCB wrote:
>> hello,
>> 1.
>> after i migrated an old clipperprogramm into xbase++ (nongui) all worked 
>> ok
>> but : printing started only after quitting the programm. I tried all 
>> sorts
>> of printersettings and avoided processoroverloads -but nothing helped. 
>> Iam
>> using printersequences for LQ850 direct to LPT1.
>> 2. i was not used to getting an XPPFATAL-LOG all the time - is that the
>> normal answer for all sorts of errors in a migrated nongui-system ? Is 
>> there
>> any better error.prg in use ?
>> Would be nice to hear from any migrating-expert 
>> Rainer
>>
>>
>
RCBRe: printerspooler after migration
on Mon, 05 Apr 2010 22:29:43 +0200
hi James,
i added one of these fatal logs from which i dont understand why they are 
showing in this way .. May be you have the answer ...
Thanks ...
Rainer
"James Loughner" <jwrl@suddenlink.net> schrieb im Newsbeitrag 
news:4aee07f0$189afb5c$5eb13@news.alaska-software.com...
> 1) how are you printing? ie what commands. It sounds like you are not
> shutting down the printing correctly when the report is done and it is
> stuck in the Windows spooler which is then released when you quit.
>
> 2) A fatal error is one that is basiclly unknown to the error system. It
> can be caused by an error in the error handler that cause recursion.
> Post some examples.
>
> Jim
>
>
>
> On 04/05/2010 01:17 PM, RCB wrote:
>> hello,
>> 1.
>> after i migrated an old clipperprogramm into xbase++ (nongui) all worked 
>> ok
>> but : printing started only after quitting the programm. I tried all 
>> sorts
>> of printersettings and avoided processoroverloads -but nothing helped. 
>> Iam
>> using printersequences for LQ850 direct to LPT1.
>> 2. i was not used to getting an XPPFATAL-LOG all the time - is that the
>> normal answer for all sorts of errors in a migrated nongui-system ? Is 
>> there
>> any better error.prg in use ?
>> Would be nice to hear from any migrating-expert 
>> Rainer
>>
>>
> 




XPPFATAL.LOG
XPPFATAL.LOG
James Loughner Re: printerspooler after migration
on Mon, 05 Apr 2010 17:12:10 -0400
Fatals are tricky because they often don't show exactly what happened
but this time look at MIKRO(53) My bet there is a divide by 0 here. but
it might be something else. What ever, it caused an error in the error
handler and caused a recursion and stack overflow.

You are using the default Xbase++ error handler and not an old one from
Clipper days???

Jim

On 04/05/2010 04:29 PM, RCB wrote:
> hi James,
> i added one of these fatal logs from which i dont understand why they are 
> showing in this way .. May be you have the answer ...
> Thanks ...
> Rainer
> "James Loughner" <jwrl@suddenlink.net> schrieb im Newsbeitrag 
> news:4aee07f0$189afb5c$5eb13@news.alaska-software.com...
>> 1) how are you printing? ie what commands. It sounds like you are not
>> shutting down the printing correctly when the report is done and it is
>> stuck in the Windows spooler which is then released when you quit.
>>
>> 2) A fatal error is one that is basiclly unknown to the error system. It
>> can be caused by an error in the error handler that cause recursion.
>> Post some examples.
>>
>> Jim
>>
>>
>>
>> On 04/05/2010 01:17 PM, RCB wrote:
>>> hello,
>>> 1.
>>> after i migrated an old clipperprogramm into xbase++ (nongui) all worked 
>>> ok
>>> but : printing started only after quitting the programm. I tried all 
>>> sorts
>>> of printersettings and avoided processoroverloads -but nothing helped. 
>>> Iam
>>> using printersequences for LQ850 direct to LPT1.
>>> 2. i was not used to getting an XPPFATAL-LOG all the time - is that the
>>> normal answer for all sorts of errors in a migrated nongui-system ? Is 
>>> there
>>> any better error.prg in use ?
>>> Would be nice to hear from any migrating-expert 
>>> Rainer
>>>
>>>
>>
> 
>
RCBerrorsys
on Tue, 06 Apr 2010 10:42:43 +0200
James ...well - its the new errosrsys.prg from alaska - and in this case -to 
trigger it-  ... i changed the name of a var which was in consequennce not 
longer existent for the programm. What ever happens as error :example : 
wrong path and others : i allways have these recursions and allways 
fatal-logs.  Do i make the wrong implementation in main ?
.....
set path to ((cRootDir)+";"+(cImpDir))
errorsys()
.......

Rainer

"James Loughner" <jwrl@suddenlink.net> schrieb im Newsbeitrag 
news:59662c8d$334772c0$5e676@news.alaska-software.com...
> Fatals are tricky because they often don't show exactly what happened
> but this time look at MIKRO(53) My bet there is a divide by 0 here. but
> it might be something else. What ever, it caused an error in the error
> handler and caused a recursion and stack overflow.
>
> You are using the default Xbase++ error handler and not an old one from
> Clipper days???
>
> Jim
>
> On 04/05/2010 04:29 PM, RCB wrote:
>> hi James,
>> i added one of these fatal logs from which i dont understand why they are
>> showing in this way .. May be you have the answer ...
>> Thanks ...
>> Rainer
>> "James Loughner" <jwrl@suddenlink.net> schrieb im Newsbeitrag
>> news:4aee07f0$189afb5c$5eb13@news.alaska-software.com...
>>> 1) how are you printing? ie what commands. It sounds like you are not
>>> shutting down the printing correctly when the report is done and it is
>>> stuck in the Windows spooler which is then released when you quit.
>>>
>>> 2) A fatal error is one that is basiclly unknown to the error system. It
>>> can be caused by an error in the error handler that cause recursion.
>>> Post some examples.
>>>
>>> Jim
>>>
>>>
>>>
>>> On 04/05/2010 01:17 PM, RCB wrote:
>>>> hello,
>>>> 1.
>>>> after i migrated an old clipperprogramm into xbase++ (nongui) all 
>>>> worked
>>>> ok
>>>> but : printing started only after quitting the programm. I tried all
>>>> sorts
>>>> of printersettings and avoided processoroverloads -but nothing helped.
>>>> Iam
>>>> using printersequences for LQ850 direct to LPT1.
>>>> 2. i was not used to getting an XPPFATAL-LOG all the time - is that the
>>>> normal answer for all sorts of errors in a migrated nongui-system ? Is
>>>> there
>>>> any better error.prg in use ?
>>>> Would be nice to hear from any migrating-expert 
>>>> Rainer
>>>>
>>>>
>>>
>>
>>
> 




ERRORSYS.PRG
ERRORSYS.PRG
Andreas Gehrs-Pahl
Re: errorsys
on Tue, 06 Apr 2010 05:52:47 -0400
Rainer,

>James ...well - its the new errosrsys.prg from alaska - and in this case -to 
>trigger it- ... i changed the name of a var which was in consequennce not 
>longer existent for the programm. What ever happens as error :example : 
>wrong path and others : i allways have these recursions and allways 
>fatal-logs. Do i make the wrong implementation in main ?
> .....
> set path to ((cRootDir)+";"+(cImpDir))
> errorsys()

There are several issues here. First, you don't have to call "ErrorSys()"
in your Main() program. This routine, like AppSys(), DbeSys(), etc. is
called automatically before Main() is called. You should never call any
of the Init or Exit Procedures directly in your code!

Secondly, the "XppFatal.log" that you included in one of your posts 
doesn't match the "ErrorSys.prg" file that you also posted. You always 
get an "XppFatal.log", because there is an error in your (actual) Error 
Handler program, specifically in line 210 of the routine ErrorMessage().

>ERRORMESSAGE(210)
>DEFERROR(99)
>(B)ERRORSYS@0000(38)

Your actual ErrorSys() routine defines the ErrorBlock() in line 38, 
while the "ErrorSys.prg" file that you posted does this in line 52. 
Also, the function that calls the ErrorMessage() routine is called 
"StandardEH()" and not "DefError()" as shown in your "XppFatal.log". 
In addition, the "ErrorMessage()" routine in the posted file starts in 
line 235, while your error happens in line 210, which is before that 
routine begins.

Whatever is in line 210 of your actually used "ErrorMessage()" routine 
is causing the recursive error, and that's where you should look. Check
your source code for any of the above mentioned routines, and if you 
can't find the problem in line 210, post the code here, and we might be
able to help. You have definitely overloaded the default Error Handler, 
and that is the reason for your issues!

-- Andreas

---                                                                      ---
  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
  415 Gute Street                     or: Andreas@DDPSoftware.com
  Owosso, MI 48867-4410               or: Andreas_Gehrs-Pahl@CrimeCog.com
  Tel: (989) 723-9927           Web Site: http://www.Aerospace-History.net
---                                                                      ---
RCBRe: errorsys
on Tue, 06 Apr 2010 13:38:18 +0200
hi Andreas,
thanks for the hint - I removed the call in main - but :
I added the original errorsys.prg from Alaska, which came over with SL1 
(folder \SYS) and added this into my project-file.
I triggered again by making a var-mistake which was announced by my old 
clipper errorssys with "unknown var" and a short message of modules ...
What happened is what you see in the attachment. hmmm ...so what is wrong ?
Thanks for thinking about it ...
Rainer

<Andreas Gehrs-Pahl> schrieb im Newsbeitrag 
news:vmf23zpgnf7j.1bqmbad9ine38.dlg@40tude.net...
> Rainer,
>
>>James ...well - its the new errosrsys.prg from alaska - and in this 
>>case -to
>>trigger it- ... i changed the name of a var which was in consequennce not
>>longer existent for the programm. What ever happens as error :example :
>>wrong path and others : i allways have these recursions and allways
>>fatal-logs. Do i make the wrong implementation in main ?
>> .....
>> set path to ((cRootDir)+";"+(cImpDir))
>> errorsys()
>
> There are several issues here. First, you don't have to call "ErrorSys()"
> in your Main() program. This routine, like AppSys(), DbeSys(), etc. is
> called automatically before Main() is called. You should never call any
> of the Init or Exit Procedures directly in your code!
>
> Secondly, the "XppFatal.log" that you included in one of your posts
> doesn't match the "ErrorSys.prg" file that you also posted. You always
> get an "XppFatal.log", because there is an error in your (actual) Error
> Handler program, specifically in line 210 of the routine ErrorMessage().
>
>>ERRORMESSAGE(210)
>>DEFERROR(99)
>>(B)ERRORSYS@0000(38)
>
> Your actual ErrorSys() routine defines the ErrorBlock() in line 38,
> while the "ErrorSys.prg" file that you posted does this in line 52.
> Also, the function that calls the ErrorMessage() routine is called
> "StandardEH()" and not "DefError()" as shown in your "XppFatal.log".
> In addition, the "ErrorMessage()" routine in the posted file starts in
> line 235, while your error happens in line 210, which is before that
> routine begins.
>
> Whatever is in line 210 of your actually used "ErrorMessage()" routine
> is causing the recursive error, and that's where you should look. Check
> your source code for any of the above mentioned routines, and if you
> can't find the problem in line 210, post the code here, and we might be
> able to help. You have definitely overloaded the default Error Handler,
> and that is the reason for your issues!
>
> -- Andreas
>
> ---                                                                      ---
>  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
>  415 Gute Street                     or: Andreas@DDPSoftware.com
>  Owosso, MI 48867-4410               or: Andreas_Gehrs-Pahl@CrimeCog.com
>  Tel: (989) 723-9927           Web Site: http://www.Aerospace-History.net
> ---                                                                      ---





ERRORSYS.PRG
XPPFATAL.LOG
ERRORSYS.PRG
XPPFATAL.LOG
Andreas Gehrs-Pahl
Re: errorsys
on Tue, 06 Apr 2010 08:59:35 -0400
Rainer,

>thanks for the hint - I removed the call in main - but :
>I added the original errorsys.prg from Alaska, which came over with SL1 
>(folder \SYS) and added this into my project-file.
>I triggered again by making a var-mistake which was announced by my old 
>clipper errorssys with "unknown var" and a short message of modules ...
>What happened is what you see in the attachment. hmmm ...so what is wrong ?

As I wrote in my previous post, the "XppFatal.log" file wasn't made by
the "ErrorSys.prg" file that you have posted. You are obviously using a 
different "ErrorSys.prg" file in your project!

The "original" Alaska "ErrorSys.prg" is compiled into the "XppSys.DLL", 
and unless you want to make changes to those routines, you don't even 
need to include them in your project. 

And because the Alaska "ErrorSys.prg" doesn't include a routine named 
"DefError()", which is shown in your "XppFatal.log" file -- but instead 
a routine named "StandardEH()" -- this "DefError()" routine must be 
somewhere else in your own source code. 

Show us your Project file and/or create a small example that shows your 
problem. If you try to do this, you will probably find where you are 
calling and linking those Error Handler routines, and then you can fix 
the problem. You might simply want to remove those routines entirely and
use the default Alaska Error Handler routines, which are automatically
included (in the "XppSys.DLL").

-- Andreas

---                                                                      ---
  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
  415 Gute Street                     or: Andreas@DDPSoftware.com
  Owosso, MI 48867-4410               or: Andreas_Gehrs-Pahl@CrimeCog.com
  Tel: (989) 723-9927           Web Site: http://www.Aerospace-History.net
---                                                                      ---
RCBRe: errorsys
on Wed, 07 Apr 2010 00:38:38 +0200
hi Andreas ..
ok - understood ... must be one of the miracles i built in myself g
Ill try to find it ... thanks ..
Rainer

<Andreas Gehrs-Pahl> schrieb im Newsbeitrag 
news:ecbkiwa67xw7.paxo1utrqlew$.dlg@40tude.net...
> Rainer,
>
>>thanks for the hint - I removed the call in main - but :
>>I added the original errorsys.prg from Alaska, which came over with SL1
>>(folder \SYS) and added this into my project-file.
>>I triggered again by making a var-mistake which was announced by my old
>>clipper errorssys with "unknown var" and a short message of modules ...
>>What happened is what you see in the attachment. hmmm ...so what is wrong 
>>?
>
> As I wrote in my previous post, the "XppFatal.log" file wasn't made by
> the "ErrorSys.prg" file that you have posted. You are obviously using a
> different "ErrorSys.prg" file in your project!
>
> The "original" Alaska "ErrorSys.prg" is compiled into the "XppSys.DLL",
> and unless you want to make changes to those routines, you don't even
> need to include them in your project.
>
> And because the Alaska "ErrorSys.prg" doesn't include a routine named
> "DefError()", which is shown in your "XppFatal.log" file -- but instead
> a routine named "StandardEH()" -- this "DefError()" routine must be
> somewhere else in your own source code.
>
> Show us your Project file and/or create a small example that shows your
> problem. If you try to do this, you will probably find where you are
> calling and linking those Error Handler routines, and then you can fix
> the problem. You might simply want to remove those routines entirely and
> use the default Alaska Error Handler routines, which are automatically
> included (in the "XppSys.DLL").
>
> -- Andreas
>
> ---                                                                      ---
>  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
>  415 Gute Street                     or: Andreas@DDPSoftware.com
>  Owosso, MI 48867-4410               or: Andreas_Gehrs-Pahl@CrimeCog.com
>  Tel: (989) 723-9927           Web Site: http://www.Aerospace-History.net
> ---                                                                      ---
RCBRe: errorsys
on Thu, 08 Apr 2010 15:08:00 +0200
ok ..Andreas - i removed this errorsys.prg and all is fine ..
But just thinking : what about overloading the build-in-errorsys by "my" 
errorsys.prg -
just add this in a projectfile ?
Rainer

<Andreas Gehrs-Pahl> schrieb im Newsbeitrag 
news:ecbkiwa67xw7.paxo1utrqlew$.dlg@40tude.net...
> Rainer,
>
>>thanks for the hint - I removed the call in main - but :
>>I added the original errorsys.prg from Alaska, which came over with SL1
>>(folder \SYS) and added this into my project-file.
>>I triggered again by making a var-mistake which was announced by my old
>>clipper errorssys with "unknown var" and a short message of modules ...
>>What happened is what you see in the attachment. hmmm ...so what is wrong 
>>?
>
> As I wrote in my previous post, the "XppFatal.log" file wasn't made by
> the "ErrorSys.prg" file that you have posted. You are obviously using a
> different "ErrorSys.prg" file in your project!
>
> The "original" Alaska "ErrorSys.prg" is compiled into the "XppSys.DLL",
> and unless you want to make changes to those routines, you don't even
> need to include them in your project.
>
> And because the Alaska "ErrorSys.prg" doesn't include a routine named
> "DefError()", which is shown in your "XppFatal.log" file -- but instead
> a routine named "StandardEH()" -- this "DefError()" routine must be
> somewhere else in your own source code.
>
> Show us your Project file and/or create a small example that shows your
> problem. If you try to do this, you will probably find where you are
> calling and linking those Error Handler routines, and then you can fix
> the problem. You might simply want to remove those routines entirely and
> use the default Alaska Error Handler routines, which are automatically
> included (in the "XppSys.DLL").
>
> -- Andreas
>
> ---                                                                      ---
>  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
>  415 Gute Street                     or: Andreas@DDPSoftware.com
>  Owosso, MI 48867-4410               or: Andreas_Gehrs-Pahl@CrimeCog.com
>  Tel: (989) 723-9927           Web Site: http://www.Aerospace-History.net
> ---                                                                      ---
Andreas Gehrs-Pahl
Re: errorsys
on Thu, 08 Apr 2010 11:55:02 -0400
Rainer,

>ok ..Andreas - i removed this errorsys.prg and all is fine ..

So you found where you added a different "ErrorSys.prg" file to your 
project?

>But just thinking : what about overloading the build-in-errorsys by "my" 
>errorsys.prg -
>just add this in a projectfile ?

Yes, if you add your own, replacement, Init and/or Exit procedures, they
will be used instead of the ones built into the "XppSys.DLL" that comes 
with the Xbase++ runtime. This includes the following Init/Exit routines:

* ErrorSys() -- To set up the Error routines.
* AppSys()   -- To set up the application environment.
* DbeSys()   -- To load and set up the Database Engines.
* AppExit()  -- To clean up the application environment.

You can also create your own "XppSys.DLL" by changing or replacing the 
code that is in the "XPPW32\Source\Compat\" and "XPPW32\Source\Sys\"
directories. You can find the corresponding "Project.xpj" file in the 
"XPPW32\Source\DLL\" directory.

But if you only want to replace the Init and/or Exit procedures, you 
can simply include a procedure with the same name in your code, and it
will automatically replace (or "overload") the default routine.

-- Andreas

---                                                                      ---
  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
  415 Gute Street                     or: Andreas@DDPSoftware.com
  Owosso, MI 48867-4410               or: Andreas_Gehrs-Pahl@CrimeCog.com
  Tel: (989) 723-9927           Web Site: http://www.Aerospace-History.net
---                                                                      ---
James Loughner Re: errorsys
on Thu, 08 Apr 2010 12:10:05 -0400
errorsys.prg's are tricky I'd start with the  Alaska one and modify it
as required. Can be found in the source directory. But be careful an
error in the error handler leads to recursion and fatal errors, as you
have seen.

Jim



On 04/08/2010 09:08 AM, RCB wrote:
> ok ..Andreas - i removed this errorsys.prg and all is fine ..
> But just thinking : what about overloading the build-in-errorsys by "my" 
> errorsys.prg -
> just add this in a projectfile ?
> Rainer
> 
> <Andreas Gehrs-Pahl> schrieb im Newsbeitrag 
> news:ecbkiwa67xw7.paxo1utrqlew$.dlg@40tude.net...
>> Rainer,
>>
>>> thanks for the hint - I removed the call in main - but :
>>> I added the original errorsys.prg from Alaska, which came over with SL1
>>> (folder \SYS) and added this into my project-file.
>>> I triggered again by making a var-mistake which was announced by my old
>>> clipper errorssys with "unknown var" and a short message of modules ...
>>> What happened is what you see in the attachment. hmmm ...so what is wrong 
>>> ?
>>
>> As I wrote in my previous post, the "XppFatal.log" file wasn't made by
>> the "ErrorSys.prg" file that you have posted. You are obviously using a
>> different "ErrorSys.prg" file in your project!
>>
>> The "original" Alaska "ErrorSys.prg" is compiled into the "XppSys.DLL",
>> and unless you want to make changes to those routines, you don't even
>> need to include them in your project.
>>
>> And because the Alaska "ErrorSys.prg" doesn't include a routine named
>> "DefError()", which is shown in your "XppFatal.log" file -- but instead
>> a routine named "StandardEH()" -- this "DefError()" routine must be
>> somewhere else in your own source code.
>>
>> Show us your Project file and/or create a small example that shows your
>> problem. If you try to do this, you will probably find where you are
>> calling and linking those Error Handler routines, and then you can fix
>> the problem. You might simply want to remove those routines entirely and
>> use the default Alaska Error Handler routines, which are automatically
>> included (in the "XppSys.DLL").
>>
>> -- Andreas
>>
>> ---                                                                      ---
>>  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
>>  415 Gute Street                     or: Andreas@DDPSoftware.com
>>  Owosso, MI 48867-4410               or: Andreas_Gehrs-Pahl@CrimeCog.com
>>  Tel: (989) 723-9927           Web Site: http://www.Aerospace-History.net
>> ---                                                                      ---
>
RCBRe: errorsys
on Fri, 09 Apr 2010 11:04:07 +0200
thanks Andreas !!
hi James ... yes this was exactly what happened. To overload the buildin 
errorsys with the one delivered by Alaska \source seems to make fatal errors 
which in my opinion should not happen - neither recursions - is that a 
mistake ? This \source errorsys by Alaska seems to be different from the one 
build in - as Andreas already noticed.
Rainer

"James Loughner" <jwrl@suddenlink.net> schrieb im Newsbeitrag 
news:3c9143fa$774dedfd$2b580@news.alaska-software.com...
> errorsys.prg's are tricky I'd start with the  Alaska one and modify it
> as required. Can be found in the source directory. But be careful an
> error in the error handler leads to recursion and fatal errors, as you
> have seen.
>
> Jim
>
>
>
> On 04/08/2010 09:08 AM, RCB wrote:
>> ok ..Andreas - i removed this errorsys.prg and all is fine ..
>> But just thinking : what about overloading the build-in-errorsys by "my"
>> errorsys.prg -
>> just add this in a projectfile ?
>> Rainer
>>
>> <Andreas Gehrs-Pahl> schrieb im Newsbeitrag
>> news:ecbkiwa67xw7.paxo1utrqlew$.dlg@40tude.net...
>>> Rainer,
>>>
>>>> thanks for the hint - I removed the call in main - but :
>>>> I added the original errorsys.prg from Alaska, which came over with SL1
>>>> (folder \SYS) and added this into my project-file.
>>>> I triggered again by making a var-mistake which was announced by my old
>>>> clipper errorssys with "unknown var" and a short message of modules ...
>>>> What happened is what you see in the attachment. hmmm ...so what is 
>>>> wrong
>>>> ?
>>>
>>> As I wrote in my previous post, the "XppFatal.log" file wasn't made by
>>> the "ErrorSys.prg" file that you have posted. You are obviously using a
>>> different "ErrorSys.prg" file in your project!
>>>
>>> The "original" Alaska "ErrorSys.prg" is compiled into the "XppSys.DLL",
>>> and unless you want to make changes to those routines, you don't even
>>> need to include them in your project.
>>>
>>> And because the Alaska "ErrorSys.prg" doesn't include a routine named
>>> "DefError()", which is shown in your "XppFatal.log" file -- but instead
>>> a routine named "StandardEH()" -- this "DefError()" routine must be
>>> somewhere else in your own source code.
>>>
>>> Show us your Project file and/or create a small example that shows your
>>> problem. If you try to do this, you will probably find where you are
>>> calling and linking those Error Handler routines, and then you can fix
>>> the problem. You might simply want to remove those routines entirely and
>>> use the default Alaska Error Handler routines, which are automatically
>>> included (in the "XppSys.DLL").
>>>
>>> -- Andreas
>>>
>>> ---                                                                      
>>>  ---
>>>  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
>>>  415 Gute Street                     or: Andreas@DDPSoftware.com
>>>  Owosso, MI 48867-4410               or: Andreas_Gehrs-Pahl@CrimeCog.com
>>>  Tel: (989) 723-9927           Web Site: 
>>> http://www.Aerospace-History.net
>>> ---                                                                      
>>>  ---
>>
>
James Loughner Re: errorsys
on Fri, 09 Apr 2010 09:13:02 -0400
You had an errorsys.prg from some other source because the calls
recorded don't exist in the Alaska source. If you copy the errorsys.prg
from the source directory and include it in the build it will over ride
the one in the Alaska library. This will actually be the same code. but
then you can modify the prg to out put additional information or
behavior about any error.  Note that "fatal" errors are handled in a
different manor and can not be modified.

Jim

On 04/09/2010 05:04 AM, RCB wrote:
> thanks Andreas !!
> hi James ... yes this was exactly what happened. To overload the buildin 
> errorsys with the one delivered by Alaska \source seems to make fatal errors 
> which in my opinion should not happen - neither recursions - is that a 
> mistake ? This \source errorsys by Alaska seems to be different from the one 
> build in - as Andreas already noticed.
> Rainer
> 
> "James Loughner" <jwrl@suddenlink.net> schrieb im Newsbeitrag 
> news:3c9143fa$774dedfd$2b580@news.alaska-software.com...
>> errorsys.prg's are tricky I'd start with the  Alaska one and modify it
>> as required. Can be found in the source directory. But be careful an
>> error in the error handler leads to recursion and fatal errors, as you
>> have seen.
>>
>> Jim
>>
>>
>>
>> On 04/08/2010 09:08 AM, RCB wrote:
>>> ok ..Andreas - i removed this errorsys.prg and all is fine ..
>>> But just thinking : what about overloading the build-in-errorsys by "my"
>>> errorsys.prg -
>>> just add this in a projectfile ?
>>> Rainer
>>>
>>> <Andreas Gehrs-Pahl> schrieb im Newsbeitrag
>>> news:ecbkiwa67xw7.paxo1utrqlew$.dlg@40tude.net...
>>>> Rainer,
>>>>
>>>>> thanks for the hint - I removed the call in main - but :
>>>>> I added the original errorsys.prg from Alaska, which came over with SL1
>>>>> (folder \SYS) and added this into my project-file.
>>>>> I triggered again by making a var-mistake which was announced by my old
>>>>> clipper errorssys with "unknown var" and a short message of modules ...
>>>>> What happened is what you see in the attachment. hmmm ...so what is 
>>>>> wrong
>>>>> ?
>>>>
>>>> As I wrote in my previous post, the "XppFatal.log" file wasn't made by
>>>> the "ErrorSys.prg" file that you have posted. You are obviously using a
>>>> different "ErrorSys.prg" file in your project!
>>>>
>>>> The "original" Alaska "ErrorSys.prg" is compiled into the "XppSys.DLL",
>>>> and unless you want to make changes to those routines, you don't even
>>>> need to include them in your project.
>>>>
>>>> And because the Alaska "ErrorSys.prg" doesn't include a routine named
>>>> "DefError()", which is shown in your "XppFatal.log" file -- but instead
>>>> a routine named "StandardEH()" -- this "DefError()" routine must be
>>>> somewhere else in your own source code.
>>>>
>>>> Show us your Project file and/or create a small example that shows your
>>>> problem. If you try to do this, you will probably find where you are
>>>> calling and linking those Error Handler routines, and then you can fix
>>>> the problem. You might simply want to remove those routines entirely and
>>>> use the default Alaska Error Handler routines, which are automatically
>>>> included (in the "XppSys.DLL").
>>>>
>>>> -- Andreas
>>>>
>>>> ---                                                                      
>>>>  ---
>>>>  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
>>>>  415 Gute Street                     or: Andreas@DDPSoftware.com
>>>>  Owosso, MI 48867-4410               or: Andreas_Gehrs-Pahl@CrimeCog.com
>>>>  Tel: (989) 723-9927           Web Site: 
>>>> http://www.Aerospace-History.net
>>>> ---                                                                      
>>>>  ---
>>>
>>
> 
>
RCBRe: errorsys
on Sat, 10 Apr 2010 11:06:03 +0200
ok - i know where to look at - i removed all other errorstuff and I now get 
all this normal buld-in-error-handling ... and i will start from the 
error-basics again . !
Thank you for your hints !!
Rainer
"James Loughner" <jwrl@suddenlink.net> schrieb im Newsbeitrag 
news:277a6b36$55cdcb00$2e33a@news.alaska-software.com...
> You had an errorsys.prg from some other source because the calls
> recorded don't exist in the Alaska source. If you copy the errorsys.prg
> from the source directory and include it in the build it will over ride
> the one in the Alaska library. This will actually be the same code. but
> then you can modify the prg to out put additional information or
> behavior about any error.  Note that "fatal" errors are handled in a
> different manor and can not be modified.
>
> Jim
>
> On 04/09/2010 05:04 AM, RCB wrote:
>> thanks Andreas !!
>> hi James ... yes this was exactly what happened. To overload the buildin
>> errorsys with the one delivered by Alaska \source seems to make fatal 
>> errors
>> which in my opinion should not happen - neither recursions - is that a
>> mistake ? This \source errorsys by Alaska seems to be different from the 
>> one
>> build in - as Andreas already noticed.
>> Rainer
>>
>> "James Loughner" <jwrl@suddenlink.net> schrieb im Newsbeitrag
>> news:3c9143fa$774dedfd$2b580@news.alaska-software.com...
>>> errorsys.prg's are tricky I'd start with the  Alaska one and modify it
>>> as required. Can be found in the source directory. But be careful an
>>> error in the error handler leads to recursion and fatal errors, as you
>>> have seen.
>>>
>>> Jim
>>>
>>>
>>>
>>> On 04/08/2010 09:08 AM, RCB wrote:
>>>> ok ..Andreas - i removed this errorsys.prg and all is fine ..
>>>> But just thinking : what about overloading the build-in-errorsys by 
>>>> "my"
>>>> errorsys.prg -
>>>> just add this in a projectfile ?
>>>> Rainer
>>>>
>>>> <Andreas Gehrs-Pahl> schrieb im Newsbeitrag
>>>> news:ecbkiwa67xw7.paxo1utrqlew$.dlg@40tude.net...
>>>>> Rainer,
>>>>>
>>>>>> thanks for the hint - I removed the call in main - but :
>>>>>> I added the original errorsys.prg from Alaska, which came over with 
>>>>>> SL1
>>>>>> (folder \SYS) and added this into my project-file.
>>>>>> I triggered again by making a var-mistake which was announced by my 
>>>>>> old
>>>>>> clipper errorssys with "unknown var" and a short message of modules 
>>>>>> ...
>>>>>> What happened is what you see in the attachment. hmmm ...so what is
>>>>>> wrong
>>>>>> ?
>>>>>
>>>>> As I wrote in my previous post, the "XppFatal.log" file wasn't made by
>>>>> the "ErrorSys.prg" file that you have posted. You are obviously using 
>>>>> a
>>>>> different "ErrorSys.prg" file in your project!
>>>>>
>>>>> The "original" Alaska "ErrorSys.prg" is compiled into the 
>>>>> "XppSys.DLL",
>>>>> and unless you want to make changes to those routines, you don't even
>>>>> need to include them in your project.
>>>>>
>>>>> And because the Alaska "ErrorSys.prg" doesn't include a routine named
>>>>> "DefError()", which is shown in your "XppFatal.log" file -- but 
>>>>> instead
>>>>> a routine named "StandardEH()" -- this "DefError()" routine must be
>>>>> somewhere else in your own source code.
>>>>>
>>>>> Show us your Project file and/or create a small example that shows 
>>>>> your
>>>>> problem. If you try to do this, you will probably find where you are
>>>>> calling and linking those Error Handler routines, and then you can fix
>>>>> the problem. You might simply want to remove those routines entirely 
>>>>> and
>>>>> use the default Alaska Error Handler routines, which are automatically
>>>>> included (in the "XppSys.DLL").
>>>>>
>>>>> -- Andreas
>>>>>
>>>>> ---
>>>>>  ---
>>>>>  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
>>>>>  415 Gute Street                     or: Andreas@DDPSoftware.com
>>>>>  Owosso, MI 48867-4410               or: 
>>>>> Andreas_Gehrs-Pahl@CrimeCog.com
>>>>>  Tel: (989) 723-9927           Web Site:
>>>>> http://www.Aerospace-History.net
>>>>> ---
>>>>>  ---
>>>>
>>>
>>
>>
>
Andreas Gehrs-Pahl
Re: errorsys
on Fri, 09 Apr 2010 17:14:50 -0400
Rainer,

I'm afraid, but you still have it wrong!

>hi James ... yes this was exactly what happened. 

No, it wasn't. You never used the "ErrorSys.prg" file that you posted 
here! You used a different one -- one of your own design, probably from 
an old Clipper program -- which contains a function or procedure called 
"DefError()"!

>To overload the buildin errorsys with the one delivered by Alaska 
>\source seems to make fatal errors which in my opinion should not happen - 
>neither recursions - is that a mistake ? 

This isn't the case at all! Including or overloading the "ErrorSys.prg" 
from the Alaska "\Source\Sys\" directory will NOT cause a recursive error. 
The error happened because you replaced (the correct and working) program
with your own one, which contains an error.

>This \source errorsys by Alaska seems to be different from the one 
>build in - as Andreas already noticed.

No, it isn't. They are identical. That's what I tried to explain to you.

Only after you removed YOUR program from your project, the original 
Alaska "ErrorSys.prg" file was used -- the same that you posted here -- 
which is compiled into the "XppSys.DLL". And only then, after you used
that original Alaska "ErrorSys.prg" program, went your "XppFatal.log"
problem away.

I don't know how to explain it more clearly: The error that caused the 
"XppFatal.log" error is in YOUR code, not in the Alaska code that you
posted!

Ich probiers nochmal in Deutsch: Du hast Dein eigenes "ErrorSys.prg" 
program in Deinem Projekt benutzt und das hat zu dem "XppFatal.log" 
Problem gefuehrt. Das "ErrorSys.prg" von Alaska hat keine Routine die
"DefError()" genannt ist und kann deswegen dieses "XppFatal.log" nicht 
erzeugen!

Try the attached program, and see for yourself. I simply added a Main()
procedure (with an error) to the "ErrorSys.prg" file that you posted.
Just compile and run the program. You won't get an "XppFatal.log"!

You need to search YOUR code for a program file that contains a function 
or procedure called "DefError()". In line 99 of the program file, this 
routine will call a function or procedure that is named "ErrorMessage()"
and which creates an error in line 210 of that routine.

-- Andreas

---                                                                      ---
  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
  415 Gute Street                     or: Andreas@DDPSoftware.com
  Owosso, MI 48867-4410               or: Andreas_Gehrs-Pahl@CrimeCog.com
  Tel: (989) 723-9927           Web Site: http://www.Aerospace-History.net
---                                                                      ---


ERRORSYS.PRG
ERRORSYS.PRG
Jorge LRe: printerspooler after migration
on Mon, 05 Apr 2010 14:38:57 -0300
Hi

1 - when finish the printer, put the command "set printer to", to close the 
file printer


"RCB" <mail-at-medmaster.de> escribió en el mensaje de noticias 
news:4c77523d$d263bae$5ebfc@news.alaska-software.com...
> hello,
> 1.
> after i migrated an old clipperprogramm into xbase++ (nongui) all worked 
> ok
> but : printing started only after quitting the programm. I tried all sorts 
> of printersettings and avoided processoroverloads -but nothing helped. Iam 
> using printersequences for LQ850 direct to LPT1.
> 2. i was not used to getting an XPPFATAL-LOG all the time - is that the 
> normal answer for all sorts of errors in a migrated nongui-system ? Is 
> there any better error.prg in use ?
> Would be nice to hear from any migrating-expert 
> Rainer
>
>
RCBRe: printerspooler after migration
on Mon, 05 Apr 2010 22:00:39 +0200
Hi Jorge ... yes ..that was it I forgot to close the channel !!
by set printer to ....
thanks ...
Rainer
"Jorge L" <jlborlando@way.com.ar> schrieb im Newsbeitrag 
news:18870978$16e041f6$5eb16@news.alaska-software.com...
> Hi
>
> 1 - when finish the printer, put the command "set printer to", to close 
> the file printer
>
>
> "RCB" <mail-at-medmaster.de> escribi en el mensaje de noticias 
> news:4c77523d$d263bae$5ebfc@news.alaska-software.com...
>> hello,
>> 1.
>> after i migrated an old clipperprogramm into xbase++ (nongui) all worked 
>> ok
>> but : printing started only after quitting the programm. I tried all 
>> sorts of printersettings and avoided processoroverloads -but nothing 
>> helped. Iam using printersequences for LQ850 direct to LPT1.
>> 2. i was not used to getting an XPPFATAL-LOG all the time - is that the 
>> normal answer for all sorts of errors in a migrated nongui-system ? Is 
>> there any better error.prg in use ?
>> Would be nice to hear from any migrating-expert 
>> Rainer
>>
>>
>
>