Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: arttu80 on March 15, 2021, 07:31:10 PM
-
Hello.
First I would like to know what this utility really is for.
Somehow I have it in my WBStartup directory, but I don't remember installing it (silly me). My setup is this: A4000/KS3.1.4 with 3.1.4.1 upgrade. The reason I ask, is that this utility crashes almost everytime I boot into WB. "Program Failed (error #8000000B)" whatever that is. Otherwise system seems pretty stable. I have X-Surf 100 with USB module in it, also FastATA card and BigRam 256Mb card. I run one 16Gb Cf card in it at the moment.
I tried to briefly google about this utility, but didn't find any useful answer for what it is for, so please enlighten me. Can I try other similar utility in place of this? I understand that this is some kind of directory path assigning tool, am I right? If so, how it is managed?
-
https://aminet.net/package/util/wb/AssignWedge
It handles volume requests supposedly and lets you ASSIIGN them to directories. I am not so sure about how it handles image MOUNTs.
Handy but not indispensable.
EDIT: I had a quick nose in the source code, it makes an unconditional jump to an absolute address early in the code. I don't know if that's all that's wrong with it, could be,
-
It is a very handy tool.
Normally, when a program wants to access a specific drive or disk, it will simply try and the OS looks for it. If it is not found, you get a simple request "please insert Foo: in any drive".
This is mostly useless regarding to hard drives etc.
Say you have Deluxepaint5 on your hdd and you double click on an old picture from a floppy disk that refers to Dpaint3:dpaint the system will request the dpaint3: disk.
Assignwedge changes the request to allow an assign of this dpaint3: to e.g. your Work:gfx/deluxepaint5/ folder for this session.
That picture therefore gets opened with dpaint5.
-
It's a wonderful annoyance killer that is a built in feature on OS4.
-
Hm, it might be included with 3.1.4.1, can't remember. Maybe thats why its crashing. Or it is patched in by MCP or similar.
-
Hm, it might be included with 3.1.4.1, can't remember. Maybe thats why its crashing. Or it is patched in by MCP or similar.
It is NOT included in AmigaOS 3.1.4(.1).
-
O.k. thank you for information on this. So it's such a "clever" program it doesn't need any setup or configuration files, wow.. But still I wonder why this want to crash on me. Is it supposed to be in WBStartup dir?
Or it is patched in by MCP or similar.
And what does that mean? What is MCP?
-
It will be included in 3.2, but in a more "clean" way than it currently is.
Yes, WBStartup is correct place for it.
8000000B suggests something tries to use an FPU that isn't there. Are you sure that AssignWedge is what causes the crashes?
Exactly _when_ does it crash? On bootup?
-
It handles volume requests supposedly and lets you ASSIGN them to directories.
Yes, or mount if there exists a mountlist entry for the volume/dosdriver asked, or deny once, or deny "forever".
I am not so sure about how it handles image MOUNTs.
It doesn't, directly.
You have to use some diskimage.device and above mentioned mountlist entries (DEVS:MountList, DEVS:DOSDrivers/#? or SYS:Storage/DOSDrivers/#?)
EDIT: I had a quick nose in the source code, it makes an unconditional jump to an absolute address early in the code. I don't know if that's all that's wrong with it, could be,
That is just the hack&patch nature of this program, it jumps to that address because that is where it can "wedge" itself in and interfer the "insert blabla" requestors (and it's not really an absolute address is it...)
-
8000000B suggests something tries to use an FPU that isn't there. Are you sure that AssignWedge is what causes the crashes?
Exactly _when_ does it crash? On bootup?
Yes right after I enter wb screen, some seconds later this error message requester pops up (It says Assign Wedge Program failed, blah blah). If I press suspend button I can continue using machine normally. Oddly, sometimes it doesn't crash (quite rarely). FPU is there, because its full 040/25MHz, original to this machine.
Actually as I made several reboots of machine it didn't crash even once, so I must say that this problem occures only on cold boot.
So to make a conclusion, can this be related to 68040.library?
-
Can I try other similar utility in place of this? I understand that this is some kind of directory path assigning tool, am I right? If so, how it is managed?
Best candidate for an alternative would appear to be;-
https://aminet.net/package/util/boot/AssignManager
No guarantees it will work with 3.1.4. But it's fairly new, and does let you point and click to change assigns made on boot (it doesn't intercept "insert volume" messages as far as I can tell).
-
FPU is there, because its full 040/25MHz, original to this machine.
So to make a conclusion, can this be related to 68040.library?
YES!!!
Seriously, without 68040.library, you can expect a lot 8000000B crashes from all kinds of programs that may or may not use the OS buildt in math libraries.
You should consider installing http://aminet.net/package/util/sys/Mu680x0Libs