copying to the system32 folder

[the_net_2.0]

All,

Would anyone have a short explanation of what attributes the system32 folder are in windows vista? I'm having a heck of time trying to figure out how to 'configure' it. From what I've read on other forums, in Vista and window 7 what Microsoft has done now is tried to protect it more so people don't tinker with the the files in there.

I am trying to register a dll so I can use it and an ocx file in an application and I cannot transfer the dll to the system folder. This is not the only time this has happened for me. And apparently the files do transfer in when I copy and paste them, but I cannot see their listings regardless of whether I have the 'show hidden files and folders' option turned on from the cp. I know that they are there because when I try to transfer any sort of file in a second time, the 'overwite' confirmation boxes pops up.

I also read on another forum somewhere that you cannot copy and paste dll files in the windows explorer anywhere so you have to drag and drop them if you want to move them. But this results in the same effect as I'm seeing with the copy/paste effort.

would someone be willing to offer me an explanation of how I can 'shut off' the protection that is happening on my machine? I don't know much about this sort of thing but I'm willing to learn. Thanks a bunch for any assistance you guys can give me!

 

[HiTechCoach]

If you are trying to register a DLL then you do NOT need to copy it to the system32 folder.

When you register the DLL you give it the path so there really is not need to place the file in the system 32 folder.

If it were mine, I would place the DLLs in my own folder in under the program files folder.

 

[the_net_2.0]

If you are trying to register a DLL then you do NOT need to copy it to the system32 folder.

When you register the DLL you give it the path so there really is not need to place the file in the system 32 folder.

If it were mine, I would place the DLLs in my own folder in under the program files folder.

thank you for the clarification boyd. However, some things that I do are necessary for efficiency. For example, on my laptop, I created a shortcut icon for the destop, named it "d" and put it in the system32 folder. that way, if I have 10 windows up and they're all maximized, I don't have to find a small grey area in the taskbar to right click so I can see the ''show desktop'' command...all I have to do is type 'd' in the command prompt. Much quicker.

The only reason I ask this is because I'm experimenting with a db right now that came with a DLL and OCX files that were creating by a third party and their instructions say to put the DLL in the system32 folder.

It is a legitimate distribution, so I am not worried about anything.

This problem though is only happening on my TV, which uses a 64 bit vista machine. my laptop is 32 bit vista, and I've never had the problems I've described here with that one. Although I guess I should get a new backlight for it, considering that the screen is completely black now!

 

[HiTechCoach]

For example, on my laptop, I created a shortcut icon for the destop, named it "d" and put it in the system32 folder. that way, if I have 10 windows up and they're all maximized, I don't have to find a small grey area in the taskbar to right click so I can see the ''show desktop'' command...all I have to do is type 'd' in the command prompt. Much quicker.

there is even a quicker way that is built into XP and later

Why not jut use the built in short cut keys:

Windows-Key + m - minimize all

Windows-Key + M (+shift + m) - maximize all

There there is also the task switcher.

Windows 7 makes life even easier with Jump list.

I rarely go to the destkop. Even in XP.

 

[the_net_2.0]

thanks much! that's all I needed, but it doesn't answer the question of course.

I am still looking for an answer. If all else fails I'll call go daddy and ask them. Heck, they've done so much for me by now that I should by stock in the company!

those shortcuts are very useful. didn't even know they existed. I will for sure use them from now on. thanks.

 

[HiTechCoach]

Forgot the part about the DLLs.

Unfortunately a lot of developers have administrator permissions on their PC. They do not properly follow the windows standards when development there DLL. They also do not properly test the deployment of their DLL.

See:
Location of custom DLL for use with MSAccess


I never touch the sytem32 folder when creating custom DLLs. There is no need. I would treat this folder as for Windows only.

Id you want to cre4te custom shortcuts that you can run form the command prompt then what I would highly recommend is that you place them in a custom folder. Add this folder to the environment variable %PATH%