tyga

I didn't vote because there wasn't an option that said, I fear change, I don't like the new page. And that penguin would scare little children. Actually, it seems too narrow, why are you conserving so much space at the sides? BTW, I think a conservative approach to web layout is always a good idea, I personally prefer plain, simple and easy to navigate web pages.

I can confirm that this works very well with Ubuntu 5.10, thanks for the tip. Here is the original menu.list generated on install: title Other operating systems: root # This entry automatically added by the Debian installer for a non-linux OS # on /dev/sda1 title Microsoft Windows XP Professional root (hd2,0) savedefault makeactive map (hd0) (hd2) map (hd2) (hd0) chainloader +1 And here is the edited list: title Other operating systems: root # This entry automatically added by the Debian installer for a non-linux OS # on /dev/sda1 title Microsoft Windows XP Professional rootnoverify (hd1,0) savedefault makeactive map (hd0) (hd1) map (hd1) (hd0) chainloader (hd1)+1

Silly me, I forgot to check the date of the thread. How come it showed up in the latest threads then? Thats why I replied,because I saw it in the latest threads. Also, I did the same thing as normael above, the first time I burnt an ISO to a disk. Not that uncommon when people first attempt to burn their own ISO's I guess.

is this mandrake 10.1 you are trying to install? I remember, for some odd reason, the installer is on the 2nd iso. you start the intall with disk 2 and then put disk 1 in when prompted. I think thats right, if memory serves me correctly, or i may just be going senile.

Yes I noticed the date of the virus as well danleff, however I thought it probably would still be propigating in the wild some place, you never now. I don't use apache or openssl, o i have no idea if it still a problem, i guess it wouldn't be though. Justbill, f-prot doesnt have a GUI. If you installed it then it should be running in the background. You update the virus signature s via command prompt by typing in something like this, as root. /usr/local/f-prot/tools/check-updates.pl heres a link for help http://www.f-prot.com/support/helpfiles/unix/workstation/man_updt.html

As far as I am aware, the virus would need root privialges in order to do anything, which is not likely unless you are silly enough to login as root. I have linux and windows systems networked at my home so I use a virus scanner on my linux box, just for peace of mind. I use the f-prot antivirus for linux, it is free for home use.

At the moment there really isn't any benefit. The only benefit is that an 64 bit system will be generally faster than an 32 bit system simply because a 64 bit system is newer than a 32 bit system and the only other benefit is that a 64 bit sytem is ready to take advantage of any new 64 bit software. There is no real observable difference between a 64 bit and a 32 bit system.

I recomend Nvidia. Not because I am particularly partial to Nvidia but because Nvidia make fairly decent linux drivers in comparison to ATI. ATI drivers leave a lot to be desired.

Sorry danleff, I was just generalising rather than actually refering to what you said or even to this particular thread. I'll try to be more specific next time. I would be glad to help in anyway that I can.

I'm not really sure why but I frequently see people advise that Windows must be on the primary master HDD. Although I agree that on a single HDD it is best to have Windows on the 1st partition and Linux after Windows, it is my opinion that in a Multi HDD setup it is best to have Linux on the Primary Master HDD and Windows on a Secodary or slave drive. My reason is this. If you install Windows first on a HDD, then place that HDD as a slave drive, then install linux on the primary master drive, the linux boot loader will recognize the Windows drive and install it in the boot loader, Lilo for example. This leaves the Windows boot loader untouched on the slave HDD making it easily and usefully possible for an easy windows boot via a simple bios boot sequence swap, in the event that your Linux install is hosed, which often does happen. However, if you install windows as the master HDD and then install linux as the slave, the boot loader will over write the windows boot loader. I know it is a fairly simple task to repair the MFT but I think it is much easier just to put windows on the slave HDD. I have done this with all my Linux windows dual boot setups without any issues.

When I first started using linux I made the mistake of putting linux on the primary partition. Then thinking that all things are equal, I put windows on the primary hardrive (hda or C) and linux on the slave drive (hdb or D, which doesn't show up in windows due to Microsofts refusal to make linux compatible with its own software) It seemed logical tp put the OS's in this order because thats the order i had the OS's on a single partitioned HDD. Being a linux noob at the time, I managed to destroy the linux install thus overwriting the MBR on the winxp drive, so now I had a useless linux drive and a winxp drive that wouldn't boot. My solution to this problem, after much head scratching, was to reinsatall, make the primary drive Linux, thus having Lilo or grub as the boot device and windows xp as the slave drive. In this way, if the linux boot loader fails for whatever reason, the windows boot loader is still left intact and fully functional. In the event that you may destroy your linux boot loader, it is an easy task with most newer Motherboards to simply change the boot sequence via the bios settings, no need to swap the ide cables around. Iv'e done it this way for a long time and have had no hastles ever since.