Ixthusdan

Texstar made excellent versions of Mandrake KDE rpms. He developed new KDE versions faster than Mandrake, and they always worked. He decided to start his own distro, what is now PCLinuxOS. He always liked KDE and as far as I know, he still does. He has not been in here in a while, but judging from the distro, he is doing just fine. ;)

You really should configure your software sources via Easy Urpmi at the top of our forum. It means you can handle software installation without any cd/dvd needed. You are missing out on one of the easiest aspects of Linux.

The video driver is what does such things as extended desktops. Install the ATI proprietary driver and you should have additional programs to control what it does. (That is the way Nvidia does it, anyway.)

First, go to this sight and download the file at the bottom of the page. (Get the free version) Then, use the program to check the iso file. Next, go back to where you downloaded and retreive the file that ends in .md5 This file is a text file containing a long number. The number will match your check if the download was good.

My comment was for windows. Windows XP is not usable with 128MB RAM. You're looking at Win98 or earlier for such a low amount of RAM. Despite Linux being more efficient with memory usage, 128MB is not sufficient for Mandriva 2008. I note that your specs indicate you have 196MB RAM, which is still more than 128MB RAM. :P

There is an upgrade option in the Mandriva installation. But beware that an upgrade frequently has odd problems that can be sorted out and corrected. If your 2006 installation is all Mandriva original software, then it should work just fine. Just boot with the Mandriva 2008 dvd and choose upgrade.

The best thing to do is to configure your software sources with Easy Urpmi (Look at the top of the page) and su to root, type "urpmi nvidia". Everything you need will be installed for you.

Added to member sites.

Notice that the first entry says that the driver is installed and that the device is present. This driver will work. But the other three are wrong and interfering with the process. So, to remove the wrong stuff, use "ndiswrapper -e bcmwl5.sys". Repeat this for each of the other bad driver entries. "ndiswrapper -e broadcom-wl-4.80.53.0.tar.tar" "ndiswrapper -e wl_aptsa-3.130.20.0.o" When you are finished with this, you can open Mandriva Control Center and configure the adapter with ndiswrapper; the driver will work.

Please provide us with more details so that we can help you with your problem. I split your post from the other thread because the same symptoms do not mean the same problem. If a computer will not boot, for example, it could be a software init problem, a bios problem, or it may need to be plugged in! Same symptom, different problems. ;)

Go back to Vista? You mean it actually worked? :P Frankly, I have never used fwcutter to get ndiswrapper going. In a console as root, type "ndiswrapper -l" and post what it says.

I do not run any of my client's computers with less that 512MB RAM using windows. 128MB simply is not usable. Will it boot up? Yes. Is it usable? No. I do not think you will find any computer users who say otherwise. KDE is the desktop to use, but I agree that running the current Mandriva with 128MB RAM is not a good idea. There are other Linux distros that would be better suited for what you are trying to do. CD burning must be done as an "image." Many people make the mistake of unpacking the iso file first or simply copying it to a disk. But it is an image file and needs to be burned as such.

Another note: Linux did nothing to your screen, anymore than any other operating system can/would do something to your screen. I suspect that we are dealing with multiple issues including some hardware failures. B) A "driver" is a software layer which a device uses to communicate to your system software layer. A driver from Linux in no way affects a driver from windows. Your XP installation, if you did not touch it, is the same software prior to running a "Live" Linux system. Your Sony laptop had a hardware problem which manifested at this particular time. If you must, blame Sony.

With the DVD, I had a problem with the new task bar in KDE4. I lost all of the functions in it--menu, clock, everything. I could launch new buttons from the "add widgets" button in the corner, but I could not get it to incorporate into the task bar. Launching "kicker" got the old task bar on top of the new one! I ended up deleting my .kde4 file whcih fixed it. But, I do not know what I did to cause the problem and i still do not know how to relaunch the new task bar.

Please use the dvd. I have seen this arise with One. Although it may be a user problem, it must be an unclear prompt with the One installer; otherwise people would not be reporting this glitch.

Looks good. I would like members posting here concerning their likes or dislikes of this repository. That way we can all check it out!

My first look at KDE4 is Mandriva's Spring Alpha. As a gui thing, I really like it. I thought I was waiting for E17 to come about, but KDE might beat them to it. But, I lost the widgets in the "panel," and can't get them back. I can launch new plasma widgets, but the panel is just an empty thing at the bottom of the screen. It is promising, but not working. Anybody know how to restart the panel? I mistakenly tried "kicker," but launching it brought the old panel on top of the new one! :lol: (aside from deleting the hidden directory, of course. That works but what else can be done?)

If the information is correct, your root partition is sda3 and swap is sda4. And so your grub entry should be: title linux 2.6.22.12-1 kernel (hd0,2)/boot/vmlinuz-2.6.22.12-desktop-1mdv BOOT_IMAGE=linux_2.6.22.12-1 root=/dev/sda3 resume=/dev/sda4 splash=silent mem=1024M vga=788 initrd (hd0,2)/boot/initrd-2.6.22.12-desktop-1mdv.img Note that the resume entry. I keep a live distro around (PCLinuxOS) so that I can get into my file system when I mess it up. I use several different distros and the installation process occasionally messes things up.

My Partition Magic 8 damaged a Linux installation by "fixing" it. As a result, I stopped using it when in windows. I had to perform a new installation in order to fix the partition error created by partition magic.

Perchance, did Partition Magic want to "fix" the partitions in order to read them?

If you are uncomfortable with messing around, you can also perform an install, choosing the "upgrade" option rather than full install. Mandriva should find the original installation, identify the partitions, (check that it does) and then zip thru the upgrade without installing anything. Finally, it will install the boot loader.

Do not mount your partitions. 1) boot rescue 2) Choose "reinstall boot loader." Do not choose to mount your partitions first. Do not choose this. Do not mount your partitions. Allow the rescue disk to do what it needs to do. When you are choosing to mount the partitions first, you are choosing to manually do things which interferes with the automatic process. Let the rescue system do it. Do not mount your partitions unless you understand how to manually fix the boot record. 3) Allow it the default install to the MBR. Do not change the installation to the linux boot partition. It should install to the drive's MBR, which contains the current windows boot loader.

I suddenly feel the need to play!

Do not mount the partitions. Just choose "Reinstall boot loader." It should be fine.

Dual processors are not a problem. I have an AMD 64 dual processor unit with no problems. Better dig deeper. Is it already installed or is this a fully operating system?