There seams to be a issue with the apod* file in the fsx_img area.
They are comming across as zero bytes in size, and has been going on for
a few days now.
There seams to be a issue with the apod* file in the fsx_img area.
They are comming across as zero bytes in size, and has been going on for
a few days now.
There seams to be a issue with the apod* file in the fsx_img area.
They are comming across as zero bytes in size, and has been going on for a few days now.
There seams to be a issue with the apod* file in the fsx_img area.
They are comming across as zero bytes in size, and has been going on
for a few days now.
I am seeing this here too.
I currently have a 0 byte fsxnet.zip and FSXNET.Z71 in my inbound.
There seams to be a issue with the apod* file in the fsx_img area.
They are comming across as zero bytes in size, and has been going on for a few days now.
The last one of any size was dated Sep 22nd.
Hello Avon!
There seams to be a issue with the apod* file in the fsx_img area.
They are comming across as zero bytes in size, and has been going on
for a few days now. The last one of any size was dated Sep 22nd.
Sysop: | Angel Ripoll |
---|---|
Location: | Madrid, Spain |
Users: | 15 |
Nodes: | 8 (0 / 8) |
Uptime: | 132:35:58 |
Calls: | 890 |
Files: | 15,281 |
D/L today: |
5 files (9K bytes) |
Messages: | 70,014 |