What I was actually running was developer image 1.03 with DS 1.1. Tony had said earlier that he had DS 1.1 working on 12 Mb ram units, so I switched to 1.1 after 2b2 failed. I got pretty much the same results with DS 1.1 that I did with 2b2.
(At the begining of the thread, I was using 2b2, hence the subject).

I guess with Smoker_Man's extra hints, I might try this again this weekend. Currently, I was playing with a debian installation on it (got ftp working, yet to get telnet working).

Now, what are the details of making the partitions writable and read only? When is it absolutely necessary to make the partitions ro again? Does the unit make them ro by itself sometimes? I have been just making them rw / rwm when I need to, and I don't worry much about making them ro again.

Smoker_Man, do you have a 12Mb unit? I'm glad I picked up a deep discount unit, so I can get that extra 4Mb.

Also, is the only "tuning" parameter the ReduceCache option? I saw somewhere else on the board mention of ReserveCache. Anyone know about that? Is the max value of ReduceCache really 48? I've seen some people trying 64.

I'll check the things you mentioned. Your last tip intrigued me. When I try to get my artists playlist up, that's when it bombs. Of course, I don't have anything encompasing my artists playlist, it's right under the empeg root. It didn't look at all like the fids were still coming down, and that I just had to wait for the page. I'll check that though. I thought what I saw on the serial line was a seg fault and hence a program crash, which would abort that html page send. You can look at some of my earlier attachments for what I get through the browser.

Chris