AppleWin 1.30.0 and supported Windows versions

[TomCh]

I've released a new AppleWin 1.30.0 here:
https://github.com/AppleWin/AppleWin/releases/tag/v1.30.0.0(try2)

There's nothing hugely significant feature-wise in this release (although it rolls up a fair chunk of internal refactoring work). But from a supported-OS point of view, I've built it with a platform toolset that now only supports Windows XP and above.

NB. I'm not testing against Win XP (only Win7-64 and Win10).

I anticipate that I'll jump Windows OS again at the end of this year to limit support to just Windows 7 and above.

The legacy 1.29.x versions are still available at https://github.com/AppleWin/AppleWin, for anyone needing them for older OS's (but obviously won't continue to be maintained).

Tom

[johnsonlam.hk]

Post by TomCh
https://github.com/AppleWin/AppleWin/releases/tag/v1.30.0.0(try2)
There's nothing hugely significant feature-wise in this release (although it rolls up a fair chunk of internal refactoring work). But from a supported-OS point of view, I've built it with a platform toolset that now only supports Windows XP and above.
NB. I'm not testing against Win XP (only Win7-64 and Win10).
I anticipate that I'll jump Windows OS again at the end of this year to limit support to just Windows 7 and above.
The legacy 1.29.x versions are still available at https://github.com/AppleWin/AppleWin, for anyone needing them for older OS's (but obviously won't continue to be maintained).
Tom

Glad to see new version!

[A2CPM]

On Monday, April 19, 2021 at 4:43:04 PM UTC-4, Tom wrote:
<--- snip --->

Post by TomCh
NB. I'm not testing against Win XP (only Win7-64 and Win10).

<--- snip --->

I'll give it some exercise on my XP system.

Willi

[A2CPM]

Hi!

I was able to use the new version a couple of times in spite of a warning about a missing "vcruntime140.dll".
Today I decided to get rid of the message. Progress, but then I got a message about a missing "api-ms-win-crt-runtime...". Got rid of that problem but now another problem. I didn't write down the text of the message but i'm hoping a reboot will fix the problem. I'm composing this message now because I need something to do while the reboot proceeds.

Willi

[fadden]

Post by A2CPM
I was able to use the new version a couple of times in spite of a warning about a missing "vcruntime140.dll".

Visual C++ runtime, one of the libraries in the "redistributable" collection.

https://support.microsoft.com/en-us/topic/the-latest-supported-visual-c-downloads-2647da03-1eea-4433-9aff-95f26a218cc0

You generally have the choice of static linking (making it part of the binary) or dynamic. CiderPress links it dynamically, so I actually include the DLL in the distribution. The previous version of CiderPress used the 2013 toolset for WinXP compatibility, which used msvcr120.dll instead. Maybe something similar needs to be updated in AppleWin?

api-ms-win-crt-runtime-l1-1-0.dll seems to live in \Windows\System32\downlevel\ on Win10.

[A2CPM]

Hi, y;all!

I timed a ProDOS assembly that generates a 475K listing file. AppleWin versions 1_21_1 and 1_25_0_4: 7 seconds. Versions 1_28_0_6 and 1_30_0: 13 minutes. Yes, emulated CPU speed was set at maximum for all runs. Not complaining, I thought the times were interesting.

Willi

[A2CPM]

Hi, y;all!

AHA!!! AppleWin 1.30.0, for some reason to be determined, is generating tons of bit maps.

Willi

[TomCh]

Hi Willi,

AHA!!! AppleWin 1.30.0, for some reason to be determined, is generating tons of bit maps.

Sounds very odd! Do you mean lots of screenshots? As if someone is pressing the PrintScreen key?

Tom

[A2CPM]

Post by TomCh

AHA!!! AppleWin 1.30.0, for some reason to be determined, is generating tons of bit maps.

Sounds very odd! Do you mean lots of screenshots? As if someone is pressing the PrintScreen key?

Yes. Version 1_28_0_6 also runs slowly so I assume the same thing happens w/ that version. Nothing resting on the keyboard for all four runs.

Willi

[TomCh]

Post by TomCh

AHA!!! AppleWin 1.30.0, for some reason to be determined, is generating tons of bit maps.

Sounds very odd! Do you mean lots of screenshots? As if someone is pressing the PrintScreen key?

Yes. Version 1_28_0_6 also runs slowly so I assume the same thing happens w/ that version. Nothing resting on the keyboard for all four runs.

Are you able to narrow this issue down to the *specific AppleWin version* where this problem started happening for you?

Tom

[A2CPM]

Post by TomCh
Are you able to narrow this issue down to the *specific AppleWin version* where this problem started happening for you?

I have many versions of AppleWin installed on my XP system. The last four are versions 1_21_1, 1_25_0_4: 7, 1_28_0_6 and 1_30_0. With the first two versions listed the the assembly runs in 7 seconds. With the latter two it takes minutes. The XP system is no longer connected to the I'net so transferring files out of it will require the use of sneakernet.

Willi

[A2CPM]

I now have a 13 MB '.ZIP' file containing two '.HDV' image files that will allow you to run the assembly yourself. Where do I send the '.ZIP' file?

Willi

[TomCh]

I now have a 13 MB '.ZIP' file containing two '.HDV' image files that will allow you to run the assembly yourself. Where do I send the '.ZIP' file?

If you have a GitHub account then you can attach the zip directly to this issue here:
https://github.com/AppleWin/AppleWin/issues/966

if you don't have an account (or don't want to create one) then perhaps you have a Dropbox or Google Drive account that you can upload to?

Thanks,
Tom

[A2CPM]

Post by TomCh
https://github.com/AppleWin/AppleWin/issues/966

File attached.

Willi

[TomCh]

I timed a ProDOS assembly that generates a 475K listing file. AppleWin versions 1_21_1 and 1_25_0_4: 7 seconds. Versions 1_28_0_6 and 1_30_0: 13 minutes. Yes, emulated CPU speed was set at maximum for all runs. Not complaining, I thought the times were interesting.

Hi Willi - if you can make a repro available - eg. create a GitHub issue (here: https://github.com/AppleWin/AppleWin/issues) and then attach a zip of your .dsk image/s, that'd be great, and I could take a look.

Tom

[A2CPM]

Hi!

The message is "...entry point ucrtbase.terminate could not be located in the dynamic link library api-ms-win...". But, the new AppleWin is working OK for the testing I'm doing.

Willi

[Nick Westgate]

The message is "...entry point ucrtbase.terminate could not be located in the dynamic link library api-ms-win...". But, the new AppleWin is working OK for the testing I'm doing.

Hi Willi.

The vcruntime140.dll issue is being tracked here:
https://github.com/AppleWin/AppleWin/issues/962

AppleWin statically links the VC runtime, but for foreign keyboard support it now uses FilterHook.dll which can't statically link the runtime. Modern VC tool chains use a "universal" runtime which comes with Windows. But to retain XP compatibility AppleWin is currently built using an older tool chain which in this case uses the VC 14 runtime (for VS 2015, 2017, 2019).

We will see if that DLL functionality can be merged into AppleWin itself, which should solve the problem.

As for the "ucrtbase" problem, that's a little unexpected. It might be the universal runtime which XP won't have. You could possibly extract the DLL from one of the installers at the following website.
https://support.microsoft.com/en-us/topic/update-for-universal-c-runtime-in-windows-c0514201-7fe6-95a3-b0a5-287930f3560c

Anyway, I'll add this problem to the GitHub issue above, and look into it later.

Cheers,
Nick.