Image checksum error???
Moderators: Icecube, StopSpazzing
Image checksum error???
Hello people.
I tried to make my own mix of bootcds (as I always do and worked fine), by extracting the image contents (luckily I have no folder conflicts), extracting the boot code and using easyboot to make a new image, and UBCD4 now gives me something like this:
"isolinux: image checksum error, sorry..."
Is there a way to trick the system to boot? (somehow ignore different checksum or something)
Thanks in advance.
Also, how come and UBCD4 is so much smaller than UBCD3.4? Was the overhead so different?
I tried to make my own mix of bootcds (as I always do and worked fine), by extracting the image contents (luckily I have no folder conflicts), extracting the boot code and using easyboot to make a new image, and UBCD4 now gives me something like this:
"isolinux: image checksum error, sorry..."
Is there a way to trick the system to boot? (somehow ignore different checksum or something)
Thanks in advance.
Also, how come and UBCD4 is so much smaller than UBCD3.4? Was the overhead so different?
---
NLS
NLS
If I remember well, Insert has been removed starting from version 4. That may explain the big size difference.
Hammerite Compendium of Precepts, Regimens and Rules of Conduct, Vol. 113 :
A stroke of thy chisel, once made, canst be undone, but a stroke thou dost not make from fear is a worse flaw.
Be not cautious - be correct.
A stroke of thy chisel, once made, canst be undone, but a stroke thou dost not make from fear is a worse flaw.
Be not cautious - be correct.
Re: Image checksum error???
Is that of initial bootup or one of the folders?nls wrote:Hello people.
I tried to make my own mix of bootcds (as I always do and worked fine), by extracting the image contents (luckily I have no folder conflicts), extracting the boot code and using easyboot to make a new image, and UBCD4 now gives me something like this:
"isolinux: image checksum error, sorry..."
Is there a way to trick the system to boot? (somehow ignore different checksum or something)
Thanks in advance.
Also, how come and UBCD4 is so much smaller than UBCD3.4? Was the overhead so different?
What you mean?
I found the total size of the image much smaller. Probably because of INSERT.
Or you mean about the checksum error?
I have a triple boot CD, where all three "original" CD folders are dropped on the new CD (luckily there is no real folder conflict) and extracted the original boot codes (easyboot can use those). It worked fine with UBCD 3.4, but now with 4.0, when I choose to load UBCD 4.0 (the other two of the mix work fine) I get this checksum error...
I don't know what it checks for checksum, but I suspect what it checks has CORRECTLY a different checksum, so I would prefer to disable this check.
I found the total size of the image much smaller. Probably because of INSERT.
Or you mean about the checksum error?
I have a triple boot CD, where all three "original" CD folders are dropped on the new CD (luckily there is no real folder conflict) and extracted the original boot codes (easyboot can use those). It worked fine with UBCD 3.4, but now with 4.0, when I choose to load UBCD 4.0 (the other two of the mix work fine) I get this checksum error...
I don't know what it checks for checksum, but I suspect what it checks has CORRECTLY a different checksum, so I would prefer to disable this check.
---
NLS
NLS
Forget about INSERT. I was referring to when does the checksum error occur. During inital boot or when you go into another menu. I'm not sure I understand what if any thing you did with the orignal version 4 cd.nls wrote:What you mean?
I found the total size of the image much smaller. Probably because of INSERT.
Or you mean about the checksum error?
I have a triple boot CD, where all three "original" CD folders are dropped on the new CD (luckily there is no real folder conflict) and extracted the original boot codes (easyboot can use those). It worked fine with UBCD 3.4, but now with 4.0, when I choose to load UBCD 4.0 (the other two of the mix work fine) I get this checksum error...
I don't know what it checks for checksum, but I suspect what it checks has CORRECTLY a different checksum, so I would prefer to disable this check.
It happens when I choose "UBCD" from my custom menu made by EasyBoot.
I have made a boot CD by mixing 3 other boot CD (MiniPE-XT, Hiren's and UBCD). This method involves extracting the contents of the 3 boot CD, luckily there is no folder conflict, and extracting the boot code from the original 3 boot CD, then "call" this boot code from inside the custom EasyBoot menu.
This worked fine with UBCD 3.4, but not with 4.0.
How does UBCD calculate the checksum? If it looks for the checksum of a specific CD portion it is obvious that this will produce an error (we have a new CD in my case, not the same image).
So I wonder if this "check" can be disabled.
I have made a boot CD by mixing 3 other boot CD (MiniPE-XT, Hiren's and UBCD). This method involves extracting the contents of the 3 boot CD, luckily there is no folder conflict, and extracting the boot code from the original 3 boot CD, then "call" this boot code from inside the custom EasyBoot menu.
This worked fine with UBCD 3.4, but not with 4.0.
How does UBCD calculate the checksum? If it looks for the checksum of a specific CD portion it is obvious that this will produce an error (we have a new CD in my case, not the same image).
So I wonder if this "check" can be disabled.
---
NLS
NLS
-
- Posts: 1368
- Joined: Mon Feb 21, 2005 10:59 pm
- Contact:
Re: Image checksum error???
UBCD is NOT reporting the checksum. IOSLINUX is. If you would havenls wrote:Hello people.
UBCD4 now gives me something like this:
"isolinux: image checksum error, sorry..."
googled "isolinux checksum" you will find many occurances of your
problem. Here is just one case in point:
http://syslinux.zytor.com/archives/2003 ... 01364.html
@nls guess what !? I now have the same error. But only when compiled with CDIMAGE/OSCDIMG. It compiles okay using Ultraiso.nls wrote:Your link concludes that there is NO work around...
I mean come on!
I noticed that the orignal ubcd40.iso was compiled using mkisofs.
Any chance of getting the command line and what options were used?
Maybe we can narrow this down.
EDIT: Wait a minute. I see the options under tools. Sorry.
I'll look into this
I'm confused. Easyboot has nothing to do with ubcd boot disk. BCDEDIT is for booting windows, ubcd is for booting cd's.nls wrote:But I cannot use those tools, you see I have created a special (graphical) boot menu using easyboot, so what you say means I need to create something from scratch plus loose my graphical menu
EasyBoot is a nice and simple editor that allows for merging bootable CDs by allowing you to "call" each of the bootable CDs' (you merged into one) boot code.
The "problem" is that EasyBoot ITSELF makes the new ISO image (so I cannot use a different software to do it since I will loose my custom boot setup).
I merged 3 bootcd and one of them was UBCD. This worked fine up to 3.4. With 4.X I get this error.
Maybe it is the way the new ISO is created (I don't have many options to control it though), maybe something different.
In any case, it seems ISOLINUX is way too hypersensitive.
The "problem" is that EasyBoot ITSELF makes the new ISO image (so I cannot use a different software to do it since I will loose my custom boot setup).
I merged 3 bootcd and one of them was UBCD. This worked fine up to 3.4. With 4.X I get this error.
Maybe it is the way the new ISO is created (I don't have many options to control it though), maybe something different.
In any case, it seems ISOLINUX is way too hypersensitive.
---
NLS
NLS
For one thing you have 2 isolinux inside the cd. One inside EZboot, and another inside ubcd. Maybe that's the conflict.nls wrote:EasyBoot is a nice and simple editor that allows for merging bootable CDs by allowing you to "call" each of the bootable CDs' (you merged into one) boot code.
The "problem" is that EasyBoot ITSELF makes the new ISO image (so I cannot use a different software to do it since I will loose my custom boot setup).
I merged 3 bootcd and one of them was UBCD. This worked fine up to 3.4. With 4.X I get this error.
Maybe it is the way the new ISO is created (I don't have many options to control it though), maybe something different.
In any case, it seems ISOLINUX is way too hypersensitive.