Database Search
If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.
TechHome
Serial
 |
- !!NEWSFLASH!!
- !List of Errors Returned from pGetLastError
- Can you do a FileCopy to an Active Port
- Capture Caller ID Information from a Modem
- Comport Being Accessed by More than one Program
- Default X-10 Monitor Sample Code
- Detect if a Line is Busy
- Detecting Valid COM Ports
- Digital Multimeters with Serial Ports
- Direct Serial Connection - No Modem
- Framing Error with Serial Extender
- Hardware Overrun Error
- How to Force a Modem to Continue
- How to Handle the Multiple Downloads with pRecvFile
- Kermit Type Transfers
- Paging and pPutLine
- pComControl
- pComOpen Error 100
- pModemDial Clicking but not Audibly Dialing
- pRecFile Failure
- pSendFile bad port handle
- Receiving Mouse Button Info on Serial Port
- Receiving Parity Error with pRecvFile
- Send Power On Hex Command to a Nec Display
- Sending Control Characters to Com Port
- Serial Communications Problems with pWaitfor
- Serial Extender - Timeouts - Boxes Functions
- Serial Extender and PPP connections
- Serial Modem Transferring Files
- Uploading Text Files using Serial Extender
- Using pCapture to Capture Log
- VT100 Emulation - ANSI chars and Serial Extender
- X-10 Control Sample Script II
- X-10 Control Sample Script
- X-10 FAQ
- X-10 What2Do WBT
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Serial Extender ZMODEM transfer failure using pRecvFile
Keywords: pRecvFile
Question:
I have been trying to automate a BBS transfer sequence without success. The connect and login exchanges work fine as do the selection exchanges. But when I get to the pRecvFile command the "Transfer Statistics" window opens, the data fields flicker without ever changing (the transfer rate shows as 4294965676), the error count goes to 10, then the function returns a 0. I have tried several protocols with and without the transfer status option turned on. I have tried several BBS sites. I am using serial extender version 20019. The following is a sample sequence:
BoxText("Sending file name")
pPutLine(port,"bisys.zip")
BoxText("Waiting for signoff option")
rs=pWaitFor(port,"download?"," ",0,3000)
BoxText("Sending Y")
pPutline(port,"Y")
BoxText("Waiting for begin indicator")
rs=pWaitFor(port,"**"," ",0,3000)
BoxText("Receiving File")
xx=pRecvFile(port,"zmodem","bisys.zip",1,1)
Am I overlooking something or is this a matter of protocol incompatibility?
Answer:
Looks vaguely ok. I would get rid of the:
BoxText("Waiting for begin indicator")
rs=pWaitFor(port,"**"," ",0,3000)
lines and let the zmodem receive worry about it.
Also I would suspect something in the initial connection parameters, close but not perfect. Maybe 7 bit text connection when zmodem needs an 8 bit connection or something.
Version 21016 of the Serial extender introduced a pComModify function that allows you to change the parity/format settings before and after receiving and sending a file.
Article ID: W12574
Filename: pRecFile Failure.txt
File Created: 2001:05:10:14:44:04
Last Updated: 2001:05:10:14:44:04