Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: carvedeye on September 13, 2015, 07:22:37 PM
-
Hi all every time I boot up my Amiga 1200T I get this message before workbench loads up
it is starting to annoy me now do any of you have any ideas? It all started when I installed boing bags 1-4?
TIA Ray
-
Have you examined your startup-sequence for that command somewhere in it?
Did you do a fresh install (onto a clean partition) of 3.9 + BB1-4, or install on top of an existing partition/OS install?
-
Which file system is on the boot disk? Is this FFS formatted or something else?
-
Have you examined your startup-sequence for that command somewhere in it?
Did you do a fresh install (onto a clean partition) of 3.9 + BB1-4, or install on top of an existing partition/OS install?
I think it was a fresh install (haven't been on the miggy for a few month) I have copy and pasted the start up sequence.
; $VER: Startup-Sequence_HardDrive 45.7 (8.11.2014) for BB4
; Startup-Sequence for hard drive systems
If Exists C:IDEFix
C:IDEFix
EndIf
FailAt 21
SYS:C/LoadResident >NIL: DEVS:card.resource DEVS:trackdisk.device L:KingCON-Handler
FailAt 20
SYS:C/LoadModule >NIL: DEVS:battmem.resource DEVS:console.device DEVS:FileSystem.resource DEVS:misc.resource DEVS:potgo.resource DEVS:scsi.device L:FastFileSystem L:Ram-Handler L:Shell-Seg LIBS:dos.library LIBS:layers.library REVERSE NOREBOOT
SYS:C/SetPatch SKIPROMUPDATES console.device,dos,filesystem,FileSystem.resource,ram-handler,scsi.device,shell 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:
SYS:C/MakeLink RAM:disk.info ENVARC:SYS/def_RAM.info SOFT
IF EXISTS S:User-Startup
Execute S:User-Startup
EndIF
Resident Execute REMOVE
Resident Assign REMOVE
C:LoadWB
EndCLI >NIL:
-
SYS:C/MakeLink RAM:disk.info ENVARC:SYS/def_RAM.info SOFT
MakeLink command doesn't have SOFT option. (Edit: it does after the latest updates to 3.9, sorry)
Other more commonly used method is to copy the .info file instead of linking it:
Copy ENVARC:SYS/def_RAM.info RAM:disk.info
-
MakeLink command doesn't have SOFT option.
Why do you say so? This is plain wrong. You *require* the SOFT option to make a link from one device to another. Hard links are only possible within one device.
The "not implemented" message obviously comes from RAM disk. Most likely the updated ram-handler was not installed or disabled. The older ram-handler indeed did not support links.
-
Haha. I love when Amiga users get into arguments. ;)
I just checked mine and for what it's worth, the "SOFT" option does work. I changed mine because I wanted to use a custom icon that's stored in a different place (and commented out the original line), I'll include a screenshot in case this is any help to OP. But I do crazy stuff so maybe it's better to "fix it right" and not follow my example. ;)
OP - try dropping down to a command prompt and checking your version of ram-handler? Should be 44.23, I think there's also a buggy 44.24 floating around out there somewhere.
Another thought - perhaps the icon def_RAM.info somehow got changed to an icon of a different type? For example a Project or a Tool icon, instead of a Disk icon?
You can also do "version c:makelink full" from a command prompt, mine is v45.0 (12/24/2000). Perhaps somehow you have an older version of the command?
-
You can also do "version c:makelink full" from a command prompt, mine is v45.0 (12/24/2000). Perhaps somehow you have an older version of the command?
That is what it says on mine? I'm have also tried it without SOFT and it still doesn't solve my problem? Its says I need the soft for it to work?
-
Another thought - perhaps the icon def_RAM.info somehow got changed to an icon of a different type? For example a Project or a Tool icon, instead of a Disk icon?
If you are using MakeLink because Peter K's icon.library ghosts the Ram Disk icon when the icon is in ENVARC:sys/def_ram.info, it is now possible to add "NoGhost" to the icon tooltype of the icon which you do not want ghosted. It is not possible to add the "NoGhost" tooltype to a disk icon but Peter claims "WB can handle that [icon] if it's a drawer, tool or project icon." The icon type can be changed with Sys:Tools/IconEdit of course.
http://eab.abime.net/showpost.php?p=1028014&postcount=1375
Another tip for keeping the S:Startup-Sequence minimal when there is adequate memory is to set the P (Pure) and H (Hold) file protection bits of C:Assign and C:Execute which allows removing the 4 resident commands pertaining to them. Other common candidates for this technique which provides a small speedup and reduces memory fragmentation include C:Execute, C:List and C:Mount if they are used from scripts or the shell often.
-
If you are using MakeLink because Peter K's icon.library ghosts the Ram Disk icon when the icon is in ENVARC:sys/def_ram.info
Haha. You guessed it, that is exactly why I moved my def_RAM.info to a different location. To avoid that ghosting. I saw that he did add those "NoGhost" features recently, but I haven't bothered to change my S-S back. ;)
-
I am using PeteK's icon.library but I don't have any ghosting on the RAM Icon? However I am getting ghosting on .lha files if that makes a difference.
-
@OP - since we're on the subject, you might also want to make sure you have the latest version of the Peter K. icon.library. It's not on Aminet, I had to hunt through a ridiculously long thread on EAB to find it. @Matthey - do you have a link handy?
-
@OP - since we're on the subject, you might also want to make sure you have the latest version of the Peter K. icon.library. It's not on Aminet, I had to hunt through a ridiculously long thread on EAB to find it. @Matthey - do you have a link handy?
The newest version of Peter's icon.library (version 46.4.412 currently) is always on the first page of the thread. I'll link to that page since it sometimes has important information.
http://eab.abime.net/showpost.php?p=814987&postcount=1
I am using PeteK's icon.library but I don't have any ghosting on the RAM Icon? However I am getting ghosting on .lha files if that makes a difference.
The idea with the icon.library was to make generic default icons (no icon) ghosted which is logical and sometimes helpful to have this visual indicator. The Ram Disk icon would not be ghosted if it was copied to the ram disk (and you had the newest icon.library) but that would require copying it at bootup every time or using MakeLink.
-
@Matthey - do you have a link handy?
A link would be great. I have checked my Libs Folder and I have 5 different icon.library files which are icon.library, icon.library.45.1, icon.library.45.4, icon.library_68000 and icon.library_69020, could this be the problem?
-
I have checked my Libs Folder and I have 5 different icon.library files which are icon.library, icon.library.45.1, icon.library.45.4, icon.library_68000 and icon.library_69020, could this be the problem?
Hahaha. While I don't think this is the cause of you're problem, you're going to want to get rid of those. :lol:
What I do with mine is rename them with a ".old" extension during testing, then once I'm sure the new replacement is working I move them into an archive partition. Keep that main LIBS: folder clean! :D
-
Hahaha. While I don't think this is the cause of you're problem, you're going to want to get rid of those. :lol:
What I do with mine is rename them with a ".old" extension during testing, then once I'm sure the new replacement is working I move them into an archive folder. Keep that main LIBS: folder clean! :D
Which library files should I delete? Do I rename the file I'm keeping as just plain icon.library?
-
The newest version of Peter's icon.library is always on the first page of the thread. I'll link to that page since it sometimes has important information.
http://eab.abime.net/showpost.php?p=814987&postcount=1
AAAAHHHHHH. FML. You know, I'd always look for it on the LAST PAGE. Thinking "last is most recent is newest". I guess my logic just totally fails, in this case. ;)
-
Which library files should I delete? Do I rename the file I'm keeping as just plain icon.library?
Correct. You want the correct one for your processor from @Matthey's link (IconLib_46.4.412.lha (http://eab.abime.net/attachment.php?attachmentid=44969&d=1438714381)), rename it to just "icon.library", and stick it in LIBS:. :)
Edit: you should also get the C: tools from the Aminet version ( Aminet - util/libs/IconLib_46.4.lha (http://aminet.net/package/util/libs/IconLib_46.4) ), as well, and stick those in your C:. You may want to play around with them, they let you do things like make outlined text, or you may not. But doesn't hurt to have them. :)
-
Which library files should I delete?
I recommend keeping icon.library 45.4 (01/24/06) as a backup with a different name. I believe this is the newest official icon.library which came with AmigaOS 3.9. You may have icon.library 40.1 (02/15/93) or similar if you have AmigaOS 3.1 installed. This version is the one in most 3.1 kickstart ROMs.
-
Correct. You want the correct one for your processor from @Matthey's link (IconLib_46.4.412.lha (http://eab.abime.net/attachment.php?attachmentid=44969&d=1438714381)), rename it to just "icon.library", and stick it in LIBS:. :)
There are 3 library files which one will I use? There is icon.lbrary_Lined, icon.library_68000 and icon.library_68020. Will it be the 68020 as I am using an 030 accelerator?
-
There are 3 library files which one will I use? There is icon.lbrary_Lined, icon.library_68000 and icon.library_68020. Will it be the 68020 as I am using an 030 accelerator?
Ding-ding-ding! :lol:
-
After you get that installed, reboot and drop down to a command prompt and give us the output of :
version ram-handler full
version c:makelink full
-
After you get that installed, reboot and drop down to a command prompt and give us the output of :
version ram-handler full
version c:makelink full
This is what I am getting.
-
This is what I am getting.
My AmigaOS 3.9 Amiga gives:
> version ram-handler full
ram-handler 44.24 (12/01/04)
> version c:makelink full
makelink 45.0 (12/24/00)
Hmm.
-
This is what I am getting.
Good sir, you need to update your ram-handler. You're using an old version from 1992, that is no bueno! ;)
-
Good sir, you need to update your ram-handler. You're using an old version from 1992, that is no bueno! ;)
Where would I get a newer version from?
-
Where would I get a newer version from?
It should have been installed as part of your BB updates, however since it sounds like you installed 3.9 on top of 3.1 (rather than a fresh 3.9 install), who knows what old junk you have left in there. One sec, let me see what I can do. Unless @Matthey beats me to it. ;)
-
Where would I get a newer version from?
A recent ram-handler 44.23 is in the AmigaOS 3.9 official BB2 "DEVS:AmigaOS ROM Update". The ram-handler 44.24 should be in the "unofficial" Boing Bag updates as well as elsewhere but this is a kickstart module. There are several ways to patch it in after kickstart is loaded which should have been done in your S:Startup-Sequence if you are using the unofficial Boing Bags. I use Blizkick and my own custom kickstart so I don't need it and can't say specifically what is need.
-
A recent ram-handler 44.23 is in the AmigaOS 3.9 official BB2 "DEVS:AmigaOS ROM Update". The ram-handler 44.24 should be in the "unofficial" Boing Bag updates as well as elsewhere but this is a kickstart module. There are several ways to patch it in after kickstart is loaded which should have been done in your S:Startup-Sequence if you are using the unofficial Boing Bags. I use Blizkick and my own custom kickstart so I don't need it and can't say specifically what is need.
I wouldn't have a clue how to do that :(
-
This page says ram-handler 44.24 is bugged:
http://lilliput.amiga-projects.net/TechDetails.htm
I've always used 44.23 (which is included in the 3.9 ROM updates), but what the heck, I'll try 44.24, and now you can, too. File attached, stick it in your L: and reboot. Save any old versions as ".old", or a backup method of your choice, first! :)
(We may have to revisit your Startup-Sequence again, but try the above, first.)
-
I wouldn't have a clue how to do that :(
If you have the "official" BB2 installed, then this should be done for you by the installation. Check that:
1) you have a file in DEVS: called "AmigaOS ROM Update" which is 321768 bytes
2) there is a SetPatch line in your S:Startup-Sequence and that it is not commented out with a ";"
3) that the Workbench "About..." menu shows Kickstart 45.57
If you are using the "unofficial" Boing Bag updates then everything also should have been installed for you and you need to refer to the documentation for it or have someone who has it installed correctly tell you what files and changes to the S:Startup-Sequence are necessary.
This page says ram-handler 44.24 is bugged:
It would probably be better to stick with ram-handler 44.23 if there is a bug. I didn't notice since the bug is not listed under the "AmigaOS 3.9 bugs" link not that I have had major problems. I'll have to ask Gulliver what the bugs are.
-
Here is another tip. I'm copying this from someone else's thread and just going to boldface the parts that you need to look at now:
C:LoadModule L:FastFileSystem L:Ram-Handler L:Shell-Seg DEVS:scsi.device LIBS:icon.library L:workbench.library NOREBOOT
C:SetPatch SKIPROMMODULES filesystem,ram-handler,shell,scsi.device,icon.library,workbench.library QUIET
In other words, somewhere in your first couple lines you should have the "LoadModule" command. After that somewhere should be "L:Ram-Handler". Likewise, your SetPatch SKIPROMMODULES should be set to skip the version of ram-handler that's in there.
Basically what you're telling your system is to ignore the old version on the ROM and load the new version from L:. Kapish? ;)
-
This page says ram-handler 44.24 is bugged:
http://lilliput.amiga-projects.net/TechDetails.htm
I've always used 44.23 (which is included in the 3.9 ROM updates), but what the heck, I'll try 44.24, and now you can, too. File attached, stick it in your L: and reboot. Save any old versions as ".old", or a backup method of your choice, first! :)
(We may have to revisit your Startup-Sequence again, but try the above, first.)
Ok I have put the new ram-handler into the L: folder renamed the other to .old rebooted my Amiga ran the "version ram-handler full" and I'm still getting version 39.4 so I copied and pasted the original file to another partition and deleted it from L: rebooted and ran the command again and I am still getting 39.4?
-
Here is another tip. I'm copying this from someone else's thread and just going to boldface the parts that you need to look at now:
C:LoadModule L:FastFileSystem L:Ram-Handler L:Shell-Seg DEVS:scsi.device LIBS:icon.library L:workbench.library NOREBOOT
C:SetPatch SKIPROMMODULES filesystem,ram-handler,shell,scsi.device,icon.library,workbench.library QUIET
In other words, somewhere in your first couple lines you should have the "LoadModule" command. After that somewhere should be "L:Ram-Handler". Likewise, your SetPatch SKIPROMMODULES should be set to skip the version of ram-handler that's in there.
Basically what you're telling your system is to ignore the old version on the ROM and load the new version from L:. Kapish? ;)
I will give that a go and report back, I really appreciate all the help.
-
Here is what my s-sequence looks like.
-
It should have been installed as part of your BB updates, however since it sounds like you installed 3.9 on top of 3.1 (rather than a fresh 3.9 install), who knows what old junk you have left in there. One sec, let me see what I can do. Unless @Matthey beats me to it. ;)
My install was a fresh copy using my emergency boot disk. Would doing fresh install of AOS 3.9 and BB 1-4 be a better option?
-
Here is what my s-sequence looks like.
Delete the linefeed after SKIPROMUPDATES. Open the file in Ed or some other text editor, and put that whole command all on one line. You'll have to scroll to the right to see the whole thing, but I think you have a linefeed stuck in there that's breaking the command.
Edit: do the same for the other lines (LoadResident & LoadModule) as well. No linefeeds. :)
Edit 2: added picture.
-
Delete the linefeed after SKIPROMUPDATES. Open the file in Ed or some other text editor, and put that whole command all on one line. You'll have to scroll to the right to see the whole thing, but I think you have a linefeed stuck in there that's breaking the command.
Edit: do the same for the other lines (LoadResident & LoadModule) as well. No linefeeds. :)
Edit 2: added picture.
What are linefeeds? mike I am hopeless at this kind of stuff :( What if you copied and pasted the s-sequence to this thread with the correct stuff on and I can copy and paste it to my Amiga would you be able to do that, that's if you don't mind I would really appreciate it.
TIA
-
What are linefeeds? mike I am hopeless at this kind of stuff :( What if you copied and pasted the s-sequence to this thread with the correct stuff on and I can copy and paste it to my Amiga would you be able to do that, that's if you don't mind I would really appreciate it.
Linefeeds man, carriage returns, don't you remember from using the old typewriters? I'm mixing my terminology a bit, but what you get when you press the enter key. Make your text be all on one line (like in my screenshot) instead of on two lines. I think you've got a break in the command because of that that's causing it to not run correctly.
I could copy & paste but my S-S is going to be different because I use a bunch of Cosmos's libraries, a bunch of extra stuff for my '040, etc. Think of a Startup-Sequence like a finely tuned machine. You wouldn't pull your 302 from your Ford Mustang and stick it in your Chevy Camero, would you? Each needs to be tuned for the specific system it's installed on. And I'll shut up with my car and typewriter analogies now! ;)
-
Like this?
-
Like this?
Looks better. :)
Save it, then load it and check it in Ed, as well.
(from the shell)
ed s:Startup-Sequence
-
Thank you so much the error I was getting is now gone. :)
I was almost gonna do a fresh install sooo.... pleased I didn't lol
-
Thank you so much the error I was getting is now gone. :)
I was almost gonna do a fresh install sooo.... pleased I didn't lol
W00t! Who owes me a beer now? Haha. ;)
To confirm that you're on the latest version, drop down to the command prompt and do that version command again.
And if you want to have some real fun, update all your other libraries/devs/handlers to the latest versions, too. Some of my favorite sites for updates (besides Aminet):
http://lilliput.amiga-projects.net/start.htm
http://amigan.1emu.net/releases/
http://amiga.foul.fr/index.php?p=Work%2FLibs (http://amiga.foul.fr/index.php?p=Work%2FLibs)
Haaaave fun! :D
-
W00t! Who owes me a beer now? Haha. ;)
To confirm that you're on the latest version, drop down to the command prompt and do that version command again.
And if you want to have some real fun, update all your other libraries to the latest versions, too. Some of my favorite sites for updates (besides Aminet):
http://lilliput.amiga-projects.net/start.htm
http://amigan.1emu.net/releases/
http://amiga.foul.fr/index.php?p=Work%2FLibs (http://amiga.foul.fr/index.php?p=Work%2FLibs)
Haaaave fun! :D
I have ran the command and I can confirm it now says 44.24 :)
-
Why do you say so? This is plain wrong. You *require* the SOFT option to make a link from one device to another. Hard links are only possible within one device.
Hmm.. as far as I can see, there's only HARD option. At least on OS3.1, OS3.9, and on MorphOS. Where can you find MakeLink command with SOFT option?
If you try to use SOFT option with 3.1 and MorphOS versions, you get "wrong number of arguments". And with "MakeLink ?" you get "FROM/A,TO/A,HARD/S,FORCE/S:"
Edit: seems to come with some BoingBag update to 3.9... because 3.9 manual still doesn't mention about it either...
-
W00t! Who owes me a beer now? Haha. ;)
I do indeed, if your ever in the UK (in the north east part) I will definitely buy you a beer :)
-
I do indeed, if your ever in the UK (in the north east part) I will definitely buy you a beer :)
It'll be a nuke won't it? They sell that in the USA so just send him a few dollars over. :)
-
It'll be a nuke won't it? They sell that in the USA so just send him a few dollars over. :)
Do I want to know what a "nuke" is? It sounds terrible. On the other hand, ask me what a "soggy buffalo" is. ;)
:pint:
-
Do I want to know what a "nuke" is? It sounds terrible. On the other hand, ask me what a "soggy buffalo" is. ;)
Maybe some kind of shot? A quick search gives a Nuke Waste, Nuke Rainbow, Jager Nuke, Nuclear Waste, Russian Nuke and Nuke bomb. I've never heard of any of them but I'm a beer drinker too. They probably have completely different liquor nomenclature across the pond. Hmm, we better be careful or the NSA may classify Amiga.org as a terrorist site :).
P.S. Nice work on getting carvedeye straightened out.
-
Maybe some kind of shot? A quick search gives a Nuke Waste, Nuke Rainbow, Jager Nuke, Nuclear Waste, Russian Nuke and Nuke bomb. I've never heard of any of them but I'm a beer drinker too. They probably have completely different liquor nomenclature across the pond. Hmm, we better be careful or the NSA may classify Amiga.org as a terrorist site :).
P.S. Nice work on getting carvedeye straightened out.
Thanks! Coming from you that means a lot. :)
I've got to remind my friends all the time not to include comments like "that site is the bomb" in their messages to me. I'm already on enough terrorist watch lists! :lol:
-
(http://www.drinks-of-the-world.de/bilder/newcastle_brown_ale,p-21000007,s-600.jpg)
-
Yum! Great for when the weather gets soggy.
-
@paul1981
Mmm, NewCastle. Good beer. I understand the picture but what did that have to do with a nuke?
-
@paul1981
Mmm, NewCastle. Good beer. I understand the picture but what did that have to do with a nuke?
Must be British slang. "Newcastle" - "Newc" - "Nuke". At least that's what I'm assuming!
At least it's not this! ;)
(http://i.ytimg.com/vi/JzOT1LDhLaM/hqdefault.jpg)
-
Must be British slang. "Newcastle" - "Newc" - "Nuke". At least that's what I'm assuming!
Makes sense now. I would have caught it if he had spelled it "Newc".
At least it's not this! ;)
Is the pic from Persion Gulf Inferno? Fun memories of that game, explosive chages and all :).
-
Being a Geordie I have never heard the term nuke lol
-
Being a Geordie I have never heard the term nuke lol
A Geordie?
(https://ametia.files.wordpress.com/2013/09/star-trek-the-next-generation-levar-burton-0.jpg)
;)