World: r3wp

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.

Then, there's also the dialect part.

no good .. I've lost the password so can't access it anymore.  And 
it won't generate a new password for me.

It was just an experiment anyway.

Well, IMHO, I'd rather spend the time getting DB access generally 
working from R3.

Especially since I'd only need to write 10% of it.  (I've been told 
I should delegate.)

Well, my app uses odbc so without it, it won't run.

The gui is not important

And it uses SSL :(

If I had to guess, I'd say it's a version issue.

There are not any registry calls in the ODBC port.  But, it's always 
been a little-bit version sensitive.

The connection flags are likely specifying 32bit data modes, so the 
ODBC server is rejecting it.

Ok, assuming that is the case, what about reading the registry when 
it is required?s

I run Windows 7 x64, so can test there.

Graham, is it possible that Firebird 64bit doesn't come with 32bit 
connection libraries? Unless there is some IPC or TCP layer between 
the client libs and the server, possible if the client and server 
are on the same system, then it is possible that the x64 version 
may not be connectable from 32bit apps.

I haven't tried in that situation, but it might be possible that 
32bit DSNs aren't the same as 64bit DSNs. Let me check.

I don't have any 64bit databases here, so I can't check. Have you 
tried connecting with MS Access?

Don't have Access.  I'm running this on a Windows 2008 virtual server 
on Ec2.

There is a 32bit library I think in a Firebird wow64 directory, and 
using this and a dsnless connection, I can connect to the database.

I'm not too concerned about this in view of this work round, but 
I would like a way rebol to access the 64 bit registry if it's just 
a flag setting ...

Just have to rewrite my installer to switch to creating a dsnless 
connection if it detects running on 64 bit windows

Maybe reboltutorial guy solved our R2 installer problem faster then 
us :-) http://reboltutorial.com/blog/how-to-create-your-own-setup-package/

Is it in a Firebird wow64 directory, or the Windows wow64 directory? 
It seems to me like the 32bit ODBC drivers aren't installed, registered 
with ODBC. Check the ODBC configurator, look at the drivers list 
and see if the 32bit drivers are listed there.

Firebird wow64 directory

And is it listed in the ODBC drivers list?