Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Using VMware v4.0, watever the latest one is anyway, all configured o.k, didn't compile this one though - used the RPM instead. Running Redhat9 on Intel and I am getting this error immediately once I start (or press the little green play button and after the VM-Bios stuff goes past) it. Can't even get to seek my floppy or cdrom.
**VMware Workstation internal monitor error ***
VM attempting to execute in undefined memory
Please report this.... ya de da de da......etc...
Admittingly I had got further in a previous attempt when using boot disks for an XP install but because there are some issues with XP and VMware I thought i would go 2000pro.. but bam! I am stuck eternally with this error and can't get around it. i have stuffed around with some memory settings but to no avail. i am a bit low on avail memory as I have a few other things permanently going. I have 512MB.
Firstly, has anyone seen this error before? It seems that info on it is hard to find.
thanks in advance for any help!!
I'd suggest using the tarball method. It's not as challenging as most source packages since most of the package is pre-compiled, and it only needs to compile several modules to be compatible with your existing kernel (which may be the reason for the problem you're having). The install process consists of running a PERL script and answering a series of questions about your configuration. Usually it's safe to accept the defaults.
Granted this is slightly more difficult than an RPM, but not nearly as hard as trying to track down errors :-)
Thanks for that. unfortunately/forntunately before I read your reply I went in and deleted the image files for that virtual machine and started again. Didn't go through config again. I restarted VM creating a new machine and so far it has gone through fine. <still installing as I type> If I get this message again though I will use your advice so thanks anyway!!
hi gmstaff, can you please elaborate, as to how you deleted the old files again. I am not able to get your point. Did you use the old VM or you deleted the old one and created a fresh customized VM. Because I have the same problem. Sometimes it goes to 2-3 steps ahead. Like once it installed 45% of the windows file, then automatically closed. I am attaching a screenshot of error in a pdf format. I have centOSx86_64. I am installing windows7_x64 as guest.