Delphi 2007 supports Windows 2008 R2? - delphi

A client runs our Delphi 2007 app on Windows 2008 R2 via Citrix XenApp.
He's been facing an issue where the file open dialog crashes sometimes. He's applied latest updates for windows and Citrix.
I've seen many articles on the net where similar issue occurs for various apps other than Delphi like MS Office apps, VS 2008, Adobe PDF etc.
The client doesn't face this on any other application and thus is blaming our application.
If the our app's "Compatibility Mode" is "Windows XP SP3" then all is fine. Hence, client has raised a question stating if our Delphi app is Windows 2008 R2 certified.
What changes are required if we have to make our Delphi 2007 app certified for Windows 7/2003/2008/2008 R2 ?

We have fixed lots of strange Delphi (2009) app crashes on Windows 2008 R2 64 Bit Terminal Server environment with these additional lines in the DPR:
// make it Terminal Server Aware (app without installer writing to ini files / registry)
{$SetPEOptFlags IMAGE_DLLCHARACTERISTICS_TERMINAL_SERVER_AWARE}
Note: to compile, it requires the Windows unit
The crashes appeared in many unexpected places like open dialogs. With the excellent madExcept tool we found that apps crashed within operating system routines in some Windows DLLs, and disappeared when we added the "terminal server aware" flag.

I am not a Delphi developer but a Google Search for Delphi 2007 System requirement took me to this page http://edn.embarcadero.com/article/36573#requirements
The following Windows platforms are supported:
Microsoft® Windows 2000 Professional or Windows 2000 Server (SP4 or higher and security updates are recommended)
Microsoft Windows XP Professional (SP2)
Microsoft Windows Vista™
Microsoft Windows Server 2003 (SP1)
The latest service packs and security updates are recommended for all platforms
Microsoft Internet Explorer 6.0 SP1 or later
I don't see Windows 2008 here.

Its not uncommon for the following:
It would be up to you to determine and test how your app functions under 2008. Knowing that a number of things as always change with each release of windows let alone server/workstation.
You tell them under what senarios YOU will support your application being run.
If you require your app to be run as compatbility mode with xp sp3, and tell them that, and tell them YOU dont support it outside that configuration. If you wont support it under a virtual environment.. then you tell them that.
Obviously the better answer would be to test it on 2008 R2, and check all your functionality and say you will support it running in a natural state.

Related

Connection String Help Microsoft Jet 4.0 Paradox

I am trying to connect to a server in PowerPivot. I am running across a few problems. Here is the connection string:
Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\accounting001\Accounting\TimeSlips2014\Databases\Philadelphia\;Extended Properties=Paradox 5.x.
It uses NT authentication as the password. I have read all about the problems with MS Jet 4.0. I am running 64x on 64x office apps. I receive the not registered on local computer error. Can anyone help me connect. I already installed the Access 2010 DB engine however I wasn't able to get it to connect. Thanks!
The Microsoft OLE DB Provider for Jet and the Jet ODBC driver are available in 32-bit versions only. You can't run them in 64 bit mode.
The Solution
If you run a program in a 64 bit environment and need to utilize jet to open an Access, Excel or text file there are several options to make this work.
Run the program in WoW64 mode (emulates 32-bit on 64 bit systems). This will make the 32 bit drivers work.
If the application is an web app hosted on IIS 7 you can choose to configure the web sites application pool to run in 32-bit mode.
With Office 2010, there are new drivers, the 2010 Office System Driver, which will be provided in both 32-bit and 64-bit versions. You can use these drivers to let your application connect to Access, Excel and text files in a 64 bit environment utilizing the new 64-bit drivers. The provider name is "Microsoft.ACE.OLEDB.12.0". You don't need to buy or install the Office suite, the components are available as a separate download. http://www.microsoft.com/downloads/details.aspx?FamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en
Summary
It is possible to open Excel, Access and text files on 64 bit systems. You can either configure your app to go 32-bit or you can change your application to use the new 64 bit drivers.
See the original link for this information here.

Delphi 2007 on Windows 7 closes debugger opens

I installed Delphi 2007 on a Windows 7 system. When I click on the Run button I see the debugger screen open and then the entire application (Delphi) closes. I have tried running two programs, one being a simple single-button-with-message type of test program.
I can successfully compile the program in 2007.
I also have XE2 installed on the same machine and it runs properly.
I have uninstalled and reinstalled. After the reinstall I tested without reloading any of the 3rd party products.
The same computer runs 2007 and XE2 under Windows XP (dual boot configuration)
My searches have not turned up any similar symptoms. I need ideas on how to diagnose further or a possible workaround.
Thanks.
Are you using a x64 version of Windows 7?
If yes, you need the hotfix.
It is already explained here:
Delphi issues on windows 7 x64?

Is there a way to install Delphi 2010 on Windows 2000

I just downloaded the Delphi 2010 iso from my SA-subscription and wanted to install it in addition to my other Delphi installations on my notebook computer. Unfortunately it refuses to install because the machine is running Windows 2000.
Is it possible somehow to get it to install it anyway? Or is there a technical reason why it might not work, even if it installed?
edit:
Some more information:
Delphi 2009 installed fine on that computer, so dotNET 2.0 is already installed.
The Delphi 2010 installer comes up, asks me for the language to use and then says "This product requires at least Windows XP. Setup cannot continue."
What I am looking for now, is either:
a way to get the installer to skip this check and install anyway - or -
a reason why this would not work (e.g. Delphi is using some Windows API that is not available in Windows 2000)
You could try to start the setup.exe with the /Win2K parameter. Maybe this helps. But I heard from a German forum that a user who installed Delphi 2010 into Windows 2000 had lots of problems with the IDE. So use the /Win2K parameter at your own risk.
And you must have at least .NET 2.0 SP1 installed
According to the minimum system requirements, Windows 2000 is not supported. They might use some XP+ specific API's these days, but then again they might not, as Delphi 2009 installed fine on Windows 2000.
The first thing you might want to check is if you have .Net (2.0 minimum) on your machine. According to the document linked above, they try to install The .Net 3.5 distributable otherwise, and that one definitely requires XP minimum.
windows 2000 is supported in Delphi 2010, check the following link:
Target Windows 2000, XP, Vista, and Windows 7 from single source
I think the problem is from your pc, maybe because there are other versions are installed, can you post the message?

Setup for MS Robotics Studio on 64 bit WIndows

What is the best way to setup Microsoft Robotics Studio 2.0 on 64 bit Windows Vista? Appearently something needs to be done beyond the default installation to get it to run properly.
Microsoft has released Microsoft Robotics Developer Studio 2008 R3 which includes 64 bit support out of the box, no special install required. It also supports Visual Studio 2010.
According to MRDS requirements Windows 7 is the best OS to run MRDS. If you use Vista, there are high possibilities to find it difficult to run RDS. read more here and here

How to install Delphi 7 on Vista

I tried to install Delphi 7 on Vista several times and Vista prevented me from doing so by telling me that there are known problems with this application (Delphi 7). Several other people in my company experienced problems with installing D7 on Vista.
This lead to the conclusion that we were at risk with our D7 application, as the company could within the lifetime of the app switch to Vista or Windows 7 and newer Delphi versions are not in the policy of the company. Therefore management decided on rewriting the app in C#.
My question(s):
How to install D7 on Vista
Experience with such an installation
Risk assessment concerning stability of IDE and developed programs
Risk assessment concerning executability under Windows 7
Not using any third party components or database - there should be no problem running the developed app under Vista. If not able to develop and debug under Vista (which at the point being will be the only customer platform, yes, internal programming) will result in a sort of cross platform development - if we would be allowed to keep XP as the development platform.
It is not a developers decision to rewrite, it has been done in the company for the last 3 years: if you had to significantly touch an app developed in Delphi or if there was a certain risk of it not to survive the planned life circle/life span, it had to be rewritten. The life cycle just expanded to 2015 due to canceling another project.
So the main issue here would really be: I would like to have educated arguments about the risks.
Running Delphi 7 under Vista is no problem if you can turn UAC off. With UAC on, you get an error message when starting D7, but it still works, just click ok and go on.
Programs compiled with D7 have no problem with Vista. But new features of Vista are supported by Delphi 2007/2009 only.
We use D7 on XP and on Vista, building and maintaining a commercial App which has gone from D2 to D4, D5 to D7. Besides problems with the BDE, which made us switch to DBX (Corelabs) there are no problems.
Just follow these instructions and you'll be fine. No reason to turn off UAC! I've been running Delphi 7 on Vista for about a year without any problem at all. Debugging is totally fine too.
http://www.drbob42.com/examines/examin84.htm
For installing Delphi 7 in Vista, you can try this patch from Microsoft.
http://support.microsoft.com/default.aspx/kb/932246
As for the rest someone else I suspect will have more knowledge.
I have Delphi 7 working fine on my Vista development box. Yes there was a few issues during installation, but no more than other applications and these issues have been resolved in subsequent versions of Delphi.
None of this should cause problems with apps developed by D7 for Vista. We use Delphi as our primary development tool for all our applications and they work just fine with Vista.
It sounds like this is an excuse by someone in the company to get rid of Delphi and move to C#. Typical FUD tactics. There may be genuine reasons for your company to move away from Delphi, but Vista compatibility should not be one of them.
Also, if you'd like all the Vista-ready features in your Delphi 7 application, have a look at this article here: Creating Windows Vista Ready Applications with Delphi
This will make it so that your application correctly appears when doing Flip3D, or when showing a preview thumbnail when hovering over the app in the taskbar. Essentially, this will give you the "Vista-readiness" of Delphi 2007, from within older versions of Delphi (I have used this with Delphi 2006 and it works very well).
You also get the new Vista task dialogs and new Common dialogs with the modifications listed on the linked website.
I think there's a big jump from having trouble installing D7 in Vista (D7 which after all contains low-level bits and pieces for the debugger and which doesn't know about the 'correct' place to put things under Vista), to assuming that your own app will have problems with Vista...
You have the source code, you can test your program running under Vista, you can make whatever (usually minor) tweaks are necessary to your code.... I'm really surprised that you would decide to rewrite the app in another language just because you can't get the (old) development tool to install under Vista.
We need to know more about what your application does, and what components you make use of, to be able to make any guess at your 3rd and 4th questions. They're too general.
FOr instance, I have several D7 applications on the market, one of which uses open-source Interbase 6 with Delphi and can be a problem to get installed/working on Vista Home (the process seems less painful on Vista Business). Another of our apps uses SQL Express 2005 and runs quite happily on Vista. Our newest app, written in D2007, runs fine on Vista. On both Delphi platforms, our two main 'third party' tools are DevExpress controls and ReportBuilder.
I have been using D4 with Vista for year as one of our key products uses it, its good version still and there are workarounds to make it use new Vista features. You can call any win32 API (new functions) so there is no point to update to D7.
I installed/moved D4 to my new machine by hand:
1. by exporting registry hive(s)
2. registering a few components
3. copying files
thats it.. no need to run slow setupper.
As others have noted, there is no problem running Delphi 7 applications under Vista: We do this with a multi-hundred-thousand line Delphi 7 application that uses numerous third-party controls (Developer Express grids, TSILang translation components, etc.).
We use Vista as our primary operating system, but we run the Delphi 7 development environment in a Windows XP Virtual machine. It works perfectly, and there are no installation issues.
It is very simple really.. All what you have to is the following:
Search UAC (User Account Control) off and then intall delphi7 but, you must have no other version of delphi on your computer.
1,2 in Vista) no problems heard if you install http://support.microsoft.com/kb/947562 and configure UAC;
3) None stability issues are known to any of my friends here...
4) Not using Windows 7 with Delphi 7... But heard of many problems with both...

Resources