Or I guess if I get windows to work w/my network card, I could do just do a samba share to a different pc on the lan and use the windows "map drive" feature.
I think Windows works/routes via the Qemu virtual network and the Qemu emulated NIC/network_card.
Using Qemu's NAT and DNS and DHCP server these get the Windows (through the mentioned emulated NIC) over/onto the real NIC that's configured and working in Slackware. And, from here, for the Windows it's now onto anywhere where Slackware can go to. (except for the need for Samba due to we have a heterogenous network here) (Samba needed if want to share files between Slackware and the Windows running in Qemu).
(from a magazine article, perhaps Linux-Magazine) When Qemu is (importantly) *not* running, you can mount the image to your Linux file system and copy files either to or from the image -- then umount the image then launch Qemu and you now can see/use these copied files in Windows.
I installed Win 2K in Qemu using on Win 2K the fat32 file system which if you want to copy files in this (the above) manner (I'm not certain but) it may require fat32 on Win due to the Linux limited support for NTFS
At the next, you must add a line to fstab like my very last line from my fstab file (win2k.img line) -- then can mount/umount the image.
al@AB60R:~$ cat /etc/fstab
/dev/sda5 swap swap defaults 0 0
/dev/sda3 / reiserfs defaults 1 1
/dev/sda1 /boot ext2 defaults 1 2
/dev/cdrom /mnt/cdrom auto noauto,users,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,users 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
/dev/sdb5 /mnt/usbhd ext3 noauto,users,rw 0 0
tmpfs /dev/shm tmpfs defaults 0 0
/home/al/images/win2k.img /mnt/win2k vfat rw,user,loop,noauto,offset=32256 0 0
al@AB60R:~$ mount /mnt/win2k
al@AB60R:~$ umount /mnt/win2k
Since then, I've recently learned how to get the networking operational in Qemu. It's easy. Samba, running on Slackware, provides the medium (which is the Samba or smb file sys) with which files can be network shared back and forth between Slackware and the MS_Win running in Qemu. (part of this is a virtual network that's within Qemu) which it appears that the Win OS in Qemu sends/receives data packets through the Qemu emulated NIC and that these data packets get NAT (forwarded) by Qemu's NAT (network address translation or forwarding which is also sometimes A.K.A. masquerade) forwarded evidently to your real NIC that Slackware uses.
(I guess a real NIC is required and also for it to be an operational NIC for Slackware). No problem for me. I'm always networking computers. The difference now for me is that Qemu is a recent first for me in the *virtual/emulated* of network whereas before I always had *real* network hardware and *real* networks connecting machines.
It still sounds funny to me ie "emulated" NIC, virtual ( as in *not a real* ) network. But the kicker is *it_works!!!* just as if it were a *real* network!!! So, this is a case where virtual is good enough 'cause all I need is for it to work!!
BTW my LAN is 192.168.1.xxx
Internet access is through my LAN (gateway IP is: 192.168.1.254) which is the (LAN side) IP address of my 2wire DSL firewall/gateway device (sbcglobal.net which is now ATT provider). (dynamic IP on internet side of the 2wire).
Win 2K running in Qemu has all LAN/network/internet access!! Through Samba, such Win 2K can access a share on (Qemu's host OS) Slackware. Through the (Qemu's) NAT and DNS (I don't know if Samba is needed for this, maybe not needed here) such Win 2K (using its virtual) accesses my real LAN and real internet gateway and onto the internet.
Yes, I much prefer to share files via Samba and a share on Slackware. It's *Much* more convenient than the cumbersome mount the image method that I enclosed up above.
There's screenshots from two months ago when I first installed Qemu. Slackware with KDE desktop. Includes installing Win 2K in Qemu. Also then installing and using several Win softwares onto/with Win 2K. All of this is on top of (the host OS) Slackware with KDE desktop.