=====================
=============================We haven't changed any code that affects the behavior of file opening between versions 4.62 and 4.70. The only variable is a change from Visual Studio 2002 to 2003, but whatever has changed only seems to affect a very small percentage of users. Following on from the discussion on the google thread, perhaps some CD-ROMs and read-only file systems do not have valid time stamps for the last accessed or last modified times. On that assumption, we've found a possible scenario that can cause the problem.
TextPad makes a seemingly innocuous call to Microsoft's code to get a filename. Some bright spark at MS thought code reuse was a "good idea", so implemented it by calling some other code which also gets the file size and its creation, accessed and last modified times. This worked fine, if inefficently, for the past 10 years, until another bright spark from MS decided to do some error checking. Now, if a time stamp is invalid, an error is thrown, with the unhelpful message "The parameter is invalid". The release notes for VS 2003 omitted to mention that change, and it did not have any effect on our systems, so TextPad 4.70 was released without taking account of it.
We've modified TextPad to avoid using Microsoft's new code, and made it available from testing from here:
I also mention it because of the recent release of Macro Scheduler 7.2.037. I don't know if VS200x is being used to create Macro Scheduler, but if it is, I thought this could be useful information to be aware of.
Hope this is helpful...............
