World: r3wp

A whole bunch of VID documents have been uploaded and updated:

http://www.rebol.com/recent.html

I still find it totally confusing that R2 & R3 stuff is mixed. I 
can't see on all pages if it's R2 or R3.

it should be possible to change, as it seems R2 and R3 docs use different 
menu headers.

so I gather there is a separate build script for R3 docs.

I think I'd rather see a 64 bit release of R2 than a R3 release now.

is there any solution or idea for multiple feeding a running console 
app
started via call/wait/input/output ?
have tried a pass a open port but no luck. the console needs more
than one command to work properly. the ideal solution would be to

hold the console app permanently open, feed it via write-io or (something
like this) and parse the output. any hint?

If your app runs under linux, you can use the telnet scheme to command 
the app.

thx sqlab

On 64 bit: really? Why?

Because Windows 2008 server is a 64 bit platform and I can't read 
the registry anymore

32bit applications can not read the 64 bit registry

Huh?

So, I can't even connect to ODBC DNS on windows 2008

DSN

I'm not familiar with changes MS has made to make the OS 64 bit. 
 Does this change apply to all API functions?

Don't know .. just know if affects the windows registry

Brian will know the details

I can understand changing various data-related APIs to allow 64 bits, 
but in general, 64 bit systems are just marketing ploys.

I think it's part of the virtualization stuff that 2008 does to make 
the 32 bit app think it is running under a 32bit os.

(BTW, I get to say this because the first 64 CPU OS architecture 
I helped design was in 1981 at HP.)

1 min... let me google it.

http://msdn.microsoft.com/en-us/library/ms724072(VS.85).aspx

So you have a fix?

Looks like just a flag change. In theory, easy. In practice, someone 
will need to test it.

I setup a Windows 2008 server on Amazon.  Setup Firebird 64 bit and 
a DSN.  Then tried to connect using ODBC.  Failed.

Where did it fail? In connect? What was the error msg?

Can't find the dsn entry

So, I'm assuming that it can't read the registry

Also, my client app under W64 (7/vista) can not read the registry 
either ...to see if certain 64 bit apps are installed ( Ghostscript 
etc )

So, any possibility of a 64 bit release of R2?

I'm not yet to the point of agreeing that this is a registry problem.

Someone was complaining that checksum ports don't work for > 2Gb 
files

Easy enough to check if you have a 64 bit windows available

Seems to me that 64 bit windows is now standard for many manufacturers 
like HP

So, you see an error "ODBC error: ***"  correct?  What's the **** 
part?

I'll have to reboot the Ec2 instance to check it

The effort to make R2 work properly in 64bit >> releasing R3 and 
adding things like native ODBC to the open host code.

Essentially, R2 is supported and gets some fixes, but not a rewrite.

Or, should I say, the rewrite is R3.

Do you have access to any Windows 64 bit PCs?

There's a pile of boxes here, one being Win64 but has not been booted 
in five years, min.

Can you create an account for me on your amazon sys?

I am going to try and start it ...

going to take 15 mins to generate the password for me

I didn't write it down since I didn't think I was going to use it 
again

ah.

Still, 15 mins seems like a long time.

An invalid pass crack should take ever-increasing authentication 
times... so a 15 min password gen time seems silly.

Does your app run in R3? If not, could it?

The ODBC port interface is only about 2 pages of C, so could probably 
be moved to R3 "easily enough" at the open host level.