Shurato wrote to Rick Smith <=-
I don't know where else to look... Its got to be a problem with irex
or fastecho.
Shurato wrote to Rick Smith <=-
I don't know where else to look... Its got to be a problem with irex or fastecho.
I suspect it's FE that doesn't have its routing table correct. You should have it set for all mail, including netmail since you cannot crashmail in IRex (IRex requires you to use a V7+ nodelist which you have told me you do not have) right now.
Double-check your FE setup and make sure all Micronet mail is routed to Rick.
Shurato wrote to Rick Smith <=-
I don't know where else to look... Its got to be a problem with irex or fastecho.
I suspect it's FE that doesn't have its routing table correct. You should have it set for all mail, including netmail since you cannot crashmail in IRex (IRex requires you to use a V7+ nodelist which you have told me you do not have) right now.
Double-check your FE setup and make sure all Micronet mail is routed to Rick.
I've got 618:* routing to 618:300/1, and arcmail set to none. Previously had it set to crash/direct which might have been the problem. I've send netmails out and sent logs to Rick Smith.
I've got 618:* routing to 618:300/1, and arcmail set to none.Previously
had it set to crash/direct which might have been the problem. I'vesend
netmails out and sent logs to Rick Smith.
Are you using a Binkley-style outbound? If not ARCmail should be set to yes. Do not send anything crash as Internet Rex cannot crash any nodes unless you are using a V7+ nodelist which you have said you are not using.
All mail, including netmail, destined for other Micronet nodes, should be routed through Rick.
--- MBSE BBS v1.1.0 (Linux-x86_64) * Origin: Outpost BBS * Johnson
City, TN (618:618/1)
Crash should work, I'm pretty sure irex crashes nodes (just sends immediately), but it can't send directly. I did get rid of direct though and have tried to send messages through that way. I've got 618:* routingto
618:300/1, which is Rick's Node.
Crash should work, I'm pretty sure irex crashes nodes (just sendsthough
immediately), but it can't send directly. I did get rid of direct
and have tried to send messages through that way. I've got 618:*routing to
618:300/1, which is Rick's Node.
IRex will only "crash" nodes that you have in your IRex config. It won't crash anyone else since you are not using a V7+ nodelist. So that's not an issue. What it sounds like is that somewhere, you have an issue.
Be aware that FastEcho is buggy and cannot be fixed as it likes
to srip the seen-by lines in a message and its Binkley support
is not the best. You've patched your FE to 1.46.1, right?
The big issue is you're using buggy software (Internet Rex and FastEcho) that may be causing issues and you may not realize it.
--digi
--- MBSE BBS v1.1.0 (Linux-x86_64) * Origin: Outpost BBS * Johnson
City, TN (618:618/1)
Shurato wrote to digimaus <=-
I did, but that would crash ntvdm regularly, so I went back to 1.46.
The DPMI mode FE was extremely unstable.
Shurato wrote to digimaus <=-
I did, but that would crash ntvdm regularly, so I went back to 1.46. The DPMI mode FE was extremely unstable.
That .1 has important fixes which may fix the issue you're having. Personally, if you can't upgrade, I'd switch to another mail tosser post-haste. I think until you fix FE, you're going to keep having issues.
Shurato wrote to digimaus <=-
I did, but that would crash ntvdm regularly, so I went back to 1.46. The DPMI mode FE was extremely unstable.
That .1 has important fixes which may fix the issue you're having. Personally, if you can't upgrade, I'd switch to another mail tosser post-haste. I think until you fix FE, you're going to keep having issues.
Ok, I've upgraded again and am not doing the stuff that made it crash (befor and after packing commands). The thing is though, this all worked just fine until recently and I hadn't changed anything other than restoring from a previously working backup. My experiences with VMs are flaky. Often I'll change something and it won't take effect. I'm using fastec16 instead of fastecho now and feutil16 instead of feutil.
On 05 Sep 24 19:30:00, Shurato said the following to Digimaus:
Ok, I've upgraded again and am not doing the stuff that made it crash(befor
and after packing commands). The thing is though, this all worked justfine
until recently and I hadn't changed anything other than restoring froma
previously working backup. My experiences with VMs are flaky. OftenI'll
change something and it won't take effect. I'm using fastec16 insteadof
fastecho now and feutil16 instead of feutil.
Not sure what OS you're on but just throwing this out there, that
Microsoft did something to NTVDM after XP where its just not
reliable for DOS stuff.
I've written about this many times in the past, I can't really "prove it" but go by the few times I've tried to migrate my BBS to anything
beyond XP and
things just randomly crashed. For no reason, just happened. Didn't matter
of the hardware or anything that our resident Professor can chime-in
on. Anything beyond XP and the NTVDM environment is unreliable...
period.
It was the DPMI executables. I was finally (after using the command.com environment to run the commands) able to upgrade my fastecho to 1.46pl1. It's running well now.
* In a message originally to Shurato, Nick Andre said:
On 05 Sep 24 19:30:00, Shurato said the following to Digimaus:
Ok, I've upgraded again and am not doing the stuff that made itcrash (befor
and after packing commands). The thing is though, this allworked just fine
until recently and I hadn't changed anything other thanrestoring from a
previously working backup. My experiences with VMs are flaky.Often I'll
change something and it won't take effect. I'm using fastec16instead of
fastecho now and feutil16 instead of feutil.
Not sure what OS you're on but just throwing this out there, that
Microsoft did something to NTVDM after XP where its just not
reliable for DOS stuff.
I've written about this many times in the past, I can't really
"prove it" but go by the few times I've tried to migrate my BBS to
anything beyond XP and
things just randomly crashed. For no reason, just happened. Didn't
matter of the hardware or anything that our resident Professor can
chime-in on. Anything beyond XP and the NTVDM environment is
unreliable... period.
It was the DPMI executables. I was finally (after using the
command.com environment to run the commands) able to upgrade my
fastecho to 1.46pl1. It's running well now.
Hello Shurato!
Friday September 06 2024 12:13, you wrote to Nick Andre:
* In a message originally to Shurato, Nick Andre said:
On 05 Sep 24 19:30:00, Shurato said the following to Digimaus:
Ok, I've upgraded again and am not doing the stuff that made itcrash (befor
and after packing commands). The thing is though, this allworked just fine
until recently and I hadn't changed anything other thanrestoring from a
previously working backup. My experiences with VMs are flaky.Often I'll
change something and it won't take effect. I'm using fastec16instead of
fastecho now and feutil16 instead of feutil.
Not sure what OS you're on but just throwing this out there, that
Microsoft did something to NTVDM after XP where its just not
reliable for DOS stuff.
I've written about this many times in the past, I can't really "prove
it" but go by the few times I've tried to migrate my BBS to
anything beyond XP and
things just randomly crashed. For no reason, just happened. Didn't
matter of the hardware or anything that our resident Professor can
chime-in on. Anything beyond XP and the NTVDM environment is
unreliable... period.
It was the DPMI executables. I was finally (after using the command.com environment to run the commands) able to upgrade my fastecho to 1.46pl1. It's running well now.
This is working now?
Sysop: | Sarah |
---|---|
Location: | Portland, Oregon |
Users: | 19 |
Nodes: | 16 (0 / 16) |
Uptime: | 53:40:01 |
Calls: | 126 |
Calls today: | 126 |
Files: | 84,009 |
U/L today: |
5 files (318K bytes) |
D/L today: |
33 files (8,385K bytes) |
Messages: | 38,259 |
Posted today: | 25 |