User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; de; rv:1.9) Gecko/2008061521 Firefox/3.0 Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4.5; de; rv:1.9) Gecko/2008061521 Firefox/3.0 With FF 3.0 Java Support of Version 1.3.1 Plugin is abandoned - Hint in readme requested - Indication: System traps with SYS2070 --> SYS127 ( SYS0127 ) Trying to run JAVA 1.3.1 Plugin result in Trap, no hint in readme Java Support of 1.3.1 abandoned with FF 3.0 Here is the Trap Info for the Search Engine: running the Java applet at http://www.bistum-osnabrueck.de/dom_rundumblick/panorama.html traps with 06-28-2008 22:24:57 SYS2070 PID 0048 TID 0001 Slot 007d S:\MOF-3000\MOZILLA\FIREFOX\FIREFOX.EXE NPOJI6->XPCOM.__dt__13nsCOMPtr_baseFv 127 0 [L:\]java -version java version "1.3.1" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1) Classic VM (build 1.3.1, J2RE 1.3.1 IBM build co131-20041210 (JIT enabled: jitc) ) [L:\] Reproducible: Always Steps to Reproduce: 1. 2. 3. A hint in the readme will safe time and honour the afford of "RFM" :-) Just a goodie for the people who actually read the Readme!
For the FF 3.0.x releases (I hope) I added the statement about Java manually when packaging the ZIP file. I am hoping to get that into the repository in bug 460247. By now I also found out about the possibility to "blocklist" plugins, as in e.g. bug 420356. Haven't tested yet if this actually prevents these crashes, but adding stuff to blocklist.xml should be simple...
We now have three files in mozilla-central and mozilla-1.9.1: widget/src/os2/README.firefox widget/src/os2/README.seamonkey widget/src/os2/README.thunderbird These can now be freely updated. First thing should be to sync the hard- and software requirements and add the Java plugin info as well as the details about font and print handling.
Created attachment 354957 [details] [diff] [review] Sync READMEs + Java, v1 OK, this finally does this. The things that is not really synced are the WPS objects stuff and the idle timer. The former because that is switched off for SM and TB, the latter because I'm actually not sure if it's used by SM and TB yet. TBC before the final versions. Please let me know, if you have comments, otherwise I'll check it in soon.
Created attachment 354958 [details] Plain text in ZIP Maybe this format (the full README files in a ZIP file) is easier to check than patches.
You need to update the Hobbes URL's eg - http://hobbes.nmsu.edu/cgi-bin/h-search?key=configapps&sort=date + http://hobbes.nmsu.edu/h-search.php?sh=1&button=Search&key=configapps&stype=all&sort=date&dir=%2F due to the new Hobbes server Generally looks good. Might want to also add that the parameter -no-remote can also be used as well as SET MOZ_NO_REMOTE=1. At least I prefer -no-remote
Pushed to mozilla-1.9.1 (http://hg.mozilla.org/releases/mozilla-1.9.1/rev/cec5323180ec) with some corrections. Hmm, never knew that -no-remote works on OS/2, too. Forgot to test and that...
Pushed to mozilla-central (with the -no-remote change, http://hg.mozilla.org/mozilla-central/rev/f7e50fb20709) and the -no-remote change to mozilla-1.9.1 (http://hg.mozilla.org/releases/mozilla-1.9.1/rev/1027d0ee46cb). Leaving this bug open for a reorganization of the README as Rich suggested in the newsgroup.
Created attachment 369799 [details] a rewrite of the Firefox readme This should also be usable for the other apps after making minor changes.
Since LIBPATHSTRICT is known to prevent audio playback in Innotek's port of Flash, This is not true if it is patched (I assume you are NOT talking about Flash 5, although that is useless, and I'm sure that can also be patched). As far as I know, the only "obvious" place to get this plugin is the Warpzilla Tips page, and that one is already patched. So, I would not mention this. However, if you want to make it more generalized, I think something along the lines of "LIBPATHSTRICT is known to cause problems in some unpatched Innotek plugins" would be better, as the Acrobat plugin fails without modification (and thanks for finding the fix!).
ftp://ftp.netlabs.org/pub/dssaver/dssaver_v18.zip Either point to the directory, or the current version: ftp://ftp.netlabs.org/pub/dssaver/dssaver_v20.exe
Comment on attachment 369799 [details] a rewrite of the Firefox readme Very, nice! I like this version much better than mine. :-) Some comments, though. >* Links > Additional resources in cyberspace > >* System Requirements > Sorry, you can't install it on a floppy I don't think these two need the extra catch phrases. > Doodle ScreenSaver - better timing for internal cleanup operations > ftp://ftp.netlabs.org/pub/dssaver/dssaver_v18.zip Yes, as Steve said, the filename should probably be removed. Was already suboptimal in my old version... >Note: Thanks to a bug in Warp v4.5, you can run multiple Mozilla apps at >the same time even if one (and only one) of them doesn't have LIBPATHSTRICT >set. Since LIBPATHSTRICT is known to prevent audio playback in Innotek's >port of Flash, you may want to omit it for your primary browser and only >set it for your other Mozilla apps Here, I would remove the "Thanks...v4.5" part. That is not important. To address Steve's concern, perhaps replace the last sentence with For best performance of most browser plugins, you may want to omit LIBPATHSTRICT for your primary browser and only set it for your other Mozilla apps. Did you remove the mention of the -no-remote parameter on purpose? >* Doodle ScreenSaver - Intelligent Timing for Internal Cleanups > When Doodle's Screen Saver (DSSaver) v1.8 or later is installed, > Firefox can determine how long the user has been inactive. This > let it suspend reloads of "Live Bookmarks" and perform cleanup > operations during idle periods rather than while you're browsing. > ftp://ftp.netlabs.org/pub/dssaver/dssaver_v18.zip Same as above. >=============================================================================== >-- Environment Variables ------------------------------------------------------ >=============================================================================== > >These can go in config.sys or the .cmd file you use to start Firefox. Do we need to mention the firefox!.env file here, too? >* MOZ_PLUGIN_PATH=[path] (recommended) I wouldn't recommend this, as it's already %MOZILLA_HOME%\Mozilla\Plugins it %MOZILLA_HOME% is defined. The stuff about clipboard was added at some point by request of people on the newsgroup. Did you remove that on purpose? Hmm, it doesn't fit well with the structure. Can you not make a main section "Known Issues" and list printing, fonts, and clipboard under that? That would also help to explain for Firefox 3.5 (if we ever release that) that @font-face and media support are missing. I have the feeling that you removed something else that I found important but I currently don't see what that might have been. ;-)
I'll probably not be able to work on any bugs in the near future.
This is a mass change. Every comment has "assigned-to-new" in it. I didn't look through the bugs, so I'm sorry if I change a bug which shouldn't be changed. But I guess these bugs are just bugs that were once assigned and people forgot to change the Status back when unassigning.
Created attachment 580817 [details] Unified readme Text of proposed readme.* replacement. Authoured by Rich Walsh with a couple of minor updates
+ - Recent kernel, 1.04a is recomemended. + (http://www.os2site.com/sw/upgrades/kernel/w420050811.zip) I'm not sure 2005 counts as recent. ;-) It should be 14.104a. How about: + - Kernel with build level 14.04a is recommended.
Would be nice if comments 9-11 were also addressed.
Created attachment 580832 [details] Unified readme with typo fix
Created attachment 580836 [details] Unified readme with Steve's comments addressed. (In reply to Steve Wendt from comment #17) > Would be nice if comments 9-11 were also addressed. Hopefully I've addressed them. Just reuploading the readme for now.
Thanks, Dave! Minor comments: 1) Typos: - * These applicationa are subject to the terms detailed in the license + * These applications are subject to the terms detailed in the license - recomended to remove browser related entries from the registry. + recommended to remove browser related entries from the registry. 2) nit: Hobbes URL for mozinst can be shorter: - http://hobbes.nmsu.edu/h-search.php?button=Search&key=mozinst&dir=%2F + http://hobbes.nmsu.edu/h-search.php?key=mozinst 3) WorkPlace Sans link points to non-bitmapped version; perhaps point to Alex's website? Recommend the bitmapped version? - http://hobbes.nmsu.edu/h-search.php?key=wpsu_ttf +? http://hobbes.nmsu.edu/h-search.php?key=wpsu_bit +? http://users.socis.ca/~ataylo00/creative/fonts/workplace/#wpsu 4) Grammar: - let it suspend reloads of "Live Bookmarks" and perform cleanup + allows it to suspend reloads of "Live Bookmarks" and perform cleanup - The mozinst.zip package includes an utility to do this and is + The mozinst.zip package includes a utility to do this and is 5) RWS crashes - it's currently suggested to try disabling RWS if "Program crashes when downloading files or viewing FTP listings" but the reproducible crash I have seen is when dragging with the mouse (since Rich said this was a bug in RWS, I have no reason to doubt it). Perhaps amend the text for that?
Created attachment 581191 [details] Unified readme with Steve's comments addressed. Points 1 to 4 addressed and I've expanded the RWS crashes section. There have been reports of crashes that were fixed by disabling RWS and in my case Thunderbird would freeze when loading some messages with attachments, SeaMonkey also started freezing on some sourceforge download pages. This on my crufty Warp 4 install. The freeze was interesting as the frame was still responsive, just nothing in the frame forcing me to kill the application.
- allows it suspend reloads of "Live Bookmarks" and perform cleanup + allows it to suspend reloads of "Live Bookmarks" and perform cleanup Otherwise, looks good!
Created attachment 582184 [details] Unified readme with Steve's comments addressed.
Created attachment 583076 [details] [diff] [review] The patch for mozilla-central
Comment on attachment 583076 [details] [diff] [review] The patch for mozilla-central r=me, though I didn't actually read the README. (shocking, I know! ;) Nit: Will OS/2 open "README.OS2" as a text file easily enough? You could just call it README.TXT or READMEOS2.TXT. It's been years since I ran Warp, so I don't remember. Fine either way!
(In reply to Justin Dolske [:Dolske] from comment #26) > Nit: Will OS/2 open "README.OS2" as a text file easily enough? It's a common enough convention; and as I recall it will open in the system editor if you haven't defined anything different. > You could just call it README.TXT I think that change was decided previously: https://bugzilla.mozilla.org/show_bug.cgi?id=561481#c29
Created attachment 585113 [details] [diff] [review] Install the unified readme for comm-central
Dave, can you clarify what is supposed to be checked in? By "Don't check in the actual readme", do you mean the readme attachment, or the readme file changes in the reviewed patch?
Created attachment 588323 [details] [diff] [review] Patch for Mozilla-central, refreshed for bit rot.
Comment on attachment 588323 [details] [diff] [review] Patch for Mozilla-central, refreshed for bit rot. Sorry, I screwed up the r+, it should be firstname.lastname@example.org who r+ the patch before bitrot set in.
(In reply to Dave Yeo from comment #30) > Created attachment 588323 [details] [diff] [review] > Patch for Mozilla-central, refreshed for bit rot. Um, is it intenional that the refreshed patch does not contain the new README.OS2 ?
(In reply to Walter Meinl from comment #32) > (In reply to Dave Yeo from comment #30) > > Created attachment 588323 [details] [diff] [review] > > Patch for Mozilla-central, refreshed for bit rot. > > Um, is it intenional that the refreshed patch does not contain the new > README.OS2 ? removing checkin-needed...
OS/2 is no longer a supported platform.