Euphoria Ticket #918: Inno setup files will not compile with new versions of Inno setup

We are required to set the Minimum setup to 5. Discuss on the mailing list.

Details

Type: Bug Report Severity: Normal Category: Distribution
Assigned To: unknown Status: Won't Fix Reported Release: 4.0.5
Fixed in SVN #: View VCS: none Milestone: 4.0.6

1. Comment by jimcbrown Jan 26, 2015

Why not discuss the issue here?

I guess we have no choice. It's unrealistic to expect us to maintain support for 9x when the installer program we have used has dropped it. We'd have to use dual installer programs or something, or come up with a non-installer zip to continue 9x support ... probably not worth the effort.

Maybe 4.0.6 should have 9x support, but it'd be the last one to do so, and we can officially drop it in 4.1.0

2. Comment by SDPringle Jan 26, 2015

Can we officially drop it in 4.0.6?

3. Comment by jimcbrown Jan 26, 2015

Dunno. We weren't suppose to even have a 4.0.6 release, it was suppose to be 4.0.5 and 4.1.0 at the same time....

If 4.0.6 is the very last one of the 4.0 line... not sure it's a good idea to drop a platform at the end of it.

4. Comment by SDPringle Feb 08, 2015

Lets release a zip file with the 3.1 installer. :)

5. Comment by SDPringle Oct 20, 2015

Changing the assignment status of this ticket because I do not have the hardware capable for testing this ticket.

Euphoria release 4.0.0, wouldn't work with 9x because it was compiled in such a way that all pointers from malloc needed to return pointers that were aligned on a 8-byte pointer value. On Windows 9x, it would simply crash with an assertion error.

In order to be portable you needed to apply a very specific set of flags and this was not done for the release. So, there is no loss in portability in going with the new Inno setup because 4.0.0 was not portable to Windows 9x systems anyhow.

6. Comment by ne1uno Oct 20, 2015

in 2011 I ziped up the last known to work on win9x version of eu4 (unofficial) https://code.google.com/p/eu4qt/downloads/list

google has shut down code.google. so eventually that link could stop working. I'll copy some of the files to sourceforge eventually http://sourceforge.net/projects/eu4qt/

current versions eu4 may still build on win9x with the right make switches, but, a few socket routines will fail and some other minor problems.

won't be long before Xp builds will start to fail to be supported in installers. already seeing problems in Xp-Sp2 where programs need at least Sp3 or hard BSOD crash. fewer and fewer tests run on Xp so things can break before anyone realizes.

  • euproria still ok though I haven't run any installers.

7. Comment by andi49 Oct 22, 2015

Sorry for interrupting. But who cares about Win95? Sorry, i do not understand. I checked my cd-board and i found a cd from 1995 SUSE Slackware with Kernel 1.2.13 (and developer kernel 1.3.25). Do you also want to support this one? Yes, i know the win32 Api is more stable than every thing the *ix frontier have to offer. But supporting a 20 years old OS make not really any sense. Just my point of view

8. Comment by jimcbrown Oct 22, 2015

Maybe we should just drop 4.0.6 altogether. 4.0.5 is the least release of the 4.0.x line, and the last to support 9x.

Then 4.1.0 will be released only supporting XP and up.

9. Comment by jimcbrown Oct 22, 2015

I really don't like the idea of dropping support for a platform in what's only a patchlevel change (4.0.5 to 4.0.6) - it feels like too big of a backwards incompatibility.

But, the more I think about it, the more dropping 4.0.6 altogether makes sense. Virtually everybody still using OE is using some version of 4.1 now. Most devs are probably set up with gcc only, and can't do a 4.0 release anyways. It's just been too long since 4.0.5 was released and 4.1.0 will be just plain too different, having added support for ARM and dropping support for OpenWatcom.

10. Comment by SDPringle Oct 22, 2015

This problem doesn't change what 4.0.6 would run on. Run a copy of 4.0.5 against the tests in the tip of the 4.0 branch. Looks bad. Two years with out a release. We will keep getting bug reports for bugs that have been fixed because they are present in the latest release 4.0.5.

11. Comment by jimcbrown Oct 23, 2015

So you are in favor of releasing 4.0.6 for 9x then?

12. Comment by jimcbrown Oct 23, 2015

It's been a while, so I've forgotten...

Why can't we use the same version of Inno Setup that was used on 4.0.0 to ship 4.0.6 ?

Anyways, the bug reports should stop once 4.1.0 ships. I dont think a 4.0.6 release is needed just for that.

13. Comment by SDPringle Oct 23, 2015

You can use the old version of Innosetup. Hold on to your old binaries and back them up!

14. Comment by jimcbrown Oct 23, 2015

Closing this out as Won't Fix.

If we do release 4.0.6 then someone will have to use an older version of Inno Setup to do the official release. Simple as that. Regardless, 4.0.x will be the last line to support 9x.

For 4.1.0 we'll bump it up to 5, and drop 9x support.

Search



Quick Links

User menu

Not signed in.

Misc Menu