1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
files: 0.874
peripherals: 0.869
user-level: 0.855
performance: 0.852
virtual: 0.838
device: 0.820
graphic: 0.818
mistranslation: 0.789
architecture: 0.777
semantic: 0.693
network: 0.658
permissions: 0.618
hypervisor: 0.574
socket: 0.573
vnc: 0.535
debug: 0.528
register: 0.513
kernel: 0.512
ppc: 0.494
risc-v: 0.436
PID: 0.431
VMM: 0.405
assembly: 0.378
boot: 0.348
TCG: 0.329
KVM: 0.316
x86: 0.315
i386: 0.282
arm: 0.255
Aten USB to Serial bridge does not work with qemu under Windows 10
I would like to use MSDOS 6.22 with qemu (unfortunatelly lot of our test programs has been written in dos).
I tried to connect two laptop by RS232 port, one of the machine have a built-in serial port and run with native MSDOS 6.22 with 4.0 norton commander. Another machine have only USB ports and i try to use a new Aten USB to Serial device. Ok. Has been started qemu with -serial and -chardev parameters, at startup appear a window with serial port setting such as baud rate, start bit, etc...
Quemu has been satrted succeeded but serial port cannot be used becouse was nothing activited on usb serial adapter :(
I tried same configuration with VirtualBox and everything was worked fine (serial connection was estabiled and copied several files from one machine into another machine), seems to be the emulated serial port has been worked fine.
I would like to use qemu, i just thougt qemu is better, simple and faster...
Exists solution or is this a qemu bug?
Thank you!
I forgot that the environment is Windows 10 64 bit.
Hi again,
Seems to be there is no solution for my problem :(
I have succeeded create NTVDMx64 patch on my Windows 10 installation, so i can run directly 16 bit ms dos applications without any dos emulator.
I take the initiative to close the bug.
Bye
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then please close this ticket as "Fix released".
If it is not fixed yet and you think that this bug report here is still
valid, then you have two options:
1) If you already have an account on gitlab.com, please open a new ticket
for this problem in our new tracker here:
https://gitlab.com/qemu-project/qemu/-/issues
and then close this ticket here on Launchpad (or let it expire auto-
matically after 60 days). Please mention the URL of this bug ticket on
Launchpad in the new ticket on GitLab.
2) If you don't have an account on gitlab.com and don't intend to get
one, but still would like to keep this ticket opened, then please switch
the state back to "New" or "Confirmed" within the next 60 days (other-
wise it will get closed as "Expired"). We will then eventually migrate
the ticket automatically to the new system (but you won't be the reporter
of the bug in the new system and thus you won't get notified on changes
anymore).
Thank you and sorry for the inconvenience.
[Expired for QEMU because there has been no activity for 60 days.]
|