I don't know of any way to change any value in HKLM from a normal user account that does not have admin rights. The only thing I can think of would be for someone with admin rights, to change the permissions on the HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services to allow modify rights to a particular group and then be sure the user is in that group. That may work but I've not tried it. 'Permissions...' is in the right-button context menu in RegEdit.

A normal user does not have authority to modify/add existing values in HKLM so if you are specifying KEY_READ | KEY_WRITE as 'samDesired' the RegOpenKeyEx will fail. If you are only going to read leave off the KEY_WRITE, but if you need to modify the value, put it somewhere other than HKLM. This is why most software has to be installed by someone with admin authority; most software installs write to HKLM.

No. That's the best solution we found for speed.

We too ran into a similar problem. We are streaming video over USB 2.0 from a cell phone to a PC as the device plays a video or pans with camera. We ran into a problem where the system could not keep up. So we tried using a memory mapped file instead of using the old standard CreateFile() and WriteFile(). That did speed things up to where we could capture data at 40 frames a second but we still have an issue at 80 fps.

Back in the early 80's I had a girlfriend who lived on a farm near Rome, NY. She noticed that the year after the nuclear anomaly at Three Mile Island, that the number of flies on the farm was down tremendously. Do you have any nuclear power plants near by? Is the farm located down wind? If so, ...

It is obvious that some manager's political agenda takes priority over the stockholder's interests.

I was having the same issue. When the ini file was created by someone in the administrators group, the file was only accessible by others in the administrators group. 'Normal' users were denied permission. So I changed the fourth parameter in the CreateFile() function call to be: m_hFile = CreateFile(..., ..., ..., GetSAForEveryone(), ..., 0, 0); SECURITY_ATTRIBUTES* GetSAForEveryone() { static SECURITY_ATTRIBUTES SA; static SECURITY_DESCRIPTOR SD; static bool FirstTime(true); if (FirstTime) { SD.Revision = SECURITY_DESCRIPTOR_REVISION; SD.Sbz1 = 0; // reserved SD.Control = SE_DACL_PRESENT; SD.Owner = 0; SD.Group = 0; SD.Sacl = 0; SD.Dacl = 0; // This grants access to everyone SA.nLength = sizeof(SECURITY_ATTRIBUTES); SA.bInheritHandle = false; SA.lpSecurityDescriptor = &SD; FirstTime = false; } return &SA; } This works great. The file is created so that everyone on the machine can read/write/delete/copy/move it. However, the next hurdle you will face is that if a user in the administrators group copies/moves the file to another folder, the file is again not accessible by all users. To get around this issue I found a page (http://support.microsoft.com/kb/310316) that addresses the issue. The bottom line is that I set the registry entry mentioned in that article for each user that creates the file. This may not be an acceptable solution in your case but it works for me.

Just remind him that both the PC and the Mac were inventerd by clever Americans.

I ran into this issue about a year ago and the issue is exactly what Michael Dunn stated. And I fixed the problem the same way suggested by syampi.

I too had to do the same thing but wrote this .bat file to register all .dll and .ocx files in the working directory. for %%i in (*.dll) do regsvr32 /s %%i for %%i in (*.ocx) do regsvr32 /s %%i The 'regsvr32 /s' can be changed to un-register them too. Perhaps this will help next time.

The good, the bad and the ugly: There are two kinds of people in this world. Those with loaded guns and those who dig. Can easily be translated into: Those who beat their swords into plowshares, plow for those who don't.

I started coding as a job in 1975. Naturally, it was on a main frame, but I soon got bored there and moved on to mini's (PDP-11, HP1000, VAX, etc.) and shortly after that got into micro's and that's what I've been doing exclusively for over 25 years (CP/M, Isis, UCSD P-system, DOS and Windows). I found that most of the people I worked with in my main frame days stuck with the employers they started with, and have pretty much retired. That CAN be one of the benefits of working for the same employer for 30 years. I have worked for several start-ups and made great money on some (stock options) and broke even on others (worthless options). I am still writing code and staying away from management mainly because I love it but also because I believe in the "50/50 rule of middle management". That is: When a company is bought out or goes public and fat needs to be cut out 'if you are over 50 years old and make over $50,000, you are expendable'. Stay away from middle management and keep your skills honed.

The way to get rid of tailgaters is to speed up.

My son's HP laptop has done the same kind of thing on two different occasions. In both instances the motherboard needed to be replaced. The first time HP's maintenance says that a liquid was spilled into the keyboard. That was totally bogus but it was covered by HP's 3 year accidental insurance so it wasn't as painful as it could have been. Also, in both cases, the hard drive was not affected so when he got it back, it still had everything on it.

I like your son's chice of PDA. My boy uses a Ma Deuce.

Here's how I do it. SERVICE_DESCRIPTION Descr = {(LPSTR)GetServiceDescription()}; ChangeServiceConfig2(schService, SERVICE_CONFIG_DESCRIPTION, &Descr);

MS bought the product known as SourceSafe sometime back in the late 90's. We used it before it was an MS product. MS developed a product initally called "Delta" that was to be their solution but it had too many usability problems to see the light of day. I went to a MS conference in Minneapolis back then and they were handing out glossy marketing brochures for Delta. When it had not been formally released within 6 months I asked our MS sales guy about it and he said that it was being dropped. (Yes, we actually had a MS sales guy come to our offices on a fairly irregular basis.) In any event, MS bought it and has not cleaned up the original SourceSafe usabilty issues. What do you expect from a company who's motto is: "We collect the money, you do the work."

I use this: { SHELLEXECUTEINFO ShExecInfo; ShExecInfo.cbSize = sizeof(SHELLEXECUTEINFO); ShExecInfo.fMask = NULL; ShExecInfo.hwnd = NULL; ShExecInfo.lpVerb = 0; ShExecInfo.lpFile = DocName; ShExecInfo.lpParameters = NULL; ShExecInfo.lpDirectory = NULL; ShExecInfo.nShow = SW_MAXIMIZE; ShExecInfo.hInstApp = NULL; ShellExecuteEx(&ShExecInfo); } Just put your document's name in DocName and the system will find the program that handles the document. I have used it with a .rtf document and it loads MSWord on systems that have MSWord or it loads WordPad on the systems that don't have MSWord.

Please tell me what even remotely leads you to believe that the drugs you will be receiving will actually be legitimate?? Ask yourself this question: "Who audits these online websites that claim to be pharmacies?" Just because you give them your credit card number and they send you something in the mail that resembles drugs does not mean they are legitimate pharmacies or have access to legitimate drugs.

The museum of science and industry (www.msichicago.org) is good. Stephen