Wow!  I finally hit the nail head instead of my thumb?

Have a good night sleep, you can think this over tomorrow.  But before I eat supper, I too wonder what changed.  I did some updates from erincanka's smart repo, they were:
Operation #36: install
Date: 2012-08-08 14:50
    * xulrunner is upgraded from 2.0.1-52-p11-x86_64 to 14.0.1-54-p11-x86_64.
    * valgrind 3.6.1-18-p11-x86_64 is installed.
    * firefox is upgraded from 12.0-171-p11-x86_64 to 14.0.1-172-p11-x86_64.
Operation #35: install
Date: 2012-08-08 14:40
    * nss is upgraded from 3.13.3-46-p11-x86_64 to 3.13.5-47-p11-x86_64.
Operation #34: install
Date: 2012-08-08 14:39
    * nspr is upgraded from 4.9-33-p11-x86_64 to 4.9.2-34-p11-x86_64.

When I get software from pardususer or pardus stable on my Anka test os, I turn off erincanka and anka test repos so they don't get confused and get that error 'The component system.base cannot be found.' 

Also, since I use dial up, I have had to change the following long ago to get nameservers in my resolv.conf file due to how ip-up and ip-down are written where ip-up looks defaultingly for resolv.conf file in /etc/ppp.  So, I created resolv.conf text file with the 3 nameservers under /etc/ppp.  I also edited /etc/ppp/options by adding 'usepeeerdns'.  Don't know if this is what makes the difference for me.   Odd as I am usually the one that has dns problems and not you dsl and wifi folks.  I've included my service list. 
And, in krunner under the wrench icon, I have unticked Contacts, Calendar Events, Kopete Contacts, and Nepomuk Desktop Search Runner.

Do I see a clue in dschzz's output,  name resolution?  My resolv.conf:
nameserver 193.140.100.210
nameserver 193.140.100.215
nameserver 193.140.100.220

I am good here in the US.  I tested by turning off anka test and erincanka 64 bit repos and turning on pardus stable and pardususer 64 bit repos, then installed 'keepnote' from pardususer to make sure and yes, it installed.  That error looks very familiar, like the error I would get when doing package installs from the anka repo.  I had to continually repeat the command line pisi up or pisi it to get it to complete fetching. 


I cancelled the updates as I have the Firefox 14.0.1 from erincanka repo as of two days ago.  I can also use Firefox to go to the repo links without any server connect problems (went to the i686 one, too). 

Try again, is only thing I can suggest, or maybe look at network connection timeout settings(?)

Oops. 
It installs correctly and now have erincanka repo added to my repo list;

Thank you.
I get the following error when trying to install the first package, nspr, and cannot install the following packages as they depend on nspr build. 

And that is a good thing, as our differences make us interesting.

And, I tried it again, and this time I waited after the services were started (dbus, services,tty and ended at login as root) and after several minutes the Yali installer began.  The only part I didn't know what to do concerned installation.  I stopped the process as I don't know if I should install a bootloader for a virtual machine, or what partition to use.  It is showing Disk 1 (sda) 15GB, but that is where I have XP installed.  So I am unsure how to continue.  Virutal=fake, so if I let it do what it suggests, maybe it is okay.  Probably not.    Time to call it a day and get ready to watch 'Inspector Lewis" on PBS.  I've got some learning to do about this part of virtualisation.  (how do you like that for a Yankee.  I spelt virtualisation without a z and 'spelt' instead of 'spelled'  )

Sorry, I don't always understand what you are saying.   You Canadians speak another mind set. 
Remember, I am dense of the thinking process.  But...I thought I'd try it with a 32 bit os, so put Pardus 2009.2 installation disc in, and it started the boot up progress bar, and I expected it either not continue or to bring me to the install Yali process, but instead it started up services, tty, etc root log in, which I entered 'startx' and brought me to a simple session manager.  I guess I am getting there.  Maybe I should have said, 'startkdm'.  So, it does seem to work on my system with a 32 bit os.  I assumed it wouldn't work on 32 bit os, no virtual of any kind.

Hi Anglo,
Thanks as I didn't know about that one.  I just gave it a try after trying to figure the qtemu GUI out, and it wouldn't do anything when I clicked 'start'. Then I found the Pardus Wiki on virtualisation for qemu and followed the command line instructions.  Behold, this time it started with a another window popping up starting the install process of Pardus,


but after getting so far in the starting kernel progress bar, I get the same error.

The error being, 'this kernel requires an x86_64 cpu but only detected an i686 cpu, unable to boot. '

But now I'm getting the hang of using the different virtual machine softwares available.  I asked my husband to try virtualbox on his lap top and it does work on his dual processor machine.  So maybe when I can get my hands on his laptop, I can play with it, or when he lets me have it if he ever upgrades.  That will be a long time in coming.   
Lisa Marie

Hi evowinds,

I completely overlooked the previous answers from you, atolboo and jasperoduus and see you mentioned the BIOS and motherboard capabilities.  Yep, both my socket 939 cpu and a8ne motherboard BIOS don't support virtualisation, so that forum where someone said  that these don't have to support virtualisation was wrong.   
Lisa Marie

Thank you evowinds for the tip!

I just got back from a week's visit to my mother and father-in-law.  I just installed Pardus on a separate partition on my large hard drive and will install Anka atop it.  But I would like to try the virtual machine thing again as that was "neato".  I was at some forum where virtualisation was discussed and there was mention that VirtualBox didn't rely on one's cpu or BIOS virtual capabilities.  We'll see.  Maybe someday I can get a used laptop newer than my desktop and try it on that.  
Lisa Marie ...as usual, spelling and/or grammar mistakes

Finally got done what I wanted to achieve but came to a 'sticking point', as the expression goes.  It is a neat idea, though and now I understand better how it works. 
I did a fresh reinstall of Pardus 2011.2 for 64-bit, and installed virtualbox by oracle.  Then started the program after adding my user to 'virt' group.  I was guessing at the next numbers when going through the virtualbox wizard.  I have 4 G of ram and gave the virt. machine 720mb of ram.  Then created a 20 G virtual disk space and had the .vdi in my home folder.  I made sure it was 'released' in virtual machine manager before I proceeded to start. Had the Pardus 2011.2 installation disc in my second dvd burner and wow,  there was the installation of Pardus , but as soon as it got to the kernel progress bar starting up, it stopped and I got the message that the 'kernel requires a x86_64 cpu but only detected an _i686 cpu...'.  My motherboard is a bit old and looks like my cpu doesn't allow virtualization (Asus a8ne withlatest BIOS update, AMD athlon 64 fx57).  Anyway, just wanted to chime in that I can't wait to try it again, but will have to wait until my tool is newer.  I liked the wizard, as it made it easy to install, which is why I put off trying it for so long, as I thought it would be complicated.
Lisa Marie

Yes, I wouldn't expect it to be otherwise since it is developed by Turkish folks.  Didn't Pardus start out this way and eventually other languages were added?  Start small then if it is a good product, make it international.  You got to have the product first. 

I'm still in waiting mode for Pardus as I still use it 90% of the time, with XP coming in second.  I use Mandriva Rosa, but there are some things I'm trying to find out what is wrong in that distro, and no offense to it, but the screen flickers at bootsplash and also when desktop opens.  It doesn't do that in Pardus.  Plus, I can still install software from the Pardus repos.  When I used the former Hymera and they closed shop, they also closed their servers.   Also, the pardususer.de depot is very valuable to me.  I very much appreciate that they have created packages for us, packages that I can't find created for Mandriva. 

Thanks again, atolboo.  Thanks Murat.  I see why it is of use for you as you can use nspluginwrapper Citrix - windows tools.  

My current set up on my desktop is two hard drives, first one has xp pro and second one has Pardus Anka and Mandriva Rosa with a swap in the middle. What I would like to do is reinstall Pardus 2011 64 bit, get all updates, and somehow install Anka OS as the virtual one since it is in its testing phase and some programs in Anka don't work for me (digikam, for one, plus that microcode error).  Forgive me for being ignorant about virtual desktop, but I see how useful it can be.  I look forward to learning how to use it.  I obviously do not understand it. Again, thank you for sharing how you have yours setup.
Lisa Marie

Thanks, atolboo.  Onward to the pardus wiki I go.

I know this is old thread, but I would like to learn about how to create a virtual desktop.  The one page I read was at ubuntu site and it said it is preferred to create a virtual desktop in windows os (if it is installed on one's computer) and then run Linux in it.  This would would require to use vmware.  Free vmware is for 32 bit and vmware for 64 bit costs money.  Is this how you folks running a virtual desktop have your systems set up (if Windows is installed, too)?