Photo above shows @Macarlo's Caldera Open Linux reporting that Opera file is corrupted Corrupted Opera
File for In Affiliation
=@MACARLO MICROSOFT= =@MACARLO YAHOO= =@MACARLO WEBALIAS= =@MACARLO ALTAVISTA=
|
by @Macarlo
Screenshot by Ksnapshot (KDE)
Hi All.
Yesterday January 11, 2000 and today I tried test on Red Hat Linux and on Caldera
Open Linux the Alpha release of the alternative browser Opera and I simply can't
untar this file! I downloaded for two times the file opera-19991224_tar.tar
(1.90MB). At the first time the file was not in the
correct size. At the second download the size was correct but the file contains
fatal error and can't be totally unpacked.
Opera For Linux 4.0a Can:
At the moment, the development team is using Linux 2.2 systems on x86. There is a member of the team currently working on ports to other platforms. Here's a few of mention:
Although we've mentioned many of the Un*x platforms we hope to support, this doesn't mean we'll get to all of them in the 4.0 release. In most cases, we simply need to recompile for each platform and create a native package for release, there are sometimes complications involved, most notable to mention is with SCO Unixware 7.0.1 which tends to be somewhat difficult to prepare a stable compile and test environment for.
We've put a great deal of thought into this problem. We've decided that initially we'll release only statically linked binaries to limit the need for Qt 2.1 to be installed. Also, for distribution purposes, this will allow the end user to save a great deal of time downloading. We will likely also make available a dynamically linked version of Opera 4.0 for Linux once Qt 2.1 has reached "released" status.
In version 4.0, integration into the environments such as KDE, Gnome, CDE, and others will not be a priority. For example, since KDE 1.1.2 is currently the standard release of KDE and it does not allow programmatically setting MIME types in the environment, we will not have the ability to do this unless we choose to also release a fully patched version of KDE to support this. When 2.0 becomes stable, we will likely add an installation option which allows Opera to act as the primary web browser for KDE.
Actually, the sad but true answer to this question is that GLIBC 2.1 has a serious problem closing certain file and socket handles. We have seen nothing short of unexplainable anomalies related to the close() function in GLIBC 2.1. Currently because of this, we're considering releasing a statically linked libc5 version until this has been brought under control in GLIBC.
Recently we have had a serious problem arise in our communication classes that causes asyncronous DNS lookups to crash the system constantly. At the last minute, the solution we reached is to remove async DNS lookups from the system. This fixed the problem temporarily, but as of the moment, the DNS lookup absorbs massive amounts of time in processing and sometimes even causes the program to freeze up.
Within the last two weeks before release, the method of redrawing the window was changed. This caused images to display the last decoded chunk of data without a hard refresh. Currently we're looking into our image code to see what methods could be used to optimize display refreshes as well as cut memory consumption. At this time, image handling is the largest memory hog in Opera and this has to change before we release. Our footprint during runtime is usually around 7 megs, we're hoping for a maximum RAM footprint of 4.
You can download the hot list for Windows from our support web site, unzip it, then copy and rename it to ~/.opera/opera.adr. This will then add items to your hotlist. The hotlist is currently only partially complete and our user interface developers are working hard on making it work as well as possible.
Yes, but for the moment the only one we'll mention is -page which is used to set the page which Opera displays on start up. For example:
opera -page='www.slashdot.org'
Oops!! This will be fixed in the next release.
Opera for Linux is currently scheduled for Tech Preview updates every 3 to 5 weeks. Now that we have one preview version available, we are working as hard as possible to make everyone say "WOW!!!!!!!!!!!" on the next release. We're can't wait to see what you think of the next one.
Many of the features actually are implemented; however, since we're actively working on major enhancements and improvements to the user interface, we haven't linked the UI to the code. Many of these features are currently turned on and off through code and command line switches. Next release should have most everything in place.
CONTACT AUTHOR
Opera Software
http://www.opera.com/
|
|
|
@Macarlo, Inc.
@Macarlo's Shareware & Web
OS/2
Java Lobby Member
Java Site Accredited
