The pros and cons of using Putty instead

[DeadDude]

Work in progress, stay tuned!


1. Built-in logging functions of VM software isn't interactive.
2. KDBG is the debugger program's name.
3. KDBG is interactive.
4. Putty auto-names debug files for you with date/time stamps.
5. You probably don't *need* com0com-> use pipes instead (if possible)
6. Putty doesn't 'install'. The exe file is portable. Easy to download and use and delete if not needed anymore.
7. This is the only way to get any debugging information out of certain stages. <- am I correct with that statement? Not entirely- you can use *any* 'terminal' app for this function

Example reason to use Putty:

Trying to install something. The install doesn't 'crash' but unexpectedly closes. The log file may or may not have detailed enough information. If you had Putty up and running, you could see more info.


Work in progress!

[Haos]

Putty is just a serial/ssh terminal. You can use anything else of similar capabilities, even MS Hyperterminal should work. I`m recommending putty due to its portability, capabilities (not only named pipes for vm , but also serial for real hardware debugging) and ability to store a very large amount of data - up to hundreds megabytes of text. Point 7 is then incorrect, alas in 1st stage you will need a terminal app to interact with debugger.

[milon]

Point 7 is then incorrect, alas in 1st stage you will need a terminal app to interact with debugger.

I didn't know this before, and I'm not sure if I understand. Can you explain further / give an example?

[Haos]

Easy to notice. Try getting into debugger in 1st and any later stages, you will quickly see the difference.