Hello Europe: MMM 0.7 is Here

There won't be a version 0.6.8 as suggested earlier. For whatever reasons several people seem to want another version numbering scheme to be used, one that exposes the build number. So now we're at MMM 0.7!

New Version 0.7

I wasn't quite ready to put out a new MMM version but then over the past three days I got two bug reports I couldn't ignore.

Both of these involved a problem with "comma as decimal point" in some international locales. A very strange coincidence, but right after fixing this the first time a second report of the same problem came in. This was enough to get me to pull a new release from the MMM codebase now that I have changed it to use the current decimal point character.

Along with the first report a second issue was raised. Some people actually do compile into folders other than the Project folder it seems. So MMM will follow the Path32 key in the .VBP file now instead of simply requiring that the compiled EXE be located in the Project folder. And yes, this appears to be the same issue raised in a comment to an earlier blog post here... that I sort of blew off because I thought MMM was already handling the matter. Doh!

The bigger changes I have coming along for MMM are not ready for beta release yet. So only a few additional changes are present in this MMM 0.7 version. These should not matter much to most users, but details can be found in the readme.txt file in this package.

ZIP Archive, Not EXE

This version has been posted as a simple ZIP archive instead of a self-extracting EXE. The tools for extracting from a ZIP are extremely common and even Windows has been capable of doing it alone for some time now. Some people are running MMM on Win9x systems (??) and the self-extractor I was using requires NT crypto libraries, so it could be a problem for these guys.

On the plus side the download is only about half the size as before: MMM 0.7

As always, let me know about any problems. Be sure to keep MMM version 0.6.7 or earlier around in case of problems with the new one.

Posted at Saturday, August 15, 2009 12:56 PM
In General Category | Permalink

Comments
#16 ~ 36 (Total 36)

This is probably the same bug or limitation others have reported in the past. If somebody could send me a whole Project that reproduces the problem I might make some headway with it.

I'd like to think anyone running into this could create a smaller stripped-down example instead of having to send me something they'd rather not share. I suspect it may be related to certain 3rd party controls though, such as some of those from vbAccelerator.

Posted by BVOCS on Sunday, November 15, 2009 06:32 AM

The MMM 0.7 app scans the large VBP file just fine if I exclude all OCX files (editing the INI file). I'm still trying to understand why its throwing an error when OCX files are included. Any insights? Most of these OCXs are custom components. Not sure if I can share all the details, but this VBP (exe) references a lot of DLLs and OCXs that are themselves VBPs. If I explicitly exclude OCX as dependencies then the programs scans VBP just fine and creates the manifest.

Posted by Saurabh on Monday, November 16, 2009 03:53 PM

This has been a very helpful tool for us, many thanks! We are having one small problem ... the following line in the vbp file generates an error something like "... a serious problem was encountered while processing your project's dependencies ..." (it is not critical since the type library is used as a reference only). We simply make a copy and delete the line and all is well.

Reference=*\G{11269241-F241-11CF-BD9A-00AA00575603}#1.0#0#Code\SHELLLNK.TLB#VB 5 - IShellLinkA Interface(ANSI)

Posted by Mark Ustik on Tuesday, November 17, 2009 04:58 PM

here is a similar command line tool:
http://www.codeproject.com/KB/COM/regsvr42.aspx

and a similar gui tool (on the tools tab):
http://tzitech.webs.com/

works from W98 to W7

Posted by nano on Monday, December 7, 2009 09:26 AM

Cannot download the GUI version of tool mentioned. The link on the associated website is bad

Posted by Saurabh on Wednesday, January 6, 2010 10:38 AM

I'm sorry, I know nothing about that tool and it isn't associated with MMM. Perhaps you can contact nano above at the link provided in his name?

Posted by BVOCS on Friday, January 8, 2010 05:14 PM

Great tool!

How do you open an .mmmp file?
They get produced, but I can't figure out how to re-open!

/Johan

Posted by Johan St�ck on Monday, February 22, 2010 03:25 AM

> How do you open an .mmmp file?
> They get produced, but I can't figure out how to re-open!

Sadly that part hasn't been completed. It was always intended but never high enough on the list to get done yet. Soon though I hope.

Posted by BVOCS on Thursday, February 25, 2010 07:35 PM

works like a charm! thx for this nice tool!

Posted by Mike on Saturday, March 27, 2010 09:26 AM

Hi, when the software scan the .vpb file, return an error: run-time error '52': bad file name or number

I done some test and i think that the problem are "Path32" in the .vpb file. If i delete that row, MMM finish your scan and show (rightly) a message: "... no EXE file found in project folder..."

Posted by matpez on Thursday, April 8, 2010 08:01 AM

Thanks. Another one for the fix list!

Posted by BVOCS on Thursday, April 8, 2010 04:12 PM

I tried using this using the simplest settings I could (no XP themes, etc.).

It makes the Manifest OK but when I run the app I get the error below.
If I remove the manifest file the app then runs, so it's something about the manifest:

This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix the problem.

Any ideas?

Posted by Clay on Friday, May 21, 2010 01:43 PM

This result can be caused by many things, but most likely there is either a DLL/OCX used that MMM cannot isolate or an ActiveX EXE is involved. Can you create a small project using each one separately until the problem reoccurs? Or remove one by one until the problem goes away? Knowing which library produces this result will help a lot.

Posted by BVOCS on Friday, May 21, 2010 09:07 PM

I've been experimenting with MMM 0.7 for a while and for the most part it seems to work great. I did however find that the manifest that was created for COMCTL32.OCX would not work, and would product the error reported by Clay. The problem is that there are duplicate 'ProgIDs' for most of the common controls - two CLSIDs for the same ProgID. I messed around with the created manifest and found out which CLSIDs were the "real" ones and have this working now. I also found a few other places where the manifest would not work, but with a little tweaking I got a working manifest for all of the OCXs & DLLs used in may app. I'm going to let "real" users check it out next week.

I can post the corrected manifest for comctl32.ocx if you would like.

Posted by Peter S on Wednesday, June 2, 2010 08:49 PM

I'll look at this Peter. Thanks for bringing it to my attention. Feel free to use the email link above or in my "posted by" link if you want to send along your edited manifest.

Posted by BVOCS on Wednesday, June 16, 2010 02:27 AM

XP SP3 + & VB6 + SP6

I can not start the program, I get the following error:
Run-time Error 7: Out of memory
Thanks
Greg

Posted by Greg on Friday, July 2, 2010 03:11 AM

Greg - Is there anything else unusual going on when you try running the program? Is your Project very large? Using any unusual DLLs or OCXs? I have never seen this one reported before.

Posted by BVOCS on Saturday, July 3, 2010 11:18 AM

---------------------------
MMM
---------------------------
Run-time error '380':

Invalid property value
---------------------------
OK
---------------------------

We found a solution, it's a "gambiarra". In our project the error occurred when we tried to generate a manifest file of some DLLs with many classes. The solution was to create a manifest file for each DLL and then join the files in a single manifest manually. At least it worked here. E mando um salve ai pra galera Unihealth.

Posted by GambiarraMan on Friday, August 20, 2010 01:21 PM

I get the "can't find project exe" error. The exe is right there next to the vbp....

Posted by Kris on Thursday, August 26, 2010 08:11 AM

I'd guess you haven't saved the project after doing a Make. The VBP file gets updated with the EXE location by saving after Make.

Posted by BVOCS on Friday, August 27, 2010 08:51 PM

<< View previous comments