jkerr82508

Uninstalling vbox should leave your vm's intact, but if you want to play it safe, move the /Machines and /VDI directories to a different directory (or even partition) until you've completed the uninstallation. By default they should be in ~/.VirtualBox. My vm's have survived clean installs of 2007.1 and 2008.0 as well as the uninstallation of vbox OSE. (I keep them in a dedicated partition.) Jim

The Mandriva rpm listed on this page: http://www.virtualbox.org/wiki/Downloads non-OS = not Open Source as opposed to vbox OSE (Open Source Edition) which is in the Mandriva repos You must uninstall all vbox rpms already installed on your system before installing this version. (In rpmdrake, search for vbox and virtualbox.) Jim

You need the non-OS version of vbox from their web-site. Then enable USB in the vm's settings and select the device filters to be used. I have tested it and it does work, although I have no need for it and so do not currently have it enabled. Jim Edit: Yes, you can just change the settings of the existing vm.

kcontrol/KDE Components/Session Manager/Start with an empty session Jim

Try: kcontrol/KDE Components/Session Manager - check "Offer shutdown options" Jim

Did you check the md5sum of the iso file and set your burning software to verify the burned disk? Jim

It's a known bug: http://qa.mandriva.com/show_bug.cgi?id=35052 Jim

I've never seen duplicate entries, (other than when they appear at the top of the menu as recent or frequently used) but the place where you can change these items is kcontrol/Desktop/Panels/Menus. Jim

Provided it's just data and not configuration or settings files that you want to "share", then an approach that I (and many others) use is to create a separate "data" partition, for documents, pictures, music etc.. This partition can then be mounted in any linux system running on your machine. It also means that if, for any reason, you need to format your /home partition, your data will be safe. Jim

The live CD requires 256 mb RAM in order to run. I'm surprised that it even booted up on just 128 mb. The Mandriva installer (on the Free CD's) also requires 256 mb, but since you seemed to be able to get the live CD to boot, perhaps it will work for you. Assuming that it does run, then the Mandriva installer will take care of wiping the disk and re-formating. Just select the option to use the entire disk, when it asks. The only way that I've been able to get Mandriva on to a system with just 128mb of RAM was to use the mini CD. There are other linux distro's that are especially designed for older and less powerful equipment: http://www.linuxbasis.com/distributions.html#minimal Jim Edit: On reflection, I may be wrong about the Mandriva installer requiring 256mb of RAM. It's worth trying it to see.

Check the name of the iso file that you downloaded. It should indicate which it is. The 3 CD set consists of three separate iso files which must be downloaded and burned individually. I don't believe that you will get a working system from just one CD. Jim

Glad you got it "sorted". I've kept a note of the working stanza, just in case I ever need to install Windows in the future. Jim

Since Grub is seeing sda and sdb as hd0 and hd1 respectively, would it not see the third hard drive (where win2k resides) as hd2? That would make the mapping entries: map (hd0) (hd2) map (hd2) (hd0) It's a long time since a booted a windows system and so I could be "out to lunch" on this. :) Jim

Report a bug: http://qa.mandriva.com/ Jim

In the Control Center, under Network and Internet, select "Setup a new network interface" and reconfigure your ethernet connection. You should re-boot after doing this to avoid possible problems. Jim

The only driver that will work on mdv 2008 with the 9200 is the xorg ati driver. The fglrx (and other) proprietary drivers are only for cards later than the 9250. Jim

Install gtk-qt-engine There is also gtk-chtheme Jim

I'm pushing at the outer edges of my expertise here, but this is what I got when I ran the rsync command. ./ alsa-driver/ alsa-kernel/ alsa-plugins/ alsa-utils/ hgwebdir.cgi* ../ alsa-firmware/ alsa-lib/ alsa-python/ hg-rsync* .htaccess alsa/ alsa-git/ alsa-oss/ alsa-tools/ hgweb.config .htaccess~ Most of these directories contained numerous files and/or directories, e.g. [alsa-driver]# ls -lt total 184 -rw-r--r-- 1 50100 50100 74123 2007-11-20 18:25 configure.in -rw-r--r-- 1 50100 50100 215 2007-11-14 11:25 kconfig-vers drwxr-xr-x 24 50100 50100 1024 2007-11-12 09:25 pci/ -rw------- 1 50100 50100 2222 2007-10-18 16:25 Makefile.conf.in -rw------- 1 50100 50100 268 2007-10-18 16:25 SUPPORTED_KERNELS -rw-r--r-- 1 50100 50100 9226 2007-10-15 08:55 Makefile drwxr-xr-x 4 50100 50100 1024 2007-09-21 07:25 include/ drwxr-xr-x 11 50100 50100 1024 2007-09-11 21:25 isa/ drwxr-xr-x 2 50100 50100 1024 2007-08-02 14:25 arm/ -rw------- 1 50100 50100 8915 2007-07-27 11:25 Rules.make drwxr-xr-x 2 50100 50100 1024 2007-05-21 12:09 sh/ drwxr-xr-x 7 50100 50100 1024 2007-05-14 18:25 soc/ drwxr-xr-x 4 50100 50100 1024 2007-04-10 15:58 usb/ drwxr-xr-x 7 50100 50100 1024 2007-01-25 13:00 drivers/ drwxr-xr-x 2 50100 50100 1024 2006-12-19 13:00 misc/ drwxr-xr-x 5 50100 50100 1024 2006-12-15 14:00 acore/ -rw------- 1 50100 50100 10159 2006-11-24 13:00 INSTALL drwxr-xr-x 6 50100 50100 1024 2006-09-05 20:00 aoa/ drwxr-xr-x 2 50100 50100 1024 2006-08-09 06:49 ppc/ drwxr-xr-x 4 50100 50100 1024 2006-06-29 22:22 utils/ -rw------- 1 50100 50100 21 2006-06-29 22:22 version.in drwxr-xr-x 4 50100 50100 1024 2006-06-29 22:22 pcmcia/ -rw------- 1 50100 50100 6729 2006-06-29 22:22 snddevices.in drwxr-xr-x 2 50100 50100 1024 2006-06-29 22:22 sparc/ drwxr-xr-x 4 50100 50100 1024 2006-06-29 22:22 support/ drwxr-xr-x 3 50100 50100 1024 2006-06-29 22:22 synth/ drwxr-xr-x 2 50100 50100 1024 2006-06-29 22:22 test/ drwxr-xr-x 3 50100 50100 1024 2006-06-29 22:22 doc/ drwxr-xr-x 2 50100 50100 1024 2006-06-29 22:22 hal2/ -rwx------ 1 50100 50100 1238 2006-06-29 22:22 hgcompile* drwxr-xr-x 4 50100 50100 1024 2006-06-29 22:22 i2c/ -rw------- 1 50100 50100 5585 2006-06-29 22:22 install-sh drwxr-xr-x 2 50100 50100 1024 2006-06-29 22:22 mips/ drwxr-xr-x 2 50100 50100 1024 2006-06-29 22:22 modules/ drwxr-xr-x 2 50100 50100 1024 2006-06-29 22:22 parisc/ -rw------- 1 50100 50100 4753 2006-06-29 22:22 CARDS-STATUS -rw------- 1 50100 50100 18009 2006-06-29 22:22 COPYING -rwx------ 1 50100 50100 1239 2006-06-29 22:22 cvscompile* -rw------- 1 50100 50100 3059 2006-06-29 22:22 FAQ -rw------- 1 50100 50100 1171 2006-06-29 22:22 README -rw------- 1 50100 50100 1603 2006-06-29 22:22 Rules.make1 -rw------- 1 50100 50100 1188 2006-06-29 22:22 TODO -rw------- 1 50100 50100 219 2006-06-29 22:22 WARNING Some of this may help you to identify the directory that you want. Sometimes one version of linux just doesn't work well with a particular combination of hardware. Although Mandriva is my preferred distro, and it has always worked for me, you may find that another distro works better with your hardware. Some of them produce live CD's which give you a chance to test before installing. (K)ubuntu, Fedora and Suse might be worth trying. Jim

Try using the full path to the target directory. This worked for me. (I used a temporary directory in my ~, since I don't really want this stuff.) Jim Edit: Sorry, I posted this before I read your post about the problems with the proxy. ftp access might be available, if you can identify the directory that contains the files that you want. Jim

This thread may give bookie and Peter a couple of things to try: http://groups.google.co.uk/group/alt.os.li...21a840d93eea217 Jim

As root: drakx11 Jim

From man urpmi; --noclean Do not remove any package from the cache in directory /var/cache/urpmi/rpms. You may be able to make this permanent, see man urpmi.cfg Jim

If you were not asked to set-up a user then it's possible that the installation did not complete properly. This can happen if you did not allow enough space on your hard drive for Mandriva. At least 4G is required to install Mandriva ONE. Jim

You don't say what virtualisation software you're using. Such software doesn't usually use your actual devices, but virtual devices. Run XFdrake and configure the virtual devices. Jim

There has been extensive discussion on the cooker mailing list about this for about a week. Take a look at the archive. http://archives.mandrivalinux.com/ It's useful to subscribe to the cooker mailing list when you're running cooker. http://wiki.mandriva.com/en/Development/Mailinglists JIm