Hi, As a followup to my previous week's post/rant/plea, I thought I'd give what amounts to my resolution of my installation problems, in case they might help others. I hadn't had a chance to tackle this until yesterday.... I will say again that I found this install extremely frustrating and puzzling since so many things that went wrong were rather basic in nature and fall into the category of "problems previously licked by the good folks at SuSE". PROBLEMS To recap, my big problems were (1) an inability to boot from disk after the install and (2) the "invisibility" of all removable storage media save my floppy disk. SOLUTIONS (1) I had to boot from the installer CD and eventually select "boot installed system" AFTER selecting "installation". Having done this, I logged on as root and reinstalled my boot loader. I had to tell it to do so on my hard drive's Master Boot Record -- as opposed to my root partition. Perhaps I had to tell YaST to do this since I have two hard drives, but this had never been an issue before, so it threw me for a loop. (2) My peripherals and removeable drives all appeared to have been detected during the install, but were the installer neither configured them automatically nor prompted me to do so during the installation. In addition to adding my scanner and printer via YaST, I had to do the following. I list each set of actions by device "recovered". (CDROM) As root, (a) in /media, mkdir cdrom; (b) add the following line to /etc/fstab: /dev/cdrom /media/cdrom auto noauto,ro,users,exec,iocharset=utf8 0 0 (PEN DRIVE) As root, (a) in /media, mkdir pen; (b) add to /etc/fstab: /dev/sda1 /media/pen auto noauto,user,sync 0 0 (c) added usb-storage to /etc/sysconfig/kernel; (d) mkinitrd. (ZIP -- Partially successful. See below.) (a) in /media, mkdir zip; (b) added to /etc/fstab: /dev/hdb4 /media/zip auto noauto,user,sync 0 0 (c) added ide-floppy to /etc/sysconfig/kernel; (d) mkinitrd. UNRESOLVED (1) The zip drive is somehow not quite autodetected. It seems that I have to either boot with a zip disk in the drive, probe for it by calling for hardware parameters in YaST with the disk inserted, or edit "hdb4" to "hdb" in /etc/fstab, attempt to mount, edit the "4" back in, then mount successfully. "hdb4" appears in /dev only after some sort of probing of the zip drive -- with disk insterted -- and gets erased upon reboot w/o the disk. This erasure occurs even if I manually add the device. I tried adding a soft link to the device there, too, and THAT disappeared upon reboot. So I have use of my zip drive, but must resort to what feels like "stupid Windows tricks" to use it. How can I get the system to automatically read the partition table of the zip disk once one is inserted? (2) And that brings me to a pair of possibly related questions. I hate automount, but was under the impression that this was the default under SuSE 10.1. I don't see media automount in FVWM, which is my default WM. No complaints there. But then, when my wife (but not I) logs into KDE (Which I also hate.), the pen drive is autodetected and apparently mounted as /media/sda1/ -- but without a corresponding /etc/fstab entry. And I never see the long, automatically-generated, serial-number-based device names I got used to in 9.2 anymore. I am able to mount the pen drive as /dev/sda1/ regardless of which individual drive I put in. I can use my devices, but this seems terribly haphazard. I am almost certainly missing something here. Any insights or illuminating links out there? Thanks in advance. Steve __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com