Hello,
> On Mar 17, 2020, at 12:47 PM, joseph.nor...@gmail.com wrote:
>
> Hi:
>
> No problem.
>
> I also found one more thing that was causing a minor problem, but, it wasn’t
> a show-stopper.
>
> Anyway, I’ll just tell you about it, just in case.
>
> If I tried to put more than one package in the assist folder for inclusion,
> it usually failed to build also, but, I don’t remember what the error was at
> the time. I was careful not to have anything that was duplicate, though.
> Again, that’s a minor issue and can be worked around.
>
> Maybe the new build process will eliminate this anyway, so it’s not a big
> issue.
I was unable to duplicate this issue…
I created a second fake assistance package.
Dropped it into the correct folder along with the existing demo package.
ran “make clean translate all”
waited a while.
RBE had no issues creating the release media.
Downloaded Custom LiveCD and examined ISO, both packages Live on CD and present
in package form for install.
So, I’m unsure what is going on to prevent you from having multiple assistance
packages.
Just as some reminders…
Only one package can contain a FDASSIST.BAT.
The APPINFO/*.LSM used to describe the package must have the same file name as
the package… mysapa.zip must have APPINFO/MYSAPA.LSM
If you have a functioning FreeDOS 1.2 or 1.3 install, you can test install and
removal of your custom packages using FDINST to help find any problems or
possible conflicts.
Jerome
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
