Problem with encoding date - but works on Win98

[jodleren]

Hi all



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?



WBR

Sonnich

 

[Don Phillipson]

"jodleren" wrote in message

news:62a22cf2-c05d-4557-9861-ae9907b70ad9@s41g2000vba.googlegroups.com...



> 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 . . .

> 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.



Windows XP offers "compatibility" settings, to emulate Win95 or

Win98, which solves this type of problem about 80 per cent of

the time. "Compatibility" is explained via / Start / Help.



--

Don Phillipson

Carlsbad Springs

(Ottawa, Canada)

 

[jodleren]

On May 16, 7:23 pm, "Don Phillipson" wrote:

> "jodleren" wrote in message

>

> news:62a22cf2-c05d-4557-9861-ae9907b70ad9@s41g2000vba.googlegroups.com...

>

> > 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 . . .

> > 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.

>

> Windows XP offers "compatibility" settings, to emulate Win95 or

> Win98, which solves this type of problem about 80 per cent of

> the time.  "Compatibility" is explained via / Start / Help.



Thanks for the idea. That does not help, for both win 95 and win 98.

The error remain.



Sonnich

 

[David H. Lipman]

From: "jodleren"



| On May 16, 7:23 pm, "Don Phillipson" wrote:

>> "jodleren" wrote in message



>> news:62a22cf2-c05d-4557-9861-ae9907b70ad9@s41g2000vba.googlegroups.com...



>> > 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 . . .

>> > 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.



>> Windows XP offers "compatibility" settings, to emulate Win95 or

>> Win98, which solves this type of problem about 80 per cent of

>> the time. "Compatibility" is explained via / Start / Help.



| Thanks for the idea. That does not help, for both win 95 and win 98.

| The error remain.



1. Win9x/ME is a different family than NT and thus can have compatibilities issues if it

isn't coded to be NT caompatible.



2. It probably wasn't Y2K compliant and thus the error.





--

Dave

http://www.claymania.com/removal-trojan-adware.html

Multi-AV - http://www.pctipp.ch/downloads/dl/35905.asp

 

[Hot-text]

ms-its:C:\WINDOWS\Help\misc.chm::/compatibility_tab_and_wizard.htm



Go to the Program *.exe File

Right Click it

Open Properties

Go to Compatibility in Properties

Check Mark Run this Program in Compatibility made for:

Window 98 / Window Me

Click Apply

Click OK





To run the Program Compatibility Wizard

Start the Program Compatibility ( hcp://system/compatctr/compatmode.htm )

Wizard.

Follow the instructions in the wizard.

Note



To start the Program Compatibility Wizard, click Start, click Help and

Support, click Find compatible hardware and software for Windows XP, and

then, under See Also in the navigation pane, click Program Compatibility

Wizard.

Set the compatibility properties manually

As an alternative to running the Program Compatibility Wizard, you can set

the compatibility properties for a program manually. The settings are the

same as the options in the Program Compatibility Wizard.



To set the compatibility properties for a program manually

Right-click the program icon on your desktop or the shortcut on the Start

menu for the program you want to run, and then click Properties.

Click the Compatibility tab, and change the compatibility settings for your

program.

Notes



The Compatibility tab is only available for programs installed on your hard

drive. Although you can run the Program Compatibility Wizard on programs or

setup files on a CD-ROM or floppy disk, your changes will not remain in

effect after you close the program.

For more information about an option on the Compatibility tab, right-click

the option and then click What's This.







"jodleren" wrote in message

news:62a22cf2-c05d-4557-9861-ae9907b70ad9@s41g2000vba.googlegroups.com...

> Hi all

>

> 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?

>

> WBR

> Sonnich

 

[jodleren]

On May 16, 10:32 pm, "Hot-text" wrote:

> ms-its:C:\WINDOWS\Help\misc.chm::/compatibility_tab_and_wizard.htm

>

> Go to the Program *.exe File

> Right Click it

> Open Properties

> Go to Compatibility in Properties

> Check Mark Run this Program in Compatibility made for:

> Window 98 / Window Me

> Click Apply

> Click OK

>

> To run the Program Compatibility Wizard

> Start the Program Compatibility ( hcp://system/compatctr/compatmode.htm )

> Wizard.

> Follow the instructions in the wizard.

>  Note

>

> To start the Program Compatibility Wizard, click Start, click Help and

> Support, click Find compatible hardware and software for Windows XP, and

> then, under See Also in the navigation pane, click Program Compatibility

> Wizard.

> Set the compatibility properties manually

> As an alternative to running the Program Compatibility Wizard, you can set

> the compatibility properties for a program manually. The settings are the

> same as the options in the Program Compatibility Wizard.

>

> To set the compatibility properties for a program manually

> Right-click the program icon on your desktop or the shortcut on the Start

> menu for the program you want to run, and then click Properties.

> Click the Compatibility tab, and change the compatibility settings for your

> program.

>  Notes

>

> The Compatibility tab is only available for programs installed on your hard

> drive. Although you can run the Program Compatibility Wizard on programs or

> setup files on a CD-ROM or floppy disk, your changes will not remain in

> effect after you close the program.

> For more information about an option on the Compatibility tab, right-click

> the option and then click What's This.

>

> "jodleren" wrote in message

>

> news:62a22cf2-c05d-4557-9861-ae9907b70ad9@s41g2000vba.googlegroups.com...

>

> > Hi all

>

> > 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?

>

> > WBR

> > Sonnich



The compability issue does not solve it. Not is it a Y2K problem, as

it works on Win98.



So, any other suggestions?



WBT

Sonnich

 

[Noel Paton]

Why not run it in a Win98 VM in XP??





--

Noel Paton

CrashFixPC



Nil Carborundum Illegitemi

www.crashfixpc.co.uk

 

[jodleren]

On May 16, 7:16 pm, jodleren wrote:

> Hi all

>

> 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?

>

> WBR

> Sonnich



To be more exact, my problem is ntdll.dll - after loading that the

error occurs. Next it loads msimtf.dll



Gee, I recall ntdll.dll - it can cause a lot of problems, and it is

probably related to user rights



WBR

Sonnich

 

[Hot-text]

Then he need to run his Windows Update

To fix it, for in 1999 thay put out a update to fix the Y2K

If he run all of the Windows Update, then Y2K is not the problem!







"jodleren" wrote in message

news:d99066d4-fa4e-4138-8987-f1206c3bfc24@o39g2000vbd.googlegroups.com...

> On May 16, 10:32 pm, "Hot-text" wrote:

>> ms-its:C:\WINDOWS\Help\misc.chm::/compatibility_tab_and_wizard.htm

>>

>> Go to the Program *.exe File

>> Right Click it

>> Open Properties

>> Go to Compatibility in Properties

>> Check Mark Run this Program in Compatibility made for:

>> Window 98 / Window Me

>> Click Apply

>> Click OK

>>

>> To run the Program Compatibility Wizard

>> Start the Program Compatibility ( hcp://system/compatctr/compatmode.htm )

>> Wizard.

>> Follow the instructions in the wizard.

>> Note

>>

>> To start the Program Compatibility Wizard, click Start, click Help and

>> Support, click Find compatible hardware and software for Windows XP, and

>> then, under See Also in the navigation pane, click Program Compatibility

>> Wizard.

>> Set the compatibility properties manually

>> As an alternative to running the Program Compatibility Wizard, you can

>> set

>> the compatibility properties for a program manually. The settings are the

>> same as the options in the Program Compatibility Wizard.

>>

>> To set the compatibility properties for a program manually

>> Right-click the program icon on your desktop or the shortcut on the Start

>> menu for the program you want to run, and then click Properties.

>> Click the Compatibility tab, and change the compatibility settings for

>> your

>> program.

>> Notes

>>

>> The Compatibility tab is only available for programs installed on your

>> hard

>> drive. Although you can run the Program Compatibility Wizard on programs

>> or

>> setup files on a CD-ROM or floppy disk, your changes will not remain in

>> effect after you close the program.

>> For more information about an option on the Compatibility tab,

>> right-click

>> the option and then click What's This.

>>

>> "jodleren" wrote in message

>>

>> news:62a22cf2-c05d-4557-9861-ae9907b70ad9@s41g2000vba.googlegroups.com...

>>

>> > Hi all

>>

>> > 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?

>>

>> > WBR

>> > Sonnich

>

> The compability issue does not solve it. Not is it a Y2K problem, as

> it works on Win98.

>

> So, any other suggestions?

>

> WBT

> Sonnich

 

[Hot-text]

If it's ntdll.dll - it's 100% of problems!

Ok I'll do a Find: All Files on my Win98

Ntdll.dll On May 16, 7:16 pm, jodleren wrote:

>> Hi all

>>

>> 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?

>>

>> WBR

>> Sonnich

>

> To be more exact, my problem is ntdll.dll - after loading that the

> error occurs. Next it loads msimtf.dll

>

> Gee, I recall ntdll.dll - it can cause a lot of problems, and it is

> probably related to user rights

>

> WBR

> Sonnich[/color]

 

[Andrew McLaren]

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?

 

[jodleren]

On May 18, 5:46 am, Andrew McLaren 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

 

[Dan]

"jodleren" wrote:



> On May 18, 5:46 am, Andrew McLaren 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.