Hi Charles ...
I am not familiar with RedHat (I'm Suse), and I dont' know HOW you
got your first system to do that without manually changing something,
but Windows executable will NOT run natively on linux, which means
another program must be used to open the Windows App (Ergo the wine
NOTEPAD.EXE) ...
HOWEVER, having said that, on Suse, you can configure it to open
extensions with specific programs - just lke Windows. In Suse you
navigate to the file, right click and select Open with, and select the
appropriate fields.
After that, you should be able to simply type in "programname" in
your terminal window, and it shoudl work - it does on mine anyways ...
hope that helps
Derek
On Thu, 2006-12-21 at 10:26 -0800, Charles Krinke wrote:
> I have two computers with wine installed. The first is a Fedora Core 6
> with all updates running wine-0.9.25. The second is a RHEL4 with
> wine-0.9.27 compiled from source (./configure, make, make install). In
> both cases I have a dual-boot partition with a WindowsXP NTFS, and I can
> install and run ntfs-3g with no problem.
>
> In the first system, I can navigate to the location of NOTEPAD.EXE and
> invoke it directly as './NOTEPAD.EXE' from a bash prompt. In the second
> system, I need to do 'wine NOTEPAD.EXE'.
>
> Can someone help me understand how to make the second system respond
> directly to an invocation of a windows executable and how this actually
> works. Is this ld.so, binfmt_misc or some file suffix association magic
> going on and how does it work, please?
>
> Charles
>
> _______________________________________________
> wine-users mailing list
> wine-users@xxxxxxxxxx
> http://www.winehq.org/mailman/listinfo/wine-users
_______________________________________________
wine-users mailing list
wine-users@xxxxxxxxxx
http://www.winehq.org/mailman/listinfo/wine-users
