SetCPU and Startup-Sequence

[orcish75]

Hi Everyone,

I have an A500 with a VXL-30 25MHZ 68030 accelerator card with 8MB 32-bit RAM set to high (Not in 24-bit space). I'm running Workbench 3.1 with a 3.1 ROM installed. I'm trying to set my Startup-Sequence (SS) to detect the type of CPU and run a couple of programs if the '030 is detected. If the 68000 is detected, I want the SS to procede as normal.

The SS looks like this:

C:SetCPU CHECK 68000
If WARN:
             C:RomTagMEM -D 8000000 800000 5 5
             C:SetCPU cache burst fastrom
Else
EndIF

This works and executes no problem, however a bunch of "Intuition is attempting to reset the Workbench screen. Please close all windows, except drawers." errors pop up before the WB screen is shown. I have tried the Run >NIL: C:SetCPU CHECK 68000 option to prevent the Intuition errors, but when I do this, the If statement doesn't run.

Is there a different CPU checking program that won't bring up the Intuition errors or be able to run with the Run >NIL: option?

I realise this isn't anything major, but the Intuition errors are annoying and it add a couple of seconds onto the boot-up time.

[Bamiga2002]

Instead of "Run C:SetCPU >NIL:" try just "C:SetCPU >NIL:"

[orcish75]

Excellent, thanks for that. I'll test it when I get home tonight and let you know how it goes.

Cheers!

[Jope]

No colon after "warn", "else" can be removed.

With the regular Commodore supplied cpu command, you must check for a higher cpu and then negate the test. Dunno about setcpu.

Something like:

C:Cpu >nil: check 68030
If NOT WARN
  echo "We're running a '030"
EndIf

[orcish75]

Instead of "Run C:SetCPU >NIL:" try just "C:SetCPU >NIL:"

That solved my problem perfectly. No longer has the Intuition error and it runs the If statement correctly now.

No colon after "warn", "else" can be removed.

Thanks for the extra tip, makes my SS that much smaller!

I tried the Commodore supplied CPU command as per your example and it works exactly the same as SetCPU in my SS. My A500 is working like a dream now!

Thanks for your help guys, it's really appreciated!

[Zac67]

Run spawns a separate task/environment which runs asynchronously and therefore cannot return any values to the script.

[orcish75]

Run spawns a separate task/environment which runs asynchronously and therefore cannot return any values to the script.

Ah, OK! That makes sense. Thanks for the heads up.

Cheers