Crashdamage

Maybe I'm so dull my posting priviledges should be revoked, but unless I'm missing something, looks to me like you've given the router a static IP. Yet you say you've configured Mandrake to look for a dynamic one provided by DHCP. If so. trash DHCP (what you need it for?), tell Mandrake to look for the router's static 192.168.1.1 address and things should go...

Fresh meat!!!

Hey, what I said... Glad you go it going.

I have SBC DSL at my business, and here in Kansas City SBC DSL runs on static IPs, not DHCP. How would the modem maker if know your ISP uses DHCP or static IPs? To find out, post the result of "ipconfig" (w/out the quotes, done from Start>Run) in Win2000 - that should tell you - and to find what your setup in Linux is, post the output of "ifconfig" (done in a terminal as root) so we can see what your settings are. Basically, if SBC SDL in your area IS using DHCP, then go into Mandrake Control Center > Network & Internet and set it to "Find an IP Automatically" (or something like that) or if static IP, then enter your IP and gateway information. I really have no experience with using USB for internet connections except enough to know it sucks. Been known to give problems in Windoze and Linux. 5-6 years ago, when I first got my home Road Runner cable connection as a beta tester for them, they insisted on hooking it up USB. WTF for??? Before the guy was in his truck, I plugged it into my NIC card and never used the USB setup. So I really can't help you with troubleshooting USB much. I wouldn't waste much time on it if I were you.

First thing you should do is get rid of the USB connection and use standard ethernet. Your DSL modem should have both. If for some weird reason it's USB-only, you should be able to exchange it for one that has a standard ethernet jack. Winblows Mac or Linux, ethernet is just a better way to go. Then you should be able to simply enter the SBC-provided info for IP and gateway just like you would for Win or Mac setup (choose LAN, not ADSL) and go. Linux is no different in this regard. Keep in mind that the 'Net runs on TCPIP, and TCPIP is still TCPIP regardless of your OS.

Nah, not really. It gave the other errors because of a 'domino effect' kinda thing. One thing leads to another...and another...soon you've got lotsa seemingly unrelated errors. Windows does the same, gives error messages that have nothing to do with the real problem, and for the same reason. At least Linux gives error messages a poor slob like me can make some sense of, unlike those friggin' BSOD error messages ya gotta be a M$ engineer to decipher.

Aww...c'mon...No OS is going to hold your hand and guide you through the millions of possible f*sk-ups users can do. You're asking for the system to trouble-shoot itself and tell you what to do, something incredibly difficult. And anyway, Linux actually gave you the info you needed, even though not perfectly definitively. How much help do you think a Windows OS would have given you if it failed to boot because you mucked up system files editing stuff as root to make something work? Consider yourself lucky to be running Linux...otherwise you'd probably be calling Billy Bob Gates begging for the code to let you re-install XP. I haven't re-installed Linux (Mandrake 8.2) on my main gotta-get-work-done box in 3 years. I think the reliabilty is just incredible, and I trust Linux (and Mandrake) completely. That doesn't mean I've quit doing backups...

Make sure you are installing Win4Lin v5. Win4Lin v4 and earlier does not work with a 2.6 kernel. If you have Win4Lin v4 and don't want to ante up for the upgrade to v5, you can still make it go by running a 2.4 kernel. If you already have Win4Lin v5, go to: https://www.netraverse.com:9100/lists/ to access the archives for the Win4Lin mailing list: win4lin-users@netraverse.com This question has been covered there several times and you'll get a better descripion of the fix than I can remember here at work right now. A quick search of the list archives should give you the help you need, or just post your question to the list if you can't find the answer. Not only is the help there from other users very good, but the developers themselves watch it closely and often post answers, usually the same day. No one has better customer support than Netraverse.

If you simply run the Win4Lin GUI installer, it will automatically download and install a generic 2.6 kernel, including adding it to your choices of kernels to choose at boot. Netraverse (the Win4lin people) always does considerable testing on Mandrake. This kernel is well tested and known to work fine with 10.0. There are *exact* replacement kernels (i.e. the original Mandrake kernels with no changes except the Win4Lin patch applied) thoughtfully compiled and made available for all by Buchan Milne, available in the Contributors section. Sorry, I'm goofin' off at work right now and don't have the link handy. Anyway, add contrib to your urpmi sources and just install the kernel via urpmi. Then run the Win4Lin installer to load the program, it will detect the patched kernel. Be aware that although Win4Lin is terrific, very fast and stable, it does not support hardware DirectX (software DirectX only). Vmware is just too slow for gaming and costs a bundle. If you need to run games requiring Direct X support, like pmpatrick said, your best bet is Cedega or dual-booting.

Sorry, I meant I have a Diamond Stealth card...Creative/Diamond - really the same, but anyway... $ glxinfo | grep direct Loading required GL library /usr/X11R6/lib/libGL.so.1.3.401 direct rendering: No GLX Gears runs fine, (but of course not at state-of-the-art speeds) 3D is fine, but I never bothered to fool around with enabling DRI. Can't help you there.

For years I've used a Creative S3 Savage 32MB video card. I'm *still* using it. I've never had any problems at all with several Linux distros, Win98, or Win2k. It just works, even 3D. However, I've never tried it with the 2.6 kernel,and I seem to remember hearing of a problem there somewhere. Just a hunch really, but you might try booting Mandrake 10 with the 2.4 kernel and see if that straightens it up. If not, try re-running video setup without the GUI (without X running, from runlevel 3). If that fails...www.google/linux?

Sendmail is THE standard 'nix mailer, by far the most widely used. The bad thing is, setup is a friggin' nightmare. The Sendmail configuration files were clearly dreamed up by an evil sadomachochist bent on total confusion. The good thing is, the default configuration works for most uses. I've never touched the config on my machine, and I can't give you any meaningful help if you need to tweak setup on yours. But in your case, I bet sendmail is not the problem. It seems to be running, since it's trying to deliver the mails, but as you say, they're denied. I'd check closely into your mail client configuration. Read your logs.

Configuration of Portsentry can get a little more complicated than easy-as-pie Bastille. Worth it though, Portsentry is very good. Best thing I can tell you here is, after you install Portsentry go to /usr/share/doc/portsentry-1.1 and do a little reading there, particularly to the /README.install file. No doubt www.google/linux will find more help for you if you need more explanation. As for your Netgear nic card, well, we could get into a long discussion troubleshooting installation. But screw all that - simplify your life and just trash the friggin' thing or stick it in a Winshaft box. For Linux, get a 3Com 3C905B or 3C905C card ($12-15) or a Realtek 8139-based card ($5-10). Most off-brand cards are based on the Realtek 8139 chipset. I bought half a dozen D-Link 8139-based cards for $5 each a while back. 3Com 905 or Realtek 8139-based cards are always properly recognized and configured by almost any Linux (or Windoze) machine. The 3Com cards usually have better thoughput speed so it's the best choice for a LAN where speed is a serious consideration. But the Realtek is plenty fast enough for most oridinary use or any WAN connection (i.e. cable, DSL).

Try man eterm - it should describe the parameters you need. Better yet, use aterm. Much lighter on resources and great for transparency.

Need more info. Open a terminal and as root do: # ifconfig Post the output and maybe someone here can help.

As it is probably the most stable version of Mandrake (or almost any other distro) ever, 8.2 should work very well for firewalling. The posts you've seen for later versions basically apply the same to 8.2, but 8.2 has the big advantage of including the most excellent Bastille firewall/security appliction. For some reason Bastille was not included with Mandrake after 8.2, although it is still under active developement. 8.2 came with Bastille 1.2, which is fine, but 2.0 (2.1?) is the current release. It can be installed on later versions of MDK with a minor hack. For a firewall though, 8.2 and Bastille 1.2 is just fine. In a nutshell... 1. Install 2 nic cards in the 8.2 box. Make the one connected to the 'Net eth0, the other eth1. 2. Install the Bastille package from the 8.2 CDs. As root, run "Interactive Bastille" from a terminal (without the quotes, but with the caps). Read the simple directions and answer the questions using #3 below for a guide. Bastille will not only configure iptables, IP masqurading and NAT for firewalling, but also let you easily configure many other Linux system permissions and security features and really lock up things tight. Be careful not to make it TOO tight... 3. Configure eth0 normally as required by your ISP. Plug the Belkin switch into eth1. Give the Windoze machines static IPs (such as 192.168.0.1, 192.168.0.2, etc.) A subnet mask of 255.255.255.0 is fine. Aim the Windows boxes at eth1 for their 'Net connection. You now have the tender asses of your M$ boxes well-protected. I would also highly recommend installing and configuring the Portsentry package. With Bastille and Portsentry both running and properly configured you have very effective security without having to sacrifice any useablity.

It looks like your Realtek 8139 card was detected and configured correctly, (those almost always are) so that shouldn't be the problem. But since it failed to intialize your 'Net connection, of course ifconfig shows eth0 dropping packets, so you need to look into the TCPIP configuration. Basic, obvious stuff first, just to be sure... Does your ISP run on DHCP or static IPs? If DHCP, did you install and enable a DHCP client? If you did and your connection is DHCP, it should simply obtain a lease and go with no other intervention. If static, have you put in the configuration info, either in Mandrake Control Center or manually? Do you need a plain cable or x-over cable with your Surfboard? And you do have a green light on the nic, don't you?

Browser: Normally Links (text-only) or smetimes links -g (w/graphics). Otherwise Opera in Linux or Windoze. Email: Mutt. Is there anything else? Usenet: slrn. As above.

When I first started to hear about WinXP and just how screwed it was likely to be, I knew I'd better make a move then 'cause M$ lock-in was only gonna get worse. Did some studying on the Web, and it seemed Mandrake would be the best place to start. So I went to the local CompUSA, snagged a boxed copy of just-released 8.0 Standard, went home and did a fresh set of backups just in case. Then I took a deep breath and started installing. Had absolutely no clue what I was doing. I was like a lost puppy those first couple of weeks (months?) and I'm sure some here can remember some really dumb-ass posts from me. Took me a while to stop the Win-think and "get" the Linux way. Some here may think I still don't and they could be right. Anyway, I was lucky I guess - everything worked pretty well right off except the Lexmark printer and HP scanner I had at the time. They soon left for more Linux-friendly Epson models. I've never looked back since, never had any regrets, never considered going back to being a Winidiot for a minute. And even though I've played with other distros and these days I really use Linux more like a Slackware user, I still like Mandrake the best. Flexible enough to use it any way I want, lotsa software available, and urpmi kills any other rpm management system.

Hey, if you really wanna have a good computer, ya gotta build it yourself. Nothing I've ever seen with a name brand on the front could compete with a good 'white box' for real value or flexibility. Laptops, of course, are another problem...

I'll put in another vote for GnuCash. I've used it for about 3 years and I like it a lot better than I ever did Quicken or the oh-so-approriately-named M$ Money.

I've used Fluxbox for almost 3 years, made a bunch of customized themes, played around plenty, but I've never had anything like the problems you have. It just works for me, and always has. Any problems I've had were self-induced, like typos in theme files, etc. And from your posts, I can't make heads or tails outta what you've done, so I don't know how to help you. Maybe the best thing for you to do is uninstall everything, reinstall it from scratch and go from there - after you do some reading. Then try posting any problems on the Flux forum.

It's not the low-cost option (I paid somethng like $165 U.S.) but my Epson 1650 works perfectly with Xsane and gives very high-quality output. Fast, too. Hard to go wrong with Epson printers and scanners.

Fluxbox, but very simplified. No slit, no dockapps - nothing, just plenty of keybindings. Looks great and ultrafast and stable. Sometimes I really get basic with Ratpoison. I've got plenty of horsepower to run whatever, but less is more.

Just to update this a bit...the Win4Lin GUI installer will again do auto-install of a Win4Lin-enabled kernel. This makes installing Win4Lin about as click-click easy for Linux noobs as it can get. However, in accordance with Natraverse's recent decision not to continue to try and keep up with building Win4Lin-enabled versions of all the individual distro kernels (VERY time-consuming), be aware that this installs a Win4Lin-patched generic kernel. It is fully tested (Mandrake is one of the distros Netravese always uses for testing) and should work just fine, but if you want an *exact* replacement of the Mandrake kernel, (identical to the MDK original, except with Win4Lin capability added) it's necessary to download and manually install the Win4Lin-patched kernels in Contrib RPMs built by Buchan Milne.