Found this Technet article for you: See the link or read below as I cut and pasted... http://support.microsoft.com/default.aspx?scid=kb;en-us;148919&Product=w98 Windows Restarts Continuously View products that this article applies to. This article was previously published under Q148919 SYMPTOMS When you start your computer, Windows may restart continuously CAUSE This behavior can occur if Win.com is called from the Autoexec.bat file using the /W or /WX switch. RESOLUTION To resolve this issue, follow these steps: Restart your computer. Windows 95: Restart your computer. When you see the "Starting Windows 95" message, press the F8 key, and then choose Safe Mode Command Prompt Only from the Startup menu. Windows 98: Restart your computer, press and hold down the CTRL key after your computer completes the Power On Self Test (POST), and then choose Safe Mode Command Prompt Only from the Startup menu. For more information about Windows 98 startup, see the following article in the Microsoft Knowledge Base: ARTICLE-ID: 178548 TITLE : No "Starting Windows 98" Message at Startup Type the following line and then press ENTER: edit autoexec.bat Locate the line that reads: win.com /W -or- win.com /WX Remove the "win.com" line. Save and then close the Autoexec.bat file. Restart the computer. MORE INFORMATION The /W and /WX switches are typically used to restore the original Config.sys and Autoexec.bat files and restart the computer after you restart your computer in MS-DOS mode. The /W switch on the Win.com line causes Win.com to rename the current Config.sys and Autoexec.bat files to Config.app and Autoexec.app, restore the original Config.sys and Autoexec.bat files from the Config.wos and Autoexec.wos files, delete the Config.wos and Autoexec.wos files, and then display the following message: Press any key to continue... When a key is pressed, the computer is rebooted to Windows. If the /WX switch is used instead of the /W switch, Win.com performs the same steps, but does not display the above message. When the /W or /WX switches are used in the Autoexec.bat file after you restart your computer in MS-DOS mode, the original Config.sys and Autoexec.bat files are successfully restored from the Config.wos and Autoexec.wos files, and Windows starts normally after the computer is rebooted. However, if you use the /W or /WX switch in the Autoexec.bat file at any other time, the Config.wos and Autoexec.wos files do not exist and the current Config.sys and Autoexec.bat files remain in the root folder of the boot drive. Because the /W or /WX switch remains in the Autoexec.bat file, Windows restarts continuously. For additional information about the process that occurs when you restart your computer in MS-DOS mode, please see the following article in the Microsoft Knowledge Base: ARTICLE-ID: 138996 TITLE : Description of Restarting Computer in MS-DOS Mode

0

you said that your pc kept restarting this can hapen because of a faulty power supply this may or may not be your problem. Scsi - What you call your week-old underwear

0

i did the command prompt thing, and nothing comes up in my Autoexec.bat, what do i do now?/

0

Start removing hardware one piece at a time, including removing, if possible, the associated drivers. When I say hardware, I do mean to include the mouse and keyboard. While the PC will boot without a mouse, some systems will not boot without a keyboard. If this is your case, then get a known good keyboard, (not a new one), and try it. (Sometimes new equipment is bad). You could try, in Safe Mode, Start|Run, type MSCONFIG, click OK, then click the "startup" Tab and un-check everything, then try to restart in Normal mode. If that does not work, go back into MSCONFIG, and on the General Tab, click selective startup and start unchecking items. If that does not work, press F8 during boot up, select the Bootlog option, (not sure which one it is), and let the system boot normally. When it "reboots", enter Safe Mode, navigate to the root directory, C:\, look for the Bootlog logfile and open it. Scroll to the bottom and somewhere around there you will be pointed in the direction of your problem. It will not "tell" you, you will have to interpret the findings yourself, or post the last few lines here for feedback. Try installing your hardware, one piece at a time, into a known, good computer. Since you post here, you have access to one. Keep switching until you find the culprit. If all tests OK, then I would say you have a hardware conflict requiring proper installation of drivers. And remember, sometimes hardware just won't work in some systems, due to the vendors resource assignments. I had two Digiboards not work in a new Dell bought for them, but they worked in an older Gateway. This was due to how the vendor assigned the motherboard resources to the associated PCI slots. End users could not manipulate them. Re-post to let me know if this helps. This is a lot to do, but needed to find the problem. I have another suggestion, one that should only be used by advanced users because it involves deleting a key in the registry, and you will have to make sure you have all the drivers for your hardware available. Normally, Your problem sounds like a hardware conflict or bad memory addresses in RAM, but my bet is a hardware conflict.

0

Theres no hardware to pull, i disabled the sound in the bios, no im trying to figure out how to disable the onboard Matrox 8MB AGP video, i think that could have a problem. The sound i didnt want to install because the program to run it, is 10MB, and trying to download that on a Modem :(. The memory was pulled from a working computer, it is Micron memory i know its compadible. Sence i dont have the right drivers for this board, should i try installing a diffrent windows like 2000/XP that would have the drivers for the hardware in this machine. Someone tried telling me the motherboard was bad, i dont think thats the case if it keeps restarting.

0

Heres what i got in the Bootlog LoadStart = DISPLAY.drv LoadSuccess = DISPLAY.drv InitDone = DISPLAY Init = Display Resources InitDone = Display Resources LoadStart = C:\WINDOWS\fonts\MARLETT.TTF LoadFail = C:\WINDOWS\fonts\MARLETT.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\SSERIFE.FON LoadSuccess = C:\WINDOWS\fonts\SSERIFE.FON LoadStart = C:\WINDOWS\fonts\LUCON.TTF LoadFail = C:\WINDOWS\fonts\LUCON.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\TAHOMA.TTF LoadFail = C:\WINDOWS\fonts\TAHOMA.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\TAHOMABD.TTF LoadFail = C:\WINDOWS\fonts\TAHOMABD.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\ARIAL.TTF LoadFail = C:\WINDOWS\fonts\ARIAL.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\ARIALBD.TTF LoadFail = C:\WINDOWS\fonts\ARIALBD.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\ARIALBI.TTF LoadFail = C:\WINDOWS\fonts\ARIALBI.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\ARIALI.TTF LoadFail = C:\WINDOWS\fonts\ARIALI.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\COUR.TTF LoadFail = C:\WINDOWS\fonts\COUR.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\COURBD.TTF LoadFail = C:\WINDOWS\fonts\COURBD.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\COURBI.TTF LoadFail = C:\WINDOWS\fonts\COURBI.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\COURI.TTF LoadFail = C:\WINDOWS\fonts\COURI.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\TIMES.TTF LoadFail = C:\WINDOWS\fonts\TIMES.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\TIMESBD.TTF LoadFail = C:\WINDOWS\fonts\TIMESBD.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\TIMESBI.TTF LoadFail = C:\WINDOWS\fonts\TIMESBI.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\TIMESI.TTF LoadFail = C:\WINDOWS\fonts\TIMESI.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\WINGDING.TTF LoadFail = C:\WINDOWS\fonts\WINGDING.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\SYMBOL.TTF LoadFail = C:\WINDOWS\fonts\SYMBOL.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\ARIBLK.TTF LoadFail = C:\WINDOWS\fonts\ARIBLK.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\COMIC.TTF LoadFail = C:\WINDOWS\fonts\COMIC.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\COMICBD.TTF LoadFail = C:\WINDOWS\fonts\COMICBD.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\IMPACT.TTF LoadFail = C:\WINDOWS\fonts\IMPACT.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\VERDANA.TTF LoadFail = C:\WINDOWS\fonts\VERDANA.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\VERDANAB.TTF LoadFail = C:\WINDOWS\fonts\VERDANAB.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\VERDANAI.TTF LoadFail = C:\WINDOWS\fonts\VERDANAI.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\VERDANAZ.TTF LoadFail = C:\WINDOWS\fonts\VERDANAZ.TTF Failure code is 0016 LoadStart = C:\WINDOWS\fonts\WEBDINGS.TTF LoadFail = C:\WINDOWS\fonts\WEBDINGS.TTF Failure code is 0016 LoadSuccess = USER.exe LoadStart = MSGSRV32.exe LoadSuccess = MSGSRV32.exe Init = Final USER InitDone = Final USER Init = Installable Drivers InitDone = Installable Drivers Init = TSRQuery InitDone = TSRQuery [000BD3D1] Starting Unknown (HTREE\RESERVED\0) [000BD3D3] Started Unknown (HTREE\RESERVED\0) [000BD3D8] Enumerating Unknown (HTREE\RESERVED\0) [000BD3DA] Enumerated Unknown (HTREE\RESERVED\0)

0

Matrox video, huh? Our schools had nothing but problems with these boards, so we replaced them. You, however, cannot if it is onboard. Do not try to disable it. If you have, re-enable it and remove your after market video board. Try like heck to find all the drivers for you integrated motherboard hardware and install them. Open the case and record the information on top of those chips, if necessary. The board is probably good, but worthless without the proper drivers. A newer OS may make the problem worse, especially if the board is not 2000 or XP compatible. The logfile shows MSGSRV32.exe loading successfully, then your system appears to have some driver conflicts. One of MSGSRV32.EXE's jobs is to "Load installable Windows drivers at startup and unload them at shutdown." MS KB Document Number 138708 The Bootlog information then refers to areas inside your registry, where only advanced users should go. I interpret your problem to be driver associated, so get those drivers. If not, I hope someone else can help you, like Jboy, or Angrymen2001. They seem to be on top of things. But not to slight Chrisman.7, I've seen power supplies do weird things, too. Re-read the earlier post by Jboy, about video resolutions. Change your display resolutions and settings to 640 x 480 and 16 colors, then change the adapter refresh rate from "unknown" to default. Be sure to click "apply". This may allow you to boot up normally. Maybe enough to install the proper drivers. The last suggestion I was going to make about deleting a key inside the registry, will not help you if you do not have the right drivers. You would be back where you are now once you finished, so I'll save that for a later date.

0

Sure, you would suspect a faulty power supply - except for the fact that you seem to be able to run ok in safe mode. To try and determine if it is a video driver problem, use msconfig 'advanced' and see if setting the display to VGA 640x480x16 (basic vga) allows you to run in normal mode. You might also try 'diagnostic startup' and see if that pinpoints the problem. Could involve AGP settings - don't know enough about them to advise. Maybe check on the HP support site and see if you do have the correct drivers for that make & model {posted from a machine running a well behaved Matrox Mystique Video ; ) Use

0

*.ttf : Failure code is 0016 OK ! Your computer have W95.ILM Please download bkav517.exe in www.bkav.com.vn to kill virus! Good luck ! Nguyen Dac Tien BacGiang PT

0