My experience has taught me that in most of these cases the end-user is powering down the PC before properly shutting down the OS (windoze). Without knowing what you have installed (besides windoze) it is very difficult to help you. There can be a myriad of reasons; all pointing to either a...
First you need to know if this app is trying to access hardware - any hardware. Since it probably is - it isn't going to work. NT does not allow direct access to hardware and older DOS apps tend to need to access hardware directly. Why don't you run this on a DOS PC or a dual-boot setup?
Is this server or workstation? If it's server, why worry about it much - unless this causes other problems. If it's workstation - is the adapter an AGP adapter? The correct NT driver is usually the fix for this - that's the NT driver not just any driver! What adapter is it?
Even while you're poking around to see if someone installed anything new, reinstall SP6a. What has changed? Software? Hardware? Anything! - is the NIC plugged into the same port? Is there any remote control installed on this server - like PCAnyWhere? You either try to move the problem or just...
Listen to MrGeek! Who advised you to install SQL Server on a DC? Don't install anything other than NT on this server - unless this isn't a serious database.
Listen to MrGeek and whoever advised you to install SQL Server on a DC? Don't install anything other than NT on this server - unless this isn't a serious database.
There's nothing to do with this log entry. You can add to the log by installing more management funtionality like with SNMP or RMON. A dirty shutdown can happen for many reasons but if you have an UPS that will trap and send messages to a pager (and make a log entry) then you're getting more...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.