+ 24 Jun 16:44:51 SEAL Begin, Seal/386 v0.50 (mem=12307K)
# 24 Jun 16:44:51 SEAL Scanning bad msgs in F:\BAD\BAD_MSGS
: 24 Jun 16:44:51 SEAL Created echo area STARGATE from 1:140/1
! 24 Jun 16:44:51 SEAL ERROR: Run-time Error 216 at 0277:0434
+ 24 Jun 16:44:51 SEAL End. (length=0:00, mem=12306K)
There is also newsgroups in my BAD_MSG area.
Believe it or not, I think that runtime error is due to one
Wow... sounds great, really sorry Mike, I'm miss-understanding your directions, still getting the 216 error.
Where did I lose you?
Correcting the distribution errors or
manually verifying SEAL.INI?
Correcting the distribution errors or
manually verifying SEAL.INI?
Both... :) Do I edit both or just one, specifically.
Do I just edit "seal.ini" and then run seal386 update?
Which files do I edit specifically?
Don't let the
runtime error make you think that the code is hosed. Robert
Don't let the
runtime error make you think that the code is hosed. Robert
This is GREAT Mike... You explained it really well. And I did
understand what ya said, so I'll try it again, it's sure half the
fun of this hobby.
By coincidence, I started getting runtime error 216 here a
few days ago, and only noticed it today. It proved to be
caused by one or more already processed netmails to Seal386,
with the SCAN parameter.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,041 |
Nodes: | 15 (0 / 15) |
Uptime: | 23:02:15 |
Calls: | 500,348 |
Calls today: | 21 |
Files: | 95,205 |
D/L today: |
12,927 files (2,093M bytes) |
Messages: | 465,961 |
Posted today: | 3 |