Strange logs in C drive after installing VS X2 patch

[manicx]

Hi there

I was using VS X2 for some time without applying this patch since I didn't have any issues before. About 3-4 weeks ago I decided to install it and all of a sudden I started having some strange log files in C drive. The files are having names like:

26_12_38_39.log or 22_17_53_49.log

Inside the log files, I see this:

Code: Select all

CMpeg4Splitter::BreakConnect() Enter
CMpeg4Splitter::BreakConnect() Enter

One time I even got a file that was larger and had more info. Both files can be seen here (the large one) and here (smaller).

In the beginning I didn't know what was causing this. I googled it a bit but found nothing. Eventually, I decided to use Process Monitor from Sysinternal to see what is creating this. After a week of monitoring and 'playing' with Process Monitor, I finally found that this is caused by MP4 splitter by Ulead. I will give direct links from 3 images that I got from Process Monitor.

Image 1: The main screen that shows that Explorer.exe created the file.

Image 2: Details of the process


Image 3: The stack that shows where this came from. Here you can see that it is caused by ulspmp4.ax.

I checked and saw that this file seems to be updated from the patch since it has a date of 22/9/2008 as opposed to 9/6/2008 that most of the other files have.

The content in the log files seems like debug info. My questions are:

• Why am I getting those log files? It is not normal. The log files, once created, remain locked and cannot be deleted unless I restart PC and delete them.
• How can I get back the old ulspmp4.ax? I don't want to uninstall VS X2 and install it from scratch without applying the patch. It seems pointless. There is no uninstall option for the patch.
• Should corel be notified for that (or even better, do they know about that)? As a software developer myself, I consider having the debug info coming to the final user completely wrong.

Thanks in advance

[jbarchuk]

I was using VS X2 for some time without applying this

I *probably* but don't know for sure that I have that patch, don't know how to test for it, and don't recall when I might have applied it. I tend to apply patches as soon as I read about them.

26_12_38_39.log or 22_17_53_49.log

Well. Hmmm. I just found ONE HUNDRED AND FORTY THREE of these little boogerettes totaling about ONE GIGABYTE. Duh. It's not just the space but the time wasted looking through that many extra root directory items.

One time I even got a file that was larger and had more info.

One time? LOL! About half of mine were one line or two lines, the other half were in the 20M to 50M range. Yep all debug info.

Process Monitor from Sysinternal

Never heard of that but but pretty dang clever and useful and will keep it in mind for the future.

I checked and saw that this file seems to be updated from the patch since it has a date of 22/9/2008 as opposed to 9/6/2008 that most of the other files have.

All my logs were dated Jan through July of this year. I've been with VS since V6 and don't know what I might have done in either Jan or July to turn the garbage on/off.

My questions are:

Forget about any of that. You may be interested in what/why and all that but after such a blatant and obvious screwup you ain't gonna get *any* answer from Corel.

How can I get back the old ulspmp4.ax?

Mine is located in /Program Files/Common Files/Ulead Systems/MPEG/ulspmp4.ax file size 660112 and dated Sep 22 2008. Do you want a copy to try?

Should corel be notified for that (or even better, do they know about that)?

HAHAHAHEHEHEHEHAHAHAHAHAHAHEHEHEHAHAAAAA LOL! ..wiping eyes and blowing runny nose.. Sorry, that was just way too funny.

As a software developer myself, I consider having the debug info coming to the final user completely wrong.

Well then you should also know that software, by definition, is a series of computer instructions that: has bugs, will crash, may do odd inexplicable things at any time, and may or may not do what you need/ask it to do depending on POM, digital hormones, and too many other variables for Bill to even understand or explain.

Until you find a real fix how about a short boot script that deletes c:/*_*_*.log ? The only other *.log I had in the root was a vcredist_x86.log but only 421K so I don't mind much.

Lemme know if you want that file. Or if what you have is the same maybe someone else has something different.

Have a day!

Jim
jb@jbarchuk.com

[Black Lab]

How can I get back the old ulspmp4.ax? I don't want to uninstall VS X2 and install it from scratch without applying the patch. It seems pointless. There is no uninstall option for the patch.

Have you tried a System Restore?

[sjj1805]

Not come across those log files before but

The log files, once created, remain locked and cannot be deleted unless I restart PC and delete them.

Have you tried using the built in Windows Security tab.
Right click the file and select the security tab, choose advanced and then change the owner to yourself. Give yourself full control (read/write/alter etc.)
and then try deleting.

[manicx]

@jbarchuk: So, others have this problem too. I thought that it may be just me. I eventually did the script as you said because I couldn't bother deleting everything in C. If you have the previous version of the filter, ie before the patch, I would love to have a shot. You can PM me for this. I will also check my version and size of file and I will let you know. However, I think that from the date you give, you have the patched version. BTW, I am editing since I found the file in the cab files in the install DVD. I will try that and see what happens.

@Black Lab: No but I deffo have no restore points. And unfortunately, my ghost images are dated from 2 weeks ago to 3 days ago but I installed the patch almost 3 weeks ago so no luck here. I really do not want to go through the process on uninstalling and installing from scratch.

@sjj1805: Thanks for you suggestion. What I do is that I have a script that kills Explorer.exe and runs it again. This can do the trick. However, the problem at first place is not how to delete these files but rather not to have them created. This is why I am thinking to revert back to old splitter file (hoping that it is only this and not a combination of things installed from the patch).

[Ron P.]

FWIW, I also get those files, however have no problem deleting them. I've not found a way to shut-off the creation of them..

[manicx]

So, do you think we can find a solution to this ie not have them created? It is not critical but still, it is annoying.

[sjj1805]

You are looking in the wrong place, if you really want to research Windows Log Files you are better off using Google.

A quick check of my laptop shows that I have 774 log files and hardly any of them are anything to do with Corel software.

[manicx]

Actually, I am looking to the right place. The log files are not Windows log files. They are Corel VS X2 log files that are created by Ulead MP4 splitter as I explained earlier. So, it has nothing to do with windows and other users verified the issue.

[Geoff_8]

Has anyone come up with a answer to this yet? It is definitely cause by Pro X2 and as was stated earlier is an annoyance and is chewing up disk space.

[sjj1805]

If they bother you that much why not download the freebie batchrun then create a batch file that can be run either on computer startup or by using Windows Scheduled Tasks.