!pas is a detection for malicious Pascal (Delphi) source files, which are temporarily created by.!dcu detects malicious Delphi library files that were created by.adds itself to the Delphi compilation process in order to then infect all files compiled with that Delphi compiler.Furthermore, in addition to only affecting versions 4 through 7 the threat doesn't run on systems which do not contain the Delphi development environment.įor the purpose of clarity, Symantec detects this Delphi virus as three separate but related threats: The current version of the threat doesn't contain a malicious payload and so doesn't actually cause any damage to systems running Delphi.
\Lib\sysconst.dcuĪny file that is subsequently compiled with Delphi will have the viral code included in it. So, if one of these older development environments is found on a machine that the malware is introduced to, it will attempt to infect Delphi files during the compilation process by placing an infection routine in the following file: It is a popular choice for writing GUI applications, as it is relatively simple to program in being of course based on Pascal.
Delphi is mainly used for the development of desktop and enterprise database applications, but it is a general-purpose software development tool suitable for most software projects including Web applications.
Delphi 7 was the last free version released, which probably explains why it is still actively used today. Using Pascal as its underlying language, Delphi came into being when Windows 3.1 was first released along with the introduction of the graphical user interface (GUI).Īccording to Wikipedia, Delphi 7 was released in August 2002 and became the standard version used by Delphi developers. To provide some brief background, Delphi is a software development environment for Microsoft Windows applications. As has been reported, there is a threat on the loose that targets Delphi development environments, specifically versions 4 through 7. Or at least older Delphi environments and programs compiled using them.
> date in the associated database table changes to 2020. > value changes to 20 as the TDbEdit receives focus. > most part it's fine, but sometimes a problem occurs where the year > TDbEdit shows a date/time field with format dd/mm/yy hh:ss. > I have an aging (10 years old!) Delphi 5 application where a Has anybody experienced similar, or can anyone suggest what might be happening? I think that will hit everything that is relevant, but I'd really like to understand the cause and provide a targeted solution TDateTimeField(('StartTime')).DisplayFormat := 'dd/mm/yy hh:mm' In an attempt to provide a solution I'm going to rebuild with Delphi 7 and include some defensive code that is triggered when the TDbEdit receives focus and is based upon. The sopftware has gone through several versions since, but the problem persists and has been tolerated for several years. It materialised when workstations were upgraded from NT4 to W2k. Simply restarting the application (not the workstation) clears the problem. The application is used daily and Users report that it can go for weeks without a problem, or they might get it several times in one day, and it's not always the same workstation.
I have no idea how to induce the problem and cannot predict when it will occur. The problem cannot be recovered without restarting the application, after which everything is fine again (except that the wrong dates needs to be corrected). The underlying date in the associated database table changes to 2020. For the most part it's fine, but sometimes a problem occurs where the year value changes to 20 as the TDbEdit receives focus. I have an aging (10 years old!) Delphi 5 application where a TDbEdit shows a date/time field with format dd/mm/yy hh:ss.