System Admin

FirstPrevNext

Problem with accessing share resource Mekong River9-Jul-04 4:52 Mekong River 9-Jul-04 4:52  Hi, I have a problem when I share a resource on the network. My computer use windows 2000 professional. I share a folder that contain a picture call "rt04" set the full permission to Everyone user. When I access from windows xp client it prompt me for user name and password. I supply "administrator" as the user name and the password of adminstrator account on my computer then it could access my share files. But when I start to access the file from windows 98 it display a dialog box with only one textbox for password. The "Resource:" labeled stand for "\\[ComputerName]\IPC$" and a check box labeld "Save this password in your password list". From here I type the password of the administrator account on my computer but it is not work, it just display the dialog box again and said that the password is incorrect. I have two question in here: 1. Why I could not access the share file from on my computer from the computer running windows 98 (windows xp is working fine ) 2. The check box labeled "Save this password in your password list". What does the password list mean, where is the list that it store the password in my computer. Please help me Roath Kanel APO-CEDC Save Children Norway-Cambodia Office Windows 2003 problem Mekong River8-Jul-04 12:11 Mekong River 8-Jul-04 12:11  Hi, a problem when I configure win3k to server and make domain to clients and user access to the server . I try to do but user can't access to the server, Could anyone tell me the way to solve the problem. Roath Kanel APO-CEDC Save Children Norway-Cambodia Office Re: Windows 2003 problem Mike Dimmick10-Jul-04 7:27 Mike Dimmick 10-Jul-04 7:27  Do you mean that you've set up Active Directory? If so, you need to ensure that DNS is set up correctly, that the users' computers are configured to use the internal DNS servers as their primary DNS servers, that the users' computers are members of the domain, that the users have accounts on the domain and that they're logging on with those accounts. Then, assuming you're talking about using file and printer sharing, the users will need to have permissions both to the share, and in the case of file sharing on NTFS drives, also to the files themselves. If you've only got a few users, AD may be overkill. The company I work for is about eight years old and we've only just started using any form of domain, largely because we're starting to migrate to Exchange before merging with another company - we currently have six users but are getting another six right now with the expectation of hiring more in the near future. If you want to avoid having a domain, your users either need to supply alternate credentials when connecting to the server, or they need to have user accounts on the server itself. To make things seamless, their local passwords and the passwords on the server must be identical. You can migrate from the duplicate accounts scheme to a domain later on - our file server is not yet a member of the domain, so it has a duplicate set of user accounts. The database server currently uses SQL Server authentication, so doesn't need the duplicated accounts. For security I'd prefer to be using Windows authentication, but my boss doesn't want the downtime. Finally, running a domain is a commitment to a certain level of service and maintenance. You must back up your domain database (using System State in the Windows Backup tool, or another method) regularly. Ours is currently backed up weekly; this probably isn't often enough. If you don't back it up and all your domain controllers fail, you won't be able to recreate it in the same state, you'll have to recreate all the user accounts and your users will all lose their profiles. I strongly recommend reading the appropriate chapters of the resource kits, reading Microsoft Certified Professional course material, and the Active Directory material on Microsoft Technet[^]. Stability. What an interesting concept. -- Chris Maunder Win XP Single user question Chris Meech8-Jul-04 5:15 Chris Meech 8-Jul-04 5:15  When I first installed XP, I never created any user accounts as the machine is functional specific and not user specific. One of the 'features' I got from doing this, is that when the machine booted, it always booted to the desktop immediately. Unfortunately I had a hardware problem and took the machine to a shop where they not only fixed the hardware problem, they changed something else so that the welcome screen shows up and you have to click on the single user account "Chris", no passowrd required, in order to get to a desktop. What do I have to do, so that the PC boots to the desktop, instead of prompting for a click on "Chris"? Thanks. Chris Meech I am Canadian. [heard in a local bar] I think people should be required to have an operator's permit to use the internet. John Simmons Re: Win XP Single user question Mekong River6-Feb-06 22:51 Mekong River 6-Feb-06 22:51  http://support.microsoft.com/?kbid=315231[^] Re: Win XP Single user question Chris Meech7-Feb-06 2:55 Chris Meech 7-Feb-06 2:55  Thanks! I did get the XP machine to auto login as the article explains. Chris Meech I am Canadian. [heard in a local bar] When I want privacy, I'll close the bathroom door. [Stan Shannon] BAD DAY FOR: Friendly competition, as Ford Motor Co. declared the employee parking lot at its truck plant in Dearborn, Mich., off limits to vehicles built by rival companies. Workers have to drive a Ford to work, or park across the street. [CNNMoney.com] Nice sig! [Tim Deveaux on Matt Newman's sig with a quote from me] Can you read this MiniDump? Anonymous7-Jul-04 23:58 Anonymous 7-Jul-04 23:58  Hello, I have a win2000 installation has began to crash a few times daily and I don't know why. This is a pretty recent install w/ current ServicePacks and major windows update security patches. Nothing out of the ordinary. It will just lock up, then shut down and reboot. Here is one of the dump's ran through windbg.exe. I struggled with windbg.exe trying to load the symbol files, but I finally got it. I just don't know how to interpit this log and figure out what the problem is. Microsoft (R) Windows Debugger Version 6.3.0017.0 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINNT\Minidump\Mini070404-06.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: C:\WINNT\Symbols Executable search path is: Unable to load image ntoskrnl.exe, Win32 error 2 Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e8f0 Debug session time: Sun Jul 04 21:35:23 2004 System Uptime: not available Unable to load image ntoskrnl.exe, Win32 error 2 Loading Kernel Symbols ....................................................................................................... Loading unloaded module list ......... Loading User Symbols *************************************************************************** **** * * * Bugcheck Analysis * * * *************************************************************************** **** Use !analyze -v to get detailed debugging information. BugCheck 1E, {c0000005, 80450ea6, 0, 5e494e26} Probably caused by : ntoskrnl.exe ( nt!NtWaitForMultipleObjects+275 ) Followup: MachineOwner --------- kd> !analyze -v *************************************************************************** **** * * * Bugcheck Analysis * * * *************************************************************************** **** KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: 80450ea6, The address that the exception occurred at Arg3: 00000000, Parameter 0 of the exception Arg4: 5e494e26, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". FAULTING_IP: nt!NtWaitForMultipleObjects+275 80450ea6 ?? ??? EXCEPTION_PARAMETER1: 00000000 EXCEPTION_PARAMETER2: 5e494e26 READ_ADDRESS: unable to read from 80483450 unable to read from 80482ea8 unable to read from 80482d78 unable to read from 80475234 unable to read from 80482d90 unable to read from 80482ea4 unable to read from 80475238 unable to read from 80482f64 unable to read from 80483420 5e494e26 CUSTOMER_CRASH_COUNT: 6 DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT BUGCHECK_STR: 0x1E LAST_CONTROL_TRANSFER: from 0000001e to 80430999 STACK_TEXT: bd038500 0000001e c0000005 80450ea6 00000000 nt!KiDispatchException+0x30e STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nt!NtWaitForMultipleObjects+275 80450ea6 ?? ??? FOLLOWUP_NAME: MachineOwner SYMBOL_NAME: nt!NtWaitForMultipleObjects+275 MODULE_NAME: nt IMAGE_NAME: ntoskrnl.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4047db83 BUCKET_ID: 0x1E_nt!NtWaitForMultipleObjects+275 Followup: MachineOwner What does this mean? Thank you in advance for your help. - Mike Re: Can you read this MiniDump? Mike Dimmick8-Jul-04 9:00 Mike Dimmick 8-Jul-04 9:00  An exception that occurred in kernel-mode code wasn't handled. The exception code was 0xC0000005, which almost any C programmer can tell you is an Access Violation exception. Parameter 1 of an access violation exception is the type of access (0 = read) and parameter 2 is the address that the code tried to access. The code that faulted was somewhere near the implementation of the NtWaitForMultipleObjects function in the NTOSKRNL.EXE module - possibly in the function itself. I'd be surprised if it was a bug in NtWait[...] because this path is very regularly exercised. I suspect that some component of this system is failing - probably the RAM. If you've overclocked the machine, set it to the correct speed. Check all cooling devices are working correctly. Ensure none of the boards are damaged. Stability. What an interesting concept. -- Chris Maunder Re: Can you read this MiniDump? Tim Deveaux8-Jul-04 9:51 Tim Deveaux 8-Jul-04 9:51  Mike has a good point - but if it is the RAM, CPU, or CPU fan that's failing, there's a good chance that each dump you analyze will show a different location and/or bugcheck codes. If the dumps are consistent, I'd do some further digging and/or start speculating on drivers and such. Again as Mike mentioned, it's unlikely that NtWaitForMultipleObjects is the real culprit. Looks like you're going to have to dig a little deeper into the dump to find the problem. This initial analysis isn't giving you the stack trace you need, which I think is a result of trapping into the exception dispatcher. Here's a doc that might be helpful: http://www.wd-3.com/archive/registercontext.htm[^] You may need more than a mini dump to work with - not sure. If you've got the time, you might try using WinDbg on a remote machine. I'm pretty sure that you would break into the debugger before the bugcheck call in response to a first chance exception, which might give you a better context to work with. Re: Can you read this MiniDump? Anonymous8-Jul-04 11:01 Anonymous 8-Jul-04 11:01  Wow, thank you very much for the responses. I've though about it more and here is some additional information to possibly filter out or confirm any theories. Here is the reasons from other dumps from the series of crashes: IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: f000e2d9, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: 8042d37c, address which referenced memory PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: e3522097, memory referenced. Arg2: 00000001, value 0 = read operation, 1 = write operation. Arg3: bcfb127c, If non-zero, the instruction address which referenced the bad memory address. Arg4: 00000001, (reserved) DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 00000028, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: bd525f25, address which referenced memory I doubt it is overheating. I don't overclock and I monitor my chipset, CPU, power, and case fans. I also keep the case open 24/7. There's been no recent hardware or driver changes in the system. I am actually on day 2 without a crash now. But it went down about 6 times earlier this week. This also happened about 2 months ago and then magically started working fine. Is it possible for the ntorkrnl.exe to be corrupt? I dunno. When it crashes, sometimes I'd be playing a game, sometimes web browsing. One time it crashed while I was trying to log off of windows the exact second I clicked "OK". I would try debugging on a remote machine, my all my other computers are either some kind of unix or linux. -Mike Re: Can you read this MiniDump? Tim Deveaux8-Jul-04 13:08 Tim Deveaux 8-Jul-04 13:08  I would think that the dumps for these should reference some kind of .sys file, not ntoskrnl.exe - that would help. Sure looks wonky though. Anonymous wrote: Is it possible for the ntorkrnl.exe to be corrupt? Anythings possible - you can actually update your ntoskrnl.exe and HAL files directly from the install disk if you like - there are usually checked and free versions for single and multiple CPUs available (hmmm - actually, I think the checked one is multi cpu). Google for 'partially checked' etc for instructions. It is possible for a reeely bad driver to produce seemingly random BSODs - I know - I've done it! But its hard to shake the hardware idea in this case - do these crashes repeat with the same data? Will ponder till morning. Keep us posted! Re: Can you read this MiniDump? Mike Dimmick9-Jul-04 5:26 Mike Dimmick 9-Jul-04 5:26  Anonymous wrote: I also keep the case open 24/7. Don't. Airflow is typically better if you assemble the case properly. If it still gets too hot, you need an exhaust fan in the box and reasonable airflow in the room - if you put the back of the system too close to the wall, the hot air has nowhere to go and simply gets sucked straight back into the system. Cooling systems work best with a low ambient temperature. My P4 2.8GHz system has the normal PSU fan, CPU fan and a fan on the graphics card, but it also has a smallish 8cm fan in the front of the case and a 12cm fan in the back. All those fans are quite noisy, which is why I used a case which comes with a large amount of acoustic wadding (from QuietPC.com[^]). The fans mostly came from QuietPC as well, but five fans still make quite a bit of noise. Stability. What an interesting concept. -- Chris Maunder Re: Can you read this MiniDump? Anonymous9-Jul-04 12:30 Anonymous 9-Jul-04 12:30  Blah. Another crash after 2 days. The computer was idle. It crashed while I was in the other room. There was no programs running. Microsoft (R) Windows Debugger Version 6.3.0017.0 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINNT\Minidump\Mini070904-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: C:\WINNT\Symbols Executable search path is: Unable to load image ntoskrnl.exe, Win32 error 2 Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e8f0 Debug session time: Fri Jul 09 18:15:50 2004 System Uptime: not available Unable to load image ntoskrnl.exe, Win32 error 2 Loading Kernel Symbols ........................................................................................................ Loading unloaded module list ....................................... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {d, 0, 0, 0} Probably caused by : ntoskrnl.exe ( nt!KiSystemFatalException+e ) Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000d, EXCEPTION_GP_FAULT Arg2: 00000000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_d CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT LAST_CONTROL_TRANSFER: from 8049747e to 80469822 STACK_TEXT: ed17f7dc 8049747e ed17f84c e37194b0 00000000 nt!KiSystemFatalException+0xe ed17f854 8049803f e32ff728 00200080 ed17f8b8 nt!HvpGetCellPaged+0x35 ed17f864 80497b44 e37f0568 ed17f8f8 00000000 nt!CmpQuerySecurityDescriptorInfo+0x10 ed17f8b8 804507ac e3e99140 00000001 ed17f8f8 nt!CmpSecurityMethod+0xb4 ed17f8f0 8045043d 0000000f ed17f91c ed17f910 nt!ObGetObjectSecurity+0x60 ed17f920 80497dd1 e3e99140 ed17fbf4 00000001 nt!ObCheckObjectAccess+0x28 ed17f948 804976f2 e32ff728 0000e500 e331f504 nt!CmpDoOpen+0x210 ed17fb40 804516eb e32ff728 818a89e0 ed17fbf4 nt!CmpParseKey+0x389 ed17fbb4 80496299 000001e0 ed17fcb0 00000040 nt!ObpLookupObjectName+0xdf ed17fcc4 80497c7c 00000000 818a89e0 8122da01 nt!ObOpenObjectByName+0xc5 ed17fd50 80465b91 0006fd2c 00020019 0006f59c nt!NtOpenKey+0x151 ed17fd50 77f833c0 0006fd2c 00020019 0006f59c nt!KiSystemService+0xc4 WARNING: Frame IP not in any known module. Following frames may be wrong. 0006f540 00000000 00000000 00000000 00000000 0x77f833c0 FOLLOWUP_IP: nt!KiSystemFatalException+e 80469822 ?? ??? SYMBOL_STACK_INDEX: 0 FOLLOWUP_NAME: MachineOwner SYMBOL_NAME: nt!KiSystemFatalException+e MODULE_NAME: nt IMAGE_NAME: ntoskrnl.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4047db83 STACK_COMMAND: kb BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+e Followup: MachineOwner I havent had this error yet. Whats this one all about? Re: Can you read this MiniDump? Anonymous9-Jul-04 12:31 Anonymous 9-Jul-04 12:31  I have new RAM on order BTW. It's my guess that the RAM is the possible culprit. Re: Can you read this MiniDump? Roger Wright9-Jul-04 17:31 Roger Wright 9-Jul-04 17:31  See Win32 Error Codes[^] for clues. For one thing, Win32 Error 2 indicates that a file could not be found. Secondly, a driver fault is indicated. The line: "WARNING: Frame IP not in any known module. Following frames may be wrong. 0006f540 00000000 00000000 00000000 00000000 0x77f833c0" Indicates that the Instruction pointer is referencing a memory address that Windows doesn't recognize as being in use, hence the data there is probably invalid. Executing it will most likely cause a serious failure. I suspect that a driver has become corrupted; isolating it will be a tedious process. Boot in Step-by-Step Confirmation mode and disable all driver loading except the basics - disk controller, keyboard, mouse, video, etc. If the failure happens on this load, you may have a motherboard or firmware (BIOS) problem. If the problem doesn't recur, boot again and enable loading of a few drivers, then wait for a failure. If none occurs, reboot again and add a few more drivers to the allowed set, repeating this procedure until a failure happens. Go back a step and enable the most recent group of enabled drivers one at a time to determine which one causes the failure. Replace that driver from the original media or with an updated version compatible with your OS version. You might also have a version conflict among the many dlls used by Windows, but the error logs don't look like that's the problem this time. Running SFC from the Start/Run menu may reveal something useful. "My kid was Inmate of the Month at Adobe Mountain Juvenile Corrections Center" - Bumper Sticker in Bullhead City Re: Can you read this MiniDump? Anonymous9-Jul-04 13:18 Anonymous 9-Jul-04 13:18  Sad, sad day... Microsoft (R) Windows Debugger Version 6.3.0017.0 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINNT\Minidump\Mini070904-02.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: C:\WINNT\Symbols Executable search path is: Unable to load image ntoskrnl.exe, Win32 error 2 Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e8f0 Debug session time: Fri Jul 09 19:19:50 2004 System Uptime: not available Unable to load image ntoskrnl.exe, Win32 error 2 Loading Kernel Symbols ....................................................................................................... Loading unloaded module list .......... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {a668c4d0, 2, 1, 80448ed8} Unable to load image SYMEVENT.SYS, Win32 error 2 *** WARNING: Unable to verify timestamp for SYMEVENT.SYS *** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS Probably caused by : SYMEVENT.SYS ( SYMEVENT+4a7e ) Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: a668c4d0, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, value 0 = read operation, 1 = write operation Arg4: 80448ed8, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: unable to read from 80483450 unable to read from 80482ea8 unable to read from 80482d78 unable to read from 80475234 unable to read from 80482d90 unable to read from 80482ea4 unable to read from 80475238 unable to read from 80482f64 unable to read from 80483420 a668c4d0 CURRENT_IRQL: 2 FAULTING_IP: nt!MiRemovePageFromList+55 80448ed8 ?? ??? CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xA LAST_CONTROL_TRANSFER: from 804494c9 to 80448ed8 TRAP_FRAME: bd1b4938 -- (.trap ffffffffbd1b4938) ErrCode = 00000002 eax=649b6a99 ebx=ffffffff ecx=818d7000 edx=81a56e20 esi=818d6fe8 edi=80474c30 eip=80448ed8 esp=bd1b49ac ebp=bd1b49ec iopl=0 nv up ei ng nz ac pe cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293 nt!MiRemovePageFromList+0x55: 80448ed8 ?? ??? Resetting default scope STACK_TEXT: bd1b49b4 804494c9 863b3c28 80442b78 e39610a4 nt!MiRemovePageFromList+0x55 bd1b49bc 80442b78 e39610a4 fffff000 004884d0 nt!MiRemoveAnyPage+0x6f bd1b49ec 804425e1 ffb977c0 863b3c7c 00001000 nt!MiResolveMappedFileFault+0x319 bd1b4a18 80441960 00000000 cfbe909c c033efa4 nt!MiResolveProtoPteFault+0x128 bd1b4a60 8044ad48 00000000 cfbe909c c033efa4 nt!MiDispatchFault+0x13d bd1b4aac 80447c52 00000000 00000000 00000000 nt!MmAccessFault+0x682 bd1b4adc 8040dbc8 cfbe909c 00000000 ffba1028 nt!MmCheckCachedPageState+0x28e bd1b4b9c 804c971a ffba1028 0002909c 00000400 nt!CcFastCopyRead+0x1d5 bd1b4c20 bd050a7e ffba1028 bd1b4cfc 00000400 nt!FsRtlCopyRead+0x1c9 WARNING: Stack unwind information not available. Following frames may be wrong. 00000000 00000000 00000000 00000000 00000000 SYMEVENT+0x4a7e FOLLOWUP_IP: SYMEVENT+4a7e bd050a7e ?? ??? SYMBOL_STACK_INDEX: 9 FOLLOWUP_NAME: MachineOwner SYMBOL_NAME: SYMEVENT+4a7e MODULE_NAME: SYMEVENT IMAGE_NAME: SYMEVENT.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 3f31ac37 STACK_COMMAND: .trap ffffffffbd1b4938 ; kb BUCKET_ID: 0xA_W_SYMEVENT+4a7e Followup: MachineOwner --------- Re: Can you read this MiniDump? Anonymous9-Jul-04 16:31 Anonymous 9-Jul-04 16:31  This is so frustrating, because I'm good with computers and I take good care of this on. The only damn reason I'm using windows is so I can play counter-strike. Re: Can you read this MiniDump? Tim Deveaux11-Jul-04 3:39 Tim Deveaux 11-Jul-04 3:39  This looks to me like pesky hardware failure. The double fault above is particularly indicative - essentially, it couldn't even blue screen [edit]/trap the exception[/edit] properly. Verifying a solution will be tough. You could remove the paint and slip a new machine underneath, but that seems overly pessimistic. I wonder if you could monitor the CPU temp somehow. I have seen machines bs when their fans got stuck, and these are the sort of [edit]useless[/edit] bugchecks you get. If we had a graph of CPU temp redlining, or not, it might give us something to work with. A colleague had a open box at the office that would bs if you touched the ram. Often, we would taunt him a second time! I leave you now with some pithy quotes: "If you would see the invisible, you must look carefully at the visible" Santayana "Eliminate the impossible, and all that is left, however improbable, must be the truth" S. Holmes. "The Force Luke... use the Force" O.Kenobi Whatever. Keep us posted, and good luck. Use the common IIS WebServer in a LAN swarnamanoo7-Jul-04 21:41 swarnamanoo 7-Jul-04 21:41  Hi all.. I've installed an IIS WebServer in a server and all the users in the LAN must be able to access that.When we are trying to develop a web application and run it on a different system,It is posting an error saying "Error while trying to run project:Unable to start debugging on the web server.Access is denied" Though i've given debugger permissions for all on the server,its not working.can any one help me out in this issue. Re: Use the common IIS WebServer in a LAN Mekong River8-Jul-04 12:27 Mekong River 8-Jul-04 12:27  Try to read an article from the following site: http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B306172[^] http://support.microsoft.com/default.aspx?kbid=306165&product=aspnet[^] it might give you some idea to solve the problem. Roath Kanel APO-CEDC Save Children Norway-Cambodia Office how to include username/password a URL Hong Dat Huynh6-Jul-04 20:13 Hong Dat Huynh 6-Jul-04 20:13  My ASP.NET web applicaton includes a window media player (wmp) object. I'm using that wmp object to play a .wmv file in the network share folder. something like <object style="Z-INDEX: 0; LEFT: 0px; RIGHT: 0px; TOP: 0px; BOTTOM= 0px; WIDTH= 100%; HEIGHT= 100%" classid="clsid:6BF52A52-394A-11D3-B153-00C04F79FAA6" id="winMediaPlayer"> <param name="URL" value="\\192.168.100.100\sharefolder\video.wmv" /> Form1.winMediaPlayer.controls.stop(); However, since at the moment I can not include the username/password to access the folder in the url, Windows Media Player gives an error message "Windows Media Player can not copy or play the file because the server denied access to it. Verify that you have access rights to the file, and then try again". Note that no authentication window appeared so that I could authenticate. wmp simply gave the above error message. That is the reason I want to include the username and password in the URL. Is it possible to include the username and password within the URL \\serverIP\sharedFolder\filename.wmv ? I know how to do that in a ftp or http URL such as ftp://username:password@serverIP/filename http://username:password@serverIP/filename.html, but not with the above URL. Thanks. Dialup connection on win98 Mazdak5-Jul-04 21:37 Mazdak 5-Jul-04 21:37  I want to format my win98 and install it again. I have a dial up connection on it which I forget its password. I want to use it again after I format/install myy win98. I know some utility like pwl tool or unlock password which I can get that password, but I can't find them. Could someone please give me FREE download of one of these utilities. Mazy "One who dives deep gets the pearls,the burning desire for realization brings the goal nearer." - Babuji Re: Dialup connection on win98 Mekong River8-Jul-04 12:18 Mekong River 8-Jul-04 12:18  How about your ISP? if it is possible you could ask your ISP for your password. Once you have it, you could proceed your task. Roath Kanel APO-CEDC Save Children Norway-Cambodia Office Will Ms stop upgrading w2k after wxp sp2 is released? kfaday4-Jul-04 13:22 kfaday 4-Jul-04 13:22  i mean upgrading as of releasing patches, giving support, etc Anybody know anything about this? this made me wonder about that: <url>http://user.cs.tu-berlin.de/~normanb/ Re: Will Ms stop upgrading w2k after wxp sp2 is released? Michael Dunn5-Jul-04 6:24 Michael Dunn 5-Jul-04 6:24  This page[^] says that mainstream support for Win 2K ends on June 30 next year. --Mike-- Personal stuff:: Ericahist | Homepage Shareware stuff:: 1ClickPicGrabber | RightClick-Encrypt CP stuff:: CP SearchBar v2.0.2 | C++ Forum FAQ ---- Pinky, are you pondering what I'm pondering? I think so Brain, but if we shaved our heads, we'd look like weasels!

Last Visit: 31-Dec-99 18:00     Last Update: 28-Sep-24 7:51 Refresh ᐊ Prev1...362363364365366367368369370371 Next ᐅ

General    News    Suggestion    Question    Bug    Answer    Joke    Praise    Rant    Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.