I currently have slackware64 -current installed. I use R and PostgreSQL and a couple of other apps a lot. It seems that trying to get recent versions of those programs requires SBopkg and other repositories and other issues. One of the main things giving me problems is that slackpkg doesn't show what I've added and I lose track of what's installed and then I've got a conflict or something. I was thinking of switching to 14.2, since at least a couple of my problems would be fixed then with the more reliable slackpkg.

The problem with 14.2 was that that I couldn't get it to install. In that link, I said then that I thought LILO and/or UEFI was the problem. Now, I think the problem had something to do with one of the components of isolinux directory, like efiboot or isolinux.bin. I don't know that for sure, but based on what I could gather from the discussion in that previous link, there is a comment that the versions of isolinux are kind of dated and that may be why my computer wasn't getting to the actual boot of the ISO DVD.

When 14.2 wasn't working, I tried the -current version, with newer versions of the isolinux components and I got the installation to work. Thus, I was thinking, what if I took the -current isolinux directory and its components and replaced the isolinux in standard 14.2 64bit with that?

I did that and used the instructions in the README of the isolinux directory of the ISO to create a new ISO DVD that I then added to a USB. Here is the relevant code from the README:
When I tried to run the install just now it gave me a menu with options for (I don't remember the exact verbiage, this is from memory)
'kernel huge
kernel huge KMS
search for any installed OS'

I selected kernel huge and then the next screen said something like
'need a kernel' (again, that's from memory and may not be exactly what it said)

It took me back to the menu listed just above and I tried the KMS option and I got the same error. Then I opted for the 'installed OS' and I'm back in Windows at the moment.

My question now is, should my idea to just copy and paste the isolinux directory in -current into the same place in 14.2 and create a custom ISO have worked? If not, what was I missing? Was there something in a script in the custom ISO that I should have edited to make it work?

I hope this isn't an annoying suggestion, but have you tried emailing the PostgreSQL slackbuild maintainer and just asking if he'll bump the version up? If there's no response, fair enough but I've had a reasonably good success rate with this.

Here is a snippet from a script I use. I have used the script for many years. Through cron jobs I create new DVD ISO images with all of my local repo updates. Works fine with 14.2. I've used the script for so long that I don't remember where I grabbed the basic components -- perhaps from one of Eric's scripts.

@bifferos, I don't think your suggestion is annoying. I've never contacted a maintainer before because I'd worry I was being annoying though. Maybe that's what you meant? I figure most of those people are have jobs and that they volunteer as maintainers and so are busy and don't need a newb like me asking them for stuff. My issue is more than the PostgreSQL thing, that was just one of the examples I threw in the post to show where I was coming from. I'll consider your suggestion. It's possible that the maintainers are waiting for the next major version? I have no idea where the cycle is concerning that.

@upnort, thanks for that script. I'll give that a whirl.

I'd never get annoyed about a version bump request for any of the (albeit two!) packages that I maintain there. I think the fact that a package does exist elsewhere (https://github.com/conraid/SlackBuil...ter/postgresql) would help things, that means someone has a working slack-build that just needs to be moved across.

I tried to create the ISO using upnort's script. I get the same error message. This time I wrote it down.