Re: [Hermesmail-discuss] How can I compile Eudora/Hermes Source Code ?

[Curtis M. <cm...@db...>]

Hi Ronald,
If you would like to give it a go I have VS 2005 Pro. I can send an 
ISO image and license key. Wish I had more time!
Regards,
Curtis Meadow

At 12:33 PM 1/8/2021, Ronald van Ginkel wrote:

>Hi Steve.
>
>Thank you for your answer, but the only thing I need to know is if 
>it is possible to compile the source code of Eudora or Hermes and 
>what is the necessary environment to do it.
>
> From here I will be able to understand where the project is 
> standing and see if I can help in any way.
>
>Regards!
>
>Ronald
>______________________________________________________________________________________________________________________________________
>At 06:48 AM 1/8/2021, Ronald van Ginkel wrote:
>
>>Hi Steve.
>>
>>I took a way, but I finally could setup a Virtual Machine with 
>>Windows XP 32 Bits (Visual Studio 2002 cannot be installed on a 64 
>>bits OS), installed VS2002 and imported Hermes project.
>>
>>... but it cannot been compiled.
>>
>>As I see, project file needs at least 2010 version.
>>
>>I've installed a VS2010 and tried to compiled, but I get a lot of 
>>errors, most of them due to the use of 'noexcept' expression that 
>>it's only supported at VS 2015 or above, and with VS2015 I get tons 
>>of errors trying to compile.
>>
>>Can anyone tell me is there a way to compile the source code ?
>>
>>Thank you in advance.
>>
>>Ronald
>
>Ronald,
>
>My main development machine keeps changing, and I have changed 
>motherboards 1-2 times in recent years, so the environment I first 
>tested the Eudora source code in no longer exists.  This pre-dated 
>the 'Hermes' project by several months at least.  I don't have the 
>'Hermes Project' files.  I have the files that were released from 
>the Computer Museum that Qualcomm authorized.
>
>A little common sense:  VS2010 didn't exist at the time of the final 
>release of Eudora, so it couldn't have been the required version.
>
>When a newer version of Visual Studio tries to open a project from a 
>previous version of Visual Studio, it will convert the old project 
>file to the new project file.  It also shows a warning box on the 
>screen when it does this, and gives you the option to save the old 
>version unmodified but you have to enter a new name for the old file 
>to use.  So if you had initially tried to compile the source code 
>with VS2010, the project file was converted.
>
>I don't presently have Visual Studio 2002 installed.  I did have it 
>installed in a 64-bit Windows 7 environment.  As I recall, it wasn't 
>easy to install.  I just finished a search, and I found some install 
>instructions which say that to install it, you need to not already 
>have newer versions of Visual Studio on the system, and there were a 
>couple of specific items you need to check-off and not install, for it to work.
>
>Use of Windows XP to make a compiling environment is a common work 
>around for these kinds of problems. I recently (recent defined as 
>within the past 2 years) had to run a 16-bit program that was 
>compiled using QuickBasic.  I had to do the same thing, as Windows 
>XP could run 16-bit programs.  I soon went to some trouble to write 
>a replacement program that runs in a 64-bit environment.
>
>I don't know anything about this 'noexcept' expression you are 
>talking about, and anything I say is going to be speculation.  I 
>generally do most of my work in older versions of Visual Studio.
>
>Steve
>
>
>_______________________________________________
>Hermesmail-discuss mailing list
>Her...@li...
>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss
>
>
>______________________________________________________________________________________________________________________________________ 
>
>_______________________________________________
>Hermesmail-discuss mailing list
>Her...@li...
>https://lists.sourceforge.net/lists/listinfo/hermesmail-discuss