Similarly, I also have been unable to do any networking with the
0.10.24.4.2 (Linux x86 glibc 6) and the 0.10.25.3.1 (Win32) REBOL/View
products myself on a couple of different machines (both with proxy & no
proxy configs) which run network code with the release versions just fine
(with the exception of the new tcp interface that I can't get to send or
receive data connecting even to a telnet port 23 in the manner suggested
by the Net docs). I haven't yet looked at it hard enough to tell if it's
successfully opening sockets or not (kinda assumed it was known to be
broken) but I will now.

I'll also have to make sure all these configs are not trying to load my
old ftp2 code that works around your SYST bug to ensure that's not the
cause too.

Later,

<SS>


On Mon, 7 Aug 2000 [EMAIL PROTECTED] wrote:

> On Mon, 07 Aug 2000, you wrote:
> > Hi,
> > 
> > On my PC running BeOS 5.0.1 Pro Edition, I can't get any of REBOL's 
> > networking features to work, with either REBOL/core 2.4.24.5.2 or REBOL
> > /view 0.10.18.5.2.  For example:
> > 
> > REBOL/View 0.10.18.5.2 28-Jul-2000
> > Copyright 2000 REBOL Technologies.  All rights reserved.
> > Type DEMO to run demo if it is disabled
> > >> read http://anobject.com/
> > (30 second pause)
> > ** Access Error: Cannot connect to anobject.com.
> > ** Where: read http://anobject.com/
> > 
> > I have BONE Beta 4 installed, but I had the some problem before I 
> > installed BONE.  Fortunately, the released REBOL/Core 2.3.0.5.2 works 
> > properly.  Any idea when this will be fixed?
> 
> Works fine here. Same REBOL versions, on BeOS 5.0 Pro, without BONE.
> Have you checked your network configuration, e.g. DNS, proxies in
> user.r ? Maybe there is a stale proxy entry somewhere when running 2.4.
> 
> Are you sure the problem existed before you switched to BONE ? Networking
> changes from REBOL 2.3 to 2.4 have been fairly minor. The big change from
> synchronous, blocking network calls to fully asynchronous operation happened
> between REBOL 2.2 and 2.3. Both 2.3 and 2.4 or BeOS pass our very extensive
> network tests -- and we used REBOL/BeOS to upload the tar.gz archive
> to our ftp/web server :-).
> 
> Btw, is BONE/Beta publically available yet ? Considering the bad shape
> "normal" TCP/IP in BeOS is in it would be useful to know if BONE fixes
> some of the problems...
> 
> --
> Holger Kruse
> [EMAIL PROTECTED]
> 
> 

Reply via email to