John Dierdorf wrote:
> I just installed Win4Lin 3.0 on my SuSE 7.1 (2.4 kernel) system.
> Unfortunately, Linux now says "VFAT access not compiled in kernel" or
> some such when I try to mount my true Windows partitions. (SuSE
> defaults to putting them at /windows/C, /windows/D, etc. THIS NO
> LONGER WORKS!!!)
>
> Either I screwed up or else the Win4Lin-modified kernel somehow was
> compiled without this essential feature. I'd appreciate either (a)
> advice as to how to fix things, or (b) assurance that a new kernel
> WITH built-in VFAT support will be available soonest. Otherwise
> Win4Lin is completely useless to me, and it's back to the store for a
> refund.
>
> Thanks.
>
>
John,
I personally have a triple-boot machine (win98se, win2000, and Redhat
7.1) with both bootable windows running on a fat32 partition. After
having problems getting the Merge NIC to work correctly (among many
other problems), I ended up doing a clean installation of RH7.1 (instead
of the upgrade option from RH7). I included firewall, iptables,
ipchains, ipforwarding, and vfat options (by creating the appropriate
mount points during the partition check of the RedHat installation) when
I re-installed RedHat. Immediately after this installation, I upgraded
to Ximian Gnome 1.4, then re-installed Win4Lin 3.0. So far all is
working great - I have access to both fat32 (vfat) partitions, and VNET
is working properly as well.
In summary, I suspect that you might need to either rebuild your kernel
or reinstall SuSE to enable kernel level support for vfat.
Cheers,
Bob Jones
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
