Re: URGENT! URGENT!

From: Rick (rschland_at_hotmail.com)
Date: 05/21/04

  • Next message: bk: "Blue Screen while booting" 
    Date: Fri, 21 May 2004 14:27:35 -0500

    What I meant was the change log for the MDaemon update. In other words,
    what changes will take place when the update is run. You can get this
    information from the manufacturer.

    "RP" <rp@nospam.com> wrote in message
    news:%235hslh2PEHA.1048@tk2msftngp13.phx.gbl...
    > Change log of MDaemon or Windows? My problem is that I cannot even get
    into
    > the system to get access to any files. The system just will not come up.
    Any
    > idea how to access the log files if windows wont boot?
    >
    > thanks
    >
    > "Rick" <rschland@hotmail.com> wrote in message
    > news:OWEswM2PEHA.1388@TK2MSFTNGP09.phx.gbl...
    > > After hearing that the mail daemon has been updated, I would look at the
    > > change log for this update and see what it does. This should indicate
    > what
    > > modifications are performed on the system.
    > >
    > > "RP" <rp@nospam.com> wrote in message
    > > news:OsCp3I2PEHA.1348@TK2MSFTNGP12.phx.gbl...
    > > > No. All I did was an update to our mail software Mdaemon. Absolutely
    no
    > > luck
    > > > at all. Been at it since this a.m. It looks like a clean install is
    the
    > > only
    > > > way out. I cannot even get to the data on the drives to move them over
    > to
    > > > another server. I am trying to do a fresh install on a different
    > partition
    > > > now. Lets see.
    > > >
    > > > thanks,
    > > > Param
    > > >
    > > > "Rick" <rschland@hotmail.com> wrote in message
    > > > news:OeLEbA2PEHA.3732@TK2MSFTNGP11.phx.gbl...
    > > > > Have you added any hardware or modified the OS?
    > > > >
    > > > >
    > > > > "Shane Daniels" <sdaniels101@yahooo.com> wrote in message
    > > > > news:eFqDd60PEHA.3660@TK2MSFTNGP11.phx.gbl...
    > > > > > Don't suppose your using a different monitor on it? Bit of a long
    > shot
    > > > > > but I had this prob and turns out the server graphics card
    > resolution
    > > > > > was set too high for the monitor.
    > > > > >
    > > > > > Shane.
    > > > > >
    > > > > > RP wrote:
    > > > > >
    > > > > > > Hi all, I have a production server running Windows 2003 Server
    > > > standard
    > > > > that
    > > > > > > just will not boot!! The system POSTS and then it shows the
    > Windows
    > > > 2003
    > > > > > > Server Splash Screen and then all I get is a BLANK SCREEN and
    > > nothing.
    > > > I
    > > > > > > cannot even get into Safe Mode by hitting the F8 key. Any ideas?
    > > > Please
    > > > > help
    > > > > > > our email and everything is down.
    > > > > > >
    > > > > > > Although I can ping the ip of the server and get a reply from
    > > another
    > > > > > > machine on the network. any ideas? Server is a Compaq 1850R. I
    ran
    > > the
    > > > > > > Compaq System diags and everything seems to be OK. This server
    was
    > > > > working
    > > > > > > fine for several months!!
    > > > > > >
    > > > > > > much thanks in advance,
    > > > > > > Param
    > > > > > >
    > > > > > >
    > > > >
    > > > >
    > > >
    > > >
    > >
    > >
    >
    >

  • Next message: bk: "Blue Screen while booting"

    Relevant Pages

    • Re: URGENT! URGENT!
      ... > What I meant was the change log for the MDaemon update. ... >> Change log of MDaemon or Windows? ... >> idea how to access the log files if windows wont boot? ...
      (microsoft.public.windows.server.general)
    • Re: URGENT! URGENT!
      ... Change log of MDaemon or Windows? ... All I did was an update to our mail software Mdaemon. ...
      (microsoft.public.windows.server.general)
    • RE: How to change log location
      ... If you're running Exchange 5.5, you can use the Optmizer utility to modify ... How to change log location ... Microsoft CDO for Windows 2000 ... >the log files? ...
      (microsoft.public.exchange.setup)
    • Re: Res: Res: RE: Problems changing from 1.30 to 1.42
      ... > I used trace() but still cannot figure out what is happening, but still dont ... > I'm sending attached the log files and the program. ... This aspect of the change log for 2.9002 applies: ...
      (perl.dbi.users)