test_client

Thanks, Xiven. I was afraid of that, but possibly somebody will come up with a good idea/solution for the problem.

I think I stomped the Windows wizards in this forum. Let me try another newsgroup. I'll let you guys know if there is a good solution.

Everyone here knows about the AT command, right? This command lets you schedule tasks under W2K when the scheduler service is enabled. Here is the question: Who is the owner of the scheduled process? I would like to enable a guest or user account to schedule some simple tasks. If they schedule these tasks will the tasks have system or admin privileges? Is there any way of defining the owner of the scheduled process before running it? Your expert opinion will be greatly appreciated.

Fresh install does it every time .

We had a similar problem on several Win98 computers and the following steps helped to fix the problem: 1. Start by removing everything from your StartUp folder. 2. Then clean out the "Run" section of your registry. You would expect booting in safe mode would do the same thing though. Also you may want to save the registry settings, so that you can add your programs back one by one and see which one causes the problem.

This is not supposed to happen to 32bit windows applications. A Win16 program that loaded a DLL with LoadLibrary and crashed or didn’t call FreeLibrary later would leave the DLL in memory even after the program exited. Matt Pietrek wrote a famous NukeDLL utility for dealing with this problem, and there are still several versions of it floating around. I am not sure if it will work in your case. Here is a link where you can get one of the versions: http://www.openinformationsystems.com/provalov/freeware/nukedll.zip Hope this helps.

Regedit is an older version and it is also available under Win95/98, so more people are familiar with it. RegEdt32 is an NT tool which is more powerful in some sense, for example it lets you set permissions and work with the registry in readonly mode. However it lacks some of the nice features of RegEdit, for example, Find -- one of the most important features of Regedit. These tools somewhat overlap in functionality. Instead of one nice tool MS gives you two bad ones, to avoid monopoly.

Has anybody seen this error before? What does it mean? One of our web scripts bails out on Winsock initialization. WSAStartup generates an error 10107. Here is what Microsoft tells you about the error: // // MessageId: WSASYSCALLFAILURE // // MessageText: // // A system call that should never fail has failed 8) . // #define WSASYSCALLFAILURE 10107L The IIS installation is standard, nothing tricky there. The server is W2K.

If mounting works than it is exactly what I am looking for. That will give me the permanent connection. Is there an option in the Disk Management for mounting computer shares?

Thanks guys, I appreciate your input. I thought possibly there was an easier way of creating a logical drive so that once it is there it is there. For all practical purposes it would appear as if it were a local disk rather than a share on another computer.

Yes, I shall try that and it may work just fine. However I was trying to avoid connecting and disconnecting with each logon. Also this connection is to be used by a service when nobody is logged on. That is the reason to avoid linking the mapping to computer users. The GroupPolicy for the computer would be an ideal place for this, but as far as I know the GroupPolicy does not let you create new connections.

I would like to create a permanent network connection between two computers. \\computer1\public - public share on computer1 (standalone W2K server). I would like the second computer to automatically map this share located on the first computer regardless of which user logs on to the second computer. In other words I want the share on the first computer look and feel like a logical disk on the second computer, as if it were hard wired. We would like to avoid assigning and using logon scripts for individual users or groups. Mapping should work for the computer rather than the users, and if at all possible mapping routine should be called only once when the computer starts up. I tried a batch file for GroupPolicies|Machine|Scripts|Startup, but group policies does not seem to allow creating new permanent connections. The batch file gets called, but mapping doesn't stay put. Is there any easy way around this? Any thoughts will be appreciated

I do not know how you would become a Windows GURU. Possibly you read books and magazines, spend a lot of time hands on with Windows, associate with people who know something about your subject. Also you need some talent, and be open-minded, as with any other profession. It is a good question, and I do not know the answer. Here is a piece from Microsoft KnowledgeBase article for your information which warns you about using the "deny" column: > >Access permissions are combined from any permissions that are >assigned directly to the user and those that are assigned to any >groups of which the user is a member. > >The exception to this rule is if there is an explicit Deny >permission on the folder or file. This occurs because Deny >permissions are enumerated first when Windows 2000 is determining >whether or not a particular user can perform a particular task. > >Therefore, you should avoid using explicit Deny permissions >(that is, avoid clicking to select a check box in the Deny column) >unless there is no other way to achieve the permissions mix that >you need. > Also I noticed that you talk about "decline" in your earlier posts. Do you mean "deny", or is there another set of "decline" permissions I am not aware of? That would be really spooky. Thanks!

Clutch: I asked for help because it got me confused. You do not have to tell me that you know better, I was hoping that somebody would know better than I did. That is why I submitted the question to this group. The idea behind removing *all* groups the account belongs to was to strip this account of *all* access rights. Ideally that would let me create a fresh group with unique access rights. As it turns out Microsoft gives *everybody* User access rights by default, even the guest account will have User rights by default. This happens because the newly created account belongs to INTERACTIVE default group, although this group does not show up in the list of groups the account belongs to. The INTERACTIVE group in its turn belongs to the Users group. These default groups are very much like ghosts lurking around in the dark granting different users different access rights. And instead of being able to *simply* look up what account belongs to which specific group the administrator has to know what was in the minds of the designers of the operating system. Reading books is very good and I do thank you for your suggestion. However it would be much better if I simply could look up who belongs to which group in the user manager. (Instead of keeping it in my memory). Account management does not really have to be so muddled. Make these "ghost" groups grayed out to identify that you cannot remove them, but they should show up in the list. But this is a request for Microsoft rather than a topic for the forum. It's true that denying access rights will override the granted access rights. However Windows gurus tell you that denying access rather than granting access should be the last resort, so they recommend staying away from denying access (I think this was a white paper on the Microsoft site or on one of the Microsoft CDs). Thank you all for your feedback.

Well, I tried this batch file under Windows 2000 and it did not work. However, my guess is that the problem arises because of the bad "inf" file which gets created. Here is the page which talks about rebooting different versions of Windows using RUNDLL which may be helpful: http://www.robvanderwoude.com/shutdown.html