If I burned an .iso with errors, yet it boots and runs, is it safe to install from it?
Also, how do you install with the GUI?
Also, how do you install with the GUI?
Mandrake 10 questions
- Thread starter bluewall21
- Start date
i dunno, what was the error?
what do you mean 'install with the gui'? you mean the user interaface for the instal isnt graphical or kde/gnome doesnt load automatically on startup??
what do you mean 'install with the gui'? you mean the user interaface for the instal isnt graphical or kde/gnome doesnt load automatically on startup??
DrakX is not coming up (the graphical install), and I don't know, Sonic RecordNow (hey, only thing I had) said "burn process complete, but with errors".(?)
use md5sum program to check the purity of the cdrom image.
I don't know how to do it in windows, I only know that you can check the iso image itself with md5sum.exe program.
Usually from the place you download the iso image you can download a simple text file that contains the md5sum number for that particular iso image.
Md5sum runs a algorythm that creates a number that can be used to compare files. If the first are different, even by a single bit, then the resulting number will be radicly different. It's not perfect but it helps a lot when dealing with copying large files like iso images.
Also in linux you have to know the names of the various harddrives and partitions. Now for IDE devices you have /dev/hd* names.
hda = primary master, hdb = primary slave, hdc = secondary master, hdd = secondary slave. Then the partition themselves are represented by the partition number + the drive name. So /dev/hda3 would be the 3rd partition on the primary master harddrive.
IDE devices represent ide cdroms, except for some distros that use SCSI emulation by default on cdrom drives. Which can be irritating. However by default in most distros you have a simple /dev/cdrom name that is a symbolic link (like a shortcut) to whatever /dev/ file is the cdrom. Also sometimes /dev/dvd for dvd drives.
So in linux you would download the iso image, then download the text file containing the recorded md5sum sum. Then would go md5sum fileimage.iso and then compare that to the contents. If that is correct then you know that the file is downloaded 100%. Then you burn the image to a cdrom, then you go md5sum /dev/cdrom. If that result matches the first 2 numbers then you know you have a 100% pure cdrom burned.
In windows you can use md5sum.exe to check the ISO image, but I don't know how to do it so to check the cdrom after you burned it.
Most distros do that check as part of the installation proccess. So should mandrake. So if it asks if you want to check the cd, let it. If it comes back with a error, then try burning another cdrom.
The #1 reason that I've had bad cdrom burns is because the buffer for the cdrom burner had a underflow.
You see the cdrom is like a record, with a single line of information that is recorded to the disk. If the cdrom runs out of information to burn to the disk, then it just can't stop. It has to keep the cdrom turning so it loses it's spot. It tries to restart in the same spot that it stopped at, however that is unlikely to work and then the cd-r is going to have a error on it.
The solution is to make sure that you have DMA access turned on for the harddrive and the cdrom. If the cdrom and harddrive are on the same ide channel, try taking the cdrom off of that IDE controller and onto the otherone.
If that is not possible then just try burning it at a slow speed.
If you ignore errors then the worst thing that will happen is usually you would be halfway thru copying the install packages to the harddrive during the install proccess it freezes up or exits with a error, then you have to start all over.
I don't know how to do it in windows, I only know that you can check the iso image itself with md5sum.exe program.
Usually from the place you download the iso image you can download a simple text file that contains the md5sum number for that particular iso image.
Md5sum runs a algorythm that creates a number that can be used to compare files. If the first are different, even by a single bit, then the resulting number will be radicly different. It's not perfect but it helps a lot when dealing with copying large files like iso images.
Also in linux you have to know the names of the various harddrives and partitions. Now for IDE devices you have /dev/hd* names.
hda = primary master, hdb = primary slave, hdc = secondary master, hdd = secondary slave. Then the partition themselves are represented by the partition number + the drive name. So /dev/hda3 would be the 3rd partition on the primary master harddrive.
IDE devices represent ide cdroms, except for some distros that use SCSI emulation by default on cdrom drives. Which can be irritating. However by default in most distros you have a simple /dev/cdrom name that is a symbolic link (like a shortcut) to whatever /dev/ file is the cdrom. Also sometimes /dev/dvd for dvd drives.
So in linux you would download the iso image, then download the text file containing the recorded md5sum sum. Then would go md5sum fileimage.iso and then compare that to the contents. If that is correct then you know that the file is downloaded 100%. Then you burn the image to a cdrom, then you go md5sum /dev/cdrom. If that result matches the first 2 numbers then you know you have a 100% pure cdrom burned.
In windows you can use md5sum.exe to check the ISO image, but I don't know how to do it so to check the cdrom after you burned it.
Most distros do that check as part of the installation proccess. So should mandrake. So if it asks if you want to check the cd, let it. If it comes back with a error, then try burning another cdrom.
The #1 reason that I've had bad cdrom burns is because the buffer for the cdrom burner had a underflow.
You see the cdrom is like a record, with a single line of information that is recorded to the disk. If the cdrom runs out of information to burn to the disk, then it just can't stop. It has to keep the cdrom turning so it loses it's spot. It tries to restart in the same spot that it stopped at, however that is unlikely to work and then the cd-r is going to have a error on it.
The solution is to make sure that you have DMA access turned on for the harddrive and the cdrom. If the cdrom and harddrive are on the same ide channel, try taking the cdrom off of that IDE controller and onto the otherone.
If that is not possible then just try burning it at a slow speed.
If you ignore errors then the worst thing that will happen is usually you would be halfway thru copying the install packages to the harddrive during the install proccess it freezes up or exits with a error, then you have to start all over.
md5sum works the same under Windows as it does under *NIX, with the exception that you have to be in the same directory as the file you're gonna check, otherwise you'll get a file not found error.
How can I create a MD5 for isos I have? I have the MD5s for all 4 disks, btu its in .txt format, i'll just create them from the file, and see if they match up.
The md5sum is just the output of the program md5sum.exe when it is run on a particular file.
You can find md5sum.exe online using google pretty easily, in Linux it's usually included and is just simply called md5sum.
To store the resulting output, just copy and paste it into the text file for reference later.
BTW
The main issue with the error being reported by burning program is probably more likely due to something hardware related then a corruption of the iso image.
The iso image is just a file of 1's and 0's, just like they were recorded on the original cdrom they were made from. The burning program has no idea weither or not it should be 100110101101 or 010110101110 so that is what md5sum is generally used for.
Check the DMA access is on for your harddrive and make sure that it is performing as fast as it can, don't do any activity on the computer during the burning proccess (like web surfing or virus scanning) just to make sure that the drive is going to be as fast as it needs to be. Also burn the cdrom at a slow speed, just in case that's the issue.
Hopefully that will get a cdrom burned without any errors being reported.
If that doesn't work there are lots of places online that will mail you a complete set of Mandrake cdroms for less the 8 bucks or so. So that may be a easy way out if it gets to frustrating.
You can find md5sum.exe online using google pretty easily, in Linux it's usually included and is just simply called md5sum.
To store the resulting output, just copy and paste it into the text file for reference later.
BTW
The main issue with the error being reported by burning program is probably more likely due to something hardware related then a corruption of the iso image.
The iso image is just a file of 1's and 0's, just like they were recorded on the original cdrom they were made from. The burning program has no idea weither or not it should be 100110101101 or 010110101110 so that is what md5sum is generally used for.
Check the DMA access is on for your harddrive and make sure that it is performing as fast as it can, don't do any activity on the computer during the burning proccess (like web surfing or virus scanning) just to make sure that the drive is going to be as fast as it needs to be. Also burn the cdrom at a slow speed, just in case that's the issue.
Hopefully that will get a cdrom burned without any errors being reported.
If that doesn't work there are lots of places online that will mail you a complete set of Mandrake cdroms for less the 8 bucks or so. So that may be a easy way out if it gets to frustrating.
.[TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 24K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter