search for: deviceid

It seems that checking for oem%d.inf in the DeviceIds registry entry doesn't always list all oemXX.inf files. For example we may have oem1.inf free in the registry key, but used in another one. Also extract this into a separate function for later use to setup another driver. --- v2v/windows_virtio.ml | 52 ++++++++++++++++++++++++++-------------...

...et001\Control\Class\<scsi_adapter_guid> > @@ -398,6 +378,28 @@ and add_viostor_to_driver_database g root arch current_cs = > @=hex(ffff0012):6f,00,65,00,6d,00,31,00,2e,00,69,00,6e,00,66,00,00,00 > *) > > +(* There should be a key > + * HKLM\SYSTEM\DriverDatabase\DeviceIds\<guid> > + * We want to add: > + * "oem1.inf"=hex(0): > + * but if we find "oem1.inf" we'll add "oem2.inf" (etc). > + *) > +and set_free_oem_inf g root guid driver_inf driverdir = > + let path = [ "DriverDatabase"; "Device...

On 21 June 2013 19:45, Christopher Covington <cov at codeaurora.org> wrote: > You were proposing to use a valid/existing MagicValue/Version/VendorID with a > special DeviceID that does nothing. I'm saying why not use a valid/existing > MagicValue/Version/VendorID/DeviceID with a special parameter setting, size=0, > that does nothing? Ah, I see. Well, it sounds from your quoted mount message as if they do actually do something (ie the kernel finds a block devi...

On 21 June 2013 19:45, Christopher Covington <cov at codeaurora.org> wrote: > You were proposing to use a valid/existing MagicValue/Version/VendorID with a > special DeviceID that does nothing. I'm saying why not use a valid/existing > MagicValue/Version/VendorID/DeviceID with a special parameter setting, size=0, > that does nothing? Ah, I see. Well, it sounds from your quoted mount message as if they do actually do something (ie the kernel finds a block devi...

On 21 June 2013 19:01, Christopher Covington <cov at codeaurora.org> wrote: > Anyhow, I just did a quick experiment with 0-size block devices, and they seem > to work for me, although trying to mount the device yields the confusing > message, "mount: mounting /dev/vda on mount failed: Invalid argument". I'm confused -- what's the significance of zero size block

On 21 June 2013 19:01, Christopher Covington <cov at codeaurora.org> wrote: > Anyhow, I just did a quick experiment with 0-size block devices, and they seem > to work for me, although trying to mount the device yields the confusing > message, "mount: mounting /dev/vda on mount failed: Invalid argument". I'm confused -- what's the significance of zero size block

...sc% = AX88172.Ndi,USB\VID_0B95&PID_1720 ;**************************************************************** ; Win98 main sections * ;**************************************************************** [AX88172.Ndi] AddReg = AX88172.Reg, AX88172.Con.Reg ;, AX88172.Params DeviceID = USB\VID_0B95&PID_1720 How can I tell if this is a RealTek chipset and more importantly, getting it working?

...8,6 +378,28 @@ and add_viostor_to_driver_database g root arch > > current_cs = > > > > @=hex(ffff0012):6f,00,65,00,6d,00,31,00,2e,00,69,00,6e,00,66,00,00 > > ,00 > > *) > > > > +(* There should be a key > > + * HKLM\SYSTEM\DriverDatabase\DeviceIds\<guid> > > + * We want to add: > > + * "oem1.inf"=hex(0): > > + * but if we find "oem1.inf" we'll add "oem2.inf" (etc). > > + *) > > +and set_free_oem_inf g root guid driver_inf driverdir = > > + let path = [ "Driv...

...false </gbp:retransmission-allowed> <gbp:retention-expiry>2010-11-14T20:00:00Z </gbp:retention-expiry> </gp:usage-rules> <gp:method>802.11</gp:method> </gp:geopriv> <dm:deviceID>mac:1234567890ab</dm:deviceID> <dm:timestamp>2010-11-04T20:57:29Z</dm:timestamp> </dm:device> </presence> --boundary1-- 1. Adding or reading the lines bellow seems easy. How can you add a whole application/pidf+xml section as above eithe...

...tered on major 196 Jul 20 00:50:26 boldsoft kernel: ZapTel device: vendor=e159 device=1 subvendor=8085 Jul 20 00:50:26 boldsoft kernel: wcfxo0: <Wildcard X101P> port 0xe800-0xe8ff mem 0xfaffe000-0xfaffefff irq 18 at device 9.0 on pci2 Jul 20 00:50:26 boldsoft kernel: ZapTel Attach for wcfxo0: deviceID : 0xe159 Jul 20 00:50:26 boldsoft kernel: wcfxo: DAA mode is 'FCC' Jul 20 00:50:26 boldsoft kernel: Found a Wildcard FXO: Wildcard X101P Jul 20 00:50:26 boldsoft kernel: ZapTel device loaded. Jul 20 00:50:33 boldsoft kernel: FXS device: vendor=e159 device=1 subvendor=b100 Jul 20 00:50:33 bo...

...--- alsa-utils-1.0.12-3.fc6 ------- /proc/asound/modules -------- 1 snd_mpu401 ------- /proc/asound/pcm -------- ------- /etc/sysconfig/hwconf -------- - class: OTHER bus: PCI detached: 0 desc: "Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control" vendorId: 1022 deviceId: 1103 subVendorId: 0000 subDeviceId: 0000 pciType: 1 pcidom: 0 pcibus: 0 pcidev: 18 pcifn: 3 - class: OTHER bus: PCI detached: 0 driver: k8_edac desc: "Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller" vendorId: 1022 deviceId: 1102 subVendorId: 0000 subDeviceId: 000...

...--- alsa-utils-1.0.12-3.fc6 ------- /proc/asound/modules -------- 1 snd_mpu401 ------- /proc/asound/pcm -------- ------- /etc/sysconfig/hwconf -------- - class: OTHER bus: PCI detached: 0 desc: "Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control" vendorId: 1022 deviceId: 1103 subVendorId: 0000 subDeviceId: 0000 pciType: 1 pcidom: 0 pcibus: 0 pcidev: 18 pcifn: 3 - class: OTHER bus: PCI detached: 0 driver: k8_edac desc: "Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller" vendorId: 1022 deviceId: 1102 subVendorId: 0000 subDeviceId: 000...

...tered on major 196 Jul 20 00:50:26 boldsoft kernel: ZapTel device: vendor=e159 device=1 subvendor=8085 Jul 20 00:50:26 boldsoft kernel: wcfxo0: <Wildcard X101P> port 0xe800-0xe8ff mem 0xfaffe000-0xfaffefff irq 18 at device 9.0 on pci2 Jul 20 00:50:26 boldsoft kernel: ZapTel Attach for wcfxo0: deviceID : 0xe159 Jul 20 00:50:26 boldsoft kernel: wcfxo: DAA mode is 'FCC' Jul 20 00:50:26 boldsoft kernel: Found a Wildcard FXO: Wildcard X101P Jul 20 00:50:26 boldsoft kernel: ZapTel device loaded. Jul 20 00:50:33 boldsoft kernel: FXS device: vendor=e159 device=1 subvendor=b100 Jul 20 00:50:33 bo...

The way we patch the Windows registry in order to allow it to boot off a virtio-blk drive was initially conceived by comparing the state with virtio-blk driver properly installed, to that without. However, we don't want to replicate the Windows PnP system; rather we need to apply just enough edits to make the system boot, and then let the Windows PnP manager figure out the rest. This series

...XI<foobar>.c man: fix copy/paste errors in XListDeviceProperties. Add XI2 property man pages. man: resurrect XGetDeviceProperty man pages (and associates) Fix typo in Makefile.am, leading to the XI2 source skipping compilation. Hierarchy changes should use "deviceid", not device. man: XIChangeHierarchy uses device ids, not XDevice* Remove CamelCase use from XIChangeHierarchy. Silence warning: missing prototype for copy_classes Rename XICreateMaster to XIAddMaster for consistency. XIHierarchyEvent should list num_info, not num...

...e "/usr/lib/python/xen/xend/XendDomainInfo.py", line 971, in waitForDevic es_ return self.getDeviceController(deviceClass).waitForDevices() File "/usr/lib/python/xen/xend/server/DevController.py", line 135, in waitFo rDevices return map(self.waitForDevice, self.deviceIDs()) File "/usr/lib/python/xen/xend/server/DevController.py", line 151, in waitFo rDevice raise VmError("Device %s (%s) could not be connected. " VmError: Device 0 (vif) could not be connected. Backend device not found. ___________________________________________...

...g voices; the problem comes with speexdec which always crashes when trying to use the sound card. I've worked a bit around it and it crashes always in module wave_out.c. In details, the cause seems to be the use of waveOutOpen function, at line 128: [...] switch ( waveOutOpen ( &dev, deviceID, &outFormat, (DWORD)wave_callback, 0, CALLBACK_FUNCTION ) ) [...] All the parameters seem to have their right values to perform a successfully call. All but the forth: ... (DWORD)wave_callback, ... which seems not to work on my system. If i replace this parameter with a 0 (zero) this call go...

...EnterCriticalSection ( &cs ); @@ -125,7 +125,7 @@ Set_WIN_Params ( FILE_T dummyFile , outFormat.nBlockAlign = (outFormat.wBitsPerSample + 7) / 8 * outFormat.nChannels; outFormat.nAvgBytesPerSec = outFormat.nSamplesPerSec * outFormat.nBlockAlign; - switch ( waveOutOpen ( &dev, deviceID, &outFormat, (DWORD)wave_callback, 0, CALLBACK_FUNCTION ) ) + switch ( waveOutOpen ( &dev, deviceID, &outFormat, (DWORD_PTR)wave_callback, 0, CALLBACK_FUNCTION ) ) { case MMSYSERR_ALLOCATED: return Box ( "Device is already open." ); case MMSYSERR_BADDEVICEID: return...

...ython2.5/site-packages/xen/xend/XendConfig.py", line 895, in to_sxp configs = controller.configurations(txn) File "/usr/lib64/python2.5/site-packages/xen/xend/server/DevController.py", line 229, in configurations return map(lambda x: self.configuration(x, transaction), self.deviceIDs (transaction)) File "/usr/lib64/python2.5/site-packages/xen/xend/server/DevController.py", line 229, in <lambda> return map(lambda x: self.configuration(x, transaction), self.deviceIDs (transaction)) File "/usr/lib64/python2.5/site-packages/xen/xend/server/DevControlle...

Pretty much all games and steam recognize my graphics card as GeForce 83000GS. I think this causes games to run slowly and even freeze/crash when i try to set graphic details to high. Setting VideoMemorySize from registry to the correct amount doesn't help at all. Also setting VideoPciDeviceID and VideoPciVendorID makes things even worse because then it's detected as Direct3D HAL. Is there any way to get wine to detect my video card properly or is this a bug in wine?