Microsoft strikes again

[Capmaster]

I was setting up someone else's machine yesterday and loading Win98SE at their request. The new machine was a 2.4 GHz P4.

During the Windows installation it reboots. I got an error screen that said "While initializing device NDIS: Windows protection error." It recommended restarting, so I did. Same thing. It doesn't do it in safe mode though.

This morning I looked it up and found it in knowledge base article 312108. It said "The timing calibration code in the network driver interface specification driver causes a divide by zero if the CPU runs at 2.2 GHz or faster. This problem does not occur with CPUs that run at 2.1 GHz or slower."

It says there is a fix, but I need to contact Microsoft support to arrange for payment.

Money-grubbing whores

[tekkieman]

It says there is a fix, but I need to contact Microsoft support to arrange for payment.

Money-grubbing whores

Just their way of burying their old POS OS'es. Pay them to keep using it, or pay them to upgrade. You DO have a choice!

[Capmaster]

It says there is a fix, but I need to contact Microsoft support to arrange for payment.

Money-grubbing whores

Just their way of burying their old POS OS'es. Pay them to keep using it, or pay them to upgrade. You DO have a choice!

I did get Win2K to work on the system last night. The network card still isn't seeing the cable modem, but it was getting late and my enthusiasm was dwindling by then. Tonight I expect to tweak it and put in the latest service pack and device drivers.

[BJ_M]

the fix for this problem is free ... get it here

http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;q243199



thank you - thank you ..

[indolikaa]

the fix for this problem is free ... get it here

http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;q243199



thank you - thank you ..

Brilliant! (Passes Guinness beer around...)

[Capmaster]

the fix for this problem is free ... get it here

http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;q243199



thank you - thank you ..

Got it. Thanks BJ_M. But does it matter that those aren't my symptoms and that the article says the fix should only be used if you experience the symptoms listed? I'm ready to believe it's Microsoft blowing more smoke up our collective asses, and the whole slew of NDIS issues is solved with a single patch.

I've got Win98 on the back burner, and he's using Win2K on his machine now. I told him I think he's better off, but if it becomes a case of app after app not working, he might want me to try Win98 with the patch. He runs strategy games and Atari/Nintendo emulators on his machine. I'm not sure how they'll do in Win2K yet.

[BJ_M]

i can not swear to it -- but that link/patch was stated to be the exact fix for the CPU over 2.2 p4 issue as you described ..

i got that info from the VIA motherboard chipset forum and it was also confirmed at another forum (cant remember which) as a solution to the same problem .

[Capmaster]

i can not swear to it -- but that link/patch was stated to be the exact fix for the CPU over 2.2 p4 issue as you described ..

i got that info from the VIA motherboard chipset forum and it was also confirmed at another forum (cant remember which) as a solution to the same problem .

That's good enough for me Thanks again

[BJ_M]

there are also a lot of posts with people having problems with more than 512 of memory also -- and installing win98

[Capmaster]

BJ_M,

That was indeed the right patch He wanted Win2K removed, the HD repartitioned and formatted, and Win98SE put back in. I was able to get Win98 loaded by using F8 at boot, selecting step-by-step, and replying "no" when it asked to load NDIS.VXD. Once Win was installed, I just ran the patch from the command line and presto! Now it boots fine, the network card works, and he's happy as a two-peckered dog because he upgraded from a 700 Celeron and this 2.4 P4 is insanely fast by comparison

I owe you a beer