none
POSReady 2009 and PCI Express RRS feed

  • Question

  • Have my first hardware incompatibility when comparing XP SP3 and PR9. A simple single port serial expansion card, PCIe x4 installs and operates OK in XP. Same motherboard w/ PR9, the drivers will not install. PR9 sees the new hardward, launches the new hardware found wizard. I point to the driver files, PR9 starts to install, then the wizard exits, saying the files are corrupted, and the card remains in Device Manager as hardware with a problem. Tested on same version motherboard, different system, same issue. Motherboard has Celeron 440, Q45 chipset, 1GB 1333MHz DDR3 DRAM.

    Exact same hardware when testing XP and PR9. No problems with same brand, different model PCI serial card installations on the mbd w/ PR9. Anyone else have issues w/ PCI Express and PR9?

    Thanks,

    Paul  

    Friday, August 13, 2010 12:10 PM

Answers

  • Hi again, Paul,

    In most cases, XP and POSReady should operate identical since what is deployed should be the same.  There is only one exception that drivers can be optional.  This means that what's installed by Setup is all that's there and nothing else can be installed afterward.  This was to free up disk space assuming that there would be no additional hardware changes afterward.

    This is just a theory, so let us know if this helps.  In Control Panel, Add/Remove Programs, Add/Remove Windows Components, there should be Additional Drivers.  If this is not checked, check it and try installing your driver again.  This may be unchecked afterward to free up the disk space.

    If it is checked, then it will require you to dig a little deeper.  There might be a driver that exists in XP that doesn't exist in POSReady.  The only way might be to dig through the SetupApi.log to find out where the error takes place.

    Brendan

    Friday, August 13, 2010 5:37 PM
    Moderator
  • Paul,

    If Brendan's solution does not lead you in the right direction, is it possible that you have POSReady installed on a USB device?  When POSReady is installed on USB devices the SetupAPI functionality is crippled in order to protect the bootable USB drivers from being overwritten with the standard USB drivers.  If this is the case, let us know and we can provide detailed instructions for working around this situation.

    Terry Warwick
    Microsoft

    Tuesday, August 17, 2010 3:34 AM

All replies

  • Hi again, Paul,

    In most cases, XP and POSReady should operate identical since what is deployed should be the same.  There is only one exception that drivers can be optional.  This means that what's installed by Setup is all that's there and nothing else can be installed afterward.  This was to free up disk space assuming that there would be no additional hardware changes afterward.

    This is just a theory, so let us know if this helps.  In Control Panel, Add/Remove Programs, Add/Remove Windows Components, there should be Additional Drivers.  If this is not checked, check it and try installing your driver again.  This may be unchecked afterward to free up the disk space.

    If it is checked, then it will require you to dig a little deeper.  There might be a driver that exists in XP that doesn't exist in POSReady.  The only way might be to dig through the SetupApi.log to find out where the error takes place.

    Brendan

    Friday, August 13, 2010 5:37 PM
    Moderator
  • Paul,

    If Brendan's solution does not lead you in the right direction, is it possible that you have POSReady installed on a USB device?  When POSReady is installed on USB devices the SetupAPI functionality is crippled in order to protect the bootable USB drivers from being overwritten with the standard USB drivers.  If this is the case, let us know and we can provide detailed instructions for working around this situation.

    Terry Warwick
    Microsoft

    Tuesday, August 17, 2010 3:34 AM