Amiga.org

Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Boot_WB on April 24, 2006, 08:34:29 PM

Title: Resource.library error after installing new OS3.9 updates
Post by: Boot_WB on April 24, 2006, 08:34:29 PM
Mentioned this in another thread, but I think it deserves its own thread.
After installing the latest unofficial patches 1 (http://www.aminet.net/package.php?package=util/sys/OS39_update_patches.lha) and 2 (http://www.aminet.net/package.php?package=util/sys/OS39_update_patches2.lha) for workbench.library, etc from aminet I have the Amidock is unable to open resource.library v44 problem.

Yes, I have checked classes - they are pretty much all more recent than the OS3.9 disk ones, indicating they are the ones installed from boing bags, not old classact ones.

I have not touched resource.library.

Has anyone elses applied these patches?  Did you apply both patches consecutively to the workbench.library, or just apply the second patch?

Following the readme of the second patch (which indicated a requirement for workbench.library 45.127) I applied this directly to workbench.library without installing the first workbench.library patch.
Sorry, that reads like crap, and is confusing.

I patched directly 45.127 --> 45.131
Should I have patched 45.127 --> 45.130 -->45.131?

If so the readme needs altering to make 45.130 a requirement of the second patch, as it is currently misleading.

Thanks.

PS I'm away from my amiga for the week, so can't test things
Title: Re: Resource.library error after installing new OS3.9 updates
Post by: lionstorm on April 24, 2006, 08:44:01 PM
from os3.9 FAQ :

"20.
Q:
On bootup, I get the following error message: "Cannot open resource.library, version 44, unable to load AmiDock". I have the correct version of resource.library installed, and AmiDock exists in SYS:WBStartup. Why does this appear, and how do I eliminate this error?
A:
In many cases the problem message you received did not accurately reflect a missing or even damaged library, but rather the absence of a "#?.gadget" file that the resource.library function depends on. Check the SYS:Classes/Gadgets/ directory on your system partition and the OS3.9 directory of the install CD-ROM and manually copy any missing #?.gadget files. Ensure that all the #?.gadget files are the latest versions (do this by checking the latest Boing Bag first, then the OS 3.9 CD-ROM).

[Mike Wilson/Cor Kriekaart]

Another cause for this message may be a corrupt or incorrectly installed 68040.library and/or 68060.library file. Make sure that you're using the correct--and valid--680x0.libraries. Such a corrupt file may work under OS 3.1, but will fail in OS 3.9.

[Rob Pleak]

Note that UnixDirs3 has the ability to redirect '/' to be the same as ':'; the root of the drive. This causes many poorly written installers to fail that rely on '/' to be 'parent directory'."

Lio

Title: Re: Resource.library error after installing new OS3.9 updates
Post by: Boot_WB on April 24, 2006, 08:49:30 PM
Thanks lio, as I said I've checked the classes (and gadgets).  I'm running BPPC so 680*0 libraries aren't an issue.
The OS3.9 installation was working fine before installing the update.
Title: Re: Resource.library error after installing new OS3.9 updates
Post by: Doobrey on April 25, 2006, 06:01:03 PM
Quote

Boot_WB wrote:

Following the readme of the second patch (which indicated a requirement for workbench.library 45.127) I applied this directly to workbench.library without installing the first workbench.library patch.
Sorry, that reads like crap, and is confusing.

I patched directly 45.127 --> 45.131
Should I have patched 45.127 --> 45.130 -->45.131?


The instructions are correct. Patches are always based on a specific version of a file, so if you try to patch the wrong file (eg. trying to patch 45.130 with the 45.131 .pch) spatch won't do it and complain.
 Did you try copying back the original workbench and icon libraries ?
Title: Re: Resource.library error after installing new OS3.9 updates
Post by: Boot_WB on April 30, 2006, 04:54:50 PM
Found the problem (eventually): another install (of what, I can't remember) had replaced picture.datatype by another version.  Also bevel.image had been replaced, but I'm guessing that wouldn't be too much of an issue.

Problem solved anyhow.  Thanks for suggestions.