P96 Piccolo64SD and WHDLoad

[Fieldday]

Hi,
I have used a SD64 with Picasso 2.1 and WHDload over years without such a problem. If you use an USB or network card you have to disable there stacks before running WHdload. Look at s/whdload.prefs if ExecuteStartup and ExecuteCleanup is set. Otherwise remove all cards and test again if this makes any differences.

Best regards

FD

 

[Xanxi]

Hi,
I have used a SD64 with Picasso 2.1 and WHDload over years without such a problem. If you use an USB or network card you have to disable there stacks before running WHdload. Look at s/whdload.prefs if ExecuteStartup and ExecuteCleanup is set. Otherwise remove all cards and test again if this makes any differences.

Best regards

FD

Thanks for the advice, but this has already been checked and overchecked in my case.

This is definitly related to Picasso96 and Google finds several people reporting the same things over the years. Why some do and some don't? Maybe Wepl can help here about the technics of kickemu.

 

[CrashMidnick]

Very strange, I have 5 systems under P96 (Picasso II, Picasso IV, CV64/A2k, A3K, A4K...) and no problem at all ! Everything is working fine. Could it be something related to Fblit/Ftext or something else in your startup/user sequences ??

I am using Picasso 2.1b with standard install (no tooltype changed). Is P96 installed on a real Amiga (not under WinUAE) ? Did you extract the main LHA on a real Amiga to avoid any corrupt data ? Do you have overclocked accelerators ? If you unattached the board from Picasso screenmodes, what happens ?

 

[Xanxi]

Hi Crash.

No FBlit in this miggy.
You can have a look at my original thread and see my Sherlock Holmes step by step investigation until i found the solution in this thread https://www.amibay.com/showthread.php?t=23459

It seems that the monitor tooltypes in the standard installation are not at all the same for the Spectrum, the C64 3D and even the Pixel64 (i always keep a backup of the partitions of my previous working systems and i have checked that).

No overclock here. I don't share the taste of Cosmos for overclocking, i prefer stability.

 

[CrashMidnick]

Xanxi,

Gimme your email address by PM, I will send you something to make a test.

 

[Wepl]

does this spectrum card add an interrupt?
you can use scout to check (use print and paste here).

 

[Xanxi]

Glad you got that figured. If there's a solution I'd love to hear about it!


Sent from my iPhone using Tapatalk

Solution for me, and possibly for you as well, is here on page 4
https://www.amibay.com/showthread.php?t=23459&page=4

 

[slk486]

Thanks for heads up Xanxi! So you basically went with an older driver?

 

[Xanxi]

Thanks for heads up Xanxi! So you basically went with an older driver?

Indeed. It might be the same for your board, with the interrupt problem with kickemu.

 

[slk486]

I'll try that


Sent from my iPhone using Tapatalk

 

[slk486]

Turns out there were a few issues with my mobo, which is currently with Bad_Ad84. I'm hoping there's a chance the recap and fixes will fix my PiccoloSD64 vs. WHDload issues also

 

[Xanxi]

Unlikely, as we have identified the problem with kickemu and the interrupt in the P96 drive of some boards.
I am too looking for another suitable board for my A2000 to clear the problem. It's not easy to find a nice board with integrated switch like my Spectrum. Downgrading to an older version of the P96 driver without interrupt solved my WHDLOAD problem but causes issues with Shapeshifter.

 

[OoZic]

Old thread, I know, but maybe this info can be helpfull

My setup:

A2000 rev. 6.2
2mb chip with MegaChip
Blizzard 2060 with SCSI and 128mb ram
Indivision
Piccolo SD64 4mb

I use OS 3.9 with BB2

The SD64 test program (for bus errors) has run for over an hour and counter was above 5000. No problems.

With CGX4 (+latest update) system runs fine, but as soon as I use a blanker (from Amiga OS or my favorite CGXblanker) system crashes within the hour. But WHDLoad works when I use the tooltype NOAUTOVEC. Running a demo from WHDLoad for over 8 hours is no problem.

With P96 (2.0+) there is no way I can get WHDLoad to run any demo (I use the 9Finger demo to test) normally. The 9Finger demo shows the intro picture, but hangs after showing this intro pic. F10 doesn't work and system hangs. All kind of tooltypes (like NOAUTOVEC, NOMMU etc.) won't help to fix the problem.

After reading this thread (thanks for the info) I decided to try P96 1.25 from Aminet to see if the INT is also the problem. CGXBlanker does not work yet, but the Amiga OS blanker has run all night without crashing, and WHDLoad works also (with also tooltype NOAUTOVEC).

Now only find out what stops CGXBlanker from running, and I am a happy man
For that I will try to use P96 2.0+ with driver from 1.25. I'll let you all know
Update: CGXBlanker is running for over an hour now with updated P96 software and old driver(s)...

Edit: anybody knows where to find a copy of P96 1.35?

 

[Wepl]

Until now only Spectrum card has been reported to have Problems with WHDLoad under P96.
Version 1.32 of Picasso96 can be found on Aminet CD #23. For Version 1.35 I have no source. Aminet #24 contains 1.36.

 

[OoZic]

Until now only Spectrum card has been reported to have Problems with WHDLoad under P96.
Version 1.32 of Picasso96 can be found on Aminet CD #23. For Version 1.35 I have no source. Aminet #24 contains 1.36.

Thank you for the info @Wepl

I forgot to mention that with CGX4 and CGXBlanker, if I use DPMS to turn off the screen the system won't crash. Only if I leave the screen on (without DPMS) the system crashes within the hour. I was thinking about overheating before I found this thread....
I know it is not P96 or INT related, just to add the info... maybe usefull for other users...

Other thing I tried with P96 and 2.1 drivers is when I start the system without the Picco64 driver in devs/monitors WHDLoad runs fine. Do I quit WHDLoad and try to load the Picco64 monitor driver by double cliccking on it, the system crashes also... Normally it loads the driver and I can go to screensettings and change the screen resolution...

Maybe it is A2000 (Zorro-II or buster 3) or Blizzard 2060 related as the Piccolo SD64 has no problem in my A4000 (buster 11) with external scandoubler. But for the A4000 I already have a CV64/3D with scandoubler. If I put the Piccolo64 in the A4000 I have to buy an expensive AGA Indivision as the external scandoubler is normally in use by my CD32... (confusing I know...). The CV64/3D scandoubler also needs hacking to make it fit in the A2000, something I don't like that much with expensive hardware
So best solution is to keep the Piccolo SD64 with the A2000 and the CV64/3D with the A4000...

 

[OoZic]

Until now only Spectrum card has been reported to have Problems with WHDLoad under P96.
Version 1.32 of Picasso96 can be found on Aminet CD #23. For Version 1.35 I have no source. Aminet #24 contains 1.36.

Somehow my CF card got corrupted and had to install OS3.9+BB2 again.... As i was installing anyway, I tried to install P96 1.36 but sadly with the same black screen result as before. Deleted the 1.36 install and went for the P96 1.32 install. This install works

So I really think the SD64 suffers the same problem as the Spectrum with the driver...

 

[Xanxi]

Until now only Spectrum card has been reported to have Problems with WHDLoad under P96.
Version 1.32 of Picasso96 can be found on Aminet CD #23. For Version 1.35 I have no source. Aminet #24 contains 1.36.

Somehow my CF card got corrupted and had to install OS3.9+BB2 again.... As i was installing anyway, I tried to install P96 1.36 but sadly with the same black screen result as before. Deleted the 1.36 install and went for the P96 1.32 install. This install works

So I really think the SD64 suffers the same problem as the Spectrum with the driver...

You mean, i think, the problem only occurs with WHDLOAD games that use the kickemu, the others should work fine.
Indeed that's the same problem.

 

[Wepl]

The latest beta of WHDLoad http://whdload.de/whdload/whd186.lha disables the interrupts and should solve the issues with P96.