My whole reason for needing a terminal program is to capture the printer output from my old Apple IIc. CoolTerm makes it so easy! But... I can view the ASCII as it streams in by clicking the View ASCII button, but to my dismay it won't capture the ASCII. If I view Hex it looks like hieroglyphics, and that is what the capture feature looks like too.
I see there was some talk about ASCII in a previous discussion, but there didn't appear to be a workaround. Is there a plan to make capturing ASCII an option in CoolTerm? Or is there a way to point the stream to another program that can do the translation for me? Any help would be appreciated!
Capture ASCII
-
roger
- Site Admin
- Posts: 558
- Joined: Fri Apr 24, 2009 12:41 am
- Contact:
Re: Capture ASCII
Frank,
is currently not possible to redirect the data stream somewhere else.
When you say ASCII, what do you expect to see? The capture option saves exactly what is received, byte by byte. The result is an ASCII (or plain text) file. I'm not sure I understand what the issue is.
is currently not possible to redirect the data stream somewhere else.
When you say ASCII, what do you expect to see? The capture option saves exactly what is received, byte by byte. The result is an ASCII (or plain text) file. I'm not sure I understand what the issue is.
-
Frank S
- Posts: 2
- Joined: Thu Jan 12, 2012 7:27 am
Re: Capture ASCII
Hi Roger,
With CoolTerm I was able to SEE the data coming in, but I couldn't capture it. I can see the data by clicking View ASCII, and it looks like this "D5AAADBDAB97B39DCDB7FDE6B4F6AEA7E6B3DE9A97..." This is data coming in from the Apple IIc, and I'm doing a printer dump of the bit pattern on the floppy through a program called Copy II Plus. So the bits coming in would be much longer of course, with D5AA being 1101010110101010 etc. But with CoolTerm if I View Hex, it looks like hieroglyphics, and no matter what mode I view the data stream in, when I go to capture the data it only captures hieroglyphics. I'd paste it here, but I'm not sure how it would transmit and display, but it looks like some form of Arabic. After I posted this I finally was able to get what I needed by using ZTerm, because it would capture the data stream properly, but it's not as easy to use as your program.
So I suppose what I'm requesting is that whatever you do by clicking the View ASCII and View Hex button, cause that result to be capturable.
With CoolTerm I was able to SEE the data coming in, but I couldn't capture it. I can see the data by clicking View ASCII, and it looks like this "D5AAADBDAB97B39DCDB7FDE6B4F6AEA7E6B3DE9A97..." This is data coming in from the Apple IIc, and I'm doing a printer dump of the bit pattern on the floppy through a program called Copy II Plus. So the bits coming in would be much longer of course, with D5AA being 1101010110101010 etc. But with CoolTerm if I View Hex, it looks like hieroglyphics, and no matter what mode I view the data stream in, when I go to capture the data it only captures hieroglyphics. I'd paste it here, but I'm not sure how it would transmit and display, but it looks like some form of Arabic. After I posted this I finally was able to get what I needed by using ZTerm, because it would capture the data stream properly, but it's not as easy to use as your program.
So I suppose what I'm requesting is that whatever you do by clicking the View ASCII and View Hex button, cause that result to be capturable.
-
roger
- Site Admin
- Posts: 558
- Joined: Fri Apr 24, 2009 12:41 am
- Contact:
Re: Capture ASCII
Frank,
The "D5AAADBDAB97B39DCDB7FDE6B4F6AEA7E6B3DE9A97..." is actually the hex view, i.e. each received byte is displayed as it's hexadecimal representation. This is the view with the white/light blue alternating lines, with 16 bytes on each line. The other view (ASCII, or plain text) displays the characters that represent each byte. In order to view the hex representation of the captured data, you will need to use a Hex Viewer or Hex Editor application, such as WinHex for Windows or 0xED for the Mac:
http://www.winhex.com/winhex/
http://www.suavetech.com/0xed/0xed.html
While capturing, CoolTerm closes the capture file between writes, i.e. it is possible to have it open in another application while CoolTerm is capturing. If you can get the hex viewer to refresh the contents when the file changes you would essentially have a real-time updating hex view in another application.
Alternatively, if you're on a Mac, you can used AppleScript to control CoolTerm which would allow you to receive data via the Script. The API I created also includes a function to convert plain text to hex. You can then pass the data on to another application (such as the OSX text editor) in hex format.
The "D5AAADBDAB97B39DCDB7FDE6B4F6AEA7E6B3DE9A97..." is actually the hex view, i.e. each received byte is displayed as it's hexadecimal representation. This is the view with the white/light blue alternating lines, with 16 bytes on each line. The other view (ASCII, or plain text) displays the characters that represent each byte. In order to view the hex representation of the captured data, you will need to use a Hex Viewer or Hex Editor application, such as WinHex for Windows or 0xED for the Mac:
http://www.winhex.com/winhex/
http://www.suavetech.com/0xed/0xed.html
While capturing, CoolTerm closes the capture file between writes, i.e. it is possible to have it open in another application while CoolTerm is capturing. If you can get the hex viewer to refresh the contents when the file changes you would essentially have a real-time updating hex view in another application.
Alternatively, if you're on a Mac, you can used AppleScript to control CoolTerm which would allow you to receive data via the Script. The API I created also includes a function to convert plain text to hex. You can then pass the data on to another application (such as the OSX text editor) in hex format.