WIndows Hang during start-up

This error may be caused by a fault in the computer's external cache controller or by bad or mismatched memory chips on the external cache (generally 64, 128, or 256K cache SRAM). If disabling the external cache does not correct this problem, there may be a problem with the motherboard at the current processor speed, A20 handler problems, or bad or mismatched main system RAM chips.
RESOLUTION
Use the following troubleshooting procedures to isolate the cause of the XMS test failure:
Disable the external cache (also known as "secondary cache" or "CPU cache") in CMOS. For information about how to do so, refer to the documentation included with your computer or contact your hardware manufacturer.

NOTE: If disabling the external cache corrects the problem, replace the memory (SRAM) on the cache with the type and speed chips recommended by your hardware manufacturer. If this does not correct the problem, you may have a bad cache controller. Contact your hardware manufacturer for more information.
Disable Turbo in CMOS.
Disable Fast Gate A20 and Fast A20 Display in CMOS.
Try different machine switches with HIMEM.SYS (/M:2, 11, 12, and 13). For more information on this procedure, type "help HIMEM.SYS" (without the quotation marks) at the MS-DOS command prompt.
Replace main system RAM chips with the type and speed memory modules recommended by your hardware manufacturer.

NOTE: You can disable XMS memory testing by adding /TESTMEM:OFF to the device line that loads HIMEM.SYS in your CONFIG.SYS file. For example, DEVICE=C:\DOS\HIMEM.SYS /TESTMEM:OFF
Disabling XMS memory testing may allow HIMEM.SYS to load, but you may experience random file corruption, system instability, or other problems until the underlying hardware problem is resolved.

Most probable cause is faulty memory above 640KB (XMS memory range). If you have more than 1 stick of RAM (except RDRAM which requires 2 modules), try booting from each stick and see what happens. If you only have 1 stick of RAM, try swapping it with a known good stick of like RAM from another PC.

Hope this helps.

Dalton

My organization is ALL Win9x machines! The new P4's we are getting in are NOT compatible with Win9x. Another one I have run into is disable the "Enhanced" IDE controller and change it to "Legacy". Win9x doesn't know what an ATA 133 drive is! Hyperthreading has never been a problem but it's probably a good idea to disable it as Win9x doesn't know what that is either. The machines I setup here have NOTHING in the autoexec.bat OR the config.sys. Newer machines have all of the memory features built in already with drivers etc. Press F8 at bootup, start command prompt only mode, type "cd\windows\command" and type edit. Find the config and autoexec files in the root directory and try to remove or rem out all info in these files. Good luck!

as for xms i foung a few things here that were close. but the last link is for google and there are many things listed there for your problem have a nice day
http://computing.net/windowsme/wwwboard/forum/19150.html
http://computing.net/windowsme/wwwboard/forum/12703.html

http://computing.net/windowsme/wwwboard/forum/2071.html

http://computing.net/windowsme/wwwboard/forum/11061.html

http://www.google.ca/search?q=xms+driver+not+installed&hl=en&btnG=Google+Search&meta=

This question was closed by the author