Tim Nikias wrote:
> Still, an answer question 2, anyone? ;-)

Not sure, it _could_ be that the Windows 3.6.1a does contain the fix for this...

	Thorsten

Post a reply to this message