Maybe, maybe not but I would say that micronet need to get their
act together with their filenaming convention for their nodelist
files before anyone attempts to offer a solution to your problem.
As things stand at the moment, I couldn't even hazard a guess as
to what the problem could be, sorry.
The last FSXNET.Z## contains:
Looking inside MICRONET.Z##:
Maybe, maybe not but I would say that micronet need to get their act together with their filenaming convention for their nodelist files before anyone attempts to offer a solution to your problem. As things stand at the moment, I couldn't even hazard a guess as to what the problem could be, sorry.
it should be noted that the micronet ZC's modem suffered from a lightning strike and they were down until a new mpdem was procured... during this time, the nodelist and ZC activities were transferred to the 2nd "in command"... the two systems are different which explains the filename
case differences as well as the appearance of the file_id.diz...
without knowing more about what the client software is doing, there's no way to even start to guess... from my side as an observer, i would say
the software is simply being too strict and needs to lighten up a little ;)
it should be noted that the micronet ZC's modem suffered from a
lightning strike and they were down until a new mpdem was
procured... during this time, the nodelist and ZC activities
were transferred to the 2nd "in command"... the two systems are
different which explains the filename case differences as well
as the appearance of the file_id.diz...
The temporary ZC activities is appreciated!
What modem replacement were you able to find? I have a modest
museum of old modems. I don't know what to do with them.
The only difference between FSXNET.Z## working and MICRONET.Z## not working is the presence of the 2nd file file_id.diz in the latter.
The only difference between FSXNET.Z## working and MICRONET.Z## not
working is the presence of the 2nd file file_id.diz in the latter.
Do you get MICRONET.Z## files? I've only ever received MICRONET.ZIP
files with a MICRONET.### (e.g. MICRONET.092) in it.
Looks like I receive an uppercase MICRONET.ZIP file (not .Z##) with a lowercase micronet.### inside of it:
Re: nodelist curveball
By: Martin Foster to August Abolins on Sun Apr 04 2021 11:33:00
Maybe, maybe not but I would say that micronet need to get their
act together with their filenaming convention for their nodelist
files before anyone attempts to offer a solution to your problem.
it should be noted that the micronet ZC's modem suffered from a lightning strike and they were down until a new mpdem was procured... during this time, the nodelist and ZC activities were transferred to the 2nd "in command"... the two systems are different which explains the filename
case differences as well as the appearance of the file_id.diz...
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 142:17:34 |
Calls: | 328 |
Files: | 5,823 |
Messages: | 228,112 |