Page 1 of 1

double Libs: assigns -> DSI crash [SOLVED]

Posted: Sun Sep 04, 2011 12:07 am
by marko
I tried to hunt down a "suspected" 3rd-party library that it causing a DSI crash when starting the games Cube and Lugaru... And it turned out none of them is actually causing it :O

Instead there seems to be an issue with my double assigns to Libs: which are causing a DSI crash in Warp3D.

So I have these two drawers, in "SYS:Libs" all the default ones and all others in the "..3rd-Party..":
* SYS:Libs
* Work:3rd-Party-Libs

If I have these lines in my User-Startup, "SYS:Libs" becomes first, and "..3rd-Party.." is added as second to the assign list, the game will start just fine.

Code: Select all

        Assign Libs:     Work:3rd-Party-Libs ADD

;        Assign Libs:	SYS:Libs REMOVE
;        Assign Libs:    SYS:Libs ADD
But, if the "3rd-Party-Libs" drawers becomes first (primary) then it crashes (note: even if the drawer is totally empty) with a DSI crash!

Code: Select all

        Assign Libs:     Work:3rd-Party-Libs ADD

		; ** Reinsert so 3rd-Party becomes first **
        Assign Libs:	SYS:Libs REMOVE
        Assign Libs:    SYS:Libs ADD
Is this Warp3D DSI crash caused by my double assigns a bug, limitation or something else... Can someone reproduce it??

EDIT:

These games started fine with Update 2 but Update 3 caused some issues with the same assign configs.
...and it turned out that I had the Warp3D stuff in the 3rd-Party drawer on the Update 2 installation as well, that's why it worked before ;)

--

This thread is a follow up to the below issue:
http://forum.hyperion-entertainment.biz ... f=17&t=309

My system:
Sam440ep-flex, 800MHz, Radeon 9250, 1GB RAM - AmigaOS 4.1 Update 3

Crashlog:
http://crashlog.os4depot.net/?function= ... hlogid=321

--

Cube:
http://os4depot.net/index.php?function= ... s/cube.lha

Lugaru:
http://os4depot.net/index.php?function= ... ru-bin.lha

EDIT: typos, Lugaru same behavior as Cube, another link, update

Re: double Libs: assigns -> DSI crash in OS4.1u3, Sam440ep-f

Posted: Sun Sep 04, 2011 12:40 am
by nbache
What happens if you change the lines

Code: Select all

        Assign Libs:   SYS:Libs REMOVE
        Assign Libs:    SYS:Libs ADD
to

Code: Select all

        Assign Libs:
        Assign Libs:    Work:3rd-Party-Libs
        Assign Libs:    SYS:Libs ADD
Best regards,

Niels

Re: double Libs: assigns -> DSI crash in OS4.1u3, Sam440ep-f

Posted: Sun Sep 04, 2011 1:09 am
by marko
It still crashes, even if the "..3rd-Party.." drawer is empty :?

Re: double Libs: assigns -> DSI crash in OS4.1u3, Sam440ep-f

Posted: Sun Sep 04, 2011 7:13 am
by xenic
marko wrote:It still crashes, even if the "..3rd-Party.." drawer is empty :?
If you look at the Warp3D.library in a Hex reader you will see that it might be looking for modules in "libs:Warp3D/GFXdrivers/#?" which it won't find if your 3rd-party-libs is assigned ahead of the system
Libs directory. Functions like OpenLibrary() will automatically search the muli-assigns. Other AmigaDOS
functions will only find files in the primary assignment. I'm surprised that this doesn't happen more often
to people who change the order of assignments. It's possible that other programs or libraries that have
files or modules in LIBS: (like xad or amigaInput) could fail if they try to load modules from LIBS:.

Try copying a file that is in a secondary assignment and see what happens. For example, I have a directory
"assign added" to LIBS: and if I try to copy a 3rd party library by entering "copy LIBS:epistula.library TO ram:"
it won't work because that library is not in the primary LIBS: assignment.

Re: double Libs: assigns -> DSI crash in OS4.1u3, Sam440ep-f

Posted: Sun Sep 04, 2011 8:33 pm
by MichaelMerkel
i found several years ago that the warp3d stuff needs to be in the FIRST libs: drawer of the assign chain. i mailed this to (i think ist was) rogue at that time. seems this is still the case? i have not checked.

regards...
michael

Re: double Libs: assigns -> DSI crash in OS4.1u3, Sam440ep-f

Posted: Tue Sep 06, 2011 8:36 pm
by marko
@xenic & MichaelMerkel

Ok, all Warp3D stuff must be in the primary assignment so functions can be find them, otherwise it crashes...

Thanks :)

EDIT: ...and it turned out that I had the Warp3D stuff in the 3rd-Party drawer on the Update 2 installation as well, that's why it worked before ;)