[Wine] Re: Wine, AMD and FAT32

[richardrosa]

vitamin wrote:
> 
> richardrosa wrote:
> > Backtrace:
> > =>1 0x00465a75 EntryPoint() in winbej (0x0032ffe8)
> > 0x00465a75 EntryPoint in winbej: pushl  %ebp
> 
> It would work if you mount it right. Wine won't run anything from partitions mounted with "noexec". That's Linux's security feature Wine can't (and won't overcome.
> 
> But as oiaohm said, don't use fat, it's greatly inferior FS which should not be used by anyone no exceptions. Unless you really want to throw all your data away. Then why do you even bother?


Thank you for the pointer. Apparently noexec is now the default for mounting VFAT partitions. Adding "exec" to the mount in fstab seems to fix the problem!  
Still don't understand why this DOESN'T happen on my Intel system, but I've updated the fstab there anyway. 

 Although I agree with everyone who suggested NOT to run FAT32, it is not that simple. The systems I support require BOTH Windows & Linux, and need to have access to common data and applications.  I would LOVE to be able to tell the folks who use these systems that Windows is no longer needed. Alas, there are some applications (and users) that insist on using an MS operating system. EXT2 does not play well in a Windows world, likewise for NTFS on the Linux side. FAT32 is the one format that seems to be tolerated well by both OSs. The day that I can bid Windows goodbye, FAT32 will go with it.

  Thanx again for your assistance.

 Rich