There is a start-up pref that shows up in the Appearance pane of the PrefUI where you can set Messenger to start on launch. The UI is working and the pref is persistent, but the back end doesn't appear to be hooked up, as messenger does not launch when I run "apprunner.exe". The pref appears to be user_pref("general.startup.mail", true); I wouldn't call this a beta stopper but it would be cool to have.

fixed. except for general.startup.calendar, all the startup prefs get heeded. remember, this is only if you launch apprunner with out command line options. doing apprunner -editor will only bring up the editor, no matter what your general.startup.* prefs are.

marking m11.

This is working on Win32 in the 16th build. I can launch apprunner.exe directly into mail with the pref set to true as stated above. Need to verify on other platforms.

OK using 1999-10-07-14m11 nt 4.0 OK using 1999-10-07-14m11 linux 6.0

Using Mac with 10-21 commercial build, this doesn't work. 1. Launch the generic "apprunner". Just navigator comes up. 2. Edit|Prefs|Appearance. Uncheck Navigator, checkmark Messenger. Confirm OK. Exit apprunner. 3. Launch generic apprunner. Just navigator comes up. Note the pref did indeed stick in the prefs UI, but didn't engage correctly. Reopening for Mac case.

M13

doesn't sound like a migration problem. shoving to m14.

marking p2

this is mac only.

M15

FYI -- still in same condition Mac OS 8.5.1 2000-01-28-08 m14 commercial build.

So we're punting on allowing mail and aim start up as defaults on the Mac for Beta 1? Nominating for beta 1 to see what PDT thinks.

Putting on the PDT- radar for beta1. will not hold for this.

this got fixed as a side effect of some other fixes. the problem was argc on the mac is set to 0 (not 1) when there are no arguments. this caused all sorts of problems. I had to fix it for a real PDT+ bug. (note to alex and vishy, your aim bug should be fixed now too.)

OK using: 2000-03-06-08 mozilla build on mac OS 9.0 2000-03-06-08 commercial build on linux rh6.0 I'm not able to get this to work using today's win32 build, but it work's using yesterday's win32 build on esther's machine. Will close as verified and investigate win32 further. If need be I'll log another bug.

Doh. Operator error on the win32 case. All platforms ok mar06 builds.