SysInfo 4.0

[apex]

But I hope this was not the last update?!?! Will there be no bugfixed 4.0 or even a 4.1?

[Geijer]

Originally Posted by chocolate_boy

When can we expect an OS4 compatible release? Hopefully soon!

Don't keep your breath, currently only a "non crashing" fix may be included but with most functionality disabled = almost useless.

Originally Posted by apex

But I hope this was not the last update?!?! Will there be no bugfixed 4.0 or even a 4.1?

Yes, working on it...

[apex]

Originally Posted by Geijer

Yes, working on it...

Thank you

[videofx]

Thanks! Testing on my New 256MB Amiga 4000T today!

[ByteRyder]

Any progress on the update?

Thanks!

[Geijer]

Originally Posted by ByteRyder

Any progress on the update?

Thanks!

My A4000 is currently broken and waiting for parts. I have been working on the 060 parts and validating calculations.
I have also tested some ideas that I want to integrate but that will probably be postponed...

[Michael]

Just wondering how is it going?
The last V4.00 update was nice, but it has a major bug that crashes it and older version too...
The problem is when you have too many devices/partitions (more then 24), then when you enter the drive sub menu you crash instantly and heavily.

[Geijer]

It's progressing slowly, thanks for the bugreport, didn't know that one.

[bubbob42]

Hi,

while you're here - any progress on the "SysInfo & boards.library"-front?

[Geijer]

Originally Posted by bubbob42

Hi,

while you're here - any progress on the "SysInfo & boards.library"-front?

No, have not solved that boards.library uses longer names yet. SysInfo has hardcoded max length...

[jimbob]

Is there an official bug reporting place for this? I think the memory page is reporting incorrect size for some configurations of chip and slow on A500(+)

[Geijer]

The official page is http://sysinfo.d0.se, currently there is no public available bug reporting system but email is preferred.

[bubbob42]

Originally Posted by Geijer

No, have not solved that boards.library uses longer names yet. SysInfo has hardcoded max length...

What's the maxlength for each field in SysInfo?

I could implement a "sysinfo flag" which would make the lib deliver truncated strings. Or you let me have a look at certain parts of a certain source.

[BigFan]

Would be easier to map those long strings into an array or truncating when reading. That can't be much of a problem here.

[Geijer]

The problem is not to make the strings shorter, the problem is if I trunk them they will be to short to look good. I am in the process to redesign the expansion board UI to make it work with longer strings.

[bubbob42]

Originally Posted by Geijer

The problem is not to make the strings shorter, the problem is if I trunk them they will be to short to look good. I am in the process to redesign the expansion board UI to make it work with longer strings.

That'll be the best solution in any case, great!

[SKOLMAN_MWS]

SysInfo natively on MorphOS AGA emulation M68K without JIT

SysInfo 3.24 on MorphOS A1200 PPC 603e 240 MHz
http://www.ppa.pl/graffiti/obrazek/3...a-m68k-bez-jit

SysInfo 4.0 on MorphOS A1200 PPC 603e 240 MHz
http://www.ppa.pl/graffiti/obrazek/3...a-m68k-bez-jit

is there possible turn off test FPU ? I have LC cpu and when is fpu speed test then my Amiga crash guru
thats mean this program is weak ! old AIBB working great and better if AIBB not see FPU then only test CPU speed

[Geijer]

Sorry for the late answere, will add an option to disable FPU tests.

If you have time, I would be glad if you can help me test out other FPU detection methods?

[matthey]

Originally Posted by Geijer

Sorry for the late answer, will add an option to disable FPU tests.

How about "FPU=No" in the icon tooltypes to disable? There could also be FPU=68881, FPU=68882, FPU=68040 and FPU=68060 to override any auto detection. The same goes for CPU and MMU. This would be very similar to AIBB tooltypes by the way.

Originally Posted by Geijer

If you have time, I would be glad if you can help me test out other FPU detection methods?

UWORD cpu_flags = SysBase->AttnFlags;

if (cpu_flags & AFF_68881)
   fpu881 = TRUE;
if (cpu_flags & AFF_FPU40)
   fpu040 = TRUE;

Be careful with being too tricky with the hardware trying to detect the CPU/MMU/FPU. Many programs fail later which try.