http://msdn.microsoft.com/en-us/library ... d.60).aspx
I am able to start an instance of cmd.exe and I even get the expected output on the DBGU port:
But it seems to exit immediately. No input from the DBGU port is processed. I am using a simple .NET application to start the process and can see that the HasExited property is true directly after the Process.Start() method call. I have tried playing with the \k argument with no effect. I have also tried adjusting the COMSpeed registry setting with no effect.
Code: Select all
Pocket CMD v 6.00 \>
I have read through the related MSDN articles and seen that this functionality seems to depend on the functions OEMInitDebugSerial, OEMWriteDebugByte, OEMWriteDebugString, OEMReadDebugByte, and OEMClearDebugCommError. I added stubs for the OEMWriteDebugString and OEMClearDebugCommError functions also with no effect. The other functions are all implemented and seem appropriate. They are shared with EBoot and seem to work input and output in that case.
It seems like either I am missing a setting somewhere (perhaps a catalog option) or the OEM implementation is missing something necessary for this to work. I am at a loss as how to continue as the Process.Start() method throws no exceptions and the ExitCode property is 0.
Any guidance would be appreciated; many thanks.