Randman,

Thanks so much for the detailed notes and confirming that PEP2/PEP3 can be installed on Windows 11.

Several additional notes based on my experiences migrating XCFs from one system to another. The XCF configuration file contains only references/links to and not the actual file contents for both Fonts and Sound (.wav) files.

Therefore, you will need to copy and install those as well.

1) For those using configurations with custom Sounds, be sure to copy the .wav files from the Sounds folder.

2) For those using configurations with custom Fonts, be sure to copy and register the fonts on the new system. Otherwise, PEP may decide to automagically change an unavailable font to ProntoMaestro either when the XCF is first loaded or when you download to the new remote.

FOR SURE, DO NOT SAVE your file to the SAME filename after you move it and open in PEP2/PEP3 on the new system.

That way, you have a backup to compare to. Unzip the file and use a file compare tool against ConfigEdit.xml which is stored inside the .zip package.

Finally,

It's been years since I touched the HTTP library and I wondered where v1.4 came from as well as v2.01. Thanks for noting that.... :-)

Not sure of the source of the HTTP Library v2.01.

I have a custom v2.1 that I use locally and I for sure made changes to that file to support chunked responses.

I actually created 2 implementations of v2.1; one that has no comments and one without that the filename ends with WithComments.

This feature was needed so I could use long-running http requests over a custom implementation of CometD protocol so I could work with LMS/SqueezeCenter and get notifications pushed vs pulled.

If anyone wants this, send me an email to the addy on my RC profile from an email address that supports receiving .js attachments (GMail has issues) and I will happily send them along.