1 files changed, 107 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/118/user-level-i386/1889421 b/results/classifier/zero-shot/118/user-level-i386/1889421
new file mode 100644
index 000000000..f005d9046
--- /dev/null
+++ b/results/classifier/zero-shot/118/user-level-i386/1889421
@@ -0,0 +1,107 @@
+i386: 0.935
+x86: 0.902
+user-level: 0.873
+files: 0.858
+graphic: 0.848
+network: 0.834
+architecture: 0.789
+permissions: 0.775
+performance: 0.758
+device: 0.740
+peripherals: 0.720
+semantic: 0.711
+vnc: 0.692
+kernel: 0.684
+ppc: 0.674
+mistranslation: 0.670
+risc-v: 0.657
+virtual: 0.656
+PID: 0.614
+hypervisor: 0.595
+boot: 0.590
+TCG: 0.574
+arm: 0.508
+register: 0.506
+socket: 0.505
+debug: 0.497
+assembly: 0.486
+KVM: 0.472
+VMM: 0.428
+--------------------
+i386: 0.996
+x86: 0.910
+virtual: 0.827
+user-level: 0.341
+TCG: 0.307
+permissions: 0.117
+debug: 0.090
+PID: 0.052
+files: 0.050
+device: 0.029
+socket: 0.026
+semantic: 0.025
+graphic: 0.022
+vnc: 0.018
+boot: 0.017
+network: 0.016
+register: 0.015
+hypervisor: 0.012
+kernel: 0.008
+risc-v: 0.008
+VMM: 0.005
+peripherals: 0.004
+performance: 0.004
+assembly: 0.003
+architecture: 0.003
+ppc: 0.002
+mistranslation: 0.001
+arm: 0.001
+KVM: 0.001
+
+VVFAT is not writable from Windows NT 3.5, 3.51 and 4.0
+
+I'm running Windows NT 3.5, 3.51 and 4.0 in QEMU 4.2.0 on Linux. I'm using a VVFAT filesystem. Command lines:
+
+$ qemu-system-i386 -L pc -cpu 486 -m 64 -vga cirrus -drive file=nt351.img,format=raw -net nic,model=pcnet -net user -soundhw sb16,pcspk -drive file=fat:rw:drived,format=raw
+
+$ qemu-system-i386 --version
+QEMU emulator version 4.2.0 (Debian 1:4.2-6)
+Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers
+
+Creating a new directory or file on drive D: (the VVFAT filesystem) fails on Windows NT 3.5, 3.51 and 4.0 (see screenshot). It succeeds on Windows NT 3.1.
+
+Is there a workaround, e.g. a QEMU flag or a change in the Windows NT driver settings?
+
+
+
+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" within the next 60 days (otherwise it will get
+closed as "Expired"). We will then eventually migrate the ticket auto-
+matically to the new system (but you won't be the reporter of the bug
+in the new system and thus 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.]
+