#Bad File?????
9 messages in this thread
I have ran into a problem with one of the files here. Something that has never
happend before. What has happend is when I tried to download FIXTEX.ARC I got a
whole bunch of timeouts, and no good data. And when I canceled the download my
software told me "Hacked code detected" and then my software aborted. This has
never happened before and I have used this same software to download many files
from here. The software I am useing is JRcomm version 1.02. And I am using CIS
B protocol. Got any ideas?
Greg, I'm sorry to hear that you had problems!
I'm sure that anything that has been here long enough to have an .ARC extension
has not been hacked! I suspect that the timeouts, etc. were you problem – you
just didn't get a good download. I have not idea why that could happen – but
I'm not immune, either. When it happens to me, I abort, and then use B+
protocols to re-start the download where I left off before. I think I'd try
another download. I get the best results at times when there are not so many
people online – either during the workday, or in the wee hours.
—Betty
Well I found that it wasn't the file. It was my software. JRcomm. I don't
understand what happend to it. The problem continues even after I unpacked the
archive fresh. So now I am using my trusty NComm 2.0 prg. It works ok, but I
can't seem to get the CIS B protocol to work, so I sit and chug along at slow
xfer rates using Xmodem. It seems to work the best with what I have. I have
tried the XPRB protocol files here on the system, but all they do is cause a
software failure and a guru. Which also kicks me off line. Got any suggestions
on how the get this NComm 2.0 to work with the XPR B protocols. I have read the
docs, and NComm does support XPR.
Greg,
I rarely use the XPR protocols. Since I use AutoPilot for CompuServe, and it
uses B+ by default, that's all that I need.
I believe, however, that there is an xprbplus.library in the libraries here.
Have you tried that one? I haven't tried it – just wondering.
If you have YModem or Kermit, they would be better than XModem.
—Betty
Thanks for the help. And I have tried both of the XPR libs thayt are here for
CIS protocols. And both caused crashes with NComm v2.0. Again thanks for the
help.
I use to have that problem using JRComm and CI$. Once it happened, it kept
happening. As the file from CI$ was not hacked (trusting aren't I?), and I did
not hack JRComm, I reloaded JRComm and I was back up in business.
Unarc JRComm and reinstall it then switch to Term or Terminus, or Termite. Then
Register whichever you use.
Roy Nash 70662,747
Thanks for the help Roy! I tried reloading and unpacking again and the same
thing happend. I will try iut a again. Right now I a am trying BackTalk 1.55a.
I'll wait and see how well that works.
Greg,
Backtalk uses the B+ protocol by default. It should work well with CIS.
—Betty
Greg: Something in Jrcomm.def file is the cause of the "hacked" msg. Make sure
the old one is deleted when u reinstall jrcomm. and set all your defaults
again, then copy and rename jrcomm.def (ie….jrcomm.def.good) and save it.
When every "hacked" strikes again , delete jrcomm.def then copy and rename
(jrcomm.def.good) as jrcomm.def and your back in business. Jrcomm.def resides
in the jrcomm.def should be under your JRCOMM dir.
………….Wes
Via Amiga A2000 and Whap! navigation program