Driver Heaven Mobility Modder.net Public Beta V 0.8.1.0 - XP and Vista Support!

ronaldace · Jun 28, 2007, 08:31 AM

Quote:

Originally Posted by SSilence

EDIT: I have solved the problem of crashes on Windows standby: I had to disable the ATT shared memory. This works under Vista and XP, for information. In Vista you can also start playing Vampire - The Masquerade Bloodlines and go standby while playing: this way you don't need to disable ATT shared mem, but the machine slowes too much for my tastes.

Yay! I was wondering what was making my laptop crash when I put it to sleep (I thought some software I installed had damaged the Vista install), and I was about to format it in a few days, now it seems the problem is solved (I have a Fujitsu-Siemens Amilo 1425 with Radeon Mobility 9700).

By the way, Modder 8.1 worked perfectly with Catalyst 7.6 on this laptop. Hopefully some problems I had with older version of Catalyst are solved (such as the drivers "forgetting" about the LCD when I plugged in an external display...). Thanks for this great software!

SSilence · Jun 29, 2007, 05:15 AM

The merit for this problem solved in Ati Tray Tools is not mine ronaldace, I have to thanks quipster811, who posted the solution at the official ATT forum...

I was thinking, the modded XG WarCat drivers behave as the normal Cat for the installation process. So I have used the Mobility Modder to patch them and I'm preparing to install them. I will post again to tell if this works or not...

Wish me good luck...

KainXS · Jun 29, 2007, 06:35 PM

is it worth uninstalling windows xp to try this mobility modder if all the other ones failed

SSilence · Jun 30, 2007, 05:44 AM

Here I am back again!

- Mission report -

Installation of WarCat using MobyModder

Mission succeeded

Details follow:
The WarCat installed fine using the Mobility Modder, but the performance gain is not so high as I expected - I will keep them until the Omegadrivers will become available for Vista.

neunon · Jul 3, 2007, 09:12 AM

When I try launching MobilityDotNET.exe, I get this ugly error (thank you .NET!):

**Spike** · Jul 3, 2007, 01:41 PM

neunon have you already tried downloadint the .NET Framework 2.0 from the MS site and reinstall that? maybe it is damaged and most times reinstalling that fixes those problems.

neunon · Jul 4, 2007, 09:46 AM

Quote:

Originally Posted by Spike

neunon have you already tried downloadint the .NET Framework 2.0 from the MS site and reinstall that? maybe it is damaged and most times reinstalling that fixes those problems.

Unfortunately, that didn't help. Note also that this is virtually a fresh install of Windows (1 week old at most), so damage is unlikely anyway. What really bugs me about this crash is that I know I could fix it if I had the source code. But I know that won't happen.

**Spike** · Jul 4, 2007, 10:32 AM

Are you sure you don't have the beta framework or compact framework installed and that you have 2.0 installed and not 1.1?

Fixing a bug is always easier when you can replicate it.

neunon · Jul 4, 2007, 12:21 PM

Quote:

Originally Posted by Spike

Are you sure you don't have the beta framework or compact framework installed and that you have 2.0 installed and not 1.1?

Fixing a bug is always easier when you can replicate it.

Yes, I'm certain. .NET Framework 2.0. Non-compact. Non-beta. Non-1.1. Please note that I do .NET development myself (though I try to avoid it because cross-platform coding is hell with it), and I'm not stupid. Forgive me for feeling a bit insulted.

And yes, bugs are easier to solve when they can be replicated. It's a shame that the stack trace provided was rather useless. It tells basically nothing about what method it was in, if any, though it looks like this happened before the program fully initialized.

**Spike** · Jul 4, 2007, 01:03 PM

neunon i am not trying to insult you, but if you know how much people mailed me with problems in Driver Cleaner or Mobility Modder and that almost all was because they had a beta framework 2.0 or damaged farmework. So that is why i asked that to be sure.

The new version should be ready soon and maybe it is fixed in that. If you want you can send me an email and you can test that version and if you have the same problem i can try to fix it before i release it. If you want to test it send an email to info@drivercleaner.net.

neunon · Jul 4, 2007, 01:07 PM

Quote:

Originally Posted by Spike

neunon i am not trying to insult you, but if you know how much people mailed me with problems in Driver Cleaner or Mobility Modder and that almost all was because they had a beta framework 2.0 or damaged farmework. So that is why i asked that to be sure.

The new version should be ready soon and maybe it is fixed in that. If you want you can send me an email and you can test that version and if you have the same problem i can try to fix it before i release it. If you want to test it send an email to info@drivercleaner.net.

I understand completely. I deal with debugging these sorts of problems in my own software all the time (though they're almost never as vague as this). You have to ask the questions that seem obvious to the informed.

If you need development help, I'd be willing to lend a hand, or if you just need a tester, I can do that too. I'm sending an email right now.

DNAtek · Jul 6, 2007, 04:03 PM

Previously I couldn't get CCC to work in Vista with an X600 SE, but after this update, all works well - thanks!

Turks · Jul 6, 2007, 08:22 PM

Thanks so much for getting the ATi drivers to work on my Toshiba laptop. It is a lot nicer having newer drivers on it.

irondog · Jul 14, 2007, 02:17 AM

Hi Spike,
I'm trying to make my mini-ITX motherboard (iBase MB879F) work with Vista.
This motherboard sports a Radeon Xpress 200M chipset that is recognized by Vista but inside device property I get ERROR CODE 43. So I tried to install mobility modder, mod 7.6 drivers but still no luck (stuck at code 43).
The device ID should be "5a42" or "PCI\VEN_1002&DEV_5A42&SUBSYS_5A411002&REV_00" .
Do you think you can help me make things work?

thanks

**Spike** · Jul 14, 2007, 04:05 AM

Do you have drivers installed for all the things in the system like motherboard chipset?

irondog · Jul 14, 2007, 06:16 AM

The NB is a ATI RC410MD and the SB is a ATI SB450.
I've found an ATI SB driver into the ATI website, I've installed it and it doesn't change anything... which other driver I should install?
This is my motherboard: http://www.ibasetechnology.net/mb879.html

thanks!

**Spike** · Jul 14, 2007, 10:22 AM

It looks wierd the page says VGA is a 9600 mobility. So the drivers that should be installed are the 9600 drivers, but you said it gets detected as a Xpress 200M. Do you know what the old driver said in the old windows?

irondog · Jul 14, 2007, 12:29 PM

I don't know, because I have never tried to install XP... but I'm willing to try...

**Spike** · Jul 14, 2007, 01:49 PM

No that is not needed. Have you also tried the official IGP drivers from the ati website? maybe that already supports your card and chipset.

irondog · Jul 14, 2007, 02:23 PM

Quote:

Originally Posted by Spike

No that is not needed. Have you also tried the official IGP drivers from the ati website? maybe that already supports your card and chipset.

Yes it's the South Bridge driver (I suppose).
Can you tell me if this board is supported by mobility modder?

**Spike** · Jul 14, 2007, 03:03 PM

I mean downloading that driver and install that. Not modding it. My program can only add support for mobility cards in the desktop driver for videocards.

I am not sure why the drivers don't work, but i am sure it is a problem with your system because if the drivers that come with windows give a code 43 then i think something is not installed right or some drivers are missing. Best you could do is ask the company where you bought the motherboard or the maker what the best thing to do is with Vista.

solian · Jul 14, 2007, 06:22 PM

Um, i just finally got the modder to work, and modded and installed the Catalyst 6.5 on my labtop with a mobility radeon 9200 32mb. But then when i restarted, everything seemed fine until the login screen. It basically gave me a black screen. So then i restarted it and this time it was a black screen again, except there's this weird thick whitish line going across somewhere near the bottom. I'm thinking maybe the catalyst version is too high for my card, but anyone know the solution? Thanks.

EDIT: ok, i got 5.3 to work. but how come it thinks my card is 9000 when its 9200?

irondog · Jul 15, 2007, 02:20 AM

Quote:

Originally Posted by Spike

I mean downloading that driver and install that. Not modding it. My program can only add support for mobility cards in the desktop driver for videocards.

I am not sure why the drivers don't work, but i am sure it is a problem with your system because if the drivers that come with windows give a code 43 then i think something is not installed right or some drivers are missing. Best you could do is ask the company where you bought the motherboard or the maker what the best thing to do is with Vista.

Hi, I've installed XP into another partition and surprisingly the board has been correctly identified installing the modified IGP drivers from ATI. I don't quite understand why it isn't recognized by Vista... I will post detailed informations on how it has been recognized by XP, I think it's some "stupid" Vista bug...

**Spike** · Jul 15, 2007, 03:15 AM

solian what is the device id of your card?

Also the 9000 and the 9200 use almost the same settings so it doe not matter. If you can tell me the device id then i can look into it.

irondog what i know from Vista is that if the hardware is not reconized by vista that you need real vista drivers for the hardware, so maybe they will come. I think also that it is better to use xp for now, because else you can't work good on Vista if the hardware doesn't get reconized.

solian · Jul 15, 2007, 02:03 PM

I think this is the DeviceID...

PCI\VEN_1002&DEV_4C66&SUBSYS_08600E11&REV_01\4&1BF A44D4&0&0008

I wasn't sure exactly where to find(the device manager actually) , but i think this is it. Thanksf or your help. And yea, i didn't notice any changes for the worst even though it thought it was a 9000.