Search results for query: *

at the one grand level, go AMD. You should get a 17" Digital monitor, 256M PC133SDRAM, 30Gig HD, CDRW, DVD, GeForce2 32M Video, and the other accessories. at the 1500.00 level go Intel. Your should get a 1.3G P4, 128M RDRAM, 40 Gig HD, CDRW, DVD, Geforce2 32M Video and the other stuff...

have you tried to restore a previous copy of explorer or attempted to repair it through the control panel? add/remove programs, remove explorer button and a menu comes ups to make the selection. if your system tray is identical to theirs, it must be a noncompliant program installation writing...

when you updated 5.5 did you go back into internet options and the advanced tab to enable/disable features? I have customers who don't and then experience atypical errors such as yours. the usual culprit has been disabled java. the culprit in any case points to a plugin not launching...

try removing the driver, shutting down, removing the modem, rebooting, shutting down, inserting modem, loading driver and try dialing and shutdown again. Also, get the latest modem driver. W2K is finicky.

reinstall the snap-ins and email client. the only other instance this has popped up is when the HD, over 16gig is formatted with an old drive utility that doesn't understand the very large drive structure and creates odd sized sectors.

More common than makes sense is the fluctuation of power when it steeps to about 124 to 126 or drops to 105 to 107. This combined with poorly made memories or poorly designed platforms for intel/via chipsets lead to lockups. We have seen a number of freezes surrounding poor video drivers or...

I agree about checking the memory. Most errors seem to spring from the lack of serial presence detection or running suspect PC133 at 133mhz when it should be slowed to PC100 specs. Memory has been the root of my of our installation problems. If there is two or more pieces make sure they are...

I have seen a few compaqs come into the shop with reboot issues. Most reboot when switching to GUI mode. In three of the cases we just downloaded a new driver for the video. In two cases there was no support for W2K Pro on the driver side. Once we uninstall Norton 5.0 and disabled the BIOS...