you enable the top three items with a "y" so that it is all compiled within the kernel to allow booting from your scsi drives.
You do not have to rebuild your initrd image.

Yes, you have achieved success here by enabling the MPT support directly within the kernel image.
A more elegant solution would be to rebuild the initrd with the MPT modules included externally, as is standard Puppy (and Linux) practice. But of course, this involves more work.

Well, I should have said "that way, you will not have to rebuild your initrd". You are right though tempestuous. I know that more items enabled into the kernel image makes it larger, but this is only a couple of items and not too much larger. I guess that adding much more support would make compiling as modules and rebuilding the initrd much more worthwhile. I thought, however, that support for a specific boot device would have to be built in or or the kernel would not be able to find the initrd image if placed on that drive (or the /lib/modules directory for full install).

@ whatupuppy: The message shown in your attached image typically means that puppy cannot find your <PupletName>_<VersionNumber>.sfs file. It will look on a hard drive first but refer to the cd if not there. This file on your cd may be corrupt or unreadable for some reason. Not sure how old your laptop is, but if it is really old, it may have a scsi cdrom drive that most puppy kernels (or initrd's) will not support.

@PupGeek and @Tempestuous thanks for your explanation of what's needed to talk to the HDDs in my DELL server. There are so many DELL and IBM servers which use SCSI and LSI, that I'm kind of surprised that it may have been overlooked here. I ahve a DELL 1600 with P4s server and an IBM P3s rack mount, each with SCSI, but unable to get this LiveCD to see the HDDs.

All SCSI machines that I have encountered over the past 10 years have more that enough RAM that a LiveCD with this support, RAM should not have been a concern. But, ....

Thanks for your help. If this ISO is extended, this might be something included for use on 32bit SCSI Puppy machines.

64bit SCSI Puppies will probably have this when they surface. SCSI seems to have shown up on ONLY 2 types of systems in my past. Customers who run servers, and customers who do drafting-engineering on workstations. In each of these cases, there is so much RAM available, that Adaptec, LSI will not be a problem in the OS, as, I would think that they would have this included and not stripped-down.

Thanks for helping me thus far. I appreciate it, the explanations, and your understanding._________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

Is the development of 4.3.2-SCSI 2.6.30.5 full older modem support finished?

In another thread which was discussing updating Puppy 4.3.1

Dewbie wrote:

I was going to mention 4.3.2 earlier in this thread, but then remembered sending a recent pm to ttuuxxx in which he replied that it was strictly a bugfix version, and that he's no longer supporting it.

responding to this statement

tlchost wrote:

Yet another piece of abandonware. Amazing how we turn our backs upon things that work.

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