Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Michele31415 on September 23, 2021, 08:40:41 PM
-
There is another thread here https://forum.amiga.org/index.php?topic=5463.0 that descibes my problem exactly. I got OS 2.9 running and then did an install of AmiFTP. It worked fine - until I rebooted. Now I get messages like:
Cannot open "resource.library", version 44
when I try to run AmiDock (although I do have that file in LIBS:) and
Can't open version 40 of gadgets/fuelgauge.gadget
when I try to run AmiFTP.(and I have that file too).
Unfortunately, even after reading that thread I still don't understand how to fix this. One suggestion was toi replace C:SetPatch from the 3.9 CD, but my CD has no SetPatch in its C directory. I did replace it from my USB backup but I think that was the same file (it was the same size anyway, 31.8K) and that didn't fix the problem anyway. Another post suggests that some classes are missing somewhere but I can't tell which ones.
And a number of other programs won't start now either. Could someone please help me out of this mess? I'm totally stumped here.
FWIW, I'm using KS 40.63, WB 45.1 and SetPatch 44.13
FWIW2: If I boot from the Emergency 3.9 Rescue Disk, AmiDock works OK but my primary boot disk FS3: does not appear on the WB screen.
-
You somehow effed up the LIBS: assign, is my guess, probably by not using the ADD keyword in user-startup somewhere.
If you open a command line shell and type “assign” and press enter, you should see many paths assigned to LIBS: - what do you see?
-
Check if you got everything copied into your Classes:
My first install did miss to copy something and I had to compare and found something was missing.
-
You somehow effed up the LIBS: assign, is my guess, probably by not using the ADD keyword in user-startup somewhere.
If you open a command line shell and type “assign” and press enter, you should see many paths assigned to LIBS: - what do you see?
I see:
Volumes:
MSDOS5.0 [Mounted]
AmigaOS3.9 [Mounted]
Ram Disk [Mounted]
AsimCDFS_v3_Install [Mounted]
FS5 [Mounted]
FS4 [Mounted]
FS3 [Mounted]
Directories:
MUI FS3:MUI
AmiTCP FS3:AmiTCP/AmiTCP-3.0b2
AsimCDFS FS3:AsimCDFS
HELP <LOCALE:Help>
LOCALE FS3:Locale
+ FS3:MUI/Locale
KEYMAPS FS3:Devs/Keymaps
PRINTERS FS3:Devs/Printers
REXX FS3:S
CLIPS Ram Disk:Clipboards
T Ram Disk:T
ENV Ram Disk:ENV
ENVARC FS3:Prefs/Env-Archive
SYS FS3:
C FS3:C
S FS3:S
LIBS FS3:Libs
+ FS3:Classes
+ FS3:MUI/Libs
DEVS FS3:Devs
FONTS FS3:Fonts
L FS3:L
Devices:
PC0 TCP CD0 AWNPIPE VNR
VNC PIPE RAM CON RAW
SER PAR PRT DH1 DF0
DH0 SDH1 DF1
My startup-sequence is:
PsdLoadModule DEVS:input.device QUIET ;Added by Poseidon-Installer
; $VER: Startup-Sequence_HardDrive 45.1 (25.11.00)
; Startup-Sequence for hard drive systems
If Exists C:IDEFix
C:IDEFix
EndIf
C:SetPatch QUIET
C:Version >NIL:
C:AddBuffers >NIL: DF0: 15
FailAt 21
C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ
Resident >NIL: C:Assign PURE
Resident >NIL: C:Execute PURE
Assign >NIL: ENV: RAM:ENV
Assign >NIL: T: RAM:T
Assign >NIL: CLIPS: RAM:Clipboards
Assign >NIL: REXX: S:
Assign >NIL: PRINTERS: DEVS:Printers
Assign >NIL: KEYMAPS: DEVS:Keymaps
Assign >NIL: LOCALE: SYS:Locale
Assign >NIL: LIBS: SYS:Classes ADD
Assign >NIL: HELP: LOCALE:Help DEFER
BindDrivers
C:Mount >NIL: DEVS:DOSDrivers/~(#?.info)
C:LoadMonDrvs
;IF EXISTS DEVS:Monitors
; IF EXISTS DEVS:Monitors/VGAOnly
; DEVS:Monitors/VGAOnly
; EndIF
; C:List >NIL: DEVS:Monitors/~(#?.info|VGAOnly) TO T:M LFORMAT "DEVS:Monitors/%s"
; Execute T:M
; C:Delete >NIL: T:M
;EndIF
SetEnv Language "english"
SetEnv Workbench $Workbench
SetEnv Kickstart $Kickstart
UnSet Workbench
UnSet Kickstart
C:AddDataTypes REFRESH QUIET
C:IPrefs
C:ConClip
Path >NIL: RAM: C: SYS:Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:WBStartup SYS:Tools SYS:Tools/Commodities
SYS:System/REXXMast >NIL:
IF EXISTS S:User-Startup
Execute S:User-Startup
EndIF
Resident Execute REMOVE
Resident Assign REMOVE
C:LoadWB
EndCLI >NIL:
and my user-startup is
;BEGIN AsimCDFS
echo "Mounting AsimCDFS..."
assign AsimCDFS: "SYS:AsimCDFS"
assign AsimCDFS_Buffer: "QDH0:AsimCDFS_Buffer"
mount >NIL: CD0:
;END AsimCDFS
;BEGIN ViNCEd
; Remove the ; default console handler CON:
; Entfernen Sie das ; die Standardkonsole CON: verwenden wollen.
;SetVNC Quiet Mount Override as CON:
; Remove the ; gadgets with new functions from ViNCEd that can be set with prefs tool ViNCEd.
; Entfernen Sie das ; FM-dhigkeiten von ViNCEd in Texteingabefeldern wollen. Diese konfigurieren Sie
; auch mit dem Voreinsteller ViNCEd.
;StringSnip >NIL: INSTALL
; Remove the ; assigns in pattern matching commands.
; Entfernen Sie das ; UnterstM-|tzung der mehrfach Assign in Dateinamensmustern
wM-|nschen.
;TrueMultiAssigns
;END ViNCEd
;BEGIN Genesis
assign AmiTCP: "FS3:Internet/Genesis"
;END Genesis
fs3:clicktofront
;BEGIN AmiTCP/IP
assign AmiTCP: FS3:AmiTCP/AmiTCP-3.0b2
path AmiTCP:bin add
; AmiTCP:bin/login -f denber >"con:*/*/*/200/AmiTCP-IP Login/AUTO/CLOSE/WAIT"
AmiTCP:bin/umask 022
run AmiTCP:bin/startnet
;END AmiTCP/IP
;BEGIN Poseidon
ENVARC:PsdStackloader
;END Poseidon
;BEGIN MUI
assign MUI: "FS3:MUI"
assign add LIBS: MUI:Libs
assign add LOCALE: MUI:Locale
assign add HELP: MUI:docs
;END MUI
-
Check if you got everything copied into your Classes:
My first install did miss to copy something and I had to compare and found something was missing.
What should I compare it to? This is what I have in FS3:Classes:
Gadgets Dir ----rwed Friday 15:08:13
DataTypes Dir ----rwed 24-Nov-00 09:05:14
Images Dir ----rwed Friday 15:08:17
arexx.class 8512 ----rwed 05-Jul-99 03:19:30
requester.class 14768 ----rwed 24-Mar-98 23:02:46
window.class 30528 ----rwed 06-Dec-98 20:15:26
USB Dir ----rwed Monday 12:35:20
classes.txt 392 ----rwed Today 12:50:14
4 files - 4 directories - 119 blocks used[/font]
-
All files? I think I had missing gadgets.
From Greg Donner website:
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]
-
All files? I think I had missing gadgets.
...
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]
Yep - I did see that. We can cross off the 040/060 comment because I only have a 68030. I didn't know what to make of "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)." I don't know where (or what) the "Boing Bag" is, and I do have all the gadgets from the CD-ROM. How do I tell what version they are? I also saw some suggestions that I have the wrong SetPatch. No idea how to address this either. If you just type "SetPatch" in OS 3.9, what should it return?
-
So I found this in the 3.9 FAQ:
Q: After installation, I have SetPatch v44.13 in my C: directory. Is this the latest version of SetPatch? [fixed in OS 3.9 SE CD]
A: No. The latest version of SetPatch on the 3.9 CD (v44.16) is not copied to your hard drive during installation, and needs to be copied manually. There are five copies of SetPatch on the CD, so you'll want to copy the last entry listed in bold:
AmigaOS3.9:OS-Version3.9/First-Install/c/SetPatch ... 44.2 (04.10.99)
AmigaOS3.9:Emergency-Boot/C/SetPatch ... 44.13 (05.03.00)
AmigaOS3.9:OS-Version3.9/Workbench3.5/C/SetPatch ... 44.13 (05.03.00)
AmigaOS3.9:OS-Version3.9/Workbench3.9/C/SetPatch ... 44.13 (05.03.00)
AmigaOS3.9:OS-Version3.9/Emergency-Disk/C/SetPatch ... 44.16 (15.09.00)
As Stephen Rupprecht pointed out, you should always use the latest version of SetPatch available.
So I did that. I copied the SetPatch from the CD-ROM to my startup-sequence and rebooted. Now it won't boot at all. I get seven flashes from the power LED, some flicking disk activity LED and then a red box "Software error" screen. If I boot from the 3.9 Emergency disk, FS3 doesn't even appear in WB. If I boot from my WB 3.1 floppy it shows up as "DH0:NDOS" and I can't do anything with it. :-(
-
Now it starts sounding like FS3: is a larger than 2GB partition… that may have been corrupted in all this messing around with rom updates and setpatch.
-
Speaking to your original problem, AmiFTP or something else you installed overwrote one or more files in SYS:Classes with older versions. For some reason, this manifests as a "cannot open resource.library" error - I don't know why. But this is a very common problem, usually resulting from badly-written install scripts that do a blind copy into SYS:Classes without checking/comparing file versions. You'll need to copy the correct files back from the 3.9 CD.
As to your new problem of being unable to boot, do a cold restart (power down the machine, wait ~30 seconds, power back on). Does the exact same thing happen, i.e., it starts to boot with disk activity and then crashes? What I'm trying to diagnose here is whether your partition is damaged (the NDOS error) or whether SetPatch (more accurately: one of the ROM module updates that SetPatch kicks in) is causing the crash.
Once you get your system bootable again, make sure to install both of the Boing Bag updates in order (available here (https://os.amigaworld.de/index.php?lang=en&page=12)). They include important bugfixes.
-
Now it starts sounding like FS3: is a larger than 2GB partition… that may have been corrupted in all this messing around with rom updates and setpatch.
By golly, it looks like you're right. I could have sworn it was 2 GB but HDtoolBox says 4 GB.
But - it turns out that after a cold boot, I was able to boot into FS3: using the new SetPatch from the CD after all.
I'm only using about 400 MB on FS3:. Can I change the partition size using HDToolBox or is this a lost cause?
SetPatch now reports:
AMIGA ROM Operating System and Libraries
Copyright M-) 1985-2000 Amiga International, Inc.
All Rights Reserved.
SetPatch (V44.16) has already been installed. Patch list:
BOOL CheckIO() workaround
Enabled Advanced Graphics Modes
AmigaOS Copyright
ramlib signal usage
stack size check for CON:, RAW:, RAM:, PAR:, PRT:, SER:
graphics/WritePixelLine8()
graphics/WriteChunkyPixel()
Memory Pools
Enabled data cache
No ROM updates have been installed by SetPatch.
-
Speaking to your original problem, AmiFTP or something else you installed overwrote one or more files in SYS:Classes with older versions. For some reason, this manifests as a "cannot open resource.library" error - I don't know why. But this is a very common problem, usually resulting from badly-written install scripts that do a blind copy into SYS:Classes without checking/comparing file versions. You'll need to copy the correct files back from the 3.9 CD.
As to your new problem of being unable to boot, do a cold restart (power down the machine, wait ~30 seconds, power back on). Does the exact same thing happen, i.e., it starts to boot with disk activity and then crashes? What I'm trying to diagnose here is whether your partition is damaged (the NDOS error) or whether SetPatch (more accurately: one of the ROM module updates that SetPatch kicks in) is causing the crash.
Once you get your system bootable again, make sure to install both of the Boing Bag updates in order (available here (https://os.amigaworld.de/index.php?lang=en&page=12)). They include important bugfixes.
Thanks. The NDOS got resolved by doing a cold boot (I keep forgetting about that). Now I'm trying to get those BoingBag files onto the Amiga. I have the net up but AmiFTP doesn't work. So I either need a different FTP client or I'll try to get the Deneb running, or maybe I can write them to a CD and read that (at least the CD-ROM is working).
What if I just copy all the classes from the 3.9 CD onto FS3, or will that mess up soemthing else.
-
Well I got Deneb working again (it was missing FAT95 from L: which causes it to silently do nothing when you insert a USB stick, unless you run Trident to see the error message) and got the BB1 update on FS3:. lha x claims it extracted successfully. But when I clicked on Install I got:
Sorry... an Error Has Occurred!
Update failed. Please check whether your AmigaDOS 3.9 CD-ROM is inserted in your CD-ROM drive and whether the download of the update archive worked correctly.
Then try again. If it still doesn't work contact our support.
Well my 3.9 CD *is* in the drive, and it's an official copy and I can see its icon in WB and I can see files on it and lha says the update was extracted successfully. So I tried again, and got the same error. :-(
-
What if I just copy all the classes from the 3.9 CD onto FS3, or will that mess up soemthing else.
Are you still getting the resource.library error? If so, yes, re-copy those files from the CD. (I'm assuming that your OS installation is basically stock apart from AmiFTP, MUI, Trident.)
I'm only using about 400 MB on FS3:. Can I change the partition size using HDToolBox or is this a lost cause?
Lost cause, I'm afraid. If you resize a partition you need to reformat it. But it might be worth undertaking that operation (back up to another partition first!) to prevent problems like what kolla describes. You're playing with fire with a 4GB boot partition.
Well I got Deneb working again (it was missing FAT95 from L: which causes it to silently do nothing when you insert a USB stick, unless you run Trident to see the error message) and got the BB1 update on FS3:. lha x claims it extracted successfully. But when I clicked on Install I got:
Sorry... an Error Has Occurred!
Update failed. Please check whether your AmigaDOS 3.9 CD-ROM is inserted in your CD-ROM drive and whether the download of the update archive worked correctly.
Then try again. If it still doesn't work contact our support.
Well my 3.9 CD *is* in the drive, and it's an official copy and I can see its icon in WB and I can see files on it and lha says the update was extracted successfully. So I tried again, and got the same error. :-(
This is a strange one. Start by re-downloading the Boing Bag, re-copying it to your system, re-extracting it and trying again.
My only other guess is that you have an old version of Installer that can't correctly parse the install script. In a shell, type 'which installer' - it will probably report C:Installer or SYS:Utilities/Installer. Whatever it tells you, now type 'version SYS:Utilities/Installer full' (but use whatever path the 'which' command gave you) and report back.
-
Are you still getting the resource.library error? If so, yes, re-copy those files from the CD. (I'm assuming that your OS installation is basically stock apart from AmiFTP, MUI, Trident.)
Yes, it's still throwing that error, and the fuelgauge.gadget error from AmiFTP too. So copy all the library files from the CD back to FS3:libs?
Lost cause, I'm afraid. If you resize a partition you need to reformat it. But it might be worth undertaking that operation (back up to another partition first!) to prevent problems like what kolla describes. You're playing with fire with a 4GB boot partition.
Well then I'll have to do that. Is it OK to try to fix the library problem first?
This is a strange one. Start by re-downloading the Boing Bag, re-copying it to your system, re-extracting it and trying again.
My only other guess is that you have an old version of Installer that can't correctly parse the install script. In a shell, type 'which installer' - it will probably report C:Installer or SYS:Utilities/Installer. Whatever it tells you, now type 'version SYS:Utilities/Installer full' (but use whatever path the 'which' command gave you) and report back.
FS3: > which installer
FS3:Utilities/Installer
FS3: > version FS3:Utilities/Installer full
installer 44.10 (10/01/1999)
I should add that the problems began after installing AmiFTP, but AmiFTP requires ClassAct, so I installed that too. Classes? Hmmm... Maybe ClassAct is the culprit here.
Or who knows. When I boot the 3.9 Emergency floppy, I do not get the AmiDock error, but the floppy has a very small set of files in LIBS. And the floppy also contains a file devs/AmigaOS ROM Update which is the same size and date as the one on FS3. The floppy also has the same SetPatch (checked with version). But FS3 will not boot at all with AmigsOS Rom Update present in devs. It blinks the LED for a while then goes to the red box "Software Failure" message. So that's odd. How come the floppy can boot OK with AmigaOS Rom Update present, and not give the AmiDock error, but FS3 cannot?
-
ClassAct spoils Reaction.
-
Are you still getting the resource.library error? If so, yes, re-copy those files from the CD. (I'm assuming that your OS installation is basically stock apart from AmiFTP, MUI, Trident.)
Yes, it's still throwing that error, and the fuelgauge.gadget error from AmiFTP too. So copy all the library files from the CD back to FS3:libs?
Yes, but it's the contents of the Classes directory on the CD to SYS:Classes, not the contents of Libs on the CD to SYS:Libs. It's a 2-part shell operation:
copy AmigaOS3.9:OS-Version3.9/Workbench3.5/Classes/#? SYS:Classes ALL CLONE
copy AmigaOS3.9:OS-Version3.9/Workbench3.9/Classes/#? SYS:Classes ALL CLONE
Lost cause, I'm afraid. If you resize a partition you need to reformat it. But it might be worth undertaking that operation (back up to another partition first!) to prevent problems like what kolla describes. You're playing with fire with a 4GB boot partition.
Well then I'll have to do that. Is it OK to try to fix the library problem first?
Yes, get the system stable first. Then use Thomas's check4gb (http://thomas-rapp.homepage.t-online.de/download.html) which will give you precise info on whether you need to undertake this operation.
This is a strange one. Start by re-downloading the Boing Bag, re-copying it to your system, re-extracting it and trying again.
My only other guess is that you have an old version of Installer that can't correctly parse the install script. In a shell, type 'which installer' - it will probably report C:Installer or SYS:Utilities/Installer. Whatever it tells you, now type 'version SYS:Utilities/Installer full' (but use whatever path the 'which' command gave you) and report back.
FS3: > which installer
FS3:Utilities/Installer
FS3: > version FS3:Utilities/Installer full
installer 44.10 (10/01/1999)
I should add that the problems began after installing AmiFTP, but AmiFTP requires ClassAct, so I installed that too. Classes? Hmmm... Maybe ClassAct is the culprit here.
Yes, as zipper says, it's ClassAct that's responsible for the resource.library and fuelgauge problems. That's what I was trying to say in my first post. Your Installer is the correct version. I don't think ClassAct would affect the BoingBag installation, but it's possible (depending on how the internal checks of the installation operate). Fix the other problems first, then come back to this one.
-
Well now this is odd. Figuring I'd just give up on AmiFTP, I installed gui-ftp. It goes into execution and I can connect to a server but it won't download anything. Next up was rsync-2.5.5. That refused to run without ixemul-48.0 so I installed that too. rsync also started running but something is wrong with its handshaking with the remote machine and it just hangs. Oh well. So then jsut for laughs I tried AmiFTP again - and this time it worked! No "can't open library" errors. ??? Go figure.
-
Well now this is odd. Figuring I'd just give up on AmiFTP, I installed gui-ftp. It goes into execution and I can connect to a server but it won't download anything. Next up was rsync-2.5.5. That refused to run without ixemul-48.0 so I installed that too. rsync also started running but something is wrong with its handshaking with the remote machine and it just hangs. Oh well. So then jsut for laughs I tried AmiFTP again - and this time it worked! No "can't open library" errors. ??? Go figure.
Did you restore the contents of SYS:Classes from the 3.9 CD? If so, AmiFTP and any other ClassAct programs should work out-of-the-box. ReAction (i.e., the contents of SYS:Classes on OS3.9) replaces/supersedes ClassAct. Since you had installed ClassAct over 3.9, you ended up with a mix of ClassAct and ReAction classes, which caused your original problem.
-
Yes, but it's the contents of the Classes directory on the CD to SYS:Classes, not the contents of Libs on the CD to SYS:Libs. It's a 2-part shell operation:
copy AmigaOS3.9:OS-Version3.9/Workbench3.5/Classes/#? SYS:Classes ALL CLONE
copy AmigaOS3.9:OS-Version3.9/Workbench3.9/Classes/#? SYS:Classes ALL CLONE
OK, I did both of those and then a cold boot. It boots OK but version reports Workbench 40.42 and AmiFTP is back to complaining about version 42 of gadgets/layout.gadget. version layout.gaget reports 45.4. Interesting that it's not complaining about fuelgauge now - this is a different gadget.
Yes, get the system stable first. Then use Thomas's check4gb (http://thomas-rapp.homepage.t-online.de/download.html) which will give you precise info on whether you need to undertake this operation.
It says:
Name Volume Size Device Unit Version DosType Version Big Check
DH1 FS3 4095G gvpscsi 0 3.7 DOS1 40.1 yes * S
DH0 FS4 4030M gvpscsi 1 3.7 DOS1 40.1 no ok
SDH1 FS5 2047M gvpscsi 3 3.7 DOS3 40.1 no ok
CD0 AmigaOS3.9 467M gvpscsi 6 3.7 ASIM 3.6 no ok
PC0 720K mfm 0 40.9 MSD0 40.19 no ok
DF0 880K trackdisk 0 40.1 DOS0 40.1 no ok
DF1 AsimCDFS_v3_Instal880K 880K trackdisk 1 40.1 DOS0 40.1 no ok
Yes, as zipper says, it's ClassAct that's responsible for the resource.library and fuelgauge problems. That's what I was trying to say in my first post. Your Installer is the correct version. I don't think ClassAct would affect the BoingBag installation, but it's possible (depending on how the internal checks of the installation operate). Fix the other problems first, then come back to this one.
I also tried running BoingBag3.9-1 again. This time it doesn't complain about the CD-ROM but when I click Proceed, the install window disappears and then nothing happens - no errors, no messages, nothing.
-
I can't tell from here what it is exactly, but your system has some serious software issues. It looks like 3.9 is not correctly/fully installed. Workbench should be 45.x. Your filesystem version (as reported in check4gb) should also be 45.x rather than 40.1.
-
Why don't I just try the install from the 3.9 CD over again. It would be nice if I could do that without killing my x-surf and Deneb installations but at this point it may be quicker to just rebuild those than continuing to try and untangle this mess.
-
I have to install 3.9 twice and even then it write protects some stuff and won't reinstall them. At that point I go to Dopus or Dir Work to move/copy files and get rid of the write protect.
Chris
PS: A similar speced 2000 6.2 machine 030/40 combo.
-
Oh, that's good to know. Could you tell me a bit more? I odn't know what Dopus or Dir Work is. How do I get rid of write protect?
-
Directory Opus is very configurable but may be difficult, Dir Work is just 1 thing, 2 windows side by side, to and from with buttons for protect, executable and so on. It's old and on aminet.
Chris
-
It says:
You've got a serious issue with that FS3 partition. It is reported as almost 4TB, that's far beyond an Amiga's capability. Not to mention that FFS V40 can only access less than 4GB. This is also the reason why it gurus after loading the OS 3.9 ROM update.
I checked with UAE. It happens if you use HDToolbox of OS 3.1 and cylinder numbers overflow. You should recreate the partition with HDToolbox of OS 3.9. And you should update FFS to version 45.
-
Lol, good catch Thomas, didn't even notice the G at the end. :o
-
Heh! Me either. I ran the check4gb program, copied its output to my PC, then copied it into my post here, and in not one of those operations did I notice it said G instead of M for DH1. Obviously that's impossible since the entireSD card is only 16 GB. I'd say excellent catch, Thomas!
So I repartitioned DH1 using the 3.9 HDToolBox and made it smaller this time, and ran check4gb again. Now it shows:
Name Volume Size Device Unit Version DosType Version Big Check
DH1 985M gvpscsi 0 3.7 DOS1 45.9 no ok
DH0 4030M gvpscsi 1 3.7 DOS1 45.9 no ok
QDH0 QDH0 2169M gvpscsi 2 3.7 DOS3 45.9 no ok
SDH1 FS5 2047M gvpscsi 3 3.7 DOS3 45.9 no ok
EMERGENCY_CD AmigaOS3.9 512M gvpscsi 6 3.7 CD01 42.19 no ok
DF0 Emergency-Disk 880K trackdisk 0 40.1 DOS0 45.9 no ok
DF1 AsimCDFS_v3_Instal880K 880K trackdisk 1 40.1 DOS0 45.9
Then I formatted DH1 as FS3, did a complete install of 3.9 from the CD-ROM and CTL-A-A rebooted. This time FS3 booted fine with no gurus, WB reported 45.1, and AmiDock started without errors. Then I tried installing BB1. That worked fine too. No complaints about the CD-ROM, everything installed fine.
So I rebooted, installed BB2 and rebooted again. This time I got a yellow "Recoverable error" box. I clicked left and got the error again. I clicked left again and then it booted into FS3 correctly. I tried a cold boot and got the same error. So what's up with that? FWIW I said Yes when BB2 offered to update my Amiga OS ROM Update. Was that a mistake? Here's the log:
******* Installation Log *******
User Level: AVERAGE
Pretend: No
>On which partition should Boing Bag 2 for AmigaOS 3.9 be installed?
Ask Drawer: Result was "FS3:".
Run Program: "C/Version "FS3:Libs/xadmaster.library" FILE VERSION 10"
>
>BoingBag 3.9-2 contains a new AmigaOS ROM Update. Although it has been
>tested thoroughly it may fail on some hardware configurations. Do you
>wish to install it?
>
>IMPORTANT: Please REALLY read the help text. ROM Update is provided with
>only limited warranty and support! Neither Amiga Inc. nor HAAGE&PARTNER
>are obliged to make sure that it will work on your system. Please also
>read the Readme file.
>
>The AmigaOS ROM Update is installed on your system. So generally, it
>should be safe for you to update it.
Ask Question: Result was "Install ROM Update".
Run Program: "C/Updater AmigaOS-Update "FS3:""
Run Program: "C/Updater XAD-Update "FS3:""
Copy file "FS3:Devs/AmigaOS ROM Update" to "FS3:Devs".
Copy file "FS3:Devs/AmigaOS ROM Update.BB39-2" to "FS3:Devs".
Copy file "C/Installer" to "FS3:C".
Copy file "C/Installer" to "FS3:Utilities".
Run Program: "C/RemoveResident"
Exiting script...
In any event aside from that things are looking much better now.
-
This time I got a yellow "Recoverable error" box.
What's the error number?
-
It says:
Recoverable Alert. Press left mouse button to continue.
Error: 0100 0003 Task: 00212E18
Oddly enough, when I cold-booted it this time, I only saw that once. After clicking left, it continued to boot normally. Was BB2 a bag too far?
UPDATE: Apparently, the error message goes away on its own after about 20 seconds even if you don't click on anything. It then proceeds to finish booting normally.
-
@Michele31415,
Why such a large System partition? I keep mine at 300 Mb or so and don't write to it often. stays nice that way.
Chris
-
I guess I was making it like my PC. I have a 2 TB drive there, and it's all one big partition, drive C:.