diis

I get this error message during the install of Windows 2k on a recently formatted HD: An unexpected error (268353600) in line 1562 in D:\nt\private\ntos\boot\setup\arcdisp.c I think that's a Ramdrive of some sort, because d: is my cd-rom drive and that directory isn't on the cd. I've done a low level format, and ran scandisk to see if there were any physical problems with the HD. I've tried two different retail Windows 2kpro cds, and I've tried installing from the 4 bootdisks and from the /i386/winnt.exe file. The message comes up after booting with the 1st startup disk, or after the winnt.exe finished copying the install files to the HD and restarts.

No overclocking. In fact, I've even tried underclocking the bus speed just to see if it might have some effect. I've also done a BIOS reset. I don't think the problem is with the CD-rom drive, because when you boot from the floppys, the error message pops up before the CD is ever accessed.

Can anyone give me some directions on how to disable ACPI steering in Windows 2000? I did it once a long time ago, and I completely forgot how I did it.

thanks all. It worked beautifully. -Jason

I work in a technical support department for a company who takes email support questions. Very often, I request a customer's msinfo32 file to try and troubleshoot any problems they might be having. Most of us here use Windows 2000 pro, because we find it to be very convienent to use an operating system that will not work with any of our products . The problem is that most of our customers use Windows 98, and we have to shift computers to view them. I am tired of doing this because I am pretty lazy when it comes to moving my IT trained ***. Any ideas on how to view Windows 98 msinfo files from Windows 2000 Pro? -Jason

I thought of this, but the problem there is that Windows 2000 can't export the Windows 98 file from the msinfo tool. The customer could, but we have enough problems getting the (usually) ignorant customers to create the msinfo file to begin with. Having it exported to .txt would probably be more trouble than it's worth. I was hoping there might be a command line parameter or possibly a third party program that might do it for us. Our org. is not very big, 5 people servicing about 200-300 unique customers/day. But we only need the system info from maybe 30% of these.