Re: Server keeps restarting



good work and made my day a little easier once again!

"Charlie Russel - MVP" wrote:

:)

--
Charlie.
http://msmvps.com/xperts64


"Anna Clark" <anna(remove this)@verizon.net> wrote in message
news:OhWEcz5$GHA.4808@xxxxxxxxxxxxxxxxxxxxxxx
Thanks Charlie. Good catch.

Two heads are better than one, and I left my second one back home when I
left town for a few days.

:-)

Anna Clark


"Charlie Russel - MVP" <charlie@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B331DBE1-12F4-463A-BDED-BD91B9436A9B@xxxxxxxxxxxxxxxx
No, you can't. The problem is that the boot process can't even SEE the
hard disk, since it has no drivers for it.

What you _can_ do is use your original install media, press F6 when it
first boots up (you'll see the prompt at the bottom), and load the
drivers from a floppy. Then, with the drivers loaded, you can open a
recovery console and copy them back to where they need to be.

--
Charlie.
http://msmvps.com/xperts64


"rhesus" <rhesus@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:98FC3B40-174A-49EB-B379-FB2D79AB1FEF@xxxxxxxxxxxxxxxx
i guess I can also use the recovery console to copy the driver back to
the
original folder (drivers folder). Wouldn't this be much easier?

"Anna Clark" wrote:

Hi rhesus:

I would only be guessing here, but do you think that moving the disk
controller driver out of the path that Windows searches on start may
have
something to do with this?

Seems to me you can either do a parallel install of Windows and put the
raid
driver back, or you can put that drive in another NT class machine to
access
the folders. Since we know that it is (probably) part of a RAID set,
moving
it is most likely not an option, so you could also put in any drive,
tell
the bios to boot on that, install a dummy copy of Windows and the raid
driver, then you should be able to access the drives and put the driver
back.

Regards:

Anna Clark


"rhesus" <rhesus@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0621F0A3-865A-4BF3-91DB-EEE0E35A7411@xxxxxxxxxxxxxxxx
I was looking into some troubleshooting of failure to shutdown.

I used sigver to remove four unsigned drivers (put them in a new
folder
inside \drivers.) One was the a320raid.sys driver, the other 3 I
didn't
write
down.

When the system was rebooting I enabled boot logging.

The welcome screen comes on, scrolls through exactly 2.5 scrolls of
the
scroll bar then reboots.

I enabled a stop error report. It was 0x73. I couldn't find anything
relevant on this.

I've tried last known. No joy.







.



Relevant Pages

  • Re: Would someone like to remind me
    ... > It can be helpful to set up a _Drivers folder on your D: ... > 28_Turn off indexing on all drives ... I know Boo also has a nice efficient System of Folders & files like ...
    (uk.people.silversurfers)
  • Re: PC Gaming vs Aging eyes & reflexes
    ... C:\Windows has a Dell folder and in there are drivers. ... first thing you install before any other drivers. ... Stupid Dell. ...
    (comp.sys.ibm.pc.games.rpg)
  • Re: STOP on shut-down, optical drives or drivers?
    ... The system drivers should be inside the ... the only thing I have been able to do is unplug both of the Sony ... drives and the problem goes away. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: OSD and format for ExtraNICs folder
    ... I have included a listing of the contents of the ExtraNICs ... > drivers that both include the same file). ... If the failure occurs before the ... >> 1) I am having trouble with the Extranics folder. ...
    (microsoft.public.sms.tools)
  • Re: Toshiba S100 Problem With RAID Driver
    ... Add RAID drivers and Service Pack 2 to your original Windows CD! ... Windows XP setup CD ... Our next objective is to extract Service Pack 2 to a folder so we can ...
    (comp.sys.laptops)