-->
- Oem Capture Software
- Video Capture Software
- What Is A Capture Device
- Oem Driver Download
- Oem Capture Utv 007 Software
A common deployment scenario is to capture a single Windows image from a reference computer and then apply the image to a group of destination computers that have identical hardware configurations.
This is a tutorial on how to properly install the Windows 7 and Vista drivers for the Easycap video capture device. Downloads: Windows 7 Drivers: http://www. EasyCAP drivers for Windows 8, 8.1 and 10. All links have been updated. The EasyCAP converts an RCA or S-video source into a USB video and audio capture device – known as a Sound, video and game controller device in Windows – the possibilities for connecting analog sources to a Windows machine are endless and it’s priced insanely cheap.
To save time during installation and to speed up the out-of-box experience (OOBE) for end users, you can instruct Windows Setup to maintain the driver configurations from the reference computer as part of the Windows image. You should do this only when the hardware on the reference computer and the hardware on the destination computers are identical. When you do this, Windows Setup maintains driver configurations during image capture and deployment.
Instructing Windows Setup to Maintain Driver Configurations
Before you capture an image, generalize the computer by using an answer file that instructs Windows Setup to maintain the driver configurations.
To maintain driver configurations by using an answer file
- On your technician computer, open Windows System Image Manager (Windows SIM). Click Start, type Windows System Image Manager, and then select Windows System Image Manager.
- Create a new answer file, or update an existing answer file. For more information, see Create or Open an Answer File and Best Practices for Authoring Answer Files.
- Add the Microsoft-Windows-PnpSysprep/PersistAllDeviceInstalls setting. For more information, see the Overview section in this topic.
- If the computer has undetectable hardware, include the Microsoft-Windows-PnpSysprep/DoNotCleanUpNonPresentDevices setting. For more information, see the Undetectable hardware section in this topic.
- Generalize the computer by using the answer file. For example:
Overview
The Windows in-box driver packages include device drivers that support a wide variety of popular hardware. If your specific hardware requires additional device drivers to boot, you can preinstall additional device drivers on your Windows image. Independent Hardware Vendors (IHVs) often supply these additional device drivers together with their device hardware. For more information about how to add device drivers, see Add a Driver Online in Audit Mode.
To prepare a Windows image for deployment to multiple computers, you must use the System Preparation (Sysprep) tool to generalize the Windows image. Generalizing a Windows image removes the computer-specific information and prepares the device drivers for first boot. This preparation includes these steps:
Browse and view FREE US Geological Survey, US Forest Service, and NRCan topo maps for the US and Canada. Us topo maps free.
Oem Capture Software
- Device state for hardware is removed.
- Boot-critical driver settings are reset to their default values.
- Device log files are deleted.
When you generalize the computer, use an answer file that has the Microsoft-Windows-PnpSysPrepPersistAllDeviceInstalls setting to save time. This setting prevents Windows Setup from removing and reconfiguring the device state for identical hardware. On first boot, the detected device drivers are already preconfigured, potentially enabling a quicker first-boot experience.
Important Avoid using the PersistAllDeviceInstalls setting when the hardware and the hardware configuration on the reference computer are not identical to those of the destination computers. Even seemingly minor differences in hardware or hardware configuration can cause severe or easily overlooked problems. For more information, see the Troubleshooting Hardware Configuration Differences section of this topic.
It's a good practice not to use the PersistAllDeviceInstalls setting on your primary reference image. Instead, for each group of computers that have a different hardware configuration, first load your primary reference image onto a new reference computer that has the planned hardware configuration. Next, capture a new image of this setup and use the PersistAllDeviceInstalls setting.
For more information about how to generalize the Windows image, see Sysprep (Generalize) a Windows installation.
Best Practices for Driver Revisions and Driver Ranking
Don't maintain multiple versions or revisions of the same driver package in the same image. Use offline or online servicing tools to update drivers.
Normally, when Windows Setup boots a computer and multiple versions of a driver package exist on that computer, Setup determines which driver to install by using driver ranking. But when you use the PersistAllDeviceInstalls setting, the normal driver-ranking processes don't occur. So, devices that use outdated drivers may remain installed. For more information about driver ranking, see How Windows Ranks Drivers on MSDN.
If you must add a device driver to an image that uses the PersistAllDeviceInstalls setting, you can update your device drivers by using one of the following methods:
- Use offline servicing tools, like the Deployment Image Servicing and Management (DISM) tool or an unattended answer file. For more information, see Add and Remove Drivers to an Offline Windows Image.
- Use online servicing methods or tools, like an unattended answer file. For more information, see Add a Driver Online in Audit Mode.
Troubleshooting Hardware Configuration Differences
For the PersistAllDeviceInstalls setting to work correctly, the hardware configuration must be identical on the reference computer and on the destination computers. Hardware configuration includes the following components:
- Hardware make and model.
- Firmware. Updates, revisions, and configuration differences can cause some devices to report different criteria for matching device drivers or to use different resources. For example:
- Peripheral Component Interconnect (PCI)–based devices can embed different subsystem revision numbers in their reported hardware IDs.
- BIOS revisions can change the Advanced Configuration and Power Interface (ACPI) namespace. This causes Windows Setup to report existing devices differently or to introduce existing devices as new devices.
- BIOS system configuration differences can cause system devices to claim different memory, I/O, direct memory access (DMA), or interrupt request (IRQ) resources.
- Physical location. Hardware configurations must use the same slot, port, or socket numbers to connect to external devices. For example:
- PCI expansion cards must be inserted in the same slot numbers.
- USB devices must be connected or wired to the same port numbers on the same USB host controllers and integrated hubs.
- Storage devices must be connected to the same storage controllers and channels.
Low-risk, medium-risk, and high-risk differences in hardware configuration
When you use the PersistAllDeviceInstalls setting, any hardware differences can potentially cause problems. But some differences are more likely to cause problems than others.
Low-risk differences
For the following types of hardware differences, you may be able to work around potential driver conflicts and still use the PersistAllDeviceInstalls setting:
- CPU clock speed
- Amount of memory
- Hard disk capacity
- External input devices, like keyboards and mouse devices
- Monitors
Medium-risk differences
For the following types of hardware differences, we recommend that you don't use the PersistAllDeviceInstalls setting:
- Video cards
- Storage drives and media readers, like optical drives and card readers
- Internal or integrated bus devices, like USB or 1394 devices
When these types of hardware differences exist, using this setting may not reduce installation time, even if you work around potential driver conflicts.
Video Capture Software
High-risk differences
For major hardware differences, don't use the PersistAllDeviceInstalls setting. These differences include:
- Motherboard chipset or CPU brand
- Storage controllers
- Form-factor differences, like a change from a desktop to a laptop or from a laptop to a desktop
- Keyboard layout differences, like a change from a standard 101-key keyboard to a Japanese 106-key keyboard
- Any other devices that are in the enumeration path of the Windows boot volume
Types of problems that can occur with a hardware configuration change
Even seemingly minor differences in hardware or hardware configuration can cause severe or easily overlooked problems, like these:
- System instabilityOnline makes it possible for anyone to convert Word, Excel, PowerPoint.(doc, xls, ppt.), image formats like TIFF, JPG, HEIC and many other to PDF, PDF/A or Image.No need to install anything on your computer - simply upload the file and select your delivery method.In case you do not need batch capabilities but would like to create PDF or Image files from any Windows application that has a Print menu available, download, install it then open your file and print it to docuPrinter.Want to implement this site on your own internal network or web server?Please contact: sales©neevia¸com. Pdf version 1.4 vs 1.6.
- Inability to use some of the basic or extended functionality of a device
- Extended boot times and extended installation times
- Misnamed devices in the Devices and Printers folder, Device Manager, and other device-related user interfaces
- Severe system problems that leave the computer in a non-bootable state
Hardware configuration differences that can cause system boot failures
When the boot-critical hardware is not identical on the reference computer and destination computers, using the PersistAllDeviceInstalls setting can cause severe system problems that can leave the computer in a non-bootable state.
Boot-critical driver packages can belong to any of the following Windows device setup classes, as identified by the ClassGUID directive in the <Version> section of the .inf files in their driver packages.
System-supplied device setup class | ClassGUID |
---|---|
System | {4D36E97D-E325-11CE-BFC1-08002BE10318} |
Computer | {4D36E966-E325-11CE-BFC1-08002BE10318} |
Processor | {50127DC3-0F36-415E-A6CC-4CB3BE910B65} |
PCMCIA | {4D36E977-E325-11CE-BFC1-08002BE10318} |
HDC | {4D36E96A-E325-11CE-BFC1-08002BE10318} |
SCSIAdapter | {4D36E97B-E325-11CE-BFC1-08002BE10318} |
DiskDrive | {4D36E967-E325-11CE-BFC1-08002BE10318} |
CDROM | {4D36E965-E325-11CE-BFC1-08002BE10318} |
FDC | {4D36E969-E325-11CE-BFC1-08002BE10318} |
FloppyDisk | {4D36E980-E325-11CE-BFC1-08002BE10318} |
Volume | {71A27CDD-812A-11D0-BEC7-08002BE2092F} |
USB | {36FC9E60-C465-11CF-8056-444553540000} |
SBP2 | {D48179BE-EC20-11D1-B6B8-00C04FA372A7} |
1394 | {6BDD1FC1-810F-11D0-BEC7-08002BE2092F} Download 4787 - Pokemon - HeartGold Version ROM for Nintendo DS(NDS) and Play 4787 - Pokemon - HeartGold Version Video Game on your PC, Mac, Android or iOS device! Pokemon heart gold rom download zip. In a small town in this region is born a Pokemon trainer and in the beginning, you chose one of the three Pokemon to start your journey to complete the Pokedex, catalog of pokemon you should catch on your journey and defeat the best Pokemon trainer in Johto and Kanto region. DOWNLOAD Pokemon HeartGold ROM (Direct) PLAY Pokemon HeartGold. Pokemon Heart Gold ROM is one of the amazing NDS ROM hack we have ever seen so far with the addition of some new features and items in the latest version. Download Pokemon Heart Gold Game Zip for free from Pokemon Host which is given by below because it has received so much appreciation in the early days of its release. The main game was. |
Enum1394 | {C459DF55-DB08-11D1-B009-00A0C9081FF6} |
Keyboard | {4D36E96B-E325-11CE-BFC1-08002BE10318} |
Mouse | {4D36E96F-E325-11CE-BFC1-08002BE10318} |
HIDClass | {745A17A0-74D3-11D0-B6FE-00A0C90F57DA} |
Ports | {4D36E978-E325-11CE-BFC1-08002BE10318} |
For more information about these device setup classes, see System-Supplied Device Setup Classes on MSDN.
Undetectable hardware
When you deploy a new computer to an end user, some hardware, like a removable device or a device that has an on/off switch, may not be present or detected during first boot. By default, on first boot, Windows Setup removes the preconfigured device state for undetected hardware.
To deploy hardware that may not be present or detected on first boot, add any applicable device drivers to the reference image, connect or turn on the applicable devices so that Windows can install them, and use the Microsoft-Windows-PnpSysprep/DoNotCleanUpNonPresentDevices setting when you capture the image.
Important Using the DoNotCleanUpNonPresentDevices setting can lead to the unnecessary storage of excess device states and contribute to slower boot times.
Troubleshooting Driver Conflicts
To avoid driver conflicts between independent boot-critical driver packages, the IHV must make sure that each device driver uses different service names, registry key values, and binary file names.
Example of a potential driver conflict
In the following example, a fictitious IHV named Fabrikam produces two types of storage controllers: StandardController and ExtremeController. Fabrikam assumes that only one type of storage controller is installed at a time on a particular computer.
The driver package defines the StandardController and ExtremeController configurations to use the same driver service name, storctrl. The storctrl driver service uses different service settings that change depending on which hardware (StandardController or ExtremeController) is installed. Because both StandardController and ExtremeController use the same service, they cannot coexist.
This sample shows the contents of the driver package file Storctrl.inf:
If StandardController is on the reference computer and its settings are maintained during image capture, the storctrl driver service is preconfigured. If ExtremeController is on the destination computer, Windows may use the preconfigured settings and files that are intended for StandardController. This can cause unexpected results.
The IHV can help resolve the conflict by using one of these options:
- Create separate driver packages that have separate .inf files for each configuration, and import only the required driver package into the Windows image during deployment. For example, split Storctrl.inf into two separate .inf files, one version for StandardController and one version for ExtremeController, and import only the required driver package into the Windows image.
- Create another service in the driver package for each configuration. Give each service a different name (for example, storctrl and storctrlx) and point to a different binary image file (for example, Storctrl.sys and Storctrlx.sys).
Related topics
Active10 months ago
I ordered EasyCap, but it does not work on windows 10. I found driver for windows 10 online, but it didn't work. Someone knows how could I solve this problem? The device is recognized as an audio device also after I installed the driver.Thank you very much.
Gennaro Arguzzi
Gennaro ArguzziGennaro Arguzzi19422 gold badges33 silver badges1717 bronze badges
5 Answers
EasyCAP DC60 Somagic 1c88:0007 / 1c88:003c
There are many different versions of hardware sold under the name of 'EasyCAP'. Some do not store the required firmware in EEPROM but expect the driver to feed the firmware into the USB hardware when inserted. The Somagic 1c88:0007 is one such device (there may be others). Once the firmware is loaded, the device ID changes to 1c88:003c.
The lack of firmware is why “VLC 3.0.4 Vetinari” can work with some EasyCAP hardware (those with built-in firmware) but not others. VLC > Open Media > Capture Device tab > Capture mode only lists DirectShow, “TV - digital”, and Desktop. There is no “USB cam”.
Windows 10 1803's Device Manager shows it under Other devices > Unknown device > Details tab > Device instance path> Value = USBVID_1C88&PID_0007SMBL007. Events tab will list entries such as:Device not migratedDevice installed (smiusbgrabber3f.inf_..Info:Driver Management concluded the process to install driver smiusbgrabber3f.inf_amd64_62fdac16904230b7 for Device Instance ID USBVID_1C88&PID_0007SMBL007 with the following status: 0xE0000234.
The Somagic device driver is installed in C:WindowsSystem32DriverStoreFileRepositorysmiusbgrabber3f.inf_amd64_62fdac16904230b7SmiUsbGrabber3F.sys. Right click the .sys file > Properties. You will note there is no “Digital Signatures” tab. That means it is not “signed” which is required for Windows 10 kernel drivers. Compare this with C:WindowsSystem32driversstorahci.sys which is signed.
You can search to disable Driver Signature Enforcement in Windows 10, but it will make your system less secure / more prone to malware. I’m not even sure if the driver will even work in Windows 10 with Driver Signature Enforcement disabled. It is only marked with Win7-64 on the CD label.
Two places point to the same Microsoft signed driver:
- https://www.driverscape.com/download/sm-usb-007
Driver Version:
1.0.8.28 Release Date: 2011-01-26
File Size: 546.04K
Supported OS: Windows 10 64 bit, Windows 8.1 64bit, Windows 7 64bit
Download https://www.driverscape.com/files/share/3f52a8986e882143628ad42e0a84c0a1.zip
- https://www.driverscape.com/download/sm-usb-007
- TonestarDeluxe 4/17/2017 9:58:25 PM
- Uninstall the unknown device in device manager
- Create a Windows restore point
- Go to http://www.driverscape.com/download/sm-usb-007 and scroll down to the second last driver. Driver details should be:
Driver Version: 1.0.8.28
Release Date: 2011-01-26
File Size: 546.04K
Supported OS: Windows 10 64 bit, Windows 8.1 64bit, Windows 7 64bit - Download the zip file and extract to a folder (virus scan first of course!).
- After the extraction, right click on the SmiUsbGrabber3C.inf file and select install.Your USB Device should be installed and recognised now. You may need to reboot if need be.
Windows 10 1809 (as of 2018-11-18) did not complain about the digital signature, but it complained about the Widows 95 era *.INF file and not being able to migrate the driver. Perhaps an older version of Windows 10 may work (until Microsoft pushes it to update).
Ubuntu 18.04.1 information about the EasyCAP device I bought via eBay:
$ sudo lsusb -d 1c88:0007 -vBus 003 Device 011: ID 1c88:0007 Somagic, Inc. SMI Grabber (EasyCAP DC60+ clone) (no firmware) [SMI-2021CBE]Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x1c88 Somagic, Inc. idProduct 0x0007 SMI Grabber (EasyCAP DC60+ clone) (no firmware) [SMI-2021CBE] bcdDevice 1.00 iManufacturer 1 Somagic, Inc. iProduct 2 SM-USB 007 iSerial 3 SMBL007 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 18 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 200mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 1Device Status: 0x0000 (Bus Powered)
Unfortunately, Linux support for this device is complicated to set up:
rcpa0rcpa0
As Phil's answer mentions, EasyCap does not need a driver if used with the free VLC player. Let me elaborate.
What Is A Capture Device
- Once you open VLC, you click on the media tab.
- Click open capture device.
- Select USB cam and USB mic.
- Then hit play
22.2k1414 gold badges5656 silver badges8989 bronze badges
Arcade EraArcade Era
I have sympathy with this problem and it took me ages to resolve. Even tried the remove / you name it solutions but narra.
There is a driver available on the following website:https://visser.io/2015/06/easycap-drivers-for-windows-8-1/
The driver file at the bottom to download is:EasyCap_W7_W10_x64.zip
Problem solved.
If it works for you, please let me know?
Mike HeynsMike Heyns
It's not the drivers I finally figured it out. It's the usb cable that comes with it. The usb cable that attaches to it and then you plug the other end to the computer .it is thin and cheaply made. Get your self a top of the line usb cable and you are good to go.I had one lying around my home and tried it and it works great. I thought it was the driver for a long time until it hit me try a quality usb cable. That is it just purchase a quality top of the line usb cable and your good to go. Post if it works for you. Take care
user711143user711143
EasyCap does not need a driver if used with free VLC Media Player https://www.videolan.org/vlc/index.html.
PhilPhil
protected by Community♦Oct 10 '18 at 17:50
Oem Driver Download
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
Would you like to answer one of these unanswered questions instead?