Not so strange. The editor does it's file transfer independently of the terminal window. You can load edit, format, and save source code without logging the terminal window in.
It's strange that you've used uniobjects in the past and it's no longer working - or have you just never used it with UniDebugger. My servers are windows based so I usually use the disk option but I've used UniObjects when I want to make sure the source code item is locked. If the server name/address or the account is invalid I get an Unable to connect to host message. If the user/password is incorrect I get an Invalid user name or password message. If the file is incorrect I get an unable to open host file message. So it looks like the user/password you are using on the "editor" side isn't valid or doesn't have the correct permissions to access the account. I did have some trouble with an example project that I got from IBM not liking certain characters in the password. I haven't seen that type of trouble with the UniDebugger but at this point it's worth a shot.... Colin Alfke Calgary, AB >-----Original Message----- >From: Shawn Waldie [mailto:[EMAIL PROTECTED] > >This is what's so strange. I can log in through other "windows". > >I have UniDebugger running right now, and I can access my source code >through the wIntegrate pane (on the right). However, I get the error >message when I attempt to access my source code with the >editor pane (on >the left). I've always used uniobjects in the past, but ftp won't work >either. I can even telnet in from the cmd line of my workstation. ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
