Looking for help with strange issue

[Bill E]

A user is trying out my mods version. He runs spacewar48, it runs fine. He turns on ss6, pidp halts. Apparently happens on some other progs that use sense switches. I can't duplicate this on an rpi4, pi5, or linux using the hardware panel, the virtual panel, the browser display, p7simES, or t30dpy. I've even done a complete new install on the pi4 of the operating system (Trixie) and pidp-mods.

Has anyone seen anything like this? Nothing I've changed should have anything to do with

the sense switches.

Thanks, Bill

PS - He does have the regular pidp version on his system, but he did a full install of mds. I do that also, again not had a problem. All I can think is that there is some mismatched binary, but if the prog runs, seems unlikely.

[Bill E]

Really getting frustrated with this one. I just tried a dual install, I can switch back and forth via the install.sh script in either, still can't duplicate the problem.

Help!

Bill

[Whit Turner]

Is he running on a physical panel? I am currently just running in virtual mode on a Pi 5 desktop since I don't have a kit yet. I just installed your pidp1-mods alongside the old pidp-1 software and could not duplicate this; things are working fine, FWIW.

Whit

--
You received this message because you are subscribed to the Google Groups "[PiDP-1]" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pidp-1+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pidp-1/2c0764d4-afc5-4fd6-9bbb-f5ad6bb091a8n%40googlegroups.com.

[Bill E]

Yes, but he also tried it using the virtual panel. I checked the address in spacewar48 that was displayed when the pidp halted, it wasn't anywhere in the program code, but the instruction in the memory buffer was a regular dpy -i 4000, which is executed in many places. It's totally strange and I still haven't been able to duplicate it with any combination of  pi4, panels, single or dual installs, etc. I'd think it was a hardware issue, except he says it happens on another pi4 also. Hmm, weren't there 2 versions of the pi4? Maybe it's the older version? Still doesn't explain why it's happening. Well, I'll keep this as an open bug for now, if someone else sees it, possibly that will give some useful info.

Bill