qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug 1889421] [NEW] VVFAT is not writable from Windows NT 3.5, 3.51 and


From: pts
Subject: [Bug 1889421] [NEW] VVFAT is not writable from Windows NT 3.5, 3.51 and 4.0
Date: Wed, 29 Jul 2020 13:50:28 -0000

Public bug reported:

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?

** Affects: qemu
     Importance: Undecided
         Status: New

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/bugs/1889421/+attachment/5396980/+files/qemu_vvfat_windows_nt.png

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1889421

Title:
  VVFAT is not writable from Windows NT 3.5, 3.51 and 4.0

Status in QEMU:
  New

Bug description:
  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?

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1889421/+subscriptions



reply via email to

[Prev in Thread] Current Thread [Next in Thread]