> One odd thing I've had happen intermittently, is that just maybe 1 in 10
> sessions, KDE's system guard will pop up...I don't crash, or lockup, but I
> have to restart D2... Not sure what its supposed to be finding that is
> objectionable...

Hmmm.  That IS strange!  From what you're saying it sounds like you've got 
the whole KDE desktop loaded, taskbar and all.  Is that right?

If so you're probably exposed to every KDE component known to man.  ;)  I 
think  KDE is great; well, let me restate that....I love the apps.  But the 
desktop is a little too restrictive for my personal taste, so I run pure 
Enlightenment (with NO gnome anything) and then enable KDE support for the 
apps that I use from that desktop environment (Kmail, Kword, and Kspreadsheet 
are good examples).  This makes for a light, fast and nimble environment.

This has been a real blast.  I've got total latitude on the desktop, plus I 
can mooch the apps from whatever environment has the best one.  Abiword is a 
gtk app (I think) that I use also, more often that kword.

Maybe if you tried temporarily switching to another WM that you like working 
with, maybe one that's a little lighter, you could learn more about the 
problem.  Or, maybe KDE system guard has a logging system that could be 
looked at or activated.

> Oh, if you have the Bastille firewall installed, nobody else on the LAN can
> join my game if I'm hosting unless I issue a:
>
> service bastille-firewall stop
>
> before starting D2: LOD...

Interesting.  I installed the bastille firewall in one of the first 
installation iterations that I did, but then I read in Linux Journal some 
articles about iptables.  After that I started searching the net and found a 
SLEW of iptables scripts.  This to me seemed a better way to create and 
control the firewall; perhaps bastille does the same thing(using iptables), 
but I figured I wouldn't learn anything new by letting bastille do all the 
background work.  In any case, I was thinking that an iptables script may be 
out there on the net for you that allows D2-LOD to pass through the ports 
that it wants to have.  At the very least, the docs will tell you how to 
construct and issue an iptables command(s) to allow access to the ports you 
need.

If you want to see what D2 is doing while you're on the local lan and 
playing, so you can record what exactly it is doing with what ports and how, 
there's a kewl utility out there that I use called netwatch.  Check it out 
here:

http://www.slctech.org/~mackay/netwatch.html

When you get it installed, use the left/right arrow keys to change your 
views.  I was impressed with the things I could track using netwatch.  
Somebody out there may know about a more informative utility;  but as yet I 
haven't found one.


> This list *rules*...I'd have been lost in Linux without it!

I agree.  I've already solved a bunch of problems just in the short time I've 
been here.

> Thanks, like I said, next time I'm at the local Wal-mart, I'm gonna try to
> find the origianl BG2 and grab it. Oh...did you install it onto a Windoze
> partition first, then run it from there first, or (it looks like) you
> installed it all from Linux (onto a Linux partition)? Thx!

Yep, it was with absolutely no windoze installed whatsoever.  The routine was:

1) Clean from scratch install of LM81; only "KDE Workstation" selected, 
nothing else

2) Individual Package selection enabled; spent an hour an 1/2 picking 
packages by hand, leaving out the junk and unwanted stuff  (specifically 
avoided anything that required "gnome-core" as a dependency)

3) Recorded entire installation routine to floppy

4) Downloaded latest version of Winex (1.03 at the time)

5)  Installed winex and proceeded to run the setup.exe from the BG2 CD

6)  Switched back and forth from Installshield to Eterm to mount and unmount 
the BG2 CD's as needed and called for by install routine

7) Was forced to kill Installshield routine as it attempted to create icons 
on a nonexistent Winblows desktop at the very end

8) Nervously and with shaking hands typed in winex /path/to/Baldur.exe

9) Heart Attack

I tried it because on Transgaming they were talking about some problems they 
had knocked out with the Installshield program in version 1.03 winex.  That's 
what made the whole thing a mind blower; the installshield came up under the 
Hand of God etheme, kind of like in your face!  I wasn't expecting it because 
I'd had some problems with LM80 and winex functionality, so my jaw just 
dropped.

But hey, that was nothing compared to when the main entrance screen for 
Baldur's Gate 2 came up, and the music flowed out of my stereo system.  I 
know I looked stupid with my mouth hanging open and my eyes popping out, 
frozen solid for ten minutes...        ;)


> Absolutely! I was awed the first time I got Starcraft running. Darned near
> speechless (which all my friends would tell you is a truly rare event!!!)
>
> <grin>

lol.  :) 

You been tracking that online game Shadowbane, by any chance?  I heard it was 
going to be the bomb!  Man, if they could get the online stuff working under 
winex, wouldn't that be totally it?


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to