Prev: delayed write falure messages differant drive each time
Next: Hibernation problem
From: Andrew McLaren on 17 May 2010 22:46
Hi Sonnich,

This error message comes from the Borland Delphi Runtime. The error is
returned by Delphi functions such as Encodedate(), if the function
cannot handle the parameters passed to it.

So, your SCM program was written using the Borland Delphi language. When
the Delphi VCL Runtime calls a date function on your XP machine, it hits
this error.

This specific error was reported quite a bit by Delphi users, after XP
SP3 was released. It even affected some of Borland's own products; see:

http://qc.embarcadero.com/wc/qcmain.aspx?d=61610

As described in that bug report, the problem is often caused by a known
issue for XP SP3 when used in the Jerusalem timezone.

If that matches your scenario, see this Microsoft KB article:

http://support.microsoft.com/kb/953917

Download and install the hotfix described in the article, and
(hopefully), SCM will then run okay on XP.

Hope this helps,

Andrew

--
amclar at optusnet dot com dot au


On 17/05/2010 02:16, jodleren wrote:
> My problem is an older programme, Next from SCM for Windor 60 to
> exact. Probably that doesnt tell you much.
> Originally it works on Win98, and can be reinstalled and work on
> Win98.
> On Win XP however, it will work the first time, but after that it will
> give this error:
>
> Invalid argument to date encode.
>
> Then an access violation will occur, and the programme will not work.
> I tried it on to Win XP computers, the result is the same. That was
> yesterday, 15.05.2010.
> It does not even read in the language or anything. All functions
> result in an access violation error.
> > As it works on Win98, it has to be related to some kind of windows DLL
> or something.
> Any ideas anyone?
From: jodleren on 18 May 2010 07:27
On May 18, 5:46 am, Andrew McLaren <and...(a)invalid.domain.com> wrote:
> Hi Sonnich,
>
> This error message comes from the Borland Delphi Runtime. The error is
> returned by Delphi functions such as Encodedate(), if the function
> cannot handle the parameters passed to it.
>
> So, your SCM program was written using the Borland Delphi language. When
> the Delphi VCL Runtime calls a date function on your XP machine, it hits
> this error.
>
> This specific error was reported quite a bit by Delphi users, after XP
> SP3 was released. It even affected some of Borland's own products; see:
>
> http://qc.embarcadero.com/wc/qcmain.aspx?d=61610
>
> As described in that bug report, the problem is often caused by a known
> issue for XP SP3 when used in the Jerusalem timezone.
>
> If that matches your scenario, see this Microsoft KB article:
>
> http://support.microsoft.com/kb/953917
>
> Download and install the hotfix described in the article, and
> (hopefully), SCM will then run okay on XP.

Thanks Andrew, that explains. At I installed the update, but that did
not change much. However, knowing the nature of the problem is enough
as I'll let them use Win XP without SP3 - then it will work for them

WBR
Sonnich
From: Dan on 18 May 2010 12:45
"jodleren" wrote:

> On May 18, 5:46 am, Andrew McLaren <and...(a)invalid.domain.com> wrote:
> > Hi Sonnich,
> >
> > This error message comes from the Borland Delphi Runtime. The error is
> > returned by Delphi functions such as Encodedate(), if the function
> > cannot handle the parameters passed to it.
> >
> > So, your SCM program was written using the Borland Delphi language. When
> > the Delphi VCL Runtime calls a date function on your XP machine, it hits
> > this error.
> >
> > This specific error was reported quite a bit by Delphi users, after XP
> > SP3 was released. It even affected some of Borland's own products; see:
> >
> > http://qc.embarcadero.com/wc/qcmain.aspx?d=61610
> >
> > As described in that bug report, the problem is often caused by a known
> > issue for XP SP3 when used in the Jerusalem timezone.
> >
> > If that matches your scenario, see this Microsoft KB article:
> >
> > http://support.microsoft.com/kb/953917
> >
> > Download and install the hotfix described in the article, and
> > (hopefully), SCM will then run okay on XP.
>
> Thanks Andrew, that explains. At I installed the update, but that did
> not change much. However, knowing the nature of the problem is enough
> as I'll let them use Win XP without SP3 - then it will work for them
>
> WBR
> Sonnich
> .
>

Just a word of warning Windows XP SP2 and earlier versions on 32 bit systems
will reach end of life on July 13, 2010 as well as Windows 2000 Professional.
First  |  Prev  | 
Pages: 1 2 3
Prev: delayed write falure messages differant drive each time
Next: Hibernation problem