cak46

Double click on the c: drive. Now, go to the top of the window and select view>folder options a new windows will open. Click on the View tab, then uncheck the option that says something like hide system files and uncheck hide hidden files. Can't remember the exact statements but what you want to do in there is unhide the hidden files and the system files. It will pop up a warning, but just tell it ok. Click ok on that screen and the hidden files should appear. Must sign out. If you have trouble, pm me and will catch up with you tomorrow!! :)

That must have been sweeeeet! Ah, I have that same problem... occasionally! :haha: go to My Computer, double click on the c: drive. Should be listed right there.

Your design looks good and should work. By using switches instead of hubs, you will minimize errant traffic on your local lan. Original is right that your speed may be slow with all of those machines on-line with a dsl connection (assumption-phoneline). Your bottleneck will be there. I wouldn't look so much at lag, but more to bandwidth available on your internet connection. 5 machines each downloading a large file at the same time could bring your connection to the internet to its knees, not so much because of latency, but more by low bandwidth. The smaller the pipe, the more collisions you have, hence higher latency. Who is your provider and what package do you have? BTW: The laptop should be able to print to the networked printer if configured correctly.

Must have been a great concert! Left a few myself for AC/DC, Nugent, Styx....... Would have liked to have seen JA in concert. BTW: Youre a Regular now (Note your stars....)

No, looks good to me. With advapi, its showing its given name, not the name of the actual file.... if that makes any sense. Check the dependencies for each of these. the first two Kerberos and lsasrv are related to security, the second (I assume as IO.dll and if it isn't, let me know) is related to input/output devices (maybe a possibility?) the fifth is part of security as well. schannel is the secure socket layer provider for Internet explorer. Got your other post. I believe its a hidden file in the root (C:) directory. Copy it by right mouse clicking on it once, then select Copy, then paste it onto your desktop. Email it to me instead of posting if you want.

No reason to be It does not necessarily mean the lsass's are different versions. I like to start general then get specific. Found in the long run things work out better that way. find the lsass file on each machine, rioght mouse click then select properties. Now, compare the version numbers on the version tab of each. If they are the same, it may still be a viable route to travel. If not, so what? Still a damn good idea in my book.

Yeah, things get fixed and better with age, supposedly.... Very good idea to look at the other machine and compare! :)! Try running advapi.dll thru the depends tool. That executes at about the same time as the lsass error. May want to check each module that runst at the same time period. See if it might be an unrelated but causal factor of the lsass.exe error? advapi is part of the security system, I believe. Also, save the log on the kit. computer from depends for lsass.exe and check the 'known dll's" and compare with the log on the other machine. It could be that a needed dll is not registred but should be. Here is the old log: The system's "KnownDLLs" list [F ] c:windowssystem32ADVAPI32.DLL [F ] c:windowssystem32APPHELP.DLL [F ] c:windowssystem32COMCTL32.DLL [F ] c:windowssystem32COMDLG32.DLL [F ] c:windowssystem32CRYPT32.DLL [F ] c:windowssystem32CRYPTUI.DLL [F ] c:windowssystem32GDI32.DLL [F ] c:windowssystem32IMAGEHLP.DLL [F ] c:windowssystem32KERNEL32.DLL [F ] c:windowssystem32LZ32.DLL [F ] c:windowssystem32MPR.DLL [F ] c:windowssystem32MSASN1.DLL [F ] c:windowssystem32MSVCRT.DLL [F ] c:windowssystem32NETAPI32.DLL [F ] c:windowssystem32NTDLL.DLL [F ] c:windowssystem32OLE32.DLL [F ] c:windowssystem32OLEAUT32.DLL [F ] c:windowssystem32OLECLI32.DLL [F ] c:windowssystem32OLECNV32.DLL [F ] c:windowssystem32OLESVR32.DLL [F ] c:windowssystem32OLETHK32.DLL [F ] c:windowssystem32RPCRT4.DLL [F ] c:windowssystem32SHDOCVW.DLL [F ] c:windowssystem32SHELL32.DLL [F ] c:windowssystem32SHLWAPI.DLL [F ] c:windowssystem32URL.DLL [F ] c:windowssystem32URLMON.DLL [F ] c:windowssystem32USER32.DLL [F ] c:windowssystem32USERENV.DLL [F ] c:windowssystem32VERSION.DLL [F ] c:windowssystem32WININET.DLL [F ] c:windowssystem32WINTRUST.DLL [F ] c:windowssystem32WLDAP32.DLL [F ] c:windowssystem32WOW32.DLL The application directory [ ] C:WINDOWSsystem32 The 32-bit system directory [ ] C:WINDOWSsystem32 The 16-bit system directory (Windows NT/2000/XP only) [ ] C:WINDOWSsystem The system's root OS directory [ ] C:WINDOWS The application's registered "App Paths" directories The system's "PATH" environment variable directories [ ] C:WINDOWSsystem32 [ ] C:WINDOWS [ ] C:WINDOWSsystem32WBEM [ ] C:Program FilesCommon FilesUlead SystemsMPEG [ ] C:Program FilesSupport Tools

Actually, look at the info at the top of the depends log.... In red this is the log you sent me. Dependency Walker: 2.1.3623 (32-bit) Operating System: Microsoft Windows XP Professional (32-bit) OS Version: 5.01.2600 Service Pack 2 Processor: x86 Family 6 Model 10 Stepping 0, AuthenticAMD, ~2193MHz Number of Processors: 1 Computer Name: User Name: Local Date: Monday, July 25, 2005 Local Time: 9:01:25 PM Pacific Daylight Time (GMT-07:00) OS Language: 0x0409: English (United States) Memory Load: 46% Physical Memory Total: 1,073,201,152 (1024 MB) Physical Memory Used: 503,476,224 Physical Memory Free: 569,724,928 Page File Memory Total: 2,582,675,456 Page File Memory Used: 345,280,512 Page File Memory Free: 2,237,394,944 Virtual Memory Total: 2,147,352,576 Virtual Memory Used: 62,889,984 Virtual Memory Free: 2,084,462,592 Page Size: 0x00001000 (4,096) Allocation Granularity: 0x00010000 (65,536) Min. App. Address: 0x00010000 (65,536) Max. App. Address: 0x7FFEFFFF (2,147,418,111)

Hello again! Got the files. What I'm looking for is a copy of your actual boot.ini file, not the bootlog (Ntb...)..... To answer your question on server vs. client systems, or try to anyways, Server in this case means a machine set up with a specialized operating system to perform a multitude of different functions pc's, and pc (client versions) of op. sys's couldn't perform. If you want I can give a more detailed description of this..... Get medievil techie on your butt... :haha: XP home is a client software, clients access servers which would run for example Windows 2003 Server. There are alot more functions that run on a server edition than on a client edition of an operating system. The two files we found missing are tied explicitly with Domain Controller functions, at least with win2000 Server, anyway. Still looking into the logs you sent..... Just saw your note.... You're right about the two files.... Domain controller functions...... missing in depends prog. does not necessarily mean its required for proper functioning of the dll in question. Will await you post! EDIT: That other missing file NTDSETUP.DLL file is used for setting up Active Directory, a server function only.... Are you running the exact same service pack level and Operating system version? Check each in the Control Panel> System icon and compare actual version numbers. You may be on to something if they are exact. Also, a side note, are both 'puters same make and model? Check the version numbers if you would.

Thats because those files are for the a server version of software. They reuse the same code for both their server software and their client software. Been doing that since nt4.0 came out. I'm going to have to do some more research tomorrow but if you could, email me a copy of your actual boot.ini file and a copy of the depends results for lsass.exe. And hey, grab me one while you're there, will ya? :haha: Most of the info I found was for nt2000 so I'm unsure if the domain controller (server) part applies or not to XP. Might be a good question for Mr. MS..... Good evening and be back in the morrow! Edit: Since you have an xp disk, you can go thru the cabs on that and see if its there but I would not suggest extracting them into system32 until we get more info on them. I think the dll.cab is holding just the installed dlls only, not all .dlls for windows. More research, I suppose. Good evening!

I do not know. the kdcsvc is tied to kerberos authentication. You could try and extract them from the .cab file you extracted the other files from the other day. Edit: Just found out. kdcsvc.dll is the domain controller equivalent of the kerberos.dll client computer file. (At least in a win2000 environment) I would wait on extracting for now until I can get more info on these files. Did you notice if there were any errors in the listings from depends as you scrolled thru them?

Good idea!

Hangin' on the Line........

And Houston, We may have found the answer. Now, do a file seach on your hard drive for the two filenames in red. I'm gonna stick it out tonite for a bit longer. Too close to bail now........

With the google toolbar, if you selected to use the advanced features, the toolbar reports info. back to google. This might be the prob with google toolbar. Not sure about the mcafee and why it would do that. SP2 doesn't like that kind of unsolicited outgoing communication..

Look at the top of my screen that I posted then look at yours I opened cwsshredder.exe.... look right beside where it says dependency walker on the screen. Go to file menu , then select open then browse to lsass.exe and try to open it..... edit: Everything below the topmost entry is a program module that depends.exe is depending upon. Widen out the top screen and you'll see the beginning.

Try disabling them one at a time to see which it is.

Yeah. It's looking at itself, I think.......

I was being win98 centric. You can try this: BTW Never used this before so I'd try the command line first. From: http://windowsxp.mvps.org/IEFAQ.htm#Reinstall Half way down the page: Reinstall or Repair IE / OE in Windows XP Try IEFix: http://windowsxp.mvps.org/IEFIX.htm Or, try the manual procedure below: First, try reinstalling from the INF files. Click Start/Run/Type the following command: rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 %windir%infie.inf

Alot of it is just for that. Debugging and testing software as you code. Never done any windows specific programming, xcept VBA in Access so I'm not familiar with the tools. All strapped in.......

There are quite a bit of tools. If you go to the first link in my post and click up one level, I think it brings you to the master contents page for the support tools. Yeah, I'm hopeful that it will be apparent which files are necessary (need to be registered) when you open lsass.exe in the utility. I just downloaded it from the link in my post. Onlty about a 405 KB download and will run on most all platforms and windows versions......... BTW: ME TOO BTW2: I am close to certifying that HP POS as clean. One more scan of each id tomorrow, put it back on the net, then clean the tools I installed off of it! A funny thing happened tonite with it. It turned itself on. I think it received the signal thru the nic card from the net to turn on but I'm behind a router. Very, very strange......... Disabled that in bios in a big hurry......

Got it. Was able to download it. http://dependencywalker.com/ Go to file, then browse to where lsass.exe is then select it.

:haha: I believe you type in the name of the program you want to view the dependencies for. Drwaing a conclusion from this info from this link. http://www.mazecomputer.com/sxs/help/builddep.htm Will look further.... Using Dependency Viewer Microsoft Windows SDK (free download from Microsoft) includes a module dependency viewer called depends.exe. This is an indispensable tool for finding missing DLL dependencies required by somebody else's code. When you are the developer of the code being packaged, you know what DLLs and COM objects are required. Not necessarily so with third party software. Use Dependency Viewer. The moment you open a DLL or an executable in Dependency Viewer, it recursively scans import tables and locates all imported DLLs and exported and imported entry points. The first thing you should do is ignore all missing delay-load imports and, in most cases, all error messages pertaining to Windows DLLs. Look for yellow marks at all non-system DLLs. These are all required to load the DLLs. If there are no more missing DLLs in the UI, there may be DLLs loaded dynamically at runtime - proceed to round two. Dependency Viewer - Round Two You may need to actually run the program or load the DLL inside depends.exe to allow the program check run-time load requests. If you need to find missing DLLs for an executable - run that program with appropriate parameters. If you are investigating a DLL (for a shared or private assembly, for example) run REGSVR32.EXE <your DLL path>. The log window displays in red failing DLL loads and entry point lookup calls - study the list. Every failing LoadLibrary* loading a DLL with no path can be fixed - just add the DLL to run-time dependencies or the manifest, whichever is appropriate. Any DLLs loaded with an explicit path must be in that explicitly named directory - no manifest will help here. *********************** Here it is..... now to read a bit................http://dependencywalker.com/

Just pm'd you info on the dependency program. I believe that this is where you will find if there are some services that may not be running. Take the list from Depends then run sc query and compare the two. SC config you're gonna have to look up in MS's infamous help and support in XP.... I'll gawk around the net a bit and see what I can come up with as well..........

Search on you HD for a file named iesetup.exe. This is the installer for IE. Run the program and select the repair option. Hopefully this helps.