CD Shell User Manual: Troubleshooting

Appendix A: Troubleshooting

Startup Error Codes

If CD Shell encounters a problem when booting up, you should be presented with an error message and a status code. Any status code that begins with the number '8' indicates a clean exit, and typically user error. If the status code begins with any other digit, then CD Shell has crashed while starting up, probably due to a bug.

If you notice strange behavior (eg. slow booting, hanging, etc.) you can step through the startup procedure by holding the Alt key or turning on Scroll-Lock. The status code will change as different startup tasks are completed, allowing you to get an indication of when the problem is occurring.

Below I will list the status codes that are most common, and typical causes and solutions.

Status Code	Problem
`804*****`	This is the most common status code. In this case the CD Shell Loader wasn't able to find the file "/boot/cdsh.bin". Make sure you have the file in the right place and try again. If that still fails, try using another ISO creation app, such as mkisofs.
`808*****`	In this case there was an error reading from the CD or DVD drive. This can happen if you have a dirty/scratched disc, or the disc is ejected while CD Shell is booting.
`810*****`	This status code indicates that CD Shell wasn't able to find any modules to load, and thus cannot execute any commands. The CD Shell binaries that are made available for download on this site have the Extend Module built in, so you will never get this code.

Problems with isolinux and memdisk

If you ever have difficulty using the isolinux or memdisk commands in CD Shell, you should follow the troubleshooting steps below. It is important you follow this procedure, because I can't fix things that don't work in isolinux and memdisk. On the same token, H. Peter Anvin can't be expected to fix things that are wrong with CD Shell.

1. Isolate the cause of the problem.

First, make a disc that boots straight into isolinux (do not have CD Shell on the disc at all). Then check to see if it works correctly. Proceed to step two if it doesn't, step three if it does.

2. If the problem still occurs.

In this situation, there is either something wrong with how you are using isolinux/memdisk, or a problem with isolinux or memdisk itself. You should contact H. Peter Anvin, the author of isolinux and memdisk, here, or request help on his mailing list.

3. If the problem does not occur in step one.

This indicates that there is probably something wrong with CD Shell. Feel free to start a topic about it on the forums or on the mailing list.

- Previous -

- Next -