Delphi 2007 and C++Builder 2007 update #2 is now available
Update 2 available for download from the Delphi 2007 for Win32 and C++Builder 2007 registered users download pages at
http://www.codegear.com/downloads/regusers/delphi
http://www.codegear.com/downloads/regusers/cppbuilder.
Download setup.exe to your computer and run it to install the update.
The readme file for update #2 is published in CDN at http://dn.codegear.com/article/36777
Notes:
As the initial install warned, you should not try to install this patch if you chose not to store the installation information during the initial install. If that is the case, you will need to reinstall your product (either Delphi 2007 for Win32 or C++Builder 2007) and leave the cache on the machine.
If you are one of these users, the install for Update 2 will not work. If you attempt the install, it will continually ask you for the location of your cache, and since you do not have it, you cannot continue.
If you do not have the cache present, you will need to do the following:
- Uninstall Delphi (or C++Builder 2007)
- Reinstall, telling the installer to retain your cache information
- Apply this patch.
If you do have the cache, apply the patch and do not worry about the above instructions.
August 9th, 2007 at 8:17 pm
Hi,
‘Notes’ is wrong at C++Builer’s page.
http://www.codegear.com/en/downloads/regusers/cppbuilder
This page says, ‘Remote debugger for use with C++Builder 2007 applications’.
August 9th, 2007 at 11:44 pm
I can remember a post by Jim Douglas about user experience and that this has to be good.
This update does not score high in user experience. Reinstall Delphi and all third party components!!!! Very nice, not.
David, maybe you can send somebody to reinstall, while I’m in a meeting.
Please make this update more user friendly.
Kind regards,
Eelco
August 10th, 2007 at 12:46 am
Is this patch also available as a full download zip file, as was available in update #1?
August 10th, 2007 at 2:18 am
I have posted on the Update 2 readme on how I copied cache files from a machine where I saved files during update 1 to a machine where I didn’t. Maybe this will help those who really don’t want to reinstall (I really didn’t). It appears to have worked OK…
August 10th, 2007 at 3:02 am
The installer is a mess! It may look good but current implementation is far from productive.
I bought the ESD version (deleted the install cache) and now I need to re-download the stuff via installer (slow) as there is no complete ESD installation available that I could download quickly? Isn’t it possible to make one "setup.msi" file that contains whole installation, so it does not need to be downloaded into many files each time and then trying to find it in obscure location by GUID?
Keeping 1 GB of setup files on the disk for case I need to install update is also a bit too much.
Isn’t it possible to "ask for setup disk/file location" so a DVD can be provided instead of the cache? I know hard disk are cheap now, but bloatware is one thing I hate. Everyone feels free to waste my hard disk space.
August 10th, 2007 at 4:05 am
It was such a unpleasant experience installing Delphi 2007 with C++ Builder 2007 the three times it took to get it right, that I don’t want to go through that again for an update.
August 10th, 2007 at 5:10 am
Shame, shame shame! Having to uninstall and re-install Delphi just to apply a patch is ridiculous!
I’m seriously thinking to stay with Turbo Delphi instead of upgrading to D2007 and its install hell.
August 10th, 2007 at 5:56 am
Will just using the default options solve the problem?
August 10th, 2007 at 8:09 am
I haven’t even checked the install notes, but even if you guys magically found a way of fixing all the wrongs, it would still not justify the extra length of work to go through that "wonderful" install/update technology of yours.
After loosing a few hours installing Update 1, I won’t be touching another update until you guys learn to do them right. There’s just not enough in them to warrant that huge amount of time… And don’t be surprised if you start loosing customers while you still haven’t got them to trust you after releasing a product that was clearly not ready to ship when it did…
In my point of view, two major problems still exist in Delphi 2007 that need urgent attention:
1) Still incomplete and bugged Help, many times it’s just a waste of time to try and find some information there;
2) Either a lousy installer is used, or a lousy work at creating the install scripts is being done on your side. It may have solved some problems on "your" end (at least, I want to believe it has!), but it surely is the WORST install/update procedures EVER to exist on Borland/Inprise/Borland/CodeGear…
These two, clearly don’t work with "Improving User Experience"; as they are implemented now, they work AGAINST improving user experience…
Sincerely,
Fernando Madruga
P.S.: I’m submitting a copy of this comment to Jim Douglas, FWIW…
August 10th, 2007 at 11:50 pm
there are 2 options left for delphi user
a. continues with installing this very very slow process for update 2 (it will take forever, mind you)
b. ignores the update 2, pretends there is no such update!
for me, i will go for options 2 since there is no way i wanna go for this process again, unless the update touches a lot of areas.
just wonder how difficult for codegear makes a drastic change for a new installer? yes, codegear already invested money on this ‘installer’ but then please think on how difficult for the users to use it
thanks
ahmoy
August 11th, 2007 at 5:47 am
The isue might become even more problematic when having other CodeGear products installed like PHP. The registration is somehow connected and having problems with one product will interfere with other products. So be aware that you can end up with both products screwed up. Since the amount of installation times is limited you might encounter this problem too as we did. Yes, the service desk was very helpful and the issue finaly solved, but it took a huge amount of time (since the timelap of EU and VS is large) as well of installation times (first the cd, then the full products download of both products etc. etc.). I desperately am needing the old way (D6) of installation, this is only bothering the legal and paying user community and won’t stop any illegal versions, in fact will only stimulate the latter imho.
albert drent
aducom software
August 11th, 2007 at 6:53 pm
Microsoft’s installers have always been inefficient, stupid, slow and problematic. I always used Wise for my installers and never had problems while everyone else did. I changed companies in 2003 and we used InstallShield/MSI for our installer. After two years of nightmares for both us and our customers and nearly losing two huge customers because they couldn’t deploy our product to their end users, I replaced it with InnoSetup.
The new installer workeds perfectly, is lightning fast. Client deployment works flawlessly, upgrades work flawlessly. The client installer on the new one finishes in seconds. The old installer couldn’t even initialize MSI in the time that the new installer completes.
Just because MSI is the only certified installer that MS is forcing down everyone’s throat doesn’t mean you have to use it.
Stop using MSI and your installer nightmare will go away.
August 13th, 2007 at 5:04 am
Almost nothing solved for Delphi in this second patch. I don’t use Delphi anymore since even with Update 1 the stability and quality was still terrible! I’m already a happy VS.NET user. You lost one more.
Bugs & annoyances that have made me stop using Delphi:
1. when opening a project with form XXX.pas, after that opening another project with it’s own XXX.pas, if you CTRL+ENTER on this unitname it will often open the file from the previous project.
2. CTRL+LEFTMOUSE CLICK on identifiers to go to their declaration generally doesn’t work.
3. Get lot’s of exceptions from the Delphi product itself. (note that I don’t have any thirdparty tools/components installed!)
4. Help sucks.
5. Install sucks.
August 20th, 2007 at 2:25 am
like wtf.. I was hoping with CTRL+LMB on a identifer would be working in the update2… I have yet to install the update1… Please say it isn’t so.
lenn dolling
whitecrow.ca
August 20th, 2007 at 11:16 pm
I hoped something would change with D2007.
We skipped 2005, stopped using 2006 and now we have D2007 and it still sucks. When I read all the above, I put D2007 on the shelf and wait until this nighmare is over. I having a really hard time to still defend Delphi when I’m not sure about it myself anymore….. This could cost us a LOT of money.
August 24th, 2007 at 2:50 am
What is this?
I have to uninstall Delphi and then reinstall it with cache?
I’ve looked inside the box, but there isn’t a spare harddrive inside.
I can’t loose that much diskspace just for an update.
Reinstalling will take more than a day. (uninstall, reinstall, install all extra components)
From this day, we will fase out Delphi and switch to Visual Studio. (Cheaper, more stable, better support)
I say Delphi IS DEAD.
September 11th, 2007 at 12:21 am
When will you understand. It’s not the new functionality which is so badly needed, but a STABLE environment…