Currently works properly, from thumb drive, on small machine.
I plug it (the thumb drive) into the desktop machine; Pegasus will not execute. I get a message on the screen..
winpm-32.exe has encountered a problem and needs to close. We are sorry for the inconvenience.
... Please tell Microsoft about this problem....
(etc.)
There is a hi-lighted blue link on that error message that says it will provide technical details. Not much help here, but I'll post it anyway just in case...
Error Signature
Event Type: InPageError P1:c000000e P2: 00000000
There was another link that indicated where the error reporting files were temporarily held.
I believe that I was able to get those files with my text editor, and can post them or E-mail them to the developers here if that would be useful; please understand that I have no idea of what this is all about; I'm just doing the best that a clueless newbee knows how to do. The names of the three files are...
--- manifest.txt ---
--- winpm-32.exe.mdmp ---
--- winpm-32.exe.hdmp ---
The first file "manifest.txt" contains what appears to be "almost ascii" text, with a nul (Value 00h) inserted between each regular character. When I removed the nuls, it reads almost like English; "ErrorText" and so on.
The other two files appear to be hex data that is beyond my ability to guess with simple cursory observation.
I suppose I could post the first one here. I think it's 19 lines long.
Anyway, if this helps anyone, let me know and I'll e-mail it to you.
For the moment, Pegasus on the thumb drive works on the small machine, but not the desktop.
<p>Currently works properly, from thumb drive, on small machine.</p><p>I plug it (the thumb drive) into the desktop machine; Pegasus will not execute. &nbsp;I get a message on the screen..</p><p>
</p><p><blockquote><em>winpm-32.exe has encountered a problem and needs to close. We are sorry for the inconvenience.&nbsp;</em></blockquote><p></p><p><blockquote><em>... Please tell Microsoft about this problem....</em></blockquote><p><blockquote><em>(etc.)</em></blockquote><p></p><p>
</p><p>There is a hi-lighted blue link on that error message that says it will provide technical details. Not much help here, but I'll post it anyway just in case...</p><p>
</p><p><blockquote><em>Error Signature</em></blockquote><p><blockquote><em>Event Type: InPageError &nbsp;P1:c000000e &nbsp; P2: 00000000</em></blockquote><p></p><p><blockquote><em>
</em></blockquote><p>
</p><p>There was another link that indicated where the error reporting files were temporarily held.</p><p>I believe that I was able to get those files with my text editor, and can post them or E-mail them to the developers here if that would be useful; please understand that I have no idea of what this is all about; I'm just doing the best that a clueless newbee knows how to do. &nbsp;The names of the three files are...</p><p><blockquote>--- manifest.txt ---</blockquote><p></p><p><blockquote>--- winpm-32.exe.mdmp ---
</blockquote><p><blockquote><p>--- winpm-32.exe.hdmp ---</p></blockquote><p>The first file "manifest.txt" contains what appears to be "almost ascii" text, with a nul (Value 00h) inserted between each regular character. When I removed the nuls, it reads almost like English; "ErrorText" and so on.</p><p>The other two files appear to be hex data that is beyond my ability to guess with simple cursory observation.</p><p>I suppose I could post the first one here. I think it's 19 lines long.</p><p>Anyway, if this helps anyone, let me know and I'll e-mail it to you.</p><p>For the moment, Pegasus on the thumb drive works on the small machine, but not the desktop.</p><p></p>