Operating Systems ▼ Windows 10 Windows 8 Windows 7 Windows XP See More... This file is located in the Systemroot\System32\Config directory. This article is intended to help clarify why the shadow drive does not always boot and how to ensure that it will boot in the case of a primary disk failure. SHOW ME NOW CNET © CBS Interactive Inc. / All Rights Reserved. navigate to this website
Please try again now or at a later time. This site is completely free -- paid for by advertisers and donations. Don't hold it down for several seconds, as that will power down the computer.) -Dave Burton d4l, Mar 12, 2006 #2 Advertisements Show Ignored Content Want to reply to this However, the desktop does not appear, and the Welcome to Windows logon screen is displayed again. http://www.tomshardware.com/forum/215300-46-hangs-startup-2000-logo-screen
First Name Last Name Email Join Now or Log In Oops, something's wrong below. I have no idea what to do. Advertisement kjfrey55 Thread Starter Joined: Oct 20, 2002 Messages: 36 I recently tried to install my SBC Yahoo software. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.
Any recovery suggestions? Monitor Displays a White Screen at Startup and Windows 2000 Stops Responding Microsoft Knowledge Base Article: 305227 - After you start your computer, the monitor may display a blank white screen Oops, something's wrong below. Join the community Back I agree Test your smarts. 88% of IT pros got this right.
Find recent content on the main index or look in the archives to find all content. Thanks. I tried booting with logging and then looking in the ntbtlog file, but that seemed pretty useless. No, that one program doesn't work in Virtual PC 7 on the Mac or in VMware on Linux).
The symptom was that Windows 2000 Pro would usually (though not always) get stuck with 11 bars of the "Starting up..." progress bar on the low-res graphical startup screen (i.e., 11/18 https://www.cnet.com/forums/discussions/help-windows-2000-pro-crashes-at-startup-154053/ Renaming the System.alt file should only be used as a last resort after you have tried to recover the system using the ERD. XP usually booted, but I saw it hang in a very similar way during startup, once, with the little moving three-bar progress indicator scanning away endlessly, but no disk activity, and I have one computer with one hard drive containing Windows 2000 Professional.
This disk contains a copy of the system Registry and provides crucial information that you need to use NT Setup's Repair process to locate and repair a damaged NT installation. useful reference Member Login Remember Me Forgot your password? You need to install Linux or something. ;-) Seriously, have you tried wine? Tips, tricks, help?
As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged Now I was able to install the same cd with the usb cd drive on a Fugiji tablet that is made for 98 and 2000 and the setup runs fine. Your name or email address: Do you already have an account? my review here kjfrey55, Jun 9, 2005 #11 kjfrey55 Thread Starter Joined: Oct 20, 2002 Messages: 36 ok guys, get this - Deleting the network settings didn't help.
I sent an email with my reply on that. Thanks. The bios has been updated and unlocked so i'm able to access the advance ide settings as well as the other settings "I had this same problem before I even upgraded
HOW TO: Troubleshoot Startup Problems in Windows 2000 Microsoft Knowledge Base Article: 315396 - This article describes general procedures that you can use to troubleshoot startup problems in Windows 2000. Call us cheap.Bob Flag Permalink This was helpful (0) Collapse - Write back when you get your 2000 CD. by R. Preview post Submit post Cancel post You are reporting the following post: HELP!
Report • #1 phil22 April 14, 2014 at 08:17:42 Well your bound to get the same error when you disable the SATA ports, so that doesn't help you diagnose the cause An error (403 Forbidden) has occurred in response to this request. Sign up now! get redirected here Windows Does Not Start After PcAnywhere 9.0 Installation Microsoft Knowledge Base Article: 317051 - When you restart your computer after you install Symantec pcAnywhere 9.0, you may receive the following error
Had 37 updates (there were none when I checked prior to the above actions). poochee replied Mar 17, 2017 at 11:22 PM "failed to load branding... I rebooted and now my system won't get past the Windows 2000 splash screen. The machine is running great, now, with the original NIC.
Yes, my password is: Forgot your password? I had this happen, too, and it was DAYS before I found the solution. There is no way to narrow down what caused it without other clues so it's google time for you. So, with everything turned off in msconfig (all programs and all non microsoft services)..
Check device manager, msinfo32, event viewer and system information, for conflicts and errors in the hardware and software or 2. Proffitt Forum moderator / February 1, 2006 12:10 PM PST In reply to: HELP! If you're having a computer problem, ask on our forum for advice. Several functions may not work.
If this screen appears again, follow these steps:Check to make sure any new hardware or software is properly installed.If this is a new installation, ask your hardware or software manufacturerfor any I register my software so Microsoft knows what I have. Start by disabling devices that you don't need for your application (especially built-in modems, sound cards, etc.). The posting of advertisements, profanity, or personal attacks is prohibited.
Known Bugs and Issues... Hello and welcome to PC Review. How many more things can go wrong? It might be overheating or is underpowered... 0 Jalapeno OP Danyal_Ali Oct 10, 2014 at 12:26 UTC If you have any devices attached to it such as USB devices,
by R. Discussion in 'Microsoft Windows 2000 Networking' started by Dave Burton, Mar 10, 2006. Note that this is not possible on all computers because of specific firmware restrictions in the Basic Input/Output System (BIOS).