I've not used a PK232 before. I've been using an old AMT-1. There are "well documented" issues around the three wiring standards for the 25-D to 9-D serial connections. I have as most people for this gear do, the EIA232 (25-D) to EIA574 (9-D) cable (that is home-brewed, I didn't get the orig connector). I have two DOS programs, PAMS2 by W5SMM and Pakratt II for DOS. Pams works fine as far as I can tell with the cable I built. After much unsoldering and resoldering I ended up forgetting which combo of pins 3-2 and 2-3 for TD and RD I had but currently have 3-2 from DTE (laptop) and 2-3 for the PK232 (DCE) and probably should stick to 4-8 RTS and 5-7 CTS. I've also tried disconnecting the RTS, CTS, DTR and DCD cables completely just sticking to TD & RD. But this doesn't fix my problem Because of the initialisation problems when changing programs, autobaud and all that, I can only use one program PAMS or PAKRATT at any one time. But when I do reinitialise and start PAKRATT I get the BAD message for my COM1 Port. It doesn't seem to function with PAKRATT fully, Sure the software of pakratt accepts some commands but none seem to make it across the RS232 cable to actually make anything happen on the PK232. But all is fine when I use PAMS, which has its own Maibox BIOS software MBBIOS.COM in the program. PAMS auto-configures a MODEM automatically at setup and works just in AMTOR. I need to get access to all the modes of hte PK232 of course, so I'm trying the old PAKRATT II software. Could it be something to do with the PK232MBX firmware? I have version 7.0 and I did just once after hours of trying, get the ROM version readout (status message) on the Laptop. But only once. I can input MYCAL, HBAUD, and other commands but I don't think I am communicating with the PK232MBX using Pakratt. I've tried following the full manual instruction, I have the full manual and have set everything up. When I enter my AAA, setup MYCAL I try to connect using C AAA but eventually get a timed out & DISCONNECTED message. But the give away is the single 'BAD' message I get during initialisation that seems to refer to the COM port, hence the RS232, but as I said this seems to work fine with other software in AMTOR mode. Very confusing. Anybody any experience of this and what I'm most probably doing wrong, if it is me.