PS TOOLS bug

[ChipB]

I use PSTOOLS alot for admin work on computers. My post is about specifically PSLIST which I use to check running processes remotely which now generates an error since XPizeing my pc. I prefer it over TASKLIST and would like to get the PSLIST functionality working. It works for local PC but a command like:

PSLIST \\PCNAME

generates a "instruction at xxx referenced memory at xxxx. It could not be read" error.

Any advice?

[XPero]

I use PSTOOLS alot for admin work on computers. My post is about specifically PSLIST which I use to check running processes remotely which now generates an error since XPizeing my pc.  I prefer it over TASKLIST and would like to get the PSLIST functionality working.  It works for local PC but a command like:

PSLIST \\PCNAME

generates a "instruction at xxx referenced memory at xxxx.  It could not be read" error.

Any advice?

<{POST_SNAPBACK}>

Gonna check what dll is causing this.

EDIT: I cannot reproduce the error. I cannot use the PSLIST \\PCNAME because there is no more PCs here, main command works without exception errors. I would recommend you uninstalling cmd.exe from XPize uninstaller. Reboot and try again.

Edited September 22, 2005 by XPero