Don’t know - looking for advice here. If it is a tar file masquerading as a floppy disk image then creating a blank raw image and copying it over will produce exactly the same image, wouldn’t it?
Perhaps someone in this mailing list has installed Xenix 386 with devsys floppy images and can guide me on how to do this? Thanks Supratim --- Supratim Sanyal, W1XMT 39.19151 N, 77.23432 W QCOCAL::SANYAL via HECnet > On Oct 29, 2019, at 4:57 AM, Pascal <[email protected]> wrote: > > hi, > if you do tar tvf on your .img file, then this file is not a disk image, but > a tar file ? > >> Le mar. 29 oct. 2019 à 04:15, Supratim Sanyal <[email protected]> a écrit : >> Hi all, >> >> I have a basic XENIX 2.3.4 installation running great under qemu-system-i386 >> version 3.1.1/FreeBSD 12-RELEASE. >> >> I recently obtained XENIX devsys 1.2MB floppy disk images and am a bit stuck >> trying to get QEMU to present 5.25" 1.2MB floppies to the XENIX guest. The >> "change floppy0" monitor command is accepted, but the "custom" XENIX >> installation script is unable to read the inserted floppy. >> >> (qemu) change floppy0 "SCO XENIX Development System 2.3.0d Disk 1.img" >> (qemu) info block >> ide0-hd0 (#block168): ./Xenix386-2.3.4-200MB-Disk1.qcow2.disk (qcow2) >> Attached to: /machine/unattached/device[23] >> Cache mode: writeback >> >> ide1-cd0: [not inserted] >> Attached to: /machine/unattached/device[24] >> Removable device: not locked, tray closed >> >> floppy0 (#block334): SCO XENIX Development System 2.3.0d Disk 1.img (raw) >> Attached to: /machine/unattached/device[16] >> Removable device: not locked, tray closed >> Cache mode: writeback >> >> sd0: [not inserted] >> Removable device: not locked, tray closed >> >> But, inside XENIX, on running "custom" -> option 4 (add supported product): >> >> fd: ERROR: error on dev floppy (2/64), block=0 cmd=00000003 status=00000002 >> >> Error: incorrect volume in drive >> >> The floppy images are: >> >> 1228800 Feb 25 2012 SCO XENIX Development System 2.3.0d Disk 1.img >> 1228800 Feb 25 2012 SCO XENIX Development System 2.3.0d Disk 2.img >> 1228800 Feb 25 2012 SCO XENIX Development System 2.3.0d Disk 3.img >> 1228800 Feb 25 2012 SCO XENIX Development System 2.3.0d Disk 4.img >> 1228800 Feb 25 2012 SCO XENIX Development System 2.3.0d Disk 5.img >> 1228800 Feb 25 2012 SCO XENIX Development System 2.3.0d Disk 6.img >> >> and I can untar the floppies on the FreeBSD host: >> >> $ tar tvf Development\ System\ 2.3.0d\ Disk\ 1.img ### on FreeBSD Host >> -r--r--r-- 0 0 0 0 Dec 14 1988 >> ./tmp/_lbl/prd=xds/typ=n386/rel=2.3.0d/vol=D01 >> -rw-r--r-- 0 3 3 21289 Dec 14 1988 ./etc/soft.perms >> -rw-r--r-- 0 3 3 0 Dec 14 1988 ./etc/perms/soft link to >> ./etc/soft.perms >> -rw-r--r-- 0 3 3 181 Aug 16 1988 ./usr/lib/help/yacc >> -rw-r--r-- 0 3 3 165 Aug 16 1988 ./usr/lib/help/xstr >> ... >> ... >> -rw-r--r-- 0 3 3 138086 Nov 7 1988 ./usr/lib/dos/Cdlibc.a >> -rw-r--r-- 0 3 3 122 Nov 7 1988 ./usr/lib/dos/binmode.o >> -rw-r--r-- 0 3 3 0 Nov 7 1988 ./usr/lib/dos/rawmode.o link >> to ./usr/lib/dos/binmode.o >> -rw-r--r-- 0 3 3 580 Oct 27 1988 ./usr/lib/help/un >> >> My command line to lauch the emulator: >> ./qemu-system-i386 -L pc-bios -m 16 -net nic,model=ne2k_isa -net >> tap,ifname=tap5,script=no -hda ./Xenix386-2.3.4-200MB-Disk1.qcow2.disk >> -nographic -accel tcg,thread=multi -vga std -vnc :3 -monitor >> telnet::54323,server,nowait -serial mon:stdio >> >> If it is a volume label issue, how does one specify the volume label for a >> raw floppy image ? Or is it something else like trying to read a 1.2MB >> floppy in a 3.5" 1.44MB QEMU-emulated floppy disk drive? Any help or >> pointers welcome. >> >> A couple of screen-shots are attached. >> >> Thank you. >> >> Supratim >> >> >> >> -- >> Sent via Thunderbird/MX-Linux on an overheated Compaq Presario CQ61
