Activate included Software (OctaMED, Final Writer, PPaint, ...) in WB installs

[phipslk]

I created a Workbench 3.2 install on my A600GS and added the "programs" folder in the settings. The workbench runs as expected and the "Programs" folder appears, but when I start any of the A600GS software (like OctaMED, Final Writer and so on) I get informed that no customer ID can be found and the software doesn't start. In AmiBench of course everything works fine.
Is there anything more I have to copy over to WB3.2 install to get the software to run?

[F0LLETT]

No, they will only run from AmiBench at the present moment.

[broadblues]

No, they will only run from AmiBench at the present moment.

The correct answer is YES :-) But they need access to various libraries in SystemV46, so when setting up your 3rd party OS install, tick the include global systemv46 check box. SystemV46 has boot priority of 0 so make sure your boot partition for your OS install has a priority of 1 or greater.

Then do:

Assign LIBS: SystenV46 ADD

either just before you launch the application or  perhaps in your S:Startup-Sequance, making sure it's after any LIBS: additions you need for your own  OS's needs.

I've been meaning to try and demonstrate this in a video but time is scarce.

[broadblues]

One caveat to the above, Final Writer is an AROS 68k elf  build as supplied by the authors, so that will only wok under AmiBench or a generic AROS install. The AEon/AmigaKit softwares like OctaMED PPaint et al will run on any 68k S sbject to the LIBS needed.

[phipslk]

if I add the whole libs directory of systemv46 to libs: won't there be libs twice in it? doesn't that could cause problems?
And add the whole systemv46 to C: or only systemv46:libs ?

[F0LLETT]

if I add the whole libs directory of systemv46 to libs: won't there be libs twice in it? doesn't that could cause problems?
And add the whole systemv46 to C: or only systemv46:libs ?

No, you misunderstand. Your just using the libs: drawer from v46.
It will not cuase problems. Not sure what you mean by C:?

[phipslk]

ups, my bad, I meant LIBS: of course, not C:

[broadblues]

The paths i a multiassign are searched in order so:

assign LIBS:  SYS:Libs (done by OS)
assign LIBS: SystemV46:Libs ADD

will look in SYS:Libs first then in SystemV46:Libs if the library needed was not found.