Win2k Upgrade over NT - very very very slow
Results 1 to 12 of 12

Thread: Win2k Upgrade over NT - very very very slow

  1. #1
    Registered User
    Join Date
    Nov 2000
    Posts
    1,639

    Post Win2k Upgrade over NT - very very very slow

    Welp, Im almost at the end of my short rope over this one..

    So far, this has happened to two PC's. Both were running Windows NT 4.0, SP6, IE 5.5..etc..etc.. very standard PC's. They are IBM Netvista's, using recommended hardware, and up until now, have behaved themselves perfectly. Until we decided to upgrade to Windows 2000. We ran the upgrade, during which, systems files were not backed up, and we converted the drives to NTFS, and the installation completed with out any issues.

    All looks happy, until we restart the PC, and go to login. After logging in, there is a good 10 to 15 minute wait, before you are able to do anything. The start bar does not respond in this time, and the only way to run anything, is through task manager > new task.

    I have (after painfully waiting) updated the system device drivers, and installed the latest Service Pack.

    Has anyone seen something like this before? Any advice?

    Cheers all.
    [email protected]

    http://forum.hot4s.com.au - Hot 4's & Performance cars

  2. #2
    Registered User
    Join Date
    Mar 2001
    Location
    Nashville, TN
    Posts
    280

    Post

    [quote]Originally posted by EvilCabbage:
    <strong>Welp, Im almost at the end of my short rope over this one..

    So far, this has happened to two PC's. Both were running Windows NT 4.0, SP6, IE 5.5..etc..etc.. very standard PC's. They are IBM Netvista's, using recommended hardware, and up until now, have behaved themselves perfectly. Until we decided to upgrade to Windows 2000. We ran the upgrade, during which, systems files were not backed up, and we converted the drives to NTFS, and the installation completed with out any issues.

    All looks happy, until we restart the PC, and go to login. After logging in, there is a good 10 to 15 minute wait, before you are able to do anything. The start bar does not respond in this time, and the only way to run anything, is through task manager > new task.

    I have (after painfully waiting) updated the system device drivers, and installed the latest Service Pack.

    Has anyone seen something like this before? Any advice?

    Cheers all.</strong><hr></blockquote>

    I've always considered it best to just do a clean install of an OS instead of installing it over the previous OS (which I assume is what you did).

    As for your problem, I haven't seen that problem. At work we will install 2k on 400s at a min, and we like to have at least 128mb of memory in them and they run fine. Of course they're not going to win any speed awards, but they get the job done.
    "If there's a better use for the Internet, I haven't found it."
    -Homer Simpson

  3. #3
    Registered User
    Join Date
    Nov 2000
    Posts
    1,639

    Post

    These were both upgrades, yes.

    The problem with rebuilding from scratch (as I have just commited to doing) is there are a lot of technical apps on these boxes, that, although are fully compatible with Windows 2000, it is just time consuming having to re-install them all. Its just something I really dont have the time for... ah well..

    Spec wise, the boxes are beasts, no excuses for running like this.

    Friggin' Windoze dodgyness...

  4. #4
    Banned Ya_know's Avatar
    Join Date
    Jun 2001
    Posts
    10,692

    Post

    These PC's, are they logging into a domain? If so, once they do login (after the 15 minutes), is everything functioning normal? If so, this could be something real simple. Perhaps DNS server address information needs to be added into the TCP/IP advanced settings...Perhaps they were never used with the NT4 Workstations.

    It could be something little, and easily overlooked. Now, if the PC’s are just dog slow with everything, then a rebuild may be your easiest/quickest solution…

  5. #5
    Registered User
    Join Date
    Nov 2000
    Posts
    1,639

    Post

    DNS is fine, etc..etc..

    The thing that annoys me about the whole thing, is the lack of an explanation. There isnt a good reason for the machines to be playing up the way they are, and not being able to explain it is going to piss me off for a while...

  6. #6
    Registered User silencio's Avatar
    Join Date
    Sep 2000
    Location
    Savannah
    Posts
    3,960

    Post

    Have you checked the eventvwr for network/application/etc timeouts. It sounds 2000 can't find something.

    Do they run fine once they're up?

  7. #7
    Registered User
    Join Date
    Nov 2000
    Posts
    1,639

    Post

    Bleh.. I blew the machines away today.

    Like I said, there was nothing obviously wrong. No services doing wierd stuff, no devices appear upset, nothing in the event logs... nothing at all to explain it ... ah well.. better luck next time.

  8. #8
    Registered User
    Join Date
    Aug 2000
    Location
    Enfield, CT
    Posts
    490

    Post

    hmm, my school upgraded some of the pc's (acer aspire p2 350 64 MB ram) from nt 4 to win2k. they were noticably faster. i guess it depends on the system that's upgraded.

  9. #9
    Registered User
    Join Date
    May 2004
    Posts
    3

    Win2k upgrade disaster

    You are absolutely right. I ruined both my PCs at home. It only happens when you do a "live-update" from Microsoft. Is related with a virus that symantec knows about.
    http://securityresponse.symantec.com...or.sdbotz.html

    I instal the virus definition before I did an upgrade and ... nothing. The 2nd PC got ruined. The CPU is 100% and the whole system is stuck. Took me 90 minutes to open NAV. I dont know the solution of the problem ... I am looking for one myself since I have a tone of work due. Well, I guess I will reformat HDD and give up win for good (I am a Linux guy).

    Is not your fault. Is Microsoft. DO NOT DO any upgrade. The system works fine without SP5. You just need SP 4.


    Quote Originally Posted by EvilCabbage
    Welp, Im almost at the end of my short rope over this one..

    So far, this has happened to two PC's. Both were running Windows NT 4.0, SP6, IE 5.5..etc..etc.. very standard PC's. They are IBM Netvista's, using recommended hardware, and up until now, have behaved themselves perfectly. Until we decided to upgrade to Windows 2000. We ran the upgrade, during which, systems files were not backed up, and we converted the drives to NTFS, and the installation completed with out any issues.

    All looks happy, until we restart the PC, and go to login. After logging in, there is a good 10 to 15 minute wait, before you are able to do anything. The start bar does not respond in this time, and the only way to run anything, is through task manager > new task.

    I have (after painfully waiting) updated the system device drivers, and installed the latest Service Pack.

    Has anyone seen something like this before? Any advice?

    Cheers all.

  10. #10
    Registered User
    Join Date
    May 2004
    Posts
    3
    Also I found what Microsoft is saying about it:
    http://support.microsoft.com/default...b;EN-US;841382

    - Cris -

    Quote Originally Posted by EvilCabbage
    Welp, Im almost at the end of my short rope over this one..

    So far, this has happened to two PC's. Both were running Windows NT 4.0, SP6, IE 5.5..etc..etc.. very standard PC's. They are IBM Netvista's, using recommended hardware, and up until now, have behaved themselves perfectly. Until we decided to upgrade to Windows 2000. We ran the upgrade, during which, systems files were not backed up, and we converted the drives to NTFS, and the installation completed with out any issues.

    All looks happy, until we restart the PC, and go to login. After logging in, there is a good 10 to 15 minute wait, before you are able to do anything. The start bar does not respond in this time, and the only way to run anything, is through task manager > new task.

    I have (after painfully waiting) updated the system device drivers, and installed the latest Service Pack.

    Has anyone seen something like this before? Any advice?

    Cheers all.

  11. #11
    Driver Terrier NooNoo's Avatar
    Join Date
    Dec 2000
    Location
    UK
    Posts
    31,824
    Welcome to Windrivers nastase!

    You have sorted your upgrade problems?

    Good information you have dug up there. thanks
    Last edited by NooNoo; May 4th, 2004 at 01:55 AM.

  12. #12
    Registered User
    Join Date
    May 2004
    Posts
    3
    Thanks .... took me a while. Actually I am kind of the end of my rope myself. I spent more than 12 hours trying to fix the problem but ... most of the time is pent waiting for the system to react. Took me 90 min to boot in safe mode and start compmgmt ... then I disabled IPSEC agent as indicated by the KB-841382
    http://support.microsoft.com/default...b;EN-US;841382

    The result ? NOTHING. Same deal. So after all this time I can summarize the whole mess.
    1. Microsoft puts up the update and knows that has a big flaw.
    2. They also know once installed your win2k become USELESS since the CPU is 100%. To open task manager takes 15 min on Athhlon 1GHz with 384 MB ram.
    3. Then they advice everybody to "WAIT TILL THE NEXT SP RELEASE"
    4. They ask MONEY for a HotFix of a problem which was caused by them.
    5. Intead of removing the patch for Win2k ... they do nothing ... so maybe some of us will go to XP (which is not affected) ... well, not me for sure.

    Hmmm ... what can I say more ...

    A good ideea for people that still wanna access their data before a reformat/reinstall is to use a bootable CD with Knoppix or Quantian, which are Linux versions. Once in you can mount your HDD and then burn or back up your data.

    Hope this helped ...
    - Cris -

    Quote Originally Posted by NooNoo
    Welcome to Windrivers nastase!

    You have sorted your upgrade problems?

    Good information you have dug up there. thanks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •