I have recently upgraded a Vista laptop to Ashell 5.1.1140.0 from 5.0.995.9.

When I now use XCALL XDATE it returns the 3 byte binary date in yy dd mm format not yy mm dd.

It should return the date as
MAP1 DATE,S
MAP3 YY,B,1
MAP3 MM,B,1
MAP3 DD,B,1
but is reversing MM and DD.

I suspect this may be something to do with US v European date formats but I can't find incorrect settings in Ashell or Vista.

Any ideas?

Barry

I had to create a little test program to look into this, as I must admit to having forgotten the details of your XCALL XDATE. Having done that, it appears to me that the correct order of the MM and DD is entirely dependent on the LDF (i.e. Language Definition File) set via the LANGUAGE= statement in the miame.ini.

Could it be that in the process of updating you somehow ended up with LANGUAGE=\ENGLSH.LDF instead of BRTISH.LDF? (And don't blame me for the unfortunate choice of the filename ENGLSH to indicate "American"; I have no idea why Alpha didn't go with something unambiguous like YANKEE.LDF)

We seem to have both with the ENGLSH.LDF at the end.

The update routine must have added the line as it wasn't there before.

LANGUAGE=C:\vm\Miame\DSK0\001006\BRTISH.LDF

[MIAME]
LANGUAGE=%MIAME%\DSK0\001006\ENGLSH.LDF

Thanks Jack

Barry

Hmmm... we did add the [MIAME] header to the miame.ini file to make it more compatible with automatic INI-updating logic in the new installer. Perhaps there is a glitch in the logic, resulting in old miame.ini files getting new lines added rather than simply updated. (For most of the commands, the last occurrence would supercede any prior ones.)

You might want to do a quick scan of your miame.ini to see if there are any other suspicious statements which include "%MIAME%".

Sorry for the confusion.

Thats the only line with %MIAME% in it.

The two new lines [MIAME] & LANGUAGE= are right at the very end of MIAME.INI with the original LANGUAGE= on line 8.

If the update routine was supposed to scan for an existing LANGUAGE= line then yes, I think it missed it.

Barry