But, I DO want to know what is new in BETA 2 of 2.33 if you can share! <G>
Well, I guess we shall see what happens if I can find all my tools
again. I'll be re-organizing a few things over the coming weeks and months, and then I need to re-check if there's actually a need/want/whatever for me to get back into the loop :-)
But, I DO want to know what is new in BETA 2 of 2.33 if
you can share! <G>
Asking again as another year has passed. Allowed to spill the
beans yet?
Well, there was lost hope 2 years ago! :(
Well, there was lost hope 2 years ago! :(
i can't say that :?
Well, there was lost hope 2 years ago! :(
i can't say that :?
Well JoHo said he's still around,
but no website update,
no addressing my zmodem issue with FD (over 2 years now <G>) ...
but no biggie ...
no addressing my zmodem issue with FD (over 2 years now <G>) ...
please refresh my memory on this... i know you've had problems but i don't remember the specifics...
but no website update,
yeah... ok... ??
Well, there was lost hope 2 years ago! :(
i can't say that :?
no addressing my zmodem issue with FD (over 2 years now <G>) ...
please refresh my memory on this... i know you've had problems but
i don't
remember the specifics...
Constant resending a file and never completing it. The file would resend, resend, resend (retry), until it timed out. Had to have
the user delete the msg packet so we could transfer mail again.
Just think ZMODEM needs optimized to run under Win32 a bit.
Always worked GREAT under OS/2 tho.
but no website update,
yeah... ok... ??
The news page hasn't been updated since they release XROBOT on
Dec. 1999.
www.defsol.se
correct?
Well, there was lost hope 2 years ago! :(
i can't say that :?
I can. :(
mmmmmm... is this mailer to mailer on POTS or something else?
mmmmmm... is this mailer to mailer on POTS or something else?
No, mailer to mailer via telnet is the issue.
1. what are your machine's specs?
a. CPU and mhz
b. memory
c. hard disk size
2. what OS?
3. what FOSSIL?
4. what telnet shim or virtual modem?
5. what version of FD?
6. describe the actual problem you are seeing.
7. post log snippets showing problem.
all i/we can do is try to help...
i forgot to ask and you forgot to tell... what type of internet connection?
i forgot to ask and you forgot to tell... what type of internet
connection?
DSL ... did the same years back when I had cable.
the reason i ask is that i've only ever seen this on high-latency connectio like dialup on paths with overly busy routers and such...
there was a lot of work done in the transfer engine to relax the timings fo these types of problems...
the reason i ask is that i've only ever seen this on high-latency
connectio
like dialup on paths with overly busy routers and such...
One was FD 2.12.SW ... one was 2.20c ... one was Argus ... and I
forget what the other uplink was.
there was a lot of work done in the transfer engine to relax the
timings fo
these types of problems...
it was all in the latest public and pay-for multiline version, AFAIR...
it was all in the latest public and pay-for multiline version, AFAIR...
it was all in the latest public and pay-for multiline version, AFAIR...
What?
it was all in the latest public and pay-for multiline version, AFAIR...
I paid for v2.20c, upgraded to 2.30, then 2.31, 2.32, and to 2.33
... I paid for the 2.12.SW (which was 2.11 at the time), and then
also paid the $$$ for the multiline version which I am running
now. If I didn't pay for FD, I wouldn't even bother using it now-a-days.
i think you should have it, then... dunno what could be the problem... like said before, i only saw problems like that on congested/slow pipes...
i think you should have it, then... dunno what could be the problem... like said before, i only saw problems like that on congested/slow pipes...
i think you should have it, then... dunno what could be the problem... like said before, i only saw problems like that on congested/slow pipes...
My other issue is the IP address being trucated ie:
199.99.999.99 would show up in the DOBBSx.BAT file as 1999999999.
I am using NetSerial/NetFOSS (Contacted Mike @ PCMicro Already), but being you're running a beta, maybe you can see something.
Whenever I answer FD via terminal mode, the IP displays PERFECTLY. But onc have FD pass the information onto the DOBBSx.BAT file to load the BBS here what I get.
EXEBBS 115200 2 10080 1 /ARQ/7125343200 N/A
Which under ALT-J (Terminal mode from WFC), it would show as 71.253.43.200 whenever I answered the "RING" ....
I never really paid much attention when I was using OS/2 and SIO, so I'm no sure if it worked then or not.
Any ideas would be GREATLY appreciated! Or some help from JoHo or Mats. O at very least them being notified on the problem.
Thanks!
Replying agian .. please read the quoted message if you didn't get
it the first time I sent it a month ago.
i got it the first time you posted it...
i don't know why it would be being written to the dobbs file like that... everything that i see here seems to show that FD writes the connecting numb as it received it from the "modem device"... my USRs send caller id data preformatted and my telnet shim also writes IP numbers formatted with the d in the proper places... FD, as far as i can see, doesn't unformat them :?
I paid for v2.20c, upgraded to 2.30, then 2.31, 2.32,
and to 2.33 ... I paid
for the 2.12.SW (which was 2.11 at the time), and then
also paid the $$$ for
the multiline version which I am running now. If I didn't pay for FD, I wouldn't even bother using it now-a-days.
Except maybe Netserial.
Except maybe Netserial.
Paid for that as well ... well worth the money also.
What's the maximum number of virtual comports for the Netserial SysOp versi
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,022 |
Nodes: | 17 (0 / 17) |
Uptime: | 01:03:05 |
Calls: | 503,380 |
Calls today: | 4 |
Files: | 107,993 |
D/L today: |
12,994 files (1,107M bytes) |
Messages: | 441,054 |