Workbench.library in Deneb flash using Luciferin

[Heiroglyph]

I've added Workbench.library to my Deneb in hopes of not requiring it on every boot disk (it's a 4000T), but it seems to still be looking for it on disk.

I just added the library to the Luciferin project and flashed it, am I missing something?

Thanks

[wawrzon]

cant exactly tell, but would be probably better to add it to a kick image and load the whole image with a submitted tool, dont recall the name.

[alexh]

Workbench.library isn't very big I don't really see the point. It's not like you regularly use boot-disks is it?

Do you need to add "setpatch NOROMUPDATE" to your startup-sequence?

There is a little bit about this in a thread over at EAB

http://eab.abime.net/archive/index.php/t-21599-p-2.html

[Heiroglyph]

I can make them boot, but I'm not happy with the solution.

The machine usually runs OS3.9 and that's the Workbench.library I used.

The old drive had 3.1 on it (with the Workbench library needed for the 4000t) and if the 3.9 Workbench is in the Deneb, it won't boot.  It acts just like not having that library on the disk so I had to remove it from the Deneb.

I've got some valuable development stuff on those drives and I need to run in that environment as it was when it was last used in order to document it and move it to newer drives.

[alexh]

So workbench.library from 3.1 is on those disks but you have a newer WB3.9 workbench.library is in your FlashROM on the deneb and causing the failure?

Why not use workbench.library from 3.1 in the Deneb?

I imagine the standard WB3.9 mechanism of patching KS3.1 ROM will just work?

Does patching workbench.library require a reboot you are trying to avoid?

[Heiroglyph]

Yes, I'm trying to avoid an extra reboot during normal operation and also prevent boot failures caused by the stupid 4000T not having that library in ROM.

It doesn't sound like there is a prefect solution to both problems

That said, 3.9 isn't giving me a lot of benefit at the moment, maybe I should just go back to a 3.1 install with tons of patches.

Does anyone have better suggestions?
Would replacing the whole kickstart with a custom 3.9 version help?

Thanks

[alexh]

Would replacing the whole kickstart with a custom 3.9 version help?

Worth a try. Talk to Cosmos.

I don't really understand why a later version of workbench.library in ROM causes WB3.1 from loading correctly. Perhaps there is a "loadmodule **** reverse" in the startup sequence or something?