I'm trying to get win98se set up under suse 10.1.
I'm running w98se just fine under suse 9.0, using win4lin - no problems whatsoever.
However, win4lin don't supply the kernel that'd work with suse 10.1 ... and they don't answer my emails as to why I can't access their forum, despite them having approved my password a year or more ago. Can't ask any questions in the relevant forum? That sucks.
So mookie said, on JR's blog, to try vmware. They have something free of charge, but I went the easy route and downloaded vmware workstation 5.5.2, which includes support for suse 10.1. (And comes with a free 30 day trial). (And for which a very good howto is available).
After a few frustrates (clicky in that virtual windows window, then press F2) (and be very fast about it: that particular chance runs away quicker than you can say "not again! ... refresh that guest window, again, and try to be faster the next time around), set the "bios" to boot from CD and/or HD (instead of the floppy that the laptop doesn't sport at all at all), and proceed to set up windows. Piece of cake.
Except ... I don't want to have my files in a cryptic 2-gigabyte file (that's the virtual HD, or, if you have several, it's part of a virtual HD) that only vmware can access. So set the thing to share folders ... clicky in windows explorer, see if there's anything new (besides C: (which to linux is that cryptic 2-gigabyte thingy) and D: (which is the CD drive)) - nada. Try network neigborhood, nada. Reboot the virtual machine, check again, nada.
Read the documentation, bingo: only win2000, win server 2003 (whatever that is), win NT 4, or win XP can read those shared folders.
Try, try again. To get ideas I sent this problem to two newsgroups I frequent. One of them came back with "why don't you try xen? That's included in your distro...".
Right then, run yast to set up the xen server ("system -> xen virtualization"), reboot into suse-with-xen-server, and try to find a way to set up windows under xen, using all (really. I tried all of them, one after the other) the various options under that same yast -> system -> xen server.
The bloody thing wants a kernel to boot into. Can you say "bloody stupid idea"? I know that I can. Here, like this: "Bloody stupid idea!".
No, I want the xen server to boot into the windows CD in order to set that up as my guest OS, and that means that there is no bloody kernel for it to boot into. Just a "setup.exe", if you please. Nor is there an initrd file, thanks anyway for requiring that, too.
There are no how-tos for any other virtualizations (with windows as a guest OS, that is), and there are no ready-made win98se files for xen. At all at all.
So it's back to the drawing board. Any suggestions?