Tag Archives: Linux

Netscape Communicator 4.04

Introduction

This may all seem like a pointless exercise. I mean, everyone has used Netscape, right? It is the most used browser for a reason. Or is it? This review is here for two reasons:

  1. Because everyone has used it. As one of the first reviews, you can see what I’m aiming for.
  2. Because many people don’t look past the hype. Microsoft bad; Netscape good. Reality is not as clear cut as this.

The main problem I have reviewing Netscape, is that browsing the web is supposed to be simple. A browser should be simple to use, and display any page you might point it at. With a few caveats, Netscape can do this and much more, but it does leave precious little to write about. Except the bad bits. What I’m trying to say is that, although this may look like a very negative review, there are lots of good things about Netscape. For example, this page has been put together using Netscape Composer, not as part of the review but because I think that it’s a good tool for the job.

How well does it display pages?

Since Netscape practically invented the web as we know it, it is hardly surprising that many pages are either designed for or work flawlessly with Navigator. Navigators hold on the browser market is such the many other browsers have actually implemented some of Netscape’s bugs so that their display pages much better!

I suspect that this state of affairs is unlikely to continue. Navigators implementation of many newer standards falls short in either completeness or implementation. The version of Java that Netscape provide with Navigator is significantly slower than that provided by Microsoft, although in its defense it is slightly more ‘pure.’ Cascading Style Sheets and DHTML is poor, and many plug-ins seem to cause it to core dump — not very user-friendly! (This last flaw is supposed to be fixed in 4.05, but I’ve not seen an RPM of this yet.)

It’s difficult to blame Netscape for X’s failings, but it does affect its page rendering. I find that X is nowhere near as good as the Macintosh or Windows at rendering fonts. Perhaps its the configuration of my X server, but I don’t think so.

Stability

Communicator has a very large memory foot-print. Just loading Navigator and loading a fairly simple page can take up to 20 Mb of memory, which although not unusual, does seem somewhat excessive.

One can partially understand the memory requirements when looking at the installation — just one executable. Composer, Navigator and the mail programs are all in one, huge executable. This is bound to stress the OS (Linux can handle it!), but does mean that Communicator dies when one component dies. I’ve lost work in Composer on a number of occasions while jumping across to Navigator to look at some web site.

Although it’s difficult to quantify this kind of thing, I feel as though I’ve had more stability problems with Netscape than Internet Explorer. Navigator also seems much more stable under Windows than Linux. This does seem contrary to most people’s experience, though.

Other Parts

Almost all of the review so far has concentrated on Navigator, since this is the part of the product that people actually download it for. The other bits are at least passable, though.

I suspect that Composer is the best WYSIWYG HTML editor available for Linux (not much competition!). It’s rendering of most pages is very impressive, although it can get very slow when there are lots of elements on the page — tables really start to bog it down — and it has no concept of frames. Probably a good thing!

The Mail and News client is very good provided that you have a permanent network connection. It doesn’t have off-line news reading like much of the competition, which is going to rack up your phone bill (if you have to pay for local calls) unless you can get another program to do this (there are many available, mostly for free).

Conference and Netcaster, two modules available in Windows, are not supplied with the Linux version. (I doubt that many people use them anyway.)

I installed Communicator using the RPM available from RedHat’s web-site (netscape-communicator-4.04-3) and experienced no problems at all. I think I’d have preferred it to have been installed in /usr/local/bin rather than /usr/bin, but if I wanted to be picky I could have downloaded the application from the Netscape web site.

Overall

My impression of Communicator 4 is that Netscape are starting to run out of ideas and inspiration. Navigator 3 came with many new and important features, but 4 just seems bloated. Why when I download a browser do I have to get a mail and news client and a HTML editor? Why do many of the features seem half finished? Why is the stability of the product only becoming acceptable after nearly a year? Why, when the competition are pumping out a significant release every six months, is Communicator over a year old?

But let’s not let this get out of hand. Netscape may not be the leading force it once was, but it is still a top class browser. It’s performance and features keep at the top of the pile for Linux (and near the top for Windows), and its re-launch as a free product can only help its popularity.

NEdit 5.02

Introduction

The bottom line is this: I’m lazy. At work I chop and change environments every few months. I usually manage to use Windows NT as my client OS. Then at the server end there’s Solaris or HP-UX. And then I go home and have Linux and Windows 95 to play with.

It gets confusing after a while. Emacs doesn’t think very much of me pressing ESCAPE-k-k-k-a when I try and put something at the end of the third line up. And Notepad is unimpressed with ^X^C when I try and quit.

No, what I needed was some consistency. ^C to cut and ^Z to undo, please and thank you.

And then out of no-where, NEdit appeared. (In all probability, it was Freshmeat, but you get the idea.)

What’s it do?

More than Vi and less than Emacs.

NEdit sit in the middle ground doing just about everything that most people want to do. It doesn’t check your mail, it doesn’t let you surf the net. But it does help you edit your text.

It will high-light the syntax of your program, and if it doesn’t know about the language that you’re using you can tell it. (I added most of PL/SQL.) It uses most of the conventions that you’ve got used to in Windows and the Mac — like ^Z to undo ^N to start a new document. I still sometime press escape at the end of a paragraph, but that’s just me being brain-washed into the ways of Vi at an early age.

To appease ‘normal’ Unix people, it is also scriptable. There’s a macro language and you can call programs from the ‘Shell’ menu. The macro language is nothing like Emacs, but does support functions and variables and seems to be able to do all the basic stuff and some of the more complex things that people want to do. (I’ve not had need to look at it in any detail, the truth be known.)

While we’re talking about configuring it, NEdit is very strong in this area. It is a little confusing at first — the obvious menu items refer to this session of NEdit rather than NEdit as a whole — but once you’ve lost all your settings a couple of times everything become clear! You can change just about any aspect of the program, from the font, it’s colour and size, through to the size of a tab character. And none of this requires the editing of a text file — it’s all menu based.

It’s all a bit too user-friendly to be a real Unix application, but I’m not complaining.

What’s wrong with it?

I’ve been using NEdit on and off for nearly six months now. I’ve used it to edit HTML, C, shell scripts, plain text, Perl and various configuration files, and there’s nothing that jumps up at me and says ‘that’s wrong!’

Okay, the help could do with being more Window-ish, but then it’s not something you have to use very much. There are some languages that don’t have syntax high-lighting built in (SQL and PL/SQL are the ones that immediately spring to mind), however there is a huge list there so I’ve probably just been unlucky — and I can add them myself if I want.

NEdit is supplied as two executables. The main one, nedit, does exactly what you’d expect. There is a second one called nc which is slightly confusing. As I understand it you should use nc most of the time. What it does it open the document with an existing copy of NEdit if there is one, and starts one if there isn’t. This is a useful feature, but I don’t understand why it couldn’t have been included as part of the main executable.

Finally, and this probably just the executable that I picked up rather than any of the author’s faults, the executables were not ‘stripped’ (meaning that it was over 200K bigger than need be). Still, it was easy to fix and it only comes in at around 2Mb, anyway (presumably with Motif libraries linked in).

Verdict

NEdit is a class application. It brings a simple to use, yet powerful editor to Unix. Since Emacs and Vi — incredibly powerful but ridiculously complex and user-hostile — still seem to be the most popular editors, this is something we need to bring Linux to the masses.

LyX 0.12.0

Introduction

When I was at university, a software engineering class had a huge argument with a lecturer. It wasn’t about any high flying computer science ideal, just how people do their word processing.

My lecturer maintained that people were interested in the text and the text alone. People should be willing to use standard text mode editors to lay down the text and then use a text formatter such as TeX to print it. The text and the formatting, she said, were completely separate.

Most students in the lecture agreed that while, say, Emacs could handle much larger files than Microsoft Word, most people were unprepared to hack around with command lines and obscure key-strokes just to write a letter. Most ‘normal’ people agree with us.

Unfortunately, the former approach has many advantages when writing long, structured documents. What we could do with is a compromise. What You See Is Almost What You Get perhaps.

LyX, as you may have guessed, is just that compromise.

What does it do?

In short: long documents. Okay, it’s quite happy letting you edit a letter, in fact it comes with a number of templates to allow you to do just that, but this is not what it excels at.

To test out LyX, I converted a long document that I’ve been using Microsoft Word to edit until now (don’t get too excited, this was a manual process!). Word wasn’t having too much difficulty with the size, but I was starting to have problems with styles and cross-references.

The first thing to note is that you have to be organized. It’s tempting in Word to just change the font or its size directly, but this is a big no-no in Lyx. You should create a style for every type of paragraph that you need. In my case I used the defaults that came with LyX and applied them to my text.

All this was incredibly straight-forward and very Windows-like. You can high-light the text by dragging the mouse over it (it turns cyan), delete text with the delete or back-space key and all the usual conventions — not something to be taken for granted in Linux.

Then I hit a bit of a problem. In Word, I had all my lines of code numbered. How could I replicate this in LyX?

To cut a long story short, while I’m sure that you can do it, I have no idea how. I suspect it has something to do with the style-sheets (like in Word), but I couldn’t figure out how to change it graphically and I have no inclination to start hacking around in the TeX source files.

In fact this is the most damning criticism of the program as a whole: you still need to know about TeX. If I’d wanted to know about that I might have stuck to Emacs! It is still a very useful program, but to get the full flexibility of the system you’ll need to get your hands dirty!

From bad to worse

Having found my first problem, things started getting even worse. I couldn’t get the cross-referencing to work either. I’m pretty sure that this time it’s because I’ve been brain-washed with nearly eight years of using Word for Windows. When I say that I want a cross-reference, I expect to be able to say which heading I want to reference and how I want it to be displayed (i.e. the text or the section number or the page number, or some combination of them). In LyX what I get is a box with five buttons and a message saying “No labels found in document.”

I managed to partly solve this by creating a number of labels which I could create cross-references to. However, this was nowhere near as flexible as Word. Do I have to create a label at the source of every cross-reference? (This looks like something else that’s been carried over from its TeX heritage.)

User Interface

Taking a step back from my difficulties, what’s it like?

LyX uses the XForms library, which some purists hate as you can’t get the source code for. In its favour, it does look very smart. The menu’s are a bit more ‘sticky’ than I’d like, but there’s nothing wrong with them. It makes LyX look like a modern Windows application, and I mean that as a compliment.

However, it’s not quite as intuitive as it might be. For example, many of the keyboard short-cuts are non-standard. What’s wrong with Ctrl-I to start and stop italic mode? How do I change the formatting of a style? How do I create a blank line?

It’s also fair to say that the configuration isn’t as easy as it could be. As has been mentioned before, I tend to use TrueType fonts rather than those that come with XFree86 and I wasn’t too upset to learn that I’d have to configure LyX to use them. It was good to see ‘Screen Fonts…’ under the Options menu; it was equally good to see that changing ‘times’ to ‘times new roman’ had immediate effect. What was not so good to see was that it had forgotten the setting next time I started. It turns out that the best way to keep the settings is to edit the ‘lyxrc’ file in the LYX_DIR directory. Okay, we can’t expect LyX to make global changes, but why not local changes?

Overall

As someone that writes many more structured, technical documentation than letters (sorry Mum), Lyx is just the kind of thing that I’m looking for.

It’s not as easy to use or well integrated with the print system or print preview program as Microsoft Word, but it is much better at handling tables and equations, not as though I use many of the latter.

However, for my purposes I think I’ll stick to dual-booting and Word 95. LyX shows a lot of promise and is very good at what it already does. However, I think that you’d have to be a TeX guru to get the best out of it, and that rules me out.

Linux 2.1.131

Introduction

It’s a long time since I used a development kernel. In fact, I don’t think I’ve ever just downloaded the source and built it myself. The last time I was on the cutting edge, it came as part of an installation of Slackware. I think it was 1.1.59, and seemed to be no less stable than the real thing. So maybe it’s a little surprising that since I moved up to a Pentium I’ve always stuck with the stable 2.0.x series?

Not really. I’m a coward, firmly fitting into the ‘if it ain’t broke, don’t fit it’ mould. Not only was I on a faster machine, but 2.0 was faster than 1.2. Why would I risk breaking things for a few extra percent?

In a sense, I think I was right. But I’m getting ahead of myself, let’s get the thing installed…

Quick Aside

I expect that most people reading this will already know about Linux’s version numbering conventions. If you fall into this category, you may as well jump to the next section.

If you’re still with me you may be wondering what all the fuss about Linux 2.2 is and why there aren’t any Linux 2.2 betas.

The reason is simple: way back when Linux 1.0 was released, Linus Torvalds decided that all stable, ‘release’ versions would have even version numbers. In the case of release 1.0.9, ‘1’ is the major version number, ‘0’ is the version and ‘9’ is the patch number. Since ‘0’ is even it is considered a stable, usable by ‘normal’ people version.

The version I tested was 2.1.131. ‘1’ is odd so this is a development kernel, usable by people that are prepared to accept the occasional glitch. Note, however, that the kernel is now in a ‘feature freeze’ which means that only bug-fixes are being added. Put another way, even this development version should be, and is, fairly stable.

Upgrade

Linux sits very much at the heart of your system, and any upgrade to it shouldn’t be taken lightly. That’s why, for pretty much the first time in history, I took a look at the documentation.

make config ; make dep ; make clean ; make zdisk ; make modules ; make modules_install

What could be easier?

Well, after being cushioned by using RedHat for a number of years it was a little confusing to be expected know which options I needed to set. Nothing I couldn’t deal with — and nothing unexpected — but I just want to make it even clearer that this isn’t something that someone who has difficulty installing a Windows 95 application would want to do.

I must confess, however, that it wasn’t as difficult as I’d expected. It only made me happier when I rebooted my machine and it started, apparently, without problem.

In Use

In use it doesn’t feel at all different to 2.0. Running some unscientific benchmarks I find that it is, indeed, slightly faster and it does use slightly less memory, but I don’t think that’s the point. The point is that it now runs on even more machines, from i386’s to Acorn Archimedes, in even more configurations, from SMP to X.25. The point is that it now optimizes for many of the Intel compatible CPUs and handles many of their bugs.

However, it’s not all rosy. The PPP daemon from RedHat 5.0 doesn’t work out of the box. You need to download and compile a new version. I found this more difficult than building the kernel! (The problem was that it expected to be built at /usr/src and failed anywhere else with screens of not very obvious errors.)

And I’ve not managed to get my 64AWE Gold working yet, either. This is more laziness than anything else, the instructions look fairly straight-forward.

More seriously, one of the main new features seems not to work on my machine: the graphical console drivers. Normally this wouldn’t matter too much. I spend almost all the time in X anyway, so some memory uselessly set aside just for the sake of being cutting-edge is not really worth it. However, one main benefit of the graphical console is the Tux logo when Linux is booting…

Actually, it is useful. It means that there’s a standard interface across all Linux platforms, from i386 to SPARC. But not, apparently, if your video card doesn’t support the VESA 2.0 standard. I would have thought that this is relatively rare. My machine is less than three years old but only supports VESA 1.2.

Other bits and pieces

Looking at Joseph Pranevich’s excellent “The Wonderful World of Linux 2.2” in this months Linux Journal (December 1998), it would seem that my ‘aging’ hardware is unable to take advantage of most of the fancy new stuff.

For example, if you have a multi-processor box, 2.2 will work much better. There’s improved support for non-x86 architecture machines and there are optimizations for non-Intel x86 machines, too.

Overall

The new development kernel is smaller and faster than the current stable version and still appears to be rock solid. I’m not sure how the development team keep managing it when the millions of dollars that Microsoft invest seems only to increase bloat.

However, the features that have been added seem to be there to please ever more niche markets.

In summary: the best has managed to get even better.

WINE 980614

Introduction

This is the second time in as many reviews that I’ve started like this: I don’t want this to be the start of a trend. I did say in my ‘policy’ document that I didn’t want to look at very early releases of software and I stand by that.

However, sometimes you see something and, even though it doesn’t work fully, it show such great promise that you need to shout about it. WINE is such a piece of software.

What is it?

Wine allows you to run Windows applications on x86 Unix machines, Linux in this case. It should work on almost any PC based UNIX like NetBSD, UnixWare, etc. and it’s supposed to run 16- and 32-bit Windows applications, although the former are much better represented at the moment. There are some that will never work properly (the FAQ says something about VxD’s which I don’t understand).

At least, that’s what it will do. At the moment it is a developers release, not even stable enough to be called beta software. However, I’m not here to bash Wine because it’s in its early stages of development. I’m here to express how shocked I am that it’s so good!

Installation

I’ve tried a number of times in the past to make Wine, and they’ve all ended in tears. I rake around my hard disk trying to find enough space — around 50 Mb — spend ages while it compiles and then when I run it I find that there’s been a segmentation fault in 32-bit code. I don’t know what that means, only that it’s not mentioned in the FAQ and that I can’t run anything, not even Notepad.

Then the other day I decided to make one last attempt and, rather than get the source code, I got a precompiled RPM. It didn’t work at first. I had to customize it, changing the configuration file to match where my Windows 95 partition is, but nothing too arduous (or unexpected).

So, I fired it up trying to run calc.exe. I wasn’t hopeful, and the fact that it was taking 100% of CPU and seeming to get nowhere fast didn’t help. I left it chugging away and made some coffee and toast.

Success!

When I returned from the kitchen, the Windows Calculator was sat proud in the middle of my Trinitron. My jaw dropped, and the dog nearly got my toast.

Okay, the display wasn’t completely right. The text in the title bar is far too small, the buttons are in the extreme top left and right rather than in the middle of the bar, and the font on the menu bar is proportionally spaced meaning that it looks rather odd, but I suspect that this is all configurable — you can certainly tell Wine to use your window manager rather than X directly.

But it worked. I could do sums; I could change between normal and scientific mode; I could get the About box. I was stunned.

Moving onto Notepad, I found that the same was true: it worked. I trundled though a few other applets that Windows 95 comes with, many of which, at least partially, worked.

Getting arrogant

Having got the tiny programs working, I started hunting around my hard disk for new challenges. Why start small and build up, I though. ‘wine "`pwd`/winword.exe"‘ I typed. That’ll show it.

I started on my toast, figuring that it’d take a while before it gave up.

But it didn’t give up. After a worrying amount of disk activity, the Word 95 splash screen appeared. As did screens and screens full of errors in the console window. Despite the errors, Wine and Word battled on, eventually displaying the normal Word screen, tool bars, menus and all. Again, the fonts weren’t quite right and the toolbar was far too dark, but there it was. Linux running Microsoft Word 95.

Tentatively I entered some text. This worked fine — even the font rendering was spot on — until I mistyped something. Word underlined the suspect characters with a wavy red line and then crashed.

Next time I managed to get the About box (fairly simple, but with a big bitmap and a sound clip) to display, followed by the Options dialog (big with lots of tabs). A few others also worked without problem. The open dialog, however, causes Wine to exit. I guess this is because Microsoft didn’t use their own standard libraries for the task! (Let’s blame Microsoft.)

Excel works roughly as well as Word. It starts without any problems, you can enter data in the cells and auto-sum works. Many of the dialogs appear, full and correct, but save crashes the system. PowerPoint vanished shortly after completing loading and Access didn’t even get as far as the splash screen.

I was very surprised at the success that I’d had up to this point. Okay, nothing useful actually worked, but I was looking from more of a technical point of view. I did, however, find a program that worked incredibly well, something much larger than clac.exe or Notepad. The program? Maxis SimCity for Windows 1.1. (Saying that it’s useful is stretching the point, but I digress.) I play tested SimCity quite thoroughly and found that, although small parts of the screen occasionally became corrupted, everything worked. Since games are usually associated with some of the worst coding and low-level hacking around this was good. (I’m not sure whether the credit should go to the Wine team or Maxis!)

Overall

I’ll not mess around: Wine is not ready for the prime time yet and is still some way off. This is not news, the developers say this too.

What is news is that it is an incredible piece of software. A non technical user might not see this (unless they want to play SimCity), but anyone who has written a non-trivial program can see what an incredible achievement Wine is.

UAE 0.7.6

Introduction

On the subject of emulators, there are two main factions. The first says that they are a good way of using all the software that you had for your previous computer when you upgrade. The second say that an emulator is a sure sign that a platform has no software. Why, they say, would you have an emulator if you could get as good or better software for your new machine? (They seem to forget that there are loads of emulators for DOS and Windows.)

I was first introduced to a useful emulator when I still had my old 386. A 386 has roughly enough power to run Sinclair Spectrum software at full speed. This was great: I could bring Bomb Jack, Manic Miner and Nebulous with me! And I could save levels and I could load complete games in a split second rather than ten minutes. The emulator was better than the real thing!

But my Amiga software just sat in the box. I had no way to bring that with me. Until now. PC’s are just about getting to the point that they are able to emulate and Amiga at full speed (and if they’re not then I can run them on my HP K box at work!).

Installation

The long and the short of it is that I’m lazy. If I can download an RPM archive of a program, I will. It’s not that Ican’t build programs — most work days I’m up to my arm-pits in C and Makfiles — it’s just that I want to use a program straight away. Okay, that makes me impatient too.

I’ve not been able to find an RPM of UAE, so I downloaded the latest stable version I tried to build it. Normally these GNU ‘configure’ scripts are straightforward: type configure; type make; and everything is ready. Configure usually goes away and finds the various bits and pieces without any trouble. The UAE configure script, however, couldn’t find my GTK library (I have the correct version according to the documentation) and it couldn’t see that I had the SVGA library, and the DGA support, which it did find and claimed to be using when I started UAE up, didn’t give full screen support.

So to summarize, I couldn’t get a nice user-interface and I couldn’t get full screen support in console or X. I wasn’t impressed.

Does it work?

It shows how long ago it is that I used a real Amiga. Like all the various kinds of memory that a PC can have (EMS, XMS, conventional, high), the Amiga has a number of different types too. I used to be able to remember all of them, what they are, what they do and why they’re there — on both the PC and Amiga — but I can’t now!

That’s to say, some of the programs that I couldn’t get working might, in fact, work fine if you can get the right combination of memory and video settings. This isn’t a criticism of UAE as such, more of the Amiga. It might be possible for the UAE team to add hints, though. (I never programmed my Amiga much, so I don’t know whether that would be possible.)

But I did have a number of successes. Workbench 1.3 seems to work fully (I’d forgotten how bad it looked), as does AmigaBasic and Deluxe Paint. With the windowed version of UAE, it is normal to have the Amiga mouse-pointer being completely independent of the X pointer. I find this annoying, but you can switch it off.

Perhaps more impressively I managed to get some games working. Arkanoid 2 works flawlessly; International Karate+ seems to work okay, albeit from the keyboard; Populous ran; as did Pacmania. However, all ran somewhat slowly. Arkanoid was fine unless the sounds was switched on. This slowed down the game, and the sound kept breaking up. Probably the worst was Pacmania, which was far too slow. The documentation does warn that some of the scrolling effects are the most processor intensive, and this is obviously the problem here.

As I mentioned before, there were a number of games that I couldn’t get working at all. Chase HQ gave me nothing more than a black screen. Rampage crashed. Paperboy didn’t work. Simulacra didn’t start. Maybe these will work if you twiddle with the memory settings?

In use

While it’s true that the performance and sounds problem can be overcome by throwing extra hardware at it, I think it’s fair to mention that most games are unplayable on a mid-range Pentium (120). Many application are probably okay, maybe even faster than the real thing, but I can’t see why anyone would want to run Amiga productivity software on a PC. Microsoft Word or LyX would be far better than anything on an Amiga.

UAE is supposed to come with a GTK-based front-end. I never managed to get this working, so all I was left with was the command line. This left no way to switch disks — they are emulated by files on your hard-disk — after the emulator had started, and no way to edit display or sound settings without resorting to obscure command-line directives.

Overall

I get the feeling that the UAE team may have bitten off more than they can chew. The Amiga was always considered a powerful machine, and trying to squeeze it into a ‘well behaved’ operating system like Unix was always going to be difficult. (One of the best Amiga emulators, Fellow, runs under DOS which is a far better option. There’s no chance of you being preempted by another process or user and you have full control over the screen.)

Maybe I’d have been more impressed if I’d managed to get the user-interface and full-screen mode working. And maybe I’d have been more impressed if I could install Linux on my PII at work. But I wasn’t and I haven’t, so, for now, I’m going to leave UAE well alone.