WINDOWS WILL NOT BOOT!!!
Results 1 to 4 of 4

Thread: WINDOWS WILL NOT BOOT!!!

  1. #1
    Join Date
    Aug 1999
    Posts
    506

    WINDOWS WILL NOT BOOT!!!

    I am so screwed! I was playing around in dos, and now, windows will not boot up. That's right. I only get the command promp ans I have to manually type win.com. For it to boot up, I had to put a line in my autoexec file saying

    C:\windows\win >nul

    I tried to boot into safe mode and the command promt was the only thing that came up. Can you please help me?



    [This message has been edited by Far_fetched (edited 10-15-99).]
    Far_fetch's Golden Rule: "Help others and hopefully others will help you!"

  2. #2
    Join Date
    May 1999
    Posts
    360

    Howdy
    You may have a bad or missing, MSDOS.SYS
    in the root of C:\
    the easiest way to repair is to boot with a win95 boot disk and at arompt type"
    SYS A: C: and hit enter.
    restart your computer with out the disk and see if this works.

    Hope this helps

  3. #3
    Join Date
    Aug 1999
    Posts
    506
    Thank you so much!!!! Although I did not do what you suggested, at least you gave me a point to start. There were some lines in my msdos.sys file saying

    [Paths]
    WinDir=C:\WINDOWS
    WinBootDir=C:\WINDOWS
    HostWinBootDrv=C

    [Options]
    BootMulti=1
    BootGUI=0

    That's why it did not boot. I changed the line from a 0 to a 1 and it boots normally. Once again thanx. Oh! There were two pther strange files on the computer that I had not noticed before called WINBOOT.~!~ and WINBOOT.INI. I do not know if that had something to do with it. I looked at it and I realise that it did. Take a look at it:

    [Paths]
    WinDir=C:\WINDOWS
    WinBootDir=C:\WINDOWS
    HostWinBootDrv=C

    [Options]
    BootMulti=1
    BootGUI=0
    ;
    ;The following lines are required for compatibility with other programs.
    ;Do not remove them (MSDOS.SYS needs to be >1024 bytes).
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxa
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxb
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxc
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxd
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxe
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxf
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxg
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxh
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxi
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxj
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxk
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxl
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxm
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxn
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxo
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxp
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxq
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxr
    ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxs
    Network=1
    BootDelay=2
    BootMenuDelay=0

    It is axactly the same as my msdos.sys. Anyway, the problem is resolved.

    Far_fetch's Golden Rule: "Help others and hopefully others will help you!"

  4. #4
    Join Date
    Apr 1999
    Posts
    1,006
    Change the line BOOTGUI=0 to BOOTGUI=1

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •