After getting Delphi 2007 to work again I tried to do the same for Delphi 2005 and 2006.

After getting Delphi 2007 to work again I tried to do the same for Delphi 2005 and 2006.

Both versions require the dotNET framework 1.1 which is officially no longer supported on Windows 8 (and 8.1). According to Microsoft, you should contact your independent software vendor (ISV) to have the application upgraded to run on the .NET Framework 3.5 SP1 or later version. Good luck with that. ...
http://blog.dummzeuch.de/2013/11/10/delphi-20052006-on-windows-8-1/

Comments

  1. I don't see any real advantage of making D2005 and D2006 run on Win8. As a developer using a win8 computer, if you have to maintain old code, you could probably use a virtual machine with an older Windows.

    ReplyDelete
  2. I am maintaining GExperts for various Delphi versions. It's very inconvenient to have to start one or maybe even multiple VMs to compile the sources for all versions.

    ReplyDelete
  3. I'm on the "use an old VM" side, sorry. It's much easier to just know that it works and not spend time trying to kludge the awful. But I support whatever makes you more willing to maintain GExperts because that's an awesome toolset :)

    ReplyDelete
  4. Thomas Mueller Your host Win8 PC plus one single VM running XP or Win7 is probably enough to run every Delphi version.

    ReplyDelete
  5. For now, one VM is enough, but since Microsoft will try to avoid another Windows XP, there will be more, probably incompatible updates in the future. But you are right, for professional development, I would probably go the VM way. Since this is my private computer and the development I do on it is mostly hobby projects, it's more likely that I will simply drop support for anything but Delphi 7, 2007 and XE+. Maintaining a VM is no fun. Currently Delphi 6 won't work. It keeps insisting that it must be activated again. So if I don't find a way to get aground this issue, Delphi 6 is likely the first version to be dropped. I never actually used that version, I went straight from Delphi 5 to Delphi 7.

    ReplyDelete
  6. For what it's worth, I have a Windows 7 VM which is my Delphi environment.

    A Windows 8 VM hosts my Visual Studio environment (including Oxygene, of course) and also provides a test environment for any Delphi apps.

    I have another Windows 8 VM where I sandbox new Oxygene beta's before rolling out to my dev VM.

    Then I have two further Windows 7 VM's - one for games and the other for various niche productivity apps that I don't want/need complicating my dev machine.

    In addition to all those I have a VM running a LAMP stack and an x86 Android VM.

    My host machine is a Mac and with 32GB of RAM I can comfortably run both my Delphi and Visual Studio environments concurrently.  :)

    To get around the Delphi 6 activation issue, Delphi distiller might help if you can track it down, though I forget how far back it's support for older Delphi versions went.  Of course, if/when/however you do resolve the issue, the beauty of a VM is that you can just take a snapshot/backup/template of your VM and barring a disaster you will never need to reinstall and activate ever again, just revert/restore/recreate from template.  :)

    ReplyDelete
  7. Delphi Distiller seems to be a rather elusive tool...

    ReplyDelete
  8. Look for LiteApplications old web pages which is where you could download Delphi Distiller. All its pages were taken down by Embarcadero request, and Alvaro (Delphi Distiller author) stopped development and moved from Delphi to GO. AFAIR, this tool supports Delphi versions up to 2010. This is about original Delphi Distiller. Newest Delphi Distiller (different project from different author) doesn't provide means to remove any license checks.

    ReplyDelete

Post a Comment