Similar Questions

• Time of exposure with MC1362 externally triggered and PCIe-1433

  Hello

  I'm capturing images with the help of a Microtron EoSens CL MC1362 camera and NI PCIe-1433 acquisition card. I have a question about exposure times - I don't know if it is related to the acquisition, the camera or the combination card, but I hope someone here can help you.

  I'm running an external signal to the SMB connector on the card acquisition and the camera set to run in "Mode Pulse width", that allows to the capture card to take control.

  My question is:

  How can I determine the exposure time in the settings of the external signal? It is a square wave, and the cycle seems to control the exposure time.

  I guess the exposure time, E = (D/f), where f is the frequency of the signal and D is the duty cycle? for example, for f = 1 kHz, and D = 80%, exposure would be E = 0.8ms. Is this correct?

  The manual of the device can be found here:

  http://G4.com.tw/Web/file/product/UserManual/995-EoSens%203CL-MC1361-manual.PDF

  and I've included a screenshot of the revelant portions that seem to describe how the pulse width. In particular, he said "exposure time is defined by the width of the external signal. Which is equivalent to my idea of E = D/f?

  Thanks in advance for any help.

  

  This looks good to me.  The exhibition remains on while the pulse is high.  When you calculate E, you're just calculating the duration of the pulse is on.

  Bruce

• How do LV2009 see my PCIE-1433?

  Hi all - I think that this problem is just a matter of choosing the right download.  I am changing an LV application that has been installed on the demo system provided by a seller. Very kindly they offer all their source code, but it is written in the 2009 version, and they do not include the development environment. I downloaded 2009 sp1 and installed using my 2014 SP1 license. So far so good.

  When I open the VI, LV could not find one of the sub - vi IMAQ. Eventually, I realized that I needed to install the 2009 version of the CQI Vision System. Downloaded and installed, and who took care of most of the missing screws. There are still some which required the development of Vision Kit, but I do not have this license, so I removed those and tried to run the VI. I get errors that it could not open the framegrabber. It turned out that I had not released the driver for PCIE-1433.

  So I downloaded the driver, installed, package and the PCIE-1433 is still not recognized.  Now I'm stuck.  I know that this system should work somehow, because demand for the seller has worked until I started playing with it.

  Ideas, people?  Install everything in a different order (above is the actual order I installed things).

  Thank you!

  Crazy

  It seems that the PCIe-1433 needs driver IMAQ 4.4 or later, which is included in going TO 2010.03. You need this driver and LabVIEW 32-bit.

  Getting started with the NI PCIe-1433

  http://www.NI.com/PDF/manuals/374000a.PDF

  What Versions of NOR-IMAQ, NOR-IMAQdx and come from e/s NOR-IMAQ, with my Version of the software for Acquisition of Vision?

  http://digital.NI.com/public.nsf/allkb/6C42133468D66324862578BC00655CF8

  NOR-IMAQ compatibility with different Versions of LabVIEW

  http://digital.NI.com/public.nsf/allkb/DB928F6D5E9D6B97862579A7006B2850

• Basler spL2048 - 70km with card PCIe-1433, low cadence

  Dear community LabView,

  I'm trying to run a Basler Sprint Mono spL-2048-70 km with a frame grabber module NI PCIe-1433. While the initial start-up was plug-and-play, turning the camera to the specified maximum speed (300 kHz) proves to be a challenge.

  Namely, I use the camera with a trigger in burst mode (main trigger frequency 10 Hz + burstmode up to 300 kHz) but the maximum reproducible work rep for the burst rate is around 30 kHz. I tried various options to increase the overall pace over the last few days but hit a wall.

  The system is a desktop based Win 7:

  Win 7 Enterprise SP 1

  Intel Core i5-2500 @ 3.3 GHz

  8 GB ram

  64-bit system

  I have attached the sample code I use below. Its the first time I tried to create fram high rate of requests so I hope it's just a very obvious mistake that can be fixed quickly and elegant.

  Thank you very much in advance

  Dear NIko,

  Thanks again for your involvement.

  I found yet another entry in the forum which helped me a lot.

  https://forums.NI.com/T5/machine-vision/acquisition-rate-is-half-of-trig-rate-why/TD-p/2029160/page/...

  Even if it of another camera and resembles another question originally it solved my problem. It seems one must trigger the acquisition card in ' Action: trigger start of acquisition "mode and the device itself in" exposure control: triggered "in order to avoid long latencies and reach higher than 100 kHz framerates.

  Brief overview:

  -use the Vi posted

  -define the Framegrabber Action: trigger the start of the acquisition

  -define a camera exposure control: triggered

  -Use 512 pixel AOI (via Basler CTC +)

  -OR-Max allows you to set the source of external camera command-line (moving the switch directly to the camera)

  --> Aquire burst mode with frequency intraburst up to 200 kHz (not sure if about 200 kHz creates problems)

  ---> be happy

  The specification from the point of view, the camera must be able to still 300 kHz. The frequency of my goal is 200 kHz I see this issue as resolved.

  Thanks a lot for your help and I hope this helps the rest of the community, and

• IMAQ Grab Acquire.vi error when you use an external trigger on a card NI PCIe-1433 (sync problem?)

  According to my recent post on getting up and running with the NI PCIe-1433 camera link card, I ran into a bit of a snag.

  When you use the internal trigger on the camera, everything works 100%. I can view all the data from the camera in MAX as well as in the labview project. However, whenever I have set the mode switch is where things start to fall apart.

  What I have confirmed:

  -Camera is switching between inside and outside triggering.

  -NI PCIe-1433 camera link card is set up properly. While in external mode, I can trigger the camera by using a function generator and check the wire to the MAX. Everything works fine.

  When the unit is in external mode, the function Acquire.vi enter IMAQ - my mistake VI. The error is:

  Code :-1074397150

  The possible reasons for a timeout.

  Now, I have it set up so that a mistake here will not end the LabVIEW file. Sometimes, data of interest makes however (about every 10 seconds-ish). So what seems to be the case, it's that this external trigger signal is not in the lineup when the clamp is attempted. Is it possible to synchronize these? May reference the trigger signal external sort in my LabVIEW project so that the clamp is performed only when that trigger impulses?

  So I solved my problem. He was in time. The external trigger that I used for the device was simply too slow. I was initially using a trigger from 2 Hz to be able to view the values changing on LabVIEW probes. But it was enough to get enough data to move above the camera cable to assemble a picture and kept it in time. Travel up to 9 kHz solved the problem. No adjustment to the camera settings or LabVIEW code was necessary.

• Why are the characters sets are getting deleted using the card PCIe-1433?

  Hello

  I have several framegrabbers PCIe-1433 in my possession and I have a routine that sends out packets of 1 KB of calibration data to a camera at a time package.  Usually after a few starts, a time-out error because not enough data is received by the camera (the camera reacts returns with a character of receipt of each whole package).  The strange thing is that the same code works fine on the other boards of framegrabber no 1433 (using framegrabbers 1428-PCI and PCIe-1429, although I'm not able to take advantage of the faster transfer speeds) on this computer.

  I think the problem is the use of framegrabber PCIe-1433 AND model of the computer.  I tried the same code on two Dell Precision T3500 and they both allow only a few packages to send before that happen a transmission error.  When I try the same code and the same jury 1433 on a Dell Precision T3400 code works fine and I am able to send 1000 a lot of packages to the camera without error.

  It can be the cause of this problem?  I tried to change the cameralink cables and had the same problem.

  Thank you

  Bruce

  
  

• IMAQ under Win XPx64 with PCIe-1433

  I have an IMAQ application written with VS2008 (managed C++, using PInvoke). The 32-bit version works fine. But I want to build a 64-bit version.

  I have IMAQ 4.4.0 (March, exit 2010) installed. My framegrabber is a PCIe-1433. I am running Windows XP Pro x 64 on a machine of BOXX Technologies.

  When I build an x 64 version, I get the error 0xBFF60150 of imgSetBufferElement (...) IMG_BUFF_ADDRESS...). imgShowError tells me that this means "the operation is not supported for 64-bit applications."

  This error means I can't do a x 64 build with IMAQ under XPx64?

  Or does this mean that one of the parameters to imgSetBufferElement (...) IMG_BUFF_ADDRESS...) is incorrect?

  Thanks in advance.

  Hi jhc2,

  If you look at the signature for imgSetBufferElement, you will see that the value of parameter is defined as a uInt32. It is not compatible with a 64-bit being the pointer 64 bits wide application. If you take a look at the C examples included with your version of IMAQdx you can see how the replacement function imgSetBufferElement2 must therefore serve as a replacement in the new code (imgSetBufferElement should now be listed as "obsolete" in the header). The new version replaces the old version of the function and is compatible with 32-bit and 64-bit code. The syntax and parameters that are passed must be identical.

  Eric

• OR PCIe-1433 grabber in project VI

  I have a LabVIEW project where I can set up the camera is connected to the NI PCIe-1433 map. But I have to close and open NI MAX to view the video.

  Is there an example on how to pull the stream into a LabVIEW project video? I know I've seen this before with webcams and a cRIO.

  Hi Jason,

  It's good that you can see and acqurie images from the camera in MAX. I advise to use some of the expedition to start. You need get the MAX interface, for example 'img0' name and use it as input to the Init.vt IMAQ.

  You can access the latter in LabVIEW by going to help-> find examples-> hardware input and output-> Vision Acq-> NI - IMAQ-> high level-> HL Grab.vi

• Installation card PCIE mSATA in Inspiron 660

  I have a 660 that I use to run Windows Home Server 2011 it works fairly well. Recently I was the system of computers from HDD to SSD update this particular machine is a problem due to the limited number of connections sata so I found a card that allows you to connect a mSATA via PCIE player while offering a the only problem extra SATA port is that 660 s does not recognize and it does not start even with the card installed. I tested the card on another PC and I start the technical preview Windows 10 that I'm typing this on card and reader of bothe are functional. I find it weird that your Asus desktop since 2009 he will recognize but this new Dell won't. If anyone knows how I could go on the correction of this part how any help would be appreciated.

  The bios has been updated? Link to the specific map.

• PCI-DIO-32HS error FFFCB820 (-215008)

  DAQmx beginning gives this unknown error. What can it mean?

  I'm under task of digital acquisition with burst (output clock) with an external device, data transmission. Alone, it works fine.

  Then I need to measure the time after the end of playback (PFI6 = Dig0/ReadyForTransfer falling edge) to digital edge to PCI-6602...

  If I configure (road/DIO/Dig0/ReadyForTransfer to RTSI2, installation on PCI-6602 counter measures), while DIO task is running (starting, measure, stop) both run fine.

  But I need to sync.

  If I first set up task HSDIO,

  Then do road, set up and commit the task of counter configuration works very well.

  But DIO-32HS beginning gives higher error.

  Because of some course which is required for the DIO task, but is blocked by connection PCI6-RTSI2?

  Solved.

  Another development name of the channel to PFI6 instead of Dig0/ReadyForTransfer

  or a DIO task commit before routing and configuration of another task.

  But still don't know what to say error.

• PCI-6025E (DAQ) and cards-1409 (Image Interface) PCI

  Hi friends,

  I have PCI-6025E (DAQ) and cards-1409 (Image Interface) PCI installed on the Windows XP desktop, that connected to the deducted Mikron camera.

  Recently I spend my Labview to 8.6, but the Mikron camera installation software does not work.

  How can I solve the problem?

  Anyone have the installation software (PCI-6025E (DAQ) and cards-1409 (Image Interface) PCI)?

  Any suggestion is appreciated.

  Thank you

  Jack

  jackp6,

  For the 6205E you will need to download an install the Drivers OR-DAQmx which you can find here:

  NOR-DAQmx

  http://Joule.NI.com/nidu/CDs/view/p/ID/2214/lang/en

  The 1409, you must NEITHER IMAQ drivers that are included in the following the Acquisition of vision available here:

  NEITHER Vision Acquisition Software 2,010.08

  http://Joule.NI.com/nidu/CDs/view/p/ID/2137/lang/en

  Please let us know if you have any other questions.

  Kind regards

  Sam K

  Technical sales engineer

  National systems

• Error 0xBFF6001F when you use Basler acA2040-180kc and NI PCIe-1430

  Hi all

  I use a camera of the Basler acA2040-180kc and the NI PCIe-1430 to acquire images. I can't do a wink or a puncture in MAX now.

  1. I know I need to have the camera file in the devices NOR-IMAQ. Initially, I went to NOR-IMAQ devices/img 0: NI PCIe-1430/Port 0: / ni.com /Search camera (right click) and I downloaded the file from camera on the Industrial Camera Advisor Web site. This is the URL: http://sine.ni.com/apps/utf8/nipc.product?pid=11013&asid=1102. But when I tried to open, MAX gave me "error 0xBFF60108: the file of the camera does not support the current interface type.

  2. then, I found that I could use the camera file generator. I generated the file, and I could open in MAX. But after connecting the camera, I still couldn't make a wink or a puncture in MAX. He gave me "error 0xBFF6001F: could not detect a recognizable video source.»

  

  I don't know what the problem is now. I use a PoCL.MDR of 199745A - 05 National Instruments to DTS 5 M of cable. I plugged the camera link port 0 PCIe-1430 to port "B" at the back of the camera (I guess that means 'Base'). The LED on the back of the camera was not turned on, so I guess that it was not connected.

  Moreover, I also borrowed a Board NI SMU 1435 and DTS in two cables SDR to connect the camera. It worked. It says on the Industrial Camera Advisor Web site the NOR - hardware Compatible is NI PCIe-1433 and 1435-SMU-NI. So is this the reason? I have PCIe-1430 on the spot so I want to really use it.

  This is the first time to post a question. Thanks a lot guys!

  PoCL is Power-over-CameraLink and allows the framegrabber power the camera. (To my knowledge), PoCL cables are backward compatible for use in a situation of non-PoCL. Since the 1430 does not PoCL, you will need to feed externally. The connector between the ports of cameralink should leave you the power on the outside.

  The other problem is that this camera is a full-configuration camera while the 1430 supports only basic configuration. It would be possible to put the camera in a basic configuration of tab to reduced performance, but you will probably have to change the files to the device yourself.

  I think the easiest path would be to use the PCIe-1433 or complete PXI-1435 configuration (and also support PoCL).

  Eric

• XP installation hang at 34 minutes to complete

  Hello

  I am rebuilding a PC that stops installing XP Pro (SP 2 and 3), XP Home (SP1) and Vista at between 33 and 35 minutes to get everything as it is to install devices or I am trying the product reference - but sit (2000) entirely.

  It has a Ga-8IPE1000Pro2 motherboard with an update of the BIOS F10 (the problem has not changed with the update). It is a 2.8 GHz, chipset 865PE, Type of Socket 478, with 1 GB of DDR ram.

  I have deleted all unnecessary devices, exchanged everything with alternatives of working known including (IDE and SATA) HARD drive, Ram, graphics (AGP8x to PCI) card, cables, power supply, cleared the CMOS memory and flashed the BIOS.

  The PC had been used by a passion for games and I only replaced the drive HARD - not sure if it worked when last used by the previous owner.

  Is there BIOS settings that would not have been reset to the standard by clearing CMOS or BIOS flashing and selecting "optimized defaults"?

  The article kb828267 Microsoft Knowledge Base refers to that and I will try to reach the last page of the reading of the "setupapi.log" file after restarting the installation once it was broken.

  Can we see if the problem is a faulty motherboard or attached reading software problem?

  All suggestions are appretiated.

  cordially Wagga

  #I022 found "PCI\CC_0101" in C:\WINDOWS\inf\mshdc.inf; Feature: ' channel Double Standard PCI IDE Controller ". Pilot: "channel Standard dual PCI IDE controller". Supplier: "Microsoft." MFG: "(les contrôleurs Standard IDE ATA/ATAPI)"; " Section name: "pciide_Inst."
  Actual installation #I023 section: [pciide_Inst]. Rank: 0 x 00003006. Effective driver date: 01/07/2001.
  Found #I022 "PCI VEN_8086 & DEV_24DB" in C:\WINDOWS\inf\mshdc.inf; Feature: "Intel (r) 82801EB Ultra ATA Storage Controllers - 24DB. Pilot: "Intel (r) 82801EB Ultra ATA Storage Controllers - 24DB. Supplier: "Microsoft." MFG: "Intel." Section name: "intelide_Inst."
  Actual installation #I023 section: [intelide_Inst]. Rank: 0 x 00002001. Effective driver date: 01/07/2001.
  # 166 device install function: DIF_SELECTBESTCOMPATDRV.
  #I063 Selected driver installs from section [intelide_Inst] 'c:\windows\inf\mshdc.inf '.
  #I320 of the remains of the device class GUID: {4D36E96A-E325-11CE-BFC1-08002BE10318}.
  #I060 set driver selected.
  Best selected #I058 driver compatible.
  #-124 making copies only the installation of ' PCI VEN_8086 & DEV_24DB & SUBSYS_24D21458 & REV_02\3 & 13C0B0C5 & 0 & F9.
  # 166 device install function: DIF_INSTALLDEVICEFILES.
  #W383 'layout. PNF"migrates: PNF language = 0409, Thread = 0809.
  # 011 installation section [intelide_Inst] of "c:\windows\inf\mshdc.inf".
  #W383 'layout. PNF"migrates: PNF language = 0409, Thread = 0809.
  # 166 device install function: DIF_REGISTER_COINSTALLERS.
  #I056 coinstallers registered.
  # 166 device install function: DIF_INSTALLINTERFACES.
  # 011 installation section [intelide_Inst.Interfaces] of "c:\windows\inf\mshdc.inf".
  #I054 interfaces installed.
  # 166 device install function: DIF_INSTALLDEVICE.
  #I123 do a full install of ' PCI VEN_8086 & DEV_24DB & SUBSYS_24D21458 & REV_02\3 & 13C0B0C5 & 0 & F9.
  #W100 query remove the installation of ' PCI VEN_8086 & DEV_24DB & SUBSYS_24D21458 & REV_02\3 & 13C0B0C5 & 0 & F9 ' has been blocked by "IDE\DiskST38421A___6.01___\4233304435393032202020202020202020202020" (veto type 6: PNP_VetoDevice).
  Peripheral #W104 "PCI VEN_8086 & DEV_24DB & SUBSYS_24D21458 & REV_02\3 & 13C0B0C5 & 0 & F9" required reboot: query remove failed (install) CfgMgr32 returned: 0 x 17: CR_REMOVE_VETOED.
  Device #I121 of ' PCI VEN_8086 & DEV_24DB & SUBSYS_24D21458 & REV_02\3 & 13C0B0C5 & 0 & F9 ' completed successfully.
  [01/07/2012 07:46:54 296.1087 driver Install]
  # 019 Searching for hardware ID: PCI VEN_8086 & dev_24d7 & subsys_24d21458 & rev_02, PCI VEN_8086 & dev_24d7 & subsys_24d21458, PCI VEN_8086 & dev_24d7 & cc_0c0300, PCI VEN_8086 & dev_24d7 & cc_0c03
  # 018 search compatible ID: PCI VEN_8086 & dev_24d7 & rev_02 PCI VEN_8086 & dev_24d7, PCI VEN_8086 & cc_0c0300, PCI VEN_8086 & cc_0c03, PCI VEN_8086, pci\cc_0c0300, pci\cc_0c03
  # 199 Executing "C:\WINDOWS\system32\setup.exe" with the command line: setup - newsetup
  #I022 found "PCI\CC_0C0300" in C:\WINDOWS\inf\usbport.inf; Feature: "Standard universal PCI to USB Host Controller"; Pilot: "Standard universal PCI to USB Host Controller"; Supplier: "Microsoft." MFG: "(contrôleur d'hôte USB Standard)"; " Section name: "UHCI. Dev»
  #I023 actual installation section: [UHCI. Dev.NT]. Rank: 0 x 00002005. Effective driver date: 01/07/2001.
  Found #I022 "PCI VEN_8086 & DEV_24D7" in C:\WINDOWS\inf\usbport.inf; Feature: "Intel (r) 82801EB USB Universal Host Controller - 24-7." Pilot: "Intel (r) 82801EB USB Universal Host Controller - 24-7." Supplier: "Microsoft." MFG: "Intel." Section name: "UHCI. Dev»
  #I023 actual installation section: [UHCI. Dev.NT]. Rank: 0 x 00002001. Effective driver date: 01/07/2001.
  # 166 device install function: DIF_SELECTBESTCOMPATDRV.
  #I063 Selected driver installs from section [UHCI. Dev] in 'c:\windows\inf\usbport.inf '.
  #I320 of the remains of the device class GUID: (36FC9E60-C465-11CF-8056-444553540000).
  #I060 set driver selected.
  Best selected #I058 driver compatible.
  #-124 making copies only the installation of ' PCI VEN_8086 & DEV_24D7 & SUBSYS_24D21458 & REV_02\3 & 13C0B0C5 & 0 & EA.
  # 166 device install function: DIF_INSTALLDEVICEFILES.
  #W383 'LAYOUT. PNF"migrates: PNF language = 0409, Thread = 0809.
  # 011 installation section [UHCI. Dev.NT] of "c:\windows\inf\usbport.inf".
  #W383 'LAYOUT. PNF"migrates: PNF language = 0409, Thread = 0809.
  #-340 extract file "usbport.sys" in the closet "C:\WINDOWS\Driver Cache\i386\driver.cab" to "C:\WINDOWS\system32\drivers\SET2BC.tmp" (the target is "C:\WINDOWS\system32\drivers\usbport.sys").
  # 024 copies the file "C:\WINDOWS\system32\drivers\SET2BC.tmp" to "C:\WINDOWS\system32\drivers\usbport.sys.
  #E360 year not or incorrectly signed file "C:\WINDOWS\system32\drivers\SET2BC.tmp" for the driver "Intel (r) 82801EB USB Universal Host Controller - 24 D 7" will be installed (policy = ignore). "." Error 0x800b0100: no signature was present in the subject.
  # 166 device install function: DIF_REGISTER_COINSTALLERS.
  #I056 coinstallers registered.
  # 166 device install function: DIF_INSTALLINTERFACES.
  # 011 installation section [UHCI. Dev.NT.Interfaces] of "c:\windows\inf\usbport.inf".
  #I054 interfaces installed.
  # 166 device install function: DIF_INSTALLDEVICE.
  #I123 do a full install of ' PCI VEN_8086 & DEV_24D7 & SUBSYS_24D21458 & REV_02\3 & 13C0B0C5 & 0 & EA.
  Device #I121 of ' PCI VEN_8086 & DEV_24D7 & SUBSYS_24D21458 & REV_02\3 & 13C0B0C5 & 0 & EA ' completed successfully.
  [01/07/2012 07:46:57 296.1091 driver Install]
  # 019 Searching for hardware ID: PCI VEN_8086 & dev_24d5 & subsys_a0021458 & rev_02, PCI VEN_8086 & dev_24d5 & subsys_a0021458, PCI VEN_8086 & dev_24d5 & cc_040100, PCI VEN_8086 & dev_24d5 & cc_0401
  # 018 search compatible ID: PCI VEN_8086 & dev_24d5 & rev_02 PCI VEN_8086 & dev_24d5, PCI VEN_8086 & cc_040100, PCI VEN_8086 & cc_0401, PCI VEN_8086, pci\cc_040100, pci\cc_0401
  # 199 Executing "C:\WINDOWS\system32\setup.exe" with the command line: setup - newsetup
  # 166 device install function: DIF_SELECTBESTCOMPATDRV.
  #W059 selection best compatible driver failed. Error 0xe0000228: there is no compatible driver for this device.
  #W157 default Installer failed. Error 0xe0000228: there is no compatible driver for this device.
  #I060 set driver selected.
  # 166 device install function: DIF_INSTALLDEVICE.
  #I125 installing NULL driver for "PCI VEN_8086 & DEV_24D5 & SUBSYS_A0021458 & REV_02\3 & 13C0B0C5 & 0 & FD.
  #E122 device failed. Error 0xe0000219: the installation failed because a function driver was not specified for this device instance.
  #E157 default Installer failed. Error 0xe0000219: the installation failed because a function driver was not specified for this device instance.
  # 166 device install function: DIF_INSTALLDEVICE.
  #I125 installing NULL driver for "PCI VEN_8086 & DEV_24D5 & SUBSYS_A0021458 & REV_02\3 & 13C0B0C5 & 0 & FD.
  Device #I121 of ' PCI VEN_8086 & DEV_24D5 & SUBSYS_A0021458 & REV_02\3 & 13C0B0C5 & 0 & FD ' completed successfully.
  [01/07/2012 07:46:58 296.1093 driver Install]
  # 019 Searching for hardware ID: PCI VEN_8086 & dev_24d4 & subsys_24d21458 & rev_02, PCI VEN_8086 & dev_24d4 & subsys_24d21458, PCI VEN_8086 & dev_24d4 & cc_0c0300, PCI VEN_8086 & dev_24d4 & cc_0c03
  # 018 search compatible ID: PCI VEN_8086 & dev_24d4 & rev_02 PCI VEN_8086 & dev_24d4, PCI VEN_8086 & cc_0c0300, PCI VEN_8086 & cc_0c03, PCI VEN_8086, pci\cc_0c0300, pci\cc_0c03
  # 199 Executing "C:\WINDOWS\system32\setup.exe" with the command line: setup - newsetup
  #I022 found "PCI\CC_0C0300" in C:\WINDOWS\inf\usbport.inf; Feature: "Standard universal PCI to USB Host Controller"; Pilot: "Standard universal PCI to USB Host Controller"; Supplier: "Microsoft." MFG: "(contrôleur d'hôte USB Standard)"; " Section name: "UHCI. Dev»
  #I023 actual installation section: [UHCI. Dev.NT]. Rank: 0 x 00002005. Effective driver date: 01/07/2001.
  Found #I022 "PCI VEN_8086 & DEV_24D4" in C:\WINDOWS\inf\usbport.inf; Feature: "Intel (r) 82801EB USB Universal Host Controller - 24-4; Pilot: "Intel (r) 82801EB USB Universal Host Controller - 24-4; Supplier: "Microsoft." MFG: "Intel." Section name: "UHCI. Dev»
  #I023 actual installation section: [UHCI. Dev.NT]. Rank: 0 x 00002001. Effective driver date: 01/07/2001.
  # 166 device install function: DIF_SELECTBESTCOMPATDRV.
  #I063 Selected driver installs from section [UHCI. Dev] in 'c:\windows\inf\usbport.inf '.
  #I320 of the remains of the device class GUID: (36FC9E60-C465-11CF-8056-444553540000).
  #I060 set driver selected.
  Best selected #I058 driver compatible.
  #-124 making copies only the installation of ' PCI VEN_8086 & DEV_24D4 & SUBSYS_24D21458 & REV_02\3 & 13C0B0C5 & 0 & E9.
  # 166 device install function: DIF_INSTALLDEVICEFILES.
  #W383 'LAYOUT. PNF"migrates: PNF language = 0409, Thread = 0809.
  # 011 installation section [UHCI. Dev.NT] of "c:\windows\inf\usbport.inf".
  [01/07/2012 08:07:24 296,1]
  # 199 Executing "C:\WINDOWS\system32\setup.exe" with the command line: setup - newsetup
  #W383 'syssetup. PNF"migrates: PNF language = 0809, Thread = 0409.
  REGISTERDLLS #-290 processing section [CryptoDlls]. Binary: '% 11%\rsaenh.dll', flags: 0x0001, time-out: 60 years.
  #W374 digital signature verification has been ignored for a saved file ("C:\WINDOWS\system32\rsaenh.dll").
  REGISTERDLLS #-290 processing section [CryptoDlls]. Binary: '% 11%\dssenh.dll', flags: 0x0001, time-out: 60 years.
  #W374 digital signature verification has been ignored for a saved file ("C:\WINDOWS\system32\dssenh.dll").
  REGISTERDLLS #-290 processing section [CryptoDlls]. Binary: '% 11%\initpki.dll', flags: 0x0001, timeout: 600 s.
  #W374 digital signature verification has been ignored for a saved file ("C:\WINDOWS\system32\initpki.dll").

  I tried the repair after installing XP Pro on a drive using the old PC, and then put this HARD drive in the defective PC.

  Yes, you can not install Windows on a hard disk on a computer then put the hard drive in another computer and loading Windows. This will simply not work.

  The offer for the family image of Windows XP Edition is for you to use as nothing more than a test to see if there might be a problem with your drive. As Vista installs without problem, I wonder if it could be a driver problem. It is also attested by the fact that the complete repair facility.  I'll do more research and after return.

  With respect to the loading of the log file, downloads are not allowed on MS Answers. You must use a host like Mediafire or similar file. Please do so in the future if we need to review the log files. This avoids long threads.

• driver pci HP 430

  Hello

  Can you give me a link for hp 430 pci driver, so that download this software... Help someone?

  Hello:

  Here is the link for the card reader driver that installs the PCI device.

  http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?sp4ts.oid=5086734&spf_p.tpst=swdMain&spf_p.prp_swdMain=wsrp-navigationalState%3Didx%253D%257CswItem%253Dob_93202_1%257CswEnvOID%253D4059%257CitemLocale%253D%257CswLang%253D%257Cmode%253D%257Caction%253DdriverDocument&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken

• R310 Dell: What do the unknown fans with PCIe cards?

  Hello

  I'm looking to replace my aging modified PE2950 gen 3 with a server that is more effective, while maintaining 2 power PCIe slots.

  My use case is not particularly normal in that it's for a home installation and the server will be install re-usable to serve my ad and TVServer for home.  Therefore, I need to be able to add two DVB - S2 cards on the chassis to receive satellite service.

  I know that with some other manufacturers, installation unknown PCIe cards cause their fans go nuts as they assume that the maps are overheated.  How Dell servers in this situation, in particular the R310?  The R310 seems to satisfy all my needs and I think it would be perfect.

  In addition, until I removed the Perc 6 / I of my R410 it was quite noisy, how the R310 Dell price for the fan noise?  The system, with all remains will be in the basement in a rack Assembly away from the living areas. I think I could deal with what up to all about 60dba but especially because it would be too noisy... I understand that 1u rack systems are not designed to be quiet around but a few real comments here would be great.

  Any help that you can provide, or direction is appreciated.

  Thank you very much

  Chris

  Hello

  Bernos

  I know that with some other manufacturers, installation unknown PCIe cards cause their fans go nuts as they assume that the maps are overheated.  How Dell servers in this situation, in particular the R310?

  PCIe cards unknown/3 rd party causes servers 13 g and likely all generations run fans to its maximum SPEED, regardless of the temperature. To my knowledge, it is new with our servers to 13g. I don't think previous generations like 11g detected what exactly was settled in the PCIe slots. They changed fan thresholds based on whether or not the slots have been filled not based not what was in the slot.

  I can't say with certainty what will be the decibels. We do not have a list of all the possible configurations and the decibels. The highest specified configuration in my Datasheet does not include additional PCIe cards, but the dBA listed under stress with this population is 43. I can't guarantee that the system will operate less than 60 dBA, but I suspect that it will do so.

  Thank you