Re: wine: notepad OK, others not

2008-05-05 Thread Tijl Coosemans
On Monday 05 May 2008 02:10:34 [EMAIL PROTECTED] wrote:
>>> ... very shortly after starting the actual install I got an error
>>> box:
>>> 
>>> 
>>>  VISIO Setup
>>> 
>>>! Tried to create an invalid path using 'A:\' and 'clipart.vs_'
>>> 
>>> 
>>> and it locked up the display so that CtrlAltF1 would not switch
>>> to a text screen (although it did allow AltTab to bring up FVWM's
>>> window list).  After clicking OK:
>>> 
>>> 
>>>  Visio Setup
>>> 
>>>i Setup failed.
>>> 
>>> 
>>> and it quit.
>>
>> What version of Visio is this?
> 
> 3.0.  Long before M$ took it over, so it should be just a generic
> Win32 app with no secret M$ tricks.

Visio 3.0 was still 16bit apparently. What you could try is to set
the Windows version in winecfg (bottom of applications tab) to
Windows 95 or even Windows 3.1.

>> Also, you should really take this to the [EMAIL PROTECTED]
>> mailing list. The people there should know more about this than
>> here on a FreeBSD mailing list.
> 
> I suppose I can try it, but I wonder how much interest there will
> be on a wine list in supporting FreeBSD.  At a minimum I suppose
> they'll want to know if it still breaks on the latest wine version,
> and I'll have no way to find out since the FreeBSD port doesn't
> support the latest wine version.

It's just that they know more about debugging such problems and
figuring out if it's Wine or a FreeBSD problem.

The latest version is in ports by the way, wine 0.9.61.

> In any case, it seems FreeBSD should not be allowing a port -- any
> port -- to lock out CtrlAltF1.

Patches welcome...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: wine: notepad OK, others not

2008-05-04 Thread perryh
> >> Wine has its own simple version of Wordpad though.
> >> Just run "wine wordpad".
> > 
> > This version has its own notepad, but it doesn't appear to have
> > wordpad.  (There's no "wordpad.exe" that I can find, but there
> > are two identical copies of "notepad.exe" -- one in .../windows
> > and the other in .../windows/system32.)
>
> "wine wordpad" still works though. It's in /usr/local/lib/wine.

Along with yet another notepad, this one twice the size of the ones
in .../windows and .../windows/system32!  The obvious followup is
which one actually gets used if someone runs "wine notepad", but
I doubt it's worth looking into.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: wine: notepad OK, others not

2008-05-04 Thread perryh
> > ... very shortly after starting the actual install I got an error
> > box:
> > 
> > 
> >  VISIO Setup
> > 
> >! Tried to create an invalid path using 'A:\' and 'clipart.vs_'
> > 
> > 
> > and it locked up the display so that CtrlAltF1 would not switch
> > to a text screen (although it did allow AltTab to bring up FVWM's
> > window list).  After clicking OK:
> > 
> > 
> >  Visio Setup
> > 
> >i Setup failed.
> > 
> > 
> > and it quit.
>
> Were there any messages printed in the terminal window?

No.

> What version of Visio is this?

3.0.  Long before M$ took it over, so it should be just a generic
Win32 app with no secret M$ tricks.

> You might also want to try on a Linux system if you have that
> somewhere, just to see if it works there.

If I had a Linux system set up, I'd have tried this there in the
first place.

> Also, you should really take this to the [EMAIL PROTECTED]
> mailing list. The people there should know more about this than
> here on a FreeBSD mailing list.

I suppose I can try it, but I wonder how much interest there will
be on a wine list in supporting FreeBSD.  At a minimum I suppose
they'll want to know if it still breaks on the latest wine version,
and I'll have no way to find out since the FreeBSD port doesn't
support the latest wine version.

In any case, it seems FreeBSD should not be allowing a port -- any
port -- to lock out CtrlAltF1.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: wine: notepad OK, others not

2008-05-04 Thread Tijl Coosemans
On Thursday 01 May 2008 08:00:23 [EMAIL PROTECTED] wrote:
>> You have to mount the floppy and then link a: to the mount point.
>> So if you mount it under /mnt you'd need this:
>>
>> mount -t msdosfs /dev/fd0 /mnt
>> ln -s /mnt ~/.wine/dosdevices/a:
> 
> That got only a little bit farther.  It did find the setup program,
> and the option dialogs seemed to work properly, but very shortly
> after starting the actual install I got an error box:
> 
> 
>  VISIO Setup
> 
>! Tried to create an invalid path using 'A:\' and 'clipart.vs_'
> 
> 
> and it locked up the display so that CtrlAltF1 would not switch
> to a text screen (although it did allow AltTab to bring up FVWM's
> window list).  After clicking OK:
> 
> 
>  Visio Setup
> 
>i Setup failed.
> 
> 
> and it quit.

Were there any messages printed in the terminal window?
What version of Visio is this?

You might also want to try on a Linux system if you have that
somewhere, just to see if it works there.

Also, you should really take this to the [EMAIL PROTECTED]
mailing list. The people there should know more about this than
here on a FreeBSD mailing list.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: wine: notepad OK, others not

2008-05-04 Thread Tijl Coosemans
On Tuesday 29 April 2008 08:10:37 [EMAIL PROTECTED] wrote:
>> Wine has its own simple version of Wordpad though.
>> Just run "wine wordpad".
> 
> This version has its own notepad, but it doesn't appear to have
> wordpad.  (There's no "wordpad.exe" that I can find, but there
> are two identical copies of "notepad.exe" -- one in .../windows
> and the other in .../windows/system32.)

"wine wordpad" still works though. It's in /usr/local/lib/wine.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: wine: notepad OK, others not

2008-04-30 Thread perryh
> You have to mount the floppy and then link a: to the mount point.
> So if you mount it under /mnt you'd need this:
>
> mount -t msdosfs /dev/fd0 /mnt
> ln -s /mnt ~/.wine/dosdevices/a:

That got only a little bit farther.  It did find the setup program,
and the option dialogs seemed to work properly, but very shortly
after starting the actual install I got an error box:


 VISIO Setup

   ! Tried to create an invalid path using 'A:\' and 'clipart.vs_'


and it locked up the display so that CtrlAltF1 would not switch
to a text screen (although it did allow AltTab to bring up FVWM's
window list).  After clicking OK:


 Visio Setup

   i Setup failed.


and it quit.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: wine: notepad OK, others not

2008-04-28 Thread perryh
> Wine has its own simple version of Wordpad though.
> Just run "wine wordpad".

This version has its own notepad, but it doesn't appear to have
wordpad.  (There's no "wordpad.exe" that I can find, but there
are two identical copies of "notepad.exe" -- one in .../windows
and the other in .../windows/system32.)

> I'm not entirely sure, but I think the :: link is only used for
> raw access to devices. Wine doesn't mount disks on its own.

For floppies, which AFAIK are always formatted as FAT, I'd settle
for having it use mtools so the disk wouldn't need to be mounted
at all :)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: wine: notepad OK, others not

2008-04-28 Thread Tijl Coosemans
On Saturday 26 April 2008 10:02:39 [EMAIL PROTECTED] wrote:
>> It's really easier to try to install an app under Wine...
> 
> With, it seems, at least two exceptions:
> 
> * Some apps -- such as Wordpad and Write -- are packaged and
>   installed with Windows, rather than on separate media.  Are
>   there instructions somewhere for "installing" such an app
>   under wine?  I'm certainly not finding it at all obvious.

Such apps you can only try to copy over to Wine. Wine has its
own simple version of Wordpad though. Just run "wine wordpad".

> * Some add-on (separately installable) apps are packaged
>   on multiple diskettes (or multiple CDs for that matter). 
>   Pre-mounting the first, and pointing wine at the mount
>   point, seems likely to result in getting stuck partway
>   through the install when it asks for the second disk.
> 
> The version of Visio that I have is in the second category.

You should ask about this on the wine-users mailing list. It should
be possible to unmount the disk when it asks for the next one. If
you can't then that's a bug.

> The manpage describes a way of pointing wine to a device
> rather than to a mounted filesystem:
> 
>   The Unix device corresponding to a DOS drive can be
>   specified the same way, except with '::' instead of
>   ':'. So for the previous example, if the CDROM device
>   is mounted from /dev/hdc, the corresponding symlink
>   would be $WINEPREFIX/dosdevices/d:: -> /dev/hdc.
> 
> but, as reported elsewhere, wine could not find setup.exe
> on the Visio install diskette with dosdevices set up this
> way.

I'm not entirely sure, but I think the :: link is only used for
raw access to devices. Wine doesn't mount disks on its own.

>> ... You also might want to have a look at
>> http://wiki.winehq.org/winetricks for a script
>> that can install and setup various packages ...
> 
> Unfortunately, I can't find Visio in its list of packages.

Yes, it's only for extra packages (libs, fonts,..) like mfc42.dll
and such. It's just that installing DLLs via winetricks might be
easier than trying to figure out what DLLs to copy from a Windows
install.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: wine: notepad OK, others not

2008-04-26 Thread perryh
> It's really easier to try to install an app under Wine ...

With, it seems, at least two exceptions:

* Some apps -- such as Wordpad and Write -- are packaged and
  installed with Windows, rather than on separate media.  Are
  there instructions somewhere for "installing" such an app
  under wine?  I'm certainly not finding it at all obvious.

* Some add-on (separately installable) apps are packaged
  on multiple diskettes (or multiple CDs for that matter). 
  Pre-mounting the first, and pointing wine at the mount
  point, seems likely to result in getting stuck partway
  through the install when it asks for the second disk.

The version of Visio that I have is in the second category.

The manpage describes a way of pointing wine to a device
rather than to a mounted filesystem:

  The Unix device corresponding to a DOS drive can be
  specified the same way, except with '::' instead of
  ':'. So for the previous example, if the CDROM device
  is mounted from /dev/hdc, the corresponding symlink
  would be $WINEPREFIX/dosdevices/d:: -> /dev/hdc.

but, as reported elsewhere, wine could not find setup.exe
on the Visio install diskette with dosdevices set up this
way.

> ... You also might want to have a look at
> http://wiki.winehq.org/winetricks for a script
> that can install and setup various packages ...

Unfortunately, I can't find Visio in its list of packages.

Is there something else to try, or is installing an app like
Visio beyond Wine's current capabilities?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: wine: notepad OK, others not

2008-04-23 Thread perryh
> >$ ls -la .wine/dosdevices
> >total 4
> >drwxr-xr-x  2 perryh  staff  512 Apr 21 00:17 .
> >drwxr-xr-x  4 perryh  staff  512 Apr 22 21:07 ..
> >lrwxr-xr-x  1 perryh  staff8 Apr 21 00:17 a:: -> /dev/fd0
>
>   Is the second colon intentional

Yes!  That is exactly what the manpage says to do, so as to have
wine use a *device* rather than a node in the Unix filesystem:

  $WINEPREFIX/dosdevices
Directory  containing the DOS device mappings. Each file in that
directory is a symlink to the Unix device  file  implementing  a
given  device.  For  instance,  if  COM1 is mapped to /dev/ttyS0
you'd have a symlink of the form $WINEPREFIX/dosdevices/com1  ->
/dev/ttyS0.
DOS  drives  are  also  specified with symlinks; for instance if
drive D: corresponds to the CDROM mounted at  /mnt/cdrom,  you'd
have a symlink $WINEPREFIX/dosdevices/d: -> /mnt/cdrom. The Unix
>>  device corresponding to a DOS drive can be  specified  the  same
>>  way,  except with '::' instead of ':'. So for the previous exam-
>>  ple, if the CDROM device is mounted from  /dev/hdc,  the  corre-
>>  sponding   symlink   would   be   $WINEPREFIX/dosdevices/d::  ->
>>  /dev/hdc.

Presumably this method is provided so that wine can be given access
to a removable device without a particular disk having to be mounted.
It would be, at the least, inconvenient to have to mount and unmount
a sequence of 5 floppies to do this installation.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: wine: notepad OK, others not

2008-04-23 Thread Tijl Coosemans
On Wednesday 23 April 2008 08:11:38 [EMAIL PROTECTED] wrote:
>> If I were you I'd just try to install Visio under Wine and see how
>> it goes. That is, mount the install cd, check with winecfg that
>> Wine can see the mount point as a drive D: or something and then
>> run "wine d:\\setup.exe" ...
> 
> It did not work at all.  This version of Visio is old enough that
> it installs from floppies, rather than from CD :) and I've set it
> up in .wine/dosdevices according to the manpage:
> 
>   $ ls -la .wine/dosdevices
>   total 4
>   drwxr-xr-x  2 perryh  staff  512 Apr 21 00:17 .
>   drwxr-xr-x  4 perryh  staff  512 Apr 22 21:07 ..
>   lrwxr-xr-x  1 perryh  staff8 Apr 21 00:17 a:: -> /dev/fd0
>   lrwxr-xr-x  1 perryh  staff   10 Apr 19 16:39 c: -> ../drive_c
>   lrwxr-xr-x  1 perryh  staff1 Apr 19 16:39 z: -> /

You have to mount the floppy and then link a: to the mount point.
So if you mount it under /mnt you'd need this:

mount -t msdosfs /dev/fd0 /mnt
ln -s /mnt ~/.wine/dosdevices/a:

> There doesn't seem to be a manpage for winecfg:
> 
>   $ man winecfg
>   No manual entry for winecfg
> 
> and when I tried to run it it was not at all obvious what to do.

Under the drives tab you can setup drive letters to point to (unix)
directories, like for instance the mount point of a cdrom or floppy
disk or your home directory.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: wine: notepad OK, others not

2008-04-23 Thread Robert Huff

[EMAIL PROTECTED] writes:

>$ ls -la .wine/dosdevices
>total 4
>drwxr-xr-x  2 perryh  staff  512 Apr 21 00:17 .
>drwxr-xr-x  4 perryh  staff  512 Apr 22 21:07 ..
>lrwxr-xr-x  1 perryh  staff8 Apr 21 00:17 a:: -> /dev/fd0

Is the second colon intentional


Robert Huff

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: wine: notepad OK, others not

2008-04-22 Thread perryh
> If I were you I'd just try to install Visio under Wine and see how
> it goes. That is, mount the install cd, check with winecfg that
> Wine can see the mount point as a drive D: or something and then
> run "wine d:\\setup.exe" ...

It did not work at all.  This version of Visio is old enough that
it installs from floppies, rather than from CD :) and I've set it
up in .wine/dosdevices according to the manpage:

  $ ls -la .wine/dosdevices
  total 4
  drwxr-xr-x  2 perryh  staff  512 Apr 21 00:17 .
  drwxr-xr-x  4 perryh  staff  512 Apr 22 21:07 ..
  lrwxr-xr-x  1 perryh  staff8 Apr 21 00:17 a:: -> /dev/fd0
  lrwxr-xr-x  1 perryh  staff   10 Apr 19 16:39 c: -> ../drive_c
  lrwxr-xr-x  1 perryh  staff1 Apr 19 16:39 z: -> /

mdir can read the disk, and it does contain a setup.exe, but
wine can't see it:

  $ wine a:setup.exe
  wine: cannot find 'a:setup.exe'
  $ wine 'a:\setup.exe'
  wine: cannot find 'a:\setup.exe'

There doesn't seem to be a manpage for winecfg:

  $ man winecfg
  No manual entry for winecfg

and when I tried to run it it was not at all obvious what to do.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: wine: notepad OK, others not

2008-04-22 Thread Tijl Coosemans
On Tuesday 22 April 2008 06:00:40 [EMAIL PROTECTED] wrote:
>>> ... If you want to run applications under Wine either install
>>> them under Wine or (with simple applications) copy them over
>>> from a Windows install into ~/.wine/drive_c.
>>
>> And specifically I'd populate  ~/.wine/drive_c/windows/fonts
>> from a real windows installation.
> 
> Which raises the question:  how does one figure out what-all
> pieces of a real windows installation should and should not be
> copied (or symlinked) into ~/.wine/drive_c?  So far it looks
> as if some (but surely not all) .exe's and .dll's, and (all?)
> fonts, should be imported.

And then you're forgetting all the bits in the register.
It's really easier to try to install an app under Wine and then
when you run it, see if there are any missing dlls or missing
functionality in Wine built-in dlls (err and fixme messages).
Then you can copy those from Windows. You also might want to
have a look at http://wiki.winehq.org/winetricks for a script
that can install and setup various packages, also fonts.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: wine: notepad OK, others not

2008-04-21 Thread perryh
> > ... If you want to run applications under Wine either install
> > them under Wine or (with simple applications) copy them over
> > from a Windows install into ~/.wine/drive_c.
>
> And specifically I'd populate  ~/.wine/drive_c/windows/fonts
> from a real windows installation. 

Which raises the question:  how does one figure out what-all
pieces of a real windows installation should and should not be
copied (or symlinked) into ~/.wine/drive_c?  So far it looks
as if some (but surely not all) .exe's and .dll's, and (all?)
fonts, should be imported.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: wine: notepad OK, others not

2008-04-21 Thread RW
On Sun, 20 Apr 2008 13:59:35 +0200
Tijl Coosemans <[EMAIL PROTECTED]> wrote:

> Wine is not meant to work that way. You should see Wine as a separate
> Windows. If you want to run applications under Wine either install
> them under Wine or (with simple applications) copy them over from a
> Windows install into ~/.wine/drive_c.
> 

And specifically I'd populate  ~/.wine/drive_c/windows/fonts from a
real windows installation. 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: wine: notepad OK, others not

2008-04-20 Thread Tijl Coosemans
On Sunday 20 April 2008 03:35:59 [EMAIL PROTECTED] wrote:
>>>  I have installed wine-0.9.20 from ports, and
>>>  there's a Win98 FAT32 slice mounted on /windoze
>>
>>  
>>   
>>>  How do I fix this?
>>
>> I would start by upgrading and re-installing wine.  You have 0.9.20;
>> the current version is 0.9.55 and I believe there have been
>> substantial improvements.
> 
> When I updated my ports, the newer wine refused to install on 6.1,
> saying it wouldn't work properly on anything prior to 6.3 IIRC.
> 
> Rather than risk breaking my primary system in an upgrade attempt, I
> installed 7.0-RELEASE and wine-0.9.48 (the version from the
> 7.0-RELEASE ports) on a different machine.  It happened to have XP,
> so I'm now trying to run XP .exe's instead of win98 .exe's.
> 
> Notepad and Write are, if anything, worse than before:  now, if I
> just start typing without selecting a font, I get something that
> looks more or less like dingbats.  They do seem to work if I
> explicitly select Courier.  (The ultimate goal is to run Visio, not
> to do word processing, but I'm trying to start with something
> simple.)
> 
> The problem with wordpad has not changed very much:
> 
>   $ wine "/winxp/Program Files/Windows NT/Accessories/wordpad.exe"
>   err:module:import_dll Library MFC42u.DLL (which is needed by 
> L"Z:\\winxp\\Program Files\\Windows NT\\Accessories\\wordpad.exe") not found
>   err:module:LdrInitializeThunk Main exe initialization for 
> L"Z:\\winxp\\Program Files\\Windows NT\\Accessories\\wordpad.exe" failed, 
> status c135

Wine is not meant to work that way. You should see Wine as a separate
Windows. If you want to run applications under Wine either install them
under Wine or (with simple applications) copy them over from a Windows
install into ~/.wine/drive_c.

> OK, it doesn't know where to find the DLLs.  Try making a symlink to
> a place which (per the manpage) is always searched:
> 
>   $ ls -l /winxp/WINDOWS/SYSTEM32/mfc42u.dll
>   -rwxr-xr-x  1 root  wheel  995384 Aug 23  2001 
> /winxp/WINDOWS/SYSTEM32/mfc42u.dll
>   $ ln -s /winxp/WINDOWS/SYSTEM32/mfc42u.dll /usr/local/lib/wine
>   $ wine "/winxp/Program Files/Windows NT/Accessories/wordpad.exe"
>   err:module:import_dll Library MFC42u.DLL (which is needed by 
> L"Z:\\winxp\\Program Files\\Windows NT\\Accessories\\wordpad.exe") not found
>   err:module:LdrInitializeThunk Main exe initialization for 
> L"Z:\\winxp\\Program Files\\Windows NT\\Accessories\\wordpad.exe" failed, 
> status c135

/usr/local/lib/wine is only for Wine built-in DLLs I think. You could
try putting the symlink or copying the DLL into
~/.wine/drive_c/windows/system32, but again it is not recommended to
run applications directly from an existing Windows install.

If I were you I'd just try to install Visio under Wine and see how it
goes. That is, mount the install cd, check with winecfg that Wine can
see the mount point as a drive D: or something and then run "wine
d:\\setup.exe". On appdb.winehq.org there's probably more information
to get Visio working.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: wine: notepad OK, others not

2008-04-19 Thread perryh
> >  I have installed wine-0.9.20 from ports, and
> >  there's a Win98 FAT32 slice mounted on /windoze
>
>   
>   
> >  How do I fix this?
>
>   I would start by upgrading and re-installing wine.  You have
> 0.9.20; the current version is 0.9.55 and I believe there have been
> substantial improvements.

When I updated my ports, the newer wine refused to install on 6.1,
saying it wouldn't work properly on anything prior to 6.3 IIRC.

Rather than risk breaking my primary system in an upgrade attempt,
I installed 7.0-RELEASE and wine-0.9.48 (the version from the
7.0-RELEASE ports) on a different machine.  It happened to have XP,
so I'm now trying to run XP .exe's instead of win98 .exe's.

Notepad and Write are, if anything, worse than before:  now, if
I just start typing without selecting a font, I get something
that looks more or less like dingbats.  They do seem to work if
I explicitly select Courier.  (The ultimate goal is to run Visio,
not to do word processing, but I'm trying to start with something
simple.)

The problem with wordpad has not changed very much:

  $ wine "/winxp/Program Files/Windows NT/Accessories/wordpad.exe"
  err:module:import_dll Library MFC42u.DLL (which is needed by 
L"Z:\\winxp\\Program Files\\Windows NT\\Accessories\\wordpad.exe") not found
  err:module:LdrInitializeThunk Main exe initialization for 
L"Z:\\winxp\\Program Files\\Windows NT\\Accessories\\wordpad.exe" failed, 
status c135

(Previously it was looking for MFC42.DLL instead of MFC42u.DLL.)

OK, it doesn't know where to find the DLLs.  Try making a symlink
to a place which (per the manpage) is always searched:

  $ ls -l /winxp/WINDOWS/SYSTEM32/mfc42u.dll
  -rwxr-xr-x  1 root  wheel  995384 Aug 23  2001 
/winxp/WINDOWS/SYSTEM32/mfc42u.dll
  $ ln -s /winxp/WINDOWS/SYSTEM32/mfc42u.dll /usr/local/lib/wine
  $ wine "/winxp/Program Files/Windows NT/Accessories/wordpad.exe"
  err:module:import_dll Library MFC42u.DLL (which is needed by 
L"Z:\\winxp\\Program Files\\Windows NT\\Accessories\\wordpad.exe") not found
  err:module:LdrInitializeThunk Main exe initialization for 
L"Z:\\winxp\\Program Files\\Windows NT\\Accessories\\wordpad.exe" failed, 
status c135

Maybe the search is case-sensitive (although Windows ordinarily
isn't)?

  $ ln -s /winxp/WINDOWS/SYSTEM32/mfc42u.dll /usr/local/lib/wine/MFC42u.DLL
  $ wine "/winxp/Program Files/Windows NT/Accessories/wordpad.exe"
  err:module:import_dll Library MFC42u.DLL (which is needed by 
L"Z:\\winxp\\Program Files\\Windows NT\\Accessories\\wordpad.exe") not found
  err:module:LdrInitializeThunk Main exe initialization for 
L"Z:\\winxp\\Program Files\\Windows NT\\Accessories\\wordpad.exe" failed, 
status c135

The symlinks in /usr/local/lib/wine *do* point to that DLL, and they
*can* be followed successfully:

  $ ( cd /usr/local/lib/wine ; ls -lL mfc* MFC* )
  -rwxr-xr-x  1 root  wheel  995384 Aug 23  2001 MFC42u.DLL
  -rwxr-xr-x  1 root  wheel  995384 Aug 23  2001 mfc42u.dll

Now what?  I can't imagine anyone would be able to do much with wine
if problems finding DLLs were common.  What am I doing wrong?

  $ wine --version
  wine-0.9.48
  $ uname -a
  FreeBSD fbsd70.uucp 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 
UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"