pmpatrick

As previously noted, pclos doesn't use urpmi. IIRC it uses apt for rpm instead and manges software installation through synaptic, just like on debian based distros. You can still install rpms on pclos since it is not really a debian apt/dpkg system but is using apt for rpm. From the command line you run as root: # rpm -ivh <package name> Unlike urpmi, the above command will not automatically download any package dependencies. If there are unmet dependencies, the package will refuse to install.

If you want a quick debian sid install, you can also take a look at a kanotix fork, sidux: http://sidux.com/index.html It has a current 2.6.20 kernel. I installed this last week and it seems pretty stable so far. Still don't like the debian font rendering but it is getting much better.

Here's a nice forum solely devoted to bash scripting as well: http://www.bashscripts.org/

I echo everything that's been said about going 32 bit. However, a bios crash/lockup can only be a hardware problem. Is this a commercially manufactured box or a home built? Overclocking can cause these types of problem but clearing the cmos should correct that. If that doesn't help, I'd do the following. Check the memory again as previously advised. Check all your connections to the motherboard and make sure the memory is seated properly. A weak or malfuctioning psu can also cause these types of problems, but if this is a home built unit, I would suspect a motherboard intermitently shorting to the case.

I think what Mr. Allison actually said was: So, essentially, he was relating a claim made by unidentified third parties re being threatened by MS. I would be very surprised if this was accurate. If we are talking about large publicly traded companies, these types of customers are not likely to be rolling their own. They would probably be using a vendor like RH/IBM and if threatened by MS they would go back to that vendor. IBM has the largest IT patent portfolio in the world and is not likely to run from a fight with MS; no one in their right mind would ever take IBM on in an IP fight, not even MS. Also, publicly traded companies have reporting requirements and threatened law suits are usually disclosed in their public filings. There may be something to the story, but Mr. Allison's characterization of the purported MS deal doesn't make a lot of sense from a business/legal perspective.

The username and password are "guest" IIRC; at least that's what mandriva has used on prior livecds. I downloaded and tried running metisse under quemu and it didn't work. I got to a login screen but it would just grind away for a long time after an attempted login and eventually dump me back to the login screen. Apparently, the emulated graphics card in qemu doesn't have the horses to run metisse.

You can boot the iso in an emulated qemu environment from within mdv2007 by running: $ qemu -cdrom filename.iso The above assumes you are in the directory with "filename.iso" and you have qemu installed. You can find the qemu rpm in the contrib repo for mdv2007 IIRC. At any rate, I use qemu all the time to check out livecds and see if I want to bother to burn the iso. It comes in very handy. The qemu window will steal the mouse focus as soon as it comes up and to get it back you do Ctrl-Alt and you can use your mouse on your regular desktop while qemu boots up the iso within its window.

What is the basis of this opinion? From the figures, I saw a large increase in expenses and with a company like mandriva, that usually corresponds to employee salaries. I imagine that's their single largest expense. Do you have some inside info as to the current staffing at mandriva? Mandriva has made a lot of acquisitions over the past two years. Unfortunately, for the employees caught up in that situation, what generally follows is cleaning house and getting rid of redundant employees, mostly from the ranks of the acquired companies.

It strikes me as somewhat alarmist. Annual revenue has increased slightly but expenses have increased much faster than revenue. Expect some cost cutting moves by mandriva and a return to the six month release cycle should help boost revenues. I wouldn't rule out an acquisition, but I can't think of anyone that would want to acquire them right off the top of my head. Insolvency within the next year, strikes me as unduly pessimistic prediction.

I had a lot of problems with fw-cutter and broadcom wireless cards on several distros, so much so, I've gone back to ndiswrapper. The main issue I saw on several distros with fw-cutter is that the designation for the wireless card kept shifting from one boot to the next from eth0 to eth1 and back again. Note, I also have a regular nic which kept shifting back and forth with the wireless from eth0 to eth1. So every other boot or so I wound up having to reconfigure everything. You can see if you are having the same trouble by running this in a console as root: # iwconfig If the interface with the "wireless extensions" shifts from eth0 to eth1 on some reboots, you have the same problem.

One further thing on this problem. I and others have noticed a lot of bugs/instability on mdv2007's rpmdrake, the graphical software installation utility in mandriva control center. You may be better off trying the command line urpmi to install the enterprise kernel: # urpmi kernel-enterprise rpmdrake is just a graphical front end for urpmi.

Sometimes when the mirrors are being updated they all suck. I know that the enterprise kernel was recently updated because of a security vulnerability so that might be a problem. Generally, I've found the Netherlands nluug repo to be very good although that will probably change now that I've posted it here. :o :D

Usually, you need to get the "kernel-enterprise" version of the kernel for high memory configurations(over 1GB of ram). There are kernel-enterprise rpms available for mdv2007. Where have you been looking? If you have setup "main" and "contrib" urpmi sources the enterprise kernels should be available. If you are not sure how to do that, post back or check out the "Easy-Urpmi" link at the top of the page.

Not sure what you want to do. The term "ripping" a cd refers to the act of taking an audio cd and extracting the contents to your hard drive as data files, typically wav files. If you already have a data cd, you can just copy the contents to your hard drive without any extra software. If you want to make an iso file of the data cd, you can do that in k3b pretty easy.

Try running this in a console: $ su <enter root password> # less /var/log/messages and: # less /var/log/syslog When using the "less" command you hit the spacebar to page down and the B key to go back a page.

Looks good. From lsmod, you can see ndiswrapper is loading on boot. As it loads it should create a wireless interface and iwconfig shows that's exactly what occurred; wlan0 was created but it is not yet configured. The ndiswrapper -l command shows you have the broadcom windows driver(bcmw15) installed but you alos improperly installed a *.sys file which I expected to see from your prior post. With ndiswrapper, you should only attempt to install *.inf files. You can get rid of bcmwl5.sys in two ways. As root you can run: # ndiswrapper -e bcmwl5.sys Or you can go into /etc/ndiswrapper and delete bcmwl5.sys. You need to be root to delete that file which you can accompolish from the command line with: # rm /etc/ndiswrapper/bcmwl5.sys In either case, bcmwl5.sys will be deleted. Make absolutely sure you are deleting bcmwl5.sys and not bcmwl5, otherwise you will have to reinstall bcmwl5 by using the bcmwl5.inf file again. After doing the above, the error message from ndiswrapper-l should go away. With that done, you can try to configure wlan0 directly from the command line. You need to know the essid for the wireless router you want to hook up with. If the router is using a wep key, you will also have to know that. wpa encryption does not work that well with ndiswrapper and you need a separate application to use it called wpa supplicant. For your initial test, I would recommend changing to wep encryption or no encryption if you are currently using wpa. Open a console, su to root, and run: # iwconfig wlan0 essid <insert essid name> # iwconfig wlan0 key <insert WEP hex key> # dhclient wlan0 That should do it assuming you are using dhcp instead of a static ip.

You probably need to get down to the command line to effectively trouble shoot this. Open a console and run: $ su <enter root password> # lsmod and post the output. Also run: # ndiswrapper -l # iwconfig and post the output of both. The above commands' output will give everyone the necessary info for troubleshooting. FYI "lsmod" lists all modules(aka drivers in windows) currently loaded on your system; "ndiswrapper -l" will list all windows drivers installed on your sytem through ndiswrapper and "iwconfig" will list all wireless devices recognized by your system.

You probably have the beta livecd of PCLOS 2007 which was just recently put on their mirrors and is 695MB; a lot of people are reporting booting problems with it. The current stable livecd, "big daddy" is about 685MB.

According to the linux install instructions: Whereas you installed on a separate partition. Try copying the limp folder to your mandriva /, reconfigure grub and see if that works.

Most 975 and 965 boards I've seen still have one standard PATA port, eg: http://www.newegg.com/Product/Product.asp?...N82E16813127014 Anyway, it's very difficult to tell exactly what's in a mandriva kernel as they are heavily patched and frequently backport features from later kernels. Also, the kernel version may change before final release; they're only at an alpha release now.

I just saw this today from innotek and have downloaded the binary version and installed the product this evening: http://www.virtualbox.org/wiki/Downloads I've installed a guest winxp in VirtualBox on LE2005 and it seems to be working pretty good. Haven't had a chance to thoroughly test it and there do seem to be a few bumps in the road but it's running winxp pretty fast; right now I'm doing updates. It is ram hungry like most virtualization software and no 3d/games AFAIK. Thought I'd pass it along if others would like to try.

I don't think it's possible to have them both running at the same time, at least when using kde. I've run into the identical problem and have to not only close amarok, I have to kill the kde sound server and restart it in kde control center>sound>sound system before audacity will run. The kde arts sound server has been known to be buggy for years. Thankfully, arts is being dumped in kde 4.

It's sticking on loading X; that's what loads after the hal daemon IIRC. Boot into nongraphical, text mode by rebooting and hitting the Esc key as soon as you see the lilo selection screen. That will take you to a command line boot prompt at which you should type: linux 3 Hit the Enter key and you should boot to a command line login. Login as root and rerun your nvidia driver install. The above procedure boots you into run level 3 where X is never loaded so you shouldn't hangup anymore. From there you should be able to reinstall your nvidia driver just like you did before.

That drive can probably be saved by doing a zero fill using seagate's hard drive utilities. For a full explanation see: http://www.seagate.com/ww/v/index.jsp?loca...000dd04090aRCRD After a zero fill, the drive will be in the same condition as when it left the factory. You will then need to partition and format the drive.

Is that 80GB sata drive installed on your new system and if so is windows installed on that sata drive or the 200GB ide drive you refer to in the above quote? If it's installed on the sata drive, you could pull the 200GB ide drive out and swap in your 80GB ide drive and run whatever windows data recovery software you want. If not, you would have to temporarily use the dvd drive ide plug. Since you are not hardware savy, I'd demand that the shop that did this work do all this for you since they buggered up your drive. Once you have the drive temporarily installed on your new system, I'd recommend the following data recovery tools: The best freebie one is PC Inspector: http://www.pcinspector.de/file_recovery/uk/welcome.htm The best for pay one I've found is Ontrack Easy Recovery: http://www.ontrack.com/easyrecoverydatarecovery/ But it's not cheap($200 for the home edition). However, they have a free trial version that will tell you what it can recover if you by it. Ontrack is pretty much the Cadillac of the data recovery software available Another more modestly priced one that I've heard good things about but never used is GetDataBack($80): http://www.runtime.org/buy_now.htm The critical thing is to make sure no data is written to the drive you want to recover data from. The more data that gets written to it, the more problems your likely to have. After you do the data recovery, take the box back to the shop and have them reinstall the 200GB drive for you.