• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

+++ dfQ Beta Release 2 +++

Wow, you go over to the darkside m0ti..... FreeDC your home now???

Well for the AT'ers in the bunch, here is what I found with that link:

__________________________

Hello Everyone,

Well a few bug fixes and feature enhancements have been incorporated into the latest version of dfQ.

The "single results file" format from version 1 is no longer used in this version. If you have had problems uploading results from this file (i.e. Uploader did not work for any reason) let me know, and I will release a small service app to upload these results.

From the whatsnew.txt file:

1) Can now shut-down cleanly.
To stop a dfQ application run the appropriate ExitDfQ*.bat file,
or delete the dfQ.lock file in the appropriate directory.

2) Better error-reporting.

3) Finer granuality for file transfers / IO operations.
Costs more in terms of IO, but keeps memory usage down and
can avoid unnecessary duplicates in the case of errors.

4) Supports unlimited size archiving.

5) File-names and formats have been slightly changed from version 1:
- .s_dfq files are now .dfq files
- .dfq files located at the Client are also valid .dfq files
- .dfq files located at the Server MAY be valid .dfq files.
If clients were always successful at uploading files
to the server then they should all be valid
- .dfq files located at the Uploader most likely aren't
compatable with the new .dfq file format
- new archive file: .a_dfq (can be of unlimited length).

Download it here

____________________________________


-Sid

 
Back
Top