Run Delphi 7 On Windows Vista

Delphi on 6. 4 bit Windows 7. Some 6. 4 bit Windows notes: File location: 3.

Program Files (x. Program Files\. Likewise, 3. Windows\Sys. WOW6.

• DPI-aware applications in Windows Vista and Windows 7 February 21st 2007.
• Fix for Windows 7 and Vista StackHash or APPCRASH which occurs when Microsoft DEP interferes with the smooth performance of.exe files.
• The Windows 7 Command Prompt Environment. To open a Command Prompt window in which you can type commands and review output, as shown in Figure 29.1, click Start, All.

Windows\System. 32 – that’s Microsoft contrarian logic for you! Registry keys also are affected so that 3.

Serial Communication Library & Components SuperCom Serial Communication, TCP/IP Data Communication Library, ActiveX, NET Class Windows, Linux Library, Component. Applies to: Borland Delphi, BDE, Paradox Databases, Windows 7. Windows 7 can be very restrictive towards applications written for the previous versions of Windows. Windows 32-bit on Windows 64 (WOW64) WOW64 emulates 32-bit Windows. Under Windows 64-bit, 32-bit applications run on top of an emulation of a 32-bit operating system.

HKLM\SOFTWARE key are now installed by Win 7 into HKLM\SOFTWARE\WOW6. Node\ and legacy programs may not know to look for them there (eg. BDEAdmin). 3. 2bit ODBC drivers are set up using 3. ODBC control panel interface found here: %WINDIR%\Sys.

WOW6. 4\odbcad. 32. ODBC drivers are set up using the default 6. ODBC control panel interface found on Control Panel or here: %WINDIR%\System. Delphi are 3. 2 bit, that is, although they can run in 6. Win 7, the executables they compile will be 3. Delphi will compile 6. ODBC drivers, don’t look in the Control Panel – they are the 6.

Windows\Sys. WOW6. Help system: Microsoft ceased installing their legacy Win. Help. 32. exe application in Windows Vista and later. Thus to allow legacy winhelp to function (eg.

BDE help), you will to download and install it – see here. Get. Version: Get. Version in Vista gave a value of 6 unless you choose to run your app in a compatbility mode in which it will return whichever OS version you choose! MS Virtual PC XP Mode: a neat little functionality in 6.

Win 7 Pro version is the easy ability to create a Win XP virtual machine to run otherwise incompatible legacy software such as old sybase ASE open client drivers, and MS SQL Server 2. XP mode runs as a separate machine and is updated as usual by Windows Update, and will need its own antiviral software.

RAM allocation is only 5. Mb. your Delphi 3. I note that I am getting list index out of bounds with one of my apps running in this mode which does not occur on a XP machine nor on 6. Win 7 itself – as I do not have Delphi installed in my XP mode virtual machine, I have not debugged why this should occur. With the free VMware Player you can convert this Virtual PC VM and use it with the VMware Player which provides better performance than the XP Mode BUT you will need to pay for Windows OS (ie.

Very easy to backup your development system and you can easily transfer it to another machine. Plus you can avoid component version conflicts between your products or product versions if you use separate VMs.

I am yet to do this, does this affect your Delphi and third party component licenses? Jon Aasenden’s blog post on using VM with various versions of Delphi. UAC, Windows Resource Protection and file virtualization issues introduced in 3.

Vista and later Windows OS including 6. Win 7: Changes to HKLM and HKCR registry keys aren’t allowed under these OS versions without admin rights. Make sure you start any installation with administrator- level rights. When installing applications designed prior to Vista, and thus not UAC- aware (eg. One may need to look at temporarily disabling then re- enabling redirection – see here. Windows 7 date format bug: a known issue with Windows 7 is a bug in date format setting, thus if you use Australian date format, the date format in non- main threads remains as USto fix this, in Control Panel, Regional settings, set date format to a non- US country date format, press Apply, then reset it to your country and press apply.

Australian locale. This will install the BDE on 6. Windows, but it does not put the BDEadmin into the control panel. Instead, go to the directory where the BDE is installed – program files (x. Borland\Common Files\BDE – and you’ll find BDEadmin. If you try running BDE Administrator or SQL Explorer and modify an alias and apply edits, the edits will be saved but the app hangs (just as it did for these guys in 6. Vista no matter what they tried)You will need to set security for idapi.

Modify instead of the default Read only file access, BETTER STILL, move this file away from the c: \Program Files\ folder so that users have read/write access. Ensure BDE Administrator is set to use this new file location by choosing Open Config file, select it then when prompted, Yes to use as default file. You may also need to go into Options from the BDE Administrator’s Object Menu and check the Win. Ensure pdoxusrs. net file is on a folder with read/write access for everyone – ie.

NOT in c: \ folder! Now, Delphi may still use the default idapi. HKLM\SOFTWARE\WOW6. Node\Borland\Database Engine\CONFIGFILE0. Setting security for idapi. If you install a later version of Delphi after installing an earlier version, remember it will over- write your idapi. Now, despite all of the above, the Delphi IDE still seems to want to put the BDE Private.

Dir as the c: \Windows\System. Delphi cannot write to in Vista and later. This seems to only be an issue when trying to open TQuery components within the IDE with the cached. Updates = true. You will get an error message such as Do not have permission to write c: \windows\system.

Del. 2. MB, etc. Set TQuery. Cached. Updates = false and you are in business. Surely there must be a way to set Delphi’s Private.

Dir folder to a read/write folder? One unresolved issue is the BDE date format – BDE applications seem to default to m/d/y despite the idapi. HKLM\SOFTWARE\WOW6.

Node\Borland\Database Engine\System\FORMATS\DATE\MODE being set to 1 (which should be d/m/y), even though date settings in Control Panel are set to d/m/yyyy. A workaround for the date format issue is to call a procedure which sets date format when the application starts – I created a procedure based upon the Set. Format. Button. Click code posted here. Installing BDE manually by just installing BDE registry . Win XP BDE registry settings and then just install these on a new machine to allow it to use a file server based BDE configuration. Unfortunately, neither 3. Win 7 will allow a simple install of this .

UAC turned off. MS SQL server developer edition: Delphi 2. MS SQL Server 2. 00. Win 7, BUT you can install it on XP Mode Virtual PC on Win 7 if you really had to. If you are using a version of Delphi older than Delphi 2. Vista or later, to avoid UAC and file virtualization issues crashing your Delphi then you MUST avoid installing onto a windows created folder! Thus I install Delphi 6 on c: \Delphi.

Delphi 2. 00. 7 on c: \Delphi. Remember Delphi 6 does not have theme support of XP and later – you can add theme support by third party fixes – but then remove these if you upgrade project to Delphi 2. You may need to detect if running Vista or later and then add code to manage theme, TTree. View, etc – see Marco Cantu’s Code. Rage supplied on D2. DVDs. Delphi 2. 00.

Delphi 2. 00. 7 and 2. HOTFIX to stop the IDE / debugger crashing. For some reason the global compiler conditional defines were ignored when compiling on 6. Win 7 when they were active when compiled on 3.

Win XP. My solution was to create a text file My. Defines. inc and place this in the project folder, and then add . Just use a different My. Defines. inc file in the project folder of other project version (eg. Set. Window. Long is replaced with Set.

Window. Long. Ptr while pointers passed must e typecast as LONG.