Ok - I have had no response so thought I would add more information;
I have been using an old Toshiba M300 laptop (with docking station which houses the integrated 9 pin RS232 Serial Port) loaded with XP SP3, which has a serial port which I know works just fine (I tested it with an EEPROM programmer which has software that runs in native XP).
I have managed to find the patched PL.EXE file (for XP, by macro/Mike) and have been trying to use that.
I put the 29B into Remote Mode by hitting SELECT, F1, START, START, and then fire up PromLink 6.2 (patched for XP). It runs fine, but when I try to communicate with the programmer, I get a red dialogue box popping up in the Dos Shell window saying the programmer cannot be reached. At this point, strangely, the LEDs on the UniPak2B for 6 & 7 Zif Sockets start to flash??
I built the Serial Cable using the Retroclinic directions here;
http://www.retroclinic.com/leopardcats/dio/dataioserial.htm
My settings for the Programmer and my Serial Port (COM1) are 9600, N, 8, 1
I have tried different variations of serial cable builds, none have worked including an off the shelf NULL Modem cable.
In order to eliminate the laptop as the potential problem, I went into my loft to dig out an old XP PC I had shoved up there a few years back. It was an old Athlon 1.7 Mhz PC with a motherboard sporting integrated Serial and Parallel Ports.
I booted it up, and fired up PromLink connected to my 29B, and was frustrated to see that I had the exact same problem. Red box complaining of no connection and LEDs 6/7 on the UniPak2B flashing.
The only thing I will add, is that I found another chap on KLOV who had the 'exact' same problem as myself. He had built the cable on the retroclinic website but never got it to work. In the end, a standard Serial Modem cable and a Null Modem Adaptor solved his problem.
See below pics of my custom cable I built using the instructions on the retroclinic website. Note that I had stupidly soldered one of the wires to pin 19 on the DB25 connector when it should have gone to pin 20. I should add that correcting this made absolute no difference.
I would really appreciate it if someone could just confirm that my cable is good or rubbish.
I also tried DOSBOX on the laptop, defined the Serial Port as COM1 realport in the configuration (so DOS can access it), mounted the PromLink folder and ran PL.EXE. Unfortunately the results were the same, the Red Dialogue box complaining of no connection and LED's 6 & 7 flashing on the UniPak2B.
I also ran PromLink 3.1 & 3.4 from DOSBOX, and again I was not able to communicate with the 29B.
To say the whole troubleshooting process has been frustrating is an understatement.
Having exhausted all avenues, I decided to dismantle the 29B. At this point, I decided to upgrade the firmware from V04 to V06 - which I did successfully.
I stripped the 29B right down to the motherboard. I have to say it was well put together and easy to dismantle. I also discovered I have the 128k RAM board.
I located the MC1488 and MC1489 ICs used in push/pull configuration to drive the RS232 port right next to the DB25 Serial Port. I desoldered them both from the PCB and was only able to test the MC1489 (tested good) as the MC1488 used non-TTL voltages and my tester did not support it. Therefore, I socketed the board and replaced the MC1488 with a fresh IC.
As you can see, it's not as though I've not tried to resolve this myself.
Ben (Purity) also took the unit away to have a play, as I had my fill of it, and sometimes a second pair of trained eyes helps.
He used Hyper Terminal successfully with the unit, but still could not get PromLink to talk to the 29B.