Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[512k]

Hi,

Was wondering how i would gather information off the system running my program.

For example how do i detect which processor and chipset are currently being used?
What is the code required to garnish this information?

Thanks for reading.

[Hungry Horace]

i am sure AMCAF has some commands for this purpose....

http://www.ultimateamiga.co.uk/HostedProjects/AMOSFactory/AMCAFguide/manual/miscellaneous.html

AGA DETECT
function: check if the computer has aga chipset
flag=Aga Detect

This is a simple function that checks for the existence of the AGA chipset, found in A1200, A4000 and CD³² machines.
It returns -1 (True), if the new chipset is mounted or 0 (False) if the ECS or OCS chipset are still in use.

Note that it does not check for the kickstart version only, so A2000 and A500 machines with kick 3.0 or higher will be detected as non-AGA correctly.
This function is 100% system conform and won't hack the hardware for it's result.
Therefore, if the AGA chipset had been disabled either using the boot menu or the "Setpatch NOAGA" command, it will return that no AGA is available.

CPU
function: return the number of the fitted cpu
chip=Cpu

The cpu function returns the identification number of the central processing unit currently installed your Amiga.
This number can currently lie between 68000 to 68060. Kickstart 1.3 knows only CPUs to the 68020.

FPU
function: return the id number of an coprocessor
chip=Fpu

This function returns the number of an installed mathematic coprocessor or 0, if none is fitted. As before, Kickstart 1.3 only knows the 68881.

On 68040/68060 machines, the cpu contains the fpu, so 68040 or 68060 will be returned instead.

[512k]

Thanks Horace but i am looking for an instruction that gives chipset specifics of all on board chips including versions of said chips such as denise agnus gary etc...

Had a look at the link and there are some useful instructions/Commands but i intend to compile my program and make it a stand alone self booting ADF and as i understand it using amcaf extensions can really bugger that up.

Any chance there is a peek i can use?
Maybe some reference/Address in RAM might be there i can use does anybody know?