similar to: More than 4 serial ports with wine.

Hi Mr newbie here. Using 32-bit Ubuntu 11.10 and Wine 1.3.28. I have installed a Creative PCI Modem and that works well as /dev/modem from things like putty. I've done the link ln -s /dev/modem ~/.wine/dosdevices/com6 so it's now my com6 within wine. However, using teraterm the response from the modem is bitty and slow and pretty useless. If I do something like AT\r the OK\r does come

Hi, I have a bunch of UPSs, most connected to pcs with Linux working 100% with NUT. The only one I have a problem with, is connected to Windows 7 64bit, and I used the straight MSI installed from the website named NUT-Installer-2.6.5-4.msi Took me a while to find a way to get it to work, but it is ugly for now. Just starting up the service results in a NUT not working at all, and I tracked it

How do you go about configuring comm ports in Wine? I have a usb to serial adapter that is using ttyUSB1 under linux. The program I want to use under wine shows only the standard Windows comm ports; i.e, com1, com2, etc. How can I redirect those to ttyUSB1? dick

Ok, so I previously thought I had to use usbhid-ups but when I eventually got it going this is what I got:- This Powercom device (0d9f/0002) is not supported by usbhid-ups. Please use the 'powercom' driver instead. So I switched to the powercom driver, but I have tried a whole bunch of likely suspects for the port setting, none of which have worked Tried so far:- com1 with these

I've tried multiple ways to get into terminal server via WINE, but have had no success. I've got Notes, Service Center, Internet Explorer... pretty much all running smoothly... but when I try to use Internet explorer to get into it, I get a box that is outlined where the desktop is supposed to be (on the IE screen, and an object load error in the IE Log)... I then tried to run mstsc.exe

Hello, I'm new to Wine and I tried to run Pepakura Designer with it. I'm using osx 10.5.8 and I've installed Wine through macports as advised in the download instructions. I downloaded Pepakura Designer 3.0.3a because it was the the most up to version with a decent rating, however I've run into the DIB Init Failed issue: Code: ine Pepakura\ Designer\ 3.exe

Hi, I am new to wine and the list. I am using Wine release 20010112 on a RH7.1 (used supplied RPM) to try and run a program to control a video switcher that doesn't have a linux ported program. The program starts OK but when it scans the com1 to diagnose the switcher, it reports a bad serial port or faulty connection. The utility has no problem under windows. I included a trace using

Hi, Since Sharps communication protocols are "top secret", I'm trying to port their sync software to linux. I'm new to wine, so this might be silly, but after hours of googling and searching for solutions I'm posting this. After installing DCOM98.exe, the Desktop software installed, and it runs. Only problem is it doesn't detect the device connected to the serial port

Hello, everyone - I have an old Windows app - a ship navigation program - that needs to see GPS input on a serial port (it was written in the pre-USB days.) My laptop, however, has no serial ports - but this same program, when run on a friend's Windows box, can read the GPS info from the USB-connected GPS via the "USB-Serial Driver". This is one of the frustrating bits of this

Unfortunately, almost all the Windows programs I want to run under Wine need to access the COM: ports, and I cannot get any of them to run. Typically, I get stuff like this ... fixme:comm:EscapeCommFunction16 no cid=0 found! fixme:comm:EscapeCommFunction16 no cid=0 found! err:comm:COMM16_ReadComplete async read failed 000003e3 fixme:comm:EscapeCommFunction16 no cid=3 found!

I have been investigating pci pass-through for virtualized guests and the documentation I have found seems to me to lack a certain consistency in its example. This may be due to my not understanding what it is trying to inform me. What I wish to do is to configure a pci multi-port serial i/o card for use by a single virtual host. I start by running lspci -v on the host to identify the serial

Hello, I am trying to create a lucid guest VM with a vmchannel between the guest and the hypervisor. Details below: KERNEL: # uname -a Linux saurav-desktop 2.6.38-2-generic #29~lucid1-Ubuntu SMP Mon Feb 7 13:35:14 UTC 2011 i686 GNU/Linux QEMU: # /usr/bin/qemu --version QEMU emulator version 0.13.0, Copyright (c) 2003-2008 Fabrice Bellard LIBVIRT: # /usr/sbin/libvirtd --version

Currently virtio-pci is specified so that configuration of the device is done through a PCI IO space (via BAR 0 of the virtual PCI device). However, Linux guests happen to use ioread/iowrite/iomap primitives for access, and these work uniformly across memory/io BARs. While PCI IO accesses are faster than MMIO on x86 kvm, MMIO might be helpful on other systems which don't implement PIO or

Currently virtio-pci is specified so that configuration of the device is done through a PCI IO space (via BAR 0 of the virtual PCI device). However, Linux guests happen to use ioread/iowrite/iomap primitives for access, and these work uniformly across memory/io BARs. While PCI IO accesses are faster than MMIO on x86 kvm, MMIO might be helpful on other systems which don't implement PIO or

I posted this problem on IRC yesterday. Here are some logs. Recap on the problem: When I do inspect_os() (from the python api) or invoke virt-inspector, I get this error: libguestfs: error: internal_parse_mountable: internal_parse_mountable_stub: /dev/vg_nestedctos1/lv_root: No such file or directory I don't have this problem when I invoke it using the OS supplied binaries (version 1.14.8).

lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.3 LTS Release: 14.04 Codename: trusty guestmount --ro -a agent-disk1.vmdk -i /mnt/vmdk --> Works fine guestmount --rw -a agent-disk1.vmdk -i /mnt/vmdk libguestfs: error: appliance closed the connection unexpectedly. This usually means the libguestfs appliance crashed. See

On (Thu) 12 Jan 2012 [09:20:05], zanghongyong at huawei.com wrote: > From: Hongyong Zang <zanghongyong at huawei.com> > > Virtio-serial set up (max_ports+1)*2 vqs when device probes, but may not all > io_ports are used. > These patches create vqs of port0 and control port when probing the device, then > create io-vqs when called add_port(). Hi, Can you resurrect this

On (Thu) 12 Jan 2012 [09:20:05], zanghongyong at huawei.com wrote: > From: Hongyong Zang <zanghongyong at huawei.com> > > Virtio-serial set up (max_ports+1)*2 vqs when device probes, but may not all > io_ports are used. > These patches create vqs of port0 and control port when probing the device, then > create io-vqs when called add_port(). Hi, Can you resurrect this

On Sun, Mar 23, 2014 at 12:26:28PM +0000, Richard W.M. Jones wrote: > Secondly, we should be able to inspect all Linux guests, including > Tiny Core Linux, but it looks like in this case it is failing. This > is a bug. I had a look at how the Tiny Core Linux ISO is arranged. It loads the main operating system root partition as a single large initramfs, with optional modules loaded

Currently virtio-pci is specified so that configuration of the device is done through a PCI IO space (via BAR 0 of the virtual PCI device). However, Linux guests happen to use ioread/iowrite/iomap primitives for access, and these work uniformly across memory/io BARs. While PCI IO accesses are faster than MMIO on x86 kvm, MMIO might be helpful on other systems: for example IBM pSeries machines not