That's what I'm getting now, I had it working before I changed my setup to use a XP VM under W10 so I'm thinking it has something to do wit.
It reads the nodelist and very slowly but it doesn't find the node# ent
if I use PXtools I can search the nodelist just fine so thinking thenodelist
isn't the problem.
Well I did find fidomsg.zip file which has the source file. I looked at it and if I read it right it looks for drive and folder. But I am not a programmer so I will need to find someone to take a look at it to maybe only look for the path without the drive desginator.
Which part of the WCC file are you lookcing at?
This part:
PXSetSystemPath("N:\PXW\SYSTEM\")
If Not PXConnectServer(0) then
Print "PX Wildcat! Netmail Feature not installed properly."
WaitEnter
GlobalResult = FALSE
end
end if
if I use PXtools I can search the nodelist just fine so thinking thenodelist
isn't the problem.
Well I did find fidomsg.zip file which has the source file. I
looked at it and if I read it right it looks for drive and folder.
But I am not a programmer so I will need to find someone to take a
look at it to maybe only look for the path without the drive
desginator.
fixBasically, I have all outbound netmail routed to my NC, which, if I
can get a response to him about not being able to connect to him, I might have to see about switching to another NC.
you don't need to change nets to change your routing... i feed your NC and there have been a few troubles recently but once notified, he was able to
them fairly quickly...
Yeah, fortunately, I have my NC's cell number and was able to identify the issue right away and after making the necessary change in Internet Rex, all is well with the world again :)
Will you tell me what changes you needed to make? Was this Irex also passing on netmail from pxwin?
I was wondering if you had a setup using Irex and pxwin and what is in
your routing section in pxwin look like for netmail.
That's what I'm getting now, I had it working before I changed my setup to use a XP VM under W10 so I'm thinking it has something to do wit.
It reads the nodelist and very slowly but it doesn't find the node# ent
if I use PXtools I can search the nodelist just fine so thinking thenodelist
isn't the problem.
Well I did find fidomsg.zip file which has the source file. I looked at it and if I read it right it looks for drive and folder. But I am not a programmer so I will need to find someone to take a look at it to maybe only look for the path without the drive desginator.
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 615 |
Nodes: | 10 (0 / 10) |
Uptime: | 70:01:25 |
Calls: | 9,853 |
Calls today: | 3 |
Files: | 96,976 |
D/L today: |
6 files (22K bytes) |
Messages: | 1,081,158 |