regopen.vbs script

  • Thread starter Thread starter RoseW
  • Start date Start date
R

RoseW

I have been using a short cut to this script all along with good results. Now after a
new harddrive, new Xpsp2 install and time consuming reinstalls this vbs script is not
operating in the same manner.
Instead of running - which removes the saving previous state in the registry- it just
opens in notepad.
I downloaded a new copy, created a short cut to the stored vbs - and no joy.
I have used the quick Oe backup utility today and the Karen Noseworthy 'replicator'
both of which are connected to vb6.
Is there some configuration selection that I have neglected to undo or do so vbs
scripts can run?
Rose
 
From a command prompt;

C:\>assoc .vbs
should return with
..vbs=VBSFile

If not
assoc .vbs=VBSFile
to restore the default file type association.


C:\>ftype VBSFile
should return with
VBSFile=%SystemRoot%\System32\WScript.exe "%1" %*

If not
ftype VBSFile=%SystemRoot%\System32\WScript.exe "%1" %*
to restore the default open action for the file type.



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
|I have been using a short cut to this script all along with good results.
Now after a
| new harddrive, new Xpsp2 install and time consuming reinstalls this vbs
script is not
| operating in the same manner.
| Instead of running - which removes the saving previous state in the
registry- it just
| opens in notepad.
| I downloaded a new copy, created a short cut to the stored vbs - and no
joy.
| I have used the quick Oe backup utility today and the Karen Noseworthy
'replicator'
| both of which are connected to vb6.
| Is there some configuration selection that I have neglected to undo or do
so vbs
| scripts can run?
| Rose
|
|
 
NewScience wrote:
| What is the default application that is used for the file extension .vbs?
|
| || I have been using a short cut to this script all along with good results.
|| Now after a
|| new harddrive, new Xpsp2 install and time consuming reinstalls this vbs
|| script is not
|| operating in the same manner.
|| Instead of running - which removes the saving previous state in the
|| registry- it just
|| opens in notepad.
|| I downloaded a new copy, created a short cut to the stored vbs - and no
|| joy.
|| I have used the quick Oe backup utility today and the Karen Noseworthy
|| 'replicator'
|| both of which are connected to vb6.
|| Is there some configuration selection that I have neglected to undo or do
|| so vbs
|| scripts can run?
|| Rose

The file type commands are Open (with notepad) Edit Print and Openwith command
Open is the default command
I don't recall changing the file type previously. ....but recollection can be a dim
thing <grin>
Rose
 
Dave Patrick wrote:
| From a command prompt;
|
| C:\>assoc .vbs
| should return with
| .vbs=VBSFile
|
| If not
| assoc .vbs=VBSFile
| to restore the default file type association.
|
|
| C:\>ftype VBSFile
| should return with
| VBSFile=%SystemRoot%\System32\WScript.exe "%1" %*
|
| If not
| ftype VBSFile=%SystemRoot%\System32\WScript.exe "%1" %*
| to restore the default open action for the file type.
|
|
|
|
| "RoseW" wrote:
|| I have been using a short cut to this script all along with good results. Now
|| after a new harddrive, new Xpsp2 install and time consuming reinstalls this vbs
|| script is not operating in the same manner. <snip>
|| Is there some configuration selection that I have neglected to undo or do so vbs
|| scripts can run?
|| Rose

Okay, did that at the root c:
The ftype VBSFile was required since Notepad returned instead of WScript.exe
But this is what shows up in the File types Open -advanced section
C:\WINDOWSSystem32\WScript.exe "%1" %*
Shouldn't there be a space or backslash after the word WINDOWS?......or the word
Windows not be there at all?
Rose
 
When you run;

ftype VBSFile=%SystemRoot%\System32\WScript.exe "%1" %*

the File Types|Advanced|Actions|Open
should resolve to;

C:\WINDOWS\System32\WScript.exe "%1" %*

(also make sure 'Open' is the default action)

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Okay, did that at the root c:
| The ftype VBSFile was required since Notepad returned instead of
WScript.exe
| But this is what shows up in the File types Open -advanced section
| C:\WINDOWSSystem32\WScript.exe "%1" %*
| Shouldn't there be a space or backslash after the word WINDOWS?......or
the word
| Windows not be there at all?
| Rose
|
|
|
|
 
Dave Patrick wrote:
| When you run;
|
| ftype VBSFile=%SystemRoot%\System32\WScript.exe "%1" %*
|
| the File Types|Advanced|Actions|Open
| should resolve to;
|
| C:\WINDOWS\System32\WScript.exe "%1" %*
|
| (also make sure 'Open' is the default action)
|
|
| "RoseW" wrote:
|| Okay, did that at the root c:
|| The ftype VBSFile was required since Notepad returned instead of WScript.exe
|| But this is what shows up in the File types Open -advanced section
|| C:\WINDOWSSystem32\WScript.exe "%1" %*
|| Shouldn't there be a space or backslash after the word WINDOWS?......or the word
|| Windows not be there at all?
|| Rose

Right, I'll just edit that missing back slash in the default open command for file
type.
Perhaps I missed typing the = sign although I checked and double checked but I was
focused on spaces and quotes.
I'm curious why this specification wasn't in the vbs file type in the first place. I
just discovered if I had looked in my other computer the exact command line is there
but it was good to learn the above method of typing in at the command prompt.
Thanks.
Rose
 
Did you restart the pc after the ftype command?

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Right, I'll just edit that missing back slash in the default open command
for file
| type.
| Perhaps I missed typing the = sign although I checked and double checked
but I was
| focused on spaces and quotes.
| I'm curious why this specification wasn't in the vbs file type in the
first place. I
| just discovered if I had looked in my other computer the exact command
line is there
| but it was good to learn the above method of typing in at the command
prompt.
| Thanks.
| Rose
|
|
 
Dave Patrick wrote:
| Did you restart the pc after the ftype command?
|
|
| "RoseW" wrote:
|| Right, I'll just edit that missing back slash in the default open command for file
|| type.
|| Perhaps I missed typing the = sign although I checked and double checked but I was
|| focused on spaces and quotes.
|| I'm curious why this specification wasn't in the vbs file type in the first
|| place. I just discovered if I had looked in my other computer the exact command
|| line is there but it was good to learn the above method of typing in at the
|| command prompt. Thanks.
|| Rose

Restarting the computer is another bag of worms. I posted a query in the
'perform-maintain' newsgroup and received a confirmation that the pc must go back to
the repair shop for further investigation.
Once I shut it down today it is not being started again until its at the repair shop
tomorrow. I'm having very quick reboot incidences when just starting up. That same
scenario went on the week of Aug11 -then the hard drive died. Now a new hard drive
and 5 days into it and the first time 3 days ago it was so quick I almost missed it.
Today the inevitable black screen with all the words(but no error code) appeared so
THAT'S IT....back for further investigation. Funny thing is- using 'start windows
normally' and we pass the Welcome screen into the desktop. If I go to the 'uncheck
automatic reboot on errors' I get a pop up message saying there isn't enough room in
the page file or to that effect- (the page file is on the second partition ONLY). I
chose to not argue with that pop up message box<grin>
Today was copy and burn files and the repair person can do some sleuthing tomorrow.
Rose
 
Dave Patrick wrote:
| Did you restart the pc after the ftype command?
|
|
| "RoseW" wrote:
|| Right, I'll just edit that missing back slash in the default open command for file
|| type.
|| Perhaps I missed typing the = sign although I checked and double checked but I was
|| focused on spaces and quotes.
|| I'm curious why this specification wasn't in the vbs file type in the first
|| place. I just discovered if I had looked in my other computer the exact command
|| line is there but it was good to learn the above method of typing in at the
|| command prompt. Thanks.
|| Rose

I neglected to say in my previous post that the regopen.vbs script now works -after
inserting the backslash into the command line using the edit section of File type.
Perfect...the registry opens at the top -not the other cluttered presentation.
Thanks for the assistance.
Rose
 
You're welcome.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| I neglected to say in my previous post that the regopen.vbs script now
works -after
| inserting the backslash into the command line using the edit section of
File type.
| Perfect...the registry opens at the top -not the other cluttered
presentation.
| Thanks for the assistance.
| Rose
|
|
 
Back
Top