I have been trying to use fopen as well as other fXXX commands to open a current .was file, move the cursor position to a specific line, capture everything on that line (lets say that line only contained the text [s1 = "oldpassword"] without the brackets) and assign that text to a string (we will call the string "oldline"). I would then replace everything on that line using fputs with a different predetermined string (lets say the string name was "newline" and it contained [s1 = "newpassword"] without the brackets). I will then use strcat to edit the "oldline" string I captured to look like this [;s1 = "oldpassword"] without the brackets, and call this newly created string "updtdoldline". I want to then move the cursor to the bottom of the script, to a line after the endproc command. I will there overwrite the contents of that line with the "updtdoldline" string. Basically what this script is going to be is a password change script. It will allow the user to edit a "password" file that sets a global variable to what the users password is. I use the same password for different switches. So far I can only get the script to work if I use multiple [if fgets 0 XXXXXX] commands in a row (however many needed to get to the desired line..). I know there has to be a way to go to a specific line number, but I cant figure it out. I dont want to use just a character number because that would change based on what the previous string lengths were (a username string is the line before in the password script). Below is the current "password" script format I have been using. I "modified" my approach for this new script I am trying to create while I was typing this post, so I will post my password change script once I have applied the changes I want to make. How do I get the script to move the cursor position to a specific line????
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How to change the Line Number accessed during a "fopen" session
- Thread starter matt1981m
- Start date
- Thread starter
- #2
- Thread starter
- #3
here is my "password" script...
everytime i try this now i get the following as a result (note: i entered MYNEWPSWD as the new password....
this is what i should see
what should i do?!?!?!?!?!
here is my password change book....for those who are pay close attention to this script... i dont have the username change section scripted yet. i wanted to atleast get the password section done first...MAIN_SCRIPT.WAS said:
CHNGPSWD said:
everytime i try this now i get the following as a result (note: i entered MYNEWPSWD as the new password....
INCORRECT RESULT said:
this is what i should see
DESIRED RESULT said:
what should i do?!?!?!?!?!
Unless each line in the file is a constant length (i.e. all lines are 20 characters line), the only way to get to a specific line is to use multiple fgets commands. If each line were the same length, you could use the fseek command to jump the appropriate number of characters into the text file.
- Thread starter
- #5
Looking back at your original message, what you are basically needing to do is update the password that is hardcoded in the script, correct? If so, it may be easier just to have the script read the password from a separate text file than have to modify the script when the password changes. This could be something as simple as having one text file per device with the password, one text file with all device name and passwords (along with a way to find the correct line and read the password), up to using DDE with an Excel spreadsheet to read passwords from the spreadsheet.
- Thread starter
- #7
i thought of that way but i would prefer to do it this way... i just go into the password script and update it manually.... the problem is that other people i work with use the scripts... i have had to edit "broken" scripts too many times because of someone deleting the wrong thing when they update their password.... this would be nice, simple, and fool proof....i would think that there would be a way to tell the script to go to line 6 and replace line 6 with XXXX text....you would think that would be possible...lol
It is possible, just a bit tricky. You would need to use fgets six times to get to that line (could have it in a loop), then you would use the rewind/delblock/insblock commands to replace the old line with the new line. I have a couple sample scripts on my site that show how to do this.
- Thread starter
- #9
Try using the profileWr and profileRd to read or write the old or new passwords.
Manually edit your main_script.was to look like this noting the necessary absence of spaces around the '=' operator.
#comment
[pwTopic]
#endcomment
proc main
set duplex 0
s0 = "currentusername"
s1="MYNEWPSWD"
pwtitlebar "Logging into Passwerks..." PERMANENT
endproc
#comment
oldPW="currentpassword"
#endcomment
Then in whatever script you use to read or write these values, use the following code:
string mainScriptFilePath = "main_script.was" ;
string oldS1
string newPassword
string prevOld
;To read the old password from oldPW -
profilerd mainScriptFilePath "pwTopic" "oldPW" prevOld
;To read the current password from s1 -
profilerd mainScriptFilePath "pwTopic" "s1" oldS1
;To write oldS1 value to oldPW -
profilewr mainScriptFilePath "pwTopic" "oldPW" oldS1
;To write a new password to s1 -
strquote newPassword ;Enclose in double quotes. <--<<<
profilewr mainScriptFilePath "pwTopic" "s1" newPassword
The beauty is that there is no manual file operations like: opening, closing, searching, deleting or inserting blocks, checking string length, etc.
The #comment and #endcomment pairs are to "hide" what is needed for profilewr/rd from the compiler so you can use your .was file as, what is traditionally called, a .ini or config file.
...To the profilewr/rd commands, main_script.was "looks like" this:
[pwTopic]
s1="MYNEWPSWD"
oldPW="currentpassword"
... and to the compiler, it looks like this:
proc main
set duplex 0
s0 = "currentusername"
s1="MYNEWPSWD"
pwtitlebar "Logging into Passwerks..." PERMANENT
endproc
Manually edit your main_script.was to look like this noting the necessary absence of spaces around the '=' operator.
#comment
[pwTopic]
#endcomment
proc main
set duplex 0
s0 = "currentusername"
s1="MYNEWPSWD"
pwtitlebar "Logging into Passwerks..." PERMANENT
endproc
#comment
oldPW="currentpassword"
#endcomment
Then in whatever script you use to read or write these values, use the following code:
string mainScriptFilePath = "main_script.was" ;
string oldS1
string newPassword
string prevOld
;To read the old password from oldPW -
profilerd mainScriptFilePath "pwTopic" "oldPW" prevOld
;To read the current password from s1 -
profilerd mainScriptFilePath "pwTopic" "s1" oldS1
;To write oldS1 value to oldPW -
profilewr mainScriptFilePath "pwTopic" "oldPW" oldS1
;To write a new password to s1 -
strquote newPassword ;Enclose in double quotes. <--<<<
profilewr mainScriptFilePath "pwTopic" "s1" newPassword
The beauty is that there is no manual file operations like: opening, closing, searching, deleting or inserting blocks, checking string length, etc.
The #comment and #endcomment pairs are to "hide" what is needed for profilewr/rd from the compiler so you can use your .was file as, what is traditionally called, a .ini or config file.
...To the profilewr/rd commands, main_script.was "looks like" this:
[pwTopic]
s1="MYNEWPSWD"
oldPW="currentpassword"
... and to the compiler, it looks like this:
proc main
set duplex 0
s0 = "currentusername"
s1="MYNEWPSWD"
pwtitlebar "Logging into Passwerks..." PERMANENT
endproc
- Thread starter
- #11
- Thread starter
- #12
i still cant get it to work... here is my update password script.... i even added a "usermsg oldS1" command after the script is supposed to read the MAIN_SCRIPT.WAS file and capture the s1 string as oldS1...the dialog box that shows up is blank instead of having the string....
and here is my main password script....
CHANGEPASSWORD.WAS said:
and here is my main password script....
MAIN_SCRIPT.WAS said:
- Thread starter
- #13
i got it to work.... i saw this in the aspect help files
i then edited the string mainScriptFilePath = "MAIN_SCRIPT.WAS" to point to the default script path and got it to work... the only problem i could see is if the user had a different script path than specified it wouldnt work. i had a great idea though, i used fetch scriptpath dfltpth to capture the default script path and assign it to the dfltpth string... it then added a forward slash by using strcat dfltpth "\". i then used strcat dfltpth mainScriptFilePath and then mainScriptFilePath = dfltpth to set the mainScriptFilePath string to the full path based on the individual users settings... i know i made this a little more complicated than it had to be, but i am a difficult person, so it is ok...lol
here is my final (AND WORKING!!!!!!!!!!!) password change script. Thanks to ambl and knob who replied to my archaic request, and to my gf for not getting mad when i ignored her the past couple weeks while trying to figure this *&($*&$ script out...
profilewr said:
i then edited the string mainScriptFilePath = "MAIN_SCRIPT.WAS" to point to the default script path and got it to work... the only problem i could see is if the user had a different script path than specified it wouldnt work. i had a great idea though, i used fetch scriptpath dfltpth to capture the default script path and assign it to the dfltpth string... it then added a forward slash by using strcat dfltpth "\". i then used strcat dfltpth mainScriptFilePath and then mainScriptFilePath = dfltpth to set the mainScriptFilePath string to the full path based on the individual users settings... i know i made this a little more complicated than it had to be, but i am a difficult person, so it is ok...lol
here is my final (AND WORKING!!!!!!!!!!!) password change script. Thanks to ambl and knob who replied to my archaic request, and to my gf for not getting mad when i ignored her the past couple weeks while trying to figure this *&($*&$ script out...
CHANGEPASSWORD.WAS said:
- Status
Similar threads
