tested this tonight on one machine running win7. replacing the pd.dll in the pd/bin folder made pd unable to start....
On May 08, 2010, at 16:38, patko wrote: > I've recently compiled a version of pd-extended > just replacing pd.dll fixes it, it's attached > > ----- "rene beekman" <[email protected]> a écrit : > >> i reported this problem several months ago. >> the suggestion back then was to test nightly builds, which did not >> work at the time. >> more recent nightly builds did not solve this problem either. >> >> it appears on some laptops running vista or windows7, but not all. >> i have so far not been able to recreate this problem on a machine that >> did not have the problem. >> >> has anyone else seen this problem? been able to solve it? >> >> i have several pd courses coming up for which i'm expecting the >> majority of participants to be running windoze - they will be brining >> in their own machines. >> problem is, once into the courses i will not have the time to >> troubleshoot this kind of problem and i dread going into this knowing >> that any machine running vista or windows7 is potentially unstable... >> >> would greatly appreciate help in figuring this out >> >> rene >> >> >> >> On Feb 14, 2010, at 19:23, Hans-Christoph Steiner wrote: >> >>> >>> 1) try a Pd-extended 0.42.5 nightly build >>> >>> 2) try this version with the [multiselect] object removed from the >> "related objects" subpatch >>> >>> <select-help.pd> >>> >>> >>> .hc >>> >>> On Feb 14, 2010, at 7:59 AM, rene beekman wrote: >>> >>>> we're having problems running pd-extended 0.41.4 on vista & >> windows7 >>>> problems seem to be related to several particular objects or >> patches >>>> one example is the select-help patch. opening the help patch either >> via the desktop, or from within pd via the browser or via the context >> menu's 'help' option results in windows closing pd >>>> >>>> the application error log on one particular machine shows this: >>>> >>>> Faulting application pd.exe, version 0.0.0.0, time stamp >> 0x4a277929, faulting module ntdll.dll, version 6.0.6002.18005, time >> stamp 0x49e03821, exception code 0xc0000005, fault offset 0x00041f3c, >> process id 0x1534, application start time 0x01caad6a4a506d60. >>>> >>>> on the windows7 machine, it is the same library that is marked as >> "faulting module", only it's a 6.1 version >>>> >>>> is this a known bug? >>>> any workarounds? >>>> >>>> thanks in advance >>>> >>>> rene >>>> >>>> >>>> _______________________________________________ >>>> [email protected] mailing list >>>> UNSUBSCRIBE and account-management -> >> http://lists.puredata.info/listinfo/pd-list >>> >>> >>> >>> >> ---------------------------------------------------------------------------- >>> >>> "We have nothing to fear from love and commitment." - New York >> Senator Diane Savino, trying to convince the NY Senate to pass a gay >> marriage bill >>> >> >> >> _______________________________________________ >> [email protected] mailing list >> UNSUBSCRIBE and account-management -> >> http://lists.puredata.info/listinfo/pd-list > <pd.dll-win32-6.0.zip> _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
