| Author |
 Topic  |
|
|
allen
Starting Member
USA
40 Posts |
 Posted - 16 Apr 2008 : 13:57:02
|
Version 6.1.6.0 was working properly. I’ve upgraded to version 6.2.1.0 and the problems that I have experienced since version 6.1.8.0 still seem to exist.
Unlike version 6.8.1.0 and 6.9.1.0 XMM no longer starts correctly from the ‘Install’ screens. It now gives an error screen indicating that one of two paths is missing. When I manually search for the 1st of these paths, the installation continues but again fails when it cannot find the language files. XMM is looking for these files at ‘C:\Net_Files\Allen\My Documents\ eXtreme Movie Manager\Languages’ which does not exist – the correct location is on my network drive at ‘\\Net_Files\Allen\My Documents\eXtreme Movie Manager\Languages’.
If I delete the config.ini in the EXE folder (at ‘C:\Additional Programs\eXtreme Movie Manager’), XMM opens correctly – including finding the language files in their network drive location. When XMM opens with the config.ini missing a new config.ini file is written to the EXE folder; however with this ‘new’ config.ini file present and XMM is started it displays the “path” error once again. I’ve found that if I close the “path” error screen – not bothering with a manual search – XMM continues to load, but as with the manual search, does not find the language files. If I copy the language files from their correct location to the location XMM thinks they are, XMM will load correctly – XMM wants to find them at ‘C:\Net_Files\Allen\My Documents\eXtreme Movie Manager\Languages’.
Now with the config.ini file deleted and the language files copied to the path XMM wants to find them, XMM loads without error, but after opening the shareware screen comes up indicating that XMM has not been registered. The database size limitations do not seem to be in effect – all 313 of my movies load – so the screen is just an annoyance, but still shouldn’t be there.
For now I am continuing to use 6.2.1.0 without deleting the “config.ini” file and with the language files in the C:\ location XMM wants. When XMM starts I just close the “path” error screen and XMM continues to load correctly without further problems. I haven’t yet tested any of the other features, but right now it seems to be just the start-up errors that a problematic.
I admit my configuration may be different, but that really shouldn’t make any difference. I should be able to keep files and databases where I want them – and version 6.1.6.0 did not/does not have a problem with my configuration. (BTW: I keep non-essential program files in a separate folder – C:\Additional Applications. My Documents are on one of my networked drives - \\Net_Files\Allen\My Documents. The actual movies are on another network drive - \\Media\Internet Movies. Therefore, the XMM EXE folder is C:\Additional Programs\eXtreme Movie Manager, the other XMM folders – languages, configuration, etc – are \\Netfiles\Allen\My Documents\ eXtreme Movie Manager\ and the actual movie files are \\Media\Internet Movies\.) |
|
|
allen
Starting Member
USA
40 Posts |
Posted - 16 Apr 2008 : 14:00:39
|
| References to versions 6.8.1.0 and 6.9.1.0 are really 6.1.8.0 and 6.1.9.0. Sorry for the confusion |
 |
|
|
allen
Starting Member
USA
40 Posts |
Posted - 17 Apr 2008 : 21:48:27
|
| I'v fixed my problems with 6.2.1.0 my making a directory on my primary drive that matches where XMM wants to find the "operational" files and now every thing works correctly. As I'd like to be able to move my "operational" files back onto my network drives, I'm hoping a 'fix' will be comming soon, but in the mean time, I'm up and working once again. (I'll be away from this computer and my network for about a month, so won't have the opportunity to test and comment on 6.2.2.0 until I return in mid May). |
|
|
| |
Topic |
|
|
|
Errors With Version 6.2.1.0