Sorry for asking what is probably a silly question, but searching the forum and the FAQ hasn't revealed an answer. I'm attempting to upload new firmware to a BW Mk2 Touchscreen (5000CT2). I'm using a windows XP laptop, connected to the screen via a USB cable into the programming port. I was able to get a connection one time, long enough to download the project into PICED. I then hit the reset button with a paperclip (through the paper seal). The screen went black, and since then I've been unable to get a connection. Here are the steps I've taken to try to get a connection: I uninstalled everything (not realising it would delete the project), including PICED, the toolkit, the USB driver thing, etc. I have the latest (downloaded today) versions of PICED and the toolkit installed, including telling it to force the USB driver installation. The install worked fine as far as I can tell. When I connect the USB cable, the laptop detects new hardware and installs the 5000CT2 driver, and sets up a COM port (COM8), which I can see through device manager. When I launch PICED, tell it to start a new project, then attempt to connect to the screen, I tell it to use COM8. In the log I can see 8 or so Tx attempts, but no replies from the screen. Attempting to "recover" the screen gives me an immediate failure. I assume the cable etc is fine, as the screen itself is detected every time I remove it and reconnect it. It is a cable I've used to connect to a printer with no issues. It does prompt me to install the device drivers for the screen every time, which seems wierd, but the install always seems to work fine. I've gone into device manager and changed the COM port in the advanced settings to COM10, and changed it in PICED, and still no connection. I note that the USB port seems to be set to 9600 baud, and the default setting in PICED is to connect at 38xxx - I've tried leaving both at default, or setting both at the same, and it hasn't helped so far. I'm sort of at wits end - I've fiddled with it as much as I can stand right now. I'm hoping someone has had the same problem, or can point me to a definitive checklist of settings to try. Thanks.