I don't have a machine to test fusion 12 or less to verify if line 140 also needs updating.

I don't have a machine to test fusion 12 or less to verify if line 140 also needs updating.

@Stromweld apologies for the delayed response here. I've been traveling so just catching up. I have Fusion 12 and can confirm that we need some extra logic for fusion 12.

Channeling @tenthirtyam here, Fusion 12 is essentially unsupported as of March this year. Which seems to imply that maybe we should look to add the fusion driver or let Fusion 12 be for 1.0.8 and move to a new minor version for Fusion 13. Thoughts?

If it's unsupported that would make sense to me to potentially drop support and simplify the driver. I'd think since that would be a breaking change for all those with fusion 12 and below that it would warrant a major version increment. 1.x would be for 12 and below, where 2.x would then be for 13+.

Can we push this fix for x86 packer vmware builds and create an issue as a follow on to decide on what to do with fusion12 and earlier support?

@tenthirtyam any update?

@nywilken @Stromweld - while it could be considered a "breaking change" I recommend the following:

• Release v1.1.0 to address support for Fusion 13.x / Workstation 17.x and the change for the isoimages.
• Previous versions, specifically v1.0.8 should be used for Fusion 12 / Workstation 16 which are no longer under general support.
• Note in the CHANGELOG .mdand the GitHub release.
• Collaborate and review the scope to invest in a cleanup of the codebase and rev to v2.x.x.

@nywilken - This pull request can be superseded by #139.