Discussion:
Delphi Win32 2007and Windows Vista
(too old to reply)
sjors
2008-01-30 14:47:11 UTC
Permalink
Since this discussion runs in the corridors here. Say I have D5 programs,
and I want to convert them to D2007 Win32. Can these programs run on Vista?
Are there any limits to these programs. I think one of the main reasons we
want Vista is that you can address more memory. But on the other hand Delphi
will probably only be used for GUI, not compilcated calculation code. That
will be called from the GUI.

Any ideas? Before we all switch to MicroSoft Visual Studio ;-)
Peter Below (TeamB)
2008-01-30 18:18:50 UTC
Permalink
Post by sjors
Since this discussion runs in the corridors here. Say I have D5
programs, and I want to convert them to D2007 Win32. Can these
programs run on Vista?
Even D5 programs can run on Vista. They will just not be able to use
the new Vista UI features. D2007 has been enhanced with Vista
compatibility.
Post by sjors
Are there any limits to these programs.
Vista is a limit in itself, regardless of what you program in <g>.
Installation requires admin rights, the access to folders etc. is much
more restricted than on older versions. Each user has its own set of
folders and requires elevated rights to write to folders outside his
home area. These special areas also existed on older Windows versions,
access to other places was just less restricted for "normal" user
accounts.
Post by sjors
think one of the main reasons we want Vista is that you can address
more memory.
Actually nobody needs Vista but Microsoft <g>. More memory space is
only available in the 64 bit version, and 32 bit programs (D2007 does
not produce 64 bit programs) will not be able to take advantage of
that, at least not more than they already could on Win2003 server (3GB
user address space).
--
Peter Below (TeamB)
Don't be a vampire (http://slash7.com/pages/vampires),
use the newsgroup archives :
http://www.tamaracka.com/search.htm
http://groups.google.com
sjors
2008-01-31 11:11:06 UTC
Permalink
Post by Peter Below (TeamB)
Actually nobody needs Vista but Microsoft <g>. More memory space is
only available in the 64 bit version
Ah yes, sorry my mistake I did not explain it correctly. We want to use the
64 bit version of Vista to address 4GB of user address space for certain
pictures and movies. So the old programs, just menu's and dialogs, could run
under Vista 64 bits, but to address the 4GB they should call a module
written for Vista 64 bits?
Remy Lebeau (TeamB)
2008-01-31 18:15:30 UTC
Permalink
Post by sjors
Ah yes, sorry my mistake I did not explain it correctly. We want to
use the 64 bit version of Vista to address 4GB of user address space
for certain pictures and movies. So the old programs, just menu's and
dialogs, could run under Vista 64 bits, but to address the 4GB they
should call a module written for Vista 64 bits?
Why not use 64-bit XP instead? Vista is such a pain for developers to
support, is it really worth the hassle?


Gambit
sjors
2008-02-01 09:11:23 UTC
Permalink
Post by Remy Lebeau (TeamB)
Why not use 64-bit XP instead? Vista is such a pain for developers to
support, is it really worth the hassle?
That could be an option. But would that make the use of the old Delphi 5,
Win32 GUI programs easier?
Remy Lebeau (TeamB)
2008-02-01 21:11:42 UTC
Permalink
Post by sjors
That could be an option. But would that make the use of the
old Delphi 5, Win32 GUI programs easier?
XP has been around for a long time and is highly supported by
Borland/CodeGear tools. Vista is still new and CodeGear is still getting up
to speed on all the new behaviors/breakages that brings.

The main problem, though, is that 32-bit processes can only access 2 GB of
memory (3 GB with a special PE flag). Borland's Memory Manager in D5 can't
address more than 2 GB even when the flag is enabled, though. Not sure
whether FastMM can. Also, the FastCode project (which is incorporated in
later VCL versions) supports more than 2 GB, but that only affects the RTL,
not the memory manager.

Otherwise, you need a true 64-bit process to access 3+ GB, whether you use
XP or Vista, but Borland/CodeGear has not released a 64-bit compiler yet.
Or simply don't code your program to require so much memory at one time.
Process your data in smaller, more managable, chunks under 2GB instead.


Gambit
WillR
2008-02-04 13:11:44 UTC
Permalink
Post by Remy Lebeau (TeamB)
Post by sjors
Ah yes, sorry my mistake I did not explain it correctly. We want to
use the 64 bit version of Vista to address 4GB of user address space
for certain pictures and movies. So the old programs, just menu's and
dialogs, could run under Vista 64 bits, but to address the 4GB they
should call a module written for Vista 64 bits?
Why not use 64-bit XP instead? Vista is such a pain for developers to
support, is it really worth the hassle?
Gambit
Because 64 Bit XP is really, really bad? This I can guarantee personally.

If you want 64 bit Windows than Vista 64 is the only workable choice.
You can use drivers from Vista or the Windows XP 64 bit drivers.

We are using Vista 64 bit and Windows XP dual boot. XP gets turned only
for the very few programs that simply cannot function under Vista 64 --
Hughes BGAN Satellite Communications gateway for example.

Even the Microsoft Virtual machine seems to function under Vista 64.
--
Will R
PMC Consulting
Peter Below (TeamB)
2008-01-31 17:44:56 UTC
Permalink
Post by sjors
Post by Peter Below (TeamB)
Actually nobody needs Vista but Microsoft <g>. More memory space is
only available in the 64 bit version
Ah yes, sorry my mistake I did not explain it correctly. We want to
use the 64 bit version of Vista to address 4GB of user address space
for certain pictures and movies. So the old programs, just menu's and
dialogs, could run under Vista 64 bits, but to address the 4GB they
should call a module written for Vista 64 bits?
I'm not sure if you can mix 32 and 64 bit code in a process...
--
Peter Below (TeamB)
Don't be a vampire (http://slash7.com/pages/vampires),
use the newsgroup archives :
http://www.tamaracka.com/search.htm
http://groups.google.com
Loading...