This kind of error happens occasionally. It is often a sign of a hardware failure. Unfortunately it can be hard to pinpoint. Ideally you want to check your log files, but how do you do that if you cannot boot your system? In some cases, it is due to failing ram. To check this you can try running Memtest86+ which is available here. It can also be a sign of software failure. In my case, last fall, I was getting this error due to a faulty boot CD though initially, the burned image was fine and I was able to use the disk for quite some time. You might try burning another copy of Puppy to see if this makes a difference. This is only a start... I am hoping some other members will weigh-in here with some good suggestions.

Monsie_________________My username is pronounced: "mun-see". Derived from my surname, it was my nickname throughout high school.

Hello,
Boot into ram from a live CD etc and fsck the partition..._________________Close the Windows, and open your eyes, to a whole new world
http://puppylinuxstuff.meownplanet.net/puppyluvr/
Puppy Linux Users Group on Facebook
Puppy since 2.15CE...

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum