View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005547 | MMW v4 | Install/Config | public | 2009-04-26 15:14 | 2009-05-15 18:57 |
| Reporter | Bex | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.1 | ||||
| Fixed in Version | 3.1 | ||||
| Summary | 0005547: MediaMonkey.ini problems. (Regression) | ||||
| Description | All of a sudden one of my MM installations can't open up with correct MediaMonkey.ini file. It has a custom location in the MM directory where also the DB is located. The ini file is correctly updated with the full DB-part. When opening this MM, it strangely enough finds the DB and copies it to the Application\Mediamonkey folder where it also creates a brand new ini file. MM then opens up and acts as if it is a first install/use. If I move the ini to the Application\Mediamonkey folder before opening MM same thing happens. If a try to force MM to use the correct ini file by using the /INIFILE=fullpath command line option, a strange error occurs "There was a problem downloading the following files" see attached image. Tested with 1240. Log, two problematic ini files and two images attached. | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | 1241 | ||||
|
|
Ok, think i know why this is happening. I've been developing scripts and needed to change some trivial ini values during testing, some of these changes makes the ini "corrupt" and triggers the described behavior. |
|
|
This is a regression. It is not reproducible in 1237. |
|
|
Bex. I've tried INI you sent to open using INIFILE parameter and didn't work. Then i've tried to open and save it in PSPad (text editor) with default setting (UTF-8) and now it's working fine so INI you sent us is not fully UTF8 compatible and MM can't read it (size before saving in PSPad was 104 136 bytes and after save 104 133 bytes). |
|
|
I used notepad. Surely ini changes made in notepad should be accepted by MM, otherwise we'll have a lot of problems. What am I missing? |
|
|
It will be accepted until you write any non-ASCII code (or when any of that character is already in INI file and you'll edit that using notepad) because of Notepad is using Windows codepage for saving files. That's not a bug in MM (MM must be able to read/save INI with unicode so we're using UTF8 standard), but it's notepad 'problem' because it doesn't supporting UTF8. |
|
|
Ok then, but we need to update all help files etc with this info, otherwise users will fail in updating their ini files, |
|
|
I've just checked and Windows XP SP3 already have UTF8 support in Notepad, but it's using special 'sign' at the beginning of the file (EF BB BF .. known as BOM we're not using) and this could be our problem. For details see http://en.wikipedia.org/wiki/UTF8#Byte-order_mark |
|
|
Interesting, I wonder if this can explain why some users have this problem from time to time? Is it possible to make MM ignore this special sign if it exists? |
|
|
Just working on it. |
|
|
Fixed in 1241 |
|
|
Reopenned Tested in 1242 There is big Difference how /INIFILE= is handled in these two cases: 1. /INIFILE="f:\?ekanje žreba\MediaMonkey.ini" 2. /INIFILE=f:\?ekanje žreba\MediaMonkey.ini Second Instance Throw an error. Solution for that would be that PARAMSTR is checks if First Char Of Param STR is "/" and if not Append all until "/" is found as First Char Of ParamStr or ParamCount is reached. Additionally adding Adding MM.DB to same Folder MediaMonkey.ini Resulted in two Exception Bug Reports (sent with "BUG 5547" in description) MediaMonkey.ini is save as ASCII/ANSI But text font was set to Arial/Central European Library used to test and MediaMonkey.ini uploaded to FTP |
|
|
Re uploaded files to FTP as An archive due the fact that mantis do not handle foreign chars good. |
|
|
This is how Windows working with parameters. Parameter with space _must_ me in commas. It's not a MM bug. Second issue ... MM's trying to find database in location specified in INI file and then in our default folder. Probably this could be added as new mantis entry with low priority. |
|
|
I know that is how windows do, it is not too hard to make simple function that will go thru all ParamStr and Create small Array of Strings as it will save us lots user reports. But I agree with that we best way it would be to update TODOC and clear things like this even it is commonly known. RE BOM: NotePad++ have great Text Format Converter. Am I right that MediaMonkey.ini in My Archive is plain ANSI without BOM? |
