Search the Community
Showing results for tags 'ASCII'.
Found 3 results
Well hello my fellow Atarians. If you're like me you still use the old Atari (either real thing or emulated), but you also use a modern computer like a Windows PC, Linux PC, or Mac. In that case you probably have cause to use text files from one system on the other and visa versa. As some of you know, I developed a program for the A8 to do converting called AAC. You can get info on that over in it's own topic. This new topic is about a different program with the same name that does the same job, but runs natively on the new machines. It is written in Python so has the ability to be cross platform. So here is AAC v0.1, 32-bit Windows, for your testing pleasure. It works fine as expected in every case I have tested so far, but I like to get feedback from others too. Once any bugs (if any) are ironed out. It will get it's v1.0 release. If you need a Linux version to test let me know.
Recently I coded up a program to allow converting ASCII and ATASCII files. The program is command line driven and intended for use under SpartaDOS X (earlier versions may also work). I posted this program in the Sparta DOS 4.47 topic, but am moving it here to its own. I am hoping for testing and feedback. When the program is finally done to the level of performance I am happy with, hopefully it can be made part of the SDX Toolkit. But if not, anyone will be free to add it to their own tools collection as they see fit. So, download it and give it a try if you like. Keep the following program usage in mind because right now, very little user entry validation is performed. It is therefore important that you spell out your device:filename entries. AAC (ASCII ATASCII Converter) is designed to copy a source text file to a destination text file, doing a text translation in the process. Only the output format is specified. It will be assumed the input file will be the opposing type. For example, if an ASCII, (either DOS/Win or Unix) output translation is used, then the input file is assumed to be in ATASCII form. Usage: AAC <source> <dest> /[T|A|U|H] /T = convert to ATASCII /A = convert to ASCII (DOS/Win) /U = convert to ASCII (Unix) /H = this help summary Eg: X AAC.EXE D1:COOLINFO.ASC D2:COOLINFO.TXT /T If using COMEXE you can get by with this: AAC D1:COOLINFO.ASC D2:COOLINFO.TXT /T Download the program.
Hi, in the office, I connect with my WIN7-PC to the BBS. If I use telnet in a CMD, the world is OK (but cannot X-Fer) If I use my preferred SecureCRT, I have this strange character-sets, not showing the nice ASCII-graphics. I already have tried all types of terminal-emulations, like ANSI (Color), VT100, Wyse .... but no gain. Yes, I remember the Ansi.sys from former times, in the Config.sys.... but is that the solution, as it works proper with the windows-given telnet.exe ? Maybe something with my CodePage (CHCP is 850, german windows) ? Any ideas ? Thanks schmitzi