I test the Windows versions and did not find the CTRL-C problem.

So I think the OP has a hardware problem.

Regards,
Xiaofan


Detail test on Windows XP SP2.
1) Programming an erased (blank) 12F675 with INTOSC and Internal MCLR 
This should be okay since it is blank and there is no code to
interfere the PGC and PGD lines. And it is okay.

E:\Coding\XWISP2~4>xwisp2w port 2 write state.HEX 
 XWisp2 version 1.6.01 (Aug 14 2005, Open Watcom C 1.30) 
File STATE.HEX loaded and is Intel Hex format conforming 
Programmer Wisp628, firmware version 1.09 
Detected target: 12F675 revision 03 (ID=0FC3) 
Transferring image to 12F675 via Wisp628 
Transferring program memory...OK! 
Transferring ID memory........OK! 
Transferring data memory......OK! 
Transferring fuses memory.....OK! 
Write terminated successfully in 1.14 seconds 
XWisp2 terminated successfully in 2.30 seconds 

2) Verify first step (False alarm, PICKit 1 verified okay) 
I reported this to Rob, the original author to look at the code.

E:\Coding\XWISP2~4>xwisp2w port 2 verify state.HEX 
 XWisp2 version 1.6.01 (Aug 14 2005, Open Watcom C 1.30) 
File STATE.HEX loaded and is Intel Hex format conforming 
Programmer Wisp628, firmware version 1.09 
Detected target: 12F675 revision 03 (ID=0FC3) 
Verifying program memory......OK! 
Verifying ID memory...........OK! 
Verifying data memory.........OK! 
Verifying fuses memory........failed at 000000, expected: '8C3F', found: '8C31' 
Verify failed after 0.28 seconds, rc 21! 
XWisp2 failed after 1.44 seconds, rc 21! 

3) rewrite the not-blank 12F675, failed because of the existing code. 

The dongle is necessary to achieve the programming but I have not
made the dongle and reluctant to do so because shorting any power
supply is not a very good idea IMHO. A better option is to control
Vdd-target at least when we have the control of Vdd-target (like
standard-alone programming). It requires some more external
circuits and some modifications of Wisp628 firmware and host
software.

E:\Coding\XWISP2170>xwisp2w port 2 write state675.HEX 
 xwisp2 version 1.7.00 (Sep 10 2005, Open Watcom C 1.30) 
File state675.HEX loaded and is Intel Hex format conforming 
Programmer Wisp628, firmware version 1.09 
Detected target: 12F675 revision 03 (ID=0FC3) 
Transferring image to 12F675 via Wisp628 
Transferring program memory...Wbus command failure 
Write failed after 0.09 seconds, rc 21! 
XWISP2 failed after 1.25 seconds, rc 21! 

4) Try to use wrong port, Xwisp2 times out and this is expected behavior. 

E:\Coding\XWISP2170>xwisp2w port 1 write state.HEX 
 xwisp2 version 1.7.00 (Sep 10 2005, Open Watcom C 1.30) 
File state.HEX loaded and is Intel Hex format conforming 
SendReceiveSlow read timeout, 0 bytes received 
Failed to activate Wbus device 
XWISP2 failed after 1.08 seconds, rc 23! 

5) Try to programan empty target by removing the 12F675.
Xwsip2 times out and this is expected behavior.  

E:\Coding\XWISP2170>xwisp2w port 2 write state.HEX 
 xwisp2 version 1.7.00 (Sep 10 2005, Open Watcom C 1.30) 
File state.HEX loaded and is Intel Hex format conforming 
Programmer Wisp628, firmware version 1.09 
Target not found in configuration table 
Target not auto-detected, please specify on commandline!

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist