Muldersoft/LameXP
Muldersoft/LameXP
1
0
Fork 0
Code Releases 2 Activity

Updated Changelog and FAQ document with respect to the fact the we do NOT support Windows 2000 and Windows XP prior to Service Pack 2 any more. These are limitations of Microsoft Visual Studio 2010, so blame Microsoft ;-)

Browse Source
This commit is contained in:
LoRd_MuldeR 2011-04-08 15:36:41 +02:00
parent 9a8f8e1c75
commit 7d6a1a0e41
4 changed files with 39 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/Changelog.html
View File

@ -16,6 +16,13 @@ a:visited { color: #0000EE; }
<body>
<h3>LameXP - Version History</h3><br>
<a name="4.02"></a>Changes between v4.01 and v4.02:<br><ul>
<li>Upgraded build environment to Microsoft Visual Studio 2010
<li>Dropping support for Windows 2000 and for Windows XP RTM/SP1, Windows XP needs SP2 or SP3 now!
<li>Added a new translation: Korean
<li>Updated language files (big thank-you to all contributors !!!)
</ul><br>
<a name="4.01"></a>Changes between v4.00 and v4.01:<br><ul>
<li>Added an option to manually specify the number of parallel instances
<li>Added an option to select a user-defined TEMP directory

48
doc/FAQ.html
View File

@ -39,7 +39,9 @@ a:visited { color: #0000EE; }
<li><a href="#d83ab3c6">Why does LameXP use LAME v3.99 rather than v3.98?</a><br>
<li><a href="#4213adbc">Can LameXP be used to convert/extract tracks from an Audio CD?</a>
<li><a href="#e7c9ae2b">Why do I get the error 'Executable doesn't support Windows compatibility mode' on startup?</a>
<li><a href="#328b0a18">Why do I get the error 'Executable requires Windows 2000 or later' on startup?</a>
<li><a href="#328b0a18">Why do I get the error 'Executable requires Windows XP or later' on startup?</a>
<li><a href="#3ffe490e">Why do I get the error 'The procedure entry point De/EncodePointer could not be located' on startup?</a>
<li><a href="#01922741">Why do I get the error 'LameXP.exe is not a valid Win32 application' on startup?</a>
<li><a href="#491aaad9">Why do I get the error 'A device attached to the system is not functioning' on startup?</a>
<li><a href="#f35cfa24">How can I translate LameXP to my language or improve an existing translation?</a>
<li><a href="#8dba381f">Where can I download the latest version of LameXP?</a>
@ -66,20 +68,23 @@ any ACM Codecs or DirectShow/DMO filters! And it will NOT install anything of th
<br>
LameXP is currently being developed and tested on the following platforms:<br><ul>
<li>Microsoft Windows XP, Service Pack 3
<li>Microsoft Windows 7, 32-Bit and 64-Bit editions
<li>Microsoft Windows 2000, Service Pack 4</ul>
<li>Microsoft Windows 7, 32-Bit and 64-Bit editions</ul>
<br>
The following platforms should work as well, but aren't tested extensively:<br><ul>
<li>Microsoft Windows XP, Service Pack 2
<li>Microsoft Windows Vista, 32-Bit and 64-Bit editions
<li>Microsoft Windows Server 2008
<li>Microsoft Windows Server 2008 R2
<li>GNU/Linux using Wine (native Linux version planned)</ul>
<br>
The following platforms are NOT supported any longer:<br><ul>
<li>Microsoft Windows 95
<li>Microsoft Windows 98
<li>Microsoft Windows XP, Service Pack 1
<li>Microsoft Windows XP, RTM (i.e. without Service Pack)
<li>Microsoft Windows 2000
<li>Microsoft Windows NT 4.0
<li>Microsoft Windows Millennium Edition
<li>Microsoft Windows NT 4.0</ul>
<li>Microsoft Windows 98
<li>Microsoft Windows 95</ul>
<br><br>
@ -200,12 +205,12 @@ is a priority, then MP3 is a good choice. However the MP3 format does NOT suppor
means that you will have to use AAC or Vorbis for multi-channel files. Last but not least, if you prefer a<br>
truly "open" and patent-free audio format, then Vorbis will be the format of your choice!<br>
<br>
Another resource you might find intersting are Sebastian's Public Listening Tests:<br><ul>
Another resource you might find interesting are Sebastian's Public Listening Tests:<br><ul>
<li><a href="http://listening-tests.hydrogenaudio.org/sebastian/mp3-128-1/results.htm" target="_blank">MP3 listening test @ 128 kbps, includes MP3 encoders (like LAME) only</a>
<li><a href="http://listening-tests.hydrogenaudio.org/sebastian/mf-128-1/results.htm" target="_blank">Multiformat listening test @ 128 kbps, includes LAME MP3, Vorbis AoTuV and others</a>
<li><a href="http://listening-tests.hydrogenaudio.org/sebastian/mf-64-1/results.htm" target="_blank">Multiformat listening test @ 64 kbps, includes Vorbis AoTuV, Nero AAC and others</a>
</ul>
(However be aware that some of the results from these listening tests are not up-to-date anymore!)<br><br>
(However be aware that some of the results from these listening tests are not up-to-date anymore)<br><br>
<br><br>
@ -448,13 +453,19 @@ switching to the 'Compatibility' tab and un-checking the 'Run this program in co
<br><br>
<a name="328b0a18"></a><b>Why do I get the error 'Executable requires Windows 2000 or later' on startup?</b><br>
<a name="328b0a18"></a><b>Why do I get the error 'Executable requires Windows XP or later' on startup?</b><br>
<a name="3ffe490e"></a><b>Why do I get the error 'The procedure entry point De/EncodePointer could not be located' on startup?</b><br>
<a name="01922741"></a><b>Why do I get the error 'LameXP.exe is not a valid Win32 application' on startup?</b><br>
<br>
You are trying to run LameXP on a platform that is NOT supported, such as Windows 95, Windows 98, Windows<br>
Millennium Edition or Windows NT 4.0. There is nothing you can do about that, except for updating to a less<br>
antiquated OS. Running an outdated/unsupported OS is a severe security risk anyway!<br>
Millennium Edition, Windows NT 4.0 or Windows 2000. There is nothing you can do about that, except for<br>
updating to a less antiquated OS. Running an outdated and unsupported OS is a severe security risk anyway!<br>
<br>
Note: This error can also occur, if your system has been configured to run LameXP in <a href="#e7c9ae2b">compatibility mode</a>.<br><br>
LameXP won't run on the 'RTM' release of Windows XP (no service packs) either. Service Pack 2 or newer is<br>
required! If needed, you can download Service Pack 3 for Windows XP as <a href="http://www.microsoft.com/downloads/en/details.aspx?FamilyID=5b33b5a8-5e76-401f-be08-1e1555d4f3d4" target="_blank">network installation</a> or as <a href="http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2FCDE6CE-B5FB-4488-8C50-FE22559D164E" target="_blank">ISO image</a>.<br>
Finally this error can also occur, if your system has been configured to run LameXP in <a href="#e7c9ae2b">compatibility mode</a>.<br>
<br>
Remark: Executable files compiled with Microsoft Visual Studio 2010 won't run on Windows 2000 (<a href="http://msdn.microsoft.com/en-us/library/ws0swas0(v=VS.100).aspx" target="_blank">details</a>).<br><br>
<br><br>
@ -464,10 +475,10 @@ This error message from the Windows operating system is somewhat misleading. It
a second error message and it means that Windows was unable to load/execute the program file. There are<br>
various reasons why this error might occur, but usually it indicates that you are trying to run LameXP or the<br>
LameXP setup/update program on a platform that is NOT supported, such as Windows 95, Windows 98, Windows<br>
Millennium Edition or Windows NT 4.0. There is nothing you can do about that, except for updating to a less<br>
antiquated OS. Running an outdated/unsupported OS is a severe security risk anyway!<br>
Millennium Edition, Windows NT 4.0 or Windows 2000. There is nothing you can do about that, except for<br>
updating to a less antiquated OS. Running an outdated and unsupported OS is a severe security risk anyway!<br>
<br>
Remark: Executable files compiled with Microsoft Visual Studio 2005 (or later) won't load on Windows 9x.<br><br>
Remark: Executable files compiled with Microsoft Visual Studio 2010 won't run on Windows 2000 (<a href="http://msdn.microsoft.com/en-us/library/ws0swas0(v=VS.100).aspx" target="_blank">see also</a>).<br><br>
<br><br>
@ -508,14 +519,15 @@ LameXP is developed using the <a href="http://en.wikipedia.org/wiki/Git_(softwar
<a name="a0c1e92b"></a><b>What are the prerequisites to build LameXP from the sources?</b><br>
<br>
LameXP is currently being developed using the following build environment:<br><ul>
<li>Visual Studio 2008, Service Pack 1
<li>Qt libraries v4.7.2 for Windows (VS 2008)
<li>Microsoft Windows SDK v7.1</ul>
<li>Visual Studio 2010 with Service Pack 1
<li>Qt libraries v4.7.2 for Windows (VS 2008), compiled with Visual Studio 2010
<li>Windows SDK for Windows 7 and .NET Framework 4 (v7.1)</ul>
<br>
Also note the following hints:<br><ul>
<li>You must launch Visual Studio using "qtvars.bat vsstart" in order to enable the Qt tools
<li>The Microsoft Windows SDK v6.0A should work as well, with a few limitations
<li>In order to make a fully "static" build of LameXP, you need to compile Qt as static libraries
<li>Visual Studio 2008 solution/project files are still provided for people targeting Windows 2000
<li>Support for the GNU Toolchain (GCC/MinGW + Make) is planned for a future version</ul>
<br><br>

2
doc/Translate.html
View File

@ -23,7 +23,7 @@ a:visited { color: #0000EE; }
<p>You can download <i>Qt Linguist</i> as a part of the Qt Framework, which is available as a free download from the <a href="http://qt.nokia.com/downloads/downloads" target="_blank">Qt download site</a>. You should pick the "LGPL" version and the "Qt: Framework Only" download. If you are using Microsoft Windows, then the "VS 2008" version should be preferred. Moreover people who don't like to download the complete framework (230 MB) can find Qt Linguist for Windows as a stand-alone download at <a href="http://code.google.com/p/mulder/downloads/detail?name=qt-linguist-471-win32.rar" target="_blank">this</a> location (4 MB).</p>
<br>
<h3>Editing the language file:</h3>
<p>LameXP v4.xx translations are created as TS (translation) files, which can be edited using the <i>Qt Linguist</i> application. For new translations an empty TS file ("Blank.ts") is provided in the LameXP Git repository. When you open the empty TS file for the first time, Qt Linguist will ask for some basic settings. Here you must keep the "Source language" options at "English" and "Any Country". Change the "Target language" options to whatever language (region) you are going to translate to. Once you have edited all (or some) text strings, you can save your work to a TS file again. It is recommended to save your work to "LameXP_XX.ts", where <i>XX</i> should be replaced with the suitable upper-case <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm" target="_blank">ISO_3166-1</a> or <a href="http://www.loc.gov/standards/iso639-2/php/code_list.php" target="_blank">ISO 639-1</a> country/language code (for example the German translation is saved as "LameXP_DE.ts"). You can re-open your TS file at any time in order to continue with your work. In case you want to improve an existing LameXP translation, simply download the corresponding TS file from the LameXP Git repository and edit it using the Qt Linguist tool.</p>
<p>LameXP v4.xx translations are created as TS (translation) files, which can be edited using the <i>Qt Linguist</i> application. For new translations an empty TS file ("Blank.ts") is provided in the LameXP Git repository. When you open the empty TS file for the first time, Qt Linguist will ask for some basic settings. Here you must keep the "Source language" options at "English" and "Any Country". Change the "Target language" options to whatever language (region) you are going to translate to. Once you have edited all (or some) text strings, you can save your work to a TS file again. It is recommended to save your work to "LameXP_XX.ts", where <i>XX</i> should be replaced with the suitable upper-case <a href="http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm" target="_blank">ISO 3166-1</a> or <a href="http://www.loc.gov/standards/iso639-2/php/code_list.php" target="_blank">ISO 639-1</a> country/language code (for example the German translation is saved as "LameXP_DE.ts"). You can re-open your TS file at any time in order to continue with your work. In case you want to improve an existing LameXP translation, simply download the corresponding TS file from the LameXP Git repository and edit it using the Qt Linguist tool.</p>
<p>The latest translation (TS) files can always be found in the LameXP Git repository at:<br><a href="https://github.com/lordmulder/LameXP/tree/master/etc/Translation" target="_blank">https://github.com/lordmulder/LameXP/tree/master/etc/Translation</a><br><br style="line-height:4px">(After you have chosen a file from the directory tree, you can download the file by right-clicking on "raw" an choosing "Save Link Target As...")</p>
<p style="border-width:1px;border-style:solid;border-color:darkred"><font color="darkred"><b>Important:</b> Before you start translating, always make sure your download the <i>latest</i> "Blank.ts" file from the LameXP Git repository. If you want to edit an existing translation, including translations you have created yourself, make sure your download the <i>latest</i> TS file from the LameXP Git repository. Never ever do any translations based on an old working copy (TS file) from your local system! The translation files in the repository will be updated continuously, as the development proceeds.</font></p>
<br>

6
src/Global.cpp
View File

@ -666,10 +666,6 @@ bool lamexp_init_qt(int argc, char* argv[])
//Check the Windows version
switch(QSysInfo::windowsVersion() & QSysInfo::WV_NT_based)
{
case QSysInfo::WV_2000:
qDebug("Running on Windows 2000 (not offically supported!).\n");
lamexp_check_compatibility_mode("GetNativeSystemInfo", executableName);
break;
case QSysInfo::WV_XP:
qDebug("Running on Windows XP.\n");
lamexp_check_compatibility_mode("GetLargePageMinimum", executableName);
@ -687,7 +683,7 @@ bool lamexp_init_qt(int argc, char* argv[])
lamexp_check_compatibility_mode(NULL, executableName);
break;
default:
qFatal("%s", QApplication::tr("Executable '%1' requires Windows 2000 or later.").arg(QString::fromLatin1(executableName)).toLatin1().constData());
qFatal("%s", QApplication::tr("Executable '%1' requires Windows XP or later.").arg(QString::fromLatin1(executableName)).toLatin1().constData());
break;
}