(1) Problem with DCC-E2 v1.20 to assign DM800 (initial) password with telnet from within DCC-E2 v1.20.
- Situation when starting DCC-E2 v.12 application : Network window: Login=root Passwd=dreambox.
- Problem description:
* When I typed "passwd" in the DCC-E2 Telnet session, the DCC-E2 program did not give control to the user after the (first) prompt "Enter passwd", but apparantly (=my guess) sends immediately a "return" control character. The result is that the (second) prompt "Re-enter passwd" appears immediately, and only then control is given to the user so that he can enter the password of his choice.
* Because the user never gets a chance to enter his password at the first prompt "Enter passwd", the password assignment procedure fails.
- My workaround : I used PuTTY program to assign DM800 password.
(2) Problem to stop DCC-E2 v1.20 after an (initial) password change.
- Situation when starting DCC-E2 v.12 application (after the DM800 password change with PuTTY): Network window: Login=root Passwd=dreambox (= this is how it worked before)
- When DCC-E2, the connection failes, which seems normal because in the DCC-E2 Network window, the Login fields are still the (original) defaults: Name=root Passwd=dreambox.
- After I changed in the DCC-E2 Network window the Login Passwd field to the new password value and made a Reconnect, the connection succeeded, and I was able to use FTP Commander and Recordings, but I was unable to stop DCC-E2.
- Problem description:
* When I want to stop the DCC-E2 program, either by the "Exit" button or by the "Close" [X] icon, nothing happens: the program refuses to stop (no message neither).
* +/- 30 sec after hitting the "Exit" button, I see the green "FTP connected" icon changing to red "FTP (dis)connected, ("Telnet connected" remains green).
* The only way to stop the DCC-E2 program is to do a kill of the application in Windows Task Manager (End Task Dcc_e2 -> "Program not responding" message).
- My workaround: I manually entered a line "Password=" at the end of the [Network] section of the dcc.ini file.
(I came upon this solution when comparing the dcc.ini files of both DCC v2.95 and DCC-E2 v1.20; DCC v2.95 had no problems to stop correctly during the first run after the (initial) password change.
Because DCC v2.95 was able to stop correctly, the wrap-up was done and I guess it is then that the Login Password field is saved in the dcc.ini file).
b2a8ae9291