Darjeeling: Yes, the Puppy & TinyCore CDs (all made with he same process) boot successfully to OS in the same hardware configuration. The MD5 is the same. The boot procedure doesn't hang - it just ignores the SliTaz CD and goes on to load the C drive OS.
totoetsasoeur: Yes, I have used the identical method for all 6 CDs - one each for Puppy Slacko, Puppy Wary, and TinyCore 4, plus 3 Slitaz CDs to ensure there wasn't a physical media problem. The MD5 checksum matches. Do you mean a 3rd PC? It already doesn't work on the 2 detailed above?
Somewhat Reticent: OK, I downloaded the Slitaz iso from the link given above using Chrome on a 64-bit Windows Home ACER laptop. I used Fastsum to check the MD5 (it matched). I used a utility program called NTI Media Maker to burn the file to a CD. I used NTI's "Data Disk" option to perform the burn. (this is the identical procedure followed for the -working- 2 Puppy & 1 TinyCore CDs) The CD's are manufactured by TDK.
On both the ACER and the MSI I have tried both allowing the default bootloader process (which is set to CD, USB, HArddrive on both machines) to run, as well as intervening at the "Press F2 key now for Boot options" phase to ensure the CD drive was selected. During the default procedure, I can hear the CD drive fire up, before the boot process wanders off to the hard drive to start Windows. This is true for both the CD drives used, on both the machines.
The ACER machine has Windows 7 Home 64-bit on a non-partitioned hard drive. The MSI has 32-bit Windows 8 Developer and Customer Preview on a partitioned hard drive in the default location as per the W8 install.
I have previously booted other OS (Chromium, TinyCore 2) from USB on both machines.
I don't use fingerprint protection.
Links:
Puppy Wary ISO ftp://distro.ibiblio.org/quirky/wary-5.3/
Puppy Slacko ISO ftp://distro.ibiblio.org/puppylinux/puppy-5.3.3/
Tiny Core ISO http://distro.ibiblio.org/tinycorelinux/4.x/x86/release/CorePlus-current.iso