Good news now about SRWare Iron - It is running in uPup 4.76

[playdayz]

ADD: There is some good news now about SRWare Iron in the bottom message of mine. It is running reasonably well in uPup 4.76.

Here's a challenge for whomever wants to take it

SRWare Iron for Linux alpha 3.0.197 - a version of the open spource Chromium browser http://www.srware.net/en/software_srware_iron_news.php

It needs dbus and dbus-glib, libgconf, and libORBit, but once those are provided it seems to want libc-2.8, but that makes 4.3 freeze such that you can click to your heart's content but no further programs will run and then I have to reset. I like FF 3.5.x and I have used FF forever it seems like, but Iron is way so much faster, noticeably, significantly, and I regard that as a quality of use factor. I ran Iron for Linux alpha in Ubuntu 9.04 to see how it works and I was impressed. Did I say it was faster?

And, oh, yes, Iron has an adblock feature that 1) does not slow it down, and 2) Google Chrome does not have the adblock feature--I wonder why?

The numbers: Iron for Linux alpha, Peacekeeper, 3348 - Firefox 3.5.3, 1689 (on my machine - number is a "score" not directly a "speed" but it corresponds to speed)

[Patriot]

Hmmm .....

........ SRWare Iron for Linux alpha 3.0.197 - a version of the open spource Chromium browser ........

Dear God Almighty in heavens ..... just the alpha binary stands at 15MB but the archived sources at 300MB (is my eyes deceiving me? If it is then I'll need more coffee) ... I'll just play with Seamonkey thank you .....


Rgds

[Makoto]

And, oh, yes, Iron has an adblock feature that 1) does not slow it down, and 2) Google Chrome does not have the adblock feature--I wonder why?

Well, Google does do a bit of work with ads - such as AdSense and those "Ads by Google" text ads you see now and then - so, how would it look if Google released a browser with an adblock feature?

[disciple]

I was looking into Iron the other day
For anyone that wants to get Iron working here's some stuff you might want to know first:

The build they provide depends on these things, which are newer than Puppy 4.1.1 has got (don't know about 4.3), but maybe you could build against older versions:

Code: Select all

./iron: /lib/libc.so.6: version `GLIBC_2.7' not found (required by ./iron)
./iron: /lib/libc.so.6: version `GLIBC_2.8' not found (required by ./iron)
./iron: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.10' not found (required by ./iron)

And this, which I have a feeling is actually hidden in Puppy somewhere:

Code: Select all

./iron: /usr/lib/seamonkey/libnss3.so: version `NSS_3.12' not found (required by ./iron)

And gconf. It seems to be happy with gconf-glib which I'm about to post in a new thread (this avoids all the ridiculous orbit dependencies), which requires dbus and dbus-glib.
Iron also wants this:

Code: Select all

        libnssutil3.so => not found

I don't notice any other unusual dependencies but heres the whole
output of ldd

Code: Select all

./iron: /lib/libc.so.6: version `GLIBC_2.7' not found (required by ./iron)
./iron: /lib/libc.so.6: version `GLIBC_2.8' not found (required by ./iron)
./iron: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.10' not found (required by ./iron)
./iron: /usr/lib/seamonkey/libnss3.so: version `NSS_3.12' not found (required by ./iron)
        linux-gate.so.1 =>  (0xffffe000)
        libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0xb7bc3000)
        libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0xb7b43000)
        libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0xb7b2c000)
        libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0xb7b07000)
        libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0xb7af7000)
        libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0xb7aee000)
        libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0xb7a92000)
        libcairo.so.2 => /usr/lib/libcairo.so.2 (0xb7a35000)
        libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0xb7a06000)
        libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb799b000)
        libfontconfig.so.1 => /usr/X11R7/lib/libfontconfig.so.1 (0xb7975000)
        libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xb793b000)
        libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xb7938000)
        libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb786c000)
        libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xb7868000)
        librt.so.1 => /lib/librt.so.1 (0xb7855000)
        libX11.so.6 => /usr/X11R7/lib/libX11.so.6 (0xb7784000)
        libXrender.so.1 => /usr/X11R7/lib/libXrender.so.1 (0xb777c000)
        libXext.so.6 => /usr/X11R7/lib/libXext.so.6 (0xb7770000)
        libnss3.so => /usr/lib/seamonkey/libnss3.so (0xb76fe000)
        libnssutil3.so => not found
        libsmime3.so => /usr/lib/seamonkey/libsmime3.so (0xb76cf000)
        libssl3.so => /usr/lib/seamonkey/libssl3.so (0xb76a4000)
        libplds4.so => /usr/lib/seamonkey/libplds4.so (0xb76a1000)
        libplc4.so => /usr/lib/seamonkey/libplc4.so (0xb769c000)
        libnspr4.so => /usr/lib/seamonkey/libnspr4.so (0xb766b000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xb7656000)
        libdl.so.2 => /lib/libdl.so.2 (0xb7652000)
        libm.so.6 => /lib/libm.so.6 (0xb762f000)
        libgconf-2.so.4 => /usr/lib/libgconf-2.so.4 (0xb760a000)
        libasound.so.2 => /usr/lib/libasound.so.2 (0xb7553000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb746c000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb7461000)
        libc.so.6 => /lib/libc.so.6 (0xb7366000)
        libXfixes.so.3 => /usr/X11R7/lib/libXfixes.so.3 (0xb7361000)
        libXi.so.6 => /usr/X11R7/lib/libXi.so.6 (0xb7359000)
        libXinerama.so.1 => /usr/X11R7/lib/libXinerama.so.1 (0xb7356000)
        libXrandr.so.2 => /usr/X11R7/lib/libXrandr.so.2 (0xb7350000)
        libXcursor.so.1 => /usr/X11R7/lib/libXcursor.so.1 (0xb7348000)
        libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb732b000)
        libz.so.1 => /lib/libz.so.1 (0xb731c000)
        libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb72ff000)
        libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0xb72ce000)
        /lib/ld-linux.so.2 (0xb7f05000)
        libXau.so.6 => /usr/X11R7/lib/libXau.so.6 (0xb72ca000)
        libXdmcp.so.6 => /usr/X11R7/lib/libXdmcp.so.6 (0xb72c5000)
        libsoftokn3.so => /usr/lib/seamonkey/libsoftokn3.so (0xb7278000)
        libdbus-glib-1.so.2 => /usr/lib/libdbus-glib-1.so.2 (0xb725e000)
        libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0xb722d000)
        libnsl.so.1 => /lib/libnsl.so.1 (0xb7219000)

FWIW our company has a javascript based internal web page (well our timesheets actually) that works (in windows at least) in Chrome, but not Firefox... so Chrome/Iron does have at least one advantage over FF (compatibility with at least one site )
I can't say I like it though... I'd choose Seamonkey, Opera, Firefox or even Konqueror over it

[trapster]

The libnssutil3.so and libnss.so were tucked away in the firefox3.5 folder (it may be in the latest seamonkey also) when I was playing with this. I quit when it still needed the GLIBC stuff.

[playdayz]

Well, I got all the stuff

gconf, libORBit, dbus, dbus-glib, glibc-2.8, (nssutil3 and nss3 are in seamonkey), libstdc++ 5 and 6..and Iron started...only to crash immediately; that was in 4.2.1. In 4.3, I got an immediate segfault and never saw Iron boot.

I said it was a challenge I think I will try uPup, because Iron does run in Ubuntu 9.04. Thanks for trying gentlemen.

ADD: Yes! SRWare Iron does run in uPup 4.76. It is not stable unfortunately and if I use it long enough it will crash and cause to me to have to reboot. But it ran long enough to score a 3250 on Peacekeeper, which is over 1,400 points higher than any other browser in any other Puppy that I have tried. The score is not the end all and be all of course, but it does run more responsively than any other browser I have tried--specifically, pages render faster.

[playdayz]

Please forgive me for a double post, but I have some good news about SRWare Iron - It is running reasonably well in uPup 4.76 now. So I thought this deserved its own message.

I made a few adjustments to 4.76 uPup: 1) changed from xvesa to using the vesa driver with xorg (xorgwizard originally choose "fbdev" which wouldn't work so I used xvesa--then I manually changed to xorg with the vesa driver), 2) used Pprocess to kill both hald and dbus (the new browsers need dbus at least on the computer but it doesn't need to be running), 3) I also added video memory up to 32MB (from 7MB). 4) Under Options -> Under the Hood I unchecked Enable DNS pre-fetching and unchecked Enable Phishing and Malware Protection. 5) Increased RAM from 385 to 512MB. Iron is running well now; much longer time between crashes--my fingers are crossed. I would say it is usable now if it keeps this up. . I think that is all I have done. I am posting in Iron now--it tested faster with the xvesa driver (3444-3021) so I might see if I can use that again.

I cannot wait for Puppy 5! My guess is that it was item #4 that helped, but that's just a guess.

[Lobster]

I have run Chrome in Wine (the Windows Chrome is more developed) and liked it a lot. I am looking forward to using it in Puppy. As it is Open source and uses XUL (I believe) - same as Firefox and Seamonkey, adblock and other addons will be possible. I rely on a browser too much to use an Alpha build

[disciple]

changed to xorg with the vesa driver

Sorry to digress, but what is the relationship between the xorg vesa driver and Xvesa? Is there no relationship? Should anything that works with one also work with the other? Does anyone know?

[playdayz]

yes Lobster, I was thinking last night that the crashes might be a problem with the alpha build rather than a problem running in Puppy. i also can't use it for my work--in a browser at least 5 hours per day. How were you running chrome in Wine; was it the original from Codeweavers or one of the more recent versions?

hey disciple, I thought of that--I do not know--it did run better after I changed to the vesa driver in xorg, but I was making other changes and I was not being systematic about them--I was happy just to see it running. I would like to know also if anyone can explain. thanks.