Vista support MxCC

Windows Vista (business version)

Mardi 05 Août 2008 12:03:18 am

Id be interested in this answer too, I currently have MXcc running on a Vista business platform.

The application seems to run OK until I try to export to an .avi file. The export process cause explorer to crash, then the app restarts.

Any suggestions to a fix ??

Lee

Vista MxCC

Jeudi 11 Décembre 2008 12:34:23 pm

I got this as well.

Did you upgrade from a earlier version??

The way I got round it was to rename the mobotix directory in Program Files and re-install the software.

I then copied Mxcc.ini from the Original system to the new one.

Started up MxCentral and all worked ok

RE: Is Vista supported by MxCC?

Mercredi 18 Août 2010 12:26:09 pm

hello folks!

yes, Vista is supported by the MxCC and it should run OK on Vista. Make sure, though, you at least have all of the current service packs installed (SP2?) and current updates, because there were serious problems with video in Vista before SP1 was released.

And the MxCC is, however, still just a 32 bit program. It will, though, run quite well on both the 64 bit and 32 bit versions of Vista. So you shouldn't have to worry about that.

And you should either be running MxCC v2.4 (just released end of July) or v2.3 - because the problem with it crashing during export should be fixed in those versions (or at least should not occur)

IF you are still getting crashes during the export process, then contact MOBOTIX Support (see http://www.mobotix.com/other/Support/Support) about this one and provide them with enough information to allow them to recreate the problem, and that includes:

1. The settings you used for the export, the steps you used exactly to perform the export meaning:

a. What were you exporting - event recording, continuous recording, snapshot recording?
b. From what time/date to what time/date were you trying to export?
c. Where did you start the export - from the player or inside the Video Search?
d. What type of camera and what software version was it using?
e. The settings in the Export dialog that you were using at the time of the crash.

(and remember screen shots help a lot!)

2. Also, a copy of the data you were trying to export will certainly help - if you can copy it or download it or export it - and I really doubt that the MxCC will crash if you export the file structure.

3. What Operating System (eg "Vista Business 64 bit with SP1"
4. MxCC Version (ie "MxCC v2.4"
5. Sending them your MxCC.ini (or whatever you have named it) will help.
6. And if you know a bit more than the average PC user you can also send the people at Support a copy of your "Control Center.log" file that was created at the time of the crash (Copy it to another location BEFORE you click "OK" on the error/crash message !!!)

... but you have to create one first by doing the following:

a. open a CMD window (click "Start", "Run", enter "cmd", press enter).
b. enter "cd %appdata%" and press enter
c. enter "cd Mobotix" and press enter
d. enter "echo. > "Control Center.log"" and press enter (see that set of quotation marks before and after "Control Center.log"? - you must type those too or the file you create will only have the name "Control&quot)
e. leave this CMD window open and start the MxControlCenter. When the program crashes, switch back to the CMD window and type in "copy "Control Center.log" "%userprofile%\Desktop"" and press enter (yeah, the quotation marks around "Control Center.log" and "%userprofile%\Desktop" must be entered.) and then a copy of that "Control Center.log" will be on your desktop (and easy to find).

and then you'll have a Control Center.log and you can go about recreating the crash.

And remember, if you can't recreate the crash and/or error, then it's unlikely MOBOTIX will be able to, so like I say, give them enough information to allow them to recreate the problem - I know they are very concerned about program crashes and have put a lot of effort into reducing the occurrence of them during the last two releases (v2.4 & v2.3) with v2.4 being the most intensively one tested on WinXP, Windows 7, Vista, Windows Server 2003 and Windows Server 2008 (incl the R2 versions).

alright?
Sam