Re: Wine-fbsd64 updated to 1.5.20 (32bit Wine for 64bit FreeBSD)

2012-12-28 Thread David Naylor
On 26 Dec 2012 9:28 AM, Jens Jahnke jan0...@gmx.net wrote:

 Hi,

Hi,

 On Mon, 24 Dec 2012 12:27:11 +0200
 David Naylor naylor.b.da...@gmail.com wrote:

 DN Since it is possible to install the existing pkg
 DN packages in a pkgng environment (which I do) this is not a high
 DN priority.

 is there a documentation for that? I searched the pkgng docs but found
 nothing regarding installation of old packages or converting them to
 a newer version.

Use the old `pkg_ng` command to install the package. As long as the files
installed with the old and the new package tools are mutually exclusive you
shouldn't have a problem.

If you patch your ports tree with the wine-fbsd64 diff then it is possible
to use `pkg2ng` to convert to the pkgng format. (Although I have never
tested that, see documentation for pkg2ng and `pkg create`).

Regards
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine-fbsd64 updated to 1.5.20 (32bit Wine for 64bit FreeBSD)

2012-12-28 Thread Jens Jahnke
Hi,

On Sat, 29 Dec 2012 07:42:02 +0200
David Naylor naylor.b.da...@gmail.com wrote:

DN  On Mon, 24 Dec 2012 12:27:11 +0200
DN  David Naylor naylor.b.da...@gmail.com wrote:
DN 
DN  DN Since it is possible to install the existing pkg
DN  DN packages in a pkgng environment (which I do) this is not a
DN  DN high priority.
DN 
DN  is there a documentation for that? I searched the pkgng docs but
DN  found nothing regarding installation of old packages or
DN  converting them to a newer version.
DN 
DN Use the old `pkg_ng` command to install the package. As long as the
DN files installed with the old and the new package tools are mutually
DN exclusive you shouldn't have a problem.
DN 
DN If you patch your ports tree with the wine-fbsd64 diff then it is
DN possible to use `pkg2ng` to convert to the pkgng format. (Although
DN I have never tested that, see documentation for pkg2ng and `pkg
DN create`).

meanwhile I've succeeded in building wine from ports using a 32bit
system under /compat/i386 following the instructions in the freebsd
wiki. I needed some tweaks which I documented here: 
https://makandracards.com/jan0sch/13429-installing-wine-under-freebsd-8-amd64

Regards,

Jens

-- 
29. Julmond 2012, 08:38
Homepage : http://www.jan0sch.de

Still looking for the glorious results of my misspent youth.
Say, do you have a map to the next joint?


pgpOfcSfwkSVo.pgp
Description: PGP signature


Re: Wine-fbsd64 updated to 1.5.20 (32bit Wine for 64bit FreeBSD)

2012-12-26 Thread Jens Jahnke
On Wed, 26 Dec 2012 07:54:58 +
Matthew Seaman matt...@freebsd.org wrote:

MS On 26/12/2012 07:27, Jens Jahnke wrote:
MS  On Mon, 24 Dec 2012 12:27:11 +0200
MS  David Naylor naylor.b.da...@gmail.com wrote:
MS  
MS  DN Since it is possible to install the existing pkg 
MS  DN packages in a pkgng environment (which I do) this is not a
MS  DN high priority.
MS  
MS  is there a documentation for that? I searched the pkgng docs but
MS  found nothing regarding installation of old packages or
MS  converting them to a newer version.
MS 
MS There's nothing in pkg_tools to stop it working on a pkgng-enabled
MS system.  This does not mean that installing pkg_tools packages in
MS that situation is in any way supported or encouraged.  If you do
MS this, you will create a mess on your systems and store up a nasty
MS job of sorting it all out for yourself.  It really isn't a good
MS idea.

Thanks for the advise. I guessed in that direction. So I'll be patient
and wait for packages because I've never been able to build wine
(64bit) myself from source. I just need it for some old games anyway. ;)

Regards,

Jens

-- 
26. Julmond 2012, 11:13
Homepage : http://www.jan0sch.de

All my friends and I are crazy.
That's the only thing that keeps us sane.


pgprZUj0u9Os7.pgp
Description: PGP signature


Re: Wine-fbsd64 updated to 1.5.20 (32bit Wine for 64bit FreeBSD)

2012-12-25 Thread Jens Jahnke
Hi,

On Mon, 24 Dec 2012 12:27:11 +0200
David Naylor naylor.b.da...@gmail.com wrote:

DN Since it is possible to install the existing pkg 
DN packages in a pkgng environment (which I do) this is not a high
DN priority.

is there a documentation for that? I searched the pkgng docs but found
nothing regarding installation of old packages or converting them to
a newer version.

Regards,

Jens

-- 
26. Julmond 2012, 08:27
Homepage : http://www.jan0sch.de

What the world *really* needs is a good Automatic Bicycle Sharpener.


pgpRsnILSI7Jk.pgp
Description: PGP signature


Re: Wine-fbsd64 updated to 1.5.20 (32bit Wine for 64bit FreeBSD)

2012-12-25 Thread Matthew Seaman
On 26/12/2012 07:27, Jens Jahnke wrote:
 On Mon, 24 Dec 2012 12:27:11 +0200
 David Naylor naylor.b.da...@gmail.com wrote:
 
 DN Since it is possible to install the existing pkg 
 DN packages in a pkgng environment (which I do) this is not a high
 DN priority.
 
 is there a documentation for that? I searched the pkgng docs but found
 nothing regarding installation of old packages or converting them to
 a newer version.

There's nothing in pkg_tools to stop it working on a pkgng-enabled
system.  This does not mean that installing pkg_tools packages in that
situation is in any way supported or encouraged.  If you do this, you
will create a mess on your systems and store up a nasty job of sorting
it all out for yourself.  It really isn't a good idea.

I know there is a lack of availability of official pre-compiled packages
from the FreeBSD project at the moment.  This is an unfortunate
consequence of the security problem in November, and all I can do is ask
for your patience as the situation gets sorted out.

In the mean time, the best advice is to compile your own.  Either
directly from ports, by using portmaster or portupgrade or else by using
an off-line package building system like poudriere or tinderbox[*].

Cheers,

Matthew

[*] You need tinderbox-devel for pkgng support, or the upcoming 4.0.0
release.

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey




signature.asc
Description: OpenPGP digital signature


Re: Wine-fbsd64 updated to 1.5.18 (32bit Wine for 64bit FreeBSD)

2012-12-24 Thread David Naylor
Hi,

Apologies, the incorrect package was uploaded for wine-1.5.x-freebsd9 for 
wine-fbsd64-1.5.18.  The correct file is:

MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.18.1.txz) =
 f256fb13adaf5c8bf313c5973ac8159c

Regards,

David

On Saturday, 1 December 2012 15:21:14 David Naylor wrote:
 Hi,
 
 Packages [1] for wine-fbsd64-1.5.18 have been uploaded to mediafire [2]. 
 The packages for FreeBSD 10 use the pkgng [3] format.
 
 Please read the installation messages, if you use the nVidia graphics
 driver, for further information.
 
 FAQ
 ---
 Q: wine: failed to initialize: / usr/local/lib32/wine/ntdll.dll.so:
 Undefined symbol _ThreadRuneLocale
 A: This problem is specific to FreeBSD-9.0, please either stick with
 wine-1.5.10 or update to a newer version of FreeBSD (-STABLE or 9.1).
 Apologies for the inconvenience.
 
 Q: Creating pkgng packages for FreeBSD-9
 A: When there is no demand for FreeBSD-8 packages I'll create additional
 pkgng packages for FreeBSD-9.  Since it is possible to install the
 existing pkg packages in a pkgng environment (which I do) this is not a
 high priority.
 
 Q: Wine doesn't run (properly) with a clang built world
 A: Clang was compiling i386 on a 16-byte boundary while gcc was using a
 4-byte boundary.  To fix, recompile world after ensuring your sources
 include http://beta.freshbsd.org/commit/freebsd/r242835 or the relevant
 MFC.
 
 Regards,
 
 David
 
 [1]
  MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.18,1.tbz) =
   7335bcf8fd3a3bcb98a74e2b9d797963
  MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.18.1.txz) =
   6fb7d760ffe9ef19457982e861e84f83
  MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.18,1.txz) =
   13c54f14d4f51e46f1b22320b41308ca
 [2] http://www.mediafire.com/wine_fbsd64
 [3] http://wiki.freebsd.org/pkgng


signature.asc
Description: This is a digitally signed message part.


Re: wine-fbsd64 -- no longer in ports

2012-11-19 Thread Hexing
per...@pluto.rain.com (Perry Hutchison) writes:

 Bernt Hansson b...@bananmonarki.se wrote:
 On 2012-11-17 21:36, Gary Aitken wrote:
  # portmaster -n emulators/wine-fbsd64
=== No /usr/ports/emulators/wine-fbsd64 exists, and no information
=== about emulators/wine-fbsd64 can be found in /usr/ports/MOVED
  hints?
 There has never been such a port, you have to install from package.

 Ordinarily, packages are created by building ports.
 If this one is an exception, how is it created?

I guess that just remove it and install /usr/ports/emulators/wine or
/usr/ports/emulators/wine-devel would be OK. 

The name 'wine-fbsd64' looks strange. You installed it before? and
when did you find this name?

-- 
Hello, world!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine-fbsd64 -- no longer in ports

2012-11-19 Thread C. P. Ghost
On Mon, Nov 19, 2012 at 1:31 PM, Hexing hexhex...@gmail.com wrote:
 per...@pluto.rain.com (Perry Hutchison) writes:

 Bernt Hansson b...@bananmonarki.se wrote:
 On 2012-11-17 21:36, Gary Aitken wrote:
  # portmaster -n emulators/wine-fbsd64
=== No /usr/ports/emulators/wine-fbsd64 exists, and no information
=== about emulators/wine-fbsd64 can be found in /usr/ports/MOVED
  hints?
 There has never been such a port, you have to install from package.

 Ordinarily, packages are created by building ports.
 If this one is an exception, how is it created?

 I guess that just remove it and install /usr/ports/emulators/wine or
 /usr/ports/emulators/wine-devel would be OK.

Nope, not for amd64:

% grep 'ONLY_FOR_ARCHS' /usr/ports/emulators/wine/Makefile
ONLY_FOR_ARCHS= i386
% grep 'ONLY_FOR_ARCHS' /usr/ports/emulators/wine-devel/Makefile
ONLY_FOR_ARCHS= i386

The wine and wine-devel ports won't even compile on amd64.

There was some guy who claims to have managed creating a
binary _package_ for amd64 somehow, and wo sent periodic
announcement updates about to this list. I don't know if it was
legit or not: I never install stuff bypassing ports. But apparently,
he didn't create a _port_, nor did he modify/enhance the current
i386-only wine ports.

 The name 'wine-fbsd64' looks strange. You installed it before? and
 when did you find this name?

-cpghost.

-- 
Cordula's Web. http://www.cordula.ws/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine-fbsd64 -- no longer in ports

2012-11-19 Thread Volodymyr Kostyrko

any
19.11.2012 15:03, C. P. Ghost wrote:

On Mon, Nov 19, 2012 at 1:31 PM, Hexing hexhex...@gmail.com wrote:

per...@pluto.rain.com (Perry Hutchison) writes:


Bernt Hansson b...@bananmonarki.se wrote:

On 2012-11-17 21:36, Gary Aitken wrote:

# portmaster -n emulators/wine-fbsd64
   === No /usr/ports/emulators/wine-fbsd64 exists, and no information
   === about emulators/wine-fbsd64 can be found in /usr/ports/MOVED
hints?

There has never been such a port, you have to install from package.


Ordinarily, packages are created by building ports.
If this one is an exception, how is it created?


I guess that just remove it and install /usr/ports/emulators/wine or
/usr/ports/emulators/wine-devel would be OK.


Nope, not for amd64:

% grep 'ONLY_FOR_ARCHS' /usr/ports/emulators/wine/Makefile
ONLY_FOR_ARCHS= i386
% grep 'ONLY_FOR_ARCHS' /usr/ports/emulators/wine-devel/Makefile
ONLY_FOR_ARCHS= i386

The wine and wine-devel ports won't even compile on amd64.

There was some guy who claims to have managed creating a
binary _package_ for amd64 somehow, and wo sent periodic
announcement updates about to this list. I don't know if it was
legit or not: I never install stuff bypassing ports. But apparently,
he didn't create a _port_, nor did he modify/enhance the current
i386-only wine ports.


He does created a port but didn't like to commit it into ports as this 
one gobbles all libraries that wine depend upon from local system and 
other installed ports and installs them as part of wine-fbsd64. And this 
is not good from a security/maintainability perspective yet it gives 
everyone a choice to use wine on amd64 machine. The port is freely 
available and regularly updated on mediafire with guides on how someone 
can make this package himself without downloading binaries compiled by 
some third party.


--
Sphinx of black quartz, judge my vow.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine-fbsd64 -- no longer in ports

2012-11-19 Thread Hexing
C. P. Ghost cpgh...@cordula.ws writes:

 On Mon, Nov 19, 2012 at 1:31 PM, Hexing hexhex...@gmail.com wrote:
 I guess that just remove it and install /usr/ports/emulators/wine or
 /usr/ports/emulators/wine-devel would be OK.

 Nope, not for amd64:

 % grep 'ONLY_FOR_ARCHS' /usr/ports/emulators/wine/Makefile
 ONLY_FOR_ARCHS= i386
 % grep 'ONLY_FOR_ARCHS' /usr/ports/emulators/wine-devel/Makefile
 ONLY_FOR_ARCHS= i386

 The wine and wine-devel ports won't even compile on amd64.

 There was some guy who claims to have managed creating a
 binary _package_ for amd64 somehow, and wo sent periodic
 announcement updates about to this list. I don't know if it was
 legit or not: I never install stuff bypassing ports. But apparently,
 he didn't create a _port_, nor did he modify/enhance the current
 i386-only wine ports.

 The name 'wine-fbsd64' looks strange. You installed it before? and
 when did you find this name?

 -cpghost.

Oh, I didn't know that and never try to install wine before. Thanks for
your information.

-- 
Hello, world!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine-fbsd64 -- no longer in ports

2012-11-19 Thread C. P. Ghost
On Mon, Nov 19, 2012 at 6:01 PM, Hexing hexhex...@gmail.com wrote:
 C. P. Ghost cpgh...@cordula.ws writes:

 On Mon, Nov 19, 2012 at 1:31 PM, Hexing hexhex...@gmail.com wrote:
 I guess that just remove it and install /usr/ports/emulators/wine or
 /usr/ports/emulators/wine-devel would be OK.

 Nope, not for amd64:

 % grep 'ONLY_FOR_ARCHS' /usr/ports/emulators/wine/Makefile
 ONLY_FOR_ARCHS= i386
 % grep 'ONLY_FOR_ARCHS' /usr/ports/emulators/wine-devel/Makefile
 ONLY_FOR_ARCHS= i386

 The wine and wine-devel ports won't even compile on amd64.

 There was some guy who claims to have managed creating a
 binary _package_ for amd64 somehow, and wo sent periodic
 announcement updates about to this list. I don't know if it was
 legit or not: I never install stuff bypassing ports. But apparently,
 he didn't create a _port_, nor did he modify/enhance the current
 i386-only wine ports.

 The name 'wine-fbsd64' looks strange. You installed it before? and
 when did you find this name?

 -cpghost.

 Oh, I didn't know that and never try to install wine before. Thanks for
 your information.

Volodymyr has pointed out that this was a port (and not a
binary package) that never got committed. As a port, you can
examine precisely what it does and it may be worth a try if you
feel that it doesn't mess with your installation and doesn't
compromise it. I didn't try it, can't say anything at all about it.

-cpghost.

-- 
Cordula's Web. http://www.cordula.ws/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine-fbsd64 -- no longer in ports

2012-11-18 Thread Perry Hutchison
Bernt Hansson b...@bananmonarki.se wrote:
 On 2012-11-17 21:36, Gary Aitken wrote:
  # portmaster -n emulators/wine-fbsd64
=== No /usr/ports/emulators/wine-fbsd64 exists, and no information
=== about emulators/wine-fbsd64 can be found in /usr/ports/MOVED
  hints?
 There has never been such a port, you have to install from package.

Ordinarily, packages are created by building ports.
If this one is an exception, how is it created?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine-fbsd64 updated to 1.5.12 (32bit Wine for 64bit FreeBSD)

2012-09-03 Thread alphachi
OK, I have solved the problem.

1.5.10 is fine for 9.0 RELEASE. 1.5.111.5.12 have the same error on it.
After 9.0 RELEASE (9.0 STABLE, etc.), all version is fine.

Thanks!
在 2012-9-1 下午11:10,David Naylor naylor.b.da...@gmail.com写道:

 Hi,

 Packages [1] for wine-fbsd64-1.5.12 have been uploaded to mediafire [2].
  The
 packages for FreeBSD 10 use the pkgng [3] format.

 There are many reports that wine does not work with a clang compiled world
 (help in fixing this problem is appreciated as it affects quite a few
 users).

 The patch [4] for nVidia users is now included in the package and is run on
 installation (if the relevant files are accessible).  Please read the
 installation messages for further information.

 Regards,

 David

 [1]
  MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.12,1.tbz) =
 335ef444a2f6f375dd22cf932b651919
  MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.12,1.txz) =
 e06673c4ab9a0bb82a7d48dad5b8877f
  MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.12,1.txz) =
 aafe06b15176f810c25cbf708c11aabb
 [2] http://www.mediafire.com/wine_fbsd64
 [3] http://wiki.freebsd.org/pkgng
 [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine-fbsd64 updated to 1.5.12 (32bit Wine for 64bit FreeBSD)

2012-09-02 Thread David Naylor
On Sunday, 2 September 2012 07:37:34 alphachi wrote:
 2012/9/1 David Naylor naylor.b.da...@gmail.com
 
  Hi,
  
  Packages [1] for wine-fbsd64-1.5.12 have been uploaded to mediafire [2].
  
   The
  
  packages for FreeBSD 10 use the pkgng [3] format.
  
  There are many reports that wine does not work with a clang compiled
  world (help in fixing this problem is appreciated as it affects quite a
  few users).
  
  The patch [4] for nVidia users is now included in the package and is run
  on installation (if the relevant files are accessible).  Please read the
  installation messages for further information.
  
  Regards,
  
  David
  
  [1]
  
   MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.12,1.tbz) =
   
  335ef444a2f6f375dd22cf932b651919
   
   MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.12,1.txz) =
   
  e06673c4ab9a0bb82a7d48dad5b8877f
   
   MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.12,1.txz) =
   
  aafe06b15176f810c25cbf708c11aabb
  
  [2] http://www.mediafire.com/wine_fbsd64
  [3] http://wiki.freebsd.org/pkgng
  [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh
 
 Hi David,

Hi

 I have pkg_add wine-fbsd64-1.5.12,1.txz and run
 /usr/local/share/wine/patch- nvidia.sh; everything is OK.
 
 When running wine, the error msg is:
 wine: failed to initialize: /usr/local/lib32/wine/ntdll.dll.so: Undefined
 symbol _ThreadRuneLocale
 
 What shall I do? Thanks!

Could you please answer some questions:
 - Are you running FreeBSD 9 or 10?
 - When last did you update world?
 - Are you using clang for any compilation (of world, ports, etc)
 - How did you run wine?

Could please run the followings commands, and provide the output:
# uname -a
# winecfg
# regedit
also please run the program that tripped wine up.  

Some things you could try [the following long shots] (although I have no idea 
what the root cause is til I get further information):
 - Have a look at http://markmail.org/thread/5kt24py6q2w2ageq
 - Update to the latest -stable or -current code
 - If you were using clang then switch to gcc and do a full rebuild

Regards


signature.asc
Description: This is a digitally signed message part.


Re: Wine-fbsd64 updated to 1.5.12 (32bit Wine for 64bit FreeBSD)

2012-09-01 Thread alphachi
2012/9/1 David Naylor naylor.b.da...@gmail.com

 Hi,

 Packages [1] for wine-fbsd64-1.5.12 have been uploaded to mediafire [2].
  The
 packages for FreeBSD 10 use the pkgng [3] format.

 There are many reports that wine does not work with a clang compiled world
 (help in fixing this problem is appreciated as it affects quite a few
 users).

 The patch [4] for nVidia users is now included in the package and is run on
 installation (if the relevant files are accessible).  Please read the
 installation messages for further information.

 Regards,

 David

 [1]
  MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.12,1.tbz) =
 335ef444a2f6f375dd22cf932b651919
  MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.12,1.txz) =
 e06673c4ab9a0bb82a7d48dad5b8877f
  MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.12,1.txz) =
 aafe06b15176f810c25cbf708c11aabb
 [2] http://www.mediafire.com/wine_fbsd64
 [3] http://wiki.freebsd.org/pkgng
 [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh

Hi David,

I have pkg_add wine-fbsd64-1.5.12,1.txz and run /usr/local/share/wine/patch-
nvidia.sh; everything is OK.

When running wine, the error msg is:
wine: failed to initialize: /usr/local/lib32/wine/ntdll.dll.so: Undefined
symbol _ThreadRuneLocale

What shall I do? Thanks!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine for Diablo 3 on FreeBSD 9.0R amd64

2012-05-21 Thread Mickaël Maillot
2012/5/19 Edward M eam1edw...@gmail.com:
 On 05/19/2012 02:28 PM, lokada...@gmx.de wrote:

 On 05/17/12 07:54, Любомир Григоров wrote:

 We have to wait, unfortunately. I am using a Linux partition with Wine
 meanwhile. As long as it's not mainstream, it will be hard to do. Not to
 mention port is at 1.4.

 FreeBSD have 2 wine- ports. :)
 http://www.freebsd.org/cgi/ports.cgi?query=wine-1stype=allsektion=all
 wine for 1.4 and wine-devel for 1.5

 But i can't help with Diablo 3.
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 freebsd-questions-unsubscr...@freebsd.org


    a user is trying  but  at the moment  is plague with wine errors.

   http://forum.winehq.org/viewtopic.php?t=15659

 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

i played the beta with patched wine (on 1.5.1 and 1.5.2)
now i play D3 with 1.5.4 without issues, just an agent.exe crash at
start but after that it works well.
some infos:
- installer does not work, i installed the game under windows +
virtualbox and cp the folder
- launcher does not work: wine32 Diablo\ III.exe -launch to bypass it
- i played with patched 1.5.4 with older AcceptEx fix 4 patches +
perl tools/make_requests
- change screen resolution crash the game but works

i have more than 60h played with only one crash.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine for Diablo 3 on FreeBSD 9.0R amd64

2012-05-21 Thread Mickaël Maillot
2012/5/21 Mickaël Maillot mickael.mail...@gmail.com:
 2012/5/19 Edward M eam1edw...@gmail.com:
 On 05/19/2012 02:28 PM, lokada...@gmx.de wrote:

 On 05/17/12 07:54, Любомир Григоров wrote:

 We have to wait, unfortunately. I am using a Linux partition with Wine
 meanwhile. As long as it's not mainstream, it will be hard to do. Not to
 mention port is at 1.4.

 FreeBSD have 2 wine- ports. :)
 http://www.freebsd.org/cgi/ports.cgi?query=wine-1stype=allsektion=all
 wine for 1.4 and wine-devel for 1.5

 But i can't help with Diablo 3.
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 freebsd-questions-unsubscr...@freebsd.org


    a user is trying  but  at the moment  is plague with wine errors.

   http://forum.winehq.org/viewtopic.php?t=15659

 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

 i played the beta with patched wine (on 1.5.1 and 1.5.2)
 now i play D3 with 1.5.4 without issues, just an agent.exe crash at
 start but after that it works well.
 some infos:
 - installer does not work, i installed the game under windows +
 virtualbox and cp the folder
 - launcher does not work: wine32 Diablo\ III.exe -launch to bypass it
 - i played with patched 1.5.4 with older AcceptEx fix 4 patches +
 perl tools/make_requests
 - change screen resolution crash the game but works

 i have more than 60h played with only one crash.

tested on 2 systems:
FreeBSD home.freelooser.fr 9.0-STABLE FreeBSD 9.0-STABLE #2 r233697:
Fri Mar 30 13:15:50 CEST 2012
r...@home.freelooser.fr:/usr/obj/usr/src/sys/FNEUFNEU  amd64
and
FreeBSD fneufneu.secuserve.net 8.2-STABLE FreeBSD 8.2-STABLE #4
r226057M: Thu Oct  6 16:43:50 CEST 2011
r...@fneufneu.secuserve.net:/usr/obj/usr/src/sys/GENERIC  amd64

all my system use xorg-dev trunk (WITH_NEW_XORG=yes for xorg-server
1.12.1) and nvidia-driver 295.49 !!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine for Diablo 3 on FreeBSD 9.0R amd64

2012-05-19 Thread lokada...@gmx.de

On 05/17/12 07:54, Любомир Григоров wrote:

We have to wait, unfortunately. I am using a Linux partition with Wine
meanwhile. As long as it's not mainstream, it will be hard to do. Not to
mention port is at 1.4.

FreeBSD have 2 wine- ports. :)
http://www.freebsd.org/cgi/ports.cgi?query=wine-1stype=allsektion=all
wine for 1.4 and wine-devel for 1.5

But i can't help with Diablo 3.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine for Diablo 3 on FreeBSD 9.0R amd64

2012-05-19 Thread Edward M

On 05/19/2012 02:28 PM, lokada...@gmx.de wrote:

On 05/17/12 07:54, Любомир Григоров wrote:

We have to wait, unfortunately. I am using a Linux partition with Wine
meanwhile. As long as it's not mainstream, it will be hard to do. Not to
mention port is at 1.4.

FreeBSD have 2 wine- ports. :)
http://www.freebsd.org/cgi/ports.cgi?query=wine-1stype=allsektion=all
wine for 1.4 and wine-devel for 1.5

But i can't help with Diablo 3.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
freebsd-questions-unsubscr...@freebsd.org




a user is trying  but  at the moment  is plague with wine errors.

   http://forum.winehq.org/viewtopic.php?t=15659
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine for Diablo 3 on FreeBSD 9.0R amd64

2012-05-16 Thread Любомир Григоров
We have to wait, unfortunately. I am using a Linux partition with Wine
meanwhile. As long as it's not mainstream, it will be hard to do. Not to
mention port is at 1.4.

2012/5/16 alphachi alpha...@mediaspirit.org

 Can anybody play diablo 3 with wine on FreeBSD 9R amd64?

 Wine 1.5.4,1 64bit can't running Diablo III perhaps because of Agent.exe.

 see http://appdb.winehq.org/objectManager.php?sClass=versioniId=25953.

 Thanks!
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to 
 freebsd-questions-unsubscr...@freebsd.org




-- 
Lyubomir Grigorov (bgalakazam)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine-fbsd64 updated to 1.5.3 (32bit Wine for 64bit FreeBSD)

2012-05-07 Thread fidaj



--- Оригінальне повідомлення ---
Від кого: David Naylor naylor.b.da...@gmail.com
Кому: freebsd-emulat...@freebsd.org, freebsd-questions@freebsd.org
Дата: 7 травня 2012, 11:45:18
Тема: Wine-fbsd64 updated to 1.5.3 (32bit Wine for 64bit FreeBSD)





Hi,

Packages [1] for wine-fbsd64-1.5.3 have been uploaded to mediafire [2].  The 
packages for FreeBSD 10 use the pkgng* [3] format.  

There are many reports that wine does not work with a clang compiled world
(help in fixing this problem is appreciated as it affects quite a few users).

The patch [4] for nVidia users is now included in the package and is run on
installation (if the relevant files are accessible).  Please read the
installation messages for further information.

Regards,

David

[1]
MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.3,1.tbz) = 
0592e0b1226314a7061ef5745fa0e59f
MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.3,1.txz) = 
002e343a7bcb0cea7456422b75aec8f6
MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.3,1.txz) = 
1e7f52dadbd6808d48fa26923ab29f17
[2] http://www.mediafire.com/wine_fbsd64[3] http://wiki.freebsd.org/pkgng[4] 
The patch is located at /usr/local/share/wine/patch-nvidia.sh
[*] To install the port first fix the arch tag use the 'fix-arch.sh' script 
from mediafire [2]


root@nonamehost# pkg_add wine-fbsd64-1.5.3,1.txz
tar: +CONTENTS: Not found in archive
tar: Error exit delayed from previous errors.
pkg_add: tar extract of
/home/my_src/ports/wine-fbsd64/wine-fbsd64-1.5.3,1.txz failed!
pkg_add: unable to extract table of contents file from
'/home/my_src/ports/wine-fbsd64/wine-fbsd64-1.5.3,1.txz' - not a package?

md5

wine-1.5.x-freebsd10/wine-fbsd64-1.5.3,1.txz 


MD5 (wine-fbsd64-1.5.3,1.txz) = 1e7f52dadbd6808d48fa26923ab29f17
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine-fbsd64 updated to 1.5.3 (32bit Wine for 64bit FreeBSD)

2012-05-07 Thread David Naylor
On Monday, 7 May 2012 18:09:29 fidaj wrote:
 --- Оригінальне повідомлення ---
 Від кого: David Naylor naylor.b.da...@gmail.com
 Кому: freebsd-emulat...@freebsd.org, freebsd-questions@freebsd.org
 Дата: 7 травня 2012, 11:45:18
 Тема: Wine-fbsd64 updated to 1.5.3 (32bit Wine for 64bit FreeBSD)

 root@nonamehost# pkg_add wine-fbsd64-1.5.3,1.txz
 tar: +CONTENTS: Not found in archive
 tar: Error exit delayed from previous errors.
 pkg_add: tar extract of
 /home/my_src/ports/wine-fbsd64/wine-fbsd64-1.5.3,1.txz failed!
 pkg_add: unable to extract table of contents file from
 '/home/my_src/ports/wine-fbsd64/wine-fbsd64-1.5.3,1.txz' - not a package?
 
 md5
 
 wine-1.5.x-freebsd10/wine-fbsd64-1.5.3,1.txz
 
 MD5 (wine-fbsd64-1.5.3,1.txz) = 1e7f52dadbd6808d48fa26923ab29f17

To install wine-fbsd64 on FreeBSD 10 please do:
# make -C /usr/ports/ports-mgmt/pkg install clean
# sh fix-arch.sh wine-fbsd64-1.5.3,1.txz
# pkg add wine-fbsd64-1.5.3,1.txz

fix-arch.sh is available from mediafire.  

Regards


signature.asc
Description: This is a digitally signed message part.


Re: Wine-fbsd64 updated to 1.5.3 (32bit Wine for 64bit FreeBSD)

2012-05-07 Thread Ivan Klymenko
В Mon, 7 May 2012 21:04:46 +0200
David Naylor naylor.b.da...@gmail.com пишет:

 On Monday, 7 May 2012 18:09:29 fidaj wrote:
  --- Оригінальне повідомлення ---
  Від кого: David Naylor naylor.b.da...@gmail.com
  Кому: freebsd-emulat...@freebsd.org, freebsd-questions@freebsd.org
  Дата: 7 травня 2012, 11:45:18
  Тема: Wine-fbsd64 updated to 1.5.3 (32bit Wine for 64bit FreeBSD)
 
  root@nonamehost# pkg_add wine-fbsd64-1.5.3,1.txz
  tar: +CONTENTS: Not found in archive
  tar: Error exit delayed from previous errors.
  pkg_add: tar extract of
  /home/my_src/ports/wine-fbsd64/wine-fbsd64-1.5.3,1.txz failed!
  pkg_add: unable to extract table of contents file from
  '/home/my_src/ports/wine-fbsd64/wine-fbsd64-1.5.3,1.txz' - not a
  package?
  
  md5
  
  wine-1.5.x-freebsd10/wine-fbsd64-1.5.3,1.txz
  
  MD5 (wine-fbsd64-1.5.3,1.txz) = 1e7f52dadbd6808d48fa26923ab29f17
 
 To install wine-fbsd64 on FreeBSD 10 please do:
 # make -C /usr/ports/ports-mgmt/pkg install clean
 # sh fix-arch.sh wine-fbsd64-1.5.3,1.txz
 # pkg add wine-fbsd64-1.5.3,1.txz
 
 fix-arch.sh is available from mediafire.  
 
 Regards

Thanks!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine-fbsd64 updated to 1.4.rc6 (32bit Wine for 64bit FreeBSD)

2012-03-06 Thread Mehmet Erol Sanliturk
On Tue, Mar 6, 2012 at 12:36 AM, David Naylor naylor.b.da...@gmail.comwrote:

 On Tuesday, 6 March 2012 00:01:48 Mehmet Erol Sanliturk wrote:
  On Mon, Mar 5, 2012 at 3:00 PM, David Naylor
 naylor.b.da...@gmail.comwrote:
   On Monday, 5 March 2012 14:17:51 Mehmet Erol Sanliturk wrote:
On Mon, Mar 5, 2012 at 6:55 AM, David Naylor
  
   naylor.b.da...@gmail.comwrote:
 Please include the full error message, also could you please try
  
   running
  
 those apps in a clean wine prefix.
   
# pwd
/root/APPLY/PROGRAMS
   
# wine x.exe
   
err : module : LdrInitializeThunk Main exe initialization for
LF:\\APPLY\\PROGRAMS\\x.exe failed , status c017
  
   I have tried to reproduce the error on my side but was unable to.  The
   programs that I tested work without error.
 
  This means that there are additional parts in your system which they do
 not
  exist here .
  Such parts are not added by pkg_add wine-fbsd64 ... .
  I do not have any idea about which parts may be missing .

 It could also mean there are extra components on your computer that are
 interfering however using a clean wine prefix (as mentioned below) has
 ruled
 that out.

   I was expecting more output from wine...  Please see below about using
 a
   clean
   wine prefix.  Do you use the nvidia graphics driver?  If so please run
   (as root), and provide the output:
   # sh /usr/local/share/wine/patch-nvidia.sh
 
  There is NO nvidia grphics driver . It is Intel DG965WH main board with
 its
  integrated graphics driver .

 That eliminates my only other idea.

   If nothing fixes your problem then please submit a bug report at
   bugs.winehq.org.
  
I could not understand the phrase :
   
in a clean wine prefix .
  
   To run a program in a clean wine prefix do:
   env WINEPREFIX=/tmp/tmp_wine_prefix wine x.exe
 
  This is NOT changing the error message . Only drive become Z: .

 As mentioned above, eliminates possible extra components causing
 interference.

   You may need to use winetricks to install some support programs.
  
   Good luck
 
  winetricks could NOT be found .

 Please see http://wiki.winehq.org/winetricks for details about winetricks.


Thanks . After my message , I searched winetricks in Google , and find
its links .
I read its list . I think , it will not contain related parts , except ,
perhaps fonts  , comctl .

I have installed fonts , all dll files , run times  , without any effect on
the generated error message .



  I tried wine which is added by
 
  pkg_add -r wine
 
  from packages
 
  in FreeBSD 9.0 RELEASE i386 as it is installed .
 
  On the same programs , the message is the same with amd64 message .

 To clarify: you tried running the program under an i386 installation of
 FreeBSD and wine gave you the same problem?



Yes .

I am using the ( three ) programs in Windows XP continuously and they are
working in there very well .
They are compiled by Delphi .

Previously , in FreeBSD 7.x ( I think 7.0 or 7.1 ) i386 , I have used the
same programs under Wine successfully .



The previous downloads from

wine-fbsd64-1.3.16,1.txz , ...1.3.37,1 ... 1.4.r3,1 ... 1.4.r3,3

series did not work because of errors displayed .


I have tested wine-fbsd64-1.3.16,1.txz now once more .


When the last published one ( 1.4.r4,1 ) also gave error , I decided to
inform you .




 Also, has a previous version of wine ever worked for your program?  Could
 you
 try installing an older version of wine (the mediafire page contains wine
 releases going back to 1.3.16).

 Regards



Thank you very much .

Mehmet Erol Sanliturk
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine-fbsd64 updated to 1.4.rc6 (32bit Wine for 64bit FreeBSD)

2012-03-05 Thread Mehmet Erol Sanliturk
On Sun, Mar 4, 2012 at 2:16 PM, David Naylor naylor.b.da...@gmail.comwrote:

 Hi,

 Packages [1] for wine-fbsd64-1.4.rc6 have been uploaded to mediafire [2].

 There are many reports that wine does not work with a clang compiled world
 (help in fixing this problem is appreciated as it affects quite a few
 users).

 The patch [3] for nVidia users is now included in the package and is run on
 installation (if the relevant files are accessible).  Please read the
 installation messages for further information.

 Regards,

 David

 [1]
  MD5 (freebsd8/wine-fbsd64-1.4.rc6,1.tbz) =
 91bc2288130c25704c9f1ac9d2923a6a
  MD5 (freebsd9/wine-fbsd64-1.4.rc6,1.txz) =
 a57b6fed2401375562931f3516e1d50b
 [2] http://www.mediafire.com/wine_fbsd64
 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh



For any x.exe :

wine x.exe

is generating the following error :

err: module : LdrInitializeThunk Main exe initialization for LF:\\ ...
path ... \\x.exe failed ,
status c017

where x.exe is in the current directory ( path is correct )

in FreeBSD 9.0-RELEASE #0 ... GENERIC amd64


Thank you very much .


Mehmet Erol Sanliturk
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine-fbsd64 updated to 1.4.rc6 (32bit Wine for 64bit FreeBSD)

2012-03-05 Thread David Naylor
On 5 March 2012 13:41, Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote:
 On Sun, Mar 4, 2012 at 2:16 PM, David Naylor naylor.b.da...@gmail.com
 wrote:

 Hi,

 Packages [1] for wine-fbsd64-1.4.rc6 have been uploaded to mediafire [2].

 There are many reports that wine does not work with a clang compiled world
 (help in fixing this problem is appreciated as it affects quite a few
 users).

 The patch [3] for nVidia users is now included in the package and is run
 on
 installation (if the relevant files are accessible).  Please read the
 installation messages for further information.

 Regards,

 David

 [1]
  MD5 (freebsd8/wine-fbsd64-1.4.rc6,1.tbz) =
 91bc2288130c25704c9f1ac9d2923a6a
  MD5 (freebsd9/wine-fbsd64-1.4.rc6,1.txz) =
 a57b6fed2401375562931f3516e1d50b
 [2] http://www.mediafire.com/wine_fbsd64
 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh



 For any x.exe :

 wine x.exe

 is generating the following error :

 err: module : LdrInitializeThunk Main exe initialization for LF:\\ ... path
 ... \\x.exe failed ,
 status c017

Please include the full error message, also could you please try running
those apps in a clean wine prefix.

 where x.exe is in the current directory ( path is correct )

 in FreeBSD 9.0-RELEASE #0 ... GENERIC amd64

I will try reproduce this when I get $HOME.

Regards
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine-fbsd64 updated to 1.4.rc6 (32bit Wine for 64bit FreeBSD)

2012-03-05 Thread Mehmet Erol Sanliturk
On Mon, Mar 5, 2012 at 6:55 AM, David Naylor naylor.b.da...@gmail.comwrote:

 On 5 March 2012 13:41, Mehmet Erol Sanliturk m.e.sanlit...@gmail.com
 wrote:
  On Sun, Mar 4, 2012 at 2:16 PM, David Naylor naylor.b.da...@gmail.com
  wrote:
 
  Hi,
 
  Packages [1] for wine-fbsd64-1.4.rc6 have been uploaded to mediafire
 [2].
 
  There are many reports that wine does not work with a clang compiled
 world
  (help in fixing this problem is appreciated as it affects quite a few
  users).
 
  The patch [3] for nVidia users is now included in the package and is run
  on
  installation (if the relevant files are accessible).  Please read the
  installation messages for further information.
 
  Regards,
 
  David
 
  [1]
   MD5 (freebsd8/wine-fbsd64-1.4.rc6,1.tbz) =
  91bc2288130c25704c9f1ac9d2923a6a
   MD5 (freebsd9/wine-fbsd64-1.4.rc6,1.txz) =
  a57b6fed2401375562931f3516e1d50b
  [2] http://www.mediafire.com/wine_fbsd64
  [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh
 
 
 
  For any x.exe :
 
  wine x.exe
 
  is generating the following error :
 
  err: module : LdrInitializeThunk Main exe initialization for LF:\\ ...
 path
  ... \\x.exe failed ,
  status c017

 Please include the full error message, also could you please try running
 those apps in a clean wine prefix.



# pwd
/root/APPLY/PROGRAMS


# ls -l

-rw-r--r-- 1 root wheel 5491200 Feb 17 22:27 x.exe

# wine x.exe

err : module : LdrInitializeThunk Main exe initialization for
LF:\\APPLY\\PROGRAMS\\x.exe failed , status c017

--

The whole message is listed above .
Desktop environment is KDE4 .
Execution is attempted in Konsole Terminal .
In GNOME Terminal in KDE4 , the error message is the same .

I could not understand the phrase :


in a clean wine prefix .

-



  where x.exe is in the current directory ( path is correct )
 
  in FreeBSD 9.0-RELEASE #0 ... GENERIC amd64

 I will try reproduce this when I get $HOME.

 Regards



Thank you very much .

Mehmet Erol Sanliturk
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine-fbsd64 updated to 1.4.rc6 (32bit Wine for 64bit FreeBSD)

2012-03-05 Thread David Naylor
On Monday, 5 March 2012 14:17:51 Mehmet Erol Sanliturk wrote:
 On Mon, Mar 5, 2012 at 6:55 AM, David Naylor 
naylor.b.da...@gmail.comwrote:
  Please include the full error message, also could you please try running
  those apps in a clean wine prefix.
 
 # pwd
 /root/APPLY/PROGRAMS
 
 # wine x.exe
 
 err : module : LdrInitializeThunk Main exe initialization for
 LF:\\APPLY\\PROGRAMS\\x.exe failed , status c017

I have tried to reproduce the error on my side but was unable to.  The 
programs that I tested work without error.  

I was expecting more output from wine...  Please see below about using a clean 
wine prefix.  Do you use the nvidia graphics driver?  If so please run (as 
root), and provide the output:
# sh /usr/local/share/wine/patch-nvidia.sh

If nothing fixes your problem then please submit a bug report at 
bugs.winehq.org.  


 I could not understand the phrase :
 
 in a clean wine prefix .

To run a program in a clean wine prefix do:
env WINEPREFIX=/tmp/tmp_wine_prefix wine x.exe

You may need to use winetricks to install some support programs.  

Good luck


signature.asc
Description: This is a digitally signed message part.


Re: Wine-fbsd64 updated to 1.4.rc6 (32bit Wine for 64bit FreeBSD)

2012-03-05 Thread Mehmet Erol Sanliturk
On Mon, Mar 5, 2012 at 3:00 PM, David Naylor naylor.b.da...@gmail.comwrote:

 On Monday, 5 March 2012 14:17:51 Mehmet Erol Sanliturk wrote:
  On Mon, Mar 5, 2012 at 6:55 AM, David Naylor
 naylor.b.da...@gmail.comwrote:
   Please include the full error message, also could you please try
 running
   those apps in a clean wine prefix.
 
  # pwd
  /root/APPLY/PROGRAMS
 
  # wine x.exe
 
  err : module : LdrInitializeThunk Main exe initialization for
  LF:\\APPLY\\PROGRAMS\\x.exe failed , status c017

 I have tried to reproduce the error on my side but was unable to.  The
 programs that I tested work without error.


This means that there are additional parts in your system which they do not
exist here .
Such parts are not added by pkg_add wine-fbsd64 ... .
I do not have any idea about which parts may be missing .



 I was expecting more output from wine...  Please see below about using a
 clean
 wine prefix.  Do you use the nvidia graphics driver?  If so please run (as
 root), and provide the output:
 # sh /usr/local/share/wine/patch-nvidia.sh



There is NO nvidia grphics driver . It is Intel DG965WH main board with its
integrated graphics driver .



 If nothing fixes your problem then please submit a bug report at
 bugs.winehq.org.


  I could not understand the phrase :
 
  in a clean wine prefix .

 To run a program in a clean wine prefix do:
 env WINEPREFIX=/tmp/tmp_wine_prefix wine x.exe


This is NOT changing the error message . Only drive become Z: .




 You may need to use winetricks to install some support programs.

 Good luck



winetricks could NOT be found .



I tried wine which is added by

pkg_add -r wine

from packages

in FreeBSD 9.0 RELEASE i386 as it is installed .


On the same programs , the message is the same with amd64 message .



Thank you very much .

Mehmet Erol Sanliturk
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine-fbsd64 updated to 1.4.rc6 (32bit Wine for 64bit FreeBSD)

2012-03-05 Thread David Naylor
On Tuesday, 6 March 2012 00:01:48 Mehmet Erol Sanliturk wrote:
 On Mon, Mar 5, 2012 at 3:00 PM, David Naylor 
naylor.b.da...@gmail.comwrote:
  On Monday, 5 March 2012 14:17:51 Mehmet Erol Sanliturk wrote:
   On Mon, Mar 5, 2012 at 6:55 AM, David Naylor
  
  naylor.b.da...@gmail.comwrote:
Please include the full error message, also could you please try
  
  running
  
those apps in a clean wine prefix.
   
   # pwd
   /root/APPLY/PROGRAMS
   
   # wine x.exe
   
   err : module : LdrInitializeThunk Main exe initialization for
   LF:\\APPLY\\PROGRAMS\\x.exe failed , status c017
  
  I have tried to reproduce the error on my side but was unable to.  The
  programs that I tested work without error.
 
 This means that there are additional parts in your system which they do not
 exist here .
 Such parts are not added by pkg_add wine-fbsd64 ... .
 I do not have any idea about which parts may be missing .

It could also mean there are extra components on your computer that are 
interfering however using a clean wine prefix (as mentioned below) has ruled 
that out.  

  I was expecting more output from wine...  Please see below about using a
  clean
  wine prefix.  Do you use the nvidia graphics driver?  If so please run
  (as root), and provide the output:
  # sh /usr/local/share/wine/patch-nvidia.sh
 
 There is NO nvidia grphics driver . It is Intel DG965WH main board with its
 integrated graphics driver .

That eliminates my only other idea.  

  If nothing fixes your problem then please submit a bug report at
  bugs.winehq.org.
  
   I could not understand the phrase :
   
   in a clean wine prefix .
  
  To run a program in a clean wine prefix do:
  env WINEPREFIX=/tmp/tmp_wine_prefix wine x.exe
 
 This is NOT changing the error message . Only drive become Z: .

As mentioned above, eliminates possible extra components causing interference.  

  You may need to use winetricks to install some support programs.
  
  Good luck
 
 winetricks could NOT be found .

Please see http://wiki.winehq.org/winetricks for details about winetricks.  

 I tried wine which is added by
 
 pkg_add -r wine
 
 from packages
 
 in FreeBSD 9.0 RELEASE i386 as it is installed .
 
 On the same programs , the message is the same with amd64 message .

To clarify: you tried running the program under an i386 installation of 
FreeBSD and wine gave you the same problem?  

Also, has a previous version of wine ever worked for your program?  Could you 
try installing an older version of wine (the mediafire page contains wine 
releases going back to 1.3.16).  

Regards


signature.asc
Description: This is a digitally signed message part.


Re: Wine-fbsd64 updated to 1.3.31 (32bit Wine for 64bit FreeBSD)

2011-11-02 Thread David Naylor
Hi,

I have fixed an issue where the integrated nVidia patch failed to install or 
run as expected.  The packages [4] have been uploaded and replaced the old 
packages.  

Only if you are a nVidia user who has been unable to get wine-1.3.31 working 
would you need to download and install the updated packages.  

Lastly, there are reports that wine does not work with a clang built world.  

Regards,

David
[4]
  MD5 (freebsd8/wine-fbsd64-1.3.31,1.tbz) = e38e694dc55a99882c137d0f11b4eb9e
  MD5 (freebsd9/wine-fbsd64-1.3.31,1.txz) = 59ec8c1b68e3eb12f4b2c97674d0d563

On Tuesday, 25 October 2011 18:52:40 David Naylor wrote:
 Hi,
 
 Packages [1] for wine-fbsd64-1.3.31 have been uploaded to mediafire [2] and
 the wine-fbsd64.diff patch has been updated.  There is a known UDP related
 problem with wine (see http://markmail.org/message/i7rtfz7uxd5s4fvl for
 details).
 
 To date there has been 1217 (+70) downloads from mediafire.
 
 The patch [3] for nVidia users is now included in the package and is run on
 installation (if the relevant files are accessable).  Please read the
 installation messages for further information.
 
 Regards,
 
 David
 [1]
   MD5 (freebsd8/wine-fbsd64-1.3.31,1.tbz) =
 3ada791cc70a692b71f331a9b658d0ce MD5 (freebsd9/wine-fbsd64-1.3.31,1.txz) =
 7b9f0b9a122646822542e540aeed09e5 [2] http://www.mediafire.com/wine_fbsd64
 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh


signature.asc
Description: This is a digitally signed message part.


Re: Wine-fbsd64 updated to 1.3.31 (32bit Wine for 64bit FreeBSD)

2011-10-30 Thread Romain Garbage
2011/10/25 David Naylor naylor.b.da...@gmail.com:
 Hi,

Hi,

 Packages [1] for wine-fbsd64-1.3.31 have been uploaded to mediafire [2] and
 the wine-fbsd64.diff patch has been updated.  There is a known UDP related
 problem with wine (see http://markmail.org/message/i7rtfz7uxd5s4fvl for
 details).

 To date there has been 1217 (+70) downloads from mediafire.

 The patch [3] for nVidia users is now included in the package and is run on
 installation (if the relevant files are accessable).  Please read the
 installation messages for further information.

$ sudo pkg_add Downloads/wine-fbsd64-1.3.31,1.txz
tar: /usr/local/share/wine/patch-nvidia.sh: Cannot stat: No such file
or directory
tar: Error exit delayed from previous errors.
A NVIDIA GRAPHICS DRIVER HAS BEEN DETECTED ON THIS SYSTEM AND THE AUTOMATED
PATCHING HAS FAILED, execute (as root)
sh /usr/local/share/wine/patch-nvidia.sh
to get 2D/3D acceleration to work with the nvidia driver.  Without this wine
will crash when a program requires 2D/3D graphics acceleration.
[...]

$ file /usr/local/share/wine/patch-nvidia.sh
/usr/local/share/wine/patch-nvidia.sh: cannot open
`/usr/local/share/wine/patch-nvidia.sh' (No such file or directory)

$ tar tf Downloads/wine-fbsd64-1.3.31,1.txz | grep -C 2 nvidia
bin32/wmc
bin32/wrc
usr/local/share/wine/patch-nvidia.sh
share/wine/fonts/coue1255.fon
share/wine/fonts/coue1256.fon

The problem here seems to be the trailing usr/local/ for
patch-nvidia.sh file, which get actually installed into
$PREFIX/usr/local/share/wine instead of $PREFIX/share/wine

Regards,
Romain

PD: I used the fbsd9 package. md5 is ok.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine-fbsd64 updated to 1.3.31 (32bit Wine for 64bit FreeBSD)

2011-10-30 Thread David Naylor
Hi Romain,

Thank you for the report.  I will address this over the coming week
and update the
packages.

In the interim, the packages will work for both nvidia and non-nvidia users
except nvidia users will need to run patch-nvidia-wine.sh (from mediafire)
manually...

Regards

On 30 October 2011 13:07, Romain Garbage romain.garb...@gmail.com wrote:
 2011/10/25 David Naylor naylor.b.da...@gmail.com:
 Hi,

 Hi,

 Packages [1] for wine-fbsd64-1.3.31 have been uploaded to mediafire [2] and
 the wine-fbsd64.diff patch has been updated.  There is a known UDP related
 problem with wine (see http://markmail.org/message/i7rtfz7uxd5s4fvl for
 details).

 To date there has been 1217 (+70) downloads from mediafire.

 The patch [3] for nVidia users is now included in the package and is run on
 installation (if the relevant files are accessable).  Please read the
 installation messages for further information.

 $ sudo pkg_add Downloads/wine-fbsd64-1.3.31,1.txz
 tar: /usr/local/share/wine/patch-nvidia.sh: Cannot stat: No such file
 or directory
 tar: Error exit delayed from previous errors.
 A NVIDIA GRAPHICS DRIVER HAS BEEN DETECTED ON THIS SYSTEM AND THE AUTOMATED
 PATCHING HAS FAILED, execute (as root)
        sh /usr/local/share/wine/patch-nvidia.sh
 to get 2D/3D acceleration to work with the nvidia driver.  Without this wine
 will crash when a program requires 2D/3D graphics acceleration.
 [...]

 $ file /usr/local/share/wine/patch-nvidia.sh
 /usr/local/share/wine/patch-nvidia.sh: cannot open
 `/usr/local/share/wine/patch-nvidia.sh' (No such file or directory)

 $ tar tf Downloads/wine-fbsd64-1.3.31,1.txz | grep -C 2 nvidia
 bin32/wmc
 bin32/wrc
 usr/local/share/wine/patch-nvidia.sh
 share/wine/fonts/coue1255.fon
 share/wine/fonts/coue1256.fon

 The problem here seems to be the trailing usr/local/ for
 patch-nvidia.sh file, which get actually installed into
 $PREFIX/usr/local/share/wine instead of $PREFIX/share/wine

 Regards,
 Romain

 PD: I used the fbsd9 package. md5 is ok.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine-fbsd64 updated to 1.3.29 (32bit Wine for 64bit FreeBSD)

2011-10-18 Thread Любомир Григоров
version 1.30.1 fixed the no fonts issue in Steam source games. Thank you for
porting and keep up the good work


-- 
Lyubomir Grigorov (bgalakazam)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine questions

2011-02-16 Thread Warren Block

On Wed, 16 Feb 2011, Fred wrote:

...
There's a downloadable version of the software on the site.  If that works 
acceptably, the final hurdle would be whether it can communicate with the 
programmer by USB.  The site says it's USB 2.0 and installs drivers on 
Windows, which doesn't bode well for the Wine/FreeBSD setup. It may work, 
although you have to expect that any support call will blame problems on 
the non-standard setup.

...

I downloaded the programmer software and wine installed it without any 
problems (350 MB!).  The software seems to run ok so far under wine.  So the 
remaining issue is the USB connection.  I found the USB port in /dev but to 
make the link I also need to know what Windows calls the USB port so the 
programmer software can find it.  If one plugs a non-storage USB device into 
Windows without installing any specific driver, what does Windows call the 
USB port?


If the device shows up as a USB serial port (/dev/cuaU0) , it can be 
linked to a Wine com port, as shown here: 
http://wiki.freebsd.org/AVR/ArduinoWINE


Don't know about other types of devices.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine questions

2011-02-16 Thread Fred

On 01/27/11 20:47, Warren Block wrote:

On Thu, 27 Jan 2011, Fred wrote:


I am interested in the Xeltek SuperPro-5000.  This unit will alsowork 
stand-alone with a CF card programmed by the PC in addition to usb.  
I believe the user software downloads a set of programming parameters 
and the file to be programmed rather than driving the programmer 
directly or otherwise do low level hardware stuff.  I am going to ask 
Xeltek if they will give a refund if I can't get the unit working in 
a reasonable time.  If it doesn't work I would otherwise be out of 
$1500.  I will not use Windows.


There's a downloadable version of the software on the site.  If that 
works acceptably, the final hurdle would be whether it can communicate 
with the programmer by USB.  The site says it's USB 2.0 and installs 
drivers on Windows, which doesn't bode well for the Wine/FreeBSD 
setup. It may work, although you have to expect that any support call 
will blame problems on the non-standard setup.


It might be easier to start with open software and choose a programmer 
that is supported by it.  For instance, devel/avrdude supports some 
faster programmers.  Depends on what you need.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
freebsd-questions-unsubscr...@freebsd.org




I downloaded the programmer software and wine installed it without any 
problems (350 MB!).  The software seems to run ok so far under wine.  So 
the remaining issue is the USB connection.  I found the USB port in /dev 
but to make the link I also need to know what Windows calls the USB port 
so the programmer software can find it.  If one plugs a non-storage USB 
device into Windows without installing any specific driver, what does 
Windows call the USB port?

Best regards,
Fred

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine questions

2011-01-28 Thread Mike Clarke
On Thursday 27 January 2011, Yuri Pankov wrote:

 On Thu, Jan 27, 2011 at 10:50:31PM +, Mike Clarke wrote:

[snip]

  But VirtualBox OSE doesn't support USB.

 VirtualBox 4 *seems* to support USB (I have the option in the GUI,
 haven't tried it though). It's available for testing from
 http://svn.bluelife.at/ at the moment.

That's very welcome news. I have a USB printer (Canon iP4500) which 
works very well with FreeBSD as far as printing is concerned but it's a 
bit of a pain having to move it over to a Windows PC if I want to run 
any of the utilities like checking ink levels or head cleaning. USB 
support with VirtualBox would be very useful for that.

I'm usually rather hesitant when it comes to experimenting 
with 'bleeding edge' versions of software but I'm seriously tempted to 
give this one a try.

-- 
Mike Clarke
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine questions

2011-01-28 Thread Fred

Warren Block wrote:

On Thu, 27 Jan 2011, Fred wrote:


I am interested in the Xeltek SuperPro-5000.  This unit will alsowork 
stand-alone with a CF card programmed by the PC in addition to usb.  
I believe the user software downloads a set of programming parameters 
and the file to be programmed rather than driving the programmer 
directly or otherwise do low level hardware stuff.  I am going to ask 
Xeltek if they will give a refund if I can't get the unit working in 
a reasonable time.  If it doesn't work I would otherwise be out of 
$1500.  I will not use Windows.


There's a downloadable version of the software on the site.  If that 
works acceptably, the final hurdle would be whether it can communicate 
with the programmer by USB.  The site says it's USB 2.0 and installs 
drivers on Windows, which doesn't bode well for the Wine/FreeBSD 
setup. It may work, although you have to expect that any support call 
will blame problems on the non-standard setup.


It might be easier to start with open software and choose a programmer 
that is supported by it.  For instance, devel/avrdude supports some 
faster programmers.  Depends on what you need.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
freebsd-questions-unsubscr...@freebsd.org





Hi Warren,
I will try installing the Xeltek software as you suggest and go from 
there.  If I get it to work ok I will post what I did.


I use 680x0 and 8051 so the avr program isn't useful at this time.  I 
need to program SPLDs and flash.


Best regards,
Fred
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine questions

2011-01-27 Thread Jarrod Slick

On 1/27/11 11:48 AM, Fred wrote:

Hello,

I need to buy an expensive logic device programmer that connects to a 
PC through USB.  Unfortunately, the user software that make it go only 
runs on Bill Gates' cancerous, virus-infested, scourge of the Earth 
excuse for an OS which I do not use.  Is it likely to work ok using 
wine?  What type of programs do not work well with wine?  There is a 
supported, commercial version of wine that runs on Linux.  Would I be 
better off buying that and running it on the FBSD Linux emulation?


Best regards,
Fred

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
freebsd-questions-unsubscr...@freebsd.org
Chaining emulators just sounds like a bad idea; I would guess that your 
risk of complications increases exponentially when doing this, and I 
would bet anything that your performance decreases exponentially as 
well.  Also, I doubt the company that sells the commercial version of 
wine would support their software when running on untested platforms 
(e.g., FBSD w/ Linux Emulation).  Further, that company probably has a 
list of supported software and won't vouch for their product's ability 
to run anything outside of that list.


If you absolutely must run it under a *nix, I would go with Linux for 
this project.


If you'd set dogma aside, though, you would probably see that Windows is 
your best bet for this project.  A close second (if you had all the time 
in the world) would be writing drivers yourself for your desired platform.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine questions

2011-01-27 Thread Pierre-Luc Drouin
Linux emulation on FreeBSD is not really emulation, in the sense that it
does not create virtual hardware. Some linux softwares run even faster on
FreeBSD than Linux... My worry would be more to make sure that USB
communication works through the emulation layers...

On Thu, Jan 27, 2011 at 2:08 PM, Jarrod Slick jarrod...@gmail.com wrote:

 On 1/27/11 11:48 AM, Fred wrote:

 Hello,

 I need to buy an expensive logic device programmer that connects to a PC
 through USB.  Unfortunately, the user software that make it go only runs on
 Bill Gates' cancerous, virus-infested, scourge of the Earth excuse for an OS
 which I do not use.  Is it likely to work ok using wine?  What type of
 programs do not work well with wine?  There is a supported, commercial
 version of wine that runs on Linux.  Would I be better off buying that and
 running it on the FBSD Linux emulation?

 Best regards,
 Fred

 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to 
 freebsd-questions-unsubscr...@freebsd.org

 Chaining emulators just sounds like a bad idea; I would guess that your
 risk of complications increases exponentially when doing this, and I would
 bet anything that your performance decreases exponentially as well.  Also, I
 doubt the company that sells the commercial version of wine would support
 their software when running on untested platforms (e.g., FBSD w/ Linux
 Emulation).  Further, that company probably has a list of supported software
 and won't vouch for their product's ability to run anything outside of that
 list.

 If you absolutely must run it under a *nix, I would go with Linux for this
 project.

 If you'd set dogma aside, though, you would probably see that Windows is
 your best bet for this project.  A close second (if you had all the time in
 the world) would be writing drivers yourself for your desired platform.
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to 
 freebsd-questions-unsubscr...@freebsd.org

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine questions

2011-01-27 Thread Dmitri Brengauz
On Thu, Jan 27, 2011 at 11:48 AM, Fred f...@blakemfg.com wrote:

 Hello,

 I need to buy an expensive logic device programmer that connects to a PC
 through USB.  Unfortunately, the user software that make it go only runs on
 Bill Gates' cancerous, virus-infested, scourge of the Earth excuse for an OS
 which I do not use.  Is it likely to work ok using wine?  What type of
 programs do not work well with wine?  There is a supported, commercial
 version of wine that runs on Linux.  Would I be better off buying that and
 running it on the FBSD Linux emulation?

 Best regards,
 Fred

 ___
  freebsd-questions@freebsd.org


Have you tried VirtualBox?   You still have to shell out for a Windows
license, but at least the Gates virus will be contained securely on your
computer.  For me, Virtual Box + FreeBSD has been running better than VMWare
+ OS X.  Once again, free software, more than worth the price.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine questions

2011-01-27 Thread Julian H. Stacey
Fred wrote:
 Hello,
 
 I need to buy an expensive logic device programmer that connects to a PC 
 through USB.  Unfortunately, the user software that make it go only runs 
 on Bill Gates' cancerous, virus-infested, scourge of the Earth excuse 
 for an OS which I do not use.  Is it likely to work ok using wine?  What 
 type of programs do not work well with wine?  There is a supported, 
 commercial version of wine that runs on Linux.  Would I be better off 
 buying that and running it on the FBSD Linux emulation?
 
 Best regards,
 Fred

FreeBSD has a special list for this topic:
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
PS main issue might be USB support within emulators from what I've read.

ALL,
Note FreeBSD has Lots of lists:   http://lists.freebsd.org/mailman/listinfo
Questions@ is/was for general simple beginners questions IMO, some
traffic here belongs on other more advanced lists.  Decide yourself,
browse the list above, click a few  read list remits.

Cheers,
Julian
-- 
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
 Mail plain text;  Not quoted-printable, Not HTML, Not base 64.
 Reply below text sections not at top, to avoid breaking cumulative context.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine questions

2011-01-27 Thread Warren Block

On Thu, 27 Jan 2011, Fred wrote:

I need to buy an expensive logic device programmer that connects to a PC 
through USB.  Unfortunately, the user software that make it go only runs on 
Bill Gates' cancerous, virus-infested, scourge of the Earth excuse for an OS 
which I do not use.  Is it likely to work ok using wine?  What type of 
programs do not work well with wine?  There is a supported, commercial 
version of wine that runs on Linux.  Would I be better off buying that and 
running it on the FBSD Linux emulation?


If you were to be more specific about the device you're considering, 
someone may be able to suggest specifics.


Sometimes Wine is surprising.  This was the case when I managed to run 
the Arduino software on Wine under FreeBSD.  That software speaks to the 
microcontroller via serial or USB-to-serial:


http://wiki.freebsd.org/AVR/ArduinoWINE

If your device speaks serial like that, it might work well.  If it wants 
to do low-level hardware or anything uncommon, it probably will not 
work in Wine.


If you have to get the device anyway, there's little harm in trying it 
on Wine.  If it doesn't work, you've lost nothing but time, and probably 
not much of that.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine questions

2011-01-27 Thread Mike Clarke
On Thursday 27 January 2011, Dmitri Brengauz wrote:

 On Thu, Jan 27, 2011 at 11:48 AM, Fred f...@blakemfg.com wrote:
  Hello,
 
  I need to buy an expensive logic device programmer that connects to
  a PC through USB.

[snip]

 Have you tried VirtualBox?   You still have to shell out for a
 Windows license, but at least the Gates virus will be contained
 securely on your computer.  For me, Virtual Box + FreeBSD has been
 running better than VMWare + OS X.  Once again, free software, more
 than worth the price.

But VirtualBox OSE doesn't support USB.

-- 
Mike Clarke
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine questions

2011-01-27 Thread George Liaskos
 But VirtualBox OSE doesn't support USB.

VirtualBox 4 does.

http://www.virtualbox.org/changeset/33813
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine questions

2011-01-27 Thread Yuri Pankov
On Thu, Jan 27, 2011 at 10:50:31PM +, Mike Clarke wrote:
 On Thursday 27 January 2011, Dmitri Brengauz wrote:
 
  On Thu, Jan 27, 2011 at 11:48 AM, Fred f...@blakemfg.com wrote:
   Hello,
  
   I need to buy an expensive logic device programmer that connects to
   a PC through USB.
 
 [snip]
 
  Have you tried VirtualBox?   You still have to shell out for a
  Windows license, but at least the Gates virus will be contained
  securely on your computer.  For me, Virtual Box + FreeBSD has been
  running better than VMWare + OS X.  Once again, free software, more
  than worth the price.
 
 But VirtualBox OSE doesn't support USB.

VirtualBox 4 *seems* to support USB (I have the option in the GUI,
haven't tried it though). It's available for testing from
http://svn.bluelife.at/ at the moment.

 
 -- 
 Mike Clarke


HTH,
Yuri
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine questions

2011-01-27 Thread Fred

Warren Block wrote:

On Thu, 27 Jan 2011, Fred wrote:

I need to buy an expensive logic device programmer that connects to a 
PC through USB.  Unfortunately, the user software that make it go 
only runs on Bill Gates' cancerous, virus-infested, scourge of the 
Earth excuse for an OS which I do not use.  Is it likely to work ok 
using wine?  What type of programs do not work well with wine?  There 
is a supported, commercial version of wine that runs on Linux.  Would 
I be better off buying that and running it on the FBSD Linux emulation?


If you were to be more specific about the device you're considering, 
someone may be able to suggest specifics.


Sometimes Wine is surprising.  This was the case when I managed to run 
the Arduino software on Wine under FreeBSD.  That software speaks to 
the microcontroller via serial or USB-to-serial:


http://wiki.freebsd.org/AVR/ArduinoWINE

If your device speaks serial like that, it might work well.  If it 
wants to do low-level hardware or anything uncommon, it probably will 
not work in Wine.


If you have to get the device anyway, there's little harm in trying it 
on Wine.  If it doesn't work, you've lost nothing but time, and 
probably not much of that.




I am interested in the Xeltek SuperPro-5000.  This unit will alsowork 
stand-alone with a CF card programmed by the PC in addition to usb.  I 
believe the user software downloads a set of programming parameters and 
the file to be programmed rather than driving the programmer directly or 
otherwise do low level hardware stuff.  I am going to ask Xeltek if they 
will give a refund if I can't get the unit working in a reasonable 
time.  If it doesn't work I would otherwise be out of $1500.  I will not 
use Windows.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: wine questions

2011-01-27 Thread Warren Block

On Thu, 27 Jan 2011, Fred wrote:


I am interested in the Xeltek SuperPro-5000.  This unit will alsowork 
stand-alone with a CF card programmed by the PC in addition to usb.  I 
believe the user software downloads a set of programming parameters and the 
file to be programmed rather than driving the programmer directly or 
otherwise do low level hardware stuff.  I am going to ask Xeltek if they will 
give a refund if I can't get the unit working in a reasonable time.  If it 
doesn't work I would otherwise be out of $1500.  I will not use Windows.


There's a downloadable version of the software on the site.  If that 
works acceptably, the final hurdle would be whether it can communicate 
with the programmer by USB.  The site says it's USB 2.0 and installs 
drivers on Windows, which doesn't bode well for the Wine/FreeBSD setup. 
It may work, although you have to expect that any support call will 
blame problems on the non-standard setup.


It might be easier to start with open software and choose a programmer 
that is supported by it.  For instance, devel/avrdude supports some 
faster programmers.  Depends on what you need.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: WINE on 6.3

2009-12-11 Thread Andrea Venturoli

Andrea Venturoli ha scritto:

Tijl Coosemans ha scritto:

On Saturday 05 December 2009 13:47:00 Andrea Venturoli wrote:

Is WINE usable on 6.3/i386?
I cannot seem to start any win32 program and before I spend time into
it, I thought I just ask.


You probably need the FreeBSD 6.x patch at http://wiki.freebsd.org/Wine



Unfortunately this didn't help.

WINE is still seems to be hogging the CPU and doing nothing.


I did some more testing.
I've got 3 machines: the one I'm working on, running the X server and 
two boxes which I ssh into.

All three are running 6.3/i386, the same version of Wine and dependencies.
Wine works fine if I start it on the machine where the X server is, but 
exhibits the afore mentioned problems if I run it on the box I ssh into.

Of course X forwarding is working (tested with a lot of other applications).
So I ask: is this a known problem? Has anyone Wine working with X11 
forwarded through ssh?


 bye  Thanks
av.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: WINE on 6.3

2009-12-07 Thread Tijl Coosemans
On Saturday 05 December 2009 13:47:00 Andrea Venturoli wrote:
 Is WINE usable on 6.3/i386?
 I cannot seem to start any win32 program and before I spend time into
 it, I thought I just ask.

You probably need the FreeBSD 6.x patch at http://wiki.freebsd.org/Wine
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: WINE on 6.3

2009-12-07 Thread Andrea Venturoli

Tijl Coosemans ha scritto:

On Saturday 05 December 2009 13:47:00 Andrea Venturoli wrote:

Is WINE usable on 6.3/i386?
I cannot seem to start any win32 program and before I spend time into
it, I thought I just ask.


You probably need the FreeBSD 6.x patch at http://wiki.freebsd.org/Wine



Unfortunately this didn't help.

WINE is still seems to be hogging the CPU and doing nothing.


 bye  Thanks
av.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: WINE on 6.3

2009-12-05 Thread Gary Gatten
I can't speak to if WINE will work or nor, but if the app is so simple why not 
use a native bsd/*nix app?

- Original Message -
From: owner-freebsd-questi...@freebsd.org owner-freebsd-questi...@freebsd.org
To: freebsd-questions@freebsd.org freebsd-questions@freebsd.org
Sent: Sat Dec 05 06:47:00 2009
Subject: WINE on 6.3

Hello.
Is WINE usable on 6.3/i386?
I cannot seem to start any win32 program and before I spend time into 
it, I thought I just ask.

My interest is almost limited to running a simple console app that does 
very litte beyond reading a text file, processing it, and outputting 
another text file.

  bye  Thanks
av.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org





font size=1
div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 
1.0pt 0in'
/div
This email is intended to be reviewed by only the intended recipient
 and may contain information that is privileged and/or confidential.
 If you are not the intended recipient, you are hereby notified that
 any review, use, dissemination, disclosure or copying of this email
 and its attachments, if any, is strictly prohibited.  If you have
 received this email in error, please immediately notify the sender by
 return email and delete this email from your system.
/font

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: WINE on 6.3

2009-12-05 Thread RW
On Sat, 05 Dec 2009 13:47:00 +0100
Andrea Venturoli m...@netfence.it wrote:

 Hello.
 Is WINE usable on 6.3/i386?
 I cannot seem to start any win32 program and before I spend time into 
 it, I thought I just ask.
 
 My interest is almost limited to running a simple console app that
 does very litte beyond reading a text file, processing it, and
 outputting another text file.

It's think it's possible that the p13 update no zero mapping might
have an affect on windows/dos programs.

For win32 console applications try using wineconsole, if you aren't
already. If your app is a DOS application you would be better-off with
dosbox.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: WINE on 6.3

2009-12-05 Thread Andrea Venturoli

Gary Gatten ha scritto:
I can't speak to if WINE will work or nor, but if the app is so simple 
why not use a native bsd/*nix app?


Because it doesn't exist and, even if it did, I have to use *that* app, 
not an equivalent one.


 bye
av.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: WINE on 6.3

2009-12-05 Thread Andrea Venturoli

RW ha scritto:


For win32 console applications try using wineconsole, if you aren't
already.


I've tried both, but both seem to hang with CPU at 100%, doing nothing.




If your app is a DOS application you would be better-off with
dosbox.


DosBox works as a charm, but this app is Win32.



 bye  Thanks
av.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: WINE on 6.3

2009-12-05 Thread Michael Powell
RW wrote:

 On Sat, 05 Dec 2009 13:47:00 +0100
 Andrea Venturoli m...@netfence.it wrote:
 
 Hello.
 Is WINE usable on 6.3/i386?
 I cannot seem to start any win32 program and before I spend time into
 it, I thought I just ask.
 
 My interest is almost limited to running a simple console app that
 does very litte beyond reading a text file, processing it, and
 outputting another text file.
 
 It's think it's possible that the p13 update no zero mapping might
 have an affect on windows/dos programs.
 
[snip]

Not sure this is present in 6.3, so check first. A quick sysctl 
security.bsd.map_at_zero will return a value of 0 if present. As RW 
indicated it may have been included in the p13 update. 

To elaborate a little, you may need to toggle the security.bsd.map_at_zero: 
0 MIB. Change this to 1 to disable, not sure if loader.conf or sysctl.conf 
is the right place. Would be better not to have to do this because leaving 
it enabled is a security feature. However, WINE may not run without it.

I'm also not sure if the following is related, I just recall reading about 
it at in the same time frame and mostly with regard to Samba. Possibly there 
is a need to place CONFIGURE_ARGS+= --disable-pie in make.conf and recompile 
WINE. This may not apply to WINE at all so if the MIB config mentioned above 
fixes the situation do not proceed with this. I suspect wrt to WINE this is 
irrelevant, but thought I'd mention it anyway.

Should you discover --disable-pie is required leaving it present in 
make.conf is not a very satisfactory arrangement, as it would then apply to 
all ports. Workaround would be to place it just for WINE recompile if 
absolutely necessary and then comment it out when done.

-Mike


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine on FBSD-7.0 amd64. Does it run?

2009-07-09 Thread Adam Vande More
On Wed, Jul 8, 2009 at 9:32 AM, kxorrao luizbcam...@gmail.com wrote:

What port of wine should I download in order to play 32bit .exe
 files on FreeBSD-7.0 amd64? Linux wine or Wine?


It's not a terribly big port.  Compile it and check.  Generally if there are
problems with port on a specific platform, it will not build.  Use regular
wine/avoid emulators within emulators if at all possible.

-- 
Adam Vande More
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine on FBSD-7.0 amd64. Does it run?

2009-07-09 Thread Roland Smith
On Thu, Jul 09, 2009 at 01:10:58AM -0500, Adam Vande More wrote:
 On Wed, Jul 8, 2009 at 9:32 AM, kxorrao luizbcam...@gmail.com wrote:
 
 What port of wine should I download in order to play 32bit .exe
  files on FreeBSD-7.0 amd64? Linux wine or Wine?
 
 
 It's not a terribly big port.  Compile it and check.  Generally if there are
 problems with port on a specific platform, it will not build.  Use regular
 wine/avoid emulators within emulators if at all possible.

The wine port only works on i386:

# grep ARCHS /usr/ports/emulators/wine/Makefile
ONLY_FOR_ARCHS= i386

If I understood correctly, the problem is that wine is a 32-bit
program. See http://wiki.winehq.org/WineOn64bit

It would need 32-bit versions of all the libraries that it uses. The
FreeBSD ports system doesn't currently isn't equipped to handle
this. Not that this would be impossible, but nobody has bothered. 

The concensus seems (and rightly so IMHO) to be that development effort
is better spent cleaning up 32-bit programs so they can run on amd64
natively than providing a 32-bit infrastructure on amd64 when you can
easily run 32-bit programs on FreeBSD i386 if necessary.

It is possible to use a 32-bit jail on amd64. If you install the ports
tree in that jail you could perhaps build wine? I haven't tried this,
though.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpaqYMQwtW5e.pgp
Description: PGP signature


Re: Wine on FBSD-7.0 amd64. Does it run?

2009-07-09 Thread Sam Fourman Jr.
 The wine port only works on i386:

 # grep ARCHS /usr/ports/emulators/wine/Makefile
 ONLY_FOR_ARCHS= i386

 If I understood correctly, the problem is that wine is a 32-bit
 program. See http://wiki.winehq.org/WineOn64bit

 It would need 32-bit versions of all the libraries that it uses. The
 FreeBSD ports system doesn't currently isn't equipped to handle
 this. Not that this would be impossible, but nobody has bothered.

I know that is must be possible, 64bit Linux's run 32bit wine apps.

Gentoo Linux and OpenSuse amd64 editions, work with wine
I use one of these two to Play World of Warcraft on my notebook.

I Would use FreeBSD but suspend resume on i386 has issues, and
no 64bit nvidia, so I am stuck with Linux on my Laptop for the moment.


Sam Fourman Jr.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Software installasion (Was: Re: Wine without X)

2009-03-29 Thread Barnaby Scott

Mel Flynn wrote:

On Saturday 28 March 2009 13:06:44 Robert Huff wrote:

Mel Flynn writes:

  Can I ask one more possibly really dumb question, to which I
   can find no answer: Is there a 'conventional', or sensible
   for one reason oranother, place to download application source to?

 Most systems I use or inherited use a variation of ~/src ~/cvs or
 ~/svn, where src are the tarballs + their extracted source and
 cvs/svn checkouts and/or exports.

I have never done this, but if I were running a private ports
tree I would be tempted to root it (if not on a separate partition)
at /usr/priv_ports or something similar and have the structure
minic /usr/ports whereever possible.  The name would then be
semi-intuitive, and a simple change of a few environment variables
(perhaps in the login file of an account dedicated to working on
those ports) would be all it took to change the framework.


A private portstree (as in: uses the ports framework for compiling and 
installing software, including registering the port in /var/db/pkg) is best 
kept in /usr/ports/local. One needs to set VALID_CATEGORIES=local in 
/etc/make.conf and optionally add SUBDIR+=local in /usr/ports/Makefile.local 
if one cares about the ports ending up in the INDEX and make search.


Ideally software not registering itself inside /var/db/pkg (as in software 
compiled by hand) should NOT be installed in $LOCALBASE (/usr/local by 
default) as there is no guarantee through the ports CONFLICTS mechanism, that 
a port overwrites files installed by your hand-compiled software.





Many thanks to all who have helped on this one.

I managed to get wine installed without X and it works :) However my
application doesn't :(

Most of the errors are concerned with MS Visual C++ libraries, which I
have unconfirmed indications might be solved with 'winetricks'
http://wiki.winehq.org/winetricks. However, I think using winetricks
means I need X anyway. So, I will leave it for now and try again after a
bit more research.

Thanks for all the ideas about where to download/install custom apps -
the one that appeals most at this stage is a jail, partly because I have
never played with them, and I think I should progress my learning in
that direction. However I find the other answers very useful insights
too. Given that winetricks calls itself a 'quick and dirty script',
along with the fact that the current wine port doesn't work, I think I
see another manual installation coming on.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Software installasion (Was: Re: Wine without X)

2009-03-29 Thread Paul Schmehl
--On March 29, 2009 11:03:03 AM -0500 Barnaby Scott b...@waywood.co.uk 
wrote:


Many thanks to all who have helped on this one.

I managed to get wine installed without X and it works :) However my
application doesn't :(

Most of the errors are concerned with MS Visual C++ libraries, which I
have unconfirmed indications might be solved with 'winetricks'
http://wiki.winehq.org/winetricks. However, I think using winetricks
means I need X anyway. So, I will leave it for now and try again after a
bit more research.



Sounds like missing dlls.  You *may* be able to just copy the missing dlls 
into the wine lib directory and get the application to work.  I would 
examine the error messages closely to see what dlls it trying to find and 
can't.


Paul Schmehl, If it isn't already
obvious, my opinions are my own
and not those of my employer.
**
WARNING: Check the headers before replying

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Software installasion (Was: Re: Wine without X)

2009-03-29 Thread User Wblock

On Sun, 29 Mar 2009, Barnaby Scott wrote:

Thanks for all the ideas about where to download/install custom apps -
the one that appeals most at this stage is a jail, partly because I have
never played with them, and I think I should progress my learning in
that direction. However I find the other answers very useful insights
too. Given that winetricks calls itself a 'quick and dirty script',
along with the fact that the current wine port doesn't work,


Today's updated wine-1.1.18,1 port works now.

-Warren Block * Rapid City, South Dakota USA
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine without X

2009-03-28 Thread Mel Flynn
On Friday 27 March 2009 15:42:27 Barnaby Scott wrote:

 Can I ask one more possibly really dumb question, to which I can find no
 answer: Is there a 'conventional', or sensible for one reason or
 another, place to download application source to?

Most systems I use or inherited use a variation of ~/src ~/cvs or ~/svn, where 
src are the tarballs + their extracted source and cvs/svn checkouts and/or 
exports.
-- 
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine without X

2009-03-28 Thread Robert Huff

Mel Flynn writes:

   Can I ask one more possibly really dumb question, to which I
can find no answer: Is there a 'conventional', or sensible
for one reason oranother, place to download application source to?
  
  Most systems I use or inherited use a variation of ~/src ~/cvs or
  ~/svn, where src are the tarballs + their extracted source and
  cvs/svn checkouts and/or exports.

I have never done this, but if I were running a private ports
tree I would be tempted to root it (if not on a separate partition)
at /usr/priv_ports or something similar and have the structure
minic /usr/ports whereever possible.  The name would then be
semi-intuitive, and a simple change of a few environment variables
(perhaps in the login file of an account dedicated to working on
those ports) would be all it took to change the framework.


Robert Huff




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: WINE installation problem

2009-03-28 Thread Mel Flynn
On Thursday 26 March 2009 14:10:48 RW wrote:
 On Thu, 26 Mar 2009 07:20:38 +0100

 Alain G. Fabry alainfa...@belgacom.net wrote:
  Hi,
 
  My WINE was running fine, but while performing a portupgrade I got an
  error message. So I decided to remove WINE and reinstall. Now I can't
  install it either.

 If you ever do that again, make a package first.

Using:
mkdir ~/packages
pkg_create -vb packagename-1.2.3 ~/packages/packagename-1.2.3.tbz

-- 
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Software installasion (Was: Re: Wine without X)

2009-03-28 Thread Mel Flynn
On Saturday 28 March 2009 13:06:44 Robert Huff wrote:
 Mel Flynn writes:
Can I ask one more possibly really dumb question, to which I
 can find no answer: Is there a 'conventional', or sensible
 for one reason oranother, place to download application source to?
 
   Most systems I use or inherited use a variation of ~/src ~/cvs or
   ~/svn, where src are the tarballs + their extracted source and
   cvs/svn checkouts and/or exports.

   I have never done this, but if I were running a private ports
 tree I would be tempted to root it (if not on a separate partition)
 at /usr/priv_ports or something similar and have the structure
 minic /usr/ports whereever possible.  The name would then be
 semi-intuitive, and a simple change of a few environment variables
 (perhaps in the login file of an account dedicated to working on
 those ports) would be all it took to change the framework.

A private portstree (as in: uses the ports framework for compiling and 
installing software, including registering the port in /var/db/pkg) is best 
kept in /usr/ports/local. One needs to set VALID_CATEGORIES=local in 
/etc/make.conf and optionally add SUBDIR+=local in /usr/ports/Makefile.local 
if one cares about the ports ending up in the INDEX and make search.

Ideally software not registering itself inside /var/db/pkg (as in software 
compiled by hand) should NOT be installed in $LOCALBASE (/usr/local by 
default) as there is no guarantee through the ports CONFLICTS mechanism, that 
a port overwrites files installed by your hand-compiled software.

-- 
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine without X

2009-03-28 Thread Chris Rees
2009/3/28 Robert Huff roberth...@rcn.com:

 Mel Flynn writes:

   Can I ask one more possibly really dumb question, to which I
    can find no answer: Is there a 'conventional', or sensible
    for one reason oranother, place to download application source to?

  Most systems I use or inherited use a variation of ~/src ~/cvs or
  ~/svn, where src are the tarballs + their extracted source and
  cvs/svn checkouts and/or exports.

        I have never done this, but if I were running a private ports
 tree I would be tempted to root it (if not on a separate partition)
 at /usr/priv_ports or something similar and have the structure
 minic /usr/ports whereever possible.  The name would then be
 semi-intuitive, and a simple change of a few environment variables
 (perhaps in the login file of an account dedicated to working on
 those ports) would be all it took to change the framework.


                                Robert Huff


I'm always inclined to use --PREFIX=/sw/local/ when compiling; I'm
used to Fink on my Mac, so /sw is a nice directory for that.

Chris
-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine without X

2009-03-27 Thread Barnaby Scott

Paul Schmehl wrote:



So, you *could* do this:
su - to root
Download the wine tarball and untar it
Go in to the wine directory and type the following, in order:
./configure --without-x
make depends
make
make install

That will install wine on your system without X.  Figuring out how to 
get your rendering binary to run is an exercise for you.  :-)


I left wine without x installed on my system.  If you have questions, I 
*may* be able to help.




Can I ask one more possibly really dumb question, to which I can find no 
answer: Is there a 'conventional', or sensible for one reason or 
another, place to download application source to? Presumably you don't 
want it mixed up in the ports distfiles, or in the system's source 
directory. I know this sounds very silly, and the answer might be 
'wherever you like', but I do like to learn the conventions which 
usually have good reasons behind them.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine without X

2009-03-27 Thread Andrew Wright

On Fri, 27 Mar 2009, Barnaby Scott wrote:

Can I ask one more possibly really dumb question, to which I can find no 
answer: Is there a 'conventional', or sensible for one reason or another, 
place to download application source to? Presumably you don't want it mixed


Not dumb at all.  There are several conventions.

The one I use is to have a user named build.

This provides a natural home for these packages (the home directory
of that account) as well as nice management for setting uname,
potential wheel association etc. for an account that is used
for building system libs by executing su - build to get that
type of admin process underway.

A.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine without X

2009-03-27 Thread Paul Schmehl
--On Friday, March 27, 2009 09:42:27 -0500 Barnaby Scott b...@waywood.co.uk 
wrote:




Can I ask one more possibly really dumb question, to which I can find no
answer: Is there a 'conventional', or sensible for one reason or
another, place to download application source to? Presumably you don't
want it mixed up in the ports distfiles, or in the system's source
directory. I know this sounds very silly, and the answer might be
'wherever you like', but I do like to learn the conventions which
usually have good reasons behind them.


I don't know that there's a convention for it, but it makes good sense to 
separate any source installs from the base system and ports system.  I use a 
folder named Downloads, put the tar files in there and then untar them.  That 
creates a separate directory for each untarred source code and leaves the 
tarballs in the base directory.


The more critical question is where should you install the software.  By 
default wine installs everything in /usr/local/bin/, /usr/local/lib/wine, 
/usr/local/include/wine and /usr/local/share/wine, which agrees with the 
default locations for files of those types on FreeBSD.  Some people prefer to 
install compiled-from-source software in other locations.  It's really up to 
you.


--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
***
Check the headers before clicking on Reply.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: WINE installation problem

2009-03-26 Thread RW
On Thu, 26 Mar 2009 07:20:38 +0100
Alain G. Fabry alainfa...@belgacom.net wrote:

 Hi,
 
 My WINE was running fine, but while performing a portupgrade I got an
 error message. So I decided to remove WINE and reinstall. Now I can't
 install it either. 

If you ever do that again, make a package first.

 I get the following message
 ===  wine-1.1.17,1 builds, but fails upon startup.
 *** Error code 1
 
 Stop in /usr/ports/emulators/wine.

I'd suggest you either get an old package of wine, or install
portdowngrade and use it to take the wine port back to a previous
version. wine-1.1.16,1 works for me.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine without X

2009-03-26 Thread Bill Moran
In response to Barnaby Scott b...@waywood.co.uk:

 I'm sorry if I'm asking in the wrong place, but I have tried elsewhere 
 and go no response.
 
 I want to install wine, but without X on the system.

Why would you expect this to be possible?  The GUI is an integral part
of MS Windows ... I can't imagine how wine would work at all without X
installed -- which is probably why you're not getting any answers.

Perhaps you should back up and consider what you're trying to accomplish.
If you don't need a GUI, then what programs do you expect to run under
wine, and is there some better way to get them?

-- 
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine without X

2009-03-26 Thread Robert Huff

Bill Moran writes:

   I want to install wine, but without X on the system.
  
  Why would you expect this to be possible?  The GUI is an integral
  part of MS Windows ... I can't imagine how wine would work at all
  without X installed -- which is probably why you're not getting
  any answers.

I'm not that familiar with Wine - does it support use of the
Windows command prompt?  I can conceive of a program which requires
Windows libraries or the kernel, but does not use the gui.
(Though I agree that at that point finding a non-Windows
solution becomes increasingly attractive.)


Robert Huff


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine without X

2009-03-26 Thread Chris Rees
2009/3/26 Robert Huff roberth...@rcn.com:

 Bill Moran writes:

   I want to install wine, but without X on the system.

  Why would you expect this to be possible?  The GUI is an integral
  part of MS Windows ... I can't imagine how wine would work at all
  without X installed -- which is probably why you're not getting
  any answers.

        I'm not that familiar with Wine - does it support use of the
 Windows command prompt?  I can conceive of a program which requires
 Windows libraries or the kernel, but does not use the gui.
        (Though I agree that at that point finding a non-Windows
 solution becomes increasingly attractive.)


                                Robert Huff


 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


If you're most worried about 'cluttering' up your base system, a jail
(8) could be the answer for you. X chomps a little hard drive space
for sure, but if it's in a jail, there're no package crossovers.


Chris

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine without X

2009-03-26 Thread Wojciech Puchar

no response.

I want to install wine, but without X on the system. Obviously trying to do


what you want to do with wine not having X?

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine without X

2009-03-26 Thread Barnaby Scott

Bill Moran wrote:

In response to Barnaby Scott b...@waywood.co.uk:

I'm sorry if I'm asking in the wrong place, but I have tried elsewhere 
and go no response.


I want to install wine, but without X on the system.


Why would you expect this to be possible?  The GUI is an integral part
of MS Windows ... I can't imagine how wine would work at all without X
installed -- which is probably why you're not getting any answers.

Perhaps you should back up and consider what you're trying to accomplish.
If you don't need a GUI, then what programs do you expect to run under
wine, and is there some better way to get them?



Thanks for your reply

I know this is possible because I have seen discussion of it in Linux 
and wine forums. I'm just too inexperienced to know which bits of the 
instructions are OS-specific, and what other nightmares I might face. I 
might be able to figure it all out by weeks of trial and error, but that 
seems crazy if someone has been there before me!


As for why I want it to run, that is because the application I want to 
run is a bolt-on to a specific bit of rendering software that we use, 
and there really is no viable non-Windows replacement in our situation - 
believe me, if there was, I'd be using it. (In case you care, we are 
talking about Vray for Rhino, which we use because we use Rhino, and 
because we use Rhino we chose RhinoCAM, and because we chose RhinoCAM I 
spent weeks writing software to make it talk to our CNC equipment, whose 
controller is inextricably Windows-based... you get the picture!)


In answer to the other replies (thanks to you guys too):

Yes, wine is fine with just the command prompt. It is somewhat confusing 
in that it offers a thing called wineconsole, but ironically that *does* 
appear to require X. Just using wine without X is fine, so long as the 
app does not attempt to open any sort of window, system tray etc.


As for the 'cluttering' - I'm not so worried about disk space, that's 
cheap these days. It's more a question of updating ports. When I once 
made the mistake of installing X and various other things I turned out 
not to need, the process of updating everything became a nightmare - 
stuff breaking because I hadn't read the updating info for a bunch of 
fonts or something stupid like that. Multiply that by 3 servers, and, 
well, no thanks!

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine without X

2009-03-26 Thread Paul Schmehl
--On Thursday, March 26, 2009 09:47:27 -0500 Barnaby Scott b...@waywood.co.uk 
wrote:




I'm sorry if I'm asking in the wrong place, but I have tried elsewhere
and go no response.

I want to install wine, but without X on the system. Obviously trying to
do this from ports drags in loads of X-related stuff. There doesn't seem
to be a WITHOUT_X11 knob available for the wine port (presuambly because
hardly anyone would want it).

I guess that leaves me installing it the 'old-fashioned' way, but
unfortunately my inexperience leaves me floundering here! Because
FreeBSD has such a wonderful ports system, all documentation I can find
for installing from source refers to ports, and I have not found a
single one showing a layman how to install from source manually, and
what problems I have to look out for.

As you can probably tell, I lack a lot experience, so keep it fairly
monosyllabic please!

(In case you wonder what on earth I want this for, it is to run a
'render slave' which is Windows only, and simply runs in the background
- it would not even count as a 'console application'. I have three very
underused FreeBSD servers and they could do with some rendering work to
keep them from getting bored, but I don't want X cluttering them up.)

Any help gratefully received


Number 1, you should always google first.  There's a wealth of posts on the web 
about running wine without X.


Note that, at present, the wine port will not work.  (There is an IGNORE line 
in the Makefile that explains why.)


Whether wine will work at all or work but not do what you want, I can't say.

Here's a post where someone compiled wine without X:
http://www.winehq.org/pipermail/wine-users/2001-October/004709.html

The wine configure file has an option --with-x, and it's been buildable without 
X since 2003, so you could try building from source.  ./configure --without-x 
builds fine on my machine, and make depends, make and make install work fine as 
well.  Whether it will do what you want it to do, only you can say.


So, you *could* do this:
su - to root
Download the wine tarball and untar it
Go in to the wine directory and type the following, in order:
./configure --without-x
make depends
make
make install

That will install wine on your system without X.  Figuring out how to get your 
rendering binary to run is an exercise for you.  :-)


I left wine without x installed on my system.  If you have questions, I *may* 
be able to help.


--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
***
Check the headers before clicking on Reply.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine without X

2009-03-26 Thread Wojciech Puchar

 part of MS Windows ... I can't imagine how wine would work at all
 without X installed -- which is probably why you're not getting
 any answers.


I'm not that familiar with Wine - does it support use of the
Windows command prompt?  I can conceive of a program which requires
Windows libraries or the kernel, but does not use the gui.


that's possible. anyway - if you can't build wine without X, built it with 
X, it will only install X libraries nothing else and it will work when 
command line utils will be used.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine without X

2009-03-26 Thread Barnaby Scott

Jeff Laine wrote:

On Thu, Mar 26, 2009 at 05:12:17PM +, Barnaby Scott wrote:

Bill Moran wrote:

In response to Barnaby Scott b...@waywood.co.uk:

I'm sorry if I'm asking in the wrong place, but I have tried elsewhere 
and go no response.


I want to install wine, but without X on the system.

Why would you expect this to be possible?  The GUI is an integral part
of MS Windows ... I can't imagine how wine would work at all without X
installed -- which is probably why you're not getting any answers.

Perhaps you should back up and consider what you're trying to accomplish.
If you don't need a GUI, then what programs do you expect to run under
wine, and is there some better way to get them?


Thanks for your reply

I know this is possible because I have seen discussion of it in Linux 
and wine forums. I'm just too inexperienced to know which bits of the 
instructions are OS-specific, and what other nightmares I might face. I 
might be able to figure it all out by weeks of trial and error, but that 
seems crazy if someone has been there before me!


As for why I want it to run, that is because the application I want to 
run is a bolt-on to a specific bit of rendering software that we use, 
and there really is no viable non-Windows replacement in our situation - 
believe me, if there was, I'd be using it. (In case you care, we are 
talking about Vray for Rhino, which we use because we use Rhino, and 
because we use Rhino we chose RhinoCAM, and because we chose RhinoCAM I 
spent weeks writing software to make it talk to our CNC equipment, whose 
controller is inextricably Windows-based... you get the picture!)


In answer to the other replies (thanks to you guys too):

Yes, wine is fine with just the command prompt. It is somewhat confusing 
in that it offers a thing called wineconsole, but ironically that *does* 
appear to require X. Just using wine without X is fine, so long as the 
app does not attempt to open any sort of window, system tray etc.


As for the 'cluttering' - I'm not so worried about disk space, that's 
cheap these days. It's more a question of updating ports. When I once 
made the mistake of installing X and various other things I turned out 
not to need, the process of updating everything became a nightmare - 
stuff breaking because I hadn't read the updating info for a bunch of 
fonts or something stupid like that. Multiply that by 3 servers, and, 
well, no thanks!



wineconsole app seems working fine in terminal with no X at all. 
I ran it like this: 


./wineconsole --backend=curses cmd



OK thanks, I stand corrected (just shows how unreliable GOOGLING 
sometimes is!) If/when I can get this working I will check out 
wineconsole, though as I said, the app I want to run has no visible 
output at all, console or otherwise - it just talks to the main renderer 
over the network, but (dammit) is a Windows binary.


Barnaby
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Wine without X

2009-03-26 Thread Jeff Laine
On Thu, Mar 26, 2009 at 05:12:17PM +, Barnaby Scott wrote:
 Bill Moran wrote:
 In response to Barnaby Scott b...@waywood.co.uk:
 
 I'm sorry if I'm asking in the wrong place, but I have tried elsewhere 
 and go no response.
 
 I want to install wine, but without X on the system.
 
 Why would you expect this to be possible?  The GUI is an integral part
 of MS Windows ... I can't imagine how wine would work at all without X
 installed -- which is probably why you're not getting any answers.
 
 Perhaps you should back up and consider what you're trying to accomplish.
 If you don't need a GUI, then what programs do you expect to run under
 wine, and is there some better way to get them?
 
 
 Thanks for your reply
 
 I know this is possible because I have seen discussion of it in Linux 
 and wine forums. I'm just too inexperienced to know which bits of the 
 instructions are OS-specific, and what other nightmares I might face. I 
 might be able to figure it all out by weeks of trial and error, but that 
 seems crazy if someone has been there before me!
 
 As for why I want it to run, that is because the application I want to 
 run is a bolt-on to a specific bit of rendering software that we use, 
 and there really is no viable non-Windows replacement in our situation - 
 believe me, if there was, I'd be using it. (In case you care, we are 
 talking about Vray for Rhino, which we use because we use Rhino, and 
 because we use Rhino we chose RhinoCAM, and because we chose RhinoCAM I 
 spent weeks writing software to make it talk to our CNC equipment, whose 
 controller is inextricably Windows-based... you get the picture!)
 
 In answer to the other replies (thanks to you guys too):
 
 Yes, wine is fine with just the command prompt. It is somewhat confusing 
 in that it offers a thing called wineconsole, but ironically that *does* 
 appear to require X. Just using wine without X is fine, so long as the 
 app does not attempt to open any sort of window, system tray etc.
 
 As for the 'cluttering' - I'm not so worried about disk space, that's 
 cheap these days. It's more a question of updating ports. When I once 
 made the mistake of installing X and various other things I turned out 
 not to need, the process of updating everything became a nightmare - 
 stuff breaking because I hadn't read the updating info for a bunch of 
 fonts or something stupid like that. Multiply that by 3 servers, and, 
 well, no thanks!


wineconsole app seems working fine in terminal with no X at all. 
I ran it like this: 

./wineconsole --backend=curses cmd

-- 
Best regards,
Jeff

| Nobody wants to say how this works.  |
|  Maybe nobody knows ...  |
|   Xorg.conf(5)|
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: WINE 21.1.5 QUESTION...

2008-10-27 Thread Tijl Coosemans
On Sunday 26 October 2008 22:21:08 Gary Kline wrote:
 On Sun, Oct 26, 2008 at 11:50:13AM +0100, Tijl Coosemans wrote:
 On Saturday 25 October 2008 03:55:26 Gary Kline wrote:
 Maybe somebody here can clue me in on how to get a 1998, windose3.1/w95
 French-learning game to work on my newly built wine.  I asked on the
 Ubuntu forums and altho somebody did try to help; Zip.
 
 I do not have a clue to the DOS-path; it's a CDROM and since I'm using
 the top CD/DVD optical drive, I'm guessing that it D:\; right? since C:\
 would be the harddrive.
 
 Otherwise, no clue.  The disc is due back at the library soon so I want
 to make the most of it ... even if it does crash every 355 minutes!
 
 You can setup drive letters using the drives tab in winecfg.
 So, insert cdrom, mount it, run winecfg and assign a drive letter
 to the mount point. If you have hal/dbus enabled most of this is
 done automatically.
 
 hal/dbus are going.  How do I mount the cdrom on C:\ ?
 I've already run winecfg and sound works, selected Windows 95.

No, you mount the cdrom like you normally would. If you use hal
and the cdrom is mounted on /var/media/something, you need
to tell wine (winecfg, drives tab) that whenever drive D: is
accessed, it should look for the files in /var/media/something.
After that you can run 'wine d:\\setup.exe'.

You should see something like this in winecfg:
C:  ../drive_c
D:  /var/media/cd0
Z:  /
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: WINE 21.1.5 QUESTION...

2008-10-27 Thread Gary Kline
On Mon, Oct 27, 2008 at 11:34:52AM +0100, Tijl Coosemans wrote:
 On Sunday 26 October 2008 22:21:08 Gary Kline wrote:
  On Sun, Oct 26, 2008 at 11:50:13AM +0100, Tijl Coosemans wrote:
  On Saturday 25 October 2008 03:55:26 Gary Kline wrote:
  Maybe somebody here can clue me in on how to get a 1998, windose3.1/w95
  French-learning game to work on my newly built wine.  I asked on the
  Ubuntu forums and altho somebody did try to help; Zip.
  
  I do not have a clue to the DOS-path; it's a CDROM and since I'm using
  the top CD/DVD optical drive, I'm guessing that it D:\; right? since C:\
  would be the harddrive.
  
  Otherwise, no clue.  The disc is due back at the library soon so I want
  to make the most of it ... even if it does crash every 355 minutes!
  
  You can setup drive letters using the drives tab in winecfg.
  So, insert cdrom, mount it, run winecfg and assign a drive letter
  to the mount point. If you have hal/dbus enabled most of this is
  done automatically.
  
  hal/dbus are going.  How do I mount the cdrom on C:\ ?
  I've already run winecfg and sound works, selected Windows 95.
 
 No, you mount the cdrom like you normally would. If you use hal
 and the cdrom is mounted on /var/media/something, you need
 to tell wine (winecfg, drives tab) that whenever drive D: is
 accessed, it should look for the files in /var/media/something.
 After that you can run 'wine d:\\setup.exe'.
 
 You should see something like this in winecfg:
 C:  ../drive_c
 D:  /var/media/cd0
 Z:  /

I get the general idea, but since I have two optical drives, not
just one, things are a bit more complicated.  In / I've got 
/media/cdroms/0 and /media/cdroms/1; in /usr/home/kline is:
~/cdroms/0 and ~/cdroms/1 . For some reason winecfg didn't
understand this and I had to type in the /usr/home/kline/cdrom/0
by hand.  It is listed as H:  That's fine; but in an
xterm/Konsole messages kept getting printed to stderr so it looks
like winecfg isn't looking at my 1sr optical drine.  

I've tried mount /media/cdroms/cd0 /mnt and other ploys.  Zip.
IMO, anybody who has tried to do the ``impossible'' (wine)
deserves a gold medal ... but I can't make it work.

gary




-- 
 Gary Kline  [EMAIL PROTECTED]  http://www.thought.org  Public Service Unix
http://jottings.thought.org   http://transfinite.thought.org


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


Re: WINE 21.1.5 QUESTION...

2008-10-26 Thread Tijl Coosemans
On Saturday 25 October 2008 03:55:26 Gary Kline wrote:
 Maybe somebody here can clue me in on how to get a 1998, windose3.1/w95
 French-learning game to work on my newly built wine.  I asked on the
 Ubuntu forums and altho somebody did try to help; Zip.
 
 I do not have a clue to the DOS-path; it's a CDROM and since I'm using
 the top CD/DVD optical drive, I'm guessing that it D:\; right? since C:\
 would be the harddrive.
 
 Otherwise, no clue.  The disc is due back at the library soon so I want
 to make the most of it ... even if it does crash every 355 minutes!

You can setup drive letters using the drives tab in winecfg.
So, insert cdrom, mount it, run winecfg and assign a drive letter
to the mount point. If you have hal/dbus enabled most of this is
done automatically.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: WINE 2 1.1.5 QUESTION...

2008-10-26 Thread Polytropon
On Fri, 24 Oct 2008 18:55:26 -0700, Gary Kline [EMAIL PROTECTED] wrote:
   I do not have a clue to the DOS-path; it's a CDROM and since I'm using
   the top CD/DVD optical drive, I'm guessing that it D:\; right? since C:\
   would be the harddrive.

It's a long long time ago that I've used wine, mostly for
gaming-experiments. But I remember a kind of symlink strukture
inside ~/.wine called dosdevices/ that included pointers to
directories, e. g. the system's root directory and the user's
home directory, and maybe mountopoints (or device files?) of
removable media. Maybe it is documented in man wine how to
use this?


-- 
Polytropon
From Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: WINE 21.1.5 QUESTION...

2008-10-26 Thread RW
On Fri, 24 Oct 2008 18:55:26 -0700
Gary Kline [EMAIL PROTECTED] wrote:

 
   Maybe somebody here can clue me in on how to get a 1998,
 windose3.1/w95 French-learning game to work on my newly built wine.
 I asked on the Ubuntu forums and altho somebody did try to help; Zip.
 
   I do not have a clue to the DOS-path; it's a CDROM and since
 I'm using the top CD/DVD optical drive, I'm guessing that it D:\;
 right? since C:\ would be the harddrive.

I don't know that you actually need to know that. I think you could
probably just mount the disk, cd to it, and install or run it from the
command line.


   Otherwise, no clue.  The disc is due back at the library soon
 so I want to make the most of it ... even if it does crash every 355
 minutes!


You might also try dosbox if the game is DOS compatible. 

In the mid-nineties at lot of games were either pure DOS applications
or had separate windows/dos binaries on the disk, 1998 is a bit late
for this though.

 The disc is due back at the library soon

I doubt anyone would care if you copied it at this stage.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: WINE 21.1.5 QUESTION...

2008-10-26 Thread Gary Kline
On Sun, Oct 26, 2008 at 11:50:13AM +0100, Tijl Coosemans wrote:
 On Saturday 25 October 2008 03:55:26 Gary Kline wrote:
  Maybe somebody here can clue me in on how to get a 1998, windose3.1/w95
  French-learning game to work on my newly built wine.  I asked on the
  Ubuntu forums and altho somebody did try to help; Zip.
  
  I do not have a clue to the DOS-path; it's a CDROM and since I'm using
  the top CD/DVD optical drive, I'm guessing that it D:\; right? since C:\
  would be the harddrive.
  
  Otherwise, no clue.  The disc is due back at the library soon so I want
  to make the most of it ... even if it does crash every 355 minutes!
 
 You can setup drive letters using the drives tab in winecfg.
 So, insert cdrom, mount it, run winecfg and assign a drive letter
 to the mount point. If you have hal/dbus enabled most of this is
 done automatically.


hal/dbus are going.  How do I mount the cdrom on C:\ ?
I've already run winecfg and sound works, selected Windows 95.


-- 
 Gary Kline  [EMAIL PROTECTED]  http://www.thought.org  Public Service Unix
http://jottings.thought.org   http://transfinite.thought.org


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


Re: Wine security question...

2008-08-28 Thread Subhro
man jail

Thanks
Subhro

On Fri, Aug 29, 2008 at 8:16 AM, Christopher Joyner
[EMAIL PROTECTED] wrote:
 Is it possible to use wine in a secure way?  I had a warning about it after 
 installing it from the ports.  So I was wondering if it's possible to limit 
 it to a certain area.  Like a sandbox?



  In Love in Jesus Christ, Or Lord and Savior.


 For God so loved the world, that he gave his only *begotten Son, that 
 whosoever believeth in him should not perish, but have everlasting life.
 --John 3:16




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

___
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-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, amd64, and fc-7

2008-05-05 Thread Boris Samorodov
Hello Steve,


On Mon, 5 May 2008 10:42:52 -0700 Steve Franks wrote:

 Anyone try to get an rpm of wine working under linux compat?  Did you
 have to install fc-7 instead of fc-4?  Is fc7 ready for primetime?
 Someone said it had issues awhile back.

It's not and fc (port) issue, it's rather kernel's one
(linux.osrelease 2.4.2 vs 2.6.16 emulation). The default is 2.4.2 even
for CURRENT (but mat change soon). And when the default
linux.osrelease is changed at CURRENT some time will pass before
something like f8 (or even f9) may become a default linux emulation
port.

 Looks like all the 64-bit linux guys run wine, why don't we?  Of

FreeBSD doesn't have 64-bit linux emulation, it's 32-bit for now.
And afaik no one is working on it.

 course, I'd prefer a native FreeBSD port over an rpm if I could get
 it...


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


Re: wine, amd64, and fc-7

2008-05-05 Thread Wojciech Puchar

Looks like all the 64-bit linux guys run wine, why don't we?  Of


run windows if you need windoze apps
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: wine, amd64, and fc-7

2008-05-05 Thread Dominic Fandrey

Boris Samorodov wrote:

Hello Steve,


On Mon, 5 May 2008 10:42:52 -0700 Steve Franks wrote:


Anyone try to get an rpm of wine working under linux compat?  Did you
have to install fc-7 instead of fc-4?  Is fc7 ready for primetime?
Someone said it had issues awhile back.


It's not and fc (port) issue, it's rather kernel's one
(linux.osrelease 2.4.2 vs 2.6.16 emulation). The default is 2.4.2 even
for CURRENT (but mat change soon). And when the default
linux.osrelease is changed at CURRENT some time will pass before
something like f8 (or even f9) may become a default linux emulation
port.


Looks like all the 64-bit linux guys run wine, why don't we?  Of


FreeBSD doesn't have 64-bit linux emulation, it's 32-bit for now.
And afaik no one is working on it.


course, I'd prefer a native FreeBSD port over an rpm if I could get
it...


I'm trying to get it to work in a 32-Bit Jail. I ain't there yet, though. It 
seems parts of the code for dynamicilly loading 32bit libraries is broken. 
Should I succeed I will create a Wiki article, containing patches and a howto 
to set things up. And of course the ports@ list would get informed.




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


Re: wine, amd64, and fc-7

2008-05-05 Thread Steve Franks
  run windows if you need windoze apps
Noo!  I'll never turn!  I've been
quite happily, actually, moving my installed base of systems in the
other direction.  (I thought I'd get a more serious response from the
fbsd higher-ups, Wojciech).

Seriously, though, I thought someone might have installed wine on
32-bit linux emualtion on amd64.  All the other linux apps run so
well, I thought it was worth a try, didn't know I'd be the guinea pig,
but hey, makes me feel special.

The speed of my kqemu installation leaves something to be desired.  I
thought I'd give wine a shot.

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


Re: wine, amd64, and fc-7

2008-05-05 Thread Wojciech Puchar

 run windows if you need windoze apps

Noo!  I'll never turn!  I've been
quite happily, actually, moving my installed base of systems in the
other direction.  (I thought I'd get a more serious response from the
fbsd higher-ups, Wojciech).


yes this is serious. there are very few things that doesn't exist for unix 
- only windows. but if you really need install windows. it is at least 
(roughly) windows compatible :)



or use qemu. it's slow but works. i do this - just to be able to check how 
my webpages display in Internet Exploder.



Seriously, though, I thought someone might have installed wine on
32-bit linux emualtion on amd64.  All the other linux apps run so
actually i never had any success with wine, only simple apps work. on the 
other hand i don't needed it much.

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


Re: wine, amd64, and fc-7

2008-05-05 Thread Wojciech Puchar

I'm trying to get it to work in a 32-Bit Jail. I ain't there yet, though. It


there is no 32-bit jails it's just jail with all programs 32-bit. but 
you don't enhance any kernel capabilities this way

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


Re: wine, amd64, and fc-7

2008-05-05 Thread Dominic Fandrey

Wojciech Puchar wrote:
I'm trying to get it to work in a 32-Bit Jail. I ain't there yet, 
though. It


there is no 32-bit jails it's just jail with all programs 32-bit. but 
you don't enhance any kernel capabilities this way


Everything apart from the Kernel is 32-Bit. This is what I'd call a 32-Bit Jail.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: wine, amd64, and fc-7

2008-05-05 Thread Tijl Coosemans
On Monday 05 May 2008 19:42:52 Steve Franks wrote:
 Anyone try to get an rpm of wine working under linux compat?  Did
 you have to install fc-7 instead of fc-4?  Is fc7 ready for
 primetime? Someone said it had issues awhile back.
 
 Looks like all the 64-bit linux guys run wine, why don't we?  Of
 course, I'd prefer a native FreeBSD port over an rpm if I could
 get it...

I looked into this when doing some work on Wine about a year ago:

* Wine doesn't work under the Linux compat layer because of
  differences between Linux and FreeBSD mmap(2) and because the
  implementation of the set_thread_area syscall is too simplistic.

* Wine doesn't work on FreeBSD/amd64 because the kernel doesn't
  preserve the segment registers on context switches.

Also, Wine and all its dependencies (xorg libs etc.) should be
built as 32 bit. Ideally the ports system would provide the
infrastructure for that.

None of this is really difficult to fix but I didn't (and still
don't) have an amd64 system so I moved on to fix other problems.
___
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-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 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 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]


  1   2   >