WinBuilder on Vista x64 does not seem to work?

Posted 08 May 2007 - 06:42 PM

• Back to top

Posted 08 May 2007 - 06:51 PM

• Back to top

Posted 08 May 2007 - 07:06 PM

1st: Welcome to our community, ptr727!

2nd: Congratulations!
Now Phox has a Vista handicapped friend!

That was a little bit ironic. To the reality:

There are really known issues when running WinBuilder on a Vista host.

Sorry, they are unsolved now (maybe, they are not even known at all).
Your issue seems to be an unknown one.

We all are working on that, but you have to be a little bit patient.

Peter

Thank you for the prompt reply
For now I'll just build on XP, and I'll look forward to a Vista compatible version.

• Back to top

Posted 08 May 2007 - 07:07 PM

wb is compiled under delphi 7 and it seems that Borland has no intentions to release a x64 delphi compiler for Windows applications. http://blogs.msdn.co.../02/446697.aspx

As a possible solution they point the wonders of using .NET instead of a native Windows and create a new wb binary from scratch under a different compiler.

If 16 bit applications are supported on 32 bit OS - why aren't 32 bit supported by 64 bit OS's using something like wow (windows on windows)?


Sorry - I also use Vista, but this means no wb support for x64 so soon..

btw: Just found this info from lazarus (open source delphi alternative):
http://www.lazarus.f...h...opic&t=3749

Maybe these are good news..

• Back to top

Posted 08 May 2007 - 07:21 PM

• Back to top

Posted 08 May 2007 - 08:33 PM

Thanks for explaining - I've never handled a x64 machine around here.

Looking again on your first reply based on the explanations from the above post I can suggest that that only network acess seems unprepared for x64.

Can you try downloading and testing a wb project (effectively creating a boot disk) on XP x32 and then use the same folder for running wb under Vista x64?

If you have some time for these testings I can also learn a whole more with your feedback and this way try to isolate the components which output errors on x64 platforms (not just vista related I guess).


About the "Rules" you are right and UAC is very restrictive - under Vista you will need to disable it in order to be allowed to load hives for creating windows based projects.

UAC might also be the reason for not acessing the internet - try disabling Firewall, UAC and antivirus (if any) in order to remove them from the list of possible reasons that can interfer with wb getting online.


Thanks for explaining x64 in more detail - really hope this can be solved, delphi7 outputs very good results and wouldn't like to move from building environment because of all these new rules..

• Back to top

Posted 08 May 2007 - 08:45 PM

• Back to top

Posted 08 May 2007 - 10:51 PM

What do yuo mean does not seem to work? Doeas it start, or it fails to build?

Here are some pictures to show what I see:

• Back to top

Posted 08 May 2007 - 10:54 PM

Yes, network acess is completely disabled - not even the IE activeX is working..

Are you connected on the internet while running wb?

Do you use any proxy, and if so - have you configured IE to use proxy as well?

(Just a few doubts..)

• Back to top

Posted 09 May 2007 - 02:00 AM

Yes, network acess is completely disabled - not even the IE activeX is working..

Are you connected on the internet while running wb?

Do you use any proxy, and if so - have you configured IE to use proxy as well?

(Just a few doubts..)

Thanks to all for suggestions, but I really don't think this can be effectively remotely debugged, at least I am not up to it

I think best would be for the developers to debug on Vista x86 / x64 on real / virtual machines.

• Back to top

Posted 09 May 2007 - 06:35 AM

I already use Vista at 32bit - Just wanted to know if you had this x64 machine connected to the internet..

• Back to top

Posted 09 May 2007 - 06:56 PM

• Back to top

Posted 09 May 2007 - 09:05 PM

• Back to top

Posted 10 May 2007 - 06:43 AM

• Back to top

Posted 10 May 2007 - 09:05 AM

I also disabled both Firewall and UAC on Vista - load hive function didn't worked even when running wb with elevated privileges.

Unfortunatelly I don't have any x64 version of Vista to debug this matter..

• Back to top

Posted 10 May 2007 - 10:38 AM

@Nuno: how do you check if a computer is connected to the internet or not?
Maybe in these internal function calls is a problem (do you also read some registry values out or are these only network-API-calls?)
I'm just programming in C++ so I have not much knowing about Delphi (TurboPascal-programming is about 10years ago ) but maybe I could help you a little bit.

(Maybe at the end of the month I will upgrade my PC (new board, cpu, etc) and I wanted to buy also 64Bit OS...we will see...)

Greets
Holger

• Back to top

Posted 10 May 2007 - 10:56 AM

Hi Holger!

You can read the wb's initial network detection details here:
http://www.boot-land...?...ost&p=13760

No registry values are read - at least to my knowledge.

Previously I was using an win32 API to ping, but it was faulty on some machines - medevil complained a lot because it wasn't supported on XP SP1 (never figured out the reason why), but replacing with a built-in ping has solved this matter.

I really appreciate your help - networking is always a troublesome area and your experience is very welcome to debug this issue.

If needed I can completely hide/disable any network dependency and make wb completely aware when it is offline - I just haven't done it yet because I am in doubt on how to do it..

Holger, do you happen to know if windows send any message when a computers gets online?

It would be an efficient way to enable/disable the web tab and download center - at least a better option that adding a timer to ping the host and check the response since this event would be fired up when the computer starts an active network connection.

The main goal of network support is working on both Internet and Intranet.

Wouldn't solve the matter - but at least it would still make wb usuable and users would only need to manually add projects to proceed.


Happy shopping for a new computer - a 64 bit CPU seems fun!

• Back to top

Posted 10 May 2007 - 05:58 PM

• Back to top

Posted 11 May 2007 - 08:35 PM

@Nuno: how do you use a ping over a proxy?
Did you implemented into the internal ping-function a proxy-using (however this could be done)?
Otherwise thisone would explain why this isn't working at my workplace.
It's difficult.
Maybe you should add an option to disable this internal ping.
@ptr727: some functions of IPHelper work since 98
However, I tried that good sounding function "InternetGetConnectedState(Ex)" - which is horrorable bad
My computer is connected over WLan/DSL-Modem with the internet.
And this function returns that my "LAN-Connection" (which is completely disabled) does this connection...

• Back to top

Posted 11 May 2007 - 09:11 PM

Ping shares the same settings as the download center from the same set of components - when ping works, the download works..

Back to the testings!

• Back to top

Posted 11 May 2007 - 09:52 PM

• Back to top

Posted 11 May 2007 - 10:14 PM

Yes, I agree with you. I was first using windows API - but it proven very unstable results as you've mentioned, on most machines it would work but on some it just didn't..

MedEvil helped out debugging this out from a XP SP1 based OS.

• Back to top

Posted 18 May 2007 - 03:49 PM

Hi Nuno

I got my 64Bit system running (for testing only at the moment cause I do not have all the new devices completely here - old HD, Videocard).
It's running now with Vista64(RC1).
At the moment I'm also downloading Windows2003x64 SP2 Trial.
So I will do some tests later/tomorrow and give you some results again...

Greets and many thanks for PM-infos and friend-adding
Holger

• Back to top

Posted 18 May 2007 - 03:52 PM

Happy testing!!

• Back to top

Posted 18 May 2007 - 08:06 PM

Hi Nuno

some pretest results:
- Downloading works here - both, in W2003X64 and VistaX64RC1

At the moment I have some problems to build a LiveXP-CD.
There is the error message that I have to "... select a Window XP Install CD or Windows 2003 Install CD".
I selected the path to the W2K3x64 install files.
I think here is an error in the source checking.
Do you have an idea - maybe also a workaround for this?
How do you check if it is a correct source?
Greets
Holger

Edit got it (I think) - script is running now.
What I did:
- copied AMD64 to another folder
- renamed AMD64 to I386
- copied all files until the letter "W" from original I386 folder to the new 'I386'-folder

• Back to top