|
| AudioManage: FAQs |
| Table of Contents |
 Which version of Windows is needed for AudioManage?
|
|
What about international language support?
|
|
AudioManage and Windows XP Service Pack 2
|
| |
| Which version of Windows is needed for AudioManage? |
NOTE: DUE TO A TECHNICAL UPDATE, THE CURRENT VERSION OF AUDIOMANAGE RUNS ONLY ON Windows 2000/XP/2003. Please ignore anything in this faq that says anything to the contrary.
AudioManage has been designed for Windows XP and Windows 2003. However, it runs beautifully on all 32-bit Windows (Win95 onwards!), with "graceful degradation". This means that some features may disappear on older versions of Windows, without effecting the rest of the program.
In general, here's a basic feature matrix as far as degradation is concerned:
Windows XP/2003: All features supported
Windows ME/2000: All features, except Direct Copy to CD
Windows 98: Like Windows ME, but does not support 'Details' view in Windows Explorer.
Windows 95: Haven't really tried, but we expect it to run like on Windows 98.
Windows 3.1: Haven't tried, won't work. 
NOTE: Also see post on Unicode support below.
AudioManage Admin
|
| Back to Top |
| What about international language support? |
AudioManage supports ALL languages that your Windows supports. It fully supports Unicode, not only in it's interface (though currently only an English interface is available), but also in it's capabilities. This means that you can use Unicode names for your all track properties such as Album, Artist, Tracks etc.
The built-in tagger also has full support for Unicode. In addition to Unicode, the tagger ALSO supports other encodings used by different file formats. For example, while writing MP3 ID3v1 tags, AudioManage uses ANSI character set, using the current locale (region setting in Windows). For ID3v2 tags, both Unicode and ANSI are supported. While writing to WMA files, AudioManage uses Unicode, and for OGG, UTF8 encoding is used. All this is done transparently, and AudioManage automatically chooses the best encoding depending on file format etc. : you just have to change the properties, rename albums, drag & drop, etc.
Note that for Unicode support to work, your Windows must be configured to use the extra languages you plan to use. You must also have already installed the extra language packs needed by Windows.
Read more about configuring Windows for using Unicode.
|
| Back to Top |
| AudioManage and Windows XP Service Pack 2 |
[Update: Most users have reported AudioManage version 1.20i onwards to not have problems with SP2]
AudioManage works best on Windows XP or better. However, some people have reported some problems with AudioManage after upgrading their Windows to Service Pack 2 (SP2). These range from getting irrelevant 'trial over' messages, to not seeing any virtual folders at all. Two common problems and their fixes are:
1) Some people have reported that if SP2 is installed after AudioManage, then AudioManage completely stops working, not even showing the top level folders (in other words, when the Audio Library is opened, it's completely blank). A quick workaround for this is to reinstall AudioManage: it starts working again, and all your earlier data is retained (the library itself is not lost).
2) If the above step doesn't get AudioManage working, or if you had SP2 prior to installing AudioManage, the problem most likely lies with the DCOM Server Process Launcher. To resolve this, follow these steps:
a) Click the 'Start' button, and select 'Run' from the menu. In the 'Run' dialog that pops up, type:
sc config dcomlaunch start= auto
(Note that there is a space before 'auto', and no space betwee the 'start' and '=')
and click 'Ok'. Then type:
sc start dcomlaunch
and click 'Ok'.
Try AudioManage after this, it should work happily.
b) If the above doesn't work, or to do this from the service manager console application, click on 'Start'->'Run', and type
services.msc
and click 'Ok'.
From the services list that appears, select the one labelled 'DCOM Server Process Launcher', and if the service is stopped, start it by pressing the 'Play' button in the toolbar on top. Also, you should set the service to run 'Automatically', by double-clicking on it and selecting the appropriate option.
If the service was stopped and you just started it, note that you may get an error that the service was not started (or was not responding etc.). Ignore that warning, and try AudioManage - it should be working now.
If the service was already on 'Automatic', set it to 'Manual', reboot the system, come back to this list, select this service ('DCOM Server Process Launcher'), press the play button - or click on 'Start service'. Also, from it's properties, set the service to start 'Automatically'. Try AudioManage - it should be working now.
|
| Back to Top |
|
The comments are owned by the poster. We aren't responsible for their content.
|
|
Home
Features
