Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

No REG association thanks to Script Sentry messup

Jun 25, 2004 10:16PM PDT

For some reason, Jason's Toolbar Script Sentry (SS) is not working http://reviews.cnet.com/5208-6142-0.html?forumID=45&threadID=25992&start=0
Messages at his forum are unanswered http://www.jasons-toolbox.com/Forum/topic.asp?TOPIC_ID=278 so far.

I tried uninstalling SS, but it is still there (?????)
Now when I try to open a REG file (merge) I get the "no association dialog). If I try to associated it with SS (yup, it is still here even though I ran the uninstaller and deselected it from MSCONFIG/ startup) I still get the error message. (error 53)
What other application do you associate the REG file if you want to merge it.

As to the file I trying to merge, it is Spyware Block List files (yues, there are other things I can do to immunize, but I am more interested in having the computer work correctly)

any ideas?

Discussion is locked

- Collapse -
Re: No REG association thanks to Script Sentry messup
Jun 26, 2004 12:30AM PDT

I do not know what Jason's Toolbar Script Sentry (SS) is supposed to do or did, perhaps the following will give you some ideas to check.

Description of the Microsoft Windows Registry (Q256986) - all MS operating system versions

1. The Registry Editor is an advanced tool for viewing and changing settings in the system registry. Windows stores configuration information in a database (the registry) organized in a tree format. Although the Registry Editor enables inspection and modifying, it is normally not necessary.

Note: The two most important things to know are that the system registry copies changes immediately and there is no Undo command. The editor does not wait for a Save to be issued since it does not have one, therefore making changes permanent as they happen -- you make a change it's gone forever unless you remember it or have already backed up a copy. Use the editor sparingly and soberly, and do not leave it open unnecessarily.

2. The article [Q318159] explains that when a registry hive becomes damaged, your computer may become unbootable, and you may receive one of the following Stop error messages on a blue screen. Damage often occurs when programs with access to the registry do not cleanly remove temporary items that they store in the registry. This problem may also be caused if a program is terminated or experiences a user-mode fault -- one created by the user:

Unexpected Shutdown
Stop:0xc0000135


3. The article [Q307545] describes how to recover a Windows XP system that does not start because of corruption in the registry and assumes that normal recovery methods have failed and access to the system is not available except by using Recovery Console. If an Automatic System Recovery (ASR) backup exists, it is the preferred method for recovery and it is recommended that you use the ASR backup before utilizing this procedure. This procedure does not guarantee full recovery of the system to a previous state; however, you should be able to recover data when used.

4. Please note that on occasion it may be come necessary to utilize the older Regedit32, run the same as Regedit, when access issues a denial permissions.

5. Supplemental reading:

a. "Prevent Regedit.exe from Using the Last State (Q244004)."

b. "The Registry Keys and Values for the System Restore Utility (Q295659)" describes certain keys pertaining to System Restore which must not be edited under any circumstances.

c. "HOW TO: Back Up, Edit, and Restore the Registry in Windows XP (Q322756)."

6. Five "Administrative Templates ship with Windows XP SP1" which includes more than 600 settings with over 100 new settings, and must be manually configured in the Computer Configuration in the Group Policy Object Editor to apply them.

7. The Prevent access to registry editing tools setting disables the Windows registry editors Regedit.exe and Regedit32.exe. Enabling this setting causes a message to appear when the user tries to start a registry editor, informing him or her that s/he cannot use them. This setting prevents users or intruders from accessing the registry using these tools, but does not prevent access to the registry itself.

8 "HOW TO: Use the Group Policy Editor to Manage Local Computer Policy in Windows XP (Q307882)."

- Collapse -
Re: No REG association thanks to Script Sentry messup
Jun 28, 2004 3:13AM PDT

Reassociate with Regedit.exe by opening a command prompt ( also sometimes called a DOS Window or DOS Prompt) and typing in the following:

assoc .reg=regfile

Double clicking a .reg file should now merge as expected.

- Collapse -
Thanks you very much! I will try that tonight! (nt)
Jun 28, 2004 3:46AM PDT

.

- Collapse -
I tried your suggestion, but it didn't change anything
Jun 28, 2004 8:30PM PDT

I copied and pasted assoc .reg=regfile at a command prompt, but when I tried to merge a *.reg file, I got a screen asking which application I wanted to use. (TW, I ran SFC the other day). Any other clues?

- Collapse -
What does it show if you...
Jun 29, 2004 2:57AM PDT

simply type ASSOC at the command prompt?

Should list all associations and you should be able to find .REG among them.

Without knowing more about the "Script Sentry" and how it functions I would guess that possibly it write protects portions of the registry OR changed any association changes back to whatever it sets them to.

Might want to contact the author.

In the meantime if you must merge a .REG file try opening REGEDIT and clicking on the Registry menu then the Import Registry File... then select the file and clisk OK.

What happens if you doubleclick the .REG file you want merged? Merging it is the default action.

- Collapse -
Answers in line
Jun 29, 2004 7:35AM PDT

simply type ASSOC at the command prompt?

ANSWER .reg=regfile

Without knowing more about the "Script Sentry" and how it functions I would guess that possibly it write protects portions of the registry OR changed any association changes back to whatever it sets them to.

ANSWER Up until recently, it warned you before running any script. Every time I tried to Merge a reg file, it ran properly. Not any more Sad

Might want to contact the author.

ANSWER Tried via his forum, no answer (see my first post)

In the meantime if you must merge a .REG file try opening REGEDIT and clicking on the Registry menu then the Import Registry File... then select the file and clisk OK.

ANSWER Thanks!

What happens if you doubleclick the .REG file you want merged?

ANSWER "This file does not have a program associated with it for performing this action. Create an association in the Folder Options control panel"

Merging it is the default action.

ANSWER Not any more!

Any clues?

- Collapse -
Re: Answers in line
Jun 30, 2004 6:53AM PDT

1. You could just keep using the work-a-round of opening REGEDIT and importing the file.

2. You could reinstall the "Script Sentry" and hope it works.

3. You could follow the directions presented by the error message and create an association. This link will (or should) provide you the necessary guidance for creating the association but be sure to set the default action to MERGE.
http://www.uksecurityonline.com/husdg/windowsxp/reg.htm

4. You might try using FTYPE.EXE to see what regfile is currently associated with (command is FTYPE regfile) It should tell you regfile=regedit.exe "%1" but probably won't. If it doesn't tell you that try using ASSOCIATE .reg REGEDIT.EXE /f (of course you will need to have those two utilities available in order to use them--if you don't try a google search or go here http://www.lynchburg-classified.com/NTReskit/ for ASSOCIATE.EXE

- Collapse -
Re: Answers in line
Jun 30, 2004 7:09PM PDT

4. You might try using FTYPE.EXE to see what regfile is currently associated with (command is FTYPE regfile) It should tell you regfile=regedit.exe "%1" but probably won't.


C:\Documents and Settings\Owner>ftype regfile
regfile=


If it doesn't tell you that try using ASSOCIATE .reg REGEDIT.EXE /f (of course you will need to have those two utilities available in order to use them--if you don't try a google search or go here http://www.lynchburg-classified.com/NTReskit/ for ASSOCIATE.EXE


I went to this link, downloaded associate.exe and when I clicked it a Command prompt opened and closed under a second, then when I pasted your command link I got this error
C:\Documents and Settings\Owner>ASSOCIATE .reg REGEDIT.EXE /f
'ASSOCIATE' is not recognized as an internal or external command,
operable program or batch file.

C:\Documents and Settings\Owner>


BTW, thanks for the tip on merging a reg file, at least I now know how to work around this annoyance. Nonetheless, I'd like to fix this. You're doing a great job walking me through this, I'm almost here, please help me get this finished!

- Collapse -
Re: Answers in line
Jul 2, 2004 7:03AM PDT
went to this link, downloaded associate.exe and when I clicked it a Command prompt opened and closed under a second, then when I pasted your command link I got this error
C:\Documents and Settings\Owner>ASSOCIATE .reg REGEDIT.EXE /f

'ASSOCIATE' is not recognized as an internal or external command, operable program or batch file.

All that means is that wherever you placed the ASSOCIATE.EXE file it is NOT in the path statement. MOVE Associate.exe to your %windir%\system32 directory and it will run fine. Command line programs/utilities should be run from the command line because normally they require variables to be added to do anything.

- Collapse -
Couldn't reply to your last answer, but...
Jul 2, 2004 8:26AM PDT

I moved associate.exe to my system 32 folder, then double clicked, copied your instructions whose results appear below

(I truly appreciate the way you are holding my hand and walking me through this mess!, thanks!)


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>FTYPE regfile
regfile=

C:\Documents and Settings\Owner>ASSOCIATE .reg REGEDIT.EXE /f
'ASSOCIATE' is not recognized as an internal or external command,
operable program or batch file.

C:\Documents and Settings\Owner>

- Collapse -
Re: Couldn't reply to your last answer, but...
Jul 2, 2004 10:00AM PDT
I moved associate.exe to my system 32 folder, then double clicked, copied your instructions whose results appear below

You do not double click the associate.exe to run it. It is a command line program that needs to be run from the command prompt just like assoc or ftype. Forget it for now and do the following EXACTLY in the order given.

Try this.

1. OPEN A COMMAND PROMPT (can do this by clicking Start | Run and typing in CMD.EXE)
2. enter the command assoc .reg=regfile
3. enter the command ftype regfile=regedit.exe "%1"
4. enter the command ftype regfile (should get back regfile=regedit.exe "%1" and association should be repaired)

5. Double click on your .reg file and you should get the successful merge message box.


IF that still was unsuccessful you can locate the file named SHELL.INF (should be in your %windir/inf directory). Once located right click on it and select INSTALL. This is not to be undertaken lightly as it resets ALL file extensions to their defaults and you would have to go back and reset associations if you have preferred apps associated with specific extensions.

Have fun.

- Collapse -
Can't reply to other posts, but THANKS!!!!!!!!!!!!!!!!!!!!!!
Jul 2, 2004 11:24AM PDT

That was it! You are the best!!!

I've been at CNET for a few years now, and I don't recall seeing you around. Did you have another name before the change over...or are you relatively new? In any event, I really appreciate the time and effort you put into my problem. I know answering problems can be frustrating at times (I like to help out where I can), but you really stood by me. Thanks a million!

I am going to remember you in my will!

As a matter of fact, I wm going to ask my attorney to add the following line to my will

"...I remember Edward O'Daniel!"

Thanks again!!

- Collapse -
You are welcome...
Jul 3, 2004 5:54AM PDT

I am still a little curious as to why ASSOCIATE.EXE did not work for you, but there are always at least two or three different ways to skin a cat.

I guess I am not exactly a "newby" as I go back, with the same name, to when the Ziff Davis forums were hosted on Compuserve and a 300 or 1200 baud modem were de rigueur as the 2400 baud high speed modem was still in the $500 price range (and Compuserve did not yet support the high speed anyway).

I don't post that often in the "Newbies" forum as I do forget sometimes that what is (or should be) an autonomic knowledge of the command prompt hasn't been learned by most here.