Search results for query: *

Thanks that did the trick. Reported clipper 5.2 so 5.3 should be fine.

I have an executable that I have been asked to review for possible editing. I have worked with clipper a bit before, but it has been a while. The compiled program is an *.exe but is there anyway to determine what version of clipper I have. I am trying to determine if I should get CA-clipper...

Excellent suggestion it worked perfectly, thank you for the help. What I did was modify the model files I created using the JPRadley patch. The last line in the model files is the visionfs print line. The reason I changed the model files is we have different models for compressed, standard...

In order to clarify what I was talking about the JP Radley patch file can be found at: http://www.aplawrence.com/Unixart/jprdiff.html

I am trying to come up with a way to automatically print to through my windows 2000 Server using visionfs. I know this has been addressed, but this is a little different. I am using JP Radley's patch file to patch my HPLaserJet model to an HPLaserVision model in order to have format control...

Here was the solution to the problem. I got help from Microsoft to solve the problem. There was a corrupt Terminal Services registry key. The following key was corrupt - HKEY\LOCALMACHINE\SYSTEM\CurrentControlSet\Services\TermService. The fix was to import a good key from a working TS server...

yes I am running server in application mode and the license server is up and running and activated. My clients are all Win2K pro and WinXP pro so they don't need a CAL it is already included in the operating system.

Permissions for connection show system, administrator and users with proper controls for each. still can't connect to server. Only other interesting problem is when I disable the connection I get an error " Unable to complete operation, internal error has occurred". Then if I exit TS...

The connection is enabled and have removed and reinstalled once. I will check the permissions in configuration - Thanks.

I have a Windows 2000 server and have installed Terminal Services. It is a domain controller and after installing terminal services I can not make a remote connection or a local connection on the network. When I try to connect I get the standard "server may be to busy, etc." I have run...