118414 - Mozilla shows up as not compatible with XP during XP install

Status: RESOLVED EXPIRED

(SeaMonkey :: UI Design, defect)

Description

[Christopher Stone]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6) Gecko/20011121
BuildID:    

When install windoze XP, the compatiblity test claims that mozilla might not be
compatible with XP.

Reproducible: Always
Steps to Reproduce:
1. Install Win98 with Mozilla
2. Try to upgrade to windoze XP
3. Compability test indicates Mozilla might not be compatible

Comment 1

[Chase Tingley]

Is the XP installer actually testing for anything meaningful, or is it just 
comparing the installed apps to a list of known "good" ones?  If the latter, 
this is basically an evangelism issue.

Comment 2

[Christopher Stone]

I don't know the answer to this, but I had other apps like gnucleus and cygwin
installed and the compatibility test did not mention those.  Perhaps the
compatibility test that comes with XP checks to see what browser you have
installed and if it says Netscape then it marks it as being incompatible.

Comment 3

[Asa Dotzler [:asa]]

sounds like a job for tech evangelism. I can't test this because I don't have XP. 

Comment 4

[timeless]

do you get something like 
http://www.microsoft.com/windowsxp/pro/techinfo/planning/appcompat/images/AppHe
lp.gif 
from 
http://www.microsoft.com/windowsxp/pro/techinfo/planning/appcompat/technologies
.asp

Asa: I think you might be able to eXPerience this on w2k if you have SP2, 
however i've never experienced this...

http://msdn.microsoft.com/library/default.asp?url=/nhp/Default.asp?contentid=28
000911
http://www.microsoft.com/winlogo/downloads/software.asp

I thought i already bounced a bug like this back to browser.

Reporter: we really need a picture of the complaint. Also very few people have 
reported this, and yet i know a bunch of people report bugs from XP so i'd like 
to know if your system has any interesting configuration flags.

Personally I don't own XP, nor do I have time to learn read about it, so if you 
could allocate time to read the .doc file listed here and report that'd be 
great.

Comment 5

[Christopher Stone]

I cannot generate a picture of the complaint because it only happens during the
upgrade procedure.  I tried re-inserting my xp cd and reperforming the
compability test, but the test didn't even run.  During the upgrade, the
compability test took 15-20 minutes to run, this time it only took 1 second and
reported no errors (I think it just doesn't run the test if XP is already
installed).  I might get the opportunity to reinstall xp in the future since it
doesnt seem to be activating the fan on my laptop :|  I think there was an
option to save the detailed report from the compability test, in fact I might
already have it saved, I don't remember if I did or not.  I will check and see
if I can find the logs of the compability test that ran when I upgraded.

Comment 6

[Christopher Stone]

More notes on how to reproduce:  Probably all you need is a win9x machine with
mozilla installed and an XP CD.  Insert the XP CD and run the compability test
from the main menu.

Comment 7

[sairuh (rarely reading bugmail)]

installer?

Comment 8

[Grace Bush]

not an installer issue

Comment 9

[Christopher Stone]

Attachment: Detailed Report of XP Compability Test

I reinstalled Windows 98SE, installed Mozilla, then ran the XP compatibility
test from the XP CD and saved the results to the attachment.

Comment 10

[Asa Dotzler [:asa]]

->XP Apps. maybe TEDS?

Comment 11

[Chris Nalls]

Has anyone tested to see if this happens with commercial versions?

Comment 12

[Peter Trudelle]

->law,  nsbeta1

Comment 13

[Peter Trudelle]

Nav triage team needs info: Does this happen for Netscape 6.2?  qawanted

Comment 14

[Peter Trudelle]

Sarah, could you please ensure this is tested with NS6?

Comment 15

[Peter Trudelle]

nsbeta1+ per Nav triage team, ->1.0, cc evelyn, tpringle.

Comment 16

[selmer (gone)]

Please update this bug with an [adt1] - [adt3] impact rating (or take it off the
list if it doesn't even rate adt3.)  Thanks!

Comment 17

[Bill Law]

I installed NS6.2 and ran the "upgrade adviser."  It did not report any issues.

That's not quite the same thing as installing WindowsXP but it's all I can do.

Also, the "(a startup program)" notation is a clue that it may only happen if 
QuickLaunch is active.

I'll try the upgrade adviser again after turning on QuickLaunch and report back.

Comment 18

[Bill Law]

Attachment: Screen shot of upgrade adviser, complaining about Netscape

This is after turning on QuickLaunch (and I also made NS6.2 handle .html and
http:).

The funny thing is that NS6.01 is listed on the compatible software page at
http://www.microsoft.com/windows/catalog/catalogshell/shell.asp?subid=22&page=2&contentpage=/windows/catalog/wcbody.asp|subid=22&catid=1fceb407-a86b-4a02-a059-55186796fb7c.
 I'm going to try again with NS6.01 and see what happens.  Maybe MS just needs
to add Mozilla and NS6.x to its list.

Comment 19

[Peter Trudelle]

This bug has been marked qawanted for a month now, with no comment.  TPreston,
could you please narrow down the reproducible cases for this bug?

Comment 20

[Terri Preston]

Sorry Peter, not sure how this missed my radar.

Using these steps I see the dialog that I will attach here:

1. Having Windows ME installed on my system, I insert the Windows XP cd
2. Click on option 3. Check system Compatibility
3. I click the first option 1. Check my system automatically
4. The program goes through my system to check compatibility (it also goes out
to MS and gets updated files)
5. Dialog comes up alerting that Netscape May not work under Windows XP

This is using Win ME build 2002032803 (will update my build but I'm pretty sure
this dialog will still appear)

Comment 21

[Terri Preston]

Attachment: Dialog from Window Compatibility

Comment 22

[Terri Preston]

Dialog saying NS is not compatible with XP still occurs with win ME build 2002041003

Comment 23

[Christopher Stone]

From comment #18:

This is after turning on QuickLaunch (and I also made NS6.2 handle .html and
http:).

Do you have to have both of these options on to recreate this? or is just one of
these causing the error?

Comment 24

[Bill Law]

I believe that this warning appears for *any* application that appears under
HKLM/Softare/Microsoft/Windows/Current Version/Run.  That only happens if you
turn on QuickLaunch.

Is "Instant Messenger" in your example *Netscape* instant messenger, or *AOL*
instant messenger.  I was going to try with AIM to see if WinXP recognized it.

If MS has a list of "ok" programs, then we need to get on it.  I don't think
there is a way to code around this warning. 

Comment 25

[Terri Preston]

this dialog occurs even if I set NS to not open html or http and turn
quicklaunch off

Comment 26

[Bill Law]

With QuickLaunch off?  I haven't seen that.

Is the warning different?  It seems like it wouldn't say "(a startup program)"
in that case.

Comment 27

[Peter Trudelle]

Seems like this is normal behavior for startup apps on this platform, removing
plus for re-triage.

Comment 28

[Peter Trudelle]

nsbeta1- per Nav triage team, ->chrisn, in case we can evangelize MS to not do this.

Comment 29

[thebeastwitheyesthatstared]

is this still an issue? I never saw this in my use of Mozilla/Phoenix etc. on 
XP, although it could be that is due to having SP2 installed and latest fixes..

Comment 30

[Christopher Stone]

You have to be running windows 98 or something and upgrade to XP in order to see
this.  Under Win98 with mozilla installed, insert a windows XP install cd and
run the compatibility test.

Comment 31

[Bob Clary [:bc] (inactive)]

Any reason this is still XP Apps and not an evangelism issue?

Comment 32

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 33

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420