LameXP v4.18 Final · Build #2240 (2019-12-18)

[LoRd_MuldeR]

Originally Posted by MrVideo

Based on the new information about lxp_curl.exe, I first started lamexp and then looked for the program. I then found the "new" version and it indeed fails. The walker indicates that normaliz.dll is missing, which indeed it is. Was this DLL ever shipped with WinXP, or ever added with a patch? I'm at SP3. I found a site to get it, but I need to know the info about the one that you are running (they have several versions). The info line from the walker program will do.

I don't know. And because Windows XP went "end of life" so long ago, it is hard to find any information. On my Windows XP (SP-3) system it just worked

The Microsoft site about the IdnToAscii() function, which is the only function cURL imports from "normaliz.dll", says:

Windows XP, Windows Server 2003:
The required header file and DLL are part of the Microsoft Internationalized Domain Name (IDN) Mitigation APIs, which are no longer available for download.

Apparently there used to be a redistributable installer, specifically for Windows XP. So you can try with this archived copy that I was able to dig up:
idndl.x86.exe

(Vista and later apparently provide "normaliz.dll" out-of-the-box)

Originally Posted by MrVideo

In this case, that is indeed true. That is because there was an album.flac.cue and album.wave.cue file. Why there is a wave cue file is beyond me, size there are no wave files.

Suggestion... if this situation arises, how about adding a pop-up asking the user to enter a new directory name? That is because I end up having to go back and manually rename the directories. Easier to do it up front.

I don't see why that would be needed. After all, we are talking about the suggested (default) name of the output directory.

If you don't like the default, you can always choose a different output directory of your liking – in the CUE Sheet import dialog – before you start the import/splitting process.

Hence, there should be no need to rename anything afterwards...

While that is true, the user would have discovered a DNS issue via other means, i.e., just by trying to go to any website via their browser. Odds are that a user would have found an issue with their LAN, or internet connection, long before running lamexp.

Well, this is not about what the user might be able to figure out. It is about how the application reliably detectes whether we have a "working" Internet connection or not.

Just go to your site to look for the update and if it doesn't work, report back to the user. At that point the user can troubleshoot their LAN/internet.

That's the point. If we weren't able to fetch the update info from our update mirror, we don't know whether it is because our update mirror is down, or because of a more general problem with the user's Internet connection.

Sure, we could simply throw a typical meaningless "Uh oh: Something went wrong!" error message and let the user figure out the specifics. But I think showing a somewhat more helpful error message is nice

Furthermore, since this is already implemented, I don't see a reason to drop a better, already working solution in favor of an inferior one.

Most important: Dropping the Internet connection test would not solve your cURL issues at all, because a working cURL would still be required for the actual download of the update information. You wouldn't gain anything.

[danlock]

> I use the cygwin terminal and it knows nothing about %TMP%.
> I just did a search of the program on te C: drive to find it.

I think the applicable Windows environment variable is %temp% (which redirects to Windows' temporary directory)

... good luck

[MrVideo]

Originally Posted by danlock

> I use the cygwin terminal and it knows nothing about %TMP%.
> I just did a search of the program on te C: drive to find it.

I think the applicable Windows environment variable is %temp% (which redirects to Windows' temporary directory)

Cygwin doesn't know it either.

[MrVideo]

Originally Posted by LoRd_MuldeR

I don't know. And because Windows XP went "end of life" so long ago, it is hard to find any information. On my Windows XP (SP-3) system it just worked

Somehow you managed to get it on your system.

The Microsoft site about the IdnToAscii() function, which is the only function cURL imports from "normaliz.dll", says:

Apparently there used to be a redistributable installer, specifically for Windows XP. So you can try with this archived copy that I was able to dig up:
idndl.x86.exe

That fixed it. Sometime after the June 2020 version of cURL you were using, the program got changed and started using normaliz.dll. You never stumbled on the issue because you already had that DLL on your system. Leave it to me to find that issue.

Most important: Dropping the Internet connection test would not solve your cURL issues at all, because a working cURL would still be required for the actual download of the update information. You wouldn't gain anything.

Well, that certainly makes the point moot.

Now we know what to do if this were to happen to anyone else.

Thanks for helping me find the issue.

BTW: I removed the other cURL directory from last year, so I won't get fooled again.

[MrVideo]

Originally Posted by LoRd_MuldeR

I don't see why that would be needed. After all, we are talking about the suggested (default) name of the output directory.

If you don't like the default, you can always choose a different output directory of your liking – in the CUE Sheet import dialog – before you start the import/splitting process.

Hence, there should be no need to rename anything afterwards...

Unfortunately, I do want the results placed in the source directory. Oh well.

[LoRd_MuldeR]

Originally Posted by MrVideo

Somehow you managed to get it on your system.

It is included with IE7 or later, and probably many other applications. Actually, I was able to extract the required "idndl.x86.exe" redistributable from an old IE7 for Windows XP setup package.

Since, after a fresh install, I always update my system to the latest version with WSUS Offline Update, including the latest supported version of IE, that's probably how I got it.

Originally Posted by MrVideo

That fixed it. Sometime after the June 2020 version of cURL you were using, the program got changed and started using normaliz.dll. You never stumbled on the issue because you already had that DLL on your system. Leave it to me to find that issue.

Okay. So I will include the "idndl.x86.exe" redistributable in the LameXP installer for now. Just to be sure.

Originally Posted by MrVideo

Unfortunately, I do want the results placed in the source directory. Oh well.

No idea

After you have opened the CUE file to be imported but before you hit "Import Cue Sheet" simply click the "Browse" button (in the "Output directory" groupbox) and then choose whatever output directory you like. That's it.

[MrVideo]

Originally Posted by LoRd_MuldeR

It is included with IE7 or later, and probably many other applications. Actually, I was able to extract the required "idndl.x86.exe" redistributable from an old IE7 for Windows XP setup package.

Since, after a fresh install, I always update my system to the latest version with WSUS Offline Update, including the latest supported version of IE, that's probably how I got it.

I never updated IE7, as I do not use IE for any web browsing. All of my browsing is done on my Linux server using Opera and Vivaldi.

Okay. So I will include the "idndl.x86.exe" redistributable in the LameXP installer for now. Just to be sure.

Sounds like a great idea.

[LoRd_MuldeR]

Originally Posted by MrVideo

I never updated IE7, as I do not use IE for any web browsing. All of my browsing is done on my Linux server using Opera and Vivaldi.

Keep in mind that many applications use embedded IE frames

[LoRd_MuldeR]

LameXP v4.19 RC-3
https://sourceforge.net/projects/lam...4.exe/download

Changes between v4.18 and v4.19 [unreleased]
* Updated LAME encoder to v3.100.1-SVN (2020-08-25), compiled with ICL 19.1 and MSVC 15.9
* Updated Vorbis encoder to OggEnc v2.88 (2020-07-07), using libvorbis v1.3.7 with aoTuV beta-6.03
* Updated Monkey's Audio binary to v6.12 (2021-02-15), compiled with ICL 19.2 and MSVC 15.9
* Updated mpg123 decoder to v1.26.4 (2020-12-24), compiled with GCC 10.2.0
* Updated MediaInfo to v20.09 (2020-10-09), compiled with ICL 2021.1 and MSVC 15.9
* Updated cURL to v7.75.0 (2021-02-03), with libcurl v7.75.0 and OpenSSL v1.1.1i
* Added Bulgarian (български) translation, thanks to Симеон Илиянов Цветков <sicvetkov@uni-sofia.bg>
* Added command-line switch --no-splash, which can be used to hide the "splash" screen at startup
* Added a workaround for missing normaliz.dll to the installer (Windows XP only)

[MrVideo]

Originally Posted by LoRd_MuldeR

Keep in mind that many applications use embedded IE frames

True. The only one that I know of that works just fine is VideoReDo. If there are others, there has never been a complaint (error). I guess I've been lucky.

[manolito]

Getting THIS again:
https://forum.doom9.org/showthread.p...86#post1892386

All I can do is repeat my request from this older post. I totally understand if you do not want your users to use alpha, beta or RC versions forever, but for stable versions this nagging is totally annoying and unnecessary.

Please...