1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Editing Autoexec.bat

Discussion in 'Legacy Windows' started by BillyNeal, 2005/05/29.

Thread Status:
Not open for further replies.
  1. 2005/05/29
    BillyNeal

    BillyNeal Inactive Thread Starter

    Joined:
    2003/10/04
    Messages:
    35
    Likes Received:
    0
    I've used Notepad to open and edit the autoexec.bat file as there seems to be extra material there that isn't needed. I did read another thread regarding the lines entered by Zone Alarm which answered one of my questions. Using Notepad I have eleminated some lines in the autoexec.bat file, however when I boot up I see a much larger autoexec.bat file during the boot up process. It's like my changes didn't have any effect although I saved the changes before exiting Notepad. Does anyone know why my changes didn't take effect?
     
  2. 2005/05/29
    goddez1

    goddez1 Inactive

    Joined:
    2002/01/12
    Messages:
    2,975
    Likes Received:
    49
    You're going to need to be specific. Not enough details in your post to answer your question. Any answer given, based on your information, would be a generic quesstimate. Want one?: (most likely syntax errors /translation=you goofed, and used or made common improper editing boos-boos).

    Want a second opinion?: Copy and Paste your autoexec.bat text in here and we'll have a look.

    In addition are you using msconfig to modify or control your bootup in any way?
     
    Last edited: 2005/05/29

  3. to hide this advert.

  4. 2005/05/29
    BillyNeal

    BillyNeal Inactive Thread Starter

    Joined:
    2003/10/04
    Messages:
    35
    Likes Received:
    0
    Thanks, Goddez1. I'll get back with what I can. Have to get on the other machine where I'm having the problem.
     
  5. 2005/05/29
    BillyNeal

    BillyNeal Inactive Thread Starter

    Joined:
    2003/10/04
    Messages:
    35
    Likes Received:
    0
    Goddez1 I'm back. Here is current autoexec.bat:
    "C:\>
    PATH C:\PAGEMGR\IMGFOLIO;C:\PAGEMGR;
    C:\>

    SET Path=%Path%; "C:\Program Files\DiskeeperLite\ "
    Set tvdumpflags=10 "

    I checked the config.sys file with Notepad and it was blank when searching "all files" file extensions.

    The DOS screen that opens during bootup contains a lot more than is shown above in the autoexec.bat file. I don't know how to capture that screen during bootup to show you.
     
  6. 2005/05/29
    BillyNeal

    BillyNeal Inactive Thread Starter

    Joined:
    2003/10/04
    Messages:
    35
    Likes Received:
    0
    BTW the initial and final quotation marks are mine just in the BBS msg.

    BN
     
  7. 2005/05/29
    NetDoc

    NetDoc Inactive

    Joined:
    2005/01/09
    Messages:
    215
    Likes Received:
    0
    Are you that you are not seeing Win98 loading? It will show some of this on the DOS screen. Exactly what are you seeing? There is nothing being loaded in the Autoexec.bat file you posted.

    DRD
     
  8. 2005/05/29
    BillyNeal

    BillyNeal Inactive Thread Starter

    Joined:
    2003/10/04
    Messages:
    35
    Likes Received:
    0
    It may be Win 98 loading, but it's a black and white DOS screen with what looks like an overstuffed autoexec.bat file. If there's no way to freeze the screen, I'll just have to memorize what I can in the time allowed. I just tried Print Screen and it caused the screen to disappear, but the bootup process continued.
     
  9. 2005/05/29
    BillyNeal

    BillyNeal Inactive Thread Starter

    Joined:
    2003/10/04
    Messages:
    35
    Likes Received:
    0
    I hit the PAUSE button and was able to copy down the following:
    C:\> C:\>
    C:\> PATH C:\PAGEMGR\IMGFOLIO; C:\PAGEMGR;
    C:\ C:\
    C:\>
    C:\SET PATH=C:\WINDOWS; C:\WINDOWS\COMMAND; C:\PAGEMGR\ IMAGEFOLIO; C:\PAGEMGR;; "C:\PROGRAM FILES\DiskeeperLite\ "
    C:\>SET tvdumpflags=10
    C:\>

    Is all this necessary and, if so, where is it coming from?

    Many thanks.
     
  10. 2005/05/29
    goddez1

    goddez1 Inactive

    Joined:
    2002/01/12
    Messages:
    2,975
    Likes Received:
    49
    From the startmenu button>run line type sysedit
    Click on the autoexec.bat tab to bring it forward
    Hightlight all of it and copy it.
    Close/exit out sysedit and
    Paste the text here, in your post.
     
  11. 2005/05/29
    jaylach

    jaylach Inactive

    Joined:
    2005/04/05
    Messages:
    412
    Likes Received:
    0
    If I remember this correctly the C:\> entries ary causing the display of C:\> C:\> displays. You are telling the autoexec.bat file to print C:\> to the screen.

    Ahhhhh, I wanna go back and look at what is being displayed again so I'm posting this and gonna come back and edit if anyone sees this before I'm done this isn't complete at this point...

    Adding what you sent as a display as a quote ...

    I believe that the empty lines are causing your C:\> displays

    is caused by the SET Path=%Path%; "C:\Program Files\DiskeeperLite\ "

    I can't remember the syntax but I believe that you can stop this whole thing by adding a line at the beginning such as echo=off... or =no... or maybe noecho... can't remember...

    Anyway thats what it looks like to me from what you have posted.
     
    Last edited: 2005/05/29
  12. 2005/05/30
    goddez1

    goddez1 Inactive

    Joined:
    2002/01/12
    Messages:
    2,975
    Likes Received:
    49
    I see potential problems in what you have. I am unsure if this is your edited version of what you are seeing or a "quoted autoexec.bat" of what is actually in your autoexec.bat. I am also unsure of what you may have edited out that you shouldn't have. Do you have an autoexec.bak ,*.bac *.old or something similar that reflects what was in the file before you edited it? What was the original problem that prompted you to edit the auto*.bat in the first place?

    Barring the above concerns and questions and based solely on what you have posted so far, the bolded text below is all you'd need in the autoexec.bat. No spaces, no empty lines, no doubled semicolons (or what ever that little booger is called ;.
    PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\PAGEMGR;C:\PAGEMGR\IMGFOLIO;C:\PROGRA~1\DISKEE~1
    SET tvdumpflags=10


    You may wish to copy your current autoexec.bat to a floppy or somewhere in a folder (name_of _choice) and use the sysedit run line directions I previously gave you. Highlight all you have in the autoexec.bat (if all that is there is as you have stated previously) and delete it. Copy and paste the bolded text I have posted into you autoexec.bat, save changes and close/exit out of sysedit. This is assuming that the applications do exist and are in the folders as the paths indicate or point to.

    NOTES*
    You don't need the quotes or long file names when using DOS 8.3
    Empty lines or spaces between command lines will results in c:\ prompt displays.
    Improper spacing, quotes, or to many semicolons will result in a bad command line that does not execute and will be ignored. Improper spelling or bad/non existent paths to the files you will result in errors. Path variable merely tells DOS in which directories to look into first, besides the current one.

    Ordinarily autoexec.bat as meager as yours would not be needed but apparently you have zonealarm and a scanner(guessing) and a program, "DiskeeperLite ", that needs these parameters set or added to the path and included in the autoexec.bat file.

    ============
    I have kept this simple. No fancy batch code, no expanded explanations of dos commands. No tips. I did not want to risk confusing you or stressing you out. I assume you have been in the (searched) archives and have looked at past posts referenced or focusing on keyword filter of autoexec.bat and the win98 forum. If not perhaps you may wish to do so at your leisure. This may give you a better idea of what you may have done wrong, commands you could and can use, syntax that should be used, explanations of additional lines that applications can add, the order in which these command lines should fall....etc. It just may help you get a better feel or grasp on what should and shouldn't be done. This knowledge foundation may help you in the long run and you may find it interesting. As I recall we've had several good past discussions and syntax explanations on the subject.

    Other members may wish to improve on the suggested Autoexec.bat or may add additional comments or suggestions. I may have missed something or failed to consider something and these will be pointed out also. I am sure we will both welcome this and I for one would be most grateful. While, I try to be most careful advising others, when system files are envolved, it always makes me a little nervous for the other member. :)
     
    Last edited: 2005/05/30
  13. 2005/05/30
    BillyBob Lifetime Subscription

    BillyBob Inactive

    Joined:
    2002/01/07
    Messages:
    6,048
    Likes Received:
    0
    Looks good to me.

    Just add @ECHO OFF At the beginning if you do not want to see it appear on the screen.

    But dealing with the autoexec is a bit tough. Because it is as individual to each machine as the person behind the keyboard.

    And a bad Autoexec can stop a machine ( or at least some programs ) from working properly.

    Also the empty line(s) will cause the C:\ on the screen.

    BillyBob
     
  14. 2005/05/30
    BillyNeal

    BillyNeal Inactive Thread Starter

    Joined:
    2003/10/04
    Messages:
    35
    Likes Received:
    0
    Per your request, Goddez1:

    CURRENT AUTOEXEC.BAT FILE VIA SYSEDIT:

    C:\>
    PATH C:\PAGEMGR\IMGFOLIO;C:\PAGEMGR;
    C:\>

    SET Path=%Path%; "C:\Program Files\DiskeeperLite\ "
    Set tvdumpflags=10
    _____________________
    OLD AUTOEXEC.BAT FILE VIA NOTEPAD:
    PATH C:\PAGEMGR\IMGFOLIO;C:\PAGEMGR
    ___________________________________
    Why I did what I did: The laptop running on Win98SE became extremely sluggish and took forever to boot. I ran Spybot SD and Ad-aware without finding any spyware. I cleaned out the cache, temp files, and Internet history files. I noticed on booting up after the appearance of the Windows logo, a DOS screen that contained way too many strange settings. My judgement was that the settings shown were from the autoexec.bat file. Double ;; marks, double C:\> marks, double C:\ marks, etc. Not a clean looking autoexec.bat file I surmised (I guess incorrectly). So, I tried to clean up the autoexec.bat file, but it didn't seem to change the DOS screen during bootup.

    I am going to install the verbatim text provided by Goddez1 for the autoexec.bat file and see if the bootup screen changes. If not, maybe I just have to live with watching that DOS screen with all its double spacings and strange looking appearances.

    As a footnote, nothing I've tried so far has eleminated the sluggish behavior of the laptop in general and lengthy bootup process.
     
  15. 2005/05/30
    BillyNeal

    BillyNeal Inactive Thread Starter

    Joined:
    2003/10/04
    Messages:
    35
    Likes Received:
    0
    I installed the verbatim text, Goddez1 for the autoexec.bat and upon bootup received a message "Too Many Parameters ".

    I think I can work on the autoexec.bat structure to have a successful path. But can anyone explain why I'm seeing the text shown in panel #8 in this thread upon bootup. Is it supposed to be a DOS screen reflecting only what is contained in the autoexec.bat file? If not, where does the "other" information come from since the config.sys file is blank.
     
  16. 2005/05/30
    BillyNeal

    BillyNeal Inactive Thread Starter

    Joined:
    2003/10/04
    Messages:
    35
    Likes Received:
    0
    Here is the current autoexec.bat I refined and now have a very tidy DOS screen on bootup:

    PATH C:\PAGEMGR\IMGFOLIO;C:\PAGEMGR;
    SET PATH=%Path%; "C:\Program Files\DiskeeperLite\ "
    SET tvdumpflags=10

    There are about 5 lines of C:\ beneath the last line of the autoexec.bat, so maybe I need a semicolon at the end of the last line to prevent that.

    Thanks for the help. I'll now move on to the suggested reading offered by Goddez.
     
  17. 2005/05/30
    jaylach

    jaylach Inactive

    Joined:
    2005/04/05
    Messages:
    412
    Likes Received:
    0
    Those 5 lines of C:\ are most likely caused by spaces at the end of the file. put the cursor at the beginning of the line right after the SET tvdumpflags=10 and hold down the delete key for a few seconds. Will remove any inadvertant spaces or carriage returns at the end of the file.
     
  18. 2005/05/30
    NetDoc

    NetDoc Inactive

    Joined:
    2005/01/09
    Messages:
    215
    Likes Received:
    0
    This could be made a bit tidier by combining the two PATH statements like this:
    PATH C:\PAGEMGR\IMGFOLIO;C:\PAGEMGR; "C:\Program Files\DiskeeperLite\ "


    Check the end of your AUTOEXEC.BAT for unseen ENTER commands ar hard returns. Scroll down to the very end of the file (don't rely on what you see, use the down arrow) and remove all of the empty lines.

    Always good to keep learning.

    DRD
     
  19. 2005/05/30
    BillyBob Lifetime Subscription

    BillyBob Inactive

    Joined:
    2002/01/07
    Messages:
    6,048
    Likes Received:
    0
    Am I thinking wrong or is there something missing in these Autoexec.Bats being discussed ?

    Every Autoexec that I HAVE seen on 95 & 98 machines has had;

    C:\Windows;C:\WINDOWS\COMMAND in the path.

    And I believe it should to be there.

    Both of my 98SE machine have a path that reads:

    Path C:\WINDOWS;C:\WINDOWS\COMMAND;C:\;E:\IMS; E:\QTW\BIN.

    And I remember 95 being the same. And if I take the E:\IMS out, Cowboy Casino will not work.

    Which I believe would make the path being discussed look like

    Path
    C:\WINDOWS;C:\WINDOWS\COMMAND;C:\PAGEMGR\IMGFOLIO;C:\PAGEMGR;


    BillyBob
     
    Last edited: 2005/05/30
  20. 2005/05/30
    BillyNeal

    BillyNeal Inactive Thread Starter

    Joined:
    2003/10/04
    Messages:
    35
    Likes Received:
    0
    That took care of it. Thanks.
     
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.