search for: oem2

...ff0012):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"; "DeviceIds"; guid ] in > + match Windows.get_node g root path with > + | None -> > + error (f_"cannot find HKLM\\SYSTEM\\DriverD...

...let scsi_adapter_guid = "{4d36e97b-e325-11ce-bfc1-08002be10318}" in - (* There should be a key - * HKLM\SYSTEM\DriverDatabase\DeviceIds\<scsi_adapter_guid> - * We want to add: - * "oem1.inf"=hex(0): - * but if we find "oem1.inf" we'll add "oem2.inf" (etc). - *) - let oem_inf = - let path = [ "DriverDatabase"; "DeviceIds"; scsi_adapter_guid ] in - match Windows.get_node g root path with - | None -> - error (f_"cannot find HKLM\\SYSTEM\\DriverDatabase\\DeviceIds\\%s in the guest registry&qu...

...ago. My other services seem to work fine, but I cannot access the samba server. Server is a Dual PII 300, 128M RAM, multiple SCSI disks, NFS exported, light load, X is not running (but it is running xmms remotely). Kernels tried were 2.4.0 and 2.2.18 with the same results. Clients: Windows 95 OEM2 in vmware, Win2K SP1 on real hardware. Initially, I copied the setup from the older box (which had 2.0.7 on it), to the new server, added a few new shares, then restarted samba. I can access using smbclient -L <server name> and all seems OK. My vmware Win95 box (which could connect to the...

...,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"; "DeviceIds"; guid ] in > > + match Windows.get_node g root path with > > + | None -> > > + error (f_"can...

Is there a little setup display right on the box? Just asking because I have seen that on some boxes. Cheers, Boris. On Sun, Sep 18, 2016 at 12:15 AM, Keith Keller < kkeller at wombat.san-francisco.ca.us> wrote: > On 2016-09-17, Alice Wonder <alice at domblogger.net> wrote: > > > > Okay if it requires DHCP this might be out, I'm currently out of town > >

...) @ 0x000f8700 (XEN) ACPI: RSDT (v001 PTLTD RSDT 0x06040000 LTP 0x06040000) @ 0x37ea2f17 (XEN) ACPI: FADT (v004 UNISYS ZORRO 0x06040000 PTL 0x00000008) @ 0x37ede144 (XEN) ACPI: OEM1 (v001 UNISYS OEM1 0x06040000 LTP 0x06040000) @ 0x37ede238 (XEN) ACPI: OEM2 (v001 UNISYS OEM2 0x06040000 LTP 0x06040000) @ 0x37ede268 (XEN) ACPI: WSPT (v001 UNISYS WSPT 0x06040000 LTP 0x06040000) @ 0x37edee64 (XEN) ACPI: SRAT (v001 UNISYS SRAT 0x06040000 LTP 0x06040000) @ 0x37edee8c (XEN) ACPI: MADT (v001 PTLTD APIC 0x06040000 LTP 0x06040000) @ 0x37ede...

Hi there, SUSE ships Virtual Machine Driver Pack for the virtio windows drivers. Get v2v and customize to discover them and use them if available. Cédric Bosdonnat (7): v2v: check next free oem%d.inf in /Windows/Inf v2v: extract controller offset discovery as a function customize: add support for pvvxsvc v2v: extract reusable parts of viostor regedits v2v: adapt the subkey in Enum

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