search

larsonmars / sysvars

Setup environment variables that hold system Information to be used for a multi-system startup-sequence
MIT License
8 stars 0 forks source link

Vampire variables are not set. #8

Closed Tallguy298 closed 1 day ago

Tallguy298 commented 2 days ago

Installed your new 0.14 version. Variables - $VampireType, $VampireCoreRev and $VampireClockMult are not set. I am running Workbench 3.2.2, Kickstart 3.2.2 on Amiga MantiCore v4. The previous version 0.13 the variables were set.

This is the output from the SET command. Chipset SAGA CPU 68080 FPU internal KickRev 111 KickVer 47 process 2 RC 0 Result2 0 TotalChipRam 6144 TotalFastRam 499712 TotalSlowRam 1536 VFreq 60 VIEWER MULTIVIEW

Thank you... Alexander.

larsonmars commented 2 days ago

Hi Alexander,

thank you very much for reporting! The only thing I cannot test here... But I think I found it, a simple typo (function is named seVampireEnvVars, instead of setVampireEnvVars...). I'll fix it and post a version for you to test.

Best regards,

Lars

larsonmars commented 2 days ago

Can you please test this?

sysvars.zip

Tallguy298 commented 2 days ago

HI Lars, SET command results... Chipset SAGA CPU 68080 FPU internal KickRev 111 KickVer 47 process 2 RC 0 Result2 0 TotalChipRam 6144 TotalFastRam 499712 TotalRam 507392 TotalSlowRam 1536 VampireClockMult 13 VampireCoreRev 10418 VampireType Unknown VFreq 60 VIEWER MULTIVIEW

My MantiCore v4 card shows as being unknown. It should be type 7 - V4_600.

I changed the register from D2 to D4 from lines 607 to 627, recompiled using VASM and seemed to fix the problem. SET command results... Chipset SAGA CPU 68080 FPU 68882 KickRev 111 KickVer 47 process 2 RC 0 Result2 0 TotalChipRam 6144 TotalFastRam 499712 TotalRam 507392 TotalSlowRam 1536 VampireClockMult 13 VampireCoreRev 10418 VampireType V4_600 VFreq 60 VIEWER MULTIVIEW

Thanks, Alexander.

larsonmars commented 1 day ago

This is the beauty of well-documented open source. You can fix it yourself if the dev makes stupid mistakes.

D4 works, because D0-D3 is actually overwritten by the SET_ENV macro (I should read my own documentation). I will put a comment there to prevent anyone in the future from changing it to any of those registers.

Thanks for spotting, new release underway.