Hello,

I have a new PC using windows 7 and I want to run D3 on it. In the past I moved from NT to XP by instaling D3 from the software cd and then fileloading from a filesave and all has been well. I have now moved to a pc with windows 7 and when I try to install from the cd I get the message "Runtime error 5 - invalid procedure call". I have tried running the cd with the compatability mode "windows NT 4" but no different.

Could anyone tell me if I can run D3, it is D3 7.1.2, on windoows 7, or am I flogging a dead horse.

Thanks for any help,

Chris

On Wednesday, 18 July 2012 05:24:27 UTC-4, chrisjpotts wrote:

That's a very, very old version of D3. You really should consider upgrading. I'm positive it's not certified for Windows 7, though I do not think that is the problem with installation.

Have you tried copying the contents of the CD to a folder on the W7 machine and running the installation from there?

Other than that, I've not had trouble installing D3 by downloading the desired version from the TigerLogic FTP site. However, the oldest version you'll find there is 7.4


--
Kevin Powick

On 18/07/2012 11.24, chrisjpotts wrote:
You need D3/Windows 7.5.5 (minimum) cause RPC changes introduced by
Microsoft starting with Vista; for 7.5 the latest is 7.5.8, but if You
upgrade please consider v.9 (actually 9.0.4).

Stefano

Hello Stefano, thanks for your reply. I have a small contract to maintain a Local Authority Mortgages system which I wrote in the nineties and which is now coming to an end because all but a very few of the loans have been repaid. The PCs which run the system for my client are not going to be changed, but the one I have here at home which I use for maintenance and to play with, I have changed for a Windows 7 machine. For the amount I use it, it is not worth paying for an up grade. I have looked on the tigerlogic website, but could not find how much an upgrade would cost.

Thanks anyway for your advice.

Chris

Thanks also to Kevin, whos reply has been deleted, I had not tried your suggestion, but obviously have now, and the error message appears as before.

Thanks

Chris