I keep getting this message:
17.03.19 8:43:37 PM Could not move file Z2DAILY.073 to file area
Z2DAILY.
17.03.19 8:43:37 PM Could not move file Z2PNT.Z74 to file area
Z2PNT.
How do I create the file areas when my arealist sends the "areas" in lowercase?
File FNEWTA11.ZIP has been moved to file area FIDONEWS.
File ELST1903.ZIP has been moved to file area ECHOLIST.
I have a "FIDONEWS" sub-directory in my "Filebase" directory which contains "FNEWTA11.ZIP and an "ECHOLIST" sub-directory in my "Filebase" directory which contains "ELST1903.ZIP"
The only reason for your problem that I can think of right now is that maybe you're not receiving accompanying .TIC files ??
UPDATE. Ido have the directories created by Winpoint, but this still keeps happening (I'll shorten the lines so they don't wrap):
8:21:37 PM Could not move file Z2DAILY.073 to file area Z2DAILY.
8:21:37 PM Could not move file Z2PNT.Z74 to file area Z2PNT.
8:21:37 PM File Z2DAILY.078 has been moved to file area Z2DAILY.
8:21:37 PM Starting Import^^^^^^^^^^^^^^
8:21:37 PM Tossed 0 messages from 0 packets
And here is the result of a manual compile-nodelist:
8:23:54 PM Beginne Diffing
8:23:54 PM Diffing beendet
8:23:54 PM Beginne Verarbeitung
8:23:54 PM 1546 EintrXge aus NODELIST.074 eingelesen
8:23:54 PM Datei Z2PNT.* nicht gefunden!
8:23:54 PM Fehler beim Éffnen der Pointliste Z2PNT !
8:23:54 PM 0 doppelte EintrXge gelXscht
8:23:55 PM Systemnamen erfolgreich gespeichert.
8:23:55 PM Sysopnamen erfolgreich gespeichert.
8:23:55 PM Standorte erfolgreich gespeichert.
8:23:55 PM Verbindungsinformationen erfolgreich gespeichert.
8:23:55 PM Hauptindex erfolgreich gespeichert.
8:23:55 PM Fertig
..so does that read success? ..or are there error messages above?
"nicht" sounds negative. :(
File FNEWTA11.ZIP has been moved to file area FIDONEWS. File
ELST1903.ZIP has been moved to file area ECHOLIST.
I have a "FIDONEWS" sub-directory in my "Filebase" directory which
contains "FNEWTA11.ZIP and an "ECHOLIST" sub-directory in my "Filebase"
directory which contains "ELST1903.ZIP"
I will try to create the directories manually and report back.
What I did during install is install the program on H:drive, and left the program to use C:drive for its default directories. Maybe this discrepency trips up the installation?
The only reason for your problem that I can think of right now is that
maybe you're not receiving accompanying .TIC files ??
I would assume that if Winpoint is trying to move the files to a
filearea, then it *knows* about the filearea name, and that would be from a .TIC
Are these two files actually in your "Inbound" directory, along with
their accompanying .TIC files?
8:21:37 PM File Z2DAILY.078 has been moved to file area Z2DAILY.Well, that worked OK :-))
8:23:54 PM 1546 EintrXge aus NODELIST.074 eingelesen^^^^^^^^^^^^^^
8:23:54 PM Datei Z2PNT.* nicht gefunden!
not found
8:23:54 PM Fehler beim ?ffnen der Pointliste Z2PNT !
The Fido nodelist(NODELIST.074) was successfully processed but the Zone2 Pointlist(Z2PNT.*) wasn't because WinPoint couldn't find it. Does
Z2PNT.Z74 actually exist on your system and where is it? If it does
exist, have you extracted the raw pointlist(Z2PNT.074) from Z2PNT.Z74
and copied it to the WinPoint "DistribNL" directory? WinPoint's nodelist processor *cannot process* packed nodelist/pointlist files, although it
*can process* packed nodediff/pointdiff files.
8:21:37 PM File Z2DAILY.078 has been moved to file area Z2DAILY.
Well, that worked OK :-))
OK but you shouldn't have to do that, as WinPoint should have created
all the root directories automatically..
Martin Foster : August Abolins wrote:
The Fido nodelist(NODELIST.074) was successfully processed but the Zone2
Pointlist(Z2PNT.*) wasn't because WinPoint couldn't find it. Does
Z2PNT.Z74 actually exist on your system and where is it? If it does
exist, have you extracted the raw pointlist(Z2PNT.074) from Z2PNT.Z74
and copied it to the WinPoint "DistribNL" directory? WinPoint's nodelist
processor *cannot process* packed nodelist/pointlist files, although it
*can process* packed nodediff/pointdiff files.
I remember encountering an error the first time I tried to process the all-zones nodelist, so I did unpack it manually and put it in the DistribNL dir.
SO... I just tried that with the Z2PNT.074 file.
9:56:51 PM Beginne Diffing
9:56:51 PM Diffing beendet
9:56:51 PM Beginne Verarbeitung
9:56:51 PM 1546 EintrXge aus NODELIST.074 eingelesen
9:56:51 PM 4549 EintrXge aus Z2PNT.074 eingelesen
9:56:51 PM 0 doppelte EintrXge gelXscht
9:56:51 PM Systemnamen erfolgreich gespeichert.
9:56:51 PM Sysopnamen erfolgreich gespeichert.
9:56:51 PM Standorte erfolgreich gespeichert.
9:56:51 PM Verbindungsinformationen erfolgreich gespeichert.
9:56:51 PM Hauptindex erfolgreich gespeichert.
9:56:51 PM Fertig
...and it must have worked because I purposely changed my entry and it shows up with the change.
Hmmmmm...so do I have to keep unarchiving and copying into DistribNL
every time? ..or was it just for the first-time-use? Maybe this anomaly should be in the uber manual.
This is how it all works .....
When you install a new nodelist or a new pointlist for the very first time, they have to be manually unpacked and copied to the "DistribNL" directory. From what you've said, you've already done this and you now have a compiled nodelist and a compiled pointlist.
However, when a new nodediff or new pointdiff arrives, you need to copy the *packed* nodediff/pointdiff to the "DistribNL" directory. There's
no need to unpack them because WinPoint does it for you...
This is how it all works .....
When you install a new nodelist or a new pointlist for the very first
time, they have to be manually unpacked and copied to the "DistribNL"
directory. From what you've said, you've already done this and you now
have a compiled nodelist and a compiled pointlist.
Yes.. I had read your wonderful guide sec 3.2. That is what helped me get the NL installed/compiled.
BTW, your guide refers to "All other fields should be left at their default settings" ..but after I started to experiment with adjustments, I nolonger had a record of those default settings to undo what may have worked before. How about including some screenshots on your guide for some of the Options/*
However, when a new nodediff or new pointdiff arrives, you need to
copy the *packed* nodediff/pointdiff to the "DistribNL" directory.
There's no need to unpack them because WinPoint does it for you...
That was very helpful. Thank you. But do I have to do the
moving/copying each and every time subsequent nodelists arrive?
...How about including some screenshots on your guide for
some of the Options/*
Yes, that was already on my ToDo list but it's the usual problem of
having the time and inclination to do it.
.. But do I have to do the
moving/copying each and every time subsequent nodelists arrive?
No, that only applies to new nodediffs/pointdiffs.
...How about including some screenshots on your guide for some of the
Options/*
Yes, that was already on my ToDo list but it's the usual problem of
having the time and inclination to do it.
I could do some screen captures, but you have to tell me which ones.
I helped to put this together (years ago): http://www.tinysbbs.com/tinys-usenet.pdf
..which then inspired the sysop to produce this: http://tinysbbs.com/howtouseabbs.pdf
.. But do I have to do the moving/copying each and every time
subsequent nodelists arrive?
No, that only applies to new nodediffs/pointdiffs.
I did a file request for NODEDIFF, when I now realize I should have used NODEDIFZ. When the correct file arrives, I only have to move the
archived file *once* to the DistribNL, right? I never have to do that *ever* again?
You need to copy the packed nodediff file to the "DistribNL" directory every time a new one arrives. Same applies to new pointdiff files.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 69:12:31 |
| Calls: | 6,655 |
| Calls today: | 1 |
| Files: | 12,200 |
| Messages: | 5,332,099 |
| Posted today: | 1 |