CVS for Dreamweaver 2004 slash problems

I’m trying out your CVS for Dreamweaver extension and I’m having a problem checking out a module.
The systems/versions I’m using
Windows XP pro
Dreamweaver 2004 vs 7.0.1
Cvs lite 1.3.0 extension installed in dreamweaver
CVSNT ver 2.0.41 installed and in widows path

I’m connecting to a unix CVS server using pserver with the following configuration in CVS for dreamweaver
Protocol – Password server (:pserver)
Server – MyCvsIP (an internal company IP, does work with other applications)
Port – no port needed
Repository folder - /usr/local/rep
I tried using the “/” at the end, but that returns an error of “cvs [checkout aborted]: /usr/local/rep/: no such repository” My CVS administrator told me I need to have the “/” at the end removed from the command line that CVS for Dreamweaver put in there.
When I remove the ending slash I get the error displayed below.

Username – set correctly
Password – set correctly
Temp dir for log files set to: “C:\temp\”

When doing a CVS checkout settings are the following:
Project Name: projectname – this is the correct project name, used in other cvs applications
Local working dir: “C:/temp/”

The error that is returned is:
cvs checkout: Server attempted to update a file via an invalid pathname:
cvs [checkout aborted]: 'C:\temp\cms/'.

Here is the CVS command line that is run:
cvs -d :pserver:MyUserName:MyPassword@MyCvsIp:/usr/local/rep checkout -d "C:\temp\projectname" "projectname" >C:\temp\/out.txt 2>C:\temp\/err.txt

It is adding in the “/” not only in the log text file path but also somehow in the local working folder path.

Please let me know what I can do to correct this.
Thanks

We are working to solve this problem.

Any news on this? Trying to Evaluate the software, and can't begin to do that until this is fixed.

I'm just checking back at this thread periodically to see if the issue has been addressed.

We hope next week in a release for this problem.

any word? bit by the same bug.
jb

sorry, thinking it was the 28th (vacation) it's not next week yet is it?
jb

We posted yesterday version 1.3.1, please try to download.

We have modified CVS for Dreamwever and the modified version is ready to download from our website.

What we have changed:

We have added in SSH connection :ext:, so now users can choose between :ssh: or :ext: connection.
On all of our server configured with CVSNT Client, we used :ssh: connection, but seems that some users need still to choose :ext:

On Configuration screen we have added on PATH a possibilities to use or not an ending SLASH on pathname.
If for you have not worked until now CVS4DW (mostly on PSERVERS), please try it now, we hope should work.
We are still looking for users for who is not working, to help us to find out why.
If you are one of this users and you can give to us access to a PSERVER or a VNC connection to your computer, please contact us at it@grafx.ro.

I have the same issue with the path adding the "\" to the end.
I see the updated check box for enabling the path, but it doesn't seem to do anything.
If I select it, and close the window, it is not selected when I reopen the config options.

Unfortunately, I cannot give you access to the server, but I am interested in a fix.

Thanks

Seems that this is happening on some PSERVERS, not on all of them and we cannot find a way to reproduce it, on our own server is working fine.
Unfortunatelly we cannot fix it until we cannot reproduce, even if we want it.
We hope that someone can help us and give an access to their PSERVER where this problem popup.

I cut and pasted the info sent to the server, directly in cvs from the command prompt, and had the same issue still. The problem seems to be in CVSNT itself.

Did you installed CVS4DW with new CVSNT installer from us?
Please download that version and let me know.

yes, I just tried that installer, and the result is the same. Is the underlying CVSNT the same? Or has it been edited to remove that slash?

CVSNT is exactly the same. Binary version from their site.
If you want to execute with CVSNT executable, same result???

Yep. I get the same errors when I try to run from the command line directly in CVSNT.

Yep. I get the same errors when I try to run from the command line directly in CVSNT.