Daveleh

Thanks v much for replying I will bear your advice in mind and let you know how I get on.

Same here except that I use a Fuji Finepix 401 and a RIO reader. The camera is not recognised. But with the Reader I simply plug the usb extension cable into a spare usb port, insert a card (with piccies) into the Reader, connect it to the cable, the yellow led flashes and an icon for sda1 mounted at /mnt/memory_card appears on my desktop. Click on the icon, Konq opens and displays the folders/piccies. Nice and simple. Reader cost £20.00 :mandrake:

I thought those were just for decoration :mystismiles:

This is just a quick request for confirmation of a process. I have recently purchased a 64Mb Geforce2 MX400 graphics card and am going to install it this weekend. I just wanted to run through the process I am going to follow in order to make sure that I haven't got anything drastically wrong. I plan to: 1. Install the card and plug my monitor into it 2. Turn on the PC and check that it is recognised and installed correctly and works 3. download and install the Nvidia drivers as per the numerous topics that I have read in these forums and check that they work correctly. That should all work Ok shouldn't it ? :mandrake:

Thanks :) :mandrake:

[quote="Linz fdisk only lists my harddrive partitions... :-( I seem to recall a reading somewhere that there may be problems accessing multi format readers. Not sure if that was valid for 9.0 or 9.1 though. Sorry I can't be of more help.

I have truoble occassionally with my single format S/M card reader. After 5 or 6 logins the icon for sda1 on /mnt/memory_card disappears from the desktop and the entry for sda1 is removed from /etc/fstab. Whenever this happens I simply insert a spare card into the reader, open a console and type: fdisk -l (thats L not 1). This then lists all the HDs I have, including the card, re-displays the icon for sda1 and re-inserts the relevant entry into /etc/fstab. You might want to try doing the same with a card inserted in your reader. If anyone can explain why this happens and how to stop it I would be most interested.

PMFBI' date=' but you're wrong. I have done this several times. The Windows installation expects partitioning to have been done beforehand and uses what it finds. Just reinstall Windows (I assume 9x) as normal - it will only see the FAT32 partitions. HTH Neil Haughton[/quote'] Well, well, I didn't know that :) Thanks for the info I will bear that in mind for the future.

Hmm, that's a problem. If you use MondoRescue it will take one or two CDRs. I think you can back up to floppy (or should I say floppy mountain :D ) with MOndo but I have always used CDRWs myself. Sorry I can't be of any further help :?

I think you'll find that when you come to re install Windows it will see and grab the whole drive and not just the partition it was originally on. That's what you get with an arrogant OS. Correct me if I'm wrong people please. One option that you could try is to use MondoRescue and make a complete backup of your Linux partitions, re install Windows, resize it, and then restore your Linux partitions from Mondo. Just a thought.

That comments ruled out my suggestion then which was to put another OS to good use and use them as door stops. :-)

BTW, its probably better to start your own thread even if your problem is related to someone else's problem, call it by ear :) Oops, sorry

I had a similar problem when I installed 9.1. :( I have two HDs, hda is a 40 Gb drive and was split into the following partitions: Windows, /, /boot, /usr and /home and hdb is a 13Gb drive and was mounted whole as /data which contained all the RPMs and tar files that I had downloaded and installed whilst using 9.0. Before I installed 9.1 I wanted to backup information so instead of copying the files to Cd, as was my oriignal plan, I copied the contents of /usr /opt and /home into a folder on /data called backup. When I installed 9.1 I wanted to get rid of the Windows partition so I selected the 'use entire drive' option but was suprised when I was only offered hda. I went along with this anyway and recreated the partitions above, however when I finally booted into 9.1 hdb was nowhere to be found, not even in MCC under mount points. So I tried the install again, this time choosing the 'use existing partitions' option and this time both hda and hdb were identified. I chose hda and selected all the partitions for reformatting and then carried on with the install. Now once it had finished I could see both drives as normal, unfortunately when I went to copy back the files from /data/backup not only could I not find /data/backup but I couldn.t find any data on the drive at all. As far as I could tell the entire drive was empty. At this point I could have reinstalled 9.0 from a mondo backup I had made prior to installing 9.1 but I decided to just start reinstalling software as I needed it instead. Anyone else come across anything like this?

Maybe, but who has the worst current licence practices MS or SCO ? And if they were to apply that to Unix what effect would that have on Linux distributors ?

Just read this on Yahoo news! http://uk.news.yahoo.com/030519/36/e0c0l.html

Have you tried the download from Sun's site? This is the one that I have installed. It's located here: http://java.sun.com/j2se/1.4.1/download.html

If you don't have the space to dual boot consider using Mondo Rescue, available from http://www.microwerks.net/~hugo . Back up your drive onto cdrs or cdrws and then try 9.1. If you have problems with it just restore from Mondo rescue and you'll be back to normal with 8.1 HTH

Yes, thanks very much, I should have listened to your advice from the start. :roll:

Ok, finally got A card reader working. I'd read in one of the posts, not sure if it was on this list or another one that I subscribe to, that in order to use multi card readers a kernel option needs to be activated. This is a bit beyond me at the moment so instead I purchased a single card reader. This is the Zio, as mentioned by mtwiederman in a post quite a while ago I seem to remember. This worked first time and works perfectly each time. I connected it to the usb port, booted up and inserted a card with photos on. Then I opened a terminal (console) and typed 'fdisk -l /dev/sda' and lo and behold I got a report giving sda1, never got anything like this before. So I then typed 'mount /dev/sda1 /mnt/camera' followed by 'cd /mnt/camera' followed by 'ls' and the folder on the card called dcim appeared. I then entered 'cd dcim' which displayed a folder called fuji_100 inside which were all the photos. Now I find that I have an icon on the desktop called something like 'mnt_memory_card' (i'm not on my linux machine at the mo) and if I enter the command 'mount /dev/sda1' I can click on it and view the contents. So if anyone else is having trouble I would recommend the Zio. It costs approx £25.00 from Dabs.com and was here within three days. BTW I 'm using ML9.0

Thanks for that

Hi, can anyone tell me whether or not those front panel media card readers, you know ... the ones with the multiple card slots that fit into a bay in the case, work with Linux and more specifically either ML9.0 or ML9.1

Thanks for all your replies. I'll let the board know how I get on.

I am eagerly awaiting ML9.1 in order to try to get my digital camera working under Linux. It's a Fuji Finepix 401 connected via USB. I have tried everything I can think of to get it to work with ML9.0 with no luck. My question is, when I install 9.1 which is the best option to go for: 1. Install with the camera cradle connected, the camera in place with a picture card installed and the camera switched on, 2. Install with the camera cradle connected, the camera in place with a picture card installed and the camera switched off then turn the camera on after successfully booting. 3. Install with the camera cradle connected but no camera, then connect the camera after successfully booting. 4. Install without the camera cradle connected and connect it after successfully booting. Any thoughts? My first choice would be 1. but when I try this with 9.0 I get loads of error messages as it is detected and the boot process freezes.