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: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,039 |
Nodes: | 15 (0 / 15) |
Uptime: | 198:21:03 |
Calls: | 500,233 |
Calls today: | 2 |
Files: | 95,197 |
D/L today: |
554 files (501M bytes) |
Messages: | 464,137 |