I do not think you need to implement any fancy protocols. From the PC you send a char which tells the PIC to dump the contents of the eeprom. I would write the Software/Firmware to handle fixed sized blocks and use hardware handshaking (if your data can range from 0 to 255 you can forget about software handshaking [xon-xoff]). Later add a CRC byte to verify each block. The PC collects the data, stores it on disk or prints the printable characters to a terminal window or both. The Windows95 API will support up to 19,200 bps so I would kick 1200 bps up several notches. Other available controls can run much faster e.g., 115,200 bps and beyond -- limited by the PC's uart (16550A = faster). I don't know what it would take to jerk around an existing modem package to make it work so I suggested you write your own. In Visual Basic you drop a control on a form, set the properties you like, write a few lines of code and you should be able to send and receive characters within the hour. BTW: ASCII and Linefeed modes have limited usefulness so binary transfers are most often supported. Rich At 11:11 PM 2/23/98 +0100, you wrote: >Oh, I did not realize it was much data. Did not read the question thru. >Is it maybe possible to use DOS "copy /b COM1: file" (or how it is) command ? >Will it exit om CTRL-Z code recieved, switch /b stated? >If not, can we end recieving using CTRL-C from keyboard, or if not rin un >windows dos-window and kill it from windows? >/Morgan > >At 10:35 1998-02-23 -0800, Rich wrote: >>This will double the file size on transfer. >> >>All that needs to be done is to filter the stream as it is received from the >>PIC and display and/or save the characters desired. >>A terminal program may have to be created (VB using microsoft's comm >control). >> >>Rich >> >>At 03:35 PM 2/23/98 +0100, you wrote: >>>Why not convert to ASCII-coded hex before transfer? >>>/Morgan >>> >>>At 14:39 1998-02-23 +0100, you wrote: >>>>I have written a program which read all adresses in a 24C16 I2C EEPROM and >>>>sends the data to a PC via RS232 (8,N,1 1200 Baud). I have used the Windows >>>>Terminal program for receiving the data. But when I receive the data as a >>>>text file (ASCII) there is a probelm with the control characters CR, FF, LF >>>>etc. They are not read as data. Can I somehow receive the data as a binary >>>>file? I have tried to use the various protocols for this purpose, but it >>>>always ends out with a failure. What do I need to do in my Pic-code to >>>>support fx. the Xmodem or the Kermit protocol? I hope you are able to help >>>>me ! >>>> >>>> >>>>With kind regards >>>>GDK-SSJ - Steen Schelle Jensen >>>>Dept.: 1545 >>>>Internet e-mail: ssjensen@grundfos.com >>>> >>>> >>>/ Morgan Olsson, MORGANS REGLERTEKNIK, SE-277 35 KIVIK, Sweden \ >>>\ mrt@iname.com, ph: +46 (0)414 70741; fax +46 (0)414 70331 / >>> >>> >> >>========================================= >>= Abolish the Income Tax! Fire the IRS! = >>= http://www.nrst.org/ = >>========================================= >> >> >/ Morgan Olsson, MORGANS REGLERTEKNIK, SE-277 35 KIVIK, Sweden \ >\ mrt@iname.com, ph: +46 (0)414 70741; fax +46 (0)414 70331 / > > ========================================= = Abolish the Income Tax! Fire the IRS! = = http://www.nrst.org/ = =========================================