resload_control error

HymnsomniaK · 24 June 2006, 21:39

Some WHDLoad installed games quit with this error.

Function 'resload_Control' called with unacceptable arguments

Any idea what it means? thank you

Codetapper · 24 June 2006, 22:10

It might help if you named a few games where this error occurred and preferably attach the .whdload_log file

HymnsomniaK · 24 June 2006, 22:30

I am currently going through my installed games to see how many/which cause that error. Does the MAKE COREDUMP option create the log file you talk about or do I have to do something else? I'm using WHDLoad(registered) for about 1 day so I don't know that much about it.

Codetapper · 24 June 2006, 23:20

Yep. I prefer to edit the .whdload_prefs file (in your s: dir) to point the coredumps to T: rather than the default of c: in case anything goes wrong while it writes the dumpfiles. The file will be in wherever you have set COREDUMPPATH to.

HymnsomniaK · 25 June 2006, 01:48

Even though COREDUMPPATH is T: it still dumps it on c: , do I have to set it as a tooltype in the slave? -> I have resolved this issue , I can now dump on t:

In c: i've got 3 files - .whdl_dump - .whdl_memory - .whdl_register -
You need all 3 or just 1? -> I know now you need all 3

I'll just dump those that gimme trouble and post here again.

HymnsomniaK · 25 June 2006, 02:20

Ok , here they are.

I'm using the latest WHDLoad official release 16.6

Codetapper · 25 June 2006, 02:45

Only the log file is generally needed as that has the status of the memory of the Amiga when it crashed. On PCs memory dumps are quite useless as nobody knows assembler whereas the WHDLoad guys can usually work out what caused a problem from the log.

HymnsomniaK · 25 June 2006, 04:08

I've included all 3 anyway , it's only bad if you are low on disk space.

Thanks for taking the time to look into this.

Wepl · 25 June 2006, 11:44

Quote:

Originally Posted by HymnsomniaK

Some WHDLoad installed games quit with this error.

Function 'resload_Control' called with unacceptable arguments

Any idea what it means? thank you

the reason could be an not actual WHDLoad version. Do you haave running the latest 16.6?

Wepl · 25 June 2006, 11:59

I have checked Stardust and at least here it is an incorrect terminated taglist. This install needs to be updated. WHDLoad 16.6 is more exact in checking the taglists therefore this errors doesn't occure with older WHDLoad's.

HymnsomniaK · 25 June 2006, 12:38

[quote=I'm using the latest WHDLoad official release 16.6[/quote]

You're absolutely right! I know this because I have WHDLoad 15 in WinUAE and Arabian Nights runs fine.
So it's an installer needing an update then? I'll keep checking the WHDLoad page for it. Thanks

Wepl · 25 June 2006, 17:24

I think all of these installs have an unsufficient terminated taglist and therefore must be updated.
I've updated SinkOrSwim and Stardust. Others should follow.
If you find more installs please use the bugreport form on the whdload page to report them!
Authors do not read these pages usually.

HymnsomniaK · 26 June 2006, 02:27

Quote:

Originally Posted by Wepl

If you find more installs please use the bugreport form on the whdload page to report them!
Authors do not read these pages usually.

I'm sorry but when I started this thread I didn't think it was for bug report , I just wanted to know if I had to change any tooltypes for it to work on my setup. It turned out to be a bug so I'll report properly any others I find.

CFou! · 26 June 2006, 13:06

Quote:

Originally Posted by HymnsomniaK

I'm sorry but when I started this thread I didn't think it was for bug report , I just wanted to know if I had to change any tooltypes for it to work on my setup. It turned out to be a bug so I'll report properly any others I find.

I will update soon 1943 & Arabian Nights (if i found source code from Mike/Bored Seal)

CFou! · 30 June 2006, 17:13

Quote:

Originally Posted by CFOU!

I will update soon 1943 & Arabian Nights (if i found source code from Mike/Bored Seal)

it's fixed but AMC/AstroMarineCorps have the same problem

Retro-Nerd · 30 June 2006, 17:57

Darkmere has the same resload error. I wrote a bug report to MiCK some days ago.

CFou! · 03 July 2006, 17:32

Quote:

Originally Posted by Retro-Nerd

Darkmere has the same resload error. I wrote a bug report to MiCK some days ago.

WEPL is fixing Darkmere and me Curse of enchantia & Krusty fun house

Retro-Nerd · 03 July 2006, 18:10

Quote:

Originally Posted by CFOU!

WEPL is fixing Darkmere and me Curse of enchantia & Krusty fun house

Yes, i saw the Darkmere update on the WHDLoad site. Thanks for fixing Curse of enchantia & Krusty.

killergorilla · 03 July 2006, 18:31

Just thought I'd let you know Chaos Engine AGA has the same error, I posted a bug report to JOTD a few days ago

(The CD32 version also quits with an "illegal instruction" message which I have also included info in the bug report)

Peter · 05 January 2007, 00:15

Does anyone know if Darkmere was fixed as I downloaded it today from Amiga Magix and tried to run it under WHDLoad 16.6 (registered) and I get the error as mentioned above - also with Cannon Fodder 2 and Chaos engine AGA - I will report the bugs but I wondered if anyone had heard any news?

24 June 2006, 21:39	#1
HymnsomniaK Onezay Riendfay Join Date: Apr 2006 Location: Portugal Age: 45 Posts: 119	resload_control error Some WHDLoad installed games quit with this error. Function 'resload_Control' called with unacceptable arguments Any idea what it means? thank you

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
WHDLoad error: error during 'resload_LoadKick' on monkey island & others	jamespstevenson	project.GameBase Amiga	14	20 February 2014 05:33
ERROR: Gunshoot (resload_Control)	killergorilla	project.Killergorilla's WHD packs	5	18 December 2012 13:06
ERROR: Metal Masters (Illegal Instruction / Address Error / Black Screen)	killergorilla	project.Killergorilla's WHD packs	7	25 March 2012 15:32
FIXED: Baby Jo in 'Going Home' (resload_Control)	killergorilla	project.Killergorilla's WHD packs	3	26 September 2007 18:19
ERROR: Arena (Psygnosis) (resload_control error)	killergorilla	project.Killergorilla's WHD packs	5	25 September 2007 17:39

24 June 2006, 22:10	#2
Codetapper 2 contact me: email only! Join Date: May 2001 Location: Auckland / New Zealand Posts: 3,187	It might help if you named a few games where this error occurred and preferably attach the .whdload_log file

24 June 2006, 22:30	#3
HymnsomniaK Onezay Riendfay Join Date: Apr 2006 Location: Portugal Age: 45 Posts: 119	I am currently going through my installed games to see how many/which cause that error. Does the MAKE COREDUMP option create the log file you talk about or do I have to do something else? I'm using WHDLoad(registered) for about 1 day so I don't know that much about it.

24 June 2006, 23:20	#4
Codetapper 2 contact me: email only! Join Date: May 2001 Location: Auckland / New Zealand Posts: 3,187	Yep. I prefer to edit the .whdload_prefs file (in your s: dir) to point the coredumps to T: rather than the default of c: in case anything goes wrong while it writes the dumpfiles. The file will be in wherever you have set COREDUMPPATH to.

25 June 2006, 01:48	#5
HymnsomniaK Onezay Riendfay Join Date: Apr 2006 Location: Portugal Age: 45 Posts: 119	Even though COREDUMPPATH is T: it still dumps it on c: , do I have to set it as a tooltype in the slave? -> I have resolved this issue , I can now dump on t: In c: i've got 3 files - .whdl_dump - .whdl_memory - .whdl_register - You need all 3 or just 1? -> I know now you need all 3 I'll just dump those that gimme trouble and post here again.

25 June 2006, 02:45	#7
Codetapper 2 contact me: email only! Join Date: May 2001 Location: Auckland / New Zealand Posts: 3,187	Only the log file is generally needed as that has the status of the memory of the Amiga when it crashed. On PCs memory dumps are quite useless as nobody knows assembler whereas the WHDLoad guys can usually work out what caused a problem from the log.

25 June 2006, 04:08	#8
HymnsomniaK Onezay Riendfay Join Date: Apr 2006 Location: Portugal Age: 45 Posts: 119	I've included all 3 anyway , it's only bad if you are low on disk space. Thanks for taking the time to look into this.

25 June 2006, 11:59	#10
Wepl Moderator Join Date: Nov 2001 Location: Germany Posts: 869	I have checked Stardust and at least here it is an incorrect terminated taglist. This install needs to be updated. WHDLoad 16.6 is more exact in checking the taglists therefore this errors doesn't occure with older WHDLoad's.

25 June 2006, 12:38	#11
HymnsomniaK Onezay Riendfay Join Date: Apr 2006 Location: Portugal Age: 45 Posts: 119	[quote=I'm using the latest WHDLoad official release 16.6[/quote] You're absolutely right! I know this because I have WHDLoad 15 in WinUAE and Arabian Nights runs fine. So it's an installer needing an update then? I'll keep checking the WHDLoad page for it. Thanks

25 June 2006, 17:24	#12
Wepl Moderator Join Date: Nov 2001 Location: Germany Posts: 869	I think all of these installs have an unsufficient terminated taglist and therefore must be updated. I've updated SinkOrSwim and Stardust. Others should follow. If you find more installs please use the bugreport form on the whdload page to report them! Authors do not read these pages usually.

30 June 2006, 17:57	#16
Retro-Nerd Missile Command Champion Join Date: Aug 2005 Location: Germany Age: 52 Posts: 12,453	Darkmere has the same resload error. I wrote a bug report to MiCK some days ago.

03 July 2006, 18:31	#19
killergorilla Lesser Talent Join Date: Jan 2003 Location: UK Age: 42 Posts: 7,957	Just thought I'd let you know Chaos Engine AGA has the same error, I posted a bug report to JOTD a few days ago (The CD32 version also quits with an "illegal instruction" message which I have also included info in the bug report)

05 January 2007, 00:15	#20
Peter Still an Amiga user Join Date: Nov 2006 Location: Kent Age: 55 Posts: 2,715	Does anyone know if Darkmere was fixed as I downloaded it today from Amiga Magix and tried to run it under WHDLoad 16.6 (registered) and I get the error as mentioned above - also with Cannon Fodder 2 and Chaos engine AGA - I will report the bugs but I wondered if anyone had heard any news?

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)