Okay. I'll be brief on the wine thing. Just finished building the
newest wine release 20040615. Getting seg faults with nothing more
then 'wine -v'. Oddly, it only seems to occur when I use wine as
user and mount my old winME partitions. Yep, I'm cheating by using a
previous install of windows (wineHQ do'th not recommend this).
Didn't see this sort of thing in my previous build of 20040505. Has
anyone in slack land seen this with the newest wine?. Seems to me
the wine code got broken somehow. I also pulled down a pre-compiled
wine package and it also seg faults on my machine. Appreciate any
comments here.

As for firefox 0.9.1, can anyone tell me (or point me in the right
direction) why I'm now seeing the profile manager when I use the
-remote commands?. See below (lines wrapped):

/usr/local/bin/callmoz.sh ->

#!/bin/sh
#
# General Purpose: Call Mozilla/Netscape/Firefox Browser
# Got those symlinks correct?
#
# Usage: callmoz.sh Url or path to a file here
#
#ps x|grep -q '[m]ozilla' && mozilla -remote "openURL($1,new-tab)"\
#|| mozilla $1 &
#
##Testing
##ps x|grep -q '[f]irefox' && firefox -remote "openURL($1,new-tab)"\
##|| firefox $1 &

Simple enough right?. Been using this script to call both moz
(1.4->1.6) and firefox since 0.7. I also dropped back to using moz
1.6 and no pesky profile manager popped up telling me the profile
was in use. Guess something changed in firefox 0.9.1?. I'd highly
*appreciate* if anyone could lead me to a solution. From what's at
http://www.mozilla.org/unix/remote.html, I don't see the problem.

Funny thing though... If I start firefox manually (outside the
script), and then fire off the above script several times with a
local file(s), I get just what I want without trouble. That is, I
get several new tabs in firefox and no complaints regarding the
profile manager.

Just what the bloody hell am I missing here... This is going to be
embarrassing isn't it?

Max

--
If Bill Gates had a dime for every time Windows crashed...
Oh wait a minute, he already does.

On Wed, 07 Jul 2004 19:18:29 +0000, Max wrote:
> As for firefox 0.9.1, can anyone tell me (or point me in the right
> direction) why I'm now seeing the profile manager when I use the
> -remote commands?. See below (lines wrapped):
>

I, too, had the same problem after updating to 9.0. Try using the
following command line instead of "mozilla -remote":

mozilla-xremote-client "openURL($1, new-tab)"

This did the trick for me.

Hope this helps you.

Mike

* Max <argos2112@bellsouth.net>:
[ ... ]

> As for firefox 0.9.1, can anyone tell me (or point me in the right
> direction) why I'm now seeing the profile manager when I use the
> -remote commands?. See below (lines wrapped):
[ ... ]

Since 0.9, Mozilla Firefox requires an additional option and argument
when using remote commands: -a firefox

The following script I use, `firefox-openurl', presents an example:
#v+
#!/bin/sh

if [ "$1" ]; then
URL="$1"
else
exit 1
fi

if firefox -a firefox -remote 'ping()' 2> /dev/null; then
firefox -a firefox -remote "openURL($URL, new-tab)"
else
firefox "$URL" &
fi
#v-

--
James Michael Fultz <xyzzy@sent.as.invalid>
Remove this part when replying ^^^^^^^^

Max wrote:

> Okay. I'll be brief on the wine thing. Just finished building the
> newest wine release 20040615. Getting seg faults with nothing more
> then 'wine -v'. Oddly, it only seems to occur when I use wine as
> user and mount my old winME partitions. Yep, I'm cheating by using a
> previous install of windows (wineHQ do'th not recommend this).
> Didn't see this sort of thing in my previous build of 20040505. Has
> anyone in slack land seen this with the newest wine?. Seems to me
> the wine code got broken somehow. I also pulled down a pre-compiled
> wine package and it also seg faults on my machine. Appreciate any
> comments here.

WINE is in continuous alpha. I've even noticed older versions running
apps better than newer versions when i used it last year. In any case,
if you can find an older version perhaps try that. Or get a package
from linuxpackages.net, which i'd assume has been tested out.

I'm wondering about whether you used wine-tools, wine setup tk, or made
your own config file. I didn't see a package for either of the listed
apps, and i had issues while compiling wine setup tk.

Thanks,

Michael

James Michael Fultz wrote:

> Since 0.9, Mozilla Firefox requires an additional option and argument
> when using remote commands: -a firefox

Thanks. I had reverted to 8.0 because of this.

--
Old Man

On 07-07-2004, in alt.os.linux.slackware,
Michael <none@none.com> wrote:

> Max wrote:
>
>> Okay. I'll be brief on the wine thing. Just finished building the
>> newest wine release 20040615. Getting seg faults with nothing
>> more then 'wine -v'. Oddly, it only seems to occur when I use
>> wine as

> WINE is in continuous alpha. I've even noticed older versions
> running apps better than newer versions when i used it last year.
> In any case, if you can find an older version perhaps try that. Or
> get a package from linuxpackages.net, which i'd assume has been
> tested out.

I'm well aware of wine being alpha code. Even if I wasn't, the
hundred or so "FixMe:.*" in the output ought to provide a clue. What
you suggested was exactly why I asked about wine in the first place.
My build failed with seg faults. The package of the newest wine I
got from linuxpackages failed in the same way on my machine.

Guess I'll drop back to an older version. I could be wrong here, but
I'm thinking the dosemu project (alpha code for sure) got broken for
a spell also. No other choice but to drop back to the last working
version.

> I'm wondering about whether you used wine-tools, wine setup tk, or
> made your own config file. I didn't see a package for either of
> the listed apps, and i had issues while compiling wine setup tk.

I know nothing about wine-tools nor wine-setuptk. All I did was copy
over the config file provided in wine-*/documentation/samples to
~/.wine, defined the drives I thought I might need, changed a few of
the more obvious options, and for the most part I was good to go.
Naturally, I had to go back and tweak the config from time to time
to get what I wanted (if even possible). I'm not sure if this has
anything to do with it, but I am using wine with a previous install
of windows. I haven't tried a purely native wine install yet.

Anyway, thanks for the reply.

Max

--
If Bill Gates had a dime for every time Windows crashed...
Oh wait a minute, he already does.

On 07-07-2004, in alt.os.linux.slackware,
James Michael Fultz <xyzzy@sent.as.invalid> wrote:

> * Max <argos2112@bellsouth.net>:
> [ ... ]
>
>> As for firefox 0.9.1, can anyone tell me (or point me in the
>> right direction) why I'm now seeing the profile manager when I
>> use the -remote commands?. See below (lines wrapped):
> [ ... ]
>
> Since 0.9, Mozilla Firefox requires an additional option and
> argument when using remote commands: -a firefox

Many thanks. Works like a charm.

Max

--
If Bill Gates had a dime for every time Windows crashed...
Oh wait a minute, he already does.

Max wrote:


> I know nothing about wine-tools nor wine-setuptk. All I did was copy
> over the config file provided in wine-*/documentation/samples to
> ~/.wine, defined the drives I thought I might need, changed a few of
> the more obvious options, and for the most part I was good to go.
> Naturally, I had to go back and tweak the config from time to time
> to get what I wanted (if even possible). I'm not sure if this has
> anything to do with it, but I am using wine with a previous install
> of windows. I haven't tried a purely native wine install yet.
>
> Anyway, thanks for the reply.
>
> Max
>

You seem to be ahead of myself in the configuration aspect. WineSetupTK
and wine-tools are just scripts to automate the config. I took the easy
way out.

As far as a "native" install, if you have the disk space you might just
mirror the whole windows or the core OS. I did a recursive copy of
several dirs to my wine fake c drive. Trying to use wine with windows
on a physical partition was similar to vmware, it would have various
changes when and if i rebooted into windows.

If you aren't tied to a completely F/OSS solution, check out Crossover
Office and WineX. CXO is $60, 30 day trial. WineX is $15 for access to
bins, or free CVS. I just p2p'd the WineX stuff. Sometimes WINE worked
better, but most of the time WineX and CXO did markedly better. IMO.

michael

On 07-09-2004, in alt.os.linux.slackware,
Michael <none@none.com> wrote:

> Max wrote:

>> I know nothing about wine-tools nor wine-setuptk. All I did was
>> copy over the config file provided in
>> wine-*/documentation/samples to ~/.wine, defined the drives I
>> thought I might need, changed a few of the more obvious options,
>> and for the most part I was good to go. Naturally, I had to go
>> back and tweak the config from time to time to get what I wanted
>> (if even possible). I'm not sure if this has anything to do with
>> it, but I am using wine with a previous install of windows. I
>> haven't tried a purely native wine install yet.
>>
>> Anyway, thanks for the reply.
>>
>> Max

> You seem to be ahead of myself in the configuration aspect.
> WineSetupTK and wine-tools are just scripts to automate the
> config. I took the easy way out.

I'm not so sure you did. The use of the scripts(?) you mentioned
just adds an extra step in the config process. You can get by with
any text editor and the config file itself. If ya know your
hardware, chances are you'll succeed. To a point that is...

> As far as a "native" install, if you have the disk space you might
> just mirror the whole windows or the core OS. I did a recursive
> copy of several dirs to my wine fake c drive. Trying to use wine
> with windows on a physical partition was similar to vmware, it
> would have various changes when and if i rebooted into windows.

Ahh!. Never once did that cross my mind. I do indeed have the space.
For some reason, this is making incredible sense. Nice weekend
project... What fun will I find myself in now?

> If you aren't tied to a completely F/OSS solution, check out
> Crossover Office and WineX. CXO is $60, 30 day trial. WineX is
> $15 for access to bins, or free CVS. I just p2p'd the WineX
> stuff. Sometimes WINE worked better, but most of the time WineX
> and CXO did markedly better. IMO.

I'll keep the above in mind. Purchasing proprietary code of any sort
is at the bottom of my list of things to do. However, pushing a few
bucks towards wineX might no be so bad. I've a ton of wintendo games
and I'm itching to play them without having to boot winblows. Yep.

Max

--
If Bill Gates had a dime for every time Windows crashed...
Oh wait a minute, he already does.