Welcome to Tech Support Forum home to more then 136,000 problems solved. Issues have included: Spyware, Malware, Virus Issues, Windows, Microsoft, Linux, Networking, Security, Hardware, and Gaming Getting your problem solved is as easy as:
1. Registering for a free account
2. Asking your question
3. Receiving an answer

Registered members:
* Get free support
* Communicate privately with other members (PM).
* Removal of this message
* See fewer ads.
* And much more..

 



Want to know how to post a question? click here Having problems with spyware and pop-ups? First Steps
Go Back   Tech Support Forum > Microsoft Support > Win 98 & ME Support
User Name
Password
Site Map Register Donate Rules Blogs Mark Forums Read


Win 98 & ME Support Find support for Windows 98 / ME here

Reply
 
LinkBack Thread Tools
Old 11-15-2005, 06:57 PM   #1 (permalink)
Member
 
glomedia's Avatar
 
Join Date: Jan 2003
Posts: 30
OS: Win 98


Exclamation OS won't load. Get this message, then shutdown

Can someone help me solve this (with Windows 98)?

When I start up, I get the following error message and then the computer shuts down on its own. (At the end, I'll describe the two things I was doing beforehand when this first occurred.) I cannot start up in Safe mode. I can get the command prompt (C:>), but I don't know what DOS command to enter in order to solve the problem.

Cannot find a device file that may be needed to run Windows or a Windows application.

The Windows registry or SYSTEM.INI file refers to this device file, but the device file no longer exists.

If you deleted this file on purpose, try uninstalling the associated application using its uninstall or setup program.

If you still want to use the application associated with this device file, try reinstalling that application to replace the missing file.

Press a key to continue


I do, but same message repeats. 30 seconds later, this new message appears:

Either memory is insufficient to run KRNL386.EXE or the value of the Windowmemsize entry in the SYSTEM.INI file is too large. You need to run the Setup program again.

Press any key to continue...
-- then computer shuts down on its own after a minute.

WHAT I HAD BEEN DOING IMMEDIATELY BEFORE:
  1. I accidentally double-clicked the installer for a program called "CallCenter." Since I already installed it a while ago (and have had no trouble with it, nor did I install any new devices with it), I canceled the install. But a dialogue appeared stating that some temporary files wouldn't be deleted. Is this the problem? Is there a DOS command I can enter to clean out my TEMP FILES directory?
  2. I updated to a newer version of my anti-virus program (which I've done before with no problem), and it prompted me to restart once the updated files were installed. During restart, I first got the above error messages.
P.S. One of the startup mode choices is "Logged," which creates a BOOTLOG.TXT file (which I assume may shed light on the problem). But how do I read this file?
glomedia is offline  
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Reddit!
Reply With Quote
Important Information
Join the #1 Tech Support Forum Today - It's Totally Free!

TechSupportForum.com is a leading support website for your computer needs. We offer free, friendly and personalized computer support. Why pay to have your computer fixed when you can do it for free.

Join TechSupportforum.com Today - Click Here

Old 11-15-2005, 10:09 PM   #2 (permalink)
Asst. Manager, Alternative Computing Forums
 
batty_professor's Avatar
 
Join Date: Jul 2004
Location: Hooterville Il 45 mi. east of St. Louis mo
Posts: 2,608
OS: Fedora Core 5 for now


Send a message via AIM to batty_professor Send a message via MSN to batty_professor Send a message via Yahoo to batty_professor
If you would like to read the bootlog file you created, type the following command at a C:\ prompt
type C:bootlog.txt type is a command here that displays the text file on the screen. If the file is too long, try the pipe | command as follows type C:bootlog.txt|more to get the file one screenfull at a time. The pipe usually shares the key with \ and looks like a colon done a vertical skid.

A handy utility you might try is the scanreg /restore utility. This will cause a scan of the windows registry, and should prompt you for input to try restore from an older copy of the registry. This may get windows back in operation, where you have more repair utilities at your disposal.
__________________
It's better to know me and not need me than to need me and not know me. B.

While users are never under any obligation, if you feel the urge please feel free to visit our donation page. Every little bit helps.
And we thank you for your support.

Microsoft free Registered Linux user 397458
batty_professor is offline  
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Reddit!
Reply With Quote
Old 11-15-2005, 11:24 PM   #3 (permalink)
Tech Hardware Team
 
Stu_computer's Avatar
 
Join Date: Jul 2005
Posts: 1,460
OS: Windows


Clean out files in the temp directory, then temporarily rename system.ini and see if windows starts up...

C:>DEL C:\windows\temp\*.* /s {note: there's a space between * and /s}
C:>cd\windows
C:>REN system.ini system.txt
C:>WIN

If windows still has that error then check the registry for errors...
C:>cd\windows\command
C:>scanreg

if error not fixed then you can restore to a previous good copy of the registry...
C:>scanreg /restore

How to Manually Restore the Windows 98/Me Registry
http://support.microsoft.com/kb/q221512/

Then post back with a progress report.
__________________
Stu_computer is offline  
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Reddit!
Reply With Quote
Old 11-16-2005, 06:32 PM   #4 (permalink)
Member
 
glomedia's Avatar
 
Join Date: Jan 2003
Posts: 30
OS: Win 98


Cry

Thank you for your replies, professor batty and stu. Unfortunately, the problem is exactly the same

Quote:
Originally Posted by Stu_computer
C:>DEL C:\windows\temp\*.* /s {note: there's a space between * and /s}
C:>cd\windows
C:>REN system.ini system.txt
C:>WIN
  1. cleaned out files in the TEMP directory - it told me the " /s" was an invalid switch, though (and I did insert the space), so I had to omit it (and it worked)
  2. renamed system.ini to system.txt (in the windows directory) - worked
  3. at the C:>, typed win - got the following error message:
    cannot find SYSTEM.INI
    You need to run Windows Setup again to install the file.
    Press any key to continue...
    --> then it shuts down

    When I power on the computer again, I get the same message.
Quote:
If windows still has that error then check the registry for errors...
C:>cd\windows\command
C:>scanreg
  1. no registry errors were found.
    Note 1: I had to type scanreg at the C:> because when I typed cd\windows\command, I received the message Invalid Directory.
    Note 2: I realized that if I renamed system.txt back to system.ini, then the command cd\windows\command was accepted. Again I typed scanreg at the C:\WINDOWS\COMMAND> prompt. Again, no registry errors were found.
Quote:
if error not fixed then you can restore to a previous good copy of the registry...
C:>scanreg /restore
Did this. Restarted computer. Getting exactly the same error messages as in my original post.

ADDITIONAL NEW INFORMATION

Item 1 (of 2): Someone gave me this link:
http://support.earthlink.net/mu/1/ps.../2172.psc.html

It describes my error message exactly. The problem is I can't get into Windows 98 in order to follow their instructions. I have a CD given to me by the vendor of the laptop, but it will only INSTALL Windows 98 onto my HD (overwriting everything currently on there). It won't boot up into Windows 98.

Item 2 (of 2): These are some of the more suspicious looking things my latest bootlog.txt file shows:

[001230F6] Loading Device = C:\AECU.SYS
[001230FE] LoadFailed = C:\AECU.SYS
(Logo disabled)

... next are a bunch of lines that say "Loading Device" followed by "LoadSuccess"...

[001231A5] 386 processor.
$You should not load Windows into high memory.

Do not use "load high" commands to start Windows.
$Windows is already running.
$Cannot run Windows while the currently installed protected-mode software is running.
Quit the protected-mode [00123209] Loading Vxd = vnetsup.vxd*
(see footnote at end for what came before and after this error msg)

Note: I don't see any line [00123209]. The following lines occur a few screens later:

[00123245] Starting Unknown (HTREE\ROOT\0)
[00123245] Started Unknown (HTREE\ROOT\0)
[00123245] Enumerating Unknown (HTREE\ROOT\0)
[00123245] Enumerated Unknown (HTREE\ROOT\0)
[00123245] Starting Unknown (HTREE\RESERVED\0)
[00123245] Started Unknown (HTREE\RESERVED\0)
[00123245] Enumerating Unknown (HTREE\RESERVED\0)
[00123245] Enumerated Unknown (HTREE\RESERVED\0)


I hope some experts out there can help. I'm at a loss. Thanks so much.

*Footnote: bootlog.txt file - What came before and after "Quit Protected Mode" message:
These occur before the line [001231A5] 386 processor:
[001231A4] Loading Vxd = VMM
[001231A4] LoadSuccess = VMM
[001231A4] Loading Vxd = C:\WINDOWS\SMARTDRV.EXE
[001231A5] LoadSuccess = C:\WINDOWS\SMARTDRV.EXE
[001231A5] Loading Vxd =

These occur after the line [001231A5] 386 processor:
[0012320A] LoadSuccess = vnetsup.vxd

Then there are a bunch of lines from [0012320A] to [0012320F] that say "Loading Vxd" followed by "LoadSuccess." The numbering resumes at [00123211]:

[0012320F] Loading Vxd = C:\WINDOWS\system\VMM32\IFSMGR.VXD
[00123211] LoadSuccess = C:\WINDOWS\system\VMM32\IFSMGR.VXD

The next 3 screenfuls of lines -- [00123211] to [00123237] -- say "Loading Vxd" followed by "LoadSuccess." The remaining lines have to do with SYSCRITINIT and DEVICEINIT, and other things (no errors).
glomedia is offline  
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Reddit!
Reply With Quote
Old 11-16-2005, 09:06 PM   #5 (permalink)
Tech Hardware Team
 
Stu_computer's Avatar
 
Join Date: Jul 2005
Posts: 1,460
OS: Windows


Go to C prompt and do each of these 4 lines, then reboot and select option 2 Logged (\bootlog.txt)

cd\
attrib -h -r bootlog.*
ren bootlog.txt bootlog.dud
ren bootlog.prv bootlog.txt


if still doesn't boot to windows then go back to C prompt and copy these two files to a floppy disk.

cd\
cd windows
attrib -h -r system.ini
attrib -h -r system.cb

copy system.ini a:\sysini.txt
copy system.cb a:\syscb.txt


When you post your next report you can attach them as txt files (use Manage Attachments button below message box) and I will review their content.
__________________
Stu_computer is offline  
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Reddit!
Reply With Quote
Old 11-17-2005, 11:08 AM   #6 (permalink)
Member
 
glomedia's Avatar
 
Join Date: Jan 2003
Posts: 30
OS: Win 98


Quote:
Originally Posted by Stu_computer
Go to C prompt and do each of these 4 lines, then reboot and select option 2 Logged (\bootlog.txt)

cd\
attrib -h -r bootlog.*
ren bootlog.txt bootlog.dud
ren bootlog.prv bootlog.txt
Thank you so much for replying again, Stu. Before I follow the above instructions, can you tell me a couple of things:
  1. What does attrib -h -r bootlog.* do? Does it change the registry or my system, and how can I change it back to what it was if it still fails to boot my computer? Should I undo this command even if it does reboot my system?
  2. When I power on my laptop, I press F8, which gives me boot up options. One of the options is to start up in "logged" mode, which generates a bootlog.txt file. If I just boot up in "logged" mode again, wouldn't that just overwrite the previous bootlog.txt file and create a new one? I don't understand why I need the two "ren" commands (but then again, I'm not as knowledgable as you ).
  3. Can I just put the above commands on hold, and start directly with your next instructions (below)?
Quote:
if still doesn't boot to windows then go back to C prompt and copy these two files to a floppy disk.

cd\
cd windows
attrib -h -r system.ini
attrib -h -r system.cb

copy system.ini a:\sysini.txt
copy system.cb a:\syscb.txt


When you post your next report you can attach them as txt files (use Manage Attachments button below message box) and I will review their content.
  1. Again, what do attrib -h -r system.ini and attrib -h -r system.cb do? Can I undo these commands or am I supposed to undo these commands once I've followed the instructions?

Thank you again, Stu, for your help. I'm sorry for all the questions; but, as you can see, I'm not well-versed in these commands (and the registry is a scary thing to me ), so I just want to have a better idea of what I'm doing before I proceed.
glomedia is offline  
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Reddit!
Reply With Quote
Old 11-17-2005, 11:58 AM   #7 (permalink)
Registered User
 
Join Date: Mar 2005
Posts: 45
OS: xp professional


Explanation of Attrib

Here is a link on what the command does.

http://www.computerhope.com/attribhl.htm

Those files are normally hidden, because they are system files, so that you dont accidently erase them. The commands that he is having you do, will make the file visible to you, so that you can copy them and post them here.
Mustang00 is offline  
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Reddit!
Reply With Quote
Old 11-17-2005, 12:02 PM   #8 (permalink)
Tech Hardware Team
 
Stu_computer's Avatar
 
Join Date: Jul 2005
Posts: 1,460
OS: Windows


Files have attributes that can be set to make the file hidden or read only (which means it cannot be written to, or replaced with a copy). Typically, system files are hidden in windows, to make them accessible you need to change their attibutes.

The attrib command is DOS's version for viewing/changing file attributes.

"attrib -h -r bootlog.*" means find file named bootlog (all extensions) and remove their hidden and read only status. You would use plus signs to make it hidden and read only.

ren bootlog.txt bootlog.dud
This renames (ren) the file, so you still have it.

ren bootlog.prv bootlog.txt
This renames the previous saved bootlog (prv) that worked, so that safe mode can use it instead.
Or you could also do "copy bootlog.prv bootlog.txt" to keep the original and just make a copy.

The "Step by step confirmation" has an option to make a new bootlog while starting windows..
The "Logged (\bootlog.txt)" uses the bootlog to start windows.

What we're doing is taking the previous bootlog, made before the problem occurred, and trying to start windows with it.

.
__________________
Stu_computer is offline  
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Reddit!
Reply With Quote
Old 11-18-2005, 10:33 AM   #9 (permalink)
Member
 
glomedia's Avatar
 
Join Date: Jan 2003
Posts: 30
OS: Win 98


Question

Quote:
Originally Posted by Stu_computer
Go to C prompt and do each of these 4 lines, then reboot and select option 2 Logged (\bootlog.txt)

cd\
attrib -h -r bootlog.*
ren bootlog.txt bootlog.dud
ren bootlog.prv bootlog.txt
I did the above exactly, but it still didn't boot up into Windows 98 and I get the same error message. Before I even posted about this problem, I was trying every which mode (by pressing F8) to boot up: I even tried the option "Step by step confirmation" -- which I now gather made a new bootlog (and thus overwrote my last good working bootlog? Maybe this is why the commands above didn't solve my problem?)

BUT the good news is I searched Microsoft Support and found an even better link relating to my problem. It appears that it's fixable (touch wood) with a registry edit. (A second search indicated that it could solve my memory error message as well.) Link: http://support.microsoft.com/default...b;en-us;132008.

It states what to do in Step 4, so I'd like to try this before doing anything else. But I first have 3 things to ask that I'm unsure about:
  1. It says to first make a backup of my current registry.

    In the instructions at http://support.microsoft.com/kb/256419/EN-US/, it says to click Start --> Run and then to type scanregw. But since I don't have the Start menu (since I can't load Windows), is there a different command I'm supposed to use at the C:>, or is it still scanregw? Or am I supposed to type cd\windows\command first? (And what is the purpose of cd\windows\command? Why can't I just type whatever command I need at the C:>?)

  2. Also regarding this backup of the registry, the instructions linked above say this:
    "When you back up the registry, the Rb0x.cab file is created in the Windows\Sysbckup folder (where x is a number from 0 to 5). Each time you back up the registry, the oldest Rb0x.cab file is overwritten."
    Here's where I'm a little confused: 11/15/05 is my last good registry. I restored from that one when I first got this problem and the registry checker (scanreg) told me there were no problems with it. Right now, when I turn on my laptop, press F8, choose "Command prompt only," and then type scanreg/restore at the C:>, it shows the following:

    11/16/05 Not Started 06:42:36pm rb003.cab
    11/16/05 Not Started 06:36:57pm rb002.cab
    11/16/05 Not Started 06:O6:56pm rb001.cab
    11/15/05 Started rb000.cab
    11/12/05 Started rb005.cab
    According to the above, this registry backup is going to overwrite the oldest registry -- 11/12/05, which was a good registry. Is there a way to make it overwrite one of the 11/16/05 registries instead? Or to make it overwrite none of those registries, but instead add it to the existing backups (as rb006.cab?). I ask this in case I need to restore the registry if something goes wrong. The restore instructions say to only restore from a registry that says "Started" beside it, so that's why I'm afraid to overwrite the 11/12/05 or 11/15/05 registries.

    BTW, why isn't there an rb004.cab?

  3. After making a backup of the registry, it says I can edit the registry.

    BUT the instructions at http://support.microsoft.com/kb/322754/ only show how to do it through the Windows interface (click Start --> Run and type regedit). Since I can't get into Windows, what is the command to edit the registry at the C:>? (And do I need to type cd\windows\command first before I use it?)
Thank you so much for your help Stu, and for your last reply in which you explained the various DOS commands in your post. I won't give up hope! I just know there's a way to get my laptop booted up again. This happened so suddenly after everything was working well, so I'm sure that the culprit is my canceling the install (or re-install, rather) of that "CallCenter" communications program. There must be blank or space values in that Vxd registry key, as the Microsoft article suggests.

P.S. - Just to Recap:
  1. the bootlog.txt file showed this message: "Quit the protected-mode [line numb] Loading Vxd = vnetsup.vxd"
  2. I previously missed this "LoadFailed" message in bootlog.txt file:
    [line numb] Loading Vxd = ndis2sup.vxd
    [line numb] LoadFailed = ndis2sup.vxd


    I read this on another site: "It's normal for the Win98 NDIS-2 to NDIS-3 Mapper Virtual Device Driver to not load if you don't need "real-mode network support." If you agree with this and that the "LoadFailed" message is normal for this device, then I won't worry about it.
Another P.S. - Silly Question, but I don't know the answer :
When my laptop is at the C:>, is it OK to just turn it off, or do I need to enter a command first in order to safely shut it down? I've been pressing CTRL - ALT - DEL to restart it again so it will go through the error messages I've been getting and shut down by itself. Is this the wrong thing to do?
glomedia is offline  
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Reddit!
Reply With Quote
Old 11-18-2005, 02:16 PM   #10 (permalink)
Tech Hardware Team
 
Stu_computer's Avatar
 
Join Date: Jul 2005
Posts: 1,460
OS: Windows


Quote:
BUT the good news is I searched Microsoft Support and found an even better link relating to my problem. It appears that it's fixable (touch wood) with a registry edit. (A second search indicated that it could solve my memory error message as well.) Link: http://support.microsoft.com/defaul...kb;en-us;132008.

It states what to do in Step 4, so I'd like to try this before doing anything else.
The article only applies if you can still get into windows.

This is why I asked you to attach the system.ini as a text file, so I can review it and remark out any problem lines. You have already set it to use a previous good copy of the registry files, so don't mess with this part now.

Quote:
When my laptop is at the C:>, is it OK to just turn it off, or do I need to enter a command first in order to safely shut it down? I've been pressing CTRL - ALT - DEL to restart it again so it will go through the error messages I've been getting and shut down by itself. Is this the wrong thing to do?
When you start up with DOS you can turn power off at the C prompt anytime.

When you start up with Windows to a desktop and use a DOS Prompt box or have it "Restart in DOS Mode" then you have to type "EXIT" to quit and return to windows mode, then quit windows.
__________________
Stu_computer is offline  
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Reddit!
Reply With Quote
Old 12-18-2005, 04:26 AM   #11 (permalink)
Registered User
 
Join Date: Dec 2005
Posts: 1
OS: win98


I have the same problem

This is a very strange problem. I installed a pnp usb card reader before my problem started. I would really like to know what the solution is. A number of threads on a number of forums have addressed this but nobody has posted the answer.

I CAN start properly in safe mode. However, in device manager, there were numerous duplications of devices. My monitor adapter is pooched in normal mode, and so is my lmouse.vxd missing, and the acpi bios is duplicated, reporting 2 of them. My last regedit restore is March, and I'd like to avoid using it unless I have to.

I have no difficulty following instructions, and understand dos pretty well.

Regards,

Outspoken
outspoken is offline  
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Reddit!
Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off




All times are GMT -7. The time now is 03:29 AM.



Copyright 2001 - 2009, Tech Support Forum
Home Tips Plus | Outdoor Basecamp | Automotive Support Forum

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85