polemicz

I believe that the mbr has to be on the master drive, i.e. hda. While some distros use Grub as default they all can install Lilo. I happen to use Lilo with my dual boot Mandrive and Debian system. I've always used Lilo and have no reason to change, but many people find Grub superior, and in many ways it is, and if you are starting out Grub may be the best way to go.

I know I made it seem complicated, but try to think of it conceptually. As long as you do not touch your Linux partitions all you can mess up is Windows. As a start while in Linux remove the Windows entry in Lilo using MCC. You will no longer be dual booting and the Windows HD will just be taking up space. You can then plan how to use the space. The nice thing about using the cp command is that you can move all your Linux files to the other HD without affecting your running Linux system. You can mount them and use them if you wish. They simply are mirrors of your Linux system Continue using your current Linux system and feel comfortable with it after the copying. When ready you can move over to the new HD by setting up a dual boot Linux on hdb and "new Linux" on hda. You can go back and forth as you wish in order to feel comfortable. At some point you can remove the hdb system. Just remember to use the hda system you have to edit /etc/fstab. Lastly, there is no reason why you can't have your main system boot off of hdb. Maybe someone has good reasons to have your system on hda, but I don't think it is necessary. Think of it as a way to set up a dual boot Linux system. I currently dual boot: Mandriva on hda and Debian Sid on hdb. The key is don't mess up hdb until you are happy that you got the transition right. Good luck and go for it.

First you can remove the Windows stanza from Lilo from MCC. At that point Linux will know nothing of Windows other than what you have mounted in /etc/fstab. If you have no data on your Windows partition(s) that you need to save you can use MCC -->Mount Points to remove the Windows partition(s). So far all we have done is to change Lilo and possibly removed a partition(s). If you need data on the Windows partition(s) the first question is what file system(s) are you using there. Back up whatever data is there that you need. At this point it would be helpful to know whether you can back up onto a Linuix partition. If all backups are taken care of, if needed, you can safely remove the partitions via MCC and create new ones. Make sure that /etc/fstab is correct. Then create new Linux partitions (give mount points and format, call mount points whatever you wish for now). With new Linux partitions created you are ready to roll. You can copy your Linux partitions to the new ones using the command cp -ax as root, i.e. # cp -ax / /new_root ; cp -ax /usr /new_user etc. This will give you a copy of your Linux partitions on the HD Windows used. You can use Lilo to create a new stanza to these while maintaining your current working Linux. In the new set of partitions you need to fix /etc/fstab, i.e. etc/fstab is /new_root/etc/fstab. There you have to change the places where things are mounted (say from hdb1 to hda1 for / ,i.e a line dev/hda1 / reiserfs ... (or whatever fs you use) where it may have been dev/hdb1). You should be able to boot when fstab is set to mirror Linux systems. When you feel certain that everythig is fine you can do what you wish to the other Linux partitions on the other hard drive and redo Lilo by removing that stanza. I know this seems pretty complicated, and my too much wine with dinner probably worsens it, but it's really straightforward: 1. remove windows partitions and references in Lilo 2. create new linux partitions where windows once lived 3. copy linux system (/, /usr,/home, etc) to new hd 4. edit /etc/fstab on new partitions, set Lilo to boot from new /. 5. boot up to see if you have a mirror of your system.

Go to the mozilla site and download the firefox files (they are called firefox-1.5.tar.gz. Go to the directory where you downloaded it and unpack them: $tar xvf firefox-1.5.tar.gz (can be done as regular user) You will now have a directory /firefox in that directory. You want to move that to /usr/lib as root su password xxxx #mv firefox /usr/lib/firefox next you want a link from /usr/bin to the usr/lib firefox executable #ln -s /usr/lib/firefox/firefox /usr/bin/firefox You should remove your current firefox before doing all this. You will also need to update your KDE menu if you are using KDE (or Gnome if using that). Hope this is clear and it helps.

If it's /home/share (for instance) you set up the share as /home/share in smb.conf. You may not want to share all the subdirectories in /home, hence explicitly /home/share. If you configure samba from swat, as I have usually done, you can go to the shares menu and set up from there, setting who has read and write permissions, etc. Probably easier to do than to manually edit smb.conf.

You should probably update from Mandriva. As has been noted often the Mandriva package 1.0.2 for Firefox (or 1.0.6 in 2006) when patched with updates is the same as 1.0.7.

The simplest way to get to 1.5 is to use the mozilla tars. Mandriva won't be doing updates from their current packages, just security patches (which is all there is from 1.0.2 to 1.0.7). It's a pretty straightforward installation for 1.5.

You can put the directory where you wish. Remembering the file system tree structure you may want a separate shared directory under /. You also may want it under /home or in a particular user's directory. One thing to remember if it falls into the / partition and you re-install it will be lost when you reformat /. I have a separate partition for such things. As for permisssions you may want 666 so that nothing is executable, but it all dpends on what kinds of things you will have in there. Hope this helps.

Welcome to the board. When you set things up and have the directory set to be shared make sure that its permissions allow it to be shared (assuming it's a Linux directory you are wanting to share). Make sure that the users are added to the smbpasswd file (smbpasswd command).

As I recall the nvidia installation readme says you will have to uninstall what you have and then re-install after the kernel change.

I wonder if you have the nvidia card, ati card problem that some folks have come up against (I did with one of my systems). As was suggested try to use the vesa driver (you'l also want to use only 256 colors). What card are you using and did any errors come up during installation, i.e. some packages that wouldn't install)?

Question: did you burn as a data cd or as iso image (not sure how the Nero menus list them)? You can't burn them as data files, but as iso images only.

If your scanner is not on the sane list of supported scanners you are out of luck unless Mercury has Linux drivers. For example, besides having drivers from Sane Epson also has good Linux software: iscan.

Kword 1.4.2 will open and edit PDF files and I believe you can then save them as you wish. 1.4.2 is not in 2006, but is in cooker. I've done some PDF editing with it. I haven't tried to see how the various options for saving work. I've only used it with Debian Sid, so I'm not sure how things are with cooker.

mcc is a link to drakconf, so you should try drakconf from a console as root. If it's not there install it, urpmi drakconf.

I assume that you removed the cd's via MCC or urpmi.removemedia command. You can add them via MCC, but as I said if you have main and contrib repositories set up you don't need them. My basic mode of operation is to install from the cd's and then set up repositories without the cd's. I do have, however, a very fast cable connection, but once you have installed there is generally not much need to install much from a cd.

The commands are urpmi.update -a and urpmi --auto-select. By the way since you have main and contrib repositories set up you ought to remove the CD media, unless you have a very slow connection and want to install some big new package. All, and more, of the packages are in main and contrib.

I think what I and others have done is remove kat via urpmi: urpme kat. It's been a good habit for me to use urpmi instead of rpm, although I do use rpm from time to time.

I installed Firefox-1.5 today (from mozilla tars) and boy is it great. I find it to be much faster than 1.0. Not only back, but pages load noticeably faster.

I have no particular help to offer, sorry, but I wonder if you have searched on the board for help and tried Google. I recall seeing posts about Lexmark printers. Try to search and see if you can find something helpful. Wish I could be of more help, but it does seem that Lexmark is not an easy one for Linux. By the way the big cost in printers isn't the printer, but the carttridges. Good luck.

When you get the boot iso worked out do a clean install instead of upgrade: too much is too different.

One of my common rants: an updated 1.0.6 in 2006 is the same as 1.0.7. All the updates are security patches. Just keep your system current. The only "new" version of Firefox is 1.5 and it is not out yet. When it comes out then it's time to upgrade, otherwise just keep your patches up to date. For what is is worth on my 2006 system my Firefox package is the 1.0.6 Mandriva package which is Firefox 1.0.7 (look at the help menu, about firefox). There have been too too many posts about this with insufficient reading of other posts. Rant over.

The obvious, which you may have checked, is check the permissions of the directory you are trying to write in. I myslf am always running into this and it's usually been a permissions issue.

I started about 4 years ago when I was 60. Finally got a machine I didn't have to share with my kids, dual booted at first I started with Mandrake 8.0 and have continued up until 2006. I've also tried Red Hat, Fedora, Suse. I also have a Debian system (currently Etch) and have used Debian Woody and Sarge. My youngest son, who is 16, has now switched completely over to Linux, using 2006. Like Ix I dislike Microsoft's business practices, which was my main reason to get off Windows, but I also hated the instability of Windows, having started on 98. I must say, however, XP seems to be pretty stable. But oh those viruses, worms, etc.

Scarecrow, thanks for the note about cards. You do have to wonder where Mandriva's heads were when they let out a release that won't work with older cards. It does, however, remind me of when I had to install Windows2000 and then had to download from nvidia's site their drivers. Working with vesa at 256 colors is trying on one's sensibilities.