Question Locked

Can someone help me identify what driver I need?

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

My company is invested in using "Symantec Backup Exec System Recovery Server Edition 6.5" for Windows Servers for backup/disaster recovery of one of our production servers. According to Symantec's own notes on the issue, this product can be used to recover an image (like Ghost) to dis-similar hardware; but during recovery you're prompted for hardware drivers that aren't in the image. One of the drivers is giving me a fit and all I know is that it's an "IDE controller" and the ID string that the software provides is the following:

"PCI\VEN_8086DEV_25A35UBSYS_01651028REV_02"

Is there any way to discover what driver is being reverenced that I need to provide to the software? Symantec's forums haven't been very helpful, and I don't wish to remain on hold with non-English speakers again if I can avoid it.

The hardware to which the image is being recovered is a Dell PowerEdge 750 server, and I've tried their driver for IDE Controllers, and that is not the driver it's asking for; nor is it the CERC SATA drive array--I have already provided that driver to the image successfully. At this point, I turn your direction in hope someone can point me in the direction of what hardware driver I need to provide for the above listed ID string.

11 replies

by phil.hall

Indeed those are useful resources, but the device ID is 25A35, not 25A3. I believe the final digit may prove important. Regardless, I've tried several ATA/SATA drivers for this particular server, all I know is that Symantec says this is a "PCI IDE Controller", and none of the drivers work in this instance. I do know that this driver is not the CERC SATA driver (as it asks for that driver if you hit "ignore" to this request, and it accepts the SATA driver; so I would assume that this driver is not SATA related.) I also tried the backplane controller, and that's not it either. Theoretically, this could be in the chipset rollup, but there's no way to get a file larger than a floppy's contents onto the server, so I don't know if that's even right.

Is there an Intel device with the ID of 25A35? As I have not been able to locate one. So far, you've allowed me to identify the manufacturer (8086=Intel, which I had guessed, but up until now had no proof), and to come close to a solution and I hope you can help me find whatever it is that this happens to be.

by thechas

It likely is the chip-set driver.

It may not be the IDE driver I suspect it is for the PCI bridge.

There are several ways to get a driver larger than a floppy onto any system.

DOS boot and copy from a CD onto the hard drive.

Use a DOS mode ZIP utility and create a multi-disk self extracting file.

Use boot from LAN, and copy the file from a server.

A second data drive.

A second optical drive.

Chas

by scott_heath

There is always a possibility. Unfortunately I couldn't find any other resources for this. I would call Intel.

BTW, almost all Device IDs are 0x####. There are very few that are more than 4 digits since it is hex, and hex characters are made of 2 digits. A 5 digit ID would leave a character left over.

Of course I can't completely rule it out so Intel is your best bet.

And is appears this system has USB support so you could copy the large driver to the PC via a USB Drive or couldn't you burn it to CD.

by phil.hall

The HDD will be formatted as NTFS on reboot, so DOS won't work (my employer won't spring for a solution after spending who-knows-how-much on this software). Plus, with the software, we're already booting to a PE mode, but can't access the drive except on reboot. And at that point it's already too late. (Which kills the second data drive as well); and we can't install another optical drive in the system.

I'm beginning to believe that this is a driver for the PCI Bridge, and is in the chipset utility from Intel. I have sent them an email in hopes they can (1) verify the device needing the driver, and (2) provide a possible slimmed-down driver for the device. It may not be perfect, but it would get me past the current roadblock.

by phil.hall

The Symantec software boots us into a PE environment, and there's no USB support; booting into Windows then is too late to apply the driver. I've emailed Intel (as I believe this is the PCI Bridge and is in the Intel chipset update utility) in hope that they can provide verifiction of the device and perhaps provide a slimmed down driver that will fit on a floppy (as CD and USB won't work.)

by sue t

you could partition the hard drive, copy the driver needed to the 2nd partition and then try using your Symantec restore. I am figuring that if you can tell it it is on a floppy then you should also be able to tell it that it is on another partition. Good luck.

by phil.hall

The driver appears to be rolled up into the Intel Chipset Update Utility, I'd need it extracted from that as the Symantec software is looking for the .OEM file for the driver. I'd actually thought of this idea, but was set back by the fact that I can't run an installer (I need the driver only.)

by jamesatmaisonverre

for the sound card.And judging by the code it is an ac97 sound card.Give this a shot.

by phil.hall

It can't be the sound card as this server doesn't have sound (no outputs, nor is it listed in the manifest.)

Thanks, though!

This discussion is closed to new replies.