RE: [OT] Call to arms...so to speak
Win4Lin provides kernel hooks that make the kernel looks like its actually a
copy of dos to windows 9x. So by installing a patched kernel windows can run
natively against it - when I used to use it its was significantly faster,
and more reliable than simply installing windows 98se onto the same box.
The advantage this has over vmware et. al. is that there is no virtual
hardware required, therefore the app you are using performs pretty much as
any other app on linux.
The downside (and why I had to go to vmware) is that I had to run server
2003 and XP, so win4lin was no longer an option.
As for running ie - While you can use either of the above, you can't (as I
recall) operate individual apps outside of the windows 'desktop' AND you
have to fully install windows. To get ie working on my underpowered laptop
(for web testing mainly) I purchased a CrossOver wine license. It also
allows me to use flash and Microsoft access, the latter being an
occupational requirement, er hazard.
Glenn
-----Original Message-----
From: Roberto C. Sanchez [mailto:roberto@familiasanchez.net]
Sent: Tuesday, 22 February 2005 11:36 AM
To: debian-user@lists.debian.org
Subject: Re: [OT] Call to arms...so to speak
Pollywog wrote:
> On 02/22/2005 12:18 am, Roberto C. Sanchez wrote:
>>Sorry for replying to myself, but I forgot to mention that could use
>>bochs, qemu, win4lin or VMWare to run Windows within Linux and then
>>run IE inside of that. Though, from the tone of your other messages, I
>>am guessing that is not the solution you were looking for :-)
>
>
> I use Win4Lin in part to deal with this problem of commercial websites
(such
> as banks and government) that are viewable or usable only with IE.
>
How does that work out? I have used VMWare in the past (at a lab where
I did reasearch) and recently started using qemu. VMWare had good
performance. I was even able to simultaneously run 4 or 5 VMs on a
machine with an Athlon XP 1800+ and 512 MB RAM. qemu is very easy to
get up and running, but it is a real resource hog.
That is not a slight agains qemu, rather it is caused by the differing
philosophies (VMWare does vitualization and executes mostly directly on
the host CPU and only handles x86, where qemu is an emulator that can
emulate x86, x86_64, Sparc, etc.).
I am just wondering where Win4Lin fits into the batch.
--
Roberto C. Sanchez
http://familiasanchez.net/~sanchezr
Reply to: