jcl

QB has loops? Sure, why not. Haven't used it in ages, but it's fairly simple. Since you didn't say what your trouble was, brace yourself for a lot of very poor QB. DO ... LOOP comes in four forms. DO WHILE .. LOOP is, I believe, equivalent to WHILE ... WEND, so just change the words. DO UNTIL ... LOOP is the same but with the conditional inverted, so again just swap the words and change the test expression. DO ... LOOP WHILE ... and DO ... LOOP UNTIL ... may be a little trickier depending on whether the test is performed before or after the body of the loop is evaluated. If the test is p

By the way, if you do clean out your old kernels, don't forget to clean up /lib/modules/ and any outdated module config files in /etc/. Heh. Just noticed that I still had kernel modules going back to kernel 2.4.20. Oh, and you do have to be slightly careful when you select backup kernels. It is possible for the kernel and glibc to get out of sync and adversely affect the system. For example, everything might sudden stop working. It's usually only a problem between major kernel releases (e.g., 2.4 vs. 2.6).

If you want. I have ten kernels in /boot right now just because I'm lazy. Correct. I also keep one really old kernel just in case something snuck in in a previous release and wasn't caught. Not with any stock bootloaders I've used, but it wouldn't surpise me if someone rolled up a script to update the menus automatically. Wild guess? Failsafe is for a failsafe kernel (e.g., the aforementioned really old kernel). nonfb is for a kernel with the normal text console instead of the spiffy new framebuffer console with bells and whistles and occasional breakage. Samba. Never worked for me ex

XP is NT 5.1 as I recall. The currently supported versions are 2k (NT 5), XP (NT 5.1), 2k3 (???), and embedded XP. NT 4 and embedded NT may still be supported, but they're not marketed. On top of that, there are four editions of 2k (Pro, Server, Advanced Server, and Datacenter), six editions of XP (Home, Pro, Media Center, Tablet, 64-bit, and x64), and six editions of 2k3 (Standard, Enterprise, Datacenter, Web, Storage, and Small Business). It's true the versions are very similar and the editions of each version are almost identical, but if there are differences at all they have to treated

Hey, you do have a choice. You can either install SP2, or stop using Windows Update ;-) what's sad is that M$ has always used tactics like this. especiall behind the sceens. Eh, I can't really blame them. The alternative is fork Windows every time a major SP is released. Right now it sounds bad because there's only two choices, but what happens when SP3 and SP4 come along? When you consider that MS maintains four or five versions of Windows, a half-dozen editions of each version, and about five SPs for each edition.... [Edit: Anyone want to confirm that that works out to 2^n versions of

Hey, you do have a choice. You can either install SP2, or stop using Windows Update ;-)

The patches should be fine for Red Hat. If they aren't, you'll know when you try to apply them. But do make sure that you actually need them and that you can make use of them. You may need to rebuild or upgrade you kernel as well.

You might also look at Fluxbox and Openbox. Both are forks of Blackbox. For what I've seen it looks like development of BB has slowed quite a bit, and the other *boxes seem to be picking up the slack.

And if you think that's bad, try building it without a package system to do the heavy lifting. That's been my experience as well. The aesthetics of GNOME are what attract me. Technically speaking, I think KDE is more refined and reliable. On the other hand, I'm using Enlightenment right now. Make of that what you will. Eh, I think it cuts both ways. KDE seems to attract fairly sophisticated users. They certainly target those users, what with the infamous four gazillion option control panels. What, the 'bloody software' thing? Yeah, I rolled it around in my mouth for a while and decide

Far more. Build GNOME and KDE and few times and you come to appreciate the virtues of Not-Invented-Here syndrome. When KDE needs some functionality, they build it themselves and package it up in the regular distribution. On the other hand, GNOME in it's full glory depends on every damn piece of the software in the known universe.

Oh boy. I didn't realize the NF7-s was an nForce2. It probably is a driver problem. The good news is that there are drivers. The bad news is that your choices are a set of binary drivers from NVIDIA or an experimental driver in the kernel. You best bet would be the binary driver. As a bonus, the NVIDIA driver also includes the drivers for the onboard audio. First thing to do is to check if there's a packaged version of the driver out there somewhere. Unfortunately I don't have Red Hat so I don't know where to look. If there isn't a packaged version, or if you just don't feel like looking

Mozilla's pop-up blocker has always been incomplete. In the past it was easy to sneak pop-ups through using JavaScript (e.g., pop-ups triggered by mouseover events), but I believe the current versions of Moz and Firefox have added some basic support for blocking those as well. The next hurdle will be slide-in ads. Not sure how to block those with interfering with browsing. Not that slide-ins should be used anyway. After that, God knows. You can do a lot of annoying stuff with JavaScript.

Assuming you have working NIC, it could be a driver issue. If you can bear with me for a few minutes (er, I guess it would be 'days' based on the last thread :-), try logging into the console or opening up a terminal window and fire off $ lspci That should produce a list of all the PCI devices in your system. Looks for either an Ethernet card or some sort of unidentified device. If lspci doesn't work, try $ less /proc/pci You should get a few pages of garbage describing all the PCI devices in your system. Again, look for anything that could be an Ethernet card. If you're lucky it may act

Neither do I. Well, I mean, I know what it's for, but I don't what all is included with it. Never owned a printer that wasn't made by HP.

You sure? What connects your machine to the router or the external world?

Good. It doesn't see the NIC, but the important thing was that the program was there. Anyway, back to square one. Try to find the device ID for the NIC. And if lsusb doesn't work, forget about it. It's not included in that many distros yet AFAIK. Lexmark may provide a driver. The support page for the X5150 lists a Caldera OpenLinux driver, but it appears that it's actually either a MacOS 9 or OS X driver. Could be the site's broken at the moment (I notice they changed the format recently) and the Linux driver will reappear. It's also possible that it's supported out of Lexmark's Linux d

Eep. Try $ /sbin/ifconfig or $ locate ifconfig Fedora does support networking as far as I know, so it has to be there somewhere. May as well find it now, you're going to need it. As for iwconfig, I didn't really expect it to be installed, but it was worth a shot. Indeed. There's a HOWTO for Red Hat 8, but it hasn't been updated in a while (duh, Red Hat 8) so I didn't want to link to it. The procedure it described involves patching the kernel to add the driver and then rebuilding. Not something you necessarily want to jump into right away. Incidentally, since the subject of using su t

Oh no doubt, but I think it's fascinating how much real knowledge is stored in legends. People would probably have been less surprised by the '80 eruption if the mountain was named Mount One-From-Whom-Smoke-Comes (Yes, you can tell I come from a family of engineers. "Wow, that's a beautiful story. I wonder if it accurately reflects the geophysical history of the region?" True romantics, my kin.)

FWIW, the Bridge of the Gods was real. It was a landslide that blocked the Columbia in the 18th century.

Nooooooo! I swear, whoever invented USB WiFi should be dragged out in a street, shot, and left to the coyotes. The short story is that WiFi is a royal PITA under Linux, and USB WiFi is an imperial PITA. There is a driver available but it requires patching the kernel and you have to know which chipset your particular MA101 uses. There may be a driver included with Fedora, but since I have neither Fedora nor an MA101 nor in fact any sort of WiFi hardware, I'm probably not the best person to be helping. However, I can at least help figure out which driver you need. Boot up Fedora with the MA1

Fedora will be fine. You'll end up formating it in Linux either way in order to get the partition table sorted out and the filesystems installed.

People usually suggest that you install Linux after Windows. That prevents Windows from clobbering the bootloader installed by the Linux installation, and gives the Linux installer a chance to pick up the Windows partitions and register them with the bootloader.

mLife?

Microsoft released a patch two weeks ago. Get thee to Windows Update!