Re: win4lin howto
On Wed, 2004-06-02 at 22:52, glenn wrote:
> Hi Robert
> Try this:
> https://www.netraverse.com/member/downloads/misc.php
> 7th-11th from bottom
>
> Glenn
> On Thu, 2004-06-03 at 15:22, Rodney D. Myers wrote:
> > On Thu, 03 Jun 2004 15:13:38 +1000
> > glenn <gdavy@tpg.com.au> wrote:
> >
> > > Makes sense. Well I never wrote a HOWTO, but I can give you vague
> > > memories :-)
> > > I've installed win4lin on very old suse, rhat, mandrake and debian -
> > > all by 'manually' applying kernel patches, which was a first for me -
> > > thats the worst case scenario, and it works out well.
> > >
> > > Debian isn't officially supported so there was no easier option for
> > > quite a while with debian, but since kernel 2.2 there has been kernel
> > > patches for the debian kernel specifically. Once you register with
> > > their site (which may or may not involve purchasing the product,
> > > don't recall) you can get to the misc downloads section, where you can
> > > download some .deb files. Be sure to get the correct ones for your
> > > kernel. I never used it beyond kernel 2.4.18 so I don't know how it
> > > goes on 2.6 kernels ( I use vmware now).
> > >
> > > Debian uses some tricky kernel patch management thingy which makes
> > > everything much easier and more orderly for applying special patches
> > > (e.g if you install the nvidia patches with aptitude, you'll see an
> > > example of what I mean). The .deb 2.4>5 patches on the win4lin site
> > > work with in this debian framework as I recall.
> > >
> > > Its all quite feasible - give it a whirl
> > >
> > > BTW did you give wine or crossover a try
> > >
> > >
> > >
> > >
> > > On Thu, 2004-06-03 at 13:18, Rodney D. Myers wrote:
> > > > On Thu, 03 Jun 2004 13:07:20 +1000
> > > > glenn <gdavy@tpg.com.au> wrote:
> > > >
> > > > > How far have you got?
> > > > > Have you got the debian win4lin patches from the misc downloads
> > > > > section on the win4lin site?
> > > > > Glenn
> > > > > On Thu, 2004-06-03 at 12:23, Rodney D. Myers wrote:
> > > > > > I've searched through the archives, and i don't see any mention
> > > > > > of a how to.
> > > > > >
> > > > > > Does anyone here, on the list, have a HOWTO written for getting
> > > > > > Win4Lin patched into the kernel, and getting things installed?
> > > > > >
> > > > > > I'm trying to dump my windos machine, but I need 7-10 programs
> > > > > > (HAM radio programming software) that only run under windos.
> > > > > >
> > > > > > Thanks
> > > >
> > > > To be honest. I haven't grabbed any software. I was looking for
> > > > someones else documentation to read through before I started
> > > > grabbing stuff. On dialup, it's kind of slow. I want to make sure I
> > > > know what I need, before I start downloading anything.
> > > >
> > > > Hope that makes sense.
> > >
> > >
> >
> > Been through the Netraverse web site, but have seen no *.deb files, and
> > I have registered when I was running RH 7.3..
> >
> > Wine won't work for some of the programs.
> >
> > Thanks
>
Interesting, I never found any deb files on the netraverse site before.
Never thought of going through the login process - there's quite a few
files I never realized were available.
As for installing win4lin on a debian system, I've installed it on my
system with kernel 2.4.22. The procedure I followed was (warning - this
is from memory):
- Installed source package for kernel-source-2.4.22 using dselect
- Downloaded netraverse mki-adapter.patch
- Downloaded netraverse Kernel-Win4Lin3-2.4.22.patch
- Followed netraverse instructions for applying patches to a generic
kernel.
- Followed debian instructions for configuring and making a kernel
(involved running make menuconfig and make-kpkg).
- Installed the resulting kernel-image .deb file using dpkg.
- Checked to make sure that grub had the right boot parameters
- Rebooted into the win4lin enabled kernel.
It worked pretty seamlessly for me. It's not as easy as installing one
of the premade rpms provided by netraverse. The procedure is very
similar to netraverse's procedure for patching generic kernels manually.
Reply to: