Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Discussion Meridian - Systems Apodising Firmware Update (Unofficial)

Successfully updated G61R and will continue assess. Initially there appears to be no functional issues.

I'm looking forward to comparing the new M upsampling filter with minimum phase up-sampling generated by a non M source.

Thanks again.

Avii

Hmm! Doesn't appear to work for me. I've tried running the exec file from various folders and the relevant firmware file is not renamed. These files are in a folder called 'G68' (path: \Program files (x86)\Meridian\Firmware\G_Series\G68). Not sure what I'm doing wrong

Looks like the automatic folder detection fails. Am I correct you are using the 64bit version of Windows? Please temporarily rename 'Program Files (x86)' to 'Program Files', and I am sure it will work.

I ran apoupdate from the download directory under windows XP. It correctly added the "a" i.e. G61R_101a.mfu version of file to the \Program Files\Meridian\Firmware\G_Series\G61R directory.

I then deleted the existing G61R_101.mfu and renamed the G61R_101a.mfu to G61R_101.mfu.

Do you already have the latest firmware files in the G68 directory?

Avi

Yep, correct 64 bit Win7. I copied the entire Meridian folder to the 'Program Files' directory but it still didn't modify the mfu file. All my programs and firmware are up to date as well.

I'll have a further play later. Thanks anyway

Cliff

That is strange. Then maybe the registry key apoupdate reads does exist, but does not contain a valid value. Are you handy with the registry editor?

I can use it, handy may be pushing it

Cliff

There is a cleaner way to fix that.

Just add a to end of program before you exit

Writeln(stdout, "Hit <cr> to exit")
Readline(stdin)

Evdberg,
Many, many thanks for doing this. I ran apoupdate once and it upgraded a slew of firmwares but then i realised i didn't have 568.2mm beta 25b9 in the Meridian firmware folder. I downloaded it into the 568_2 folder and ran the tool again but it didn't generate a 568_25b9a.mfu file.

I ran it from the command line too and it says "15 firmwares updated" I hope it isn't adding the apodising code every time I run it! But when I tried to point it at 568_25b9.mfu it simply says "unable to update 568_25b9.mfu".

I am using Win XP SP3 if that matters.
What am I missing?

Rgds,
Duncan

Yep, correct 64 bit Win7. I copied the entire Meridian folder to the 'Program Files' directory but it still didn't modify the mfu file. All my programs and firmware are up to date as well.

I'll have a further play later. Thanks anyway

Cliff

[/quote]

That's correct way to work around it. I ran into the same issue.

Make sure you run Erwin's program as Admin (right click Run as Admin) too because it is writing to Program Files it needs admin rights.

In fact that might be the only problem. If Erwin's program did find the right folder it may of failed because of admin rights not because it didn't find it.

You need to put the 568_25b9 folder that comes out of the zipfile in the 500_series folder, then it should work.

Because they are the only ones with more than one MFU file updated, and those firmwares need to be uploaded to different ports on the device. Since the MFP file handles connecting the RS232 cable to the correct port I thought it would be safer to use the MFP file (unless you really know what you are doing).