Program Crashes At Start

[cyberber]

This is what happens i installed Roxio Creator 2009 all goes well once asked to reboot i do. Afterwords Computer boots back up and i open Roxio Creator 2009 from the desktop on start i got a error box saying Roxio Creator has encountered a Problem and needs to Close. We are sorry for the inconvenience. Then on the bottom left hand side of the window it says What data does this error report contain? so i clicked it and this is what it says

 

Eventype: clr20r3 P1: RoxioCentralfx.exe P2: 4.12.0.0

P3: 48a05348 P4: roxiocentralfx P5: 0.0.0.0 P6: 48a05348

P7: 17e P8: 12 P9: system.badimageformatexception

 

Also i can open the individual Applications fine just the Main App does not open it really weird i tried reinstalled many times also i am using Windows Xp SP3 and i got .net 3.5 SP1 please help. This one is different from the the others described, because its not missing the milcore.dll file that others have reported so far it has something to do with initial image format. Can any of the gurus in this community help??????

 

 

I would really appreciate it, & thank you in advance

[gi7omy]

The milcore.dll problem is one created by Microsoft. When you installed SP1 to dotNET 3.5, that knocked it out.

 

Solution is to remove 3.5 (in order to take out the SP1) and also do a clean install of EMC2009. Do NOT install SP1 until MS comes up with a 'fix'

 

Check the following (EMC2009 is not alone in having this problem)

 

http://social.msdn.microsoft.com/Forums/en...6-9a5581782061/

 

There is a download of milcore.dll available here (but it may be incompatible with your version of dotNET so install it at your own risk)

 

http://www.dynamiclink.nl/htmfiles/rframes...info_m/1045.htm

 

 

[KennethELamb]

I usually stay out of the back and forths between people, but I have to comment on the "Roxio Apologist" attitude seen in a series of one individual's posts. After more than 12,000 posts, it's possible he has lost some objectivity.

 

1) It's Roxio's responsibility to "get with the program" and patch their product to MS's standards. You write to Windows; Windows does not write to you. The reason is simple: MS has to cover thousands and thousands of programs, and the Roxio programmers only have to cover 2 OSs - XP and Vista.

 

2) I keep seeing this attempt to push Roxio's poor programming off onto MS; that is what I mean by becoming an unobjective apologist for Roxio. The guy at the top who complained about Roxio using old code, and not updating their product to the latest standards is correct to be miffed; end-users shouldn't be expected to unload 2, or possibly 3 .net framework versions, then go through the contortions of a highly sequential flow chart of reinstalling them. End-users are exactly that: end-users. They are not "digital gurus."

 

3) It appears Roxio did get with the program, although the SP1 for 2009 is undated on the Roxio site (another sloppy programming practice). You can find it at:

 

http://www.roxio.com/enu/support/c2009/software_updates.aspx

 

According to the disclaimer, it, "Resolves a Windows XP compatibility issue with .Net Framework."

 

4) The file is dated 10/20/2008. Most of these posts making excuses for Roxio are in November. I guess some digital gurus didn't check out the latest FAQs.

 

5) But for good measure, have you tried to download the PDF versions of the Getting Started Guide and the Users Manual from the Roxio site? Good Luck - they are both "HTTP 404 not found" dead links. How exactly does Roxio explain having dead links to these high-demand products? For the Roxio Kool-Aid drinkers out there, I will tell you that there is no excuse. It is just another example of sloppy programming.

 

6) Just to give you some perspective, I've used Roxio since version 4, and every version since then. When my company manufactures computers with optical drives ordered for them, I end up putting in Nero because Roxio is not out there making the contracts it needs to make with the drive manufacturers. It breaks my heart, but keeping Roxio in business is not my problem.

 

Nero is eating their lunch, not because it is a better product (it isn't), but because it is taking a highly aggressive market-share campaign straight to the desktops of end-users - and Roxio isn't. This is another example of sloppy management at Roxio. Their market share is decreasing simply because the shortest learning curve is the one you already know, and this sloppy management practice of giving away market share to Nero means that Nero will end up with a perceived "everybody I know is using it" dominance. I add this in case you are invested in Roxio; all this sloppiness is going to hurt the company no matter how "psychologically invested" you are in Roxio.

 

7) In summary, get off MS's back. Thank God Bill Gates beat Steve Jobs, or we'd all still pay $5,000 for a mediocre desktop with Jobs micro-managing our lives. As it is, Apple addicts pay about 100% more for an Intel machine just so they can have their narrow choice of software, and no choice - for all practical purposes - of hardware. There is a reason why Jobs is at 3% of the market, and Gates is at 90%. MS has done an incredible job of making computing as wide-open to new programs and hardware as possible.

 

This thread tells the real story: sloppy programmers and their knee-jerk excuses blaming MS for their shortfalls. On the bright side, Roxio got out an SP to fix the .net problem - and frankly, considering the program has only been out a couple of months, and the SP1 fix came out in about 6 weeks after the official launch of 2009, so give them that credit.

 

But regardless, it's still a pain, and Roxio should have incorporated the fix in their Gold Release (Roxio attends developer conferences and knew well in advance about this problem).

 

That's it for me on this topic. I don't care to get into it with the digital gurus who obviously have a lot of time on their hands (how do you write 13,000 posts in less than a year?). So if you want to flame me, have at it. It won't change the fact that after all is said and done, it is Roxio's responsibility to keep its programming current, and not the end-users' responsibility to spend hours loading and unloading programs to make up for Roxio's sloppiness.

 

I mean, the manual links tells it like it is as a reflection of the bigger issues here: they either don't know their manual links are dead or don't care. Either way, it tells the story of Roxio and the quality of its programming and its management.

 

Well, enough. I'm sure we'll all just muddle through. Happy Thanksgiving!

-30-

[gi7omy]

Shall we get a few facts straight here:

 

SP1 for dotNET came out AFTER the release of 2009 - not before

 

The date on the patch file is irrelevant - the date of release is what counts. No-one here knew about it until then, so we couldn't say 'go here, do that'

 

MS change things without notification - it is not the first time, nor will it be the last, that one of their updates has hit applications (and I'm not just referring to Roxio here)

 

Regarding post counts - the 'date of joining' is a different thing - this is a replacement forum and the date I came here is that date - the post counts (which to me are a joke) were carried over from the old forum. I've been posting here since version 5

 

Roxio have been informed of the dead links on the guides. It's down to the webmaster (if there IS one after the last round of pay-offs)

 

I agree that it is the responsibility to keep things current - but when MS issue a patch that has a knock-on effect on some computers (some people had problems with dotNET, others didn't) it takes time to catch and fix, especially when the MS patch has been changed slightly from their beta to release (the 'killed' dll file was a case in point - 2009 installed just fine EXCEPT where someone did an 'optional' update and put it in themselves before installing 2009)

 

I fail to see your comparison between Gates and Jobs as relevant - Sun can put out its Solaris 10 for FREE and still make money. Jobs charges an arm and a leg for proprietary hardware and a software that is just a fancy desktop based on FreeBSD, Gates just charges an arm and a leg for software (and probably curses IBM for making PC architecture open source)

 

Nero does have a more pushy stance on OEM software. Why Sonic doesn't do the same, I don't know, but then I'm not employed by Sonic. Nero also releases a LOT of patches - now why should such a stable program NEED patching so often?

 

btw - I keep all my old app installation stuff - want a copy of ECD2 by Adaptec?

[Jim_Hardin]

The clean install starts a user at a known point and condition. You cannot believe how many threads go on for 25 entries back and forth before the user casually mentions that there were 4 or 5 error messages during install but he just ignored them… Or something to that effect.

 

The choice is yours, continue to thrash about with a program that doesn't work or try something that most often fixes it...

 

Another option I woudl do if I were in your place is put down the keyboard and pick up my telephone.

[drawsalot]

"Program Crashes at Start with Error"

 

I have a similar issue, one that I discovered through these posts is related to a file from .NET Framework called Milcore.dll. After doing a "clean" (read pain-in-the-butt) uninstall of Creator 2009, and re-installing, the issue persisted. I uninstalled .NET Framework 3.5 and .NET Framework 3.0 Service Pack 2. I downloaded .NET Framework 3.0 from Microsoft and installed it.

 

Subsequently, the main program window for Creator 2009 opened normally (and a quick check of \Windows\System32\ showed the Milcore file present).

I copied the file to my Desktop and installed .NET Framework 3.0, Service Pack 1 (I found no Service Pack 2 available for download). After this installation, it also worked normally.

 

Once I installed .NET Framework 3.5, the application again launched normally.

 

So, I would suggest uninstalling .NET versions 3.5 SP1, 3.5, 3.0 and then downloading the 3.0, 3.0 SP1 and 3.5 .NET Frameworks from MS and starting there. Hope this helps.

[gi7omy]

Actually that's what was reported some time back - the fault lies with the service pack for 3.5 and that's down to MS

 

It's covered in a number of posts on the board (to uninstall 3.5 and 2 as the installation will patch 2 and install the working version of 3.5)

[Jim_Hardin]

How does it work after you do the Clean Install? - XP

 

(that is a backward way of suggesting you do the Clean Install )

 

[cyberber]

I did a clean install I reformatted my Hard Drive installed Windows XP SP3, & installed the latest Drivers for the Video and Audio Card & after that I installed the updates from Microsoft, Once I did all that I installed the Roxio Creator 2009. So yes its a pretty clean install I would say. Why do you always make people revert back to a clean install instead of finding solutions to the problems. I have in my machine with Nero latest version, NTI Media maker latest version & Gear Pro Mastering Edition latest version, none of them have caused me any problems. Yet Roxio Creator 2009 has been a pain to a lot of people this is worst than an alpha or pre beta versions, they are using us as Ginnie Pigs for a revised version. If this version has so many failures why don't they just release a patch. First it was the problem with .Net 3.5 why can't people have the latest versions in their machines .NET 3.5 SP1. Roxio released this product in in the begging of Sept of this year, Roxio is using version 3.5 for the installation a product released by Microsoft in July 0f 2007. Version SP1 was released first in March 2008, why can't Roxio develop programs with the latest versions. The next issue was with DirectX they also used a very old version instead of the newest version. Please answer me all these questions and finally bring solutions to the problems expressed by the people who have paid for this program, not silly questions if this is a clean install.

[grandpabruce]

I did a clean install I reformatted my Hard Drive installed Windows XP SP3, & installed the latest Drivers for the Video and Audio Card & after that I installed the updates from Microsoft, Once I did all that I installed the Roxio Creator 2009. So yes its a pretty clean install I would say. Why do you always make people revert back to a clean install instead of finding solutions to the problems. I have in my machine with Nero latest version, NTI Media maker latest version & Gear Pro Mastering Edition latest version, none of them have caused me any problems. Yet Roxio Creator 2009 has been a pain to a lot of people this is worst than an alpha or pre beta versions, they are using us as Ginnie Pigs for a revised version. If this version has so many failures why don't they just release a patch. First it was the problem with .Net 3.5 why can't people have the latest versions in their machines .NET 3.5 SP1. Roxio released this product in in the begging of Sept of this year, Roxio is using version 3.5 for the installation a product released by Microsoft in July 0f 2007. Version SP1 was released first in March 2008, why can't Roxio develop programs with the latest versions. The next issue was with DirectX they also used a very old version instead of the newest version. Please answer me all these questions and finally bring solutions to the problems expressed by the people who have paid for this program, not silly questions if this is a clean install.

 

Ask Roxio, directly. This is a users forum, and the folks posting here, are users, like you and don't work for Roxio.

 

[jgoldb1]

It is very possible that the Ropxio WPF app is using a Splash Screen based on the older sample from this blog (http://blogs.msdn.com/jgoldb/archive/2007/12/10/splash-screen-to-improve-wpf-application-perceived-cold-startup-performance.aspx)

This sample was written for .Net 3.0/3.5 before WPF 3.5 Sp1 was designed and has explicit dependency on on milcore.dll.

 

If this is the case, Roxio need to fix the splash screen in their app for it to work with .Net 3.5 Sp1

Read comments in the blog

 

 

[joris]

Anyone know of another workaround then to uninstall the different versions of the .Net framework. That is definitely not an option since I can't uninstall them since there are other programs which have dependencies upon them - such as Visual Studio 2008,

 

Rgds,

 

Joris

[gi7omy]

2 and 3.5 will be re-installed.

 

The problem, I repeat, occured when MS 'patched' 3.5 and removed a critical file

[BigTem]

The clean install starts a user at a known point and condition. You cannot believe how many threads go on for 25 entries back and forth before the user casually mentions that there were 4 or 5 error messages during install but he just ignored them… Or something to that effect.

 

The choice is yours, continue to thrash about with a program that doesn't work or try something that most often fixes it...

 

Another option I woudl do if I were in your place is put down the keyboard and pick up my telephone.

 

I have the same problem with milcore.dll missing. I manually installed .net 3.5 SP1 when the .net 3.5 installation kept locking up with the Creator 2009 CD. I also did a clean install. I tried the telephone, but it's after hours. Do you know where I can download milcore.dll? Thanks.

[gi7omy]

It is very possible that the Ropxio WPF app is using a Splash Screen based on the older sample from this blog (http://blogs.msdn.com/jgoldb/archive/2007/12/10/splash-screen-to-improve-wpf-application-perceived-cold-startup-performance.aspx)

This sample was written for .Net 3.0/3.5 before WPF 3.5 Sp1 was designed and has explicit dependency on on milcore.dll.

 

If this is the case, Roxio need to fix the splash screen in their app for it to work with .Net 3.5 Sp1

Read comments in the blog

 

Would it not be beholden on MS to refrain from messing things up in the FIRST place?

 

They chan ged things and caused problems for others

 

People used to joke about Linux changing things - MS seem to have been bitten by the bug to constantly tinker - at least Linux changes worked without wiping other apps out