Can i assume from the lack of negative feedback, that the latest SCPrompt is a stable release ???JDaus wrote:Update FINALLY released ...
I would like to update the front page and the downloads section of the vnc2me site if this is the case ...
Can i assume from the lack of negative feedback, that the latest SCPrompt is a stable release ???JDaus wrote:Update FINALLY released ...
Am experiencing the same issue Do not like having to right click and run as adminZyxyx wrote:On Windows 7 (32 bits / 64 bits) :
When SCPrompt is built with Build_SCPrompt.exe and the IExpress option, there is an error message when double clicking on the resulting scprompt_0.10.8.41_2010-09-xx_xx-xx-xx.exe
---------------------------
SCPrompt Remote Desktop Control
---------------------------
Erreur de création du processus <C:\Users\%username%\AppData\Local\Temp\IXP000.TMP\scprompt.exe>. Raison : L’opération demandée nécessite une élévation.
> In english : The requested operation requires elevation.
Is there a way to avoid this error message without being forced to run SCPrompt as an Administrator.
Thank you for this great (and still updated...) app !
Zyxyx
So its the builder thats having the problem is it ??? i will add the #requireadmin option when win_7 is detected ... that should then run as admin each time its run ...Zyxyx wrote:On Windows 7 (32 bits / 64 bits) :
When SCPrompt is built with Build_SCPrompt.exe and the IExpress option, there is an error message when double clicking on the resulting scprompt_0.10.8.41_2010-09-xx_xx-xx-xx.exe
...
The requested operation requires elevation.
What GUI version are you using ? what language is your system default ?Frontier wrote:When I start a newly built .exe file, I get a message in my tray saying "app_start_title".
I have gotten 2 new large buttons, saying "connect" and "exit". I used to be able to set the text in those...
Ah! ... i didn't develop the button GUI ... so i guess it has some bugs with some of the latest changes ... i will take a lookZyxyx wrote:Other problem with the Button GUI (same used for my previous bug report) :
If the manual option is selected when building the app, the Manual button is there but it's not possible to enter anything in the 'Support address' and 'Port' fields... so it's not working
Thats using the tools menu from the tray icon that isn't working ??? is that right ???Frontier wrote:if one lets the end-user click "service mode", the only way of ending the session is to go to services on the user's computer and stop the service. If one selects "uninstall service", it still reappears...
Guess not quite yet ... maybe next releaseJDaus wrote:Can i assume from the lack of negative feedback, that the latest SCPrompt is a stable release ???
I always start the builder as Administrator, so there should not be any problem when building the app (I do it with the IExpress option).JDaus wrote:So, its the builder thats having the problem is it ??? i will add the #requireadmin option when win_7 is detected ... that should then run as admin each time its run ...
Ah ... i see ... i will try to work out why this is, if its related to iexpress or an application thing ... off to work now ... will try to look at it tonight ... also i made the builder require admin from vista up (win_7 & win2008 included)Zyxyx wrote:the resulting scprompt_0.10.8.41_2010-09-xx_xx-xx-xx.exe gives the error when started (only tested on Win 7 32 and 64 bits) on the computer I want to control.
So what happens if you just zip up the files and extract them on the clients machine and run scprompt.exe ???Zyxyx wrote:the resulting scprompt_0.10.8.41_2010-09-xx_xx-xx-xx.exe gives the error when started (only tested on Win 7 32 and 64 bits) on the computer I want to control.
I have not actually used the iexpress version ... so i will have to test this these out ...Elroy wrote:1. (the suportee) ... restarted their computer without first exiting SCPrompt, thus leaving the vnc service installed ... deletes all files except winvnc.exe, so ... they get warned about the dangers of not having set a password for vnc.
2. The person has an old buggy version of uvnc installed
Try right mouse clicking on the scprompt tray icon ... you should see a tools menu there now ... force uninstall does similar, but through WMI (i think). This should also be translation ready ...Elroy wrote:sc stop uvnc_service
sc delete uvnc_service
this sounds good, but i am not sure how to do this with autoit ... if you find an example written in autoit (search the forums), let me know, and i will take a look at it ...Elroy wrote:A great solution would be to have a context/popup menu appear when they right click anywhere in the SCPrompt window. In this menu would be a single item "Delete existing uvnc_service", which would execute sc stop and delete commands.
do you have an old XP machine you can test on ???jeffik wrote:Still having some issues making it work locally ... trying to figure out how to open port 5500 on my win 7 64 bit laptop.
that address should work fine for internal pcs, but its not an internet address, so you cannot support external clients ...jeffik wrote:I removed all the ports relating to any VNC and put in a exception for port 5500. Here is a screen cap of my settings manager. the .225 is the Win 7 laptop lan IP.
if you need it desperately ... I can always set it up for you, at a small cost ... otherwise, read through some setup guides for getting sc running, but just skip the parts about setting up the actual program ...jeffik wrote:I have to make this work as I have users i support remotely.
Finally found the problem with this ...Zyxyx wrote:The requested operation requires elevation.
thanks, i will add this to the bugs list, also, thanks for good explanation and stating where else it does actually work ... should make troubleshooting a little easier ...CPC wrote:I’m experiencing the following issue. Visual Effects change crashes/disconnected with no reconnect (on vista / 7).
mostly yes, but i am realy strugling with the button gui manual selection ... have had to change ALOT of code to try to get it working ... still cant get it going ... think it will have to stay as a bug for a while longer ...Zyxyx wrote:Did you solve some of the remaining problems with SCPrompt ?
nope ... Just need to find spare time to get the 42 version built and tested ...Zyxyx wrote:Do you want me to test anything at this point that could help you complete the next stable release ?
Its not dead yet ... but it may take some time to work out (i basically coded myself into a knot trying to work this out ... changing hundreds of lines of code ... and spending the majority of my project coding time on this bug ... in the end, i have taken it back to where we were last release, efectively trashing all that time)Zyxyx wrote:To bad for the manual mode
AwesomeZyxyx wrote:'build_via_batch_nsis.bat' :
Ok ... thanks for the feedback ... looks like i need to add some more variables at the top, to allow for foldername changes, product name changes, and application name changes ... thanksZyxyx wrote:When changing PRODUCT_NAME "Remote-Assistance"), I also had to make some changes to make it work :
First, I had to rename the "scprompt.exe" (in the .\scprompt subfolder) with the name I chose... here : "Remote-Assistance.exe". If I don't, the shortcut created on the desktop is looking for the following file : .\AppData\Local\Remote-Assistance\Remote-Assistance.exe
... and this file doesn't exist !
There is one Remote-Assistance_Uninst.exe and one scprompt.exe, but no Remote-Assistance.exe ... so the shortcut on the desktop is not working (the one pointing to the uninstaller is ok).
Then, in ".\build_resources\scprompt.nsi", I changed :
- line 67
Icon "..\${PRODUCT_NAME}\Logo.ico" > Icon "..\scprompt\Logo.ico"
- line 68
UninstallIcon "..\${PRODUCT_NAME}\Logo.ico" > UninstallIcon "..\scprompt\Logo.ico"
- line 70
LicenseData "..\${PRODUCT_NAME}\License.txt" > LicenseData "..\scprompt\License.txt"
- line 82
File "..\${PRODUCT_NAME}\*" > File "..\scprompt\*"
OK .. this is a problem ... what OS are you using for this ... i tested it on 7, and had no problemsZyxyx wrote:After that, when I try a loopback connection, it's working fine... if I start "Remote-Assistance_0.1.1.1.exe" with admin rights (Right click / Run as administrator).
If I don't, I get an error message from UltraVNC : 'Failed to open service control manager'.
With all the changes you made above, i think something got broken ... try downloading and building what i supplied without any modifications ... think this is your problem here ... above added vars should fix this.Zyxyx wrote:SCPrompt.exe (or Remote-Assistance.exe) is not starting automatically after running "Remote-Assistance_0.1.1.1.exe" ; I have to start it manually via the shortcut created on the desktop (not very user friendly > three manipulations : download, install, run).
Hmm ... don't understand this one ... will have a look locally to see if i can get it to workZyxyx wrote:I also changed the 'Logo.ico' but it's only used for the uninstaller (and its shortcut on the desktop) ; not for the SCPrompt / Remote-Assistance.exe, still using the SCPrompt logo.
Yes ... as this is set within scprompt.exe ... not within the "Builder" ... the builder version should reflect the real scprompt version ... when i roll these into the builder, this will work fine, as the version will be taken from scprompt rather than manually editing in the NSIZyxyx wrote:Other cosmetic details :
When you leave your mouse over the SCPrompt icon in the traybar, you see the SCPrompt version '0.10.11.43' and not the custom version set in the scprompt.nsi (!define PRODUCT_VERSION "0.1.1.1").
LOL ... thanks, haven't gone through the translations and revised them ...Zyxyx wrote:+ when starting = 'SCPrompt 2010' baloon/tooltip in the traybar
+ when exiting = 'VNC2Me Prompt 2009' baloon/tooltipin the traybar
Thanks ... i forgot it was in there ...Zyxyx wrote:One more thing : in the 'SCPrompt2010_roll-your-own_0.10.11.43\scprompt' subfolder, I think that the scprompt.exe shortcut can safely be removed for the next build.
yes ... they are setup in the NSI includes, and i am not sure how to disable it at the moment ... NSIS is a massive beast of a thing, and i spent hours learning what i needed to get the script to run as it does ... as time goes on, i will learn more, and improve it more ...Zyxyx wrote:FYI, when running "build_via_batch_nsis.bat" with the above modifications, here is what I get :
13 warnings:
SCPrompt is built so that the latest server / viewer version can be used, simply by replacing the winvnc.exe (in the scprompt sub folder). your welcome to update to the latest beta of UVNC ...Zyxyx wrote:Do you plan to use the new UltraVNC 1.0.9.2 with the next SCPrompt build ?
awesome, great work, i should have solved this one, i will build a version in the next few days, and get you to test it furtherZyxyx wrote:The 'Failed to open service control manager' error appears... but only on Windows 7 64 bits (tested OK on Windows Vista 32 bits and on Windows 7 32 bits > no error message). Same error after replacing the winvnc.exe from UltraVNC 1.0.9.3 (and using the latest viewer, of course).
hmmm ... will have to look into this one. as logo.ico should be the default for all GUI windows (but it does not replace the icon in the exe file...)Zyxyx wrote:I can confirm that the 'Logo.ico' is only 'applied' to the uninstaller (and its shortcut on the desktop) but not for the SCPrompt main program..
i have already updated the NSIS script to have additional variables at the start. this will get posted with the next update ...Zyxyx wrote:I hope you'll find some time to fix/adapt and then implement this NSIS script in your builder... it's going to be a great instant support solution for many people waiting for a reliable one for a long time.
I can see that but is it the expected behavior for future releases too ? Will it be possible, at some point, to automatically replace the icon in the exe file or will we still have to use a resource editor like this one ?Logo.ico should be the default for all GUI windows (but it does not replace the icon in the exe file...)
Anythings possible ... but unlike chunkvnc and others, the application is "Build" when shipped ... you just "zip" or "package" the directory to allow the client to run an EXE, and it extract and run scprompt.Zyxyx wrote:Will it be possible, at some point, to automatically replace the icon in the exe file or will we still have to use a resource editor like this one ?
There are no stupid questions ...Blizzard1234 wrote:this is a stupid question - how do I setup and configure SCPrompt
Yep ... thats the purpose of the manual button ... if all you want is manual mode ... download the latest RTR, extractJ0H4N wrote:Is it possible to configure the Manual button so that a user is able to write the adress in the field "Support address" when he starts the program?