os3.2.1 - iprefs fails with whdload on autostart

[Condor-2-4-2]

Hello,

for a few days I posted and issue on running whdload games under AmigaOS3.2.1 (https://eab.abime.net/showthread.php?t=110899). Since then I did further tests with clean hdf installs of both AmigaOS3.2 and AmigaOS3.2.1. On both clean wb installations I additionally installed only the official whdload18.8 with kickstarts under dev.

In the user-startup scripts of both workbenches I inserted only the following code for the START script:

if exists DH2:START
    cd DH2:
    execute START
 endif

The code for the START script is:

CD DH2:3DGalax
WHDLoad 3DGalax.slave Preload

Now I tested both wb hdf's with 3DGalax (mounted in WinUAE as DH2).

With wb 3.2 the game was loaded on boot whithout errors. But under wb 3.2.1 I got an iprefs error immediatly after the whdload splashscreen delay time was over (see attachment). Nevertheless the game was loaded and worked without problems. But the error stayed in the backround and after closing the game the wb could not fully load.

I also tested many other whdload games and had always the same error. But I found two ways to prevent the error:

- At first by pressing the return key immediatly after splashscreen appears.
- And last by adding "set echo on" before user-startup routine.

Because this specific issue only happens for me on wb 3.2.1 there seems to be a problem with the wb update or the startup-sequence. Has anyone an idea what can cause this issue? I attached both startup-sequence scripts, if that could help.

My system specifications under WinUAE 4.9.1 are:

Kickstart ROM A1200.47.102 / CPU 68020 / cycle exact full / chipset AGA / 2MB Chip RAM / 16MB Z3 Fast RAM /no rtg

[DisasterIncarna]

not sure, but is it normal having IPrefs execute well before your Path entries, user-startup/etc? IPrefs is typically executed near the end not long before LoadWB in most startup-sequences ive seen or used myself.

[Condor-2-4-2]

I changed the loading order of the startup-sequence as follows:

; $VER: Startup-Sequence_HardDrive 47.16 (18.10.2021)
; Startup-Sequence for hard drive systems
;SET ECHO ON
Version exec.library version 47 >NIL:
If Warn
  LoadModule L:System-Startup ROMUPDATE
Else
  Version strap version 47 >NIL:
  If Warn
    LoadModule DOWNGRADE L:Ram-Handler L:Shell-Seg L:System-Startup Libs:dos.library Libs:gadtools.library Libs:graphics.library >NIL:
  EndIf
EndIf
SetPatch >NIL:

;------------------- CPU CheckInstall Section ------------------------

FailAt 31
CPU CHECKINSTALL

SET temp1 $RC

If VAL $temp1 EQ 30
  ECHO ""
  ASK "Press the RETURN key to resume booting into a restricted system."
  Execute S:Startup-failsafe
  QUIT
EndIf

If VAL $temp1 EQ 5
  ECHO ""
  ASK "Press the RETURN key to resume booting."
EndIf

UNSET temp1

;---------------- End of CPU CheckInstall Section --------------------

FailAt 10
Version >NIL:

Assign >nil: EXISTS DF0:
If not warn
  AddBuffers DF0: 15 >NIL:
EndIf

If EXISTS ENVARC:
   MakeLink RAM:ENV to ENVARC: FORCE
Else
   MakeDir RAM:ENV
Endif
MakeDir RAM:T RAM:Clipboards

Resident C:Assign PURE

Assign ENV: RAM:ENV
Assign T: RAM:T
Assign CLIPS: RAM:Clipboards
Assign REXX: S:

FailAt 21
Assign PRINTERS: DEVS:Printers
Assign KEYMAPS: DEVS:Keymaps
Assign LOCALE: SYS:Locale
Assign LIBS: SYS:Classes ADD
Assign HELP: LOCALE:Help DEFER

BindDrivers
Mount DEVS:DOSDrivers/~(#?.info)

LoadMonDrvs >NIL:

FailAt 10
SetEnv Language "english"
SetEnv Workbench $Workbench
SetEnv Kickstart $Kickstart
UnSet Workbench
UnSet Kickstart

stack 40000

IF EXISTS S:User-Startup
  Execute S:User-Startup
EndIF

AddDataTypes REFRESH QUIET
IPrefs
ConClip

If EXISTS SYS:System/RexxMast
  SYS:System/RexxMast >NIL:
EndIF

Path C: SYS:Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:Tools SYS:Tools/Commodities

MakeLink RAM:Disk.info TO ENVARC:Sys/def_RAM.info SOFT

IF EXISTS S:User-Startup2
  Execute S:User-Startup2
EndIF

LoadWB
EndCLI >NIL:

Now the whdload games start without error. I added a second script "User-Startup2" in the place where "User-Startup" was. I use this for games like Genetic Species, because if I load them before iprefs, the game crashes or will not be loaded.

[DisasterIncarna]

ah right, sounds like your doing a sequence select type of thing as part of your startup to do other stuff before a full sequence starts?

I did something like this many, many years ago with my own startup-sequence selector program which runs if i hold my RMB during boot, i can then pick a new startup and start for example programs that dont play well with my normal workbench or they dont like certain patches or need all the memory they can get.

I made this ages ago and lost my code, starting to remake it slowly as theres additions i want as well as modifications, sucks i dont have my original code, but it kinda works in its current state so i still use it till i can remake it.

I do re4call i originally didnt want to remake it as I coulda sworn at some point there was something better on aminet? or some rando 17bit/almathera CD i had ages ago and now I just cant remember/find the alternative so im back to just doing it myself.

Heres a copy of my OS 3.2.x startup, which shows how i kinda do it with my boot selection program and the normal stuff needed in the correct order for various patches to work together (birdie/VP/etc).

[Condor-2-4-2]

Yes, this is what I wanted, but with different start scripts which are loaded on different lines in the startup-sequence order. In my case, "user-startup" executes "START" for whdload games and "user-startup2" executes "START2" script for games like Genetic Species. So for each game I have a separate folder with its corresponding start script and WinUAE config file.

You wondered why the user-startup execution came after iprefs in my startup-sequence. This is the startup-sequence as it was setup by the wb installer after clean installation.

Your boot selector is a interesting solution, but it requires a manually startup selection. But I prefer the games to load automatically with the right startup script.

Thank you for posting your startup-sequence. Perhaps your sequence could help me to enhance my own.

[DisasterIncarna]

Making progress on my updated startup-sequence selector, I made the mistake of building certain functions into the original program, then when i lost the code i kinda forgot how some stuff worked, so now im making it more open ended and letting it use various config/script files which it just runs

It just means things like my buttons to boot a CD32 game will run a script which can be edited/fixed/expanded upon instead of baking all that into the program which would need a recompile for any minor change.

Kinda glad this thread came up so i could revisit and update my boot sequence selection program instead of sticking to my old 1/2 working version.