Ghost Solution Suite

Dear Symantec,

When I import the VMXNet3 (and other ESXi 5.5 drivers) into DA within GSS 3.0, it seems to have imported the driver, but the driver seems not to be picked up by Windows. I have been running around in ever-decreasing circles, until I found this in the DriversDB Driver Manifest file:

{
    "VMXNet3" = {
        class = network,
        drivers = ({
            path = "VMXNet3\\vmxnet3ndis6.inf",
            devices = {
                0x15ad = {
                    0x7b0 = (-0x1)
                }
            },
            os = ("2003" "2008" "VISTA" "WINDOWS7" "WINDOWS8" "WINDOWS8_1" "X64_2003" "X64_2008" "X64_2008_R2" "X64_2012" "X64_2012_R2" "X64_VISTA" "X64_WINDOWS7" "X64_WINDOWS8" "X64_WINDOWS8_1" "X64_XP" "XP"),
            architecture = (X86 AMD64),
            files = ("vmxnet3ndis6.inf" "vmxnet3n61x86.sys" "vmxnet3n61x64.sys" "vmxnet3ndis6.cat")
        }),
        internal = 0
    }
}

All seems to be OK, but I noticed that all of the affected drivers have the following line:

                    0x7b0 = (-0x1)

Which I think (-0x1) looks like a NULL value!

Is the driver being uploaded improperly? What should the right value to the right of the equals and is there a fix to this?

I see no fixes for this in the HF1 and I am loathe to upgrade if there is not an issue that can be fixed with a patch.

Kindest regards,

QuietLeni

The driver manifest file is created from INF file only. If possible can you please provide INF file (driver file) ? 

Swap,

I have attached the .inf as a .txt file...

QuietLeni

Attachment(s)

vmxnet3ndis6.txt   33 KB 1 version

Studied the inf file, as per the inf this is not as issue from DA and this what exactly being expected by DA.

In the inf , for vendor ID 0x15ad and system ID 0x7b0 there is no Subsystem ID and hence there would be only 0x01 entry against this.

Thanks, Swap. This is a popular hardware type in VMWare - why will it not be used by DA?