|
Notes |
|
|
|
Could you please run with SNOOPOCS MMU COREDUMP options, quit at the black screen and attach the ".whdl*" files? Might need to be SNOOPAGA for Dig Dug 2.
Might reveal something in a custom register that isn't as it should be. |
|
|
|
|
|
Here it goes for Piracy Deluxe... |
|
|
|
|
|
|
|
|
For Piracy Deluxe I can see it is inside WHDL LoadFileDecrunch when you exit. Could you try with PRELOAD as well please?
Also use SNOOPAGA throughout as that lists out all registers. :)
|
|
|
|
|
|
Can do it later with SNOOPAGA as well, but I'm pretty sure PRELOAD was already set on it. |
|
|
|
(0014785)
|
|
Wepl
|
2026-01-07 20:44
(Last edited: 2026-01-07 20:47) |
|
Please set option TRACE.
Run it one time with WHDLoad 19.2 and one time with the latest WHDLoad beta.
Then attach the created file .whdl_trace
|
|
|
|
|
Ok, focusing on Piracy Deluxe for now. PRELOAD was indeed already set.
Dunno if this is expected, but with TRACE enabled, the game doesn't start even with v19 (stays on a black screen, but quitkey works).
Trace file attached, as per requested. |
|
|
|
(0014787)
|
|
Wepl
|
|
2026-01-07 22:23
|
|
Could you please attach your S:WHDLoad-Startup?
Is this v20 the first beta you tried, or did you also try previous v20 beta versions?
That Trace changes the behavior is unexpected and should not happen.
The last beta fixed the ExecuteStartup. Now it waits until finished. |
|
|
|
|
Startup script attached (I indeed use it to stop my network connection), together with the other script referred on it.
I tried earlier v20 betas, and haven't seen issues until this latest one (but haven't necessarily tried the same slaves back then). |
|
|
|
|
|
|
|
(0014790)
|
|
Wepl
|
|
2026-01-07 23:12
|
|
|
Please try the attached WHDLoad. It does not contain the ExecuteStartup fix. |
|
|
|
|
|
|
|
(0014792)
|
|
Wepl
|
|
2026-01-08 09:07
|
|
So there is a problem caused by your ExecuteStartup.
You may check latest v20 and option ExecuteStartup deactivated. |
|
|
|
|
Unfortunately, that indeed was the case.
Disabling completely my network, as well as the startup and cleanup scripts, solved the issues.
But it's a shame that, somehow, it was enough for v19 but not for v20.
I guess network and WHDLoad will never be good pals, after all... |
|
|
|
|
|
Do you have a wait in your script? Possibly some command it is executing is not quite finishing in time before WHDLoad starts? |
|
|
|
|
I tried waiting 5 seconds, but it didn't help.
Will try longer values, just in case... |
|
|
|
(0014796)
|
|
Wepl
|
|
2026-01-08 15:52
|
|
The fix made in last v20 beta is that in v18.9 I broke ExecuteStartup/Cleanup so that it didn't wait anymore to finish the script. Instead it was started async.
Now the old correct behavior is restored that it will wait until finished.
See 0006827
Please try to disable SMB2-Shutdown |
|
|
|
|
Talking in private with DJ Mike, we found the culprit.
Even after issuing a "NetShutdown" command, my PCMCIA network card keeps sending level 2 interrupt signals for the Amiga.
I tried the "CardReset" command from Aminet (with the FORCE argument) after NetShutdown, and now everything works as it should, bar one small detail: as you can see on the CardReset readme, it issues a returncode 5 on this cases, and WHDLoad opens a nag requester about it, before launching the slave.
Is there a way to make WHDLoad ignore it? Sending to >NIL: isn't enough... |
|
|
|
(0014798)
|
|
DJ Mike
|
2026-01-08 17:32
(Last edited: 2026-01-08 17:33) |
|
Presumably WHDL reads the returncode issued by the last command.
It may be enough to run another command after it in the script simply so returncode 0 is set. You could probably even use "SETENV RC 0". I don't 100% remember what the correct approach is here. :)
If the non-zero returncode is causing the script to abort, then try starting your script with "FAILAT 10".
|
|
|
|
|
|
Nice ideas! Will try them later and then report. |
|
|
|
(0014800)
|
|
DJ Mike
|
2026-01-08 17:35
(Last edited: 2026-01-08 17:36) |
|
A WAIT may also be enough since it will presumably return 0.
Just bear in mind: if you've forcibly shut down your network adapter like that, whatever application was still using the device may not be happy after you exit WHDLoad.
|
|
|
|
|
|
My "WHDLoad-Cleanup" script restores the network and SMB2 share after exiting. Used to work pretty well! Let's see... |
|
|
|
|
Using WAIT indeed solved the nag requester.
Thanks a lot for the help, guys, and sorry for opening a ticket that wasn't WHDLoad's fault, after all. |
|
|
|
|
|
You're welcome - glad we could figure it out. :) |
|
PiracyDeluxe.zip (5,173) 2026-01-07 16:40
PiracyDeluxe.whdl_register (2,912) 2026-01-07 20:40