Re: Copying extended files between systems

[ Follow Ups ] [ Post Followup ] [ Forum ]

Posted by Grant Foraker on August 05, 2013 at 12:13:42: Uploaded files: 2

In Reply to: Re: Copying extended files between systems posted by Bob A on August 05, 2013 at 09:51:00:

GDOSCOPY is a replacement for the old Qtilities option 32. It's all windows controls and no Comet DOS functions.

Good for Comet16 & 32.
CometAnywhere is blocked for now.
Tested for wide screens at 1440, and 1920. 1024 is workable.
Using RDP you can copy files over the internet. Good for something quick and small.

Unzip the attached ZIP somewhere.

In Comet use Qtilites option 32 (ironic?) to copy the files into Comet.

#PATH is where the last/default Windows/DOS path is kept. The file comes empty and a "Folder" dialog will come up the first time. I have multiple #PATH's spread around so that I can have different defaults for different customers.

GDOSCOPY can be on any DIR. REL and UTL would be bad choices. I have a common DIR that I use for this purpose.

GCOPY.DLL can be in the same DIR as the OBJ but it isn't required. GDOSCOPY uses Comet to find the DLL.

GDOSCOPY uses (CopyFile) and is quite fast. A 1GB file on my developer PC takes about 60 seconds to copy from inside Comet to a folder like C:\Export. The copy back takes about the same time. By going out and back, you can achieve a "fastcopy" and avoid the slowness of CometEx or the old Qtilities COPY.

Caveats - GDOSCOPY does not rebuild a file the way CometEx and COPY would. It doesn't LOCK the file while it's being copied. So, you could have synchronization problems with the copied file.

Follow Ups:

Post a Followup



What is the name of the main Signature System's Product?  


Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):

Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.

[ Follow Ups ] [ Post Followup ] [ Forum ]