I have just started to load the release version of Vista on my primary
development desktop (the only one with definitely enough power to let
Vista go at full flow guaranteed). The process has just finished the
compatibility check.
It told me I had to uninstall Nero buring ROM and Dell storage
Manager stuff before proceeding with the installation. No big deal.
I use VSO software rather than Nero anyway, and I am sure I can live
without the Dell stuff.
However the next paragraph went on to list stuff that would not
interfere with installation but might not work properly afterwards.
There were 4 items on the list. The last 3 were Intel Network
Configuration Services, Nero Vision 4, and Windows Messenger 5.1. No
big deal, again.
However the first item on the "potential issues" list *is* a big deal.
It is Borland Delphi 7.0 - in which many of you will be interested.
I have just aborted the Vista installation (update, not fresh load).
So I am unable to tell if it is a false alarm or not. Has anyone
else proceeded with the installation after receiving that warning? If
so, what happened? Has anyone done it with BDS2006 and not received
any warnings (and subsequently confirmed all was well)? Has anyone
done a fresh Vista Installation, and then reloaded D7 without problem?
Everyone else, of course, needs to be aware of this potentially huge
problem.
Last, but not least, is Codegear aware of this situation and in a
position to advise something other than upgrading to BDS2006?
Regards
Allan Knox
I don't understand why you are installing Vista at all?
Doesn't Vista require on-line registration?
JoeH
Several people have reported here that they are running various versions of
Delphi, including D7 and BDS 2006, on Vista.
--
Wayne Niddery - Winwright, Inc (www.winwright.ca)
"If there is any principle of the Constitution that more imperatively
calls for attachment than any other, it is the principle of free
thought - not free thought for those who agree with us, but freedom for
the thought that we hate." - Oliver Wendell Holmes
http://www.itwriting.com/blog/?postid=535
--
I think the problem is not online registration as a concept but rather
that Borlands online registration has been an extremely clunky and
annoying process. It is just a badly developed part of the software.
With WinXP at least registration is an almost painless experience. I
cant comment on Vista registration.
Craig.
I just activated another XP machine to remember exactly how the process
goes. It didn't require any serial numbers, usernames, passwords or
emails addresses. In fact I didn't type anything in, just tick a few
boxes. CodeGear learn from this.
Craig
Install D7 on Vista and just ignore the warning.
After the install and before starting D7 for the first time, select
properties on two folders, the bin and project folder.
Set permission to full control for all users (what ever it's called in
english).
Now D7 can run normally.
--
Finn Tolderlund
Finn,
Your input is much appreciated, but I am not completely following
you. You are saying "install D7 on Vista" whereas I am talking about
installing Vista while D7 is already there.
Will the setting of the properties on the 2 folders work if I take
that action after the Vista upgrade but before running D7 for the
first time after the upgrade? Or, do I have to reload D7 after
installing Vista ? In the latter case, I might as well do a fresh
install, and I am not about to do that on my primary machine.
Regards
Allan
Wayne,
I appreciate that. That was why I went to load the RTM version in
the first place. However, those people were probably using the beta
versions of Vista, and none (to my knowledge) mentioned any warning of
incompatibility which turned out could be ignored.
We are talking live Vista here. This is the one that matters (as
DevEx and many others will testify). The betas are now history.
Finn's response suggests that the problem can be overcome and all
will be well. It would be nice to hear it from CodeGear that they
have tested the most recent pure Win32 product, together with the
latest 2 BDS, both against an upgrade and a fresh install. Obviously,
they cannot speak for all Third Party components but, given assurances
on the base product, the Thirdy Party guys can then proceed with their
own testing and assurances.
Regards
Allan
Joe,
I presume the question is more wry than serious. But, please do
not take this thread off at a tangent. It is possibly just too
important to too many people to be cluttered with apple and orange
comparisons.
Just for the record, though, I did not pariticipate in the Beta for
either Office or Vista because they were supported ONLY by on-line
registration. Similarly, I am not touching Office 2007 because there
are known problems with the BDE. And yet, I am fully paid up MSDN
subscriber.
If you want to continue a debate on the point, please do so by email
or on another thread. First, though, consider the percentage
probabiility of a Microsoft OS within the latest 3 generations being
abandoned without replacement, compared with the same possibility for
a 3 generation-old, ex Borland product. Also consider what would
happen to all our Win32 products if CodeGear flourished totally (just
as we are pretty well hoping will be the case) but all Microsoft OS
died totally for an extended period. Certain things are bedrock, and
the continued availability of a PC with a reasonably current Microsoft
OS on it is one such supposition. And just in case the casual reader
missed the point, without Microsoft OS available, all ex-Borland Win32
products are toast.
Regards
Allan Knox
Not at all - and you clarified nicely, thanks. I have not looked at my MSDN
Vista DL options yet, but knew some in here were mentioning issues with the
registration procedure, so I asked.
JoeH
If your machine can handle Vista then it can handle a virtual PC.
M
Hi, do you, or anyone else, know if this is the case with the
release-version of Office 2007?
Hi Allan,
If you're trying to install Vista over an existing XP installation you will
get a warning that you have to uninstall BDS and reinstall it after you have
upgraded to Vista.
I am currently running BDS2006 with all updates and hotfixes on Vista
Ultimate RTM (MSDN-version) with no problems. I did a clean install though.
Best Regards,
Tom Reiertsen
DevExpress are warning of such problems in their latest release which
comes after the release version of Office 2007. It was their warning
which prompted me to check by killing the latest beta installation on
the machine which I deliberately expose to such risks, and which had
just had the BDE rogered. Sure enough, once the beta was uninstalled,
everything else came back to full life. So, based on my experience,
the damage is not permanent, applies only to the later betas, and may
or may not apply to the live version. Once Microsoft get round to
adding the live version to my MSDN site, I will be checking it out.
(Personally I have a suspicion that it was quietly pulled after they
became aware of this or similar problems.) I will post the result of
that check if no one else has given a definite answer in the meantime.
Regards
Allan
That was the place I first read about it, too.
> I will post the result of
> that check if no one else has given a definite answer in the meantime.
Yes, please do that - I fear some of our customers will get their hands on
Offce 2007 before me...
>If you're trying to install Vista over an existing XP installation you will
>get a warning that you have to uninstall BDS and reinstall it after you have
>upgraded to Vista.
In other words, it appears that the situation differs between D7 (for
example) and BDS2006 in an XP-Vista upgrade situation. With D7, the
warning is potential only and relates to a risk for D7, not with Vista
itself - whereas, with BDS2006, if I interpret you correctly, you
cannot perform the upgrade at all if BDS2006 remains installed.
Interesting!
>I am currently running BDS2006 with all updates and hotfixes on Vista
>Ultimate RTM (MSDN-version) with no problems. I did a clean install though.
>
Thank you Tom. That is very useful information which I am sure many
others will also appreciate, including those still waivering over the
decision to upgrade from D5-7.
Finn has also intimated that D7 will install on top of Vista, but
needs permissions resetting - but I still await confirmation whether
or not that permissions resetting will suffice for an upgrade
situation on top of D7.
>
Regards
Allan
>
Moni,
Thank you for that confirmation, but I was hoping for a "simple"
upgrade to my primary development machine - and while your implied
suggestion would allow me to check my problem, I am rather hoping that
someone else has already checked and solved it.
I have it in mind for my next generation of primary machine for it to
be native Vista (thus not relying on my continuing MSDN subscription)
and to have at least 4GB memory (rather than the current 2GB) before
entering the virtual PC world and covering continued compatibility
with XP and 2000 on a single machine. Of course, even with a single
PC capability, I will still have others in reserve - including always
a laptop and a standby desktop both holding the previous fully tested
environment.
Regards
Allan
For the non-native English speakers, waiver is a mistype and should
have read waver. Waver about is "undecided" while waiver is a correct
word but with a completely different meaning (associated with giving
up rights to something).
Please note that I am correcting myself, not someone else!
>
>Clean installation of Vista will save you from countless troubles and upgrade-related bugs. System of such complexity as Windows, cannot be upgraded reliably (especially with minimal support from third-party software developers). It was the same with Windows2000, XP, and now is the same with Vista.
Alex,
Thanks for your input, but actually I take it one stage further when
it comes to my (longer-term) main development machine. I buy a new
one with the required OS pre-installed and, therefore, covered fully
by the guarantee (and without giving tech staff the excuse that it is
"not their fault, but the other thing". I only do clean installs on
an existing PC, following some disaster or other (or upgrade of hard
disc etc.). For all other circumstances I want to emulate what my
clients might do, and an OS upgrade is what they will most likely do
if a new machine is not appropriate. In this particular instance, I
want to be able to check out Vista as soon as possible with my
existing code base.
I have followed that rule with all the OS you listed and actually
never once had a significant problem following the upgrade - at least
not one related to the upgrade. I have had plenty relating to
incompatible drivers etc. of course but that would have happened with
a clean install.
As a general observation, however, your advice is completely sound
IMO. All else being equal, a clean install is the way to go.
Regards
Allan Knox
Well, it says something like "It may not work after upgrading to Windows
Vista and/or it has know problems". It then goes on to say you should
deinstall before upgrading and reinstall after the upgrade.
>
> Finn has also intimated that D7 will install on top of Vista, but
> needs permissions resetting - but I still await confirmation whether
> or not that permissions resetting will suffice for an upgrade
> situation on top of D7.
That's probably just to circumvent the new User Account Control features.
You can also disable that on a system wide basis (which I have done on my
system).
According to the Vista help, this is waht UAC is:
"User Account Control (UAC) is a feature in Windows that can help prevent
unauthorized changes to your computer. UAC does this by asking you for
permission or an administrator? password before performing actions that
could potentially affect your computer's operation or that change settings
that affect other users. When you see a UAC message, read it carefully, and
then make sure the name of the action or program that's about to start is
one that you intended to start.
By verifying these actions before they start, UAC can help prevent malicious
software (malware) and spyware from installing or making changes to your
computer without permission."
Best Regards,
Tom Reiertsen
I had no registraion/activation problems with the release version. In
fact I must say that this was the easiest installations of any Windows
OS I have ever installed. I installed it on my HP dv8100US laptop in a
dual boot configuration, keeping Windows XP on partiion(0). In this
kind of install, it wants the parition to itself so you may want to
remove any files you want to keep on that partition, although it does
back them all up to a folder first. I also installed MS Office 2007 on
Vista without any registration/activatoin issues.
I will continue to develop Delphi apps in XP but needed to test them in
Vista (for logo compliance). They ran just fine, although I have some
work to do on the colors and fonts, etc.
--
David Farrell-Garcia
Whidbey Island Software, LLC
Q2. Do you have BDE installed with Office 2007 on either or both
partitions?
Regards
Allan Knox
> David,
> Q1. Do you have D7 or BDS2006 on the Vista partition?
>
> Q2. Do you have BDE installed with Office 2007 on either or both
> partitions?
Hi Alan,
No and No. Sorry.