Following this thread I tried "pd.com -stderr -verbose -noprefs -nogui -noaudio" on my working 0.54 windows 10 system and got errors about no recognized cmdlet. When I use "./pd -stderr -verbose -noprefs -nogui -noaudio" in the Powershell/CMD, without quotes of course, it works and I see the float precision and verbose channels saying 0 channels. Have you tried installing to a different folder like your root? I see your folder structure is a bit different that I'm used to seeing on Win10 maybe from all the multi-boot setup but I doubt that's an issue.
Further note "pd.exe" launches the app fine no luck at all with "pd.com"
Hope the info might help. I can do any other tests here if needed.
Kylee Kennedy
On Mon, Jul 10, 2023 at 9:42 AM Linux ROUEN linux.rouen@free.fr wrote:
Hello Christof,
No chance at all! "pd.com -noaudio" awa "pd.com -stderr -verbose -noprefs -nogui -noaudio" give the same "no result" than all my previous tests with Pd 0.54.0.
For the time being, I'm giving up on my production PC which has a multi-boot 3x GNU/Linux + Windows 10 and will use for Windows another PC which has a working Pd Vanilla 0.52.3 installed (of course, I will not try to update it). In a couple of days, I will reinvestigate my production PC and will try to reinstall first Pd 0.53.2 under Windows 10, as even that is not working for the time being. Fortunately the updated Purr Data 2.19.3 is running like a charm, but without Else and the up-to-date Cyclone 0.7.
Many thanks to All for your contribution. Joseph Gastelais
-----Message d'origine----- De : Pd-list [mailto:pd-list-bounces@lists.iem.at] De la part de Christof Ressi Envoyé : lundi 10 juillet 2023 02:28 À : pd-list@lists.iem.at Objet : Re: [PD] HELP: Pure Data Vanilla v.0.54-0 under Windows 10 22H2 64-bit is not running!
So within a CMD terminal the following commands
- pd.com
- pd.com -stderr -verbose
- pd.com -nogui
- pd.com -noprefs
give the same "no result" for both the installed and the portable
versions
of Pd 0.54.0.
Ok, thanks for testing. So it has nothing to do with the registry or with the gui preferences...
Now, can you also try "pd.com -noaudio"? And also "pd.com -stderr -verbose -noprefs -nogui -noaudio"?
==> Sig[3].Name=Nom du module défaillant = Name of the failing module ==> Sig[3].Value=ntdll.dll
Ah, right I missed that. Unfortunately, the crash report is very vague. To get the actual reason for the crash you would need to run Pd in a debugger...
Christof _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list