On Feb 21, 2009, at 12:21 PM, Wouter van Ooijen wrote:

> Joseph Bento wrote:
>> There may or may not
>> be a fix to use this hardware in a virtual machine, but I'm unaware  
>> of
>> what to try.
>
> Listing the exact "all sorts of errors" might be a start.

Hi Wouter,

Yes, listing the errors would likely help.  I was not in a position to  
list everything at the time.

Here's a screen capture:

C:\PICjal\xwisp2>xwisp2w port 3 go c:\jallib\16f690\blink.hex
  xwisp2 version 1.9.5 for Windows (Jan 24 2008, Open Watcom C/C++ 1.70)
File c:\jallib\16f690\blink.hex loaded and is Intel Hex format  
conforming
More bytes received (2) than expected!
Detected programmer: Wisp628, firmware version 1.27
Target: 16F690 revision 05 (ID=1405)
Target erased
Transferring program to 16F690 via Wisp628
Transferring program memory...100%
Verifying program memory......  0%failed at 000008, expected: '01A3',  
found: '3F
FF'
Write-Verify operation failed after 0.30 seconds, rc 21
xwisp2 failed after 1.92 seconds, rc 21
Press 'Enter' to continue:


C:\PICjal\xwisp2>

Someone commented on using a simpler USB/serial adaptor.  I have had  
worse results with plain adaptors, in that they would not work  
properly with my ham radio related stuff in a native windows  
environment, nor would OS-X recognize them.    The Keyspan previously  
worked in Parallels before Parallels flaked.  For most of my work, I  
love the Mac.  If I were more comfortable at a command line, I could  
do all my PIC learning and development on the Mac.  I hadn't wanted to  
resort to bootcamp, but that might be my best option.

Joe



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