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

5162 serial port, 9600bps, interlink -- use xcopy with /v?

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

    5162 serial port, 9600bps, interlink -- use xcopy with /v?

    5162 serial port, 9600bps, interlink -- use xcopy with /v?

    I just started >3hr xcopy transfer of >14MB (I had no more hard drive space to zip the files before transferring).
    I'm xferring nearly 1,000 files and did not want to have the overhead of verifying file transfers..

    I have not xcopied over interlnk in a bazillion years.
    What is your confidence level of me not using the verify switch with xcopy?
    Wanted: Sony CDU-535 or CDU6250 CD-ROM Drive (Caddy drive) for 8-bit Sony Interface Card
    sigpic <-- This is me using my IBM PC 5150 over Ethernet TCP/IP network with assignable drive letters

    #2
    I don't believe that xcopy has any knowledge of interlink. The speed should be the same with or without the /v. The verify is probably to verify that it was written from ram to the hard drive properly.

    Comment


      #3
      Oh.. I was thinking xcopy verified from source to target.. Sheesh.
      Wanted: Sony CDU-535 or CDU6250 CD-ROM Drive (Caddy drive) for 8-bit Sony Interface Card
      sigpic <-- This is me using my IBM PC 5150 over Ethernet TCP/IP network with assignable drive letters

      Comment


        #4
        Interlink is listed as having error correcting ability so there should not be many errors get through. Retries will slow the transfer down.

        If you don't want to spend the time verifying every file, create hash values for every file on both systems and then compare the hashes.

        I would still run some form of verification after the transfer ends. It is easy to repeat the transfer of any files that failed while the system is still hooked up.

        Comment


          #5
          My view of this is, if you don't want to take the time to verify the data was correctly copied, then don't bother doing the copy.

          (Which is why I still have my original BASIC programs from over 30 years ago ...)

          Comment


            #6
            Or, you could use a very simple parallel port network like U-NET II.
            PM me if you're looking for 3" or 5" floppy disks. EMail For everything else, Take Another Step

            Comment


              #7
              Originally posted by luvit View Post
              I have not xcopied over interlnk in a bazillion years.
              What is your confidence level of me not using the verify switch with xcopy?
              I wouldn't be too worried but you could always do a global file compare using a recursion utility such as SWEEP and FC or equivalent:
              http://www.cadalyst.com/management/a...s-toolbox-6396

              Comment


                #8
                Originally posted by joekster View Post
                I don't believe that xcopy has any knowledge of interlink. The speed should be the same with or without the /v. The verify is probably to verify that it was written from ram to the hard drive properly.
                What makes you think that, why does XCOPY have to have a knowledge of Interlink, and what would be the point of verifying if not to compare the copied file to the original?

                Comment


                  #9
                  FWIW, ZIPping is an excellent method of preserving the integrity of files that need to be transferred. When files are unZIPped their CRCs are verified.
                  PM me if you're looking for 3" or 5" floppy disks. EMail For everything else, Take Another Step

                  Comment


                    #10
                    Originally posted by MikeS View Post
                    What makes you think that, why does XCOPY have to have a knowledge of Interlink, and what would be the point of verifying if not to compare the copied file to the original?
                    See this.
                    Looking for a cache card for the "ICL ErgoPRO C4/66d V"

                    Comment


                      #11
                      Originally posted by Krille View Post
                      See this.
                      Interesting info, thanks!

                      I almost always use PKZIP when transferring files, not only to save time but also for the reason Stone mentioned, so I never use any verify options; when it's critical I use FC as Microsoft also suggests.

                      Comment


                        #12
                        PKZIP is so versatile and I use it all the time so I have BAT files for it. The main one is U.BAT and it reads... pkunzip %1 %2 %3 %4.
                        PM me if you're looking for 3" or 5" floppy disks. EMail For everything else, Take Another Step

                        Comment


                          #13
                          The /V option on the standard DOS commands does not verify the contents - it just makes sure that the target is readable.

                          This dates back to the floppy era ... it was assumed that if there was a problem, it was due to bad media. If the block was bad, a verify pass on the newly written data would detect that.

                          Comment


                            #14
                            Originally posted by mbbrutman View Post
                            The /V option on the standard DOS commands does not verify the contents - it just makes sure that the target is readable.

                            This dates back to the floppy era ... it was assumed that if there was a problem, it was due to bad media. If the block was bad, a verify pass on the newly written data would detect that.
                            That's pretty well what Krille's link said, but thanks for making it explicit.

                            Comment


                              #15
                              That's funny. Nothing in the link that Krille posted has the word "floppy" in it. Or the insight that it was just a matter of verifying that if the write was good, the data was probably good too.

                              Troll somebody else.

                              Comment

                              Working...
                              X