Since i am not seeing anyone else reporting a problem this may very well be a bug on my part with the iso burn, but I have tried burning two discs from the iso that had the correct md5sum and when I boot it goes right past the disc and into my grub menu, as if the disc is not there.
But the disc and it's contents is easily accessible when mounted from within puppy 4.1.2 that I have installed on my laptop.
I checked my bios again, just to be sure, and it is correct, the CD boots before the HDD.
I have booted numerous versions of puppy from the discs with this computer and never run into this problem before.
In the past when I get a bad burn I get it at least trying to boot and then get some sort of kernel panic.
I also tried the disc on my desktop computer that also has puppy 4.1.2 on it (this is on my laptop) and the same thing happed, it went right to my grub menu as if the disc was not there.
Looking in the disc when mounted I have the following files;
boot.msg
help.msg
initrd.gz
logo.16
pup_420.sfs
syslinux.cfg
vmlinuz
and the content of the syslinux.cfg
I will try to download another iso and burn another disc tomorrow, but I have to go to work now.default puppy
display boot.msg
prompt 1
timeout 80
F1 boot.msg
F2 help.msg
label puppy
kernel vmlinuz
append initrd=initrd.gz pmedia=cd
I am fairly new to Puppy and Linux, but I will help in anyway I can by testing and reporting bugs, even if I don't know how to fix them.
Is it possible to have a good md5sum and the burn go fine and still have a bad disc?
I suppose I would think it is, but I just wanted to be sure it was just me and not the iso.
Thanks,
Tom B.