Log in

View Full Version : Possible bug found (with either Megui Or Microsoft.net)


cogman
4th November 2007, 04:39
So I have been using Megui development versions without a hitch all the way up to the current 1034 release. Well, being the clean freak that I am, I went through and uninstalled stuff that I don't need (MS Visual Studios Express) That in turn uninstall .net framework 3.5. And now Megui does not work, it starts up with a fatal error and a long list of problems.

I have uninstalled and reinstall .net framework (1.0 to 3.0) to no avail, do I need to go out and find 3.5 to get Megui working? Is Megui supposed to work with 3.0? or is there a registry trick I need to employ? Either way, I broke something that I don't think should have broke.

BTW I have also uninstalled and reinstalled MeGui, both through a direct download and trough a update from stable to development.

Kurtnoise
4th November 2007, 11:17
Install the framework .net 2.x

cogman
4th November 2007, 16:43
It is installed. Like I said, it was working just fine until I uninstalled visual studios with .net 3.5 framework.

Ill try and reinstall it though.

cogman
4th November 2007, 22:28
Here is a screen shot of what is going on (and shows a bit of the environment in which im running it.)

Sharktooth
5th November 2007, 13:53
say "thanks!" to microsoft...

cogman
5th November 2007, 14:29
:angry: Thank you Microsoft!

Dang, Well, I guess it is up to me to do some registry mining. Let this be a lesson to every one, don't install the Visual studios express (it was a beta version, so I guess I was asking for it) and then uninstall it. Microsoft shall smite you.

cogman
6th November 2007, 06:31
Ok, now im stumped. I can't get Megui to work at all. As you can see the running environment should be sane. I have tried completely removing all codecs, .Net, megui then reinstalling them all again, including visual studios .net express 2008 beta all over again. Yet the problem is exactly the same.

Any Ideas of what could be causing this error (error dialog box is exactly the same)

Kurtnoise
6th November 2007, 10:55
Honestly, I don't know why you have installed MSVC Express 2008. Just make a clean up and install *only* the Framework .Net 2.0...

cogman
6th November 2007, 15:46
Honestly, I don't know why you have installed MSVC Express 2008. Just make a clean up and install *only* the Framework .Net 2.0...

Honestly I don't know why that *only* Framework .Net 2.0 should make that big of a difference, and for the record I DID do that to no avail. The reason I reinstalled MSVC was because it was working at a time when I had it installed. I figured that the 3.5 framework must have jiggered with the 2.0 framework in some way to make it compatible (or incompatible). I have to ask you though, Why should me having framework 3.0 and 3.5 installed make that big of a difference? Shouldn't Megui still work as long as I have 2.0 installed?

The more I have been playing with this, the more I'm starting to believe it is not a problem with Microsoft and is a problem with megui. Could someone give me a list of dependencies? It is possible that I uninstalled something vital in my uninstalling frenzy or something that did not clean itself up properly that is somehow making megui think it is still there (and hence it crashes because it cant find the required files)

I have rolled back to a 1028 version of megui and that works. Call me crazy but that development version is not that much newer then 1034 so if my environment is truly insane then why does that version work and not 1034?

Right now I am updating all files except for the core, we will see what happens there.

cogman
6th November 2007, 15:50
alright, I updated everything except for the core from the development servers in version 1028. Had success on all files. Megui restarted and did not crash. Ill try and find a more recent version of megui and see if works.

I found a version 1033 of Megui installed it and everything worked fine. The only conclusion I can come to is that something has broken or changed in 1034, be it a dependency added or new assumption made on the system it is running on that wasn't there before. I don't know what else I could give you guys that would help you help me get it fixed, but it is DEFINITELY not microsofts fault.

Sharktooth
6th November 2007, 17:45
uhm... can you please check if you have the Lucida Console font installed?
if you dont then install it and check if 1034 works.
Oh, btw it could be MS fault... Lucida Console is a system font that comes with windows... and something (probably vs2008) could have removed it...

Kurtnoise
6th November 2007, 17:46
Are you kidding ?

Honestly I don't know why that *only* Framework .Net 2.0 should make that big of a difference, and for the record I DID do that to no avail.
trying to isolate the "bug"...thats all.


Anyway, MeGUI works for most people. So, I don't think there is a problem on this side but more on your side...

cogman
6th November 2007, 20:26
Are you kidding ?


trying to isolate the "bug"...thats all.


Anyway, MeGUI works for most people. So, I don't think there is a problem on this side but more on your side...

Yes, I know, I'm just a little frustrated with things not working.

So here are the steps which I have taken. I have completely removed All media related stuff (Megui, CCCP, Winamp, ect) I have remove all microsoft .Net stuff. so Now my computer should be clean, correct?

Ok, so the first thing I reinstalled was .Net Framework 2.0 from microsoft, no security updates. Next I reinstalled Megui. No Dice, it failed with the same error as before (it should be noted that I did see what would happen if I tried to run MeGui without either, it failed but a different fail. That is expected)

Ok, so in my current situation, I have uninstalled Megui 1034 and installed 1033. That works. This seems to tell me the problem lies in how megui was built or that I don't have a Dependency that the developer and most everyone else does have and was added just recently. Is that right? Something had to have changed from 1033 to 1034 or else both should not work.

Sharktooth
6th November 2007, 21:16
Have you checked for the presence of Lucida Console font in your system as already was told to you here (https://forum.doom9.org/showthread.php?p=1062788#post1062788)?

cogman
6th November 2007, 22:23
Have you checked for the presence of Lucida Console font in your system as already was told to you here (https://forum.doom9.org/showthread.php?p=1062788#post1062788)?

Yes, I did (sorry, the above post is actually my second as .net frameworks security update required a restart). But yes, I checked for it in the fonts directory under the control panel (in classic view) and it was present.

BTW I am using Windows XP SP2 Professional Edition (I don't know if I stated that earlier).
Ohh, And thanks for taking the time to look over my problem as well, I know you guys could have better things to do.

Sharktooth
7th November 2007, 02:41
well, the problem must be something weird on your side.
i installed megui in 2 different windows boxes and it doesnt crash.
also there are no foundamental changes between 1033 and 1034 to justify a similar crash (while it works on other systems).

DarkZell666
7th November 2007, 16:40
So here are the steps which I have taken. I have completely removed All media related stuff (Megui, CCCP, Winamp, ect) I have remove all microsoft .Net stuff. so Now my computer should be clean, correct?Let me tell you that's a mega-big mistake, and if you base your tests on that assumption you're gonna bang into a freakin' brick wall ;)

In this precise case, why not install a fresh xp copy inside a virtualbox (http://www.virtualbox.org/), install .net fw 2.0, then megui 1034 (see if that works), then install .net fw 3.5 (check if megui still works), then install msvc2008 (+check megui again), remove msvc2008 (+check again), remove .net fw 3.5 (+check again). This sounds like a sane test procedure I think. Keep "system restoration" active inside the virtualbox so you can rollback and compare between each step. At least you'll be able to do that without screwing your system up :)

cogman
8th November 2007, 08:13
Well, version 1035 works. So I guess I'll just never be able to use 1034... :D. Im guessing a residual file or registry key was left behind for version 1034 that was corrupt and undeleted, but since 1034 is already outdated, I just wont worry about it.

Thanks for the help again.