Then its not browser related but rather: network-related =P
Ah. Just tested on our Comcast line (prior tests were done on an AT&T
line) and it worked fine there. Not sure what this means, but seems
the problem has something to do with the AT&T network.
On Tue, Jun 8, 2010 at 12:32 PM, Ben Baker-Smith <bbakersmith@gmail.com> wrote:
> I just tested on the following systems / browsers with the same
> results as I posted previously:
>
> Mac OS X 10.4
> -Mozilla Firefox 3.6.3
> -Opera 10.54
> -Safari 3.2.1
>
> Windows XP
> -Internet Explorer 8.0.6001
> -Google Chrome 5.0.375.55
> -Mozilla Firefox 3.0.5
>
> I am in Chicago, IL, USA
>
>
> Ben Baker-Smith
> --
> http://bitsynthesis.com
>
>
> On Tue, Jun 8, 2010 at 12:26 PM, Pedro Lopes <pedro.lopes@ist.utl.pt> wrote:
>>>puredata.org resolves to this for me: http://i50.tinypic.com/2rm5kec.jpg
>> Here it works fine (Mozilla Firefox 3.6.3 and Chrome 5.0.375.70 beta both in
>> WinXP)
>> What's your browser+OS? Could that be a browser related issue?
>>
>> --
>> Pedro Lopes
>> contacto: jazz@radiozero.pt
>> website: http://web.ist.utl.pt/Pedro.Lopes
>>
>