🚀 go-pugleaf

On Thu, 6 Mar 2003 09:45:37 -0500, "Ed Mulroy [TeamB]" <ed@mulroy.org>
wrote:

>> Helmut Giese wrote in message
>> news:3e675170.1917379@forums.borland.com...
>> Hm, I thought of that, too. But when going this
>> route everything has to work out 100% - no error
>> allowed - never. Or else the system time
>> will remain set at an arbitrary point in the past
>> - and leave a very puzzled user.
>
>When Windows 3.0 (yes, the replacement for Win 386) came out I was greatly
>bothered by how it commonly would lock up a program of any size.  I used to
>do this by executing a second, small exe with a hidden window which would
>accept a set of messages.  I would tell it what my main window's caption was
>(so it could find the window later), and what the original and phony time
>was.  This 2nd app would look for the first window and if found would then
>yield.  If it did not find the first window it would check the time and date
>and if wildly off, adjust the time.  It would then quit.
What a sneaky way :)
Ok, I concede that this looks like a rather reliable approach.
However, the problem I'm trying to solve looks like a minor issue
right now - hey, even when I unzip archives with commercial tools I
don't get the original timestamp for directories. For my app, I'll
wait until this feature gets requested - then do some big eye-rolling,
"oh, oh, complicated stuff you're asking there" -- while all the time
having a solution ready.
Thanks a lot for your advice.
Helmut Giese