Correction, msvcr100.dll starts in the 11.12's, not 11.11's, I just downloaded them all again to recheck ( for desktop PC )

if the msvcr100.dll could be added to the DP's than that would fix these newer drivers for all, full install of ATI drivers, it is placed into the 'C:\windows\system32' folder

If there is a test version of this done, I will test the DP out smile I use win 7 x64 Pro and desktop PC not mobile ( just noticed this was a Mobile section )

I can confirm this is a issue on ATI's side, I have been usin ATI's drivers to make my own DP's and then all of a sudden I got this same error on a install of win 7 x64 Pro, I thought the drivers were corrupted.

I re download the x64 drivers from ATI and made my DP up, integrated them, and did a clean install, and the error was present, the same happens to x86 users also.

The MSVCR100.dll is in the main folder after extracting the ATI_xxx_ccc_ocl.exe, witch I thought was/is very stupid of them to do, knowin many, many people integrate these drivers and it would cause issues.

I have checked the drivers from 11.9's on up, this MSVCR100.dll is in 11.11's on up, nothing can be done about it, use the 11.10's for integratin, then install 11.11's full package onward is wat I am doin.

There is not much info about this in google search either.

EDIT:
In fact, if anyone would like to affirm this, just download any newer version of the ATI drivers from ATI ( version 11.11 on up ), act like yer goin to install the .exe, then cancel install, then go to the extracted folder witch in my case is C:\ATI, in this folder do a search for MSVCR100.dll, you will find., get any version earlier than 11.11, do the same, no MSVCR100.dll.

3

(41 replies, posted in Vista / 7 DriverPack Graphics B)

I get this error in DISM with DP_Graphics_B_wnt6-x64_1007\x64\G_B\ATI\1\CH_98791.inf:Error - An error occurred. The driver package could not be installed.


DISM log..
2011-03-28 22:37:38, Error                 DISM   DISM Driver Manager: PID=2844 Failed to install the driver package 'C:\DP_Graphics_B_wnt6-x64_1007\x64\G_B\ATI\1\CH_98791.inf'. - CDmiDriverStore::Import(hr:0x80070002)
2011-03-28 22:37:38, Error                 DISM   DISM Driver Manager: PID=2844 Failed to install the driver package 'C:\DP_Graphics_B_wnt6-x64_1007\x64\G_B\ATI\1\CH_98791.inf'. - CDriverPackage::InternalInstall(hr:0x80070002)
2011-03-28 22:37:38, Error                 DISM   DISM Driver Manager: PID=2844 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmiprovider\dll\driverpackage.cpp:433 - CDriverPackage::Install(hr:0x80070002)
2011-03-28 22:37:38, Info                  DISM   DISM Driver Manager: PID=2844 Driver package C:\DP_Graphics_B_wnt6-x64_1007\x64\G_B\ATI\1\CH_98791.inf failed to install. (hr:0x80070002). - CDriverManager::AddDriverPackagesFromCollection


EDIT: seems a .dll is missing from the folder..

     flq:                SourcePath   - [C:\DP_Graphics_B_wnt6-x64_1007\x64\G_B\ATI\1\B_98282]
     flq:                SourceFile   - [atitmp64.dll]
     flq:                Flags        - 0x00000000
     flq:           {_commit_copyfile}
!!!  flq:                Error installing file (0x00000002)
!!!  flq:                Error 2: The system cannot find the file specified.
!    flq:                     SourceFile   - 'C:\DP_Graphics_B_wnt6-x64_1007\x64\G_B\ATI\1\B_98282\atitmp64.dll'


EDIT 2:

Now that I look there is no mention of this CH_98791.inf in the Overview.. http://driverpacks.net/driverpacks/wind … 07/drivers

Well after the time I had with it to be in this much of a trouble shooting atmosphere<- before I posted here also -  I just re downloaded everything, and redid my entire Win Xp CD with all up to date stuff DP's, DPBase, all updates for Win - that would allow for integration up to know/ last week if its the case.., NOW it will not go into windows for some reason witch I think I know the problem to that is it has IGP and I'm running a HD4830 and I think I left the IGP drivers by mistake lol @ that 1. <- and yes I cut the DP's down by a few MB's to allow for some programs to be put on the CD disk also.

Anyways, I got it past the RAID recognition problem - never doubted the DP's - This is a NEW system so I'm still getting use to the way this this acts, now I just need to figure out the *final boot into windows, hard reboot problem.

Thanks OverFlow for the help and suggestions to resolve this as You are a commendable Admin here!!

P.S. the rest of the DP's worked Great to this point, I feel I will have this minor issue fixed by the end of this evening.

Keep up the good work on these driver packs as they are 1 in a million!!! ahh billion??

Thanks for the Welcome,

However I have applied the MassStorage DP several times with thoughts that I was missing something but to no avail it will not pick up the RAID

Which OS -  XP Pro Corp SP3




=========== 
PCI Devices 
=========== 
PCI\VEN_1002&DEV_4383&SUBSYS_820F1565&REV_00\3&267A616A&0&A2: Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_1002&DEV_4384&SUBSYS_00000000&REV_00\3&267A616A&0&A4: PCI standard PCI-to-PCI bridge
PCI\VEN_1002&DEV_4385&SUBSYS_37001565&REV_3A\3&267A616A&0&A0: ATI SMBus
PCI\VEN_1002&DEV_4393&SUBSYS_43931002&REV_00\3&267A616A&0&88: AMD AHCI Compatible RAID Controller    <---this little buggar
PCI\VEN_1002&DEV_4396&SUBSYS_37001565&REV_00\3&267A616A&0&92: Standard Enhanced PCI to USB Host Controller
PCI\VEN_1002&DEV_4396&SUBSYS_37001565&REV_00\3&267A616A&0&9A: Standard Enhanced PCI to USB Host Controller
PCI\VEN_1002&DEV_4397&SUBSYS_37001565&REV_00\3&267A616A&0&90: Standard OpenHCD USB Host Controller
PCI\VEN_1002&DEV_4397&SUBSYS_37001565&REV_00\3&267A616A&0&98: Standard OpenHCD USB Host Controller
PCI\VEN_1002&DEV_4398&SUBSYS_37001565&REV_00\3&267A616A&0&91: Standard OpenHCD USB Host Controller
PCI\VEN_1002&DEV_4398&SUBSYS_37001565&REV_00\3&267A616A&0&99: Standard OpenHCD USB Host Controller
PCI\VEN_1002&DEV_4399&SUBSYS_37001565&REV_00\3&267A616A&0&A5: Standard OpenHCD USB Host Controller
PCI\VEN_1002&DEV_439C&SUBSYS_439C1002&REV_00\3&267A616A&0&A1: AMD PCI IDE Controller
PCI\VEN_1002&DEV_439D&SUBSYS_00000000&REV_00\3&267A616A&0&A3: PCI standard ISA bridge
PCI\VEN_1002&DEV_944C&SUBSYS_15311462&REV_00\4&92B7792&0&0010: ATI Radeon HD 4800 Series  
PCI\VEN_1002&DEV_AA30&SUBSYS_AA301462&REV_00\4&92B7792&0&0110: Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_1022&DEV_1200&SUBSYS_00000000&REV_00\3&267A616A&0&C0: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1201&SUBSYS_00000000&REV_00\3&267A616A&0&C1: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1202&SUBSYS_00000000&REV_00\3&267A616A&0&C2: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1203&SUBSYS_00000000&REV_00\3&267A616A&0&C3: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1204&SUBSYS_00000000&REV_00\3&267A616A&0&C4: PCI standard host CPU bridge
PCI\VEN_1022&DEV_9600&SUBSYS_00000000&REV_00\3&267A616A&0&00: PCI standard host CPU bridge
PCI\VEN_1022&DEV_9603&SUBSYS_00000000&REV_00\3&267A616A&0&10: PCI standard PCI-to-PCI bridge
PCI\VEN_1022&DEV_9607&SUBSYS_00000000&REV_00\3&267A616A&0&38: PCI standard PCI-to-PCI bridge
PCI\VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10\4&2966AB86&0&30A4: Realtek RTL8139/810x Family Fast Ethernet NIC
PCI\VEN_10EC&DEV_8168&SUBSYS_23071565&REV_02\4&2BA546C5&0&0038: Realtek RTL8168C(P)/8111C(P) PCI-E Gigabit Ethernet NIC
25 matching device(s) found.
 
===========

I'm gonna re-download everything to see if it wasn't a corrupt download and give that a spin as it seems it should have worked  - by now-

If this is in the wrong place my apologizes, or has already been posted of the sort



I've been using the driver packs for sometime now and not a glitch while using them smile and I have created my own driver packs for my "older" system. However I'm in a fix with my new system TA790GX128M AMD based board, I have the drivers for the txt setup on RAID 0 etc for x86 and x64 that fits on floppy. I'm tired of relying on that drive for installation, as they are good for paper weights now, seems I have a few other files in my driver package that I really don't know what to do with sad , screens below,

http://img194.imageshack.us/img194/4244/35883523.jpg
http://img129.imageshack.us/img129/7987/87284371.jpg
http://img193.imageshack.us/img193/3931/27241053.jpg
http://img193.imageshack.us/img193/9035/44972380.jpg

My question is -  For these drivers to be recognized at setup, so I can continue without the F6 stroke, what part of these would I need??

and in what fashion would I organize them to work??

I have used Driver Guinness Pro to grab all my other NON Windows drivers for this board, and to my surprise it grabbed the AHCI drivers witch I thought were what I need to install in RAID 0 but they are not, I was confused for a bit till I looked at the PCI VEN code from system hardware info. to drivers that was grabbed with DGPro etc..

Floppy disk drivers for the RAID..
this is just the first part of the txtsetup.oem file in the second shoot above the rest is PCI\VEN code

[Disks] 
disk0 = "AMD AHCI Compatible RAID Controller Driver Diskette", \ahcix86, \
disk1 = "AMD AHCI Compatible RAID Controller Driver Diskette", \ahcix86, \x86
disk2 = "AMD AHCI Compatible RAID Controller Driver Diskette", \ahcix64, \x64

[Defaults] 
SCSI = Napa_i386_ahci8086 

[SCSI] 
Napa_i386_ahci8086 = "AMD AHCI Compatible RAID Controller-x86 platform", ahcix86 
Napa_amd64_ahci    = "AMD AHCI Compatible RAID Controller-x64 platform", ahcix64

[Files.SCSI.Napa_i386_ahci8086] 
inf	= disk1, ahcix86.inf
driver	= disk1, ahcix86.sys, ahcix86
catalog = disk1, ahcix86.cat

[Files.SCSI.Napa_amd64_ahci] 
inf	= disk2, ahcix64.inf
driver	= disk2, ahcix64.sys, ahcix64
catalog = disk2, ahcix64.cat

OPPS forgot to say this is for 32 bit for xp and x64 for Xp on seperate builds..

Any help on this would be of Great Appreciation, and would be nice to add to the MassStorage or a new driver pack for SATA RAID only maybe - I dont know lol

Thanks for Your time on this

EDIT:..As I look through the MassStorage pack I do see the IDE and SATA drivers also the RAID for 6xx and 7xx in AM2 folder,,SO I guess at this point the question would be - where/what would I need to edit to add the txt setup.oem file to be read during setup as the rest looks like just relative editing the main .ini and adding the corresponding folder with proper lable to said edited .ini area?? correct