RonCam

Thanks very much. I just now had to follow the directions a second time. Here's some feedback that may be helpful to others who have to modify the installation packages in the same way. Is there something missing from the directory, B107327? The installer threw up an error message, that a file was missing, when it was 'copying files' -- and the file was: ativvamy.dl_I hit 'retry' and no luck, then did a separate search through that folder -- and then through other folders I had downloaded -- and the search failed to find the file. I located the driver disc that came with the adapter, looked in the XP driver directory, found the file, and copied it into above directory. Then, uninstalled and reinstalled the BWC modified driver, and this time going to completion without an error. One other thing, I searched through the .inf file for two relevant entries for my card: 5000 series, and I also saw 5450 series. Both had a DevID that didn't match my card, so this was fixed before the installation was started. I was offered a choice of two drivers by the installer: the 'recommended' one didn't work, so I uninstalled that, and on the second try selected 'Mobility Radeon'. That one worked. So thanks again for the drivers, the card is again working in Windows 2000.

On the topic of Radeon drivers for Windows 2000, is it likely/possible that the kernel upgrade in Windows2000-UURollup-v11-d20140103-x86-ENU along with the XP program compatibility feature ... would permit a 'stock' ATI driver to function? This is with reference to an EAH5450 graphics adaptor. I'm curious to learn if anyone has had this experience -- or are the blackwingcat modifications still the only way to get this type of card to work, in Windows 2000?

So it's not commonly seen? Was I running it incorrectly? I ran it from inside Windows Explorer. Is it better to run it from the Win2K Command Line? Not sure if I ever saw it specified, as to where it should be run. The error message was from Win2K, when the first boot failed: the indicated folder (with the registry) 'is missing or corrupt'. I didn't check that with a file manager, but only saw no program files from the imaging software, while I was replacing the directory contents from the last good image. Here, the directory looked blank, but there could have been something that didn't show in that window. One other point, Win2Ksp5.1 went to completion, but finishing with an error message, that my Win2K installation was corrupt. So, I did an in-place reinstallation from the original Win2K sp3 CD, from inside Win2K. There was a message when it ran, that an sp3 disk couldn't be used to repair an sp4 installation, but it seemed to work anyway. I then took the only choice, a complete re-installation, which went ahead -- in spite of the warning -- and when that finished copying files, and rebooting, I was surprised to see that 1) the installed programs and desktop setup appeared untouched and 2) sp4 was still shown as installed. I thought I'd have to reinstall sp4 and so was surprised to see it still there. So this is the additional background for this case, in the event that someone sees a pattern that could have led to the Registry directory reported as missing or corrupt -- after the final step, attempting to install the 'UURollup'. I'll go through it again using your files, and perhaps running the executables from the Command Line, for good measure.

Thanks for the link. I didn't even know that would be possble. I'm going to use your rollup file in place of the other, from the YouTube link. That's the directory that contains the Windows Registry, so this couldn't be happening for everyone.

Am I correct, that the word 'here' was supposed to contain a hyperlink? I'm following the steps in your description of how to set-up Win2K, so much appreciated if you could share the link you've found, in reply to my post! I was following instructions on a YouTube video, but the copy of Windows2000-UURollup-v11-d20141130x86 at the link posted there wiped out the contents of my \winnt\system32\config\system directory. Strangely, replacing that directory's contents from a backup didn't work. So, I'm starting over and now I'm going to follow your links -- and hope for better results.

Thanks for your interest! I don't know how common, or uncommon it is for the DevID on an individual card to vary from what the driver's manufacturer thinks it should be. The source for most or all of what's on the repair/recovery disc is SAC Diagnostic Utilities, and since some of the menu selections didn't even run on my system, and some gave blank DevID fields, not sure if there's a specific utility that will be satisfactory, for everyone. I was working from the from the System Information Tools section, and I just went down the menu, running each one in sequence, until one gave me the DevID. From what I saw, I'm not sure if there's one single utility that will work for each different system. If someone wants to try sequential-downloads from the above-linked site, rather than going from one menu selection to the next, then begin with this one, and proceed from there. My best guess ... If you have a dual, or multiple boot setup, you don't need to use a boot-disc or hunt for the right download -- you just type this, at terminal. Note the DevID number this command produces. That DevID is totally absent from ATI's .inf file, so the installer acts as if the card doesn't exist on the system. sudo lshw -numeric -C display *-display description: VGA compatible controller product: Park [Mobility Radeon HD 5430] [1002:68E1] vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002] physical id: 0 bus info: pci@0000:02:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:65 memory:c0000000-cfffffff memory:ff4e0000-ff4fffff ioport:c000(size=256) memory:ff4c0000-ff4dffffI found no equivalent command for Microsoft operating systems. Not to say it doesn't exist, maybe I just couldn't find it.

This post is purely informative, for anyone following this thread: I had to return to an operating system image, taken before the blackwingcat drivers were installed, and in repeating the steps to install them, I found out why the Device Manager Device selection box was empty. The problem is with ATI not being able to keep their DevIDs 'straight', and not with the way the drivers were modified. The quotes below describe the original problem, and the solution follows, below the quoted posts: ... ... If you've never seen this before, then let me know that as well. Perhaps it will not repeat when I go to a higher driver in the 10.x series? Thanks! Hi blackwingcat, Thanks for the continuing advice. Are these the correct numbers, that you're looking for, in this list? Identification numbers for my VGA ASUS RADEON HD5450 Silent 512MB HDMI/DDR2PCIE2 card:Vendor ID: 0x1002Device ID: 0x68E1... Thanks again! The problem, the reason MS Window's driver upgrade would not 'see' the card ... is that the ATI driver package's .inf file is supplying the wrong DeviceID number. If the numbers don't match, Windows 'thinks' the system lacks the right card, for the package. Blackwingcat, is this the way it works? In the 10.07 package, I opened its .inf file for the graphics adapter and saw the line for "Radeon 5400 series" (there are no entries for the individual cards, just for the 'series') gives a different DevID number that the one above, that I gave to blackwingcat. But, I had not made a mistake -- it was copied correctly, from a label pasted to the card. The online 'Device ID - Vendor ID' databases are all giving a DevID# that matches the one in ATI's .inf file. But this is different from the one on the card's label. Then, wondering which was correct, I found a utility (in HBCD/DVD v15.2) that reads a card's DevID number, directly, and it gave me a number that matched the one given on the card's written label. Solution: with a text editor, I changed the package's DevID# for 'Radeon 5400 Series' -- from the one given in all the 'official databases' -- to the one that the utility read, directly from my card, itself. Now, the Driver Upgrade Device Selection box was populated with all the selections from the .inf file, I was able to select the '5400 series', <Enter>, and the driver files were copied and installed, the expected behavior. Reason for this post: to thank blackwingcat for all his hard work by sharing a solution to a problem, that no one would have suspected: some adapter cards can have DevID's that differ from what's given on the official lists, as well as the driver packages provided by the manufacturer. The installation won't work, until the user discovers the card's real number, and makes the number in the driver package match the one the system is reading, from the card itself.