Announcement

Collapse

Forum Rules and Etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Rule 1: Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Rule 2: Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Rule 3: Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


Rule 4: "PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Rule 5: Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

Help!! Dos Setup Disk Question

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    If the C:\DOS directory is in your path, it will often try to run the file in there instead of the one on the floppy. Try booting from the floppy and then type a:\sys.com c: and see if that works. Failing that, you can make a boot disk with setver installed (call it from the config.sys) and then use the setver command to tell DOS what version of itself to report to specific programs. Usually DOS utilities will run just fine on the wrong version of DOS if you fake it like that.

    Comment


      #17
      Originally posted by james1095 View Post
      ...Try booting from the floppy and then type a:\sys.com c: and see if that works...
      Just a reminder (again): if the version of DOS on the hard disk is different from that on the floppy, this will almost certainly make the hard disk unbootable!

      And using SETVER to fool DOS about its OWN programs instead of just installing the proper DOS programs in the first place is also asking for trouble.

      Comment


        #18
        Originally posted by james1095 View Post
        If the C:\DOS directory is in your path, it will often try to run the file in there instead of the one on the floppy. . . .
        DOS will look in your current directory first, then it will go through your path from the beginning and run the first match it finds. If you don't specify, then there is also a hierarchy of extensions. Also, there is absolutely no reason for having a C:\DOS directory unless that is your personal preference.
        WANTED: Cardinal 2450MNP modem.

        Comment


          #19
          Sean's trick is right. The date and time on DOS files matches. If I remember right, the time stamp matched the version number in those days. So DOS 3.1 files will have a time stamp of 3:10, while 3.2 files will have a stamp of 3:20. That can help you in getting the file versions right if they're mixed up.
          my blog: http://dfarq.homeip.net
          I wanna live where it's always Saturday. --Guadalcanal Diary

          Comment


            #20
            Someone on here was kind enough to send me a dos 3.31 setup so that should make everything work right. Regarding the date/time stamps, most of my dos files are 12:00pm so I dont think that tells me much. I'd much rather just install dos 3.31 since thats what the os was before I screwed things up and copied a few dos 3.1 files on there.

            Thank you got all your help everyone
            "Deep down I'm pretty superficial." - Ava Gardner

            My Computer Museum Website: http://tanrunomad.com/

            My YouTube Channel: http://www.youtube.com/brianpicchi

            Comment


              #21
              Originally posted by Ole Juul View Post
              DOS will look in your current directory first, then it will go through your path from the beginning and run the first match it finds. If you don't specify, then there is also a hierarchy of extensions. Also, there is absolutely no reason for having a C:\DOS directory unless that is your personal preference.
              I can think of a reason to have a DOS directory. If you have a program that accesses the hard drive a lot, moving the DOS commands to a separate directory allows you to set the PATH variable in the autoexec.bat file so that the directories that your program is accessing are searched before the DOS directory. Useful for running Windows, for example.

              Sean

              Comment


                #22
                I was thinking that the date would be the more useful indicator.

                Sean

                Comment


                  #23
                  Originally posted by MikeS View Post
                  Just a reminder (again): if the version of DOS on the hard disk is different from that on the floppy, this will almost certainly make the hard disk unbootable!

                  And using SETVER to fool DOS about its OWN programs instead of just installing the proper DOS programs in the first place is also asking for trouble.

                  It's not something I'd generally recommend, but it works in a pinch. I've used setver a few times to solve chicken/egg problems where I had setup files to install one version of DOS, but no boot disk with that version. Once you get the thing up and running you can do a proper install of whatever version you like.

                  Comment


                    #24
                    Originally posted by Floppies_only View Post
                    I can think of a reason to have a DOS directory. If you have a program that accesses the hard drive a lot, moving the DOS commands to a separate directory allows you to set the PATH variable in the autoexec.bat file so that the directories that your program is accessing are searched before the DOS directory. Useful for running Windows, for example.
                    I meant that it doesn't have to be "C:" or "DOS". Personally I very rarely use the MS utilities and besides the very useful help command I can't see why anybody would. They serve very little practical purpose since most of them are duplicated in better non-MS versions. My root directory only has two directories, SYS and TMP, and the C: drive is only used for system files. The SYS directory primarily contains "0", "1", "2", "F", and "MS". The 0, 1, and 2 contain the system binaries and the F contains the batch files which are what really define the system. The MS is, of course, the Microsoft files.

                    One of the reasons that I stayed with DOS and never moved to Win 3.1 was that the file structure was too messy for me and I would have lost control of the system. While still selling DOS, Microsoft hadn't yet figured out how to take control away from the user. The two hidden system files and the (optional) shell (command.com) were so incredibly functional just by themselves that users like me started ignoring their other shenanigans right from the start .

                    My path statement looks like this: path m:\no\;c:\sys\0;c:\sys\f;c:\sys\1;c:\sys\2;c:\sys\ ms;c:\
                    And my comspec: shell=c:\sys\ms\command.com c:\sys\ms /e:1024 /p /f

                    Regarding using the hard drive a lot, I solved that problem by having a carefully chosen selection of the most used utilities put in a hidden directory in one of the ram disks and turning off the HDD which rarely needs to start under normal use.
                    WANTED: Cardinal 2450MNP modem.

                    Comment


                      #25
                      You only need 3 files to make a disk bootable: IO.SYS, MSDOS.SYS and COMMAND.COM
                      I want to do this and can not see how you get the MBR on the disk.

                      Comment


                        #26
                        Originally posted by abpccpba View Post
                        I want to do this and can not see how you get the MBR on the disk.
                        To create the bootable disk you also need FORMAT and FDISK (and a system running an appropriate DOS or Windows of course).

                        Comment


                          #27
                          Originally posted by abpccpba View Post
                          I want to do this and can not see how you get the MBR on the disk.
                          The MBR is a product of the FDISK routine when you partition and format your HD.
                          Surely not everyone was Kung-Fu fighting

                          Comment

                          Working...
                          X