[1L]

Any help would be appreciated.

[NYC GOP Chick]

I could be wrong (sure wouldn't be the first time), but I *think* it's better to do a clean install of operating systems. IOW, save everything you want to save and then reformat the hard drive. But best to check with an actual expert.

[Sungirl]

CAn you install that over NT? Did it say it would work? Does seem like alot to ask.

[JRandomFreeper]

Ping.

/john

[KellyAdmirer]

Sounds like a driver conflict. XP has the same kind of situation with certain third-party software. If this really bugs you, I suggest you ask about it on one of the Microsoft W2k newsgroups. You problem is probably not unique. You can probably solve it with a software patch, or by deleting some old software, or updating some old drivers on some other software you have installed.

[IRtorqued]

woodyswatch.com

[RedBloodedAmerican]

What version of NT did you have?

[RedBloodedAmerican]

Check the Advanced tab in Power Options in control Panel. Check these settings.

You might try Microsofts Technet

[Henk]

Make sure you have installed the latest service pack

[Buckeroo]

Take your MSWindows2000 CDRom back to the store and demand your money back. Upon your next boot, save all your files. Goto any one of dozens of Linux websites and download the version of your choice for free. Reformat your disk and install Linux with X11. Goto the Sun website and pick up StarOffice to resume your MSOffice environment.

This is the best information that I can provide.

[RickyJ]

Format your hard disk and install Linux.

[IRtorqued]

here's another web site to check
worldstart.com

[Marauder]

I didn't experience that particular problem, but I did have a few problems when I tried Win2K.

One problem that I remember was an inability to print with my HP printer. Not only were there no drivers - not even any compatible drivers that I could find - but it wouldn't even use the drivers on the CD. It would run the printer, but special characters like bullets and square brackets were changed to something else.

So I went back to Win NT 4.0, the "old reliable" OS. It's working great, and the only thing I miss is the USB support, but I understand I can get an expansion board to facilitate that, when I'm ready to mess with it. I may even try Win2K again, if and when they produce the Service Packs required for normal operation.

[aaaDOC]

Unfortunately, my advice is a little late for you.

I use Windows 98, first edition, with all the patches.

I have not upgraded for several reasons. The main one being...

If it ain't broke, don't fix it!
 

[j_tull]

I've seen this too, usually on a laptop setup for a network, but not attached to the network. During boot, hit F8 and select "Enable boot logging." This should tell you where the hangup is.
Merry Christmas

[Souled_Out]

Probably one of the easiest things to do is remove all cards (sound card, NIC etc..) from your system and reinstall with the bare essentials (hard drive, CD ROM, monitor, keyboard and mouse). Then once you have the system booting add the cards back into the system one at a time. Start with the NIC so you will beable to connect to the net and get SP2.

[Michael Barnes]

Just a thought, but try booting up in "safe Mode", then shutting down. If that works, it's definatly driver related. If not, I would check APM and your BIOS rev. (Especially if you have a VIA chipset).

Good luck...happy holidays to you and yours..

[Blennos]

I had the very same problem when I first installed Win2k. It was indeed a BIOS problem. I went into the BIOS, turned off or disabled anything not absolutely essential and magically the machine booted up into Win2K. Then I went back into the BIOS, turned on items one at a time. Now all is well.

It is a good idea to write down what you are changing in the BIOS for later use.

Good Luck.

[Still Using Air]

Win2K APM and Shutdown Issues I don't know if this is your answer, but it's another place to look.
I recently upgraded to Win2000 Pro, and I most definately love it. I have a 3 month old computer, lots of good ram, and Win2K is the fastest O/S I've ever used, and the most stable.
Before the penguin people jump on me, I'm also running Mandrake Linux 8.1 on two other partitions of this drive, and I have to agree with the pro-Win2K people. Sure, Linux is relatively stable, and not prone to a lot of internet virii, but the lack of quality graphics/web design apps keep me rebooting to Windows.
After finally taking the plunge to upgrade from Win98SE, I find I am hardly ever in Linux anymore. With a good up-to-date virus program, and Zone Alarm, internet security is no longer much of an issue in Windows. IMHO.

[bigcheese]

I run 2000 servers and 2000 workstations. Runs like charm. But keep up on the patches ;-)

BUT, and this is a biggie, me and my guys could not get a machine to install over an existing NT install. We would even delete NT programs files all together, leaving just an NTFS disk with some unimportant (= to the install) data, .... still no go.

we did have one or two desktops we got working but there has been mystery problems ever since. But I would never ever try to upgrade a server in any manner. The last thing I need is more problems with IIS than just keeping up with the patches and the ASP cowboy newbies who host with us.

I believe it has something to do with data in the boot sector. Been noticing this type of problem with MS since Win 98.

Clean your disk... not FDISK, but if it is IDE, get a low level formatter (back up your data, of course). Low level formatting is a *must* to clean the boot sector. If SCSI, the built-in SCSI bios should do the trick (usually can be entered right after BIOS on boot. Then let 2000 do the partitioning and formatting (another thing I found out!)... It doesn't seem to like you doing the partitioning yourself beforehand.

I have been running MS servers and workstations since NT 3.51.... since before ASP (I belive it was IIS 2).... And after this last go around with 2000, I swore what I have swore a dozen times before.... slave the data disks, copy the data over, and do a low level and do a clean install.

In fact, in my 6-7 years of running MS OS's in production enviroments.... I have found the easiest way to fix any *system* problem is low level format and re-install.

pathetic in a way, but once you have 2000 operating, you will love it.

[Paulus Invictus]

An iMAC and OS 10.1 will clear that right up for you! (and hackers won't be able to access and wreck your hard drive either).