wine commandline options

[Rick Romero]

I was playing with Pegasus Mail (silver list) to see what I could get
working.  It looks like it doesn't detect winsock.dll using it's own
'search algorythm, so the TCP/IP options don't get enabled - hence the
(paraphrased) 'wtf?' in the silver list description.

So, I tried to force Pegasus Mail to load winsock explicitly using the
-Z 128 option:
$wine winpm-32 -Z 128
but wine comes back with 'Unknown option -Z'.

I'm not quite sure how these are getting parsed, but I see in
misc/options.c parse_options()
    if (*p++ != '-') continue;  /* not an option */
 Should exit if the 2nd char isn't a - (am I right?)
 BUT, when parse_options returns to OPTIONS_ParseOptions()
The following:
  /* check if any option remains */
    for (i = 1; argv[i]; i++)
    {
        if (!strcmp( argv[i], "--" ))
        {
            remove_options( argv, i, 1, 0 );
            break;
        }
        if (argv[i][0] == '-')
        {
            MESSAGE( "Unknown option '%s'\n\n", argv[i] );
        //    OPTIONS_Usage();
        }
    }
Still picks up '-' as an invalid option.  My first thought would be to
stop checking for options after the 1st and 2nd chars are not '-' (ie.
after the Win32 program name), but I'm not sure if that's correct.

Any thoughts?  (FYI, no, the option didn't make Pmail work.)

Rick

[Roderick Colenbrander]

This does the trick:
wine winpm-32 -- -Z 128

next time read the docs first instead of the source .. ;)

Roderick

On Monday 18 November 2002 18:06, Rick Romero wrote:
> I was playing with Pegasus Mail (silver list) to see what I could get
> working.  It looks like it doesn't detect winsock.dll using it's own
> 'search algorythm, so the TCP/IP options don't get enabled - hence the
> (paraphrased) 'wtf?' in the silver list description.
>
> So, I tried to force Pegasus Mail to load winsock explicitly using the
> -Z 128 option:
> $wine winpm-32 -Z 128
> but wine comes back with 'Unknown option -Z'.
>
> I'm not quite sure how these are getting parsed, but I see in
> misc/options.c parse_options()
>    if (*p++ != '-') continue;  /* not an option */
>  Should exit if the 2nd char isn't a - (am I right?)
>  BUT, when parse_options returns to OPTIONS_ParseOptions()
> The following:
>   /* check if any option remains */
>     for (i = 1; argv[i]; i++)
>     {
>         if (!strcmp( argv[i], "--" ))
>         {
>             remove_options( argv, i, 1, 0 );
>             break;
>         }
>         if (argv[i][0] == '-')
>         {
>             MESSAGE( "Unknown option '%s'\n\n", argv[i] );
>         //    OPTIONS_Usage();
>         }
>     }
> Still picks up '-' as an invalid option.  My first thought would be to
> stop checking for options after the 1st and 2nd chars are not '-' (ie.
> after the Win32 program name), but I'm not sure if that's correct.
>
> Any thoughts?  (FYI, no, the option didn't make Pmail work.)
>
> Rick

wine commandline options / Pegasus Mail

[Rick Romero]

On Mon, 2002-11-18 at 11:16, Roderick Colenbrander wrote:
> This does the trick:
> wine winpm-32 -- -Z 128
>
> next time read the docs first instead of the source .. ;)

Doh.  It's even in the Pmail KB article below, and I didn't see it.

Pegasus Mail TCP/IP works after reading the following KB article from pmail:

http://kbase.pmail.gen.nz/viewfull.cfm?ObjectID=E1D7B847-576A-4BA3-BEE13F10C...

I think if you don't start Pmail the first time with the -Z 128, it sets an option 
to never load it.

I assume for it to be gold, that shouldn't be necessary?  It should work 
'out of the box'?

Damnit. --. I knew I couldn't have been the first person to do that, and I couldn't 
remember what worked last time I ran it :/

Rick

[Uwe Bonnes]

> > > > > "Rick" == Rick Romero  writes:

Rick> I was playing with Pegasus Mail (silver list) to see what I could
    Rick> get working.  It looks like it doesn't detect winsock.dll using
    Rick> it's own 'search algorythm, so the TCP/IP options don't get
    Rick> enabled - hence the (paraphrased) 'wtf?' in the silver list
    Rick> description.

Rick> So, I tried to force Pegasus Mail to load winsock explicitly using
    Rick> the -Z 128 option: $wine winpm-32 -Z 128 but wine comes back with
    Rick> 'Unknown option -Z'.

Rick> I'm not quite sure how these are getting parsed, but I see in
Options for the win-programm should be givven after a blank "--"

E.g.

$wine -- winpm-32 -Z 128
      ^^
Bye

[Tony Lambregts]

Rick Romero wrote:
> I was playing with Pegasus Mail (silver list) to see what I could get
> working.  It looks like it doesn't detect winsock.dll using it's own
> 'search algorythm, so the TCP/IP options don't get enabled - hence the
> (paraphrased) 'wtf?' in the silver list description.
>
> So, I tried to force Pegasus Mail to load winsock explicitly using the
> -Z 128 option:
> $wine winpm-32 -Z 128

Try

wine -- winpm-32 -Z 128
> but wine comes back with 'Unknown option -Z'.
>
> I'm not quite sure how these are getting parsed, but I see in
> misc/options.c parse_options()
>    if (*p++ != '-') continue;  /* not an option */
> Should exit if the 2nd char isn't a - (am I right?)
> BUT, when parse_options returns to OPTIONS_ParseOptions()
> The following:
>  /* check if any option remains */
>    for (i = 1; argv[i]; i++)
>    {
>        if (!strcmp( argv[i], "--" ))

This is testing for "--" which tells wine to treat arguments after the 
first (program name) as command line arguments.
>    {
>        remove_options( argv, i, 1, 0 );
>        break;
>    }
>    if (argv[i][0] == '-')
>    {
>        MESSAGE( "Unknown option '%s'\n\n", argv[i] );
>    //    OPTIONS_Usage();
>    }
>
> }
> Still picks up '-' as an invalid option.  My first thought would be to
> stop checking for options after the 1st and 2nd chars are not '-' (ie.
> after the Win32 program name), but I'm not sure if that's correct.
>
> Any thoughts?  (FYI, no, the option didn't make Pmail work.)

You have misread what the function is doing it looks for "--" to tell it 
that there are command line arguments to be passed onto the programs. 
Hope this helps (TM.)

[Rein Klazes]

On 18 Nov 2002 11:06:40 -0600, you wrote:
> I was playing with Pegasus Mail (silver list) to see what I could get
> working.  It looks like it doesn't detect winsock.dll using it's own
> 'search algorythm, so the TCP/IP options don't get enabled - hence the
> (paraphrased) 'wtf?' in the silver list description.
> From a thread in the newsgroup more then a year ago, I understand that

pegasus looks for the existance of a file winsock32.dll in  the system
dir. A "touch winsock32.dll" was enough to convince it that winsock
was installed.

Rein.

[Rick Romero]

On Mon, 2002-11-18 at 13:21, Rein Klazes wrote:
> On 18 Nov 2002 11:06:40 -0600, you wrote:
> > I was playing with Pegasus Mail (silver list) to see what I could get
> > working.  It looks like it doesn't detect winsock.dll using it's own
> > 'search algorythm, so the TCP/IP options don't get enabled - hence the
> > (paraphrased) 'wtf?' in the silver list description.
>
> From a thread in the newsgroup more then a year ago, I understand that
> pegasus looks for the existance of a file winsock32.dll in  the system
> dir. A "touch winsock32.dll" was enough to convince it that winsock
> was installed.

It seems 'touch wsock32.dll' in the system32 directory works as well.  
For whatever reason though, it's not enough to tell Pmail to run the
inital setup wizard.  Though I don't think that's a glaring issue.

What is an issue, on my system the Pmail window doesn't refresh properly
when changing virtual desktops.  I don't remember that happening in the
past, so I'm testing other versions of wine to see if it's a regression,
or my famously bad memory :)  (or maybe something changed from Pmail
3.12 to 4.02 that's caused it..)

Rick
> Rein.