Unable to install ATI Mobility Radeon X600 display driver RRS feed

  • Question

  • Opening a dedicated thread, since the X1400 thread got resolved in a way that doesn't seem to apply (Mobilty Radeon X1400 Driver Won't Install ).

    I've already installed the 32 bit version and was presented with no display driver option other than "Microsoft Basic Display Adapter".

    This machine, Asus M6000, runs Aero fine under Windows 7.

    Is there some way to expand the choices for display driver selection to try something else? or pull a driver from Win7 somehow?

    edit: I've tried "Update Driver" from adapter "Properties". Says it's up to date as of the post date.

    Microsoft: also, is supported hardware for Win8 an evolving story in general? Sinofsky demonstrated in the keynote that older hardware is a priority.. seems to makes sense to open the door on more OS upgrade unit sales.

    • Edited by Mick N Monday, October 17, 2011 11:45 PM add ATI to heading
    Tuesday, October 4, 2011 6:08 AM

All replies

  • Hi Mick,

    Try downloading Mobility Radeon x1400 drivers from Microsoft catalog. When downloaded, unpack the CAB cabinet archive file to a new folder. Find the setup bootstrapper EXE and set compatibility with Windows 7 in its property.

    Does not guarantee the result but worth trying.

    Also, what if you have disk an browse to "%systemroot%\Inf" where %systemroot% is your Windows 7 setup?

    Well this is the world we live in And these are the hands we're given...

    Tuesday, October 4, 2011 9:53 AM
  • Try boot into Windows 8 and then check Windows update and install all updates then restart your PC and boot in Windows 8 and then restart back and try boot into Windows 7, see if it works.
    Tuesday, October 4, 2011 12:32 PM
  • Thanks for the suggestions with some of the questions asked.

    Unfortunately I didnt take the additional time to setup a dual boot with the prior win7 install... it's only a 40GB disk anyway.

    I'll check the CAB optioned offered above though shortly. I'm currently spending my spare time rebuilding another PC to also run Windows 8.


    If anyone's got any ideas about any of the questions in the OP in the meantime please feel free to chime in.

    • Edited by Mick N Monday, October 10, 2011 12:36 AM
    Monday, October 10, 2011 12:35 AM
  • I found X600 cab's for Win7 to download on that catalog link. One's 10MB, the other 20MB.


    In the 10MB one are the following files

        69,112 atiumdva.cap
       293,188 cl_72011.cat
       293,188 cl_72207.cat
       314,521 cl_72275.cat
       314,521 cl_72277.cat
       291,117 cl_72482.cat
       293,188 cl_72737.cat
       293,188 cl_72839.cat
       314,521 cl_72878.cat
       293,188 cl_72936.cat
       293,188 cl_72981.cat
       293,188 cl_72983.cat
       293,188 cl_73041.cat
       293,188 cl_73111.cat
       293,188 cl_73114.cat
       314,521 cl_73150.cat
       293,188 cl_73153.cat
       293,188 cl_73157.cat
       293,188 cl_73161.cat
       293,188 cl_73176.cat
       293,188 cl_73178.cat
       293,188 cl_73187.cat
       328,162 ativcaxx.cpa
       180,720 atiicdxx.dat
     3,107,788 atiumdva.dat
        53,248 amdcalcl.dll
     3,256,320 amdcaldd.dll
        57,344 amdcalrt.dll
        50,688 amdpcom32.dll
        43,520 ati2edxx.dll
        53,248 ati2erec.dll
       274,432 ati2evxx.dll
        98,304 atiadlxx.dll
       425,984 atidemgx.dll
     2,340,352 atidxx32.dll
    10,981,376 atioglxx.dll
       331,776 atipdlxx.dll
       159,744 atitmmxx.dll
     4,033,536 atiumdag.dll
     4,754,432 atiumdva.dll
       262,144 oemdspif.dll
       720,896 ati2evxx.exe
        45,056 atiodcli.exe
        81,920 atiode.exe
        20,682 CL_72011.inf
        26,367 CL_72207.inf
       214,584 CL_72275.inf
       213,448 CL_72277.inf
        60,057 CL_72482.inf
       197,364 CL_72737.inf
        31,050 CL_72839.inf
       143,996 CL_72878.inf
        26,168 CL_72936.inf
        31,361 CL_72981.inf
        26,553 CL_72983.inf
        88,968 CL_73041.inf
       127,277 CL_73111.inf
       127,971 CL_73114.inf
       348,285 CL_73150.inf
       289,889 CL_73153.inf
        36,226 CL_73157.inf
       193,791 CL_73161.inf
        31,361 CL_73176.inf
        26,553 CL_73178.inf
       107,356 CL_73187.inf
           529 atiodcli.exe.manifest
           527 atiode.exe.manifest
     4,179,968 atikmdag.sys
           929 ativcaxx.vp
         2,096 ativdkxx.vp
         2,096 ativokxx.vp
         2,096 ativpkxx.vp
        52,400 ativvpxx.vp
        15,079 atiogl.xml

    If I try using hdwwiz on these files via have disk, I get an empty list of drivers, so dead end so far there.


    In the 20MB one, if I do the same with hdwwiz it tells me there are no 32 bit drivers, so I guess the 20MB version is an x64 download.

    I have installed 32bit windows8 onto this laptop.


    How do you load these drivers? I tried running the executables, but they didnt appear to do anything without parameters.

    • Edited by Mick N Monday, October 17, 2011 10:46 PM fix typo
    Monday, October 17, 2011 12:57 AM
  • Okay, could you please do the following:

    1. Press WindowsKey+Pause to open System Properties and start the Device Manager.
    2. In the Device Manager locate your video graphical card device.
    3. Double click the device that is missing drivers to open its properties dialog box.
    4. Switch to the Details tab.
    5. On the Details tab in the Property drop-down list scroll to Hardware Ids. Click the topmost record like:


    1. Press Ctrl+C to copy this string.
    2. Open the folder with unpacked driver and INF files.
    3. With a search tool such as Windows built-in search or Notepad++ find the INF file containing your device string (leaving just Vendor ID and Device ID such as PCI\VEN_10DE&DEV_0622 will be enough). Just search for the INF file that contains this string. Navigate the device setup tool to this specific INF file.

    By the way, when I was installing my LAN printer, I managed to get Windows automatically download missing drivers after I chose Have disk and selected Windows Update as a source.


    Well this is the world we live in And these are the hands we're given...
    Monday, October 17, 2011 12:49 PM
  • I'm coming to the conclusion this display adapter is a dead duck under Windows 8 for now. Details follow:


    This is the string PCI\VEN_1002&DEV_3150 you refered me to identifying

    It matched contents of two files



    attempting to point "have disk" to these specific files said it wants a folder and nothing was contained in the file I pointed to.


    I did try another 2 approaches

    1. hdwwiz, manual select, display adpaters, intel corp, (why oh why is this dialog box still not resizable?), Intel Graphics Media Accelerator 3150 (Microsoft Corp - WDDM1.0) - interesting the 3150 matching above - I also happen to know the adapter is WDDM1.0 - , "The software for this device is now installed, but may not work correctly. This device is not working properly because Windows cannot load the drivers requiered for this device. Code 31."


    2. From device manager, display adapters, basic display adapter, rclick, update driver software, browse my computer,


    Windows encountered a problem installing the driver software for your device but encountered an error while trying to install it.

    ATI MOBILITY RADEON X600 (hello!)

    "The system cannot find the file specified."


    This gives me the impression this Windows7 driver might otherwise be loaded by this method, but won't be because it's not conforming to Windows 8 expectations in some manner.


    I also tried 2. from the 20MB cab unpacked and it just said the basic display adapter is the best driver for your hardware.

    • Edited by Mick N Monday, October 24, 2011 4:04 AM emphasis for error code
    Monday, October 17, 2011 11:44 PM
  • Thank you for your response. Interesting... Please let us know if you find a solution.
    Well this is the world we live in And these are the hands we're given...
    Tuesday, October 18, 2011 6:38 AM
  • Mick,

    there is a solution to the "The system cannot find the file specified".

    1. open the Application event log, look for events with id = 1001, (source = Windows Error Reporting)

    2. in the detailed description of the event there is a text something like: "These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.8.8102.0_698fece647ac7222e3cd9ed3866acced4e834ded_cab_08cd5e35" ...

    3. open the directory ( which is different than the one in my example)

    4. there are some files, the one of type "TMP File" ( e.g. named like "LOGB408" or similar ) is the one you have to open in notepad ( or some other editor )

    5. scroll down to the end ( in notepad ) and look for the lines which state "Error 2" ...

    6. here is a text from my tmp file

    !!!  flq:                Error 2: The system cannot find the file specified.
    !    flq:                     SourceFile   - 'e:\ati\.\B_43087\atiogl.xml'

    7. the "B_43087" is the directory which is missing ( in my case, yours will be differently named ), simply create it ( but in YOUR directory structure of course, here I had "e:\ati" where the driver files were copied into originally by me )

    8. copy all the driver files into the directory ( COPY not MOVE them all !! ) and RESTART your driver installation, it should work now !


    the described procedure let me install an ATI Radeon Mobility x1600 driver onto a Windows 8 developer preview running on a HP Laptop of type nx9420, and it is WORKING !!


    HOPE, THIS WILL HELP YOU - let me know if you need further assistance )




    • Proposed as answer by MPacher Wednesday, November 2, 2011 3:03 PM
    • Edited by MPacher Wednesday, November 2, 2011 4:08 PM
    • Unproposed as answer by Mick N Thursday, November 3, 2011 4:40 AM
    Wednesday, November 2, 2011 3:03 PM
  • Hi Michael,

    Thanks for the info. I've installed Windows 8 to my main pc on an alternate disk for now and put XP back on the Asus laptop to do some low perf browser tests for the time being.

    I'd like to come back to trying Windows 8 on this laptop though, so will keep these suggestions handy, thank you.

    In the meantime somebody else trying win8 on this model might like to try the method evolving in this thread and report back if it's successful in this scenario and propose which posts here are leading to a resolution.

    • Edited by Mick N Thursday, November 3, 2011 4:41 AM
    Thursday, November 3, 2011 4:40 AM