On Wed, 21 Nov 2001 01:35:44 +0000
David
I am running KDE but it is said to be ok so long as the Gnome libraries are installed.
It looks like you have spotted and corrected the typo in my last post, where I said "former" but meant "latter". It is correct that if you have the libraries gnome apps will generally run under kde and vice-versa. I have noticed, however, that occasionally you will see (generally harmless), error messages thrown up because the application is expecting to find its full enviromnent, and doesn't.
It is meant to start on dial up, but doesn't. The alternative is to put it into the start up, there are only instructions for RH. Where do I go in Suse.
I think you need to be careful here. To begin with, are you sure that your configuration survives the destruction of the particular instance of ppp0 that is running during the online session when you configured it? You will, I expect, have a dynamically configured IP address, which changes from session to session, and which Firestarter may extract for its own use when ppp0 is up and which it cannot extract again until you reconfigure. That is *not* necessarily the case, but if it *is* then there is no point to trying to start Firestarter automatically until that issue is sorted. Secondly, if it is meant to start on dial-up, then I would have thought that the right approach would be to modify something like /etc/ppp/ip-up rather than have it run at boot-time. Take a look at that script - it contains some commented-out options for starting stuff that one might use as a model. I have never done this though - if anyone reading this knows better please post accordingly. Third, there are several ways of having things start at boot-time. The easiest is to put them in the /sbin/init.d/boot.local script, which SuSE has kindly provided for your convenience. At least I assume that you have this, please do bear in mind in reading anything I write that I am using 7.0 and your 7.2 may differ. There may be a problem with the boot.local approach, however, because I do not think that the network will be available at the time when it runs and that *may* screw up Firestarter's initialisation - I am just guessing here. If the boot.local approach does not work, there are slightly deeper alternatives, but we need to bear in mind that any errors we make in modifying your boot structures could leave the box unbootable. That can usually be fixed via the SuSE rescue system, but we obviously do not want to get into that if we can avoid it. May I suggest that you (a) make sure that your configuration survives going on and off line a few times. (b) Post the RH instructions so that we can see if they modify easily for SuSE. We can then take it from there.
On connection I think I am using kinternet, little plug in bottom right hand corner. Can it be configured not to disconnect after a couple of minutes.
Is there an equivalent to the Windows modem lights in the sys tray. I find it useful to know what is going on.
Back when I was playing with KDE I used Kppp, which had the lights you need. I never tried kinternet. There are many mini-apps that show the lights (asmodem is one ), http://www.tigr.net/afterstep/list.pl) I suggest, however, that you try Kppp first unless that has gone from the current KDE.
Now I have to work out how to get the Win box to connect through.
That may involve sending an evelope stuffed with fivers to Mr Gates ;-)
Regards,
Geoff _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com