DriverPacks.net Forum - Dell D610/Mobility X300 Problems

Re: Dell D610/Mobility X300 Problems

null@example.com (mr_smartepants) — Fri, 04 Jul 2008 12:01:06 +0000

OverFlow wrote:

what if the new folder was G_Com (Common) and contained the main files...
then if ati mobile or GA was selected then G_Com would automaticaly be selected?

Sure, I suppose. You could put the common items (control panels etc.) in G_Com and have the finisher take care of the rest. The drivers on the other hand would need dedicated folder structure since some of the .infs are looking for specific folder names (that we cannot change due to driver signing). It's an interesting concept. Hmmm.

Re: Dell D610/Mobility X300 Problems

null@example.com (OverFlow) — Fri, 04 Jul 2008 08:18:29 +0000

thinking it through...

if we select all packs then we still have the same conflicts as now...
... we dont have to select all packs

if all the ati are in one pack (includeing the mobile) then we still have the same conflicts as now...
... ?

what if the new folder was G_Com (Common) and contained the main files...
then if ati mobile or GA was selected then G_Com would automaticaly be selected?

i really differ to you mr_s you are the Graphics Master and i respect your experience and viewpoint.

Re: Dell D610/Mobility X300 Problems

null@example.com (mr_smartepants) — Fri, 04 Jul 2008 05:12:49 +0000

Because the ATI/nvidia mainstream drivers are shared between their desktop/mobile counterparts, there's going to be a size hit by splitting the DriverPacks because of the overlap. We'll have to have multiple copies of control panels etc. to make each DriverPacks standalone. Unless you use a dependency (G_C depends on ATICCP from G_A) in which case you're not saving any space.
One option is to increase the number of graphics DriverPacks but split them into sub groups (G_A-a ATI, G_A-n nVidia, G_B-i Intel, etc.) since this would make it easier to update and release DriverPacks and lessen the server load since you wouldn't have to download a huge monolithic DriverPacks to get a single update. But this would require the dpbase to be recoded with the new naming schema.

Re: Dell D610/Mobility X300 Problems

null@example.com (OverFlow) — Thu, 03 Jul 2008 18:34:03 +0000

I dont think adding a pack is very difficult. It would take me a couple hours to code test and beta and a couple hours to modify the existing packs and create the new one. the hours that it would take to do are not as signifigant as the result. If it is worth doing then the time it takes is a secondary concern. Lets do what is the best solution for our short and long term goals.

Re: Dell D610/Mobility X300 Problems

null@example.com (Northland) — Wed, 02 Jul 2008 19:16:26 +0000

Hi, mr_smartepants.

Thanks for the clarification. I would be willing to test a separate mobile drivers folder (with a sysprep image) if it becomes a reality, although I realize that it would probably be a lot of work, and may not be feasible if the DPBase is coded with hard paths. I don't know if others have experienced the same results as I have, nor do I know if this is the direction the DriverPacks.net development team wants to take. I do want to express my thanks to all of you who have contributed. I appreciate your help.

Re: Dell D610/Mobility X300 Problems

null@example.com (mr_smartepants) — Wed, 02 Jul 2008 18:50:19 +0000

Northland wrote:

I am not sure how this would be possible as most ATI drivers I have seen reference the mobile drivers

Actually, the official ATI mobile drivers only reference about a dozen chipsets or so. The other hundred (I exaggerate) are added by the mobility.inf which is NOT digitally signed and we add/subtract from that .inf whenever possible to avoid breaking the driver-signing.

Re: Dell D610/Mobility X300 Problems

null@example.com (Northland) — Wed, 02 Jul 2008 18:20:32 +0000

Howdy.

Thanks for your input mr_smartepants and Jaak. I have been following the discussion, and am interested in any additional ideas you may have. I would like to find a way to not have to address this driver specifically, although Overflow's idea may end up being the only one that allows for an automated install. A separate mobile drivers folder is interesting. A separate folder may allow for excluding it in an image for testing purposes to see if issues like this are caused by other drivers (although I am not sure how this would be possible as most ATI drivers I have seen reference the mobile drivers - and editing the ATI infs break the security....)

Re: Dell D610/Mobility X300 Problems

null@example.com (mr_smartepants) — Tue, 01 Jul 2008 05:43:43 +0000

Northland wrote:

The ATI inf files reference the X300 (the mobility.inf does not - as someone commented out the X300 entry. -I think they should add it back in and fix the hardware id of ati2mtag_M22, PCI\VEN_1002&DEV_5461 to 5460 instead of the x200's 5461 - which is why I think it is commented out.)

I originally commented out the HWID in mobility.inf because it conflicted with the standard .inf from the mobile catalyst drivers. Now there's a new mobility.inf, this is a non-issue.

Jaak wrote:

Hi,
I still think we'll have to consider a real split.
DriverPack Graphics A / b /c and dpgM for the Mobile drivers (because they share common silicon and code, but fight about how it gets used.)

This is definitely possible. I'm not sure if the DPBase is coded with hard paths to ATICCC/ATICCP. It is much easier to let the DPFinisher to do all the work with exceptions.
The downside is increased filesize since we need to make all DriverPacks standalone.

Re: Dell D610/Mobility X300 Problems

null@example.com (OverFlow) — Tue, 01 Jul 2008 04:03:48 +0000

i am still leaning twards upgradeing / replaceing the integrated windows driver as the best solution.

I am just not sure waht files in addition to dosnet and txtsetup need to be modified so syprep will play nicely with the upgraded files.

It is likely that a file copy is failing - file is in use, can't replace errors

just my thoughts. i still think you can make an entry in the INI and call the dell setup.exe from the finisher that should fix it. It will probably require a reboot.

Re: Dell D610/Mobility X300 Problems

null@example.com (Jaak) — Tue, 01 Jul 2008 02:59:40 +0000

Northland wrote:

Thanks for the idea OverFlow. Unfortunately, I don't think that will work unless I stop using the entire ATI driverpacks folder in A1. The ATI inf files reference the X300 (the mobility.inf does not - as someone commented out the X300 entry. -I think they should add it back in and fix the hardware id of ati2mtag_M22, PCI\VEN_1002&DEV_5461 to 5460 instead of the x200's 5461 - which is why I think it is commented out.)

Hi,
I think our graphics guru should read this.

I still think we'll have to consider a real split.
DriverPack Graphics A / b /c and dpgM for the Mobile drivers (because they share common silicon and code, but fight about how it gets used.)

Re: Dell D610/Mobility X300 Problems

null@example.com (Northland) — Mon, 30 Jun 2008 17:53:29 +0000

Hi Overflow.

Fixing the line in the mobility.inf files was one of the first things I did to try and resolve this issue. The results are the same - the driver appears to install under device manager, but XP uses its default VGA driver instead. I am thinking that I may just have to install this one manually (post sysprep.)

Re: Dell D610/Mobility X300 Problems

null@example.com (OverFlow) — Fri, 27 Jun 2008 21:26:36 +0000

can you try updateing the commented out line with the correct value and report the result?

Re: Dell D610/Mobility X300 Problems

null@example.com (Northland) — Fri, 27 Jun 2008 17:03:32 +0000

Thanks for the idea OverFlow. Unfortunately, I don't think that will work unless I stop using the entire ATI driverpacks folder in A1. The ATI inf files reference the X300 (the mobility.inf does not - as someone commented out the X300 entry. -I think they should add it back in and fix the hardware id of ati2mtag_M22, PCI\VEN_1002&DEV_5461 to 5460 instead of the x200's 5461 - which is why I think it is commented out.)

Even if I did somehow update the XP driverstore with newer drivers, I think (correct me if I am wrong) they would not install if the driverpacks drivers were also in my image (unless the driverpacks drivers were older than the driver I used to update XP's driverstore.) I have played around with updating Vista's driver store using pnputil.exe, but have not had the need to do so in XP.

Re: Dell D610/Mobility X300 Problems

null@example.com (OverFlow) — Fri, 27 Jun 2008 07:16:06 +0000

you could slipsrteam in the newer file to your source - or even "replace" the included driver
to do so you would only need to make a few changes (maybe none if your real lucky)
use makecab to compress them and place them in the I386 folder
verify that all the references in txtsetup and dosnet are updated (if needed) and add the files to the "force copy" section.

since this is syprep it may not work unless all the files have the same names as the originals. but worth a shot i figure...

let us know... thanks for your feedback

PS you might even get away with just overwriteing the one file

Re: Dell D610/Mobility X300 Problems

null@example.com (Northland) — Thu, 26 Jun 2008 19:18:33 +0000

Well, I can verify that manually installing the Dell driver does indeed also install a newer version of ati2mtag.sys, even though it does not show up in the setupapi.log. Why it is not documented like it is when sysprep tries to install it is beyond me. I do now that the 1307 error is seen with every ati2mtag.sys file that I have tried to install through sysprep. At first I thought that this was the problem, perhaps some sort of MD5 hash issue, but I have seen this error on original ATI drivers that have never been modified. I have also seen the error with the Dell drivers that install just fine if installed manually (not to mention all of the driverpacks drivers.) Of course, this may not even be the problem...