because my WB is screen of 1600*900!

here my works space:
https://imgur.com/rkIzgnJ.png

Well the NoMMU option seems to be really needed on my setup, otherwise the demo will not finish and I get an Exception. If I specify this when WB is loaded with all the LoadModule and MuTools mumbo jumbo, I get the message:

Ignore causes the screen to remain black and a cold reboot is needed afterwards. WHDLoad runs also fine from the commandline without WB though.

Ah, cheers, that explains it then.

Will check 1.0 now like you suggested in the other post with the mentioned setup that is known to be working all the way to the end.

:lol lol, ok , that makes sense :lol
Here is mine ;)


http://eab.abime.net/zone/My-WB-BoogieTown.zip

Hmm, with the options specified earlier, the demo crashes halfway, but there was no slow down between the various effects (!)

- slave 1.0
- No S-S
- Setpatch
- NoMMU
- PreLoad

Still some red screen glitches here and there, but you already mentioned that is probably part of the code atm ;)

The icon is actually too small on my basic WB 3.1 + NewIcons on my A500 !
Attachment 71386

i will in some days (when i will transfert all new patches on my CFs) on my really A1200 +1230 et 1260 to compare....

indeed for your desktop, my icon is a bit too.... big ;)

Yupp, BIGGEST SIZED, EXTRA LARGEST Icon i have ever seen on AMIGA since 1987 :lol
I remember that the Secret of Monkey island icon was quiet big.
(could i go even more of topic???)

Rocking the WB in SD "Pal Hi-Res" since back in the day :) Sure i had RTG, but nowadays it just feels ...wrong ... feels like a ..might i say it ... a PC ... of even MAC :)

For a little bit protracker here,a little bit a DPaint there, Hardcore Gaming and Demo sessions ...
i stick to classic resolutions :)
But for work...like you do.. for sure, RTG makes total sense.
...still, this is one HUGE ICON ;the biggest i have ever seen :)
i like i tho XD

(sorry again for the total "off topicness") ;)

have you try another 68060.library?

Ps: i think main problem are caused by desynchronization with the music.

the 68060 is too fast.

The music stop from time to time because it awaits an event without already intervened. the slower the CPU, the less the stop is important to be normal on 68000.

I will test different 68060.library +nommu to compare (when i ll have some free time!). If you found good 68060.libray for 1260 send it to me please ;)
pS2: some version of 68060.library need 68040.libray too (same for 60060) if you have doubt look 60060.libray with hex editor and see if there are call to 68040.library

I ran the WHDload version through amibian/amiberry and it glitched out, also when running as an adf. Have it set to AGA and 040 by default and tried no ther configs.

On the other hand, ran like a charm with Amikit on the PC and also my real 1200 both WHD and adfs.

What config are you using? 640 x 256? 8 colors? 16? Some commoditie maybe? And icons name... ;)

I thought of you, see the read-me file here :cheese

:spin That is so sweet of you CFOU! :spin i will test version 1.2 immediately :bowdown

:spin I did some testing and here are the results :spin Tested on Amiga600 Furia :spin

Version 1.1 is still the best for Furia users. (use CACHE toolype)
(just a super smal glitch in the diamond/stern sequene,thats all)

Version 1.2 give me red screens from time to time that stay for a few seconds and short red flashes.
If i use CACHE there is a short glitch in the TEK logo, plus super short sound stutter at some point in the Demo.

So, FURIA users, use version 1.1 with CACHE :great

This is something i would recommend WHDLoad beginnners anyway,
dont think that the newest version of a slave is automaticly "the best"
for youre Setup. Sure, try the newest, but keep the old working one, just in case ;)

Here a few examples :

The newest slave of Elfmania glitches the graphics on Furia badly, no matter the Tooltypes.
So i use a older one that works perfectly on Furia !

Another example. The Immortal is with every Slave other that 1.0 a pretty mess, soundwise on the Furia.
So i use the Immortal 1.0 slave version.

I know that was kind a "offtopic" but i wanted to be sure people do not blindly update there Slaves,
thinking the newer is somehow "better".

Use the Slave that works for YOURE system people and give thanks to creators of those Slaves.

So, thank you :bowdown CFOU! :bowdown , from the bottom of my little heart for youre time and energy you put into those slaves
AND for the neat icon you made, especially for this stupid Torti Guy ;)

:spin Love you style, CFOU! :spin

You must read the ReadMe file red flashes are caused by lost synchronisations as musics pause...

I can't patch it . This demo push hardware limites.
So it's almost impossible to do a version working perfectly on all config by patches..
Perhaps futurs authors patch...

Yeah, i know CFOU!

Maybe this is a good time to introduce people to the concept of ALL WDHLoad slaves are relevant. !!! (use the one that works for you, DONT assume the newest is "the best" for you)

I knew from the beginning that it would be pretty impossible to make one slave for hologon that works on every Amiga Config.

You did an amazing job CFOU! ; with hologon, you had a "tuff Nut to crack" ;)
Thank you so much :bowdown CFOU! :bowdown

tested on my real blizzard 060+1200

nommu needed and some red/blue flash (pb synchro), but it's correct and all demo works

Yes, actually WHDLOAD v1.1 works more fluently (less red flashes) than 1.2 on my A500 + ACA500plus

(whereas floppy version works without flashes)


Thank you CFOU it's much more convenient through WHDLoad ! :great

indeed, there must also be synchronization with the data loading.
The data arrives too fast with the whdlaod patch, but it is almost impossible to synchronize

Have you try both slaves v1.2 with and without fast memory to compare?

I had tried v1.1a fast and regular. But I have just tried the v1.2 from the regular RetroPlay pack "Hologon_v1.2_TheElectronicKnights.lha".
I'll try the "Hologon_v1.2_512k_TheElectronicKnights.lha" after Easter, I guess it's the "fast" version.