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: | smooth0401 |
|---|---|
| Location: | New Providence, NJ |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 14:30:11 |
| Calls: | 320 |
| Files: | 609 |
| D/L today: |
10 files (10,002K bytes) |
| Messages: | 53,753 |