@clm1919 :-
Yah, that kernel will do just fine. To 'translate' ozsouth's kernel-naming 'code':-
For '6.6.25-64oz-aoum-lolat':-
'a' means it will work with Puppy's traditional AUFS file-system
'o' means it will work with the overlayfs file-system that is slowly being adopted. Bookwormpup64 needs this (I'm not 100% certain about this statement, so am willing to be corrected here)
'um' means it's been built to work with the recently-adopted 'usrmerge' construction that all Linux mainstream distros are now using. Again, Bookwormpup64 requires this specific set-up
And 'lolat' means it's low-latency.....and hence, that little bit more responsive.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
What you need to do is simple. Assuming this is BWP64 10.0.7 in use:-
Rename 'vmlinuz-6.6.25-64oz-aoum-lolat' to JUST 'vmlinuz'
Rename 'kernel-modules.sfs-6.6.25-64oz-aoum-lolat' to 'zdrv_dpupbw64_10.0.7.sfs'
As for the firmware 'module' - the 'fdrv' - these are kernel-agnostic. They're not tied to any specific kernel, so my advice would be to leave that one as-is for now.
Now, just swap those two files for the identically-named items in Bookwormpup's 'base' directory (alongside all the other system SFS files - the 'adrv', bdrv', etc. Then, re-boot.
(Put the original two somewhere 'safe' temporarily.....just in case you need to revert, like.)
During the boot-time verbosity, you'll see what the kernel is; it's usually mentioned in the very first line! You'll soon see if you got it right....
Let us know if that works for ya. I always do this sort of thing manually; it's not that I don't like using the provided utilities, but I've always found a lot of this kinda stuff is just quicker done by hand....
Mike.