Dapper Dan

In my 2 years as a Linux user, I've never re-compiled a kernel nor at this point do I ever see the need to. You may want to look into kernel re-compiling at some point, but it is entirely unnecessary for you to do so at this stage. Slackware is a great distro but I'm not sure I would have chosen it for my first choice. For a new user, Slack can be very frustrating. You may want to consider running a more new user friendly distro like Fedora Core 1 or Mandrake. Once you install your Linux along with XP, you'll be given a choice to install boot loaders Grub or Lilo, making booting between the two effortless, negating the need for a boot floppy. Still, create a boot floppy during the final stages of an install in case the Linux boot loader doesn't get installed correctly. The install will give you the choice to make one. Also, make an XP boot floppy before installing anything new.

I haven't played with my Core 2 much yet. Prelink isn't even showing in my Core 1 sevices, so I would think it *should* be ok to just shut it down. I had to shut mine down to run Half-Life, so I guess this works in all instances. Here's the directions I followed, and never got that error again.

That's great news! Congratulations! I never had any luck with those Linuxant drivers with Conexant Winmodems. I'm glad it's easier with the wireless cards! Whoda thunk it! I just built a "new" experimental box from scratch out of old junk boxes I have. It's got an Asus motherboard, 6 gig drive, 128 ram and a Pentium II 650. Fedora Core 2 installed! I had trouble with it finding the NetGear card, it just wouldn't see it! I changed pci ports and it still wouldn't see it! Finally out of desperation, I found a lower slot that had never been used, knocked out the blank and installed it there, and it finally found it! Two bad pci ports in a row! Whoda thunk that either! Fedora installed the Prism 2 drivers for it, but I switched to the orinoco_pci, and she's working like a charm, 2.6 kernel and all! This is the third time I've been able to piece together a fairly decent Linux box from junk computers I've collected from the Salvation Army store and various other places. What a money saver! Linux really breaths new life into these older boxes!

It could be a corrupted disk which can be caused by many factors, but usually from the writing speed being set to fast. I download and burn a lot of Linux ISOs, and you should never burn an ISO image any faster than x8. What speed did you burn it? Is the surface clean and scratch free?

I'm afraid I wouldn't know how to do that. Sorry.

I presume you are asking how to customize your terminal. Certain terminals allow for customizing and others don't. I'm not aware of options to customize xterm. Rxvt, eterm, konsole, gnome-terminal and my favorite, aterm are cutomizable. For a list of options, open a terminal and enter the command of your favorite terminal followed by: --help [enter] As in: aterm --help look for the options you want and give them a try. Aterm is very versatile in this way. If you have aterm, enter the below command on your box to see how I've got mine set. aterm -tr -bg black -fg white -trsb -sh 50% -tint white -ls -cr purple hope this helps..

Try the install in text and see what happens. What is your ram and video card?

Take it from a long time Linux gamer. I've used both, and Nvidia is THE card to use. It is the least frustrating way to enjoy all Linux gaming and Windows games through Winex3.

I'm using Fedora Core one and 128 so I couldn't tell you. You may be ahead of Linux on this one. Someone will create modules or "drivers" for 256 soon enough though. In the meantine, continue to use the "nv" modules, or you can always get a 128 or less fairly cheaply at Kmart.

I'm posting this from a box running DSL, VNCing to a server machine using Fedora Core 1. Everything is working perfectly, but I simply cannot figure out how to make the VNCserver's default desktop environment change from Gnome to Icewm! I've tried editing a bunch of different files in diffenent locations from suggestions on the net, but it always falls back to Gnome no matter what. I've even editied ~/.vnc/xstartup to run kde, and it still will only run Gnome. Anyone know how I can fix this? Thanks.

What type router?

Originally posted by iamroot: Quote: is it true that winex cannot work with redhat? If it is, then I've been hallucinating when I've been busting some serious ass in Team Fortress Classic. Also, all the Starcraft, Trespasser, Opposing Force, Half-Life, Blue Shift games were my imagination as well. I can't imagine why I thought I was playing those games under winex in Red Hat 9 and Fedora Core one..

Originally posted by jarves: Quote: do i have to uninstall wine before i install winex or i will just leave wine as it is??? Leave, "as is." Quote: my winex is winex-3.3.1-1.i696.rpm when i run it after the installation, will the command to run it be winex3 starcraft.exe??? or just winex?? All winex after "3" are started with winex3

Originally posted by jarves: Quote: do i have to uninstall wine before i install winex or i will just leave wine as it is??? No. The two run independantly of each other.

Originally posted by jarves: Quote: what does the -workdir mean???? That lets winex know which directory to work out of.. Quote: the winex i downloaded is not 3.3.2, but lower version, winex3.3.2 is the new release version, mywinex version is the version before that, does that mean that i have to replace those 3.3.2 with whatever my version is. yes.. Quote: Where will i execute the rpm command, does anywhere will do??? Just follow the steps above. The RPM knows where to install itself.. Quote: how can i change the path so that whenever i will try to execute new binaries from the console, the binary will run??? If you run Windows executables with winex3, and you cd to the directory where the chosen .exe is, and open it using winex3, such as.. winex3 bobswordprocessor.exe ...winex will attempt to run it. Quote: And also where will the files for the wine rpm be installed? /usr/lib Quote: where can i find its executable??? /usr/bin Quote: and also what does the back slash \, in Program\ Files mean??? In Windows, its just "Program Files." In Linux, if you use a space between two words, you must let it know to "read" that as a space. The way you do that is putting a \ before that space to tell it that it's there.

The wireless network is working flawlessly now that I have a new Linksys Wireless-B. I just can't figure out why the Netgear MA311 didn't want to talk to the Wireless-G when it works fine with the Orinoco Gold PCMCIA. By the way, did you know the Wireless-G runs embedded Linux?! http://www.batbox.org/wrt54g.html How'd you ever come out with your wireless card?

I had to reboot the server machine this morning, and to my suprise, everything now works! Must be something that has to be loaded into memory at boot. Anyway, for posterity, here's my ~/.vnc/xstartup that gets IceWM via VNC from a client box.. Code: #!/bin/sh# Red Hat Linux VNC session startup script# exec /etc/X11/xinit/xinitrcxsetroot -solid greyxterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &icewm-session &

A quick Google shows this. Have a look at the first one at Justlinux.

cd to the directory where you downloaded the winex3 rpm, become root, and go: rpm -ivh winex3-3.3.2-1.i386.rpm [enter] It should install without incident. Then put the Starcraft cd into your cdrom and type: mount /mnt/cdrom [enter] cd /mnt/cdrom [enter] ls [enter] Which will show.. autorun.inf directx5 help install.exe isp sc.ico setup.exe smackw32.dll then go: winex3 install.exe [enter] ...which will bring up the Starcraft installer. Follow the directions, and Starcraft will then install into your .transgaming/c_drive/Program\ Files directory. To run, log back in as regular user and go: winex3 -workdir ".transgaming/c_drive/Program\ Files/Starcraft" StarCraft.exe -opengl [enter] You can create a desktop shortcut to it using the above command to run. You can copy and paste the above commands if you use the "konsole" terminal.

I played around with Damn Small 5 when it came out several months back, and for a distro you can fit onto one of those mini cds, I thought it was novel and interesting. 2 nights ago I downloaded Damn Small 7, and have been playing with it ever since. It found and configured all my hardware, including my Netgear MA311, (..yes the one that drove me to madness for two weeks!) easily, and after running wlcardconfig and netcardconfig I was on the Internet in a matter of minutes. Being such a small distro, all the apps are small too, making it very resource friendly. If you have the bandwidth, click "Synaptic" and it will install apt-get, upgrade, then install synaptic, and bring it up with just one click! All the apps fly, and with g-links, you can cruise the Internet at lightening speed. I had Sylpheed downloading my mail in just a few minutes. I've found most cd based distros to be sluggish, but not Damn Small. In fact, I noticed no lag when bringing up apps and running them, even on my old 650 Celeron box. I've tried a lot of the live cd distros, and Damn Small Linux has impressed me more than any of the others. You simply won't believe that such a complete distro could be crammed into such a small space! I've since installed it on one of my work machines and it's running perfectly. The install to HD is very simple, quick, (..about 5 minutes!) and it does a good job of installing and setting up Lilo on the MBR. I first considered the fact that Damn Small creates only an Ext2 file system a drawback, until I realized that journalized file systems are to save you time from shutting down uncleanly. This distro is so small, it can run a complete check after an unclean shutdown about as quickly as it takes larger distros to get up and running using journalized! Damn Small is ideal for older and slower boxes, and is a great way to create your custom made Debian box from scratch. The people behind this project thought their concept through, and I for one am VERY impressed! This live cd at 47 MB is really neat, and you should download and burn a copy for yourself to see just how truly amazing it is!

We have Klaus Knopper to thank for making the the "live cd" distro so popular, which not only is a very useful resue tool, but is also a great way to introduce potential users to Linux and additionally is just downright fun! The advantage with a live cd distro is that you can boot it on a potential Linux box to see if it will find and configure your hardware, and all of them are different. For instance, Morphix worked like a champ having no problems finding and configuring the hardware on our Toshiba laptop, so I installed it to the hard disk and it still works great. Morphix does not however find and configure the hardware on my old 1998 Celeron 650 satisfactorily, but Damn Small Linux did! Consequently, I installed it to hard drive. Live cds are also a very valuable tool to rescue your present Linux install if you've accidentally misconfigured something and cannot get your computer to even boot. Once I mis configured /boot/grub.conf, effectively making my box a boat anchor. I used Morphix to mount the hard drive which enabled me to fix it using vi. If you're a Linux enthusiast, live cd based distros are just downright fun to play with! All of them are so different, and it's fascinating and fun to watch them grow and develop. I predict all distros will soon adopt the Knoppix standard of the live cd, and incorporate it into their present install cds. What a great way to actually know whether or not an operating system is going to work on a computer without the risk of destroying one's present o.s.!

Yes, Redhat and Fedora come with rescue on their installation cds. Just type "rescue" and follow the instructions. To mount your Linux, go: mount /mnt/sysimage [enter] ..and you will then be able to edit using vi.

What distro? Install Openssh server, then set your firewall to restrict all ports except ssh (22).

I used RH 9 and now Fedora. These things happen from time to time and I've never found out why and thought it would take too much time trying to find a solution. Quick solution: Save your Mozilla/Firefox/Galeon/Epiphany/Thunderbird bookmarks, delete their respective configuration files in your home directory, then uninstall and reinstall. Then put your saved bookmarks into the new directory the reinstall created. I put all my plugins in the Mozilla-*.*.* directory in usr/lib for just such an occasion..

I would just start somewhere and give them a try. I would try to start with whichever seems to be the "first."