hugin-devs team mailing list archive

[Matthew Petroff <692957@xxxxxxxxxxxxxxxxxx>]

I'm not sure what else to try other than recording where Hugin looks for
chcp.

Could you download Process Monitor from:
http://technet.microsoft.com/en-us/sysinternals/bb896645

Then use the following procedure:

1. Save this attachment

2. Open Hugin and have it ready to stitch

3. Open Process Monitor (procmon.exe)

4. In procmon: "File --> Import Configuration..." then select the
attachment

5. Try to stitch with Hugin.

6. In procmon: "File --> Capture Events" to stop the event tracer

7. In procmon: "File --> Save..." the default options are fine

8. Add the resulting log file to this bug report.

The log file will contain all attempts to access chcp and where those
attempts were.

** Attachment added: "ProcmonConfiguration-chcp.pmc"
   https://bugs.launchpad.net/hugin/+bug/692957/+attachment/1779259/+files/ProcmonConfiguration-chcp.pmc

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/692957

Title:
  Windows: can't find chcp command

Status in Hugin - Panorama Tools GUI:
  Confirmed

Bug description:
  I use Windows 7 64bit. After starting the stitching I receive a message, that the command chcp couldn't be found. Originally in german:  "Der Befehl "chcp" ist entweder falsch geschrieben oder konnte nicht gefunden werden."

I even changed the path variable from "%systemroot%\system32" into "c:\windows\system32", but it didn't help. All other things are working, so It looks like a bug for me.

Thanks for any help.