From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,65b902127ca8a604 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII Path: g2news2.google.com!postnews.google.com!n4g2000vba.googlegroups.com!not-for-mail From: Adam Beneschan Newsgroups: comp.lang.ada Subject: Re: Issue with GNAT GPL 2009 and GtkAda Date: Tue, 30 Jun 2009 08:26:16 -0700 (PDT) Organization: http://groups.google.com Message-ID: <87d92ccd-b232-42c4-ad5c-f69c3c6dbcef@n4g2000vba.googlegroups.com> References: <4A414EBB.8060204@free.fr> <1avd65rn49abv$.krcxo2gdzb16$.dlg@40tude.net> <4a43c9ce$0$420$426a74cc@news.free.fr> <4a44ae4e$0$6295$4f793bc4@news.tdc.fi> NNTP-Posting-Host: 66.126.103.122 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1246375576 10387 127.0.0.1 (30 Jun 2009 15:26:16 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Tue, 30 Jun 2009 15:26:16 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: n4g2000vba.googlegroups.com; posting-host=66.126.103.122; posting-account=duW0ogkAAABjRdnxgLGXDfna0Gc6XqmQ User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; WOW64; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.5.21022; .NET CLR 3.5.30729; .NET CLR 3.0.30618),gzip(gfe),gzip(gfe) Xref: g2news2.google.com comp.lang.ada:6759 Date: 2009-06-30T08:26:16-07:00 List-Id: On Jun 30, 4:13=A0am, Stephen Leake wrote: >> > Aside: The "blank screen" problem seems to be somewhere between our we= b > > server and the broad Internet, because it sometimes happens when I surf= out > > as well as surf in. It seems to be caused by overloading with too many > > requests (especially a problem because of spammers constantly pounding = our > > mail and web servers); > > When I switched from Firefox to MS Internet Explorer, the problem was > immediately and consistently solved, so I don't think that's it. I believe I've still had the same behavior occasionally with IE. (IE7 to be specific.) -- Adam