Reboot failure

Hi all,

If I select shutdown | reboot, ME shuts down and comes back to a black
screen with the cursor blinking in the upper left corner.

If I shut down fully and then restart, it starts up Ok.

Any ideas?

"DonC" wrote:
Hi all,

If I select shutdown | reboot, ME shuts down and comes back to a black
screen with the cursor blinking in the upper left corner.

If I shut down fully and then restart, it starts up Ok.

Any ideas?

http://snipurl.com/ars7

Silj

--
siljaline

MS - MVP Windows (IE/OE) 2003/04 AH-VSOP
________________________________________
Security Tools Updates
http://forum.aumha.org/viewforum.php?f=31

(Reply to group, as return address
is invalid - that we may all benefit)

Don,

Shutdown all programs and close as many running tasks as possible before
restarting the PC.

If that solves the problem, selectively shutdown programs and tasks before
restarting PC until it happens again.

Hopefully you found the culprit.

Zee





"DonC" wrote in message
...
Hi all,

If I select shutdown | reboot, ME shuts down and comes back to a black
screen with the cursor blinking in the upper left corner.

If I shut down fully and then restart, it starts up Ok.

Any ideas?

Thanks for the response. However, I have a second ME machine which works
perfectly and doesn't have the file VWIM32.VXD anywhere on the system -- if
that's the solution you're pointing out : (


"siljaline" wrote in message
...
"DonC" wrote:
Hi all,

If I select shutdown | reboot, ME shuts down and comes back to a black
screen with the cursor blinking in the upper left corner.

If I shut down fully and then restart, it starts up Ok.

Any ideas?

http://snipurl.com/ars7

Silj

--
siljaline

MS - MVP Windows (IE/OE) 2003/04 AH-VSOP
________________________________________
Security Tools Updates
http://forum.aumha.org/viewforum.php?f=31

(Reply to group, as return address
is invalid - that we may all benefit)

DonC wrote:

Thanks for the response. However, I have a second ME machine which
works perfectly and doesn't have the file VWIM32.VXD anywhere on the
system -- if that's the solution you're pointing out : (

Look again. Without the file vmm32.vxd your system will not boot and you
will see one of a number of error messages rather than a black screen.
--
Mike Maltby MS-MVP

My bad. I read this:

"The original post was submitted twice by Osama Shaban with the subjects
Black Screen!!! and Start-up Problem!!! and I replied to the latter. I
had the same problenm a few weeks ago and found that VWIN32.VXD had gone
missing"

and assumed VWIN32,VXD was the file you were referring to.

So which exact thread am I suposed to be looking at. All I got was a google
search on "Black Screen" with dozens of posts to sort through.

Help!

Dave
"Mike M" wrote in message
...
DonC wrote:

Thanks for the response. However, I have a second ME machine which
works perfectly and doesn't have the file VWIM32.VXD anywhere on the
system -- if that's the solution you're pointing out : (

Look again. Without the file vmm32.vxd your system will not boot and you
will see one of a number of error messages rather than a black screen.
--
Mike Maltby MS-MVP

DonC wrote:

My bad. I read this:

"The original post was submitted twice by Osama Shaban with the
subjects Black Screen!!! and Start-up Problem!!! and I replied to the
latter. I
had the same problenm a few weeks ago and found that VWIN32.VXD had
gone missing"

and assumed VWIN32,VXD was the file you were referring to.

So which exact thread am I suposed to be looking at. All I got was a
google search on "Black Screen" with dozens of posts to sort through.

My bad also. When you typed VWIM32.VXD I thought you were referring to
VMM32.VXD when in fact you were referring to VWIN32.VXD. VWIN32.VXD is
usually built in to and part of VMM32.VXD which is a composite file built
from a 30 or more virtual device drivers when the system was first
installed and the contents of which is specific to the machine for which
it was built. Therefore unless vwin32.vxd has been updated (no update for
this file has ever been released by Microsoft for Win Me) you won't ever
see a copy of this file.

As to helping you solve your problem it would help if one had some idea as
to what changes were made to your system in the session prior to shutting
down. In the absence of any other information it might be worth restoring
the registry to the state it was in when you last successfully used the PC
as follows:

Boot to a DOS prompt using a boot floppy and at the A:\ prompt enter
SCANREG /RESTORE
and from the five copies of the registry you are offered choose the one
that immediately precedes the beginning of your problems. When the
command is complete remove the floppy and reboot. Hopefully this will
enable you to boot your PC after which you can either look for what might
have caused the problem or use system restore and roll back the system to
the last good checkpoint before the problem. I suggest using both scanreg
/restore and then system restore as using scanreg /restore could cause the
registry and the system files to be out of synch.

Best of luck,
--
Mike Maltby MS-MVP

"Mike M" wrote in message
...
SNIP

As to helping you solve your problem it would help if one had some idea as
to what changes were made to your system in the session prior to shutting
down. In the absence of any other information it might be worth restoring
the registry to the state it was in when you last successfully used the PC
as follows:

Boot to a DOS prompt using a boot floppy and at the A:\ prompt enter
SCANREG /RESTORE
and from the five copies of the registry you are offered choose the one
that immediately precedes the beginning of your problems. When the
command is complete remove the floppy and reboot. Hopefully this will
enable you to boot your PC after which you can either look for what might
have caused the problem or use system restore and roll back the system to
the last good checkpoint before the problem. I suggest using both scanreg
/restore and then system restore as using scanreg /restore could cause the
registry and the system files to be out of synch.

Best of luck,
--
Mike Maltby MS-MVP



Hi Mike,

I'm actually working on my daughter's machine 170 miles north of hear. I
did a clean install of Windows ME, installed McAfee 2004 and installed all
the MS critical updates and her applications before I delivered it to her
last week.

I also have an ME machine here for my grandsons' use -- i.e., to keep them
from destroying our two XP macines: )

All she had left to do was install her printer drivers. Somehow, in spite
of all this, she (or hubby) managed to get hit with the W32/Opaserv.worm.
She also had it a year or so ago so she is knowledgable re getting rid of it
and thinks she's wiped it out.

Anyhow, I got suspicious of the win.ini file and asked her to take a look at
the "run=" line. Sure enough it contained two items identified as
associated with the worm -- natal.scr and speedy.bat. I emailed her to
delete these entries and search for the two files.

I'm waiting for a response to see if this is her problem.

Thanks,

Don