Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Karlos on January 08, 2004, 12:16:49 AM
-
Hi all,
I have just installed OS3.9 onto a previously completely blank, bootable FFS partition using the "Full install over 3.0/3.1 or empty drive" option.
The installation does work in that it boots up to workbench 3.9.
However, the fun stops there. Nothing seems to work since resource.library V44 cannot be opened for some reason.
A quick "version resource.library" shows resource.library 44.102 from Sep 1999.
This is a completely fresh install (no boing bags yet) on a rather unremarkable system:
BlizzPPC 603e+ 240MHz / 68040 @25MHz
256Mb 60ns Fast RAM
BVision (no RTG is installed yet, using PAL display)
10G IDE drive on motherboard IDE (boot partition is
under the 4G barrier)
IDE CDRom, via PCMCIA adaptor
I still have a bootable 3.5 partition which works fine and happens to use the exact same version of the resource.library..
Anybody experience anything like this?
Cheers,
K
-
hmm could be a setpatch thing... are you cold booting straight into the new 3.9 setup? check the correct setpatch is there... thats about all I can think of, oh and does the requester not come up if you stop amidock from loading at the beginning? no real reason for asking, well there is but I cant be bothered to explain myself right now ;-)
-
14.Workbench:Libs> version resource.library full
resource.library 44.103 (28/11/2001)
is what I have...
-
Have resource.library 44.103 on my system.(AmigaOS 3.9 BoingBag 2)
But I think 44.102 is right since 44.103 is from 2001 after OS 3.9 was
made.
Check that the ROM update is installed.
7.System3.9:> version "AmigaOS ROM Update"
AmigaOS ROM Update 44.26
BoingBag 2 gives 44.57!
-
Booting cold straight into it, I noticed that there wasnt the reset stage that 3.5 has. No rom update I wonder?
-
Most likely a missing 68040 or 68060 library, afaik. At least that's what it was for me...
Regards
-
you need the 68040New.libray and the 68040dummy.library renamed 68040.library from DCE or Phase 5.
rename the 68040.libray to 68040old.library
Does anybody know what happened to the DCE download site.
I tried to link there and it does not exist any more.
Ohh do yourself a big Favor and ditch FFS get SFS from aminet.
Besides being Faster and Safer you can no longer invalidate your hard drive. It also is supported under 4.0
Yesterday I set up a hard drive on my A1200 System Using SFS. Made a mirror copy of my hard drive. Updated it to 4.0 stuck it in my AmigaOne and that was the one I showed AMUSE last night.
The reason I mirrored my A1200 HD. Was this way I could show my legacy programs running under OS 4.0 without have to install them all. Yes I was being lazy. But it worked!
-
It's there just hard to find...
http://www.dcecom.de/downloads.html
:-? Why can't I do links in posts when using Voyager 3.3.
-
@neo
you can do links... just not with the buttons, you have to use the proper syntax which the buttons would put in for you, its all in the FAQ for this site iirc... its blah (http://blah) same sorta thing for images etc...
@Karlos...
hmm could be 680x0 lib problem but ive never had such a problem...
@all
all you ever need for Phase5/DCE things can be got from ftp://ftp.meanmachine.ch :-)
Now does anyone have a spare IDE CD-Rom drive... mine just died :-(
-
@Zerohero
Most likely a missing 68040 or 68060 library, afaik. At least that's what it was for me...
These libraries are in the BlizzPPC flashrom, so they can't be missing.
@Karlos
I think OS 3.9 FAQ (http://www.gregdonner.org/os39faq/os39faq.html) Installation Tips (http://www.gregdonner.org/os39faq/installtips.html) should help.
-
The drivers at meanmachine are a little bit older than those at DCE's
homepage but should still work. GREXX drivers work even if you don't
have a GREXX just ensure to update CGX drivers first if you have a
CyberVisionPPC board. (It will show up as a PCI board afterwards)
(Edit: Forgot that you use Blizzard board. But should work similary.)
-
My setup is as follows.
A1200T,Phase 5 PPC 275Mhz 603+/60Mhz 68060,192MB RAM,Yamaha 2100 SCSI CDRW,Pioneer SCSI DVD, Seagate Baricuda SCSI HD 8.5G,IBM SCSI Ultrastar HD 73G,Mediator1200SX,Voodoo 5500,Abit AU-10 Sound Card,Spider USB,Win TV Card,8139 Ethernet Card,RAKA1200 Keyboard Adpater,RAMA mouse adapter,IDEKILL12,Septre 19.1"LCD Monitor. Logitech Cordless Keyboard and Trackman Marble.
To save you alot of nightmares with setting up 3.9 here is what I did
1. formatted HD with SFS .
2. Installed OS 3.9 onto HD
3. Before rebooting make sure you check the startup-sequence. Erase all that setpatch happy horse ####. This is what the begining of your Startup-sequence should look like
; $VER: Startup-Sequence_HardDrive 45.1 (25.11.00)
; Startup-Sequence for hard drive systems
C:BPPCFix install >NIL:
C:SetPatch SKIPROMUPDATES "scsi.device" QUIET
C:Version >NIL:
C:AddBuffers >NIL: DF0: 15
FailAt 21
4. Make sure you have the DCE/Phase5 libraries installed
5. installed CDROM software from 3.9 install script
6. installed PowerPC software support Warp OS V5 from 3.9 Install script selected Wshell Support & Bvision GFX card from Question.
7. Installed BPPCFix from WarpUP archive. In the Startup-sequence before setpatch wrote C:BPPCFix Install >NIL:
Fixes nasty terminate message on starting desktop and is needed to prevent BB2 problems
8. Installed Boing Bag One & Two ALWAYS MAKE SURE TO CHECK THE STARTUP-SEQUENCE SO THAT IT READS LIKE LINE 3 before rebooting.
-
I was told, and i dont know if its correct or not but... if you flash with the grexx flash a mediator wont work, and you cant reflash with an older flash... I did wonder about the reflash part, why wouldnt it be possible? either way I personally see no reason why I should be using the grexx flash on either of my BPPC setups so....
-
@RYU
Good question I had A GREX installed into this mess at one time. I wonder What I did when I installed the mediator. Is there A way to check what version you have flashed?
-
use reportplus from aminet : it can check your os3.9 install and report any missing/wrong/deleted files comparing to a normal os3.9.
I installed the grex flash although I dont have one just because I expected better performance with my BPPC+BVPPC which was not so I flash the older one (231099 IIRC) without problem.
Lio
-
karlos:what is your SETPATCH line? and do u use Blizkick or simmilar ?
-
Hi guys,
I have checked libraries and so on. The 3.9 startup sequence looks odd, but I can see that ultimately SetPatch QUIET is called. This is basically exactly how it looked under 3.5.
I put the BPPCFix before setpatch, just as it is in my 3.5 installation.
Failing all else, I will install a clean, working OS3.5 and then put 3.9 on top of that.
The bizzare thing about all of this is how it complains there is no resource.library v44, when clearly there is. Probably something it itself opens is missing I guess :-)
-
Hi Karlos
IIRC the AOS3.9 CD (first release) install the wrong SetPatch on the HD.
Check if it is at least 44.16 (in the Emergency-Disk directory on the OS3.9 CD)
Ciao
-
@Framiga
Seems to be v44.17 in there...
How ironic. Everybody else seemed to find 3.5 a nightmare and 3.9 bliss. Am I the only one to have ther reverse experience? :-D
-
by Karlos on 2004/1/8 15:50:31
@Framiga
Seems to be v44.17 in there...
your AOS3.9 CD, is the one with the installer for Emulation?
AFAIK, SetPatch 44.17 is by BB-1 that is already integrated in those OS3.9 CD.
I've had the same problem, and IIRC the answer was in the AOS3.9 FAQ section on the official site.
Ciao
-
Hi Karlos,
take a look:
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'.
[Shawn Holwegner]
From here:
http://www.gregdonner.org/os39faq/installtips.html
Ciao
-
@Framiga
Hey, thanks :-) I just installed 3.5 with the plan of installing 3.9 over it, but I might quickly reformat and try that :-D
Incidentally, there doesn't seem to be any mention of the OS3.9 boingbag 2 on os.amiga.com, only the first 3.9 boingbag is there. Where can I get the second one?
Basically, I need a completely clean, unpatched, unhacked OS3.9 installation updated to bb2 status...
-
Hi Karlos,
BB-2 available here:
http://www.haage-partner.de/aos39/index-e.html
Amiga . . . the same old story :-)
Ciao
-
Karlos wrote:
Basically, I need a completely clean, unpatched, unhacked OS3.9 installation updated to bb2 status...
Any luck with the install yet?
-
Does anyone have the same problem as me with Amplifier after
installing BB2. My Amplifier crashes randomly after the update. :-(
The bad thing is that you can't do a manual install from the BB2
package.
-
@GadgetMaster
Not yet mate :-(
Right - heres a weird thing. I have 3 bootable partitions, DH0:, DH1: and DH2:
DH0: is my usual, hacked to bits 3.5 install.
DH1: is a relatively clean 3.5 + bb2 install with just magic menu, king con, and some ppc datatypes.
DH2: is for a clean 3.9 install, which has been formatted like 10 times today already :lol:
Now, clean installing OS3.5 onto DH2: had the same problem as 3.9 - the resource.library error cropped up again! Out of curiosity, I formatted it (again) and copied my DH1: over to it and it functioned fine.
I am left wondering if some changes (blizzard flash updates etc.) I made after installing 3.5 bb1 and bb2 has made my system incompatible with bare 3.5 / 3.9?
-
Have you tried installing the BoingBags straight a fter a clean install of 3.9? or is the resource .lib error preventing the installer from working?
I hope you manage to get it working soon. :-)
-
As a last resort how about installing 3.9 without the accellerator card installed (Sloooow :-( )
Then try getting it to work afterwards. A bit extreme, i know, but I can't really think of anything else at the mo.
-
Thats the basic problem. Without the resource.library virtually nothing works.
Including the installer, it seems :-(
I expect I can keep booting from DH1: (3.5) and tell it to install the bb updates over DH2: anyway, so I will try that later :-)
-
Blimey. Absolutely nothing suggested in this thread so far has worked.
I cant even boot from a 3.5 to run the 3.9 boing bag installer over the 3.9 partition since the installer thinks I am attempting to install over 3.5 ;-)
Somehow, my configutation simply does not get on with OS3.9.
This is becoming a real nusiance. I never expected OS3.9 to be such an a*se.
Random things left to try
1) install under UAE and archive installation to a CD for extraction to DH2:
2) 'swapping' partitions to make the 3.9 install on 'DH0:' in case that makes a difference (no idea why it should)
3) Removing one of the 128M SIMMs in case for some odd reason that makes a difference (no idea why it should).
This is fast becoming a farce...
-
I think I had similar problems. I simply made a double check and found that some files were missing from my installed OS compared to the CD. I think they all were missing from Classes, perhaps Classes/gadgets. After a copy per hand everything began to work. Perhaps a protection flag gone haywire or sun spots...