I used the same media (CD) to install antiX on one of my PCs and the installation is done successfully. I have never ever faced any problem with MD5SUM. Always the MD5SUM of the downloaded iso files are equal to the MD5SUM of that distribution.oldhoghead wrote:I think that Phil is on the right track, when I dl an iso, I check the md5sum and then after burning a cd or dvd I check the md5sum. It will save a lot of grief in the long run. Also, the media that the iso is burned to will impact certain older hardware, I used to use cd-rw, but found that they were very unreliable, they might boot on newer hardware but would fail on my old dell laptop, or if they did work and I manage to do an install, then anomaly's would surface. I now use only quality cd-r or dvd-r. As to the harddrive, you might want to read this post, a short one.
viewtopic.php?f=40&t=2795
The op is a long time debian and antiX user who adheres to the KISS philosophy, which I too endorse.
You could spend days trying to figure out what went wrong, but really, double check the md5 sum's', wipe the drive and then reinstall. If you end up in the same boat, well then just chalk it up to experience and move on. The fact that XP worked fine on that laptop, but ran slow is not surprising. XP was very efficient in running on low ram, contrary to what many may think about XP. But, of course you had to deal with BSOD, virus's, spam, etc. and remember the hardware was designed for windows. I have found that where XP ran but was slow, when I installed antiX it really flew. I know from working with older hardware that it is exasperating at times, but a real joy when I did get it working.
I don't know why you got a debain boot screen, but the fact that you can't do anything there is indicative of a failed install, ie bad burn, etc.
Just my 2c
cheers,
ohh
I know what you mean but if I used the same CD to install antiX successfully on one of my PCs and I used it again to install antiX on the laptop's HDD while it's connected to the same PC where antiX was installed successfully (yes, I unplugged all the internal HDD before I connected the laptop's HDD) which means same CPU, same RAM, same everything except the HDD, the chance of media failure is ZERO in my humble opinion.
You could be right IF and ONLY IF I installed antiX while the HDD of that laptop is inside that laptop which is not what happened in my case.
Allow me to disagree with you and the other user who recommended to check MD5SUM. However, I might re-install again but I'll use this method:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://antix.mepis.org/index.php?title=Installation_Tips"
linktext was:"http://antix.mepis.org/index.php?title= ... ation_Tips"
====================================
I just need to make sure I can do that and the chance is high to get it up and running.
I thought someone could walk me through to fix it and get the GUI instead of CLI.
By the way, I found out that hda1 was not set as bootable. I ran"fdisk -l" and there's no (*) next to hda1. I set it as bootable but that did not change the fact that I'm still getting the same thing.
Before I re-install, I'd like to know:
1- How to check the HDD for error? I tried fschk but it gave me error (bash: command not found).
Is there any way to make sure the HDD is fine and error free?
2- Is there anyway to start the desktop? I mean, another command rather than"startx"? or startx is the only command to start the GUI?
Thank you!