OK, long email in an attempt to resolve all questions from both threads:
I'll address your mkisofs questions later in this post, but let's first start with the objective:
Since you purchased a CDROM as opposed to downloading the ISO, you want to verify the integrity of your UBCD 3.3 Full CD. I provided a list of files and their checksums, but you want to make sure that the checksums I gave you are indeed legit (I take no offense)
way you'll be able to accomplish this is to have someone else send you the individual file checksums like I did. If you are trying to duplicate Victor's mastering and get the same ISO checksum it's NEVER
going to happen. Once you are able to master your own ISO (as shown below) you'll see this is true. As far as why
it's true one would have to look into the mkisofs source code; but the fact that it doesn't generate an ISO with the exact checksum is neither a bug nor necessarily bad programming practice.
You want to generate your own ISO because you've customized it, or simply to know that you can.
OK. Some of the issues you've run into probably are due to the fact mkisofs is a port from unix systems so it's syntax isn't always "Windows" consistent. This isn't a problem, just something to be aware of. Let's start with some definitions:
= This is the directory you
are working from. We'll assume it's c:\ubcd
. Your working directory will contain the extracted contents of UBCD 3.3 Full (and perhaps other files that you may or may not want in your ISO, like mkisofs). To make sure you are in the correct directory, get to a command prompt and type the following:
= This is the mkisofs parameter which specifies the path of the directory tree to be copied into the iso9660 filesystem. Since your working directory is the same as your pathspec, the pathspec parameter to mkisofs will be "." (dot, a period, no quotes).
For the sake of simplicity, you'll want to copy mkisofs.exe to c:\ubcd
(it isn't necessary to have mkisofs.exe in your working directory, but if it's not, you would need to understand environment variables, specifically the PATH environment variable).
Now, to make your iso, type the following:
mkisofs -N -J -r -o \ubcd.iso -b boot/loader.bin -no-emul-boot -boot-load-size 4 .
This will create the ubcd.iso file in C:\.
Assuming you don't want mkisofs.exe in your iso, you'll have to type:
mkisofs -N -J -r -m mkisofs.exe -o \ubcd.iso -b boot/loader.bin -no-emul-boot -boot-load-size 4 .
If you want to exclude multiple files you use multiple "-m" options like so:
mkisofs -N -J -r -m mkisofs.exe -m makeubcd.bat -o \ubcd.iso -b boot/loader.bin -no-emul-boot -boot-load-size 4 .
This would also exclude the file makeubcd.bat.
If you want to exclude a bunch of files using the "-exclude-list" option, create a file in c:\ubcd
using notepad and name it excluded.txt
Here are some examples of exclusions you might add to this file:
File names are case sensitive, so ./INSERT would exclude the INSERT directory, but ./insert would not.
At this point you've created the ubcd.iso file several times and noticed a few "messages" from mkisofs.exe, such as "Warning: creating filesystem that does not conform to ISO-9660" and "Using XXX for YYY". This is normal and you can ignore the messages or google around for what these messages are all about. Needless to say they are the same messages Victor gets when he creates the master.
Now, for the checksum issue, create an iso then check it's MD5 checksum with your favorite utility. Then create the iso again and check the checksum. They will differ.
And finally, here is a script you can place anywhere on your computer and it will create your iso. You can play with the batch file to experiment with options.If you are using Notepad to create this batch file make sure you change "Save as type" to "All Files" and save the file as "makeubcd.bat"
REM Changing the drive and directory via the
REM cd command below might fail if you're not
REM running WinXP or 2000.
rem * Change UBCD_DIR to any location you like.
rem * This should contain the extracted contents of the UBCD
rem * We'll assume mkisofs.exe in in C:\ubcd, but you
rem * could put it anywhere on your system provided
rem * you change MKISOFS_UTIL below
rem * The name of the iso will be myubcd.iso and can
rem * be found in C:\ Change UBCD_ISO if you want.
if exist %UBCD_DIR%\ubcd.ico GOTO CHECK2
echo %UBCD_DIR% does not contain the extracted UBCD files
if exist %MKISOFS_UTIL% GOTO DOIT
echo Can't find %MKISOFS_UTIL%
rem Change working directory
rem * Now, make the iso excluding mkisofs and this batch file
rem * in case they are in C:\UBCD. If they are not, no big
rem * deal.
%MKISOFS_UTIL% -o %UBCD_ISO% -N -J -r -m mkisofs.exe -m makeubcd.bat -b boot/loader.bin -no-emul-boot -boot-load-size 4 .
rem * And finally, pause in case you running this
rem * from Explorer, etc
I've run out of time so didn't get a chance to proofread but all should be correct.