cluberti

Sorry, there's two posts in this thread, so it's getting confusing. We're not responding to you, but I had a chance recently to look at the mobo you're using, and I have a Gigabyte GA-P31-ES3G system sitting over here in the lab I'm sitting in, and I tried the same installation as you - Win7 x86 installed quite fast, about 25 minutes, and the x64 install took 2 hours. It's either the 64bit driver for the ICH7 (I also have an ICH9 and a few ICH10 systems that do not have this problem), or some other driver that would affect install (perhaps something on the USB or PCI bus, not sure). However, once installed, it boots and runs just as fast as the x86 install, for what it's worth. You might want to disable anything that's not necessary to install Win7 in your system's BIOS (like the network interfaces, audio, USB, etc) and see if that changes anything.

You have an explorer shell extension causing the error when it tries to load and hook explorer.exe if it only happens once for the life of the session. You can see your hooks with a combination of Sysinternals' Autoruns and Nirsoft's ShellExView.

Agreed - it's the nvidia driver causing the slowdowns.

This will change Windows 2000's HAL to use the PMTimer instead of the ACPI timer. It might drop the CPU by a bit, but nowhere near as far as the other apps will. Using the PMTimer will lessen the load on a machine with an ACPI timer issue, but this is more relevant on AMD chips than Intel chips, and will do little on Intel chips (this makes a huge difference on AMD processors).

64bit versions of Windows support a max of 64 processors (32 cores on one socket someday??? ), 32bit would support a max of 32 processors - again, theoretical. But you are correct in the socket support - 1 for the home versions, 2 for the professional/business/ultimate versions.

They're both technically the same code, so slowness like that would definitely come back to driver issues (and seeing how slow the actual install is, probably the disk subsystem drivers). If you can reproduce it on a clean x64 install (not partitioned), you probably want to make that issue known.What hardware are we talking about here?

One thing you also may wish to consider is that your laptop (Thinkpad x61) wasn't designed for Windows 2000 (it ships with Vista, I believe), and may not have the necessary apps and utilities to run said OS properly.

All have the same limitations - technically most of that is still NT4 code, and didn't change much for XP or 2003 (it's better, but it's still somewhat inefficient). You would have to use an OS designed AFTER the advent of such multicore CPUs before you can really use them properly (XP came out before multicore, and 2003 is built on that codebase - however, Vista and 2008 were out after, and are tweaked and written to better utilize these types of CPUs). What specifically are you trying to do? If all you want is to reduce CPU power and heat consumption, you can use apps (like RMClock or Intel SpeedStep, if supported) to try and compensate for Windows 2000's shortcomings.

OK, I think this is because of the score rebasing between RC and betas. Can you try this - run "winsat cpu -compression -v" and winsat cpu -encryption -v" and paste just the section below "Running: CPU Assessment" in the output? I need to see what scores you're getting, because I have access to a T2500 later today.

Can you run "winsat cpu -v" and paste the output? Also, what was the score in Win7 7000?

If we're talking about TRUE multiprocessors (and not multi-core, or worse, hyperthreading), Windows 2000 should work fine without any additional changes. However, if we're talking about newer CPU parts that are multicore and/or hyperthreaded, Windows 2000's scheduler does not "understand" that these may be logical processors on physical CPUs (or in the case of hyperthreading, not even a real processor) and Windows 2000 will schedule across all "processors" equally regardless of whether or not they're a dedicated CPU, a dedicated core on a multi-core die, or an HT-enabled virtual processor (whereas XP "understands" hyperthreading, and Vista/2008 and Win7 actually understand the difference between a dedicated CPU and a CPU with multiple cores as well, and change processor scheduling accordingly). There have been fixes to Windows 2000 for AMD timer issues and for Services For Macintosh race conditions on hyperthreaded CPUs, but there's no patch to make Windows 2000 "understand" multiple cores or hyperthreaded CPUs. Usually this is seen with hyperthreading and less with multicore chips. Is that the case here?

From what I understand, there were changes to WinSat between the betas and the RC, so the processor score changing may be expected, especially considering you can change it by changing the power scheme. What CPU is this?

Agreed - probably the video driver given the symptoms. What hardware is this?

Microsoft doesn't support, AT ALL, products that have exited their support phase. As Windows ME is not considered a business OS (NT-based), it only got 5 years of support, ending in 2006 (it was available at the end of 2000, so the clock started in 2001). If you want updates, you'll have to find them outside of Microsoft - the_guy's service pack seems quite a reasonable suggestion given the circumstances. Also, in regards to your posts, you are free to your feelings and opinions but profanity will not be tolerated. If you have a rant, try to make it somewhat targeted and legible, and written in proper English, without profanity. I might even read them on my own in the future, without seeing it only because I had to check your posts for profanity. Rule 7.a deals with this, and if we have to warn again, you will be banned.

Well, this is a bit of a stretch, but I think PunkBuster is causing it. // This thread holds a lock on a notification timer that the crashing thread has 2 IRPs waiting on: 2: kd> !thread fffffadf98ffe040 THREAD fffffadf98ffe040 Cid 06b4.06cc Teb: 000000007efd8000 Win32Thread: 0000000000000000 WAIT: (DelayExecution) UserMode Non-Alertable fffffadf98ffe0f8 NotificationTimer Not impersonating DeviceMap fffffa8000003780 Owning Process fffffadf9b8ddc20 Image: PnkBstrB.exe Attached Process N/A Image: N/A Wait Start TickCount 1751998 Ticks: 0 Context Switch Count 12765540 UserTime 00:00:00.515 KernelTime 00:00:00.203 Win32 Start Address 0x00000000002da860 Start Address kernel32!BaseThreadStartThunk (0x000000007d4d1504) Stack Init fffffadf850c4e00 Current fffffadf850c49b0 Base fffffadf850c5000 Limit fffffadf850bf000 Call 0 Priority 8 BasePriority 8 PriorityDecrement 0 Child-SP RetAddr : Args to Child : Call Site fffffadf`850c49f0 00000000`000006cc : 00000000`0000000f 00000000`00000008 fffffadf`98ffe040 fffff800`0127ec16 : nt!KiSwapContext+0x85 fffffadf`850c4b70 00000000`0000000f : 00000000`00000008 fffffadf`98ffe040 fffff800`0127ec16 00000000`00000003 : 0x6cc fffffadf`850c4b78 00000000`00000008 : fffffadf`98ffe040 fffff800`0127ec16 00000000`00000003 00000000`00000144 : 0xf fffffadf`850c4b80 fffffadf`98ffe040 : fffff800`0127ec16 00000000`00000003 00000000`00000144 00000000`00000001 : 0x8 fffffadf`850c4b88 fffff800`0127ec16 : 00000000`00000003 00000000`00000144 00000000`00000001 fffffadf`90a8b180 : 0xfffffadf`98ffe040 fffffadf`850c4b90 fffff800`0102e33d : 00000000`78b83980 00000000`00bff110 00000000`00bffd00 00000000`7efd8000 : nt!NtDeviceIoControlFile+0x56 fffffadf`850c4c00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3 I believe that due to the fact that the kbdclass IRPs on the crashing thread are waiting on the above timer, and this thread appears to have potentially spawned the csrss.exe thread that is crashing, that when there was an attempt to access nonpaged pool the crash was caused. I can see that the address being requested is space allocated for expansion, but that hasn't been allocated (thus causing the page fault and the crash). 2: kd> !address fffffadfd8fb77d0 fffffadf9ce00000 - 0000000063200000 ffadf9871d040 Usage KernelSpaceUsageNonPagedPoolExpansion I believe PunkBuster is a copy protection mechanism, so I don't know how it got on your box or for what software package, but if this is indeed causing the crash you might be SOL if you still need to use said software (probably won't work without the copy protection on the box). I do believe a google search for punkbuster and bugcheck's 0xA do come up with quite a few hits, so while I can't nail this down due to the paged out stack it does seem the most likely (the crashing thread is waiting on the timer in this thread, which appears to be doing an IO Control operation on the kbdclass driver, which the IRPs are waiting on, etc).

Looks like a toolbar or an add-in is failing during a repaint of the explorer UI. In digging into the callstack, I can see that the toolbar has a folder location on the stack: // First argument to comctl32!ToolbarWndProc contains the folder location: 0:001> kb ChildEBP RetAddr Args to Child 00fcf7e8 7e428ff5 77443a2c 0001007c 00fcf8c4 ntdll!KiFastSystemCallRet 00fcf908 7744584b 000cb2d8 00000000 00fcfa14 user32!NtUserBeginPaint+0xc 00fcf9ac 7e418734 0001007c 0000000f 00000000 comctl32!ToolbarWndProc+0xc60 00fcf9d8 7e418816 77444beb 0001007c 0000000f user32!InternalCallWinProc+0x28 00fcfa40 7e42a013 0009f238 77444beb 0001007c user32!UserCallWinProcCheckWow+0x150 00fcfa70 7e42a039 77444beb 0001007c 0000000f user32!CallWindowProcAorW+0x98 00fcfa90 773e1b67 77444beb 0001007c 0000000f user32!CallWindowProcW+0x1b 00fcfaac 773e1eba 0001007c 0000000f 00000000 comctl32!CallOriginalWndProc+0x1a 00fcfb08 773e207c 000e8d58 0001007c 0000000f comctl32!CallNextSubclassProc+0x3c 00fcfb2c 010021b2 0001007c 0000000f 00000000 comctl32!DefSubclassProc+0x46 00fcfb48 773e1eba 0001007c 0000000f 00000000 explorer!s_FilterCaptureSubclassProc+0x41 00fcfba4 773e20df 000e8d58 0001007c 0000000f comctl32!CallNextSubclassProc+0x3c 00fcfbf8 7e418734 0001007c 0000000f 00000000 comctl32!MasterSubclassProc+0x54 00fcfc24 7e418816 773e208b 0001007c 0000000f user32!InternalCallWinProc+0x28 00fcfc8c 7e428ea0 0009f238 773e208b 0001007c user32!UserCallWinProcCheckWow+0x150 00fcfce0 7e428eec 005fb1a0 0000000f 00000000 user32!DispatchClientMessage+0xa3 00fcfd08 7c90e453 00fcfd18 00000018 005fb1a0 user32!__fnDWORD+0x24 00fcfd2c 7e42aef1 7e42aedc 0001007c 0000005e ntdll!KiUserCallbackDispatcher+0x13 00fcfd40 010053b4 0001007c 00000000 000bf824 user32!NtUserCallHwndLock+0xc 00fcfd64 01005492 00000113 000bf824 00010078 explorer!CTaskBand::_AsyncAnimateItems+0x64 00fcfde8 01001b5c 00010078 00000113 00000003 explorer!CTaskBand::v_WndProc+0x271 00fcfe0c 7e418734 00010078 00000113 00000003 explorer!CImpWndProc::s_WndProc+0x65 00fcfe38 7e418816 01001b1d 00010078 00000113 user32!InternalCallWinProc+0x28 00fcfea0 7e4189cd 0009f238 01001b1d 00010078 user32!UserCallWinProcCheckWow+0x150 00fcff00 7e418a10 00fcff28 00000000 00fcff44 user32!DispatchMessageWorker+0x306 00fcff10 01001a35 00fcff28 00000000 010460f8 user32!DispatchMessageW+0xf 00fcff44 0100ffd1 00000000 00fcffb4 77f76f42 explorer!CTray::_MessageLoop+0xd9 00fcff50 77f76f42 010460f8 0000005c 00000000 explorer!CTray::MainThreadProc+0x29 00fcffb4 7c80b713 00000000 0000005c 00000000 shlwapi!WrapperThreadProc+0x94 00fcffec 00000000 77f76ed3 0007fdbc 00000000 kernel32!BaseThreadStart+0x37 // Looks like your application data folder is in a user location called "flashram": 0:001> du 0001007c 0001007c "\Documents and Settings\Flashram" 000100bc "\Application Data" // It looks like, perhaps, this could be a problem with either the ATI software or Yahoo Messenger: 0:001> dc 0x0009f238 0x0009f238+500 0009f238 0000003f 00000000 00be0000 7c8130ae ?............0.| 0009f248 00000000 00000008 00000000 00000000 ................ 0009f258 00000000 00000000 00000000 00000000 ................ 0009f268 00000000 00000008 00000000 00000000 ................ 0009f278 00000000 00000000 00000000 00000000 ................ 0009f288 00000000 00000000 00000003 0009f298 ................ 0009f298 00000000 00000000 000a1cd0 003b006d ............m.;. 0009f2a8 003a0043 0050005c 006f0072 00720067 C.:.\.P.r.o.g.r. 0009f2b8 006d0061 00460020 006c0069 00730065 a.m. .F.i.l.e.s. 0009f2c8 0041005c 00490054 00540020 00630065 \.A.T.I. .T.e.c. 0009f2d8 006e0068 006c006f 0067006f 00650069 h.n.o.l.o.g.i.e. 0009f2e8 005c0073 00540041 002e0049 00430041 s.\.A.T.I...A.C. 0009f2f8 005c0045 006f0043 00650072 0053002d E.\.C.o.r.e.-.S. 0009f308 00610074 00690074 00000063 00000000 t.a.t.i.c....... 0009f318 001d000e 000c010a 00000000 0000034c ............L... 0009f328 00000001 00000001 00000000 0009f330 ............0... 0009f338 00000000 77be0000 0009fe68 00000000 .......wh....... 0009f348 00000000 00000000 0009ed98 ffffffff ................ 0009f358 00000000 00000000 00000000 00000000 ................ 0009f368 000000b8 00000001 000000bc 00000001 ................ 0009f378 00000000 00000000 0000001a 00000000 ................ 0009f388 000e0060 000b0118 00000000 20d04fe0 `............O. 0009f398 10693aea 0008d8a2 9d30302b 432f0019 .:i.....+00.../C 0009f3a8 00005c3a 00000000 00000000 00000000 :\.............. 0009f3b8 00000000 31006a00 00000000 00000000 .....j.1........ 0009f3c8 44001000 6d75636f 73746e65 646e6120 ...Documents and 0009f3d8 74655320 676e6974 44000073 04000300 Settings..D.... 0009f3e8 00beef00 00000000 14000000 44000000 ...............D 0009f3f8 63006f00 6d007500 6e006500 73007400 .o.c.u.m.e.n.t.s 0009f408 61002000 64006e00 53002000 74006500 . .a.n.d. .S.e.t 0009f418 69007400 67006e00 00007300 42002600 .t.i.n.g.s...&.B 0009f428 00003100 00000000 10000000 6c6c4100 .1...........All 0009f438 65735520 2a007372 04000300 00beef00 Users.*........ 0009f448 00000000 14000000 41000000 6c006c00 ...........A.l.l 0009f458 55002000 65007300 73007200 18000000 . .U.s.e.r.s.... 0009f468 31005800 00000000 00000000 41001000 .X.1...........A 0009f478 696c7070 69746163 44206e6f 00617461 pplication Data. 0009f488 03003800 ef000400 000000be 00000000 .8.............. 0009f498 00001400 70004100 6c007000 63006900 .....A.p.p.l.i.c 0009f4a8 74006100 6f006900 20006e00 61004400 .a.t.i.o.n. .D.a 0009f4b8 61007400 20000000 31003a00 00000000 .t.a... .:.1.... 0009f4c8 00000000 59001000 6f6f6861 24000021 .......Yahoo!..$ 0009f4d8 04000300 00beef00 00000000 14000000 ................ 0009f4e8 59000000 68006100 6f006f00 00002100 ...Y.a.h.o.o.!.. 0009f4f8 42001600 00003100 00000000 10000000 ...B.1.......... 0009f508 73654d00 676e6573 2a007265 04000300 .Messenger.*.... 0009f518 00beef00 00000000 14000000 4d000000 ...............M 0009f528 73006500 65007300 67006e00 72006500 .e.s.s.e.n.g.e.r 0009f538 18000000 3100ac00 00000000 00000000 .......1........ 0009f548 34001000 33376265 2d353939 33313366 ...4eb73995-f313 0009f558 3466342d 39342d61 312d3561 64346362 -4f4a-49a5-1bc4d 0009f568 65336337 2e383665 756c7079 006e6967 7c3ee68.yplugin. 0009f578 03007000 ef000400 000000be 00000000 .p.............. 0009f588 00001400 65003400 37006200 39003300 .....4.e.b.7.3.9 0009f598 35003900 66002d00 31003300 2d003300 .9.5.-.f.3.1.3.- 0009f5a8 66003400 61003400 34002d00 61003900 .4.f.4.a.-.4.9.a 0009f5b8 2d003500 62003100 34006300 37006400 .5.-.1.b.c.4.d.7 0009f5c8 33006300 65006500 38003600 79002e00 .c.3.e.e.6.8...y 0009f5d8 6c007000 67007500 6e006900 3c000000 .p.l.u.g.i.n...< 0009f5e8 31004000 00000000 00000000 4d001000 .@.1...........M 0009f5f8 46494e41 00545345 03002800 ef000400 ANIFEST..(...... 0009f608 000000be 00000000 00001400 41004d00 .............M.A 0009f618 49004e00 45004600 54005300 18000000 .N.I.F.E.S.T.... 0009f628 32005a00 00000000 00000000 70000000 .Z.2...........p 0009f638 6967756c 72702e6e 7265706f 73656974 lugin.properties 0009f648 03003a00 ef000400 000000be 00000000 .:.............. 0009f658 00001400 6c007000 67007500 6e006900 .....p.l.u.g.i.n 0009f668 70002e00 6f007200 65007000 74007200 ...p.r.o.p.e.r.t 0009f678 65006900 00007300 00002000 00000000 .i.e.s... ...... 0009f688 00600033 000c01b8 0009f828 ffffffff 3.`.....(....... 0009f698 00000000 00000000 00000000 00000000 ................ 0009f6a8 00000001 0009f320 00000000 0000000d .... ........... 0009f6b8 00000000 00000000 00000000 77be144f ............O..w 0009f6c8 0000000b 00000001 00000002 00000001 ................ 0009f6d8 0009d800 00000000 00000000 00000000 ................ 0009f6e8 77be144f 00000001 77be1a08 006e0049 O..w.......wI.n. 0009f6f8 00650074 006e0072 006c0061 00500020 t.e.r.n.a.l. .P. 0009f708 004d0043 00430020 006e006f 00650076 C.M. .C.o.n.v.e. 0009f718 00740072 00720065 00630000 0033006d r.t.e.r...c.m.3. 0009f728 002e0032 006c0064 0000006c 00000000 2...d.l.l....... 0009f738 00000000 .... Since the problem has already occurred when a static dump is taken (the caller to the worker thread is a fastcall, so it goes away before this finishes and crashes) we have to do some investigation, but it does look like perhaps one of these two could be part of the problem. Assuming you have the yahoo toolbar/messenger installed (and this is a toolbar/taskbar notification area repaint), it seems more likely that the Yahoo toolbar or messenger is causing it, but again, seeing the ATI driver in the heap region near it could mean otherwise. I'd start by removing the Yahoo toolbar if you don't use it, or even as just a test, and see if the problem clears up.

Server 2008 and Vista SP1 are the exact same code tree, so drivers designed for one will work for the other in almost all circumstances.

PM sent.

Not on real hardware, no. The NT boot manager and SMSS.exe literally shut everything down during a shutdown and then call the BIOS to reboot the box. I suppose you could consider rewriting your own kernel to handle this differently, but with the stock kernel this isn't possible.

I had the same problem on my Asus board that only resolved itself when I disabled the Linux boot partition in the BIOS - once that was disabled, everything installed quickly as it should have.

They're actually the same issue, according to your logs. Upload the .dmp files and we'll take a look.

He doesn't owe us anything, including a reply. It's his life, and regardless of what anyone thinks, he's free to do with his life and his code what he pleases.

Nothing on Technet yet (integrated ISOs).... here's hoping e get more than just the installers. Supposedly within 2 weeks they'll appear on Technet and MSDN. Not confirmed, but from a reliable source so it's almost as good as confirmation directly .

Well, considering Internet Connection Sharing automatically tries to use the same subnet to dole out IPs, I think changing your internal subnet to something different might help quite a bit, perhaps 172.16.0.x or 10.0.0.x (both /24, of course).

Merging topics. Do NOT double post.