MEPISThis forum is for the discussion of MEPIS Linux.
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.
If you are connected to a network, disconnect before you try to boot from the CD. (Once I did that, I was able to boot into Linux. After I was in MEPIS and went for the Installation option, I reconnected my Etherlink cable and had no problem.)
You did change your BIOS preferences to boot first from CD, right? If not, reboot and use the special key (F8? F2?) on the very first screen after power-on to alter your boot up sequence.
Well, it's probably not your hardware. You meet the minimum specs on that. Also, I know you should be able to boot from the Live CD with W'98, since I did that myself.
It's possible (since we're dealing with Linux!) that the error message is actually related to the problem... So, what file system is running under your W98 installation? Do you have FAT32? Is your disk compressed? How much free space is left?
Btw, is that the very first message you see?
If your file system is relatively standard, and you have sufficient free space (at least 2G for install), you could try running W98 defrag first, then see if it will boot. The only other suggestion I have is, as the MEPIS.org site warns, they were doing all those revisions to the brand-new version in late July, so mirror sites might not have had good, complete versions. Did you check the hash (or byte count) when you did the d/l? Are you sure you have a good CD? (I ended up purchasing mine -- $14.95 includes shipping -- but when I tried to d/l it, the correct version was over 700Mg.)
You may have already done this, if so, don't take offense. When you downloaded the .iso, did you check the md5 checksum before you burned it to a CD. It may be that your download is corrupt or incomplete. I'm not sure what is the best way to check this from Windows 98 (it's easy to do from KDE Konqueror, but I assume you don't already have an existing Linux installation elsewhere). Here is a link to a free download for software to do this in Windows from a command line: http://www.fastsum.com/
You will also need to look on a site with the same download version (version of Linux) that you already downloaded for an md5 filesize. Preferably go to the site you downloaded it from. You then compare that number sequence with the one you get from the checksum software that you ran against your .iso file. If they are the same, then your .iso file is good. If they are not then you should attempt another download.
Thanks for your support, I will need to first, check through the various suggestions that you have made, as some of the terminology/apps are new.
I'll post and let you know how I get on.
I downloaded the trial version of fast sum, I have installed it and performed the checksum on the iso image and the files on the bootable cd itself. Neither of the two results matched with the original checksum value below:
Here are the results:
Bootable cd contents:
I'm not sure if these results from the *bootable cd* need to be aggregated in some way, not sure how this should be done, no feature listed in the fastsum sofware documentation. If anyone has any further ideas or suggestions please forward.
Fearing a bad burn I have begun to get another iso from a diff location